fuel-dev team mailing list archive

[Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>]

Ok, sounds good.
As far as I know, QA ran a set of tests already.
Anastasia, can you share results? Also, how easily would it be to revert it
back?

>  extending of feature freeze up to the end of the week.
It is not an option. We need to have a sufficient time for QA, and we
already have a ton of bugs to fix.

Thanks,


On Mon, Apr 14, 2014 at 6:35 PM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>wrote:

> 1. All the security updates, newer 3.11 LTS kernel, newer openvswitch,
> support for latest hardware
> 2. No. But it should not affect basic openstack functionality.
> 3. Kernel/openvswitch will be just fine - at least tested by me yesterday.
> 4. I do not see any risks.
>
> So I ask only for extending of feature freeze up to the end of the week.
> AFAIK, QAing of 12.04.4 went succesfully for nova-network based
> installations. So the only thing we need is wait for Neutron tests.
>
>
> On Mon, Apr 14, 2014 at 4:46 PM, Mike Scherbakov <mscherbakov@xxxxxxxxxxxx
> > wrote:
>
>> Vladimir,
>> I'd like to know the following then:
>>
>>    1. What changes are gonna be introduced, what packages are being
>>    updated? What are the benefits from a user and internal maintenance
>>    perspective for having this version of Ubuntu? (I know I sound silly, and I
>>    obviously with on having newer Ubuntu, but it's late.... )
>>    2. Was it tested with Icehouse packages and manifests
>>    3. Will it affect anyhow networking stack, i.e. what about
>>    kernel/openvswitch ?
>>    4. Are there any risks not mentioned above?
>>
>> Overall it sounds pretty risky even if we want it so much. If all can be
>> QAed in a day and can easily be reverted in case of discovered regressions
>> in next couple of weeks, then it can be an exception...
>>
>>
>> On Mon, Apr 14, 2014 at 3:56 PM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>wrote:
>>
>>> Mike
>>>
>>> I would suggest that we extend merge deadline for Ubuntu 12.04.4 as it
>>> is really important to update to the latest distro version. According to
>>> the latest data from our QA team, we can easily test it and merge it until
>>> the 19th of April.
>>>
>>>
>>> On Fri, Apr 11, 2014 at 5:47 PM, Mike Scherbakov <
>>> mscherbakov@xxxxxxxxxxxx> wrote:
>>>
>>>> After internal discussion, we added Linux bonding in the list....
>>>> a) it's 90% done: https://review.openstack.org/85077
>>>> b) it doesn't affect other features, i.e. it can't block anything else
>>>> from being QAed
>>>>
>>>> Considering two facts above, and that it was actually long-waited
>>>> feature, I'm adding this in the list:
>>>> 10. https://blueprints.launchpad.net/fuel/+spec/linux-bonding - April,
>>>> 14th - last day to land the feature code re: linux bonds.
>>>>
>>>>
>>>>
>>>> On Fri, Apr 11, 2014 at 4:24 PM, Mike Scherbakov <
>>>> mscherbakov@xxxxxxxxxxxx> wrote:
>>>>
>>>>> Thanks Nadya,
>>>>> I think it's both then -
>>>>> https://blueprints.launchpad.net/fuel/+spec/ceilometer-fuel-integraition,
>>>>> which has a sub-bp
>>>>> https://blueprints.launchpad.net/fuel/+spec/mongodb-fuel-integration
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Apr 11, 2014 at 4:16 PM, Nadya Privalova <
>>>>> nprivalova@xxxxxxxxxxxx> wrote:
>>>>>
>>>>>> Mike,
>>>>>> MongoDB integration is not Ceilometer integration actually. Please
>>>>>> consider
>>>>>> https://blueprints.launchpad.net/fuel/+spec/ceilometer-fuel-integraition.
>>>>>> All Work items in this bp are up to date. I think that item 2 can be just
>>>>>> changed to ceilometer-fuel-integraition.
>>>>>>
>>>>>> Thanks,
>>>>>> Nadya
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 11, 2014 at 2:06 PM, Mike Scherbakov <
>>>>>> mscherbakov@xxxxxxxxxxxx> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> we are delayed with feature freeze which was planned for 9th of
>>>>>>> April. We still have a number of features to merge, which are "must" for
>>>>>>> 5.0. We also need to release before design summit starts which is 12th of
>>>>>>> May.
>>>>>>>
>>>>>>> To avoid a situation, when we have a number of things merged in one
>>>>>>> hour with breaking ISO, we propose to define different dates for feature
>>>>>>> freeze. So these dates are considered last day when we can land the code of
>>>>>>> a feature into master:
>>>>>>>
>>>>>>>    1. Upgrade to RabbitMQ v.3 -  April, 12th
>>>>>>>    2. Integration of MongoDB database into fuel<https://blueprints.launchpad.net/fuel/+spec/mongodb-fuel-integration> -
>>>>>>>    April, 15th
>>>>>>>    3. Support to deploy compute nodes using VMware hypervisor<https://blueprints.launchpad.net/fuel/+spec/fuel-vmware-hypervisor> -
>>>>>>>    April, 16th
>>>>>>>    4. Monitoring of Openstack services<https://blueprints.launchpad.net/fuel/+spec/monitoring-system> -
>>>>>>>    April, 14th
>>>>>>>    5. Patch (minor fixes) to OpenStack<https://blueprints.launchpad.net/fuel/+spec/patch-openstack> -
>>>>>>>    April, 14th
>>>>>>>    6. REST API should be freezed together with upgrades
>>>>>>>    implementation<https://blueprints.launchpad.net/fuel/+spec/nailgun-rest-api-freeze-v1> -
>>>>>>>    April, 14th
>>>>>>>    7. Support multiple networks per cluster<https://blueprints.launchpad.net/fuel/+spec/multiple-cluster-networks> -
>>>>>>>    April, 14th
>>>>>>>    8. Patch or upgrade Fuel<https://blueprints.launchpad.net/fuel/+spec/fuel-upgrade> -
>>>>>>>    April, 20th
>>>>>>>    9. Single Controller HA<https://blueprints.launchpad.net/fuel/+spec/single-controller-ha> -
>>>>>>>    April, 11th
>>>>>>>
>>>>>>> All other features which didn't get merged by 8pm UTC time today, 11
>>>>>>> of April, should be considered out of 5.0. Please don't merge features
>>>>>>> after this time, unless they are part of the list above.
>>>>>>>
>>>>>>> Please respond ASAP if you consider something which must become a
>>>>>>> part of the list above, but there is should be a very good reason for that.
>>>>>>> Keep in mind, that we also have a ton of bugs to solve...
>>>>>>>
>>>>>>> A few more dates to consider, because of the shift in feature freeze
>>>>>>> dates:
>>>>>>> April, 25 - soft code freeze
>>>>>>> April, 29 - hard code freeze
>>>>>>> ~ May 10th - release date, after acceptance testing phase
>>>>>>>
>>>>>>> In a first priority we keep working on bringing up Icehouse support.
>>>>>>> Expectation is that it appears more or less working in master no later than
>>>>>>> by US morning on 14th.
>>>>>>>
>>>>>>> Core reviewers, with merge rights, please keep rules enforced. Once
>>>>>>> we agree on the strategy, please don't step aside unless it's discussed
>>>>>>> here and we are all in agreement.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> --
>>>>>>> Mike Scherbakov
>>>>>>> #mihgen
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Mike Scherbakov
>>>> #mihgen
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>
>
>
> --
> 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
>



-- 
Mike Scherbakov
#mihgen