Open Stack

​Guys, you are awesome. Thank you all very much.​

Vladimir Kozhukalov

On Mon, Mar 28, 2016 at 11:50 PM, Alexey Shtokolov <ashtokolov at mirantis.com>
wrote:

> Fuelers!
>
> I'm glad to announce that all patches [0] were merged!
>
> Many thanks to all of you who help us to make Fuel more flexible and
> unlimited.
>
> Special thanks to our code and design reviewers: Igor Kalnitsky, Sergii
> Golovatiuk, Vitaly Kramskikh.
>
> And especially to the Team: Bulat Gaifullin, Ilya Kutukov, Vladimir
> Sharshov, Julia Aranovich, Stanislaw Bogatkin, Evgeniy L and Vladimir Kuklin
> My sincerest thanks and appreciation for your great efforts, sleepless
> nights and sense of purpose!
>
> WBR, Alexey Shtokolov
>
> [0] - https://goo.gl/kSwej5
>
> 2016-03-25 21:48 GMT+03:00 Vladimir Kozhukalov <vkozhukalov at mirantis.com>:
>
>> Granted. New deadline is 21:00 UTC 03/28/2016.
>>
>> Vladimir Kozhukalov
>>
>> On Fri, Mar 25, 2016 at 8:17 PM, Alexey Shtokolov <
>> ashtokolov at mirantis.com> wrote:
>>
>>> Fuelers!
>>>
>>>
>>> We are very close to landing our feature "Unlock Settings Tab". But we
>>> still have a set of reviews [0] to be merged due to several reasons (incl.
>>> the migration to python27-db gates on OpenStack Infra). I would like to
>>> request extra time till Monday to land them.
>>>
>>>
>>> [0] - https://goo.gl/kSwej5
>>>
>>> 2016-03-14 11:00 GMT+03:00 Dmitry Borodaenko <dborodaenko at mirantis.com>:
>>>
>>>> Thanks for working this out! Confirming that task history remains
>>>> included in the scope of this FFE until the merge deadline, March 24.
>>>>
>>>> On Fri, Mar 11, 2016 at 11:48:51PM +0200, Igor Kalnitsky wrote:
>>>> > Hey Dmitry,
>>>> >
>>>> > I confirm that we agreed on feature design, and you can proceed with
>>>> > granting exception.
>>>> >
>>>> > ,- Igor
>>>> >
>>>> > On Fri, Mar 11, 2016 at 8:27 PM, Alexey Shtokolov
>>>> > <ashtokolov at mirantis.com> wrote:
>>>> > > Hi Dmitry,
>>>> > >
>>>> > > We've reached the design consensus with Igor today. Could you
>>>> please remove
>>>> > > the conditional status of the FFE request?
>>>> > > As agreed: the merge deadline is March 24.
>>>> > >
>>>> > > --
>>>> > > WBR, Alexey Shtokolov
>>>> > >
>>>> > > 2016-03-11 2:27 GMT+03:00 Dmitry Borodaenko <
>>>> dborodaenko at mirantis.com>:
>>>> > >>
>>>> > >> Granted. Design consensus deadline for the task history part of
>>>> this
>>>> > >> feature is extended to March 11. This does not change the merge
>>>> deadline
>>>> > >> for other parts of this feature, which is still March 24.
>>>> > >>
>>>> > >> --
>>>> > >> Dmitry Borodaenko
>>>> > >>
>>>> > >>
>>>> > >> On Fri, Mar 11, 2016 at 01:02:52AM +0300, Alexey Shtokolov wrote:
>>>> > >> > Dmitry,
>>>> > >> >
>>>> > >> > We are really close to have the consensus, but we need one more
>>>> meeting
>>>> > >> > with Fuel-Python Component Lead Igor Kalnitsky to make the final
>>>> > >> > decision.
>>>> > >> > All patches [0] are on review. The meeting is scheduled for
>>>> tomorrow
>>>> > >> > (03/11
>>>> > >> > 1:30pm CET).
>>>> > >> > Could you please grant us one more day for it?
>>>> > >> >
>>>> > >> > [0] -
>>>> > >> >
>>>> https://review.openstack.org/#/q/topic:bp/store-deployment-tasks-history
>>>> > >> >
>>>> > >> > --
>>>> > >> > WBR, Alexey Shtokolov
>>>> > >> >
>>>> > >> > 2016-03-04 3:13 GMT+03:00 Dmitry Borodaenko <
>>>> dborodaenko at mirantis.com>:
>>>> > >> >
>>>> > >> > > Granted, merge deadline March 24, task history part of the
>>>> feature is
>>>> > >> > > to
>>>> > >> > > be excluded from this exception grant unless a consensus is
>>>> reached by
>>>> > >> > > March 10.
>>>> > >> > >
>>>> > >> > > Relevant part of the meeting log starts at:
>>>> > >> > >
>>>> > >> > >
>>>> > >> > >
>>>> http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.log.html#l-198
>>>> > >> > >
>>>> > >> > > --
>>>> > >> > > Dmitry Borodaenko
>>>> > >> > >
>>>> > >> > >
>>>> > >> > > On Wed, Mar 02, 2016 at 06:00:40PM +0700, Vitaly Kramskikh
>>>> wrote:
>>>> > >> > > > Oh, so there is a spec. I was worried that this patch has
>>>> > >> > > > "WIP-no-bprint-assigned-yet" string in the commit message,
>>>> so I
>>>> > >> > > > thought
>>>> > >> > > > there is no spec for it. So the commit message should be
>>>> updated to
>>>> > >> > > > avoid
>>>> > >> > > > such confusion.
>>>> > >> > > >
>>>> > >> > > > It's really good I've seen this spec. There are plans to
>>>> overhaul UI
>>>> > >> > > > data
>>>> > >> > > > format description which we use for cluster and node
>>>> settings to
>>>> > >> > > > solve
>>>> > >> > > some
>>>> > >> > > > issues and implement long-awaited features like nested
>>>> structures,
>>>> > >> > > > so we
>>>> > >> > > > might also want to deprecate our expression language and
>>>> also switch
>>>> > >> > > > to
>>>> > >> > > > YAQL (and thus port YAQL to JS).
>>>> > >> > > >
>>>> > >> > > > 2016-03-02 17:17 GMT+07:00 Vladimir Kuklin <
>>>> vkuklin at mirantis.com>:
>>>> > >> > > >
>>>> > >> > > > > Vitaly
>>>> > >> > > > >
>>>> > >> > > > > Thanks for bringing this up. Actually the spec has been on
>>>> review
>>>> > >> > > > > for
>>>> > >> > > > > almost 2 weeks: https://review.openstack.org/#/c/282695/.
>>>> > >> > > > > Essentially,
>>>> > >> > > > > this is not introducing new DSL but replacing the existing
>>>> one
>>>> > >> > > > > with
>>>> > >> > > more
>>>> > >> > > > > powerful extendable language which is being actively
>>>> developed
>>>> > >> > > > > within
>>>> > >> > > > > OpenStack and is already a part of other projects (Murano,
>>>> > >> > > > > Mistral),
>>>> > >> > > which
>>>> > >> > > > > has much more contributors, can return not only boolean
>>>> but any
>>>> > >> > > arbitrary
>>>> > >> > > > > collections. So it means that we want to deprecate current
>>>> > >> > > > > Expression
>>>> > >> > > > > language that you wrote and replace it with YAQL due to
>>>> those
>>>> > >> > > > > reasons.
>>>> > >> > > You
>>>> > >> > > > > are not going to extend this Expression-based language in
>>>> 3 weeks
>>>> > >> > > > > up to
>>>> > >> > > > > level of support of extensions, method overloading, return
>>>> of
>>>> > >> > > > > arbitrary
>>>> > >> > > > > collections (e.g. we also want to calculate cross-depends
>>>> and
>>>> > >> > > > > requires
>>>> > >> > > > > fields on the fly which require for it to return list of
>>>> dicts)
>>>> > >> > > > > and
>>>> > >> > > support
>>>> > >> > > > > of this stuff on your own, are you?
>>>> > >> > > > >
>>>> > >> > > > > On Wed, Mar 2, 2016 at 10:09 AM, Vitaly Kramskikh <
>>>> > >> > > vkramskikh at mirantis.com
>>>> > >> > > > > > wrote:
>>>> > >> > > > >
>>>> > >> > > > >> I think it's not a part of best practices to introduce
>>>> changes
>>>> > >> > > > >> like
>>>> > >> > > > >> https://review.openstack.org/#/c/279714/ (adding yet
>>>> another DSL
>>>> > >> > > > >> to
>>>> > >> > > the
>>>> > >> > > > >> project) without a blueprint and review and discussion of
>>>> the
>>>> > >> > > > >> spec.
>>>> > >> > > > >>
>>>> > >> > > > >> 2016-03-02 2:19 GMT+07:00 Alexey Shtokolov
>>>> > >> > > > >> <ashtokolov at mirantis.com>:
>>>> > >> > > > >>
>>>> > >> > > > >>> Fuelers,
>>>> > >> > > > >>>
>>>> > >> > > > >>> I would like to request a feature freeze exception for
>>>> "Unlock
>>>> > >> > > settings
>>>> > >> > > > >>> tab" feature [0]
>>>> > >> > > > >>>
>>>> > >> > > > >>> This feature being combined with Task-based deployment
>>>> [1] and
>>>> > >> > > > >>> LCM-readiness for Fuel deployment tasks [2] unlocks
>>>> Basic LCM in
>>>> > >> > > Fuel. We
>>>> > >> > > > >>> conducted a thorough redesign of this feature and
>>>> splitted it
>>>> > >> > > > >>> into
>>>> > >> > > several
>>>> > >> > > > >>> granular changes [3]-[6] to allow users to change
>>>> settings on
>>>> > >> > > deployed,
>>>> > >> > > > >>> partially deployed, stopped or erred clusters and
>>>> further run
>>>> > >> > > redeployment
>>>> > >> > > > >>> using a particular graph (custom or calculated based on
>>>> expected
>>>> > >> > > changes
>>>> > >> > > > >>> stored in DB) and with new parameters.
>>>> > >> > > > >>>
>>>> > >> > > > >>> We need 3 weeks after FF to finish this feature.
>>>> > >> > > > >>> Risk of not delivering it after 3 weeks is low.
>>>> > >> > > > >>>
>>>> > >> > > > >>> Patches on review or in progress:
>>>> > >> > > > >>> <https://review.openstack.org/#/c/284139/>
>>>> > >> > > > >>> https://review.openstack.org/#/c/284139/
>>>> > >> > > > >>> https://review.openstack.org/#/c/279714/
>>>> > >> > > > >>> https://review.openstack.org/#/c/286754/
>>>> > >> > > > >>> https://review.openstack.org/#/c/286783/
>>>> > >> > > > >>>
>>>> > >> > > > >>> Specs:
>>>> > >> > > > >>> https://review.openstack.org/#/c/286713/
>>>> > >> > > > >>> https://review.openstack.org/#/c/284797/
>>>> > >> > > > >>> https://review.openstack.org/#/c/282695/
>>>> > >> > > > >>> https://review.openstack.org/#/c/284250/
>>>> > >> > > > >>>
>>>> > >> > > > >>>
>>>> > >> > > > >>> [0]
>>>> > >> > > > >>>
>>>> https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab
>>>> > >> > > > >>>
>>>> > >> > > > >>> <
>>>> https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab>[1]
>>>> > >> > > > >>>
>>>> > >> > >
>>>> > >> > >
>>>> https://blueprints.launchpad.net/fuel/+spec/enable-task-based-deployment
>>>> > >> > > > >>> [2]
>>>> > >> > > > >>>
>>>> > >> > >
>>>> > >> > >
>>>> https://blueprints.launchpad.net/fuel/+spec/granular-task-lcm-readiness
>>>> > >> > > > >>> [3]
>>>> > >> > > > >>>
>>>> > >> > >
>>>> > >> > >
>>>> https://blueprints.launchpad.net/fuel/+spec/computable-task-fields-yaql
>>>> > >> > > > >>> [4]
>>>> > >> > > > >>>
>>>> > >> > >
>>>> > >> > >
>>>> https://blueprints.launchpad.net/fuel/+spec/store-deployment-tasks-history
>>>> > >> > > > >>> [5]
>>>> > >> > >
>>>> https://blueprints.launchpad.net/fuel/+spec/custom-graph-execution
>>>> > >> > > > >>> [6]
>>>> > >> > > > >>>
>>>> > >> > >
>>>> > >> > >
>>>> https://blueprints.launchpad.net/fuel/+spec/save-deployment-info-in-database
>>>> > >> > > > >>>
>>>> > >> > > > >>> --
>>>> > >> > > > >>> ---
>>>> > >> > > > >>> WBR, Alexey Shtokolov
>>>> > >> > > > >>>
>>>> > >> > > > >>>
>>>> > >> > > > >>>
>>>> > >> > >
>>>> > >> > >
>>>> __________________________________________________________________________
>>>> > >> > > > >>> OpenStack Development Mailing List (not for usage
>>>> questions)
>>>> > >> > > > >>> Unsubscribe:
>>>> > >> > > > >>>
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> > >> > > > >>>
>>>> > >> > > > >>>
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>> > >> > > > >>>
>>>> > >> > > > >>>
>>>> > >> > > > >>
>>>> > >> > > > >>
>>>> > >> > > > >> --
>>>> > >> > > > >> Vitaly Kramskikh,
>>>> > >> > > > >> Fuel UI Tech Lead,
>>>> > >> > > > >> Mirantis, Inc.
>>>> > >> > > > >>
>>>> > >> > > > >>
>>>> > >> > >
>>>> > >> > >
>>>> __________________________________________________________________________
>>>> > >> > > > >> OpenStack Development Mailing List (not for usage
>>>> questions)
>>>> > >> > > > >> Unsubscribe:
>>>> > >> > > > >>
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> > >> > > > >>
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>> > >> > > > >>
>>>> > >> > > > >>
>>>> > >> > > > >
>>>> > >> > > > >
>>>> > >> > > > > --
>>>> > >> > > > > 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
>>>> > >> > > > > vkuklin at mirantis.com
>>>> > >> > > > >
>>>> > >> > > > >
>>>> > >> > >
>>>> > >> > >
>>>> __________________________________________________________________________
>>>> > >> > > > > OpenStack Development Mailing List (not for usage
>>>> questions)
>>>> > >> > > > > Unsubscribe:
>>>> > >> > > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> > >> > > > >
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>> > >> > > > >
>>>> > >> > > > >
>>>> > >> > > >
>>>> > >> > > >
>>>> > >> > > > --
>>>> > >> > > > Vitaly Kramskikh,
>>>> > >> > > > Fuel UI Tech Lead,
>>>> > >> > > > Mirantis, Inc.
>>>> > >> > >
>>>> > >> > > >
>>>> > >> > >
>>>> > >> > >
>>>> __________________________________________________________________________
>>>> > >> > > > OpenStack Development Mailing List (not for usage questions)
>>>> > >> > > > Unsubscribe:
>>>> > >> > > OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
>>>> > >> > >
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>> > >> > >
>>>> > >> >
>>>> > >> >
>>>> > >> >
>>>> > >> > --
>>>> > >> > ---
>>>> > >> > WBR, Alexey Shtokolov
>>>> > >>
>>>> > >> >
>>>> > >> >
>>>> __________________________________________________________________________
>>>> > >> > OpenStack Development Mailing List (not for usage questions)
>>>> > >> > Unsubscribe:
>>>> > >> > OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
>>>> > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>> > >
>>>> > >
>>>> > >
>>>> > >
>>>> > > --
>>>> > > ---
>>>> > > WBR, Alexey Shtokolov
>>>> > >
>>>> > >
>>>> __________________________________________________________________________
>>>> > > OpenStack Development Mailing List (not for usage questions)
>>>> > > Unsubscribe:
>>>> OpenStack-dev-request at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>
>>>
>>>
>>> --
>>> ---
>>> WBR, Alexey Shtokolov
>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> ---
> WBR, Alexey Shtokolov
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160329/349745ac/attachment.html>