I support 12 factor. But 12 factor only works if you can commit to always deploying on top of 12 factor tools. If OpenStack committed to only ever deploying api services on k8s then my answer might be different. but so far has been unable to do that. Barring that, I think simplifying the operators life so you get more users/contributors has priority over pure 12 factor ideals.
It also is about getting Project folks working together to see how their parts fit (or not) in the greater constilation. Just writing a document on how you could fit things together doesn't show the kinds of suffering that actually integrating it into a finished whole could show. Either way though, I think a unified db-sync would go a long way to making OpenStack easier to maintain as an Operator. Thanks, Kevin ________________________________________ From: Jay Pipes [jaypi...@gmail.com] Sent: Tuesday, April 24, 2018 9:13 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier? On 04/24/2018 12:04 PM, Fox, Kevin M wrote: > Could the major components, nova-api, neutron-server, glance-apiserver, etc > be built in a way to have 1 process for all of them, and combine the upgrade > steps such that there is also, one db-sync for the entire constellation? So, basically the exact opposite of the 12-factor app design that "cloud-native" people espouse? -jay __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
