OpenStack operator should be provided with an option to just provision nodes. We want to provide flexibility for sophisticated users, and I consider this as normal use case. So I disagree that we should treat provisioning as just developers feature.
For newbies / simplest clouds, we want to keep the easiest way of installation possible, i.e. just Deploy button. We can claim that we've succeeded with this once 6-year kid is able to deploy OpenStack with Fuel. On Fri, May 22, 2015 at 7:33 AM, Roman Prykhodchenko <[email protected]> wrote: > Hi folks! > > Recently I encountered an issue [1] that the Deploy Changes button in the > web ui is still active when a provisioning of single node is started using > the command line client. > The background for that issue is that the provisioning task does not seem > to update the cluster status correctly and Nailgun’s API returns it as NEW > even while some of the node are been provisioned. > > The reason for raising this thread in the mailing list is that > provisioning a node is a feature for developers and basically end-users > should not do that. What is the best solution for that: fix Nailgun to set > the correct status, or make this provisioning feature available only for > developers? > > 1. https://bugs.launchpad.net/fuel/7.0.x/+bug/1449086 > > > - romcheg > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Mike Scherbakov #mihgen
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
