Author(s):	Laura Thomson,Shyam Mani,Justin Dow
Location	Caro
Date	jan Tue 17	Days Raw Files
Start	15:40	First Raw Start	error-in-template
Duration	0:50:00	Offset	None
End	16:30	Last Raw End
Chapters
Total cuts_time	None min.

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

assets release.pdf Moving_Day_Migrating_Big_Data_from_A_to_B.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:	In January 2011 we moved the Mozilla crash reporting system from old creaky hardware in San Jose to a new shiny datacenter in Phoenix. This system contains more than 40TB of data in HBase, the Hadoop database, and PostgreSQL. The data collecting app has a requirement for close to 100% uptime. On top of that we have data processing, an API, and a webapp. After many months of work, the migration went seamlessly. In this session we’ll talk about: - The checklist manifesto, reprised, and understanding the critical path - How to move all that data in a reasonable timeframe - The importance of devops culture in success - Automating packaging and configuration and how it will save you - Understanding the difference between old and new platforms: correctness testing, load testing, and smoke testing Attendees should walk away with an outline of everything they’ll need to do to achieve a successful data center migration. markdown
Comment:	production notes