Re: [zones-discuss] Zones and NPIV
Steve Lawrence wrote: We working on having the virtual HBA's WWN automatically assigned - either using a random number or using a range of WWN available from the HBA's base WWN. This will alleviate typing long strings of digits. Just to clarify, the generated virtual wwn number would be chosen at zonecfg time when the npiv is added, this way it remains the same across zone reboots and migrations? I'm under the assumption that SAN featurues like lun masking key off of the wwn number of the host adaptor. -Steve L. That's exactly right. Once created, the WWN is constant across migration. Aaron ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zones and NPIV
I work with Jack, and wanted to follow up to the community about our latest thoughts: In answer to Mike Gerdts' query, we will allow an NPIV WWN to follow a non global zone from one box to another. One caveat is that the user will have to intervene to bind the virtual NPIV port to a new physical HBA. Also, due to the way zones works, all devices are visible in the global zone. In answer to Ed Pilatowicz's reply, we decided to change behavior, which I think fits the zones management model better: zonecfg will only update parameters to non global zone zoneadm verify (and implicit verify at zoneadm boot) will verify that the physical HBA exists, and that it supports NPIV zoneadm boot will create the NPIV port We will dynamically mount block devices as they appear. We working on having the virtual HBA's WWN automatically assigned - either using a random number or using a range of WWN available from the HBA's base WWN. This will alleviate typing long strings of digits. Cyril's post - currently non global zones only see block devices - there's no way to do scsi passthrough, or use the HBA API. So, a global zone administrator must create the partitions on the SCSI device, and handle FC administration. Then the block device will be usable in the non global zone. This does limit the usability of NPIV, but I believe due to zones architecture, there's a limitation of only mapping leaf nodes to non global zones. Aaron This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zones and NPIV
jey jack, interesting idea. i'm not really familiar with NPIV, but i can make some general comments based on your examples below. first off, doing a zonecfg should not change the state of the machine, allocate resources etc. all zonecfg can do is update the zone xml configuration file and verify it's contents. so things like allocating a virtual port in the global zone during zonecfg and the npiv-attach command don't really seem like a good idea to me. zone resources are actually allocated and initialized when moving into the zone ready state, which can be triggered via zoneadm(1m). also, the current ??wwn numbers seem very user unfriendly and easily prone to typing errors. couldn't these be managed in some central naming service? perhaps a new nsswitch.conf name service map? if that was the case then you could use a resource name that would map to the nubers below, and that resource could be available on all machines that are connected to the same fc fabric, there by making it easy to migrate zones around. if i'm totally offbase then just let me know since i haven't actually read up on how npiv works. take it easy, ed On Fri, Nov 02, 2007 at 10:45:32PM -0700, Ran Jack Meng wrote: Hi Folks, I'm an engineer working on the NPIV project, http://opensolaris.org/os/project/npiv/, which is a method for virtualizing a FibreChannel Port. It is considered useful in virtual environment as Xen and Logical Domain as each virtual system could have its own FC N_PORT_ID and storages via the virtual port and the virtual port could be still available after migration therefore associating storage. However I'm thinking if NPIV could also be applied to Zones, and implementing a prototype. The idea is to add a resource type as 'npiv' and three resource prop for it, 'vpwwn'(virtual port WWN), 'vnwwn' (virtual node wwn) and 'ppwwn'(physical port wwn). A subcommand in global scope, 'npiv-attach' is also added to attach devices from the virtual FC port. Here is a sript showing how it should work, - [EMAIL PROTECTED]:$ /net/kungfu/export/home1/jack/zone/snv/usr/src/cmd/zonecfg/zonecfg -z my-zone zonecfg:my-zone info zonename: my-zone zonepath: /zone/my-zone ... zonecfg:my-zone add npiv zonecfg:my-zone:npiv set vpwwn=1011 zonecfg:my-zone:npiv set vnwwn=1010 zonecfg:my-zone:npiv set ppwwn=0100 zonecfg:my-zone:npiv end (A virtual port will appear here in global zone) zonecfg:my-zone info zonename: my-zone zonepath: /zone/my-zone . npiv: vpwwn: 1011 vnwwn: 1010 ppwwn: 0100 dedicated-cpu: ncpus: 1 importance: 10 zonecfg:my-zone npiv-attach Attaching FC dev /dev/rdsk/c7t226000C0FFAA7AF9d1s2. Attaching FC dev /dev/dsk/c7t226000C0FFAA7AF9d1s2. Attaching FC dev /dev/rdsk/c7t226000C0FFAA7AF9d0s2. Attaching FC dev /dev/dsk/c7t226000C0FFAA7AF9d0s2. zonecfg:my-zone info zonename: my-zone zonepath: /zone/my-zone . net: address: 10.13.49.146 physical: e1000g0 npiv: vpwwn: 1011 vnwwn: 1010 ppwwn: 0100 device: match: /dev/rdsk/c7t226000C0FFAA7AF9d1s2 device: match: /dev/dsk/c7t226000C0FFAA7AF9d1s2 device: match: /dev/rdsk/c7t226000C0FFAA7AF9d0s2 device: match: /dev/dsk/c7t226000C0FFAA7AF9d0s2 dedicated-cpu: ncpus: 1 importance: 10 ... zonecfg:my-zone commit zonecfg:my-zone exit -- Reboot the zone then it sees FC devices -- [EMAIL PROTECTED]:$ zoneadm -z my-zone halt [EMAIL PROTECTED]:$ zoneadm -z my-zone boot [EMAIL PROTECTED]:$ zlogin -C my-zone [Connected to zone 'my-zone' console] Sep 25 01:47:07 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.11 snv_64a October 2007 bash-3.00# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c7t226000C0FFAA7AF9d0 DEFAULT cyl 1303 alt 2 hd 255 sec 63 sd65 at fp3 slave 555008 1. c7t226000C0FFAA7AF9d1 DEFAULT cyl 1303 alt 2 hd 255 sec 63 sd64 at fp3 slave 555009 Specify disk (enter its number): --- Any comment on the idea and the prototype? Thanks, Jack 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] Zones and NPIV
On 11/3/07, Ran Jack Meng [EMAIL PROTECTED] wrote: Any comment on the idea and the prototype? I love the idea. I had assumed that I would have to implement LDOMs to get this level of integration with NPIV. The key thing that I would be looking for is that I can detach a zone from one box and attach it to another and all would be well without storage reconfiguration - the storage would be accessible by the non-global zone regardless of where it is at but would not be accessible by the global zone or any other non-global zone. If that wouldn't work, I guess I need to get better grounded in how NPIV works and would appreciate any pointers to concise info to help bring me up to speed. Mike -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Zones and NPIV
Hi Folks, I'm an engineer working on the NPIV project, http://opensolaris.org/os/project/npiv/, which is a method for virtualizing a FibreChannel Port. It is considered useful in virtual environment as Xen and Logical Domain as each virtual system could have its own FC N_PORT_ID and storages via the virtual port and the virtual port could be still available after migration therefore associating storage. However I'm thinking if NPIV could also be applied to Zones, and implementing a prototype. The idea is to add a resource type as 'npiv' and three resource prop for it, 'vpwwn'(virtual port WWN), 'vnwwn' (virtual node wwn) and 'ppwwn'(physical port wwn). A subcommand in global scope, 'npiv-attach' is also added to attach devices from the virtual FC port. Here is a sript showing how it should work, - [EMAIL PROTECTED]:$ /net/kungfu/export/home1/jack/zone/snv/usr/src/cmd/zonecfg/zonecfg -z my-zone zonecfg:my-zone info zonename: my-zone zonepath: /zone/my-zone ... zonecfg:my-zone add npiv zonecfg:my-zone:npiv set vpwwn=1011 zonecfg:my-zone:npiv set vnwwn=1010 zonecfg:my-zone:npiv set ppwwn=0100 zonecfg:my-zone:npiv end (A virtual port will appear here in global zone) zonecfg:my-zone info zonename: my-zone zonepath: /zone/my-zone . npiv: vpwwn: 1011 vnwwn: 1010 ppwwn: 0100 dedicated-cpu: ncpus: 1 importance: 10 zonecfg:my-zone npiv-attach Attaching FC dev /dev/rdsk/c7t226000C0FFAA7AF9d1s2. Attaching FC dev /dev/dsk/c7t226000C0FFAA7AF9d1s2. Attaching FC dev /dev/rdsk/c7t226000C0FFAA7AF9d0s2. Attaching FC dev /dev/dsk/c7t226000C0FFAA7AF9d0s2. zonecfg:my-zone info zonename: my-zone zonepath: /zone/my-zone . net: address: 10.13.49.146 physical: e1000g0 npiv: vpwwn: 1011 vnwwn: 1010 ppwwn: 0100 device: match: /dev/rdsk/c7t226000C0FFAA7AF9d1s2 device: match: /dev/dsk/c7t226000C0FFAA7AF9d1s2 device: match: /dev/rdsk/c7t226000C0FFAA7AF9d0s2 device: match: /dev/dsk/c7t226000C0FFAA7AF9d0s2 dedicated-cpu: ncpus: 1 importance: 10 ... zonecfg:my-zone commit zonecfg:my-zone exit -- Reboot the zone then it sees FC devices -- [EMAIL PROTECTED]:$ zoneadm -z my-zone halt [EMAIL PROTECTED]:$ zoneadm -z my-zone boot [EMAIL PROTECTED]:$ zlogin -C my-zone [Connected to zone 'my-zone' console] Sep 25 01:47:07 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.11 snv_64a October 2007 bash-3.00# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c7t226000C0FFAA7AF9d0 DEFAULT cyl 1303 alt 2 hd 255 sec 63 sd65 at fp3 slave 555008 1. c7t226000C0FFAA7AF9d1 DEFAULT cyl 1303 alt 2 hd 255 sec 63 sd64 at fp3 slave 555009 Specify disk (enter its number): --- Any comment on the idea and the prototype? Thanks, Jack This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
