Base Packaging Guidelines
Devstack is a great template for a development environment, but we don't have example packaging for production usage. This means that each downstream package has to roll-their-own, and I've also observed some pretty big gotchas, like mixing user configuration into the routing files (Bug #956709) If we had an example production configuration: 1) We would identify and fix any packaging issues (early) 2) Packagers wouldn't each have to solve these issues (duplication of effort, fragmentation issues) 3) We would hopefully converge on the same basic setup - e.g. service names, log file locations etc, which would make documentation and problem diagnosis much easier 4) It should be practical to run a production deployment from source I hope that the various OS packaging efforts can contribute their problems & solutions, that we can pick the best, and produce either a document or automated deployment code. Hopefully this can then help downstream packagers. I've been doing some investigations here: https://github.com/justinsb/openstack-simple-config (Session lead is justinsb)
Attendance numbers do not account for private attendees. Get there early!
Remove this from your schedule?
You may not be able to get back in if this is full.