Open Stack

On 4/6/2016 8:06 AM, Qiming Teng wrote:
> Thanks for the explanation, Sean. I wasn't subscribing to the operators
> mailinglist so wasn't aware of the notice. With that, I'm still
> surprised that there was no response to that email.
>
> Anyway, if people believe the benefits overweighs the impacts caused,
> just do it.
>
> The only thing I can think of is about tagging a email with some
> eye-catching tags, e.g. [!!!] [Disruptive!] [Important!] ...
> It is so easy to have such big change go unnoticed.
>
> Regards,
>    Qiming
>
> On Wed, Apr 06, 2016 at 06:47:12AM -0400, Sean Dague wrote:
>> On 04/06/2016 04:19 AM, Sylvain Bauza wrote:
>>>
>>>
>>> Le 06/04/2016 06:44, Qiming Teng a écrit :
>>>> Not an expert of Nova but I am really shocked by such a change. Because
>>>> I'm not a Nova expert, I don't have a say on the *huge* efforts in
>>>> maintaining some builtin/default flavors. As a user I don't care where
>>>> the data have been stored, but I do care that they are gone. They are
>>>> gone because they **WILL** be supported by devstack. They are gone with
>>>> the workflow +1'ed **BEFORE** the devstack patch gets merged (many
>>>> thanks to the depends-on tag). They are gone in hope that all deployment
>>>> tools will know this when they fail, or fortunately they read this email,
>>>> or they were reviewing nova patches.
>>>>
>>>> It would be a little nicer to initiate a discussion on the mailinglist
>>>> before such a change is introduced.
>>>
>>>
>>> It was communicated accordingly to operators with no strong arguments :
>>> http://lists.openstack.org/pipermail/openstack-operators/2016-March/010045.html
>>
>> Not only with no strong arguments, but with a general - "yes please,
>> that simplifies our life".
>>
>>> You can also see that https://review.openstack.org/#/c/300127/ is having
>>> three items :
>>>   - a DocImpact tag creating a Launchpad bug for documentation about that
>>>   - a reno file meaning that our release notes will provide also some
>>> comments about that
>>>   - a Depends-On tag (like you said) on a devstack change meaning that
>>> people using devstack won't see a modified behavior.
>>>
>>> Not sure what you need more.
>>
>> The default flavors were originally hardcoded in Nova (in the initial
>> commit) -
>> https://github.com/openstack/nova/commit/bf6e6e718cdc7488e2da87b21e258ccc065fe499#diff-5ca8c06795ef481818ea1710fce91800R64
>>   and moved into the db 5 years ago to be a copy of the EC2 flavors at
>> the time -
>> https://github.com/openstack/nova/commit/563a77fd4aa80da9bddac5cf7f8f27ed2dedb39d.
>> Those flavors were meant to be examples, not the final story.
>>
>> All the public clouds delete these and do their own thing, as do I
>> expect many of the products. Any assumption that software or users have
>> that these will exist is a bad assumption.
>>
>> It is a big change, which is why it's being communicated on Mailing
>> Lists in addition to in the release notes so that people have time to
>> make any of their tooling not assume these flavors by name will be
>> there, or to inject them yourself if you are sure you need them (as was
>> done in the devstack case).
>>
>> 	-Sean
>>
>> --
>> Sean Dague
>> http://dague.net
>
>
> __________________________________________________________________________
> 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
>

There were several replies in the operators list thread and as Sean said 
they were generally favorable about this because they delete the default 
flavors anyway.

-- 

Thanks,

Matt Riedemann