Feature Request: Allow user specified vendor-data to be applied to all machines
Bug #1863918 reported by
Nick Niehoff
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
There are certain cases where a user may have site specific customization they would like to do on all of their nodes. MAAS does some of this for NTP through the UI, but cloud-init allows for so much more with vendor data. I would suggest allowing the user to provide a yaml for vendor data that would be merged with the MAAS vendor data and applied to all nodes.
Related branches
~nniehoff/maas:nniehoff-vendor-data-feature
- Adam Collard (community): Needs Information
- MAAS Lander: Needs Fixing
-
Diff: 54 lines (+22/-1)1 file modifiedsrc/metadataserver/vendor_data.py (+22/-1)
| Changed in maas: | |
| status: | New → Incomplete |
| tags: | added: sts |
| Changed in maas: | |
| status: | Incomplete → In Progress |
Revision history for this message
| Adam Collard (adam-collard) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Nick Niehoff (nniehoff) |
| Changed in maas: | |
| assignee: | Nick Niehoff (nniehoff) → nobody |
| status: | In Progress → Triaged |
| status: | Triaged → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in maas: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Thanks for the patch! There are some hygiene issues with the branch (no tests, won't work in the snap) but I think more importantly we need to understand the kinds of customisation that is required here. The existing preseeds mechanism is valuable as a workaround for things that MAAS doesn't (yet) support, but we have to be very careful extending it.
Can you evaluate the customisation that you're needing and classify it?