fuel-dev team mailing list archive

[Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>]

Ok. I changed priority to High for 5.1.


On Tue, Apr 22, 2014 at 1:15 PM, Lukasz Oles <loles@xxxxxxxxxxxx> wrote:

> I'm currently not involved in SL work. This change was made for Fuel 4.0
> and they currently try to use vanilla Fuel 4.1 so they do not have this
> change in their Fuel version.
>
> I would postpone it to 5.1, there may be some race in Puppet and we can
> introduce hard to find and reproduce bugs just before summit.
>
>
> On Mon, Apr 21, 2014 at 9:41 AM, Mike Scherbakov <mscherbakov@xxxxxxxxxxxx
> > wrote:
>
>> I've created a bug for 5.1 on this:
>> https://bugs.launchpad.net/fuel/+bug/1310494.
>> If you consider this is non-risky item for 5.0, and if it was tested many
>> times on SoftLayer, I'm for fixing it in 5.0.
>>
>>
>> On Thu, Mar 27, 2014 at 2:23 AM, Lukasz Oles <loles@xxxxxxxxxxxx> wrote:
>>
>>> We have done it for MOE project
>>> https://github.com/loles/fuel-web/commit/88391c44c192de06c14e4c26a6f195a5750a6b90in SoftLayer  and as far as I know it works
>>>
>>>
>>> On Tue, Mar 25, 2014 at 5:30 PM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>wrote:
>>>
>>>> Ok, guys, let's start a blueprint for this feature. There should be
>>>> some information on the current state of the art. AFAIK there is no testing
>>>> result on parallel controller deployment.
>>>>
>>>> Andrew, did you try to implement this feature? Did you test parallel
>>>> deployment of the controllers? Did it fail or did it succeed?
>>>>
>>>> As for me speaking for parallel deployment reminds us of our pluggable
>>>> architecture that should allow us to run some roles in parallels. I am not
>>>> quite sure that we have an opportunity to spend resources on such tasks
>>>> right now.
>>>>
>>>>
>>>> On Wed, Mar 12, 2014 at 2:42 AM, Sergey Vasilenko <
>>>> svasilenko@xxxxxxxxxxxx> wrote:
>>>>
>>>>> For decrease count of possible HA-issues in the parallel deployment
>>>>> mode we should:
>>>>> * create any Pacemaker resources only at primary controller deployment
>>>>> process
>>>>> * move Galera deployment to the its ows stage (for prevent parallel
>>>>> galera deployment)
>>>>> * OR rewrite galera ocf script, for syncing slave nodes with master as
>>>>> node-by-node (not all together)
>>>>>
>>>>>
>>>>> /sv
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Yours Faithfully,
>>>> Vladimir Kuklin,
>>>> Fuel Library Tech Lead,
>>>>
>>>> Mirantis, Inc.
>>>> +7 (495) 640-49-04
>>>> +7 (926) 702-39-68
>>>> Skype kuklinvv
>>>> 45bk3, Vorontsovskaya Str.
>>>> Moscow, Russia,
>>>> www.mirantis.com <http://www.mirantis.ru/>
>>>> www.mirantis.ru
>>>> vkuklin@xxxxxxxxxxxx
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Łukasz Oleś
>>>
>>> --
>>> Mailing list: https://launchpad.net/~fuel-dev
>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>
>
>
> --
> Łukasz Oleś
>



-- 
Mike Scherbakov
#mihgen