Feature #1696
Add support for branded zones
| Status: | Closed | Start date: | 10/27/2008 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | Solaris | |||
| Target version: | 0.24.7 | |||
| Affected Puppet version: | 0.24.5 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
This patch adds two new parameters on the zone type, and the backing provider support. The parameters are create_args and install_args. These are passed to the zonecfg create and zoneadm install commands, respectively. I implemented these so that I could create solaris8 branded zones, but it’s probably useful for other things, including linux branded zones, and anything else you’d want to pass these arguments in for.
History
Updated by James Turnbull over 3 years ago
- Category set to Solaris
- Status changed from Unreviewed to Accepted
- Assignee set to Andrew Shafer
- Target version set to 0.24.7
Updated by Clayton O'Neill over 3 years ago
- File 0002-Add-support-for-branded-zones.patch added
Attached is a fixed patch. Original patch would break non-branded zones.
Updated by Andrew Shafer over 3 years ago
There are no tests for this. (not just for the patch, at all)
I think I can get them spec’d up this week.
Not knowing anything at all about branded zones (and not much more about zones for that matter) it’s hard for me to judge what is the most appropriate way to manage them. But… I think it is worth exploring managing these with a little more semantic detail.
The commands should not be a single ‘space’ delimited string, at least pass in any array.
The zone provider also has no way to really manage zone attributes. It looks like the management is only one direction and can’t go back to change the attributes of a zone that already exists. That’s a limitation for the moment, but solving that generically seems like a good idea. (but probably not for this simple patch.)
I’d like to talk with coneill about what the command actually look like and then decide if it makes sense to break them out into parameters in the type.
Updated by Luke Kanies over 3 years ago
I agree with Andrew — the args should be an array of arguments, rather than a string that you split based on whitespace.
Updated by James Turnbull over 3 years ago
- Status changed from Accepted to Code Insufficient
- Assignee changed from Andrew Shafer to Clayton O'Neill
- 3 changed from Unknown to Trivial
See comments.
Updated by James Turnbull over 3 years ago
- Status changed from Code Insufficient to Tests Insufficient
- Assignee changed from Clayton O'Neill to Andrew Shafer
Updated by Andrew Shafer over 3 years ago
- Status changed from Tests Insufficient to Ready For Checkin
- Assignee changed from Andrew Shafer to James Turnbull
ticket/0.24.x/1696
Updated by James Turnbull over 3 years ago
- Status changed from Ready For Checkin to Closed
Pushed in commit:3eff2254e69cf66b6e9f94631900fba26172c850 in branch 0.24.x