Re: [openstack-dev] [fuel][puppet] Managing upstream puppet modules in fuel-library under librarian
On 07/17/2015 11:27 PM, Dmitry Borodaenko wrote: One of the concerns raised by TC in response to the proposal to add Fuel to OpenStack Projects [0] is the fact that fuel-library includes copies of upstream Puppet modules, most importantly from OpenStack Puppet [1]. [0] https://review.openstack.org/199232 [1] https://lwn.net/Articles/648331/ I have brought this up in the Fuel weekly meeting [2], and we have agreed to start implementing the proposal from Alex Schultz to use puppet-librarian to manage upstream modules [3]. [2] http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-07-16-16.00.log.html#l-245 [3] http://lists.openstack.org/pipermail/openstack-dev/2015-June/067806.html We are days away from Feature Freeze for Fuel 7.0 scheduled for July 23 [4], so it's not reasonable to make librarian mandatory for all upstream modules just yet, but I believe that we should make full migration to librarian a blocker requirement for Fuel 8.0. Thanks for stepping up to address this requested change, Dima. I've given a preliminary review to Alex's puppet-librarian patch and things look fine from my perspective. I'm quite interested to know Emilien and Chris Hoge's opinions on this direction and proposed timeline. [4] https://wiki.openstack.org/wiki/Fuel/7.0_Release_Schedule In the meanwhile, we're going to try to implement integration of the newly added puppet-ironic module under librarian [5][6][7]. [5] https://review.openstack.org/194184 [6] https://review.openstack.org/202763 [7] https://review.openstack.org/202767 To make sure this effort does not block integration of Ironic support in Fuel 7.0 and does not impact the Feature Freeze, we've set a deadline for this effort until Tuesday July 21. Fuelers and other Puppet experts, please help Alex and Pavlo get this done on time by reviewing their changes and offering advice. It is a small but crucial step towards full convergence with upstream, it would help a lot if we could confirm now that this approach is viable. Agreed, reviews from fuel-core folks would be very much appreciated. Best, -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
Re: [openstack-dev] [fuel][puppet] Managing upstream puppet modules in fuel-library under librarian
Dmitry, +1 to full migration to librarian a blocker requirement for Fuel 8.0. thanks, dims On Fri, Jul 17, 2015 at 11:27 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: One of the concerns raised by TC in response to the proposal to add Fuel to OpenStack Projects [0] is the fact that fuel-library includes copies of upstream Puppet modules, most importantly from OpenStack Puppet [1]. [0] https://review.openstack.org/199232 [1] https://lwn.net/Articles/648331/ I have brought this up in the Fuel weekly meeting [2], and we have agreed to start implementing the proposal from Alex Schultz to use puppet-librarian to manage upstream modules [3]. [2] http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-07-16-16.00.log.html#l-245 [3] http://lists.openstack.org/pipermail/openstack-dev/2015-June/067806.html We are days away from Feature Freeze for Fuel 7.0 scheduled for July 23 [4], so it's not reasonable to make librarian mandatory for all upstream modules just yet, but I believe that we should make full migration to librarian a blocker requirement for Fuel 8.0. [4] https://wiki.openstack.org/wiki/Fuel/7.0_Release_Schedule In the meanwhile, we're going to try to implement integration of the newly added puppet-ironic module under librarian [5][6][7]. [5] https://review.openstack.org/194184 [6] https://review.openstack.org/202763 [7] https://review.openstack.org/202767 To make sure this effort does not block integration of Ironic support in Fuel 7.0 and does not impact the Feature Freeze, we've set a deadline for this effort until Tuesday July 21. Fuelers and other Puppet experts, please help Alex and Pavlo get this done on time by reviewing their changes and offering advice. It is a small but crucial step towards full convergence with upstream, it would help a lot if we could confirm now that this approach is viable. Thank you, -- Dmitry Borodaenko __ 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 -- Davanum Srinivas :: https://twitter.com/dims __ 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-dev] [fuel][puppet] Managing upstream puppet modules in fuel-library under librarian
One of the concerns raised by TC in response to the proposal to add Fuel to OpenStack Projects [0] is the fact that fuel-library includes copies of upstream Puppet modules, most importantly from OpenStack Puppet [1]. [0] https://review.openstack.org/199232 [1] https://lwn.net/Articles/648331/ I have brought this up in the Fuel weekly meeting [2], and we have agreed to start implementing the proposal from Alex Schultz to use puppet-librarian to manage upstream modules [3]. [2] http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-07-16-16.00.log.html#l-245 [3] http://lists.openstack.org/pipermail/openstack-dev/2015-June/067806.html We are days away from Feature Freeze for Fuel 7.0 scheduled for July 23 [4], so it's not reasonable to make librarian mandatory for all upstream modules just yet, but I believe that we should make full migration to librarian a blocker requirement for Fuel 8.0. [4] https://wiki.openstack.org/wiki/Fuel/7.0_Release_Schedule In the meanwhile, we're going to try to implement integration of the newly added puppet-ironic module under librarian [5][6][7]. [5] https://review.openstack.org/194184 [6] https://review.openstack.org/202763 [7] https://review.openstack.org/202767 To make sure this effort does not block integration of Ironic support in Fuel 7.0 and does not impact the Feature Freeze, we've set a deadline for this effort until Tuesday July 21. Fuelers and other Puppet experts, please help Alex and Pavlo get this done on time by reviewing their changes and offering advice. It is a small but crucial step towards full convergence with upstream, it would help a lot if we could confirm now that this approach is viable. Thank you, -- Dmitry Borodaenko __ 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
