Open Stack

Evgeniy,

That's also a good point. Due to all these issues and need to significantly
change Nailgun for this feature we decided to move it out of 8.0 and come
back to it in the next release so that we can design and implement
everything properly.

2015-11-23 16:49 GMT+07:00 Evgeniy L <eli at mirantis.com>:

> Hi,
>
> I have several comments, just to make sure, that we are on the same page
> here.
> Current API calls for provisioning/deployment are used by developers and
> fuel hackers,
> and by design there was removed all validation. So shouldn't there be some
> more
> user friendly API calls which have validation? For example we don't run
> any pre
> deployment checks and network validation, you can even ask to deploy
> offline nodes.
> As result novice user can easily break her/his cluster.
>
> Thanks,
>
> On Fri, Nov 13, 2015 at 11:46 AM, Julia Aranovich <jkirnosova at mirantis.com
> > wrote:
>
>> Hi fuelers,
>>
>> Currently Fuel UI team is working on blueprint [1] to give Fuel UI user
>> an ability to launch provisioning of environment nodes separately from
>> deployment (without choosing particular nodes for now).
>>
>> In the process we were faced with the following issues. Some of them
>> block the blueprint:
>>
>>    - deployment constantly failed on environment with pre-provisioned
>>    nodes [2]
>>    - node pending_addition flag is reset to False for provisioned nodes
>>    [3]. This causes a lot of UX problems: provisioned node roles, disks,
>>    interfaces can not be reconfigured, node can not be deleted from
>>    environment, just can be marked as pending deletion (that requires
>>    environment deployment)
>>    - completed provisioning task has Null message. So, there is no to
>>    show the user after provisioning finished [4]
>>    - no notification comes on UI after provisioned finished [5]
>>    - fake provisioning task is also should be fixed: environment nodes
>>    stay in 'provisioning' status after provisioning finished [6]. This breaks
>>    fake Fuel UI workflow and brings difficulties in Fuel UI development.
>>
>> Could you please consider/fix the tickets and help to unblock the
>> blueprint targeted for the current release.
>>
>> Also, you can check how provisioning works in Fuel UI on #547 custom 8.0
>> ISO.
>>
>> Thank you!
>> Julia
>>
>> [1]
>> https://blueprints.launchpad.net/fuel/+spec/support-separate-provisioning-and-deployment-in-ui
>> [2] https://bugs.launchpad.net/fuel/+bug/1515903
>> [3] https://bugs.launchpad.net/fuel/+bug/1515898
>> [4] https://bugs.launchpad.net/fuel/+bug/1515895
>> [5] https://bugs.launchpad.net/fuel/+bug/1515891
>> [6] https://bugs.launchpad.net/fuel/+bug/1515893
>>
>>
>> __________________________________________________________________________
>> 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
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151123/fa6ff76d/attachment.html>