Description of problem: Document Generic node deployment - hardware provisioning phase (split stack - part1) in Tripleo.
Hi Emilien, What kind of documentation requirements are needed for this BZ. Is the case of deploying a Generic node simply a matter of creating a "generic" role with no services (or possibly a minimal number of kernel-related services)? - Dan
Yes, from my understanding this is about: Split Stack phase 1: the ability to deploy baremetal nodes and not deploy any software configuration on those nodes.
Yes Dan, I think this is about defining a roles_data without any services, such that folks might reasonably configure them with some other tool. So it's probably going to be something like cp /usr/share/openstack-tripleo-heat-templates/roles_data.yaml my_roles_data.yaml <edit my_roles_data.yaml to make the Services lists empty> openstack overcloud deploy --templates -r my_roles_data.yaml There will still be some hieradata written to the nodes, and we'll still configure networking, but otherwise they will be unconfigured.
Thanks, Emilien and Steve. I've put some content for this item: https://doc-stage.usersys.redhat.com/documentation/en/red-hat-openstack-platform/10-Beta/single/advanced-overcloud-customization/#example_5_generic_node_with_no_services Any chance you guys could take a look and provide feedback? Also, I tested this out and found a little "gotcha" -- you need to omit the `ServicesDefault` parameter completely -- not just have a blank list. If you leave an empty `ServicesDefault` param, it throws up an error: ERROR: Failed to validate: : resources.GenericServiceChain: : The Resource Type (None) could not be found.
It looks good to me. Only thing is "any OpenStack services configured", we don't install any service on it (OpenStack or not OpenStack). Otherwise it's good to me.
(In reply to Emilien Macchi from comment #7) > It looks good to me. Only thing is "any OpenStack services configured", we > don't install any service on it (OpenStack or not OpenStack). Otherwise it's > good to me. Yeah, I worded it like this on purpose since this overcloud-full image has the OpenStack components pre-installed.
@ddomingo -- this is ready for peer review.