[openstack-dev] [puppet] Stepping down from puppet core
Hello Puppeteers! I'd like to step down as a core review for the OpenStack Puppet. Unfortunately, as you could see I didn't participate in Puppet activities last few months. My career objective has changed and now I won't be able even to take a look on OpenStack Puppet. This was an exciting experience for me to work with you and I will never forget our meetings in Austin. We did several releases together, we applied common patterns for all our modules, implemented clear integration process for new projects and many many other cool stuff. I am glad that I worked with such strong leaders as Alex and Emilien! Puppeteers, I will miss all of you! __ 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] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules
+1 2017-01-21 3:07 GMT+04:00 Emilien Macchi <emil...@redhat.com>: > plus one > > On Fri, Jan 20, 2017 at 12:19 PM, Alex Schultz <aschu...@redhat.com> > wrote: > > Hey Puppet Cores, > > > > I would like to nominate Zhong Shengping as a Core reviewer for the > > Puppet OpenStack modules. He is an excellent contributor to our > > modules over the last several cycles. His stats for the last 90 days > > can be viewed here[0]. > > > > Please response with your +1 or any objections. If there are no > > objections by Jan 27 I will add him to the core list. > > > > Thanks, > > -Alex > > > > [0] http://stackalytics.com/report/contribution/puppet% > 20openstack-group/90 > > > > > __ > > 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 > > > > -- > Emilien Macchi > > __ > 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 > -- Thanks, Ivan Berezovskiy Senior Deployment Engineer at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules
+1, well done! 2017-01-20 12:20 GMT+04:00 Denis Egorenko <degore...@mirantis.com>: > +1 > > 2017-01-20 4:10 GMT+04:00 Emilien Macchi <emil...@redhat.com>: > >> On Thu, Jan 19, 2017 at 5:25 PM, Alex Schultz <aschu...@redhat.com> >> wrote: >> > Hey Puppet Cores, >> > >> > I would like to nominate Mykyta Karpin as a Core reviewer for the >> > Puppet OpenStack modules. He has been providing quality patches and >> > reviews for some time now and I believe he would be a good addition to >> > the team. His stats for the last 90 days can be viewed here[0] >> > >> > Please response with your +1 or any objections. If there are no >> > objections by Jan 26, I will add him to the core list. >> >> +1, that's well deserved. >> Thanks Mykyta for your contributions! Keep rocking :-) >> >> > Thanks, >> > -Alex >> > >> > [0] http://stackalytics.com/report/contribution/puppet%20opensta >> ck-group/90 >> > >> > >> __ >> > OpenStack Development Mailing List (not for usage questions) >> > Unsubscribe: openstack-dev-requ...@lists.op >> enstack.org?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> -- >> Emilien Macchi >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Best Regards, > Egorenko Denis, > Senior Deployment Engineer > Mirantis > > __ > 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 > > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [puppet] Core nominations
+1, great job, guys! Keep rocking! 2016-09-15 18:03 GMT+03:00 Denis Egorenko <degore...@mirantis.com>: > +1, good job > > 2016-09-15 17:44 GMT+03:00 Matt Fischer <m...@mattfischer.com>: > >> +1 to all. Thanks for your work guys! >> >> On Thu, Sep 15, 2016 at 6:59 AM, Emilien Macchi <emil...@redhat.com> >> wrote: >> >>> While our group keeps moving, it's time to propose again new people >>> part of core team. >>> >>> Dmitry Tantsur / puppet-ironic >>> Dmitry is the guardian of puppet-ironic. He's driving most of the >>> recent features in this module and he now fully deserves being core on >>> it. >>> >>> Pradeep Kilambi / puppet-aodh,ceilometer,gnocchi,panko >>> Prad is our Telemetry guru and he never stops to bring attention on >>> these modules! Keep going Prad, we appreciate your help here. >>> >>> Iury Gregory / all modules >>> Iury is our padawan. Still learning, but learning fast, he has been a >>> continuous contributor over the last months. He's always here on IRC >>> and during meetings to help. >>> He always volunteer to help and not for the most fun tasks. (He drove >>> the authtoken work during Newton). I would like to reward his work and >>> show that we trust him to be a good core reviewer. >>> Iury, keep going in your efforts! >>> >>> >>> If your name is not here yet, please keep doing consistent work, help >>> in bug triage, maintain stable CI, doing good reviews, improve our >>> documentation, etc. >>> >>> As usual, Puppet OpenStack core team is free to -1 / +1 the proposal. >>> >>> Thanks, >>> -- >>> Emilien Macchi >>> >>> >>> __ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: openstack-dev-requ...@lists.op >>> enstack.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:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > Best Regards, > Egorenko Denis, > Senior Deployment Engineer > Mirantis > > __ > 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 > > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] Propose Denis Egorenko for fuel-library core
+1, great job! 2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya <bdobre...@mirantis.com>: > +1 > > On 25.08.2016 21:08, Stanislaw Bogatkin wrote: > > +1 > > > > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko > > <adide...@mirantis.com <mailto:adide...@mirantis.com>> wrote: > > > > +1 > > > > On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko > > <svasile...@mirantis.com <mailto:svasile...@mirantis.com>> wrote: > > > > +1 > > > > > > /sv > > > > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > <http://openstack-dev-requ...@lists.openstack.org?subject: > unsubscribe> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack-dev <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://openstack-dev-requ...@lists.openstack.org?subject: > unsubscribe> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > > > > > > > > -- > > with best regards, > > Stan. > > > > > > > __ > > 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 > > > > > -- > Best regards, > Bogdan Dobrelya, > Irc #bogdando > > __ > 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 > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core
+1, good job! 2016-07-28 18:50 GMT+03:00 Matt Fischer <m...@mattfischer.com>: > +1 from me! > > On Jul 28, 2016 9:20 AM, "Emilien Macchi" <emil...@redhat.com> wrote: > >> You might not know who Sofer is but he's actually "chem" on IRC. >> He's the guy who will find the root cause of insane bugs, in OpenStack >> in general but also in Puppet OpenStack modules. >> Sofer has been working on Puppet OpenStack modules for a while now, >> and is already core in puppet-keystone. Many times he brought his >> expertise to make our modules better. >> He's always here on IRC to help folks and has excellent understanding >> at how our project works. >> >> If you want stats: >> http://stackalytics.com/?user_id=sofer-athlan-guyot=commits >> I'm quite sure Sofer will make more reviews over the time but I have >> no doubt he fully deserves to be part of core reviewers now, with his >> technical experience and involvement. >> >> As usual, it's an open decision, please vote +1/-1 about this proposal. >> >> Thanks, >> -- >> Emilien Macchi >> >> __ >> 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 > > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [puppet] proposal about puppet versions testing coverage
> > Greating folks, > > In a recent poll [1], we asked to our community to tell which version > of Puppet they were running. > The motivation is to make sure our Puppet OpenStack CI test the right > things, that are really useful. > > Right now, we run unit test jobs on puppet on 3.3, 3.4, 3.6, 3.8, 4.0 > and latest (current is 4.5). > We also have functional jobs (non-voting, in periodic pipeline), that > run puppet 4.5. Those ones break very often because nobody (except > me?) regularly checks puppet4 periodic jobs. > > So here's my proposal, feel fee to comment: > > * Reduce puppet versions testing to 3.6, 3.8, 4.5 and latest (keep the > last one non-voting). It seems that 3.6 and 3.8 are widely used by our > consumers (default in centos7 & ubuntu LTS), and 4.5 is the latest > release in the 4.x series. > * Move functional puppet4 jobs from experimental to check pipeline > (non-voting). They'll bring very useful feedback. It will add 6 more > jobs in the check queue, but since we will drop 2 unit tests jobs (in > both check & gate pipelines), it will add 2 jobs at total (in term of > time, unit tests jobs take 15 min and functional jobs take ~30 min) so > the impact of node consumption is IMHO not relevant here. > > [1] > https://docs.google.com/forms/d/1rJZxP52LyrFhFTy8w4J_5tnA7-A5g32YVhHSaCd7-F8/edit#responses +1 I am also agree with Matt and Denis that we should work on making functional puppet4 jobs stable and then enable them in voting mode. -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [puppet] Proposing Ivan Berezovskiy for puppet-openstack-core
Thank you all for the trust! I'll do my best :) 2016-05-19 18:57 GMT+03:00 Alex Schultz <aschu...@mirantis.com>: > +1 great job Ivan > > On Thu, May 19, 2016 at 8:32 AM, Matt Fischer <m...@mattfischer.com> > wrote: > >> +1 from me! >> >> On Thu, May 19, 2016 at 8:17 AM, Emilien Macchi <emil...@redhat.com> >> wrote: >> >>> Hi, >>> >>> I don't need to introduce Ivan Berezovskiy (iberezovskiy on IRC), he's >>> been doing tremendous work in Puppet OpenStack over the last months, >>> in a regular way. >>> >>> Some highlights about his contributions: >>> * Fantastic work on puppet-oslo! I really mean it... Thanks to you and >>> others, we have now consistency for Oslo parameters in our modules. >>> * Excellent quality of code in general and in reviews. >>> * Full understanding of our process (code style, release notes, CI, doc, >>> etc). >>> * Very often, he helps with CI things (Fuel or Puppet OpenStack CI). >>> * Constant presence on IRC meetings and in our channel where he never >>> hesitate to give support. >>> >>> I would like to propose him part of our Puppet OpenStack core team, as >>> usual please -1/+1. >>> >>> Thanks Ivan for your hard work, keep going! >>> -- >>> Emilien Macchi >>> >>> >>> __ >>> 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 > > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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][Fuel-Library] Fuel CI issues
Hello, Fuelers! Yesterday we've faced an issue which came from puppet-neutron module: LP #1549934 <https://bugs.launchpad.net/fuel/+bug/1549934>. Fix was prepared very fast: https://review.openstack.org/#/c/284882/ (thanks Sergey for this). So, If CI is red on your patch please re-base it on top of master. Anyway, this issue affected a lot of patches and blocked some developers, because BVT and neutron_smoke tests was also broken. We need to find a way how to minimize risks and affection of such changes on fuel-library. We have jobs which monitors upstream patches: https://ci.fuel-infra.org/view/puppet-openstack/ Let's start to monitor those jobs on daily basis. We should have at least 1 (ideally 2 or more) engineers which are responsible for analysis of those CI failures. If patch to puppet module is incorrect - we should review it with explanation what is actually wrong. If patch is correct, but breaks current Fuel CI, it means that problem is in our side and we should prepare fuel-library adapt patch to fix the issue. Ideally, we should have an ability to test this fuel-library patch together with upstream one e.g. using 'Depends on' in commit message. Thoughts? -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core
+1 for Matthew! 2016-02-24 17:34 GMT+03:00 Fedor Zhadaev <fzhad...@mirantis.com>: > +1 > > On Wed, Feb 24, 2016 at 5:30 PM Julia Aranovich <jkirnos...@mirantis.com> > wrote: > >> +1 >> >> On Wed, Feb 24, 2016 at 4:57 PM Denis Egorenko <degore...@mirantis.com> >> wrote: >> >>> I'm not a fuel core member, but i also would like to vote +1 for >>> Matthew. He's doing great job! >>> >>> 2016-02-24 16:02 GMT+03:00 Aleksandr Didenko <adide...@mirantis.com>: >>> >>>> +1 >>>> >>>> On Wed, Feb 24, 2016 at 1:50 PM, Vladimir Kuklin <vkuk...@mirantis.com> >>>> wrote: >>>> >>>>> Fellow Fuelers >>>>> >>>>> I would like to kindly ask you to consider voting for Matthew Mosesohn >>>>> as a Fuel Library Core >>>>> reviewer. >>>>> >>>>> Matthew has been working with Fuel since its inception, worked on >>>>> countless amount of features, such as : >>>>> >>>>> Master Node Upgrades and Backup >>>>> Improvements to Fuel Infra >>>>> Mitaka, Kilo and Juno Support >>>>> Detachable Services Plugins >>>>> RHOS Support in Fuel >>>>> UCA Support >>>>> Refactoring of Haproxy and Firewall pieces >>>>> >>>>> He has also been known as our Fuel Master node and Docker guru and has >>>>> been continuously working on bugfixing where he scores as a bug squashing >>>>> monster with more than 150 bugfixes to all the parts of Fuel Library (#1 >>>>> throughout FL history). >>>>> >>>>> As you can see, there is not a piece of Fuel Library that he has not >>>>> yet gained experience with. >>>>> >>>>> And this can easily be fetched with simple statistics of Matt's >>>>> contribution. He is the topmost contributor to all Fuel projects among all >>>>> Fuel Library folks and is the 3rd contributor of Fuel Library. >>>>> He also reviews a lot and has a fair amount of -1's (he is not as >>>>> cruel as me, though :-)) >>>>> >>>>> Having that said, I would like to open the vote to promote Matt to >>>>> OpenStack Fuel Library core reviewers. >>>>> >>>>> -- >>>>> Yours Faithfully, >>>>> Vladimir Kuklin, >>>>> Fuel Library Tech Lead, >>>>> Mirantis, Inc. >>>>> +7 (495) 640-49-04 >>>>> +7 (926) 702-39-68 >>>>> Skype kuklinvv >>>>> 35bk3, Vorontsovskaya Str. >>>>> Moscow, Russia, >>>>> www.mirantis.com <http://www.mirantis.ru/> >>>>> www.mirantis.ru >>>>> vkuk...@mirantis.com >>>>> >>>>> >>>>> __ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> Egorenko Denis, >>> Senior Deployment Engineer >>> Mirantis >>> >>> __ >>> 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 >> > -- > Kind Regards, > Fedor Zhadaev > > skype: zhadaevfm > IRC: fzhadaev > > __ > 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 > > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] Testing before switching to upstream librarian
Hi, First of all, I want to mention (I don't blame anyone), that two patchsets in bug description ([0], [1]) were not merged into upstream puppet-openstacklib module (and commit messages don't contain links to upstream review). I see only one proposed patch [2] from Dmitry Ilyin, which was abandoned at Sep 18. Now it's restored and those issues should be fixed using it. Second, our patches (moving to librarian) were tested several times under Fuel CI jobs, on BVTs, smoke_neutron tests with Kilo and Liberty code. Unfortunately, we didn't find problems with deployment. Third, two weeks passed after merging of our patches for librarian, and only now we are speaking about regressions. Patch [2] covers missing two commits [0], [1], that's why I suggest to get it merged and then recheck issues, because it's very late for reverting. [0] - https://review.openstack.org/#/c/219668/ [1] - https://review.openstack.org/#/c/223676/ [2] - https://review.openstack.org/#/c/220224/ 2015-10-19 20:59 GMT+03:00 Sergii Golovatiuk <sgolovat...@mirantis.com>: > Hi, > > The policy should be revert, IMHO. cherry-pick doesn't guarantee the > consistency, so it will take more time... Also this way gives time to write > tests to exclude the regression in future. > > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Mon, Oct 19, 2015 at 6:52 PM, Matthew Mosesohn <mmoses...@mirantis.com> > wrote: > >> Hi Fuelers, >> >> It seems we have a regression on two critical bugs because of switching >> Fuel to puppet-openstacklib: >> https://bugs.launchpad.net/fuel/+bug/1507685 >> >> This regressed to patches that were in Fuel Library that addressed two >> bugs marked as Critical. >> >> We should improve the acceptance criteria for moving to upstream modules >> to ensure no bugs are regressed that relate to the particular Puppet module >> being migrated. >> >> Secondly, what should our policy be? Revert the switch to upstream >> module? Or just work on cherry-picking the appropriate fixes? >> >> Best Regards, >> Matthew Mosesohn >> >> __ >> 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 > > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [puppet] Running Debian packages on top of Trusty
Hello, thanks for bringing up this topic, that's what I wanted to discuss on next puppet-openstack irc meeting. So, user case is following: users may want to install Debian packages on Ubuntu host or vice versa, the same problem can probably happen with CentOS, RHEL, Fedora; or users may use non-official package repositories with their own package (service) naming strategy and so on. Current situation in puppet modules is following that package and service names are (let's say) hardcoded in 'params' class (e.g. [0]). But in situation that I've described it won't work. Puppet will try to use Ubuntu names on Ubuntu host and it won't allow to install and work with Debian packages. I've researched puppet modules and found an interesting example which can help to solve this issue. It's implemented in puppetlabs mongodb module: they have 'globals' class [1] that allows to override most part of parameters from 'params' class [2]. So, I've decided to rework this soltuion and use it in OpenStack modules. As result I got draft patch for ceilometer module [3]. By default we use parameters from 'params' class, but every parameter can be now overridden using 'globals' class. OpenStack Puppet team, what do you think about this solution? Also, I'l bring up this topic on weekly puppet-openstack irc meeting. [0] - https://github.com/openstack/puppet-ceilometer/blob/master/manifests/params.pp [1] - https://github.com/puppetlabs/puppetlabs-mongodb/blob/master/manifests/globals.pp [2] - https://github.com/puppetlabs/puppetlabs-mongodb/blob/master/manifests/params.pp [3] - https://review.openstack.org/#/c/229918/ 2015-10-02 15:43 GMT+03:00 Ivan Udovichenko <iudoviche...@mirantis.com>: > Hello, > > On 10/02/2015 03:15 PM, Emilien Macchi wrote: > > Hey Thomas, > > > > On 10/02/2015 04:33 AM, Thomas Goirand wrote: > > [...] > >> We also may need, at some point, to add the type mosdebian and moscentos > >> to the list of supported package suite, as there still will be some > >> differences between the upstream Debian or CentOS packages. What is the > >> best way to add this variable values? > >> > >> Could you Puppet experts explain to me and my Mirantis colleagues again? > > > > So we partially discussed about that during our last weekly meeting [1] > > and it come out the best way to support both Debian & Ubuntu are Puppet > > conditionals, like we already have in place. > > > > [1] > > > http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-09-29-15.00.html > > It does not solve the original problem. Let's say you want to install > Debian packages on-top of Ubuntu, it will fail and you will have to use > workarounds, for example in the params.pp [1] you have specified. > > [1] > > https://github.com/openstack/puppet-nova/blob/master/manifests/params.pp#L100-L107 > > > > > See the example with puppet-nova |2] where we use $::operatingsystem > > fact [3] to detect if we're running Ubuntu or Debian. > > If we're running Ubuntu, we take reference from UCA packaging. If > > Debian, we take your work as reference. > > > > [2] > > > https://github.com/openstack/puppet-nova/blob/master/manifests/params.pp#L100-L107 > > [3] https://puppetlabs.com/facter > > > > What we need is some variable which can override the decision which > Operating System is used and thereby required packages will be > installed. At least for Debian, that is what we really need. > I'd be grateful if you look into it. Thank you. > > > > >> Sorry that I didn't take notes about it and couldn't explain, > >> Cheers, > >> > >> Thomas Goirand (zigo) > >> > >> P.S: Where may I find the best tutorial to get up-to-speed about puppet, > >> so that I know what I'm talking about next time? > >> > > > > I personally learnt (and am still learning) by using official > > documentation [4], that I suggest you to start with. > > > > [4] http://docs.puppetlabs.com/puppet/ > > > > Hope it helps, > > > > > > > > > __ > > 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 > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [puppet] monasca,murano,mistral governance
Emilien, puppet-murano module have a bunch of patches from Alexey Deryugin on review [0], which implements most of all Murano deployment stuff. Murano project was added to OpenStack namespace not so long ago, that's why I suggest to have murano-core rights on puppet-murano as they are till all these patches will be merged. Anyway, murano-core team doesn't merge any patches without OpenStack Puppet team approvals. [0] - https://review.openstack.org/#/q/status:open+project:openstack/puppet-murano+owner:%22Alexey+Deryugin+%253Caderyugin%2540mirantis.com%253E%22,n,z 2015-09-15 1:01 GMT+03:00 Matt Fischer <m...@mattfischer.com>: > Emilien, > > I've discussed this with some of the Monasca puppet guys here who are > doing most of the work. I think it probably makes sense to move to that > model now, especially since the pace of development has slowed > substantially. One blocker before to having it "big tent" was the lack of > test coverage, so as long as we know that's a work in progress... I'd also > like to get Brad Kiein's thoughts on this, but he's out of town this week. > I'll ask him to reply when he is back. > > > On Mon, Sep 14, 2015 at 3:44 PM, Emilien Macchi <emil...@redhat.com> > wrote: > >> Hi, >> >> As a reminder, Puppet modules that are part of OpenStack are documented >> here [1]. >> >> I can see puppet-murano & puppet-mistral Gerrit permissions different >> from other modules, because Mirantis helped to bootstrap the module a >> few months ago. >> >> I think [2] the modules should be consistent in governance and only >> Puppet OpenStack group should be able to merge patches for these modules. >> >> Same question for puppet-monasca: if Monasca team wants their module >> under the big tent, I think they'll have to change Gerrit permissions to >> only have Puppet OpenStack able to merge patches. >> >> [1] >> http://governance.openstack.org/reference/projects/puppet-openstack.html >> [2] https://review.openstack.org/223313 >> >> Any feedback is welcome, >> -- >> Emilien Macchi >> >> >> __ >> 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 > > -- Thanks, Ivan Berezovskiy MOS Puppet Team Lead at Mirantis <https://www.mirantis.com/> slack: iberezovskiy skype: bouhforever phone: + 7-960-343-42-46 __ 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] [diskimage-builder] CentOS support
Hi, I am working on 'centos' element for bulding CentOS cloud images. It is partially implements bug https://bugs.launchpad.net/diskimage-builder/+bug/1182723 . Please, review https://review.openstack.org/#/c/49335/ . Scripts for this element are written like as for Fedora and RHEL. This element uses CentOS 6.4 with cloud-init as baseline. I couldn't find free CentOS 6.4 with cloud-init, so I made it using cloud-init rpm package of last version and uploaded to our CDN. Thanks, Ivan. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [savanna] Fwd: Change in stackforge/savanna-extra[master]: Add diskimage-creating script, elements for mirrors
Hi,
1.We used mvn to create tar.gz and I'll add documentation for that.
2. The command is simple: parameter1='some_value1' ...
parameterN='some_valueN' disk-image-create element1 ... elementM -o
image_name.
Some files in ~/.cache/image-create/ are owned by root (for example, it is
file SHA256SUMS*). So, we need to use 'sudo' for cleaning this directory.
3. This script should not be run with itself. And the command
disk-image-create should not be run with itself too.
Thanks, Ivan.
2013/9/3 Matthew Farrellee m...@redhat.com
Long weekend here in the US, so I didn't get a chance to comment before
this was merged, so...
Re Oozie - How did you create the oozie-3.3.2.tar.gz?
Re sudo image-cache - That's not the case for me, the wget is run without
sudo. How are you running disk-image-create?
Re DIB_work - it's best practice to use /tmp for temporary work, and
mktemp. This script running concurrently with itself will result in unknown
output.
Best,
matt
Original Message
Subject: Change in stackforge/savanna-extra[**master]: Add
diskimage-creating script, elements for mirrors
Date: Thu, 29 Aug 2013 14:37:36 +
From: Ivan Berezovskiy (Code Review) rev...@openstack.org
Reply-To: iberezovs...@mirantis.com
CC: Sergey Lukjanov slukja...@mirantis.com,Dmitry Mescheryakov
dmescherya...@mirantis.com,Nadya Privalova
nprival...@mirantis.com,Matthew Farrellee m...@redhat.com
Ivan Berezovskiy has posted comments on this change.
Change subject: Add diskimage-creating script, elements for mirrors
..**..**..
Patch Set 6: (16 inline comments)
..**..
File diskimage-create/diskimage-**create.sh
Line 11: export OOZIE_DOWNLOAD_URL=http://**a8e0dce84b3f00ed7910-**
a5806ff0396addabb148d230fde09b**7b.r31.cf1.rackcdn.com/oozie-**
3.3.2.tar.gzhttp://a8e0dce84b3f00ed7910-a5806ff0396addabb148d230fde09b7b.r31.cf1.rackcdn.com/oozie-3.3.2.tar.gz
We don't use custom tarball. It is our own tarbal. Please, show me link,
if you know, where I can download oozie with all binary files.
Line 15: if [ $str = 'NAME=Ubuntu' ]; then
Package 'redhat-lsb' is not preinstalled in some Fedora images like cloud
image. So, we can't use this command.
In DIB you can see script 02-lsb ('https://github.com/**
openstack/diskimage-builder/**blob/master/elements/fedora/**
pre-install.d/02-lsbhttps://github.com/openstack/diskimage-builder/blob/master/elements/fedora/pre-install.d/02-lsb')
that install this package.
Line 21: fi
Done
Line 24: sudo rm -rf /home/$USER/.cache/image-**create/*
Image caching execute under 'sudo'. You can try to delete images without
sudo and you'll see 'premission denied'
Line 31: cd DIB_work
Why? This directory will be removed after creating images.
Line 41: export DIB_COMMIT_ID=`git show --format=%H | head -1`
https://github.com/stackforge/**savanna-extra/blob/master/**
elements/savanna-version/**install.d/01-savanna-versionhttps://github.com/stackforge/savanna-extra/blob/master/elements/savanna-version/install.d/01-savanna-version
Line 42: cd ../
Done
Line 48: export SAVANNA_ELEMENTS_COMMIT_ID=`**git show --format=%H | head
-1`
https://github.com/stackforge/**savanna-extra/blob/master/**
elements/savanna-version/**install.d/01-savanna-versionhttps://github.com/stackforge/savanna-extra/blob/master/elements/savanna-version/install.d/01-savanna-version
Line 49: cd ../
Done
Line 64: fi
We can't use 'lsb_release' as I said before.
..**..
File diskimage-create/README.rst
Line 7: 1. If you want to change build parameters, you should edit this
script at 'export' commands.
Done
Line 9: 2. If you want to use your local mirrors, you can specify urls for
Fedora and Ubuntu mirrors using parameters 'FEDORA_MIRROR' and
'UBUNTU_MIRROR' like this:
Done
Line 15: 3. If you want to add your element to this repository, you should
edit this script in your commit (you should export variables for your
element and add name of element to variables 'element_sequence').
Done
..**..
File elements/apt-mirror/root.d/0-**check
Line 2: if [ -z $UBUNTU_MIRROR ]; then
Done
..**..
File elements/yum-mirror/root.d/0-**check
Line 2: if [ -z $FEDORA_MIRROR ]; then
Done
..**..
File README.rst
Line 10: * Script for creating Fedora and Ubuntu cloud images with our
elements and default parameters. You should run command only:
Done
--
To view, visit
https://review.openstack.org/**43916https://review.openstack.org/43916
To unsubscribe, visit
https://review.openstack.org/**settingshttps://review.openstack.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I12632b5cee42b1dbfd79b7b7c3a7b
Re: [openstack-dev] [Savanna-all] [savanna-all] merging savanna-extra elements
Matt, install.d is good place to install packages (like java and hadoop) and editing its configuration files. First scripts for Fedora was in subdirectory install.d too, but during installation I got error related to proc-trigger (input/output errors in proc-trigger). So I decided to change subdirectory. Regarding 70,80,90-... vs 11,12,13... This number is position of script that runs in it subdirectory. All scripts of elements in the same directories are sorted by number. So the values of these numbers are not important, but all numbers should be unique within each subdirectories. -- Thanks, Ivan 2013/7/10 Matthew Farrellee m...@redhat.com Ivan, $ tree elements/hadoop/install.d elements/hadoop/install.d |-- 70-setup-java |-- 80-setup-hadoop `-- 90-setup-ssh 0 directories, 3 files $ tree elements/hadoop_fedora/post-**install.d elements/hadoop_fedora/post-**install.d |-- 11-setup-java |-- 12-setup-hadoop `-- 13-connection-setup 0 directories, 3 files I want to align these two directory structures and filenames. install.d vs post-install.d, which is preferred? 70,80,90-... vs 11,12,13-..., which is preferred? Best, matt -- Mailing list: https://launchpad.net/~**savanna-allhttps://launchpad.net/~savanna-all Post to : savanna-all@lists.launchpad.**netsavanna-...@lists.launchpad.net Unsubscribe : https://launchpad.net/~**savanna-allhttps://launchpad.net/~savanna-all More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
