Re: [zones-discuss] Centralized Zone Management Tool
Yes -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Centralized Zone Management Tool
Sorry to interrupt your discussion. when you are discussing Puppet, are you discussing this project http://projects.reductivelabs.com/projects/puppet or something else? thank you, Jerry Kemp On 07/10/09 07:17, Bryan Allen wrote: +-- | On 2009-07-10 04:52:59, Robert Gst??hl wrote: | | Date: Fri, 10 Jul 2009 04:52:59 PDT | From: Robert Gst??hl | To: zones-discuss@opensolaris.org | Subject: [zones-discuss] Centralized Zone Management Tool | | Hello World, | | I started to think about a centralized zone management utility / system. I know exactly one tool that does this, which is proprietary, expensive, complicated and has too much half baked features. xVM ops center doesn't do what I need either and is closed source too. | | It's time to scratch an itch. | | To further illustrate what I'm thinking about here some use cases: | | crud (create, read, update, delete) on zone configurations | state changes of zones (boot, halt, restart, ...) | migrate a zone from one host to another to build ha / desaster tolerant solutions | | administration of the underlying storage of a zone (san luns, isci, nfs, zfs, - you get the idea) is propably the toughest part, I guess keeping this out of scope in the first phase is a good idea ;) | | I'm eager to hear what you the opensolaris zone community thinks about such a tool, who would like to help me do a little initial design work in the inception phase. | | Thanks for your time and input. Regards Robert Puppet manages zones, ZFS, NFS, and you could write providers to do the rest. Puppet is free, well-written, and has a great dev team. It's also being incorporated into many other management projects (like Cobbler), so you could say it's either already or on its way to becoming an industry standard. The DR stuff would probably be non-trivial, though in my shop I just move the zone class to another host, boot it, it mounts the data via NFS or what have you, and I'm done. ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone in down state.
See the following threads: http://opensolaris.org/jive/thread.jspa?threadID=101438&tstart=30 http://www.opensolaris.org/jive/thread.jspa?threadID=107664&tstart=0 Derek On Mon, Jul 13, 2009 at 12:23 AM, Ketan wrote: > One of my zone is stuck in down state, not able to boot it or halt it .. > not even detach .. is there any way to recover without rebooting the whole > system ( global zone ) ? > -- > This message posted from opensolaris.org > ___ > zones-discuss mailing list > zones-discuss@opensolaris.org > ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Centralized Zone Management Tool
Ok, I've looked at the zone puppet type and have come to the conclusion that puppet, at least in it's current form, does not what I need. At least not without some other distributed mechanism. The Problem is the migration of a zone from one host to another. Such scenarios typically involve some shared storage (SAN luns in our case) for the zone roots. Migrating a zone from host A to host B might look like this: host A: shutdown zone host A: unmount zone root host A: release metaset host B: get the zone configuration from somewhere host B: modify the zone configuration if needed (network interfaces might have another name) host B: take metaset host B: mount zone root host B: boot zone To manage this scenario, puppet would need to: 1) know that the zone is currently deployed on host A, 2) be able to resolve dependencies spanning multiple nodes. For 1) there's propably a workaround which involves specifying all the zone on all the physical nodes and use a ensure property detached or unmounted to make sure that the zone roots of zones, which are currently deployed on another node, are unmounted: node A { zone{"foobar": ensure => detached #(1 } } node B { zone {"foobar": ensure => running, require => A::Zone["foobar"] #(2 This would trigger the unmounting of the zone root } } 2) is more tricky because this feature doesn't exist in puppet. Regards Robert -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org