Hi, added [ops] tag. As an operator the mentioned change of related module impact not only the openstack infrastructur. As long as the module names differ, there is no big issue, but as soon as they have the same name (as sysctl and powerdns) transition is difficult. Please keep also in mind, that usually we avoid making big bang migrations, migration modules means migration all related openstack projects to the next version the same time .. I suggest to use wrapping classes and ressources for at least 2 releases (like for deprecations) so the transition can be done smooth. Thanks for considering ! Benedikt On 28.02.19 17:13, Alfredo Moralejo Alonso wrote:
On Thu, Feb 28, 2019 at 2:32 AM Chris Hoge <chris@openstack.org <mailto:chris@openstack.org>> wrote:
> On Feb 27, 2019, at 6:59 AM, Alex Schultz <aschultz@redhat.com <mailto:aschultz@redhat.com>> wrote: > > On Tue, Feb 26, 2019 at 5:38 PM Chris Hoge <chris@openstack.org <mailto:chris@openstack.org>> wrote: >> >> Welcome Eduardo, and Hunter and Jason. >> >> For the initial work, we will be looking at replacing GPL licensed modules in >> the Puppet-OpenStack project with Apache licensed alternatives. Some of the >> candidate module transitions include: >> >> antonlindstrom/puppet-powerdns -> sensson/powerdns >> >> duritong/puppet-sysctl -> thias/puppet-sysctl >> >> puppetlabs/puppetlabs-vcsrepo -> voxpupuli/puppet-git_resource >> >> Feedback and support on this is welcome, but where possible I would like for >> the students to be sending the patches up and collaborating to to help make these >> transitions (where possible, it’s my understanding that sysctl may pose serious >> challenges). Much of it should be good introductory work to our community >> workflow, and I'd like for them to have an opportunity to have a >> successful set of initial patches and contributions that have a positive >> lasting impact on the community. >> > > Please note that this also has an impact on TripleO and any other > downstream consumers of the puppet modules. Specifically for TripleO > we'll need to consider how packaging these will come into play and if > they aren't 1:1 compatible it may break us. StarlingX might also be > impacted as well.
Given the difficulties of coordinating the limited scope of the capstone project and release schedule constraints of RDO and TripleO, we've decided to focus on work related to other OpenStack projects. Thanks for your feedback.
As follow-up in case someone wants to take this over in the future:
antonlindstrom/puppet-powerdns -> sensson/powerdns
puppet-powerdns is used only in puppet-designate. old and new package are not backwards compatible but it should be quite easy to just coordinate tje package change preparation in RDO with the upstream change to implement the required changes.
duritong/puppet-sysctl -> thias/puppet-sysctl
Old and new modules are not backwards compatible. This is the hardest one. To ease the transition we could treat them as different packages with different names and play with dependencies but both modules can not live together so it'd require change between all projects involved, puppet-neutron, puppet-tripleo, packstack and puppet-openstack-integration. Definitively it will take time to coordinate all changes and make a smooth transition.
puppetlabs/puppetlabs-vcsrepo -> voxpupuli/puppet-git_resource
- This shouldn't be big issue, it's just two different unrelated modules, so both modules could live together in the transition.
-Chris
> >> Thanks in advance, and my apologies for not communicating these efforts >> to the mailing list sooner. >> >> -Chris >> >>> On Feb 19, 2019, at 6:40 PM, Urbano Moreno, Eduardo <eduardo.urbanomoreno@ndsu.edu <mailto:eduardo.urbanomoreno@ndsu.edu>> wrote: >>> >>> Hello OpenStack community, >>> >>> I just wanted to go ahead and introduce myself, as I am a part of the NDSU Capstone group! >>> >>> My name is Eduardo Urbano and I am a Jr/Senior at NDSU. I am currently majoring in Computer Science, with no minor although that could change towards graduation. I am currently an intern at an electrical supply company here in Fargo, North Dakota known as Border States. I am an information security intern and I am enjoying it so far. I have learned many interesting security things and have also became a little paranoid of how easily someone can get hacked haha. Anyways, I am so excited to be on board and be working with OpenStack for this semester. So far I have learned many new things and I can’t wait to continue on learning. >>> >>> Thank you! >>> >>> >>> -Eduardo >> >> >