[RFE] Allow setting {provisioning,cleaning}_network in node driver_info
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Fix Released
|
Wishlist
|
Dmitry Tantsur | ||
Bug Description
There are several reasons users might want it:
1. Users of our API are not necessary the same people who install Ironic. They might not have rights to modify configuration files. This is even more important now that we have policy support.
2. Installers like TripleO install and configure all services before the first objects (like networks) are created by users. So a user has to set this configuration option manually on all Ironic nodes or run a long stack-update process just for this one option.
3. They actually have different provisioning/
4. For consistency with deploy_
I suggest accepting driver_
| summary: |
- It is impossible to set cleaning_network_uuid per node + [RFE] Allow setting cleaning_network_uuid per node |
| Changed in ironic: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| tags: | added: rfe |
| description: | updated |
| description: | updated |
| description: | updated |
| summary: |
- [RFE] Allow setting cleaning_network_uuid per node + [RFE] Allow setting {provisioning,cleaning}_network_uuid in node + driver_info |
| description: | updated |
| Changed in ironic: | |
| assignee: | nobody → Dmitry Tantsur (divius) |
| Jim Rollenhagen (jim-rollenhagen) wrote Re: [RFE] Allow setting {provisioning,cleaning}_network_uuid in node driver_info | #1 |
| Dmitry Tantsur (divius) wrote | #2 |
| Changed in ironic: | |
| assignee: | Dmitry Tantsur (divius) → nobody |
| Ruby Loo (rloo) wrote | #3 |
| tags: |
added: rfe-approved removed: rfe |
| summary: |
- [RFE] Allow setting {provisioning,cleaning}_network_uuid in node - driver_info + [RFE] Allow setting {provisioning,cleaning}_network in node driver_info |
| Changed in ironic: | |
| assignee: | nobody → M V P Nitesh (m-nitesh) |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ironic (master) | #4 |
| Changed in ironic: | |
| status: | Confirmed → In Progress |
| Changed in ironic: | |
| assignee: | M V P Nitesh (m-nitesh) → Dmitry Tantsur (divius) |
| Changed in ironic: | |
| assignee: | Dmitry Tantsur (divius) → Harald Jensås (harald-jensas) |
| Changed in ironic: | |
| assignee: | Harald Jensås (harald-jensas) → Dmitry Tantsur (divius) |
| OpenStack Infra (hudson-openstack) wrote Fix merged to ironic (master) | #5 |
| Changed in ironic: | |
| status: | In Progress → Fix Released |
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ironic 10.1.0 | #6 |
While I don't think this is very useful, and I think it's kind of silly, I'm okay with this if we fall back to config. Someone is going to come along eventually with a real use case for it anyway.
Let's be clear though: I don't think tripleo's architecture alone is ever a reason to do something like this in ironic.