+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.
>
> -
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
to 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 <gkibar...@mirantis.com>
wrote:
> Bulat is suggesting to move with 4. He suggest to merge all actions of
> UpdateDnsmasqTask into one
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 <gkibar...@mirantis.com>
wrote:
> Hi All,
>
> Currently we can only run one instance of
+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
>>
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