Issue #2528 has been updated by Rahul Gopinath.
puppet 2.7
#puppet --version
2.7.14
#cat x
zone { 'z1':
ensure => running,
autoboot => 'true',
ip => ['e1000g0:192.168.10.01','e1000g0:192.168.10.02'],
iptype => 'shared',
path => '/export/xxx'
}
#puppet apply x
notice: /Stage[main]//Zone[z1]/ensure: created
notice: Finished catalog run in 14.82 seconds
#puppet resource zone z1
zone { 'z1':
ensure => 'running',
autoboot => 'true',
ip => ['e1000g0:192.168.10.01', 'e1000g0:192.168.10.02'],
iptype => 'shared',
}
----------------------------------------
Feature #2528: Solaris zones provider does not support multiple IPs
https://projects.puppetlabs.com/issues/2528#change-67391
Author: Bryan Allen
Status: Needs More Information
Priority: Normal
Assignee: Martin Englund
Category: Solaris
Target version:
Affected Puppet version: 0.24.8
Keywords:
Branch:
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).
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
