Feature #2528
Solaris zones provider does not support multiple IPs
| Status: | Needs More Information | Start date: | 08/12/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | Solaris | |||
| Target version: | - | |||
| Affected Puppet version: | 0.24.8 | Branch: | ||
| Keywords: | ||||
| Votes: | 1 |
Description
There is no way, currently, to assign more than one IP to a zone. This is tedious in that if you have zones with more than a single IP, you have to remove their being included in a node after they are installed (and the other IPs are added to them).
No idea what the most elegant interface for this may be, as you may have multiple interfaces on a zone, or you may have to assign more IPs to the loopback in addition to the public interface(s).
Related issues
History
Updated by James Turnbull almost 3 years ago
- Status changed from Unreviewed to Needs Decision
Updated by James Turnbull almost 3 years ago
- Status changed from Needs Decision to Accepted
Updated by Martin Englund about 2 years ago
- Assignee set to Martin Englund
Updated by Martin Englund about 2 years ago
- Status changed from Accepted to Needs More Information
Multiple IPs can be set for a zone by using an array:
ip => ["e1000g0:192.168.0.1", "e1000g1:192.168.1.1"]
isn’t that working for you?
Updated by jerry blun over 1 year ago
I´m using puppet 2.6 and changing the ip of an existing zone with iptype=exclusive fails after the first successful run:
(/Stage[main]//Node[rs1]/Zones::Instance[ns1]/Zone[ns1]/ip) defined 'ip' as 'vphys_int0::'
all following runs:
(/Stage[main]//Node[rs1]/Zones::Instance[ns1]/Zone[ns1]/ip) change from vphys_ext0vphys_int0 to vphys_int0:: failed: Failed to apply configuration
My piece of code:
$zname = "$name.$domain"
zone { '$name':
autoboot => 'true',
iptype => 'exclusive',
ip => ['vphys_int0::', 'vphys_ext0::'],
path => "/export/zones/$name",
realhostname => $zname,
require => File["/export/zones/$name"],
}