|Summary:||[RFE] Provision overcloud with only Ironic and Neutron (without Nova and Glance)|
|Product:||Red Hat OpenStack||Reporter:||Dmitry Tantsur <dtantsur>|
|Component:||openstack-tripleo-common||Assignee:||Steve Baker <sbaker>|
|Status:||ON_QA ---||QA Contact:||Alistair Tonner <atonner>|
|Version:||16.0 (Train)||CC:||acanan, amcleod, bdobreli, bfournie, dbecker, dcadzow, fiezzi, ggrasza, jlabarre, jslagle, markmc, mburns, morazi, racedoro, sasha, scohen, shardy, slinaber|
|Target Milestone:||beta||Keywords:||FutureFeature, TechPreview, Triaged|
|Target Release:||16.1 (Train on RHEL 8.2)|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Dmitry Tantsur 2018-05-08 12:38:14 UTC
Making TripleO workflows use Ironic directly to provision nodes has quite a few benefits: 1. First and foremost, getting rid of the horrible "no valid hosts found" exception. The scheduling will be much simpler and the errors will be clearer. 2. Also important for the generic provisioner case, we'll be able to get rid of Nova and Glance, reducing the memory footprint. 3. We'll get rid of pre-deploy validations that currently try to get what nova scheduler will expect. 4. We'll become on charge of building the configdrive, potentially putting more useful things there. 5. In the future we'll be able to integrate things like building RAID on demand much easier. 6. Also in the future we might want to use introspection data in scheduling and provisioning decisions. Particularly, we can automate handling root device hints. 7. We'll probably have easier time combining ironic with pre-deployed services or virtual solutions (e.g. putting controllers on oVirt, which is currently done via an unsupported ironic-staging-driver driver). 8. Hopefully, scale-up will be less error-prone. The way I see it implemented is probably similar to the config-download work (and based on it). We can have a Heat flag to not provision instances, essentially stop after creating ports and creating ansible input. Then a mistral workflow will pick the required number of nodes, prepare them and provision. Then the usual config-download will proceed.
Comment 1 Bob Fournier 2018-08-29 17:03:26 UTC
From ML discussion, making this TechPreview for OSP-15.
Comment 17 Steve Baker 2019-10-30 19:58:28 UTC
I've attached the upstream docs bug. I think this could still be Tech Preview for 16, and ready to be the default for 16.1
Comment 23 Ramon Acedo 2020-04-22 10:55:40 UTC
Exit TP in 16.1.
Comment 24 Bob Fournier 2020-04-22 12:15:28 UTC
Ramon - this isn't planned for testing in 16.1 so should probably stay in TechPreview.