[zones-discuss] Centralized Zone Management Tool

2009-07-10 Thread Robert Gstöhl
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
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Centralized Zone Management Tool

2009-07-10 Thread Bryan Allen
+--
| On 2009-07-10 04:52:59, Robert Gst??hl wrote:
| 
| Date: Fri, 10 Jul 2009 04:52:59 PDT
| From: Robert Gst??hl no-re...@opensolaris.org
| 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.
-- 
bda
cyberpunk is dead. long live cyberpunk.
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Centralized Zone Management Tool

2009-07-10 Thread Robert Gstöhl
I'm already using puppet at home and at work - and I love it (planning the 
migration to 0.25 right now ;).

I've not used the zone resource type yet but will give it a shot asap.

However, I need some time to get used to the idea that we might migrate our 
zones through editing a puppet manifest. It's either scary or sexy as hell - 
have to spend some time with the zone resource type and the code... ;)

Regards Robert
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] exclusive-ip

2009-07-10 Thread KARTIK VASHISHTA
Have any GLD drivers for qfe on sparc been released? I'm looking for 
developments on this. What's the likelihood, that, drivers for 
sparc-opensolaris, will, on, Solaris 10 sparc, work?

Kartik Vashishta
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] exclusive-ip

2009-07-10 Thread Wolfgang Ley
Hi,

KARTIK VASHISHTA wrote:
 Have any GLD drivers for qfe on sparc been released? I'm looking for 
 developments on this. What's the likelihood, that, drivers for 
 sparc-opensolaris, will, on, Solaris 10 sparc, work?
 
 Kartik Vashishta

The Nevada (OpenSolaris) qfe drivers are GLDv3 based. These drivers
however will not directly work on Solaris 10.

The GLDv3 qfe driver depends on the GLDv3 hme driver so first you
would need to backport the hme driver to Solaris 10 and then the
qfe driver. There are only a few code changes necessary to do this
but this will still not be done because there are several interface
changes which will break compatibility (e.g. when using the ndd
command on /dev/qfe and instance vs. /dev/qfeinstance).

So most likely there will not be any GLDv3 based qfe driver for
Solaris 10. See RFE 6590092 (qfe) and 6568532 (hme) which both have
the request for Solaris 10 backports (not done though).

Bye,
  Wolfgang Ley.
___
zones-discuss mailing list
zones-discuss@opensolaris.org


[zones-discuss] Zone Stuck in down state - nfs share

2009-07-10 Thread ajmaidak
I needed to share out a non-global zones folder via nfs so I did it from the 
global zone like so:

# share /slabzone1/zonepath/root/home

Later I rebooted the zone:
# zoneadm -z slabzone1 reboot

The reboot command hung and the zone became stuck in the down status.  I 
assume this is because of the nfs share,  I tried unsharing it, but that didn't 
help:

# unshare /slabzone1/zonepath/root/home
nfs unshare: /slabzone1/zonepath/root/home: not shared

My attempts to get the zone to transistion to installed state have all 
failed.  I assume this is a known issue, is there anyway to recover without a 
reboot?

Thanks,

Alex

___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone Stuck in down state - nfs share

2009-07-10 Thread Derek McEachern
You can look at the following thread where I had a similar problem with a
zone stuck in a shutting down state:

http://opensolaris.org/jive/thread.jspa?threadID=101438tstart=30


The other thing to look for is processing that might be accessing the ngz
from the gz using fuser. You can also use pwdx /proc/* | grep slabzone1to
find process. If you find any you can see what they are doing and kill them,
then try shutting down the zone again.

Otherwise I haven't found a way to kill the short of rebooting the box.


As an aside, I was under the impression that it was not advisable to access
ngz filesystems from the gz. A quick search only seems to point to the gz
possibly doing something nefarious to the ngz but I can't find any technical
reason it shouldn't be done.


On Fri, Jul 10, 2009 at 10:58 AM, ajmai...@mchsi.com wrote:

 I needed to share out a non-global zones folder via nfs so I did it from
 the global zone like so:

 # share /slabzone1/zonepath/root/home

 Later I rebooted the zone:
 # zoneadm -z slabzone1 reboot

 The reboot command hung and the zone became stuck in the down status.  I
 assume this is because of the nfs share,  I tried unsharing it, but that
 didn't help:

 # unshare /slabzone1/zonepath/root/home
 nfs unshare: /slabzone1/zonepath/root/home: not shared

 My attempts to get the zone to transistion to installed state have all
 failed.  I assume this is a known issue, is there anyway to recover without
 a reboot?

 Thanks,

 Alex

 ___
 zones-discuss mailing list
 zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

[zones-discuss] prebuilt solaris 10 container pkgs

2009-07-10 Thread Jerry Jelinek

I've uploaded prebuilt SVr4 pkgs onto the project page
for the solaris10 brand that we're building.

http://opensolaris.org/os/project/s10brand/

I'll do this from now on as we sync to each nevada build.
The current pkgs are meant to be used with b118.  The
OpenSolaris dev repository should be hosting that soon (next
week I think).

This might make it easier for people who want to play around
with the brand.  Since these are development bits, not everything
is going to work properly inside the zone but overall it is
pretty usable at this point, although we only work with shared stack
right now and delegated ZFS datasets don't work yet.  Feel free to
send us feedback if you try this out and let me know if there are
any questions.

Thanks,
Jerry
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Centralized Zone Management Tool

2009-07-10 Thread Bryan Allen
+--
| On 2009-07-10 06:29:51, Robert Gst??hl wrote:
| 
| I'm already using puppet at home and at work - and I love it (planning the 
migration to 0.25 right now ;).
| 
| I've not used the zone resource type yet but will give it a shot asap.
| 
| However, I need some time to get used to the idea that we might migrate our 
zones through editing a puppet manifest. It's either scary or sexy as hell - 
have to spend some time with the zone resource type and the code... ;)

Migrating in my context is ensuring the zone is stopped on the original host,
and then including the zone manifest (which includes the zone resource, and the
zone's node resource) in the new host. My stuff is not smart enough to copy
required data, etc.

I was not referring to the Sun concept of zone migration, which includes the
above (and might actually work now, with upgrade on attach), but which in my
shop would be a lot of tedious overhead (I like zfs send as much as the next
guy, but... :)

I'd be happy to share manifests, but they're still first-run (though over a
year old) and sort of ghetto, in terms of current Puppet BCP.
-- 
bda
cyberpunk is dead. long live cyberpunk.
___
zones-discuss mailing list
zones-discuss@opensolaris.org