Darren J Moffat wrote:
Support for configuring NWAM via SMF properties doesn't exist. And the
Install team would prefer to not have to understand the details of an
NWAM profile to create one themselves.
Sorry but that comment alone is grounds for derailing the case. There
is an existing "profile" based architecture that already deals with
all of the things this case can do and much more.
Please put this case in waiting-need-spec and have the spec updated
with detailed information on why using an NWAM profile with a static
rather than DHCP based configuration won't work. When that
information is available the case can be re-railed if it is still even
necessary.
There has been a very significant amount of engineering work put into
NWAM profiles and the case of static configuration was an important
part of it.
Just to be clear (since I've been informed that I wasn't). What I meant
was that the Install team wants configuration to be agnostic to them.
They don't want the install mechanism to understand the format of an
NWAM profile (unless it is an SMF-based profile ... which it isn't).
Install does not even want to rely on the existence of an ipadm(1M)
command to configure an IP interface. Install is asking for committed
SMF properties that can be used to configure a system. No such thing
exists today for configuring IP interfaces. True we (Solaris Networking)
could be proposing to provide an SMF profile and SMF service that
configured an NWAM profile. However, AI install is seen to be geared
more towards Enterprise users. And it is believed that those users would
not be interested in having NWAM enabled by default by install.
Sorry if that wasn't clear when I said that the "Install team would
prefer not to understand the details of an NWAM profile". What I meant
was that the Install team does not believe that the install mechanism
should have that knowlege.
_______________________________________________
opensolaris-arc mailing list
[email protected]
