Re: [openstack-dev] [Fuel] [Fuel UI] Support of separate provisioning is blocked by backend issues

2015-11-23 Thread Evgeniy L
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?

Re: [openstack-dev] [Fuel] [Fuel UI] Support of separate provisioning is blocked by backend issues

2015-11-23 Thread Vitaly Kramskikh
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

Re: [openstack-dev] [Fuel] [Fuel UI] Support of separate provisioning is blocked by backend issues

2015-11-16 Thread Igor Kalnitsky
Hey Julia, Thank you for feedback. I took a look over the bug and here's my thoughts: * [1] Looks like Invalid to me. I'm not sure, but it looks like you VMs just wrongly configures. It's a pretty common mistake for VBox scripts. Did you use them? * [2] Partially Invalid. I left my comments, so

[openstack-dev] [Fuel] [Fuel UI] Support of separate provisioning is blocked by backend issues

2015-11-13 Thread Julia Aranovich
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