Greetings, Please, be informed that the source code of Nailgun API extension has landed to the designated repository [1]. Project was code named 'tuning-box'. We are working to integrate it into the build and testing systems provided by Fuel infra. I suggest that the FFE can be closed.
I'd like to thank the community for the trust you've put in us. Hope we laid a foundation for more flexible and modular architecture for the future Fuel versions. Sorry for the delay with this heads up. [1] https://git.openstack.org/openstack/tuning-box.git -- Best regards, Oleg Gelbukh On Fri, Mar 4, 2016 at 12:27 AM, Dmitry Borodaenko <dborodae...@mirantis.com > wrote: > Granted, merge deadline March 24, no impact expected in core components > (fuel-library, fuel-web, fuel-ui). > > -- > Dmitry Borodaenko > > > On Tue, Mar 01, 2016 at 04:22:05PM +0300, Oleg Gelbukh wrote: > > Greetings, > > > > As you might know, we are working on centralised storage for > > deployment configuration data in Fuel. Such store will allow external > > 3rd-party services to consume the entirety of settings provided by > > Fuel to deployment mechanisms on target nodes. It will also allow to > > manage and override the settings via simple client application. > > > > This change is required to enable Puppet Master based LCM solution. > > > > We request a FFE for this feature for 3 weeks, until Mar 24. By that > > time, we will provide tested solution in accordance with the following > > specifications [1] [2] > > > > The feature includes 3 main components: > > 1. Extension to Nailgun API with separate DB structure to store > serialized data > > 2. Backend library for Hiera to consume the API in question to lookup > > values of the certain parameters > > 3. Astute task to download all serialized data from nodes and upload > > them to ConfigDB API upon successful deployment of cluster > > > > Since introduction of stevedore-based extensions [3], we could develop > > extensions in separate code repos. This makes change to Nailgun > > non-intrusive to core code. > > Backend library will be implemented in fuel-library code tree and > > packaged as a sub-package. This change also doesn't require changes in > > the core code. > > Astute task will add a task in the flow. We will make this task > > configurable, i.e. normally this code path won't be used at all. It > > also won't touch core code of Astute. > > > > Overall, I consider this change as low risk for integrity and timeline > > of the release. > > > > Please, consider our request and share concerns so we could properly > > resolve them. > > > > [1] > https://blueprints.launchpad.net/fuel/+spec/upload-deployment-facts-to-configdb > > [2] > https://blueprints.launchpad.net/fuel/+spec/serialized-facts-nailgun-api > > [3] > https://blueprints.launchpad.net/fuel/+spec/stevedore-extensions-discovery > > > > -- > > Best regards, > > Oleg Gelbukh > > Mirantis Inc. > > > > > __________________________________________________________________________ > > 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 >
__________________________________________________________________________ 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
