cobbler-enlist and the Orchestra installation experience
Last cycle we drafted a tool called cobbler-enlist, which is included in the installer and to be used from preseeds for automatically enrolling a fresh system into Cobbler, Orchestra and Juju. We've laid the groundwork, but we need to define exactly what we expect this work flow to look like, what pieces of information it needs to phone home and how it fits into the larger installation experience.
Blueprint information
- Status:
- Complete
- Approver:
- Robbie Williamson
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Robbie Williamson
Whiteboard
Thoughts
* the debconf question in the installer should optionally take a simple ip address of the cobbler server and build a proper cobbler_api url around it
* the orchestra server could avahi advertise that it exists on the network and the ISO could pick that up
* ideally, the cobbler-enlist option should be as hands-off as possible (skipping language/
