Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

2016-09-08 Thread Georgy Kibardin
+1 On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky wrote: > Hey Fuelers, > > I'd like to nominate Ilya for joining fuel-plugins-core group. He's a > top contributor by both reviews [1] and commits [2] over the past > release cycle. Fuel cores, please share your votes. > > - Igor > > [1] http://s

[openstack-dev] [fuel] mcollective configuration on slaves

2016-08-11 Thread Georgy Kibardin
Guys, Currently, at the time of the first boot Mcollective on slaves is configured by Cloud-init (host, port etc.) and by Nailgun agent when node identity is written. This happens in any order and already caused several problem which were fixed in bounds of https://bugs.launchpad.net/fuel/+bug/145

Re: [openstack-dev] [Fuel] It is impossible to queue UpdateDnsmasqTask

2016-07-07 Thread Georgy Kibardin
incorrect list of admin networks by the end of environment deletion. So the option 4 just doesn't work. On Wed, Jul 6, 2016 at 11:41 AM, Georgy Kibardin wrote: > Bulat is suggesting to move with 4. He suggest to merge all actions of > UpdateDnsmasqTask into one puppet task. There are th

Re: [openstack-dev] [Fuel] It is impossible to queue UpdateDnsmasqTask

2016-07-06 Thread Georgy Kibardin
passing any additional data to "puppet apply". Cobbler sync seems to be a reasonable part of updating dhcp ranges config. Best, Georgy On Thu, Jun 16, 2016 at 7:25 PM, Georgy Kibardin wrote: > Hi All, > > Currently we can only run one instance of subj. at time. An attempt to run

Re: [openstack-dev] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

2016-06-28 Thread Georgy Kibardin
+1 On Tue, Jun 28, 2016 at 1:12 PM, Kyrylo Galanov wrote: > +1 > > On Tue, Jun 28, 2016 at 1:16 AM, Matthew Mosesohn > wrote: > >> +1. Maksim is an excellent reviewer. >> >> On Mon, Jun 27, 2016 at 6:06 PM, Alex Schultz >> wrote: >> > +1 >> > >> > On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrel

[openstack-dev] [Fuel] It is impossible to queue UpdateDnsmasqTask

2016-06-16 Thread Georgy Kibardin
Hi All, Currently we can only run one instance of subj. at time. An attempt to run second one causes an exception. This behaviour at least may cause a cluster to stuck forever in "removing" state (reproduces here https://bugs.launchpad.net/fuel/+bug/1544493) or just produce incomprehensible "task