Re: [openstack-dev] [Ironic] ENROLL state and changing node driver
On 06/04/2015 06:18 PM, Devananda van der Veen wrote: On Jun 4, 2015 5:53 AM, Dmitry Tantsur dtant...@redhat.com mailto:dtant...@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... I'm not trying to solve anything right now, I'm just wondering what the point of verification is, if we can change driver right in available state (and what the consequences of such change are). I'm fine with answer #1 do nothing :) -Deva Cheers, Dmitry [1] https://review.openstack.org/#/c/179151 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] ENROLL state and changing node driver
On Jun 4, 2015 5:53 AM, Dmitry Tantsur dtant...@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... -Deva Cheers, Dmitry [1] https://review.openstack.org/#/c/179151 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Ironic] ENROLL state and changing node driver
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??) Cheers, Dmitry [1] https://review.openstack.org/#/c/179151 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
