I’m planning on putting up a patch for this today. My proposal is to add a
setting that disables it by default, then add a big warning side on the setting
documentation and release notes. Anyone who then explicitly enables it will see
the warning. Beyond that, we can deprecate it this cycle, but
On 08/03/2017 04:21 AM, Sean Dague wrote:
On 08/03/2017 06:13 AM, Zhenyu Zheng wrote:
I was thinking, the current "edit" in Horizon is delete-and-create, and
it is there maybe just because
flavor has many fields, user may want to have a new flavor but just
modify one of the old flavor, so
they d
On 08/03/2017 06:13 AM, Zhenyu Zheng wrote:
> I was thinking, the current "edit" in Horizon is delete-and-create, and
> it is there maybe just because
> flavor has many fields, user may want to have a new flavor but just
> modify one of the old flavor, so
> they don't want to manually copy all othe
I was thinking, the current "edit" in Horizon is delete-and-create, and it
is there maybe just because
flavor has many fields, user may want to have a new flavor but just modify
one of the old flavor, so
they don't want to manually copy all other fields. And it is the automatic
delete action that c
On 08/02/2017 10:12 PM, Zhenyu Zheng wrote:
> Hi All,
>
> Horizon provided the feature to allow user edit existing flavors, no
> matter it is currently used by any instances or not. While Nova doesn't
> provide this kind of ability, Horizon achieved this by deleting the old
> flavor first and crea
On Thu, Aug 3, 2017 at 11:12 AM, Zhenyu Zheng
wrote:
> Hi All,
>
> Horizon provided the feature to allow user edit existing flavors, no
> matter it is currently used by any instances or not. While Nova doesn't
> provide this kind of ability, Horizon achieved this by deleting the old
> flavor firs
