[openstack-dev] [Ironic] ENROLL state and changing node driver

Devananda van der Veen devananda.vdv at gmail.com
Thu Jun 4 16:18:43 UTC 2015

On Jun 4, 2015 5:53 AM, "Dmitry Tantsur" <dtantsur at redhat.com> wrote:
> Hi!
> While working on the enroll spec [1], I got a thinking: within the new
state machine, when should we allow to change a node driver?
> My initial idea was to only allow driver change in ENROLL. Which sounds
good to me, but then it will be impossible to change a driver after moving
forward: we don't plan on having a way back to ENROLL from MANAGEABLE.
> What do you folks think we should do:
> 1. Leave driver field as it was before
> 2. Allow changing driver in ENROLL, do not allow later
> 3. Allow changing driver in ENROLL only, but create a way back from
MANAGEABLE to ENROLL ("unmanage"??)

What problem are you trying to solve? Because I don't see a problem with
the current behavior, and you're proposing breaking the API and requiring
users to follow a significantly more complex process should they need to
change what driver is in use for a node, and preventing ever doing that
while a workload is running...


> Cheers,
> Dmitry
> [1] https://review.openstack.org/#/c/179151
> __________________________________________________________________________
> 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/20150604/be4364aa/attachment.html>

More information about the OpenStack-dev mailing list