TripleO UI

Setting Boot option

Registered by Jason E. Rist

TripleO requires nodes to have properties/capabilities/boot_option:local
This should be done on registration
Question is whether this should be impemented in baremetal.register action on the backend or provided by clients. Agreement so far is to make clients provide it (CLI already does that, GUI needs to implement this)

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Jason E. Rist
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

[jpichon] There is some overlap with what I'm working on for https://bugs.launchpad.net/tripleo/+bug/1595205 (writing the client 'overcloud node configure' command). When I uploaded an extremely preliminary patch ( https://review.openstack.org/#/c/344875/1 ) and discussed it with Jirka on #tripleo the desired approach seemed to lean toward migrating the Python logic around boot configuration and root device choices to Mistral actions, so that the GUI can benefit from it as well. Perhaps we should discuss it with a wider audience to make sure that approach is indeed welcome? If it is, I'm happy to take on the tripleo-common part of the work, as I need it for that other bug anyway.

(Also for the 'registration' workflow itself I proposed a patch to add the boot option earlier on -> https://review.openstack.org/#/c/348875/ )

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.