On Tue, Sep 08, 2009 at 10:33:56PM -0700, Nicolas Droux wrote: > > On Sep 8, 2009, at 6:55 PM, Renee Danson Sommerfeld wrote: > >> As I said, NWAM phase 1 will ignore VNICs. They will not show up in >> the Automatic NCP. >> >> At the request of folks who (as I understand it) wish to have VNICs >> created on a system which is running NWAM, the start method for the >> nwam >> service will be instantiated at boot time, just as they are in the >> start >> method for network/physical:default (the alternative to nwam). But >> because NWAM phase 1 does not yet have the flexibility to manage VNICs >> and etherstubs and other advanced link types, those links will be >> ignored, and not added to the Automatic NCP. > > That is a major pain point right now, so that will help. > > Are you also going to instantiate user-flows when is NWAM enabled? These > should be simpler to handle since they should be transparent to NWAM. Yes, I was just talking with Mike Lim about that the other day; I agree that we need to do that as well. >> If users wish to create their own configuration in a User NCP, it is >> possible to add VNICs there; however, they will be treated by NWAM >> exactly as other physical links. They must still be created using >> dladm. > > And conversely it will be possible to configure a User NCP which allows > the administrator to instruct NWAM to not plumb and configure other > (possibly non-VNIC) data links? Yes. The User NCP specifies exactly what to do with links and interfaces. This has been part of the design, described in the nwam spec (http://opensolaris.org/os/project/nwam/p1spec), for quite a long time now.
> It would be nice in the future to make this more automatic, i.e. instead > of using the data link class, query the zone/VM configuration to > determine whether a data link should be plumbed/configured by NWAM in > global zone/dom0. There are a great many things that would be nice for nwam to do in the future. Right now, we're trying really hard to lay the groundwork by getting phase 1 integrated. Please file RFEs for features you'd like to see in the future. -renee _______________________________________________ networking-discuss mailing list [email protected]
