Author(s):	Robert Collins
Location	MCC4
Date	feb Fri 01	Days Raw Files
Start	10:40	First Raw Start	error-in-template
Duration	0:45:00	Offset	None
End	11:25	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30331/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Openstack_on_Openstack_a_single_management_API_for_all_your_servers.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Typical cloud deployments - be it Openstack, Eucalyptus etc - have a separate control layer installed and upgraded using separate tools (which might be hand-configured PXE + preseeding, Cobbler, Orchestra/MAAS, FAI etc). As a result you have two distinct provisioning systems in play, which allows for more user error and increased special cases in automation. Using Openstack’s bare-metal hypervisor, my team are building a fully self contained cloud, where the control layer for the cloud is itself deployed and upgraded via the same cloud API. Come hear me talk about the challenges involved in bootstrapping and operating such an environment, the benefits it can bring and what you can do with it! markdown
Comment:	production notes