[openstack-dev] [Fuel] [UI] Deploy Changes dialog redesign

Evgeniy L eli at mirantis.com
Mon Jan 26 17:11:19 UTC 2015


To be more specific, +1 for removing this information from UI, not from
backend.

On Mon, Jan 26, 2015 at 7:46 PM, Evgeniy L <eli at mirantis.com> wrote:

> Hi,
>
> I agree that this information is useless, but it's not really clear what
> you are going
> to show instead, will you completely remove the information about nodes
> for deployment?
> I think the list of nodes for deployment (without detailed list of
> changes) can be useful
> for the user.
>
> Thanks,
>
> On Mon, Jan 26, 2015 at 7:23 PM, Vitaly Kramskikh <vkramskikh at mirantis.com
> > wrote:
>
>> +1 for removing "changes" attribute. It's useless now. If there are no
>> plans to add something else there, let's remove it.
>>
>> 2015-01-26 11:39 GMT+03:00 Julia Aranovich <jkirnosova at mirantis.com>:
>>
>>> Hi All,
>>>
>>> Since we changed Deploy Changes pop-up and added processing of role
>>> limits and restrictions <https://review.openstack.org/#/c/126930/> I
>>> would like to raise a question of it's subsequent refactoring.
>>>
>>> In particular, I mean 'changes' attribute of cluster model. It's
>>> displayed in Deploy Changes dialog in the following format
>>> <http://s2.postimg.org/ak9inonhl/deploy_changes_dialog.png>:
>>>
>>>    - Changed disks configuration on the following nodes:
>>>    - <node_name_list>
>>>    - Changed interfaces configuration on the following nodes:
>>>       - <node_name_list>
>>>    - Changed network settings
>>>    - Changed OpenStack settings
>>>
>>> This list looks absolutely useless.
>>>
>>> It doesn't make any sense to display lists of new, not deployed nodes
>>> with changed disks/interfaces. It's obvious I think that new nodes
>>> attributes await deployment. At the same time user isn't able to change
>>> disks/interfaces on deployed nodes (at least in UI). So, such node name
>>> lists are definitely redundant.
>>> Networks and settings are also locked after deployment finished.
>>>
>>>
>>> I tend to get rid of cluster model 'changes' attribute at all.
>>>
>>> It is important for me to know your opinion, to make a final decision.
>>> Please feel free and share your ideas and concerns if any.
>>>
>>>
>>> Regards,
>>> Julia
>>>
>>> --
>>> Kind Regards,
>>> Julia Aranovich,
>>> Software Engineer,
>>> Mirantis, Inc
>>> +7 (905) 388-82-61 (cell)
>>> Skype: juliakirnosova
>>> www.mirantis.ru
>>> jaranovich at mirantis.com <jkirnosova 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150126/de5df267/attachment.html>


More information about the OpenStack-dev mailing list