http://defect.opensolaris.org/bz/show_bug.cgi?id=8649
Summary: ncu type vs. ncu class
Classification: Development
Product: nwam
Version: unspecified
Platform: ANY/Generic
OS/Version: All
Status: NEW
Severity: major
Priority: P2
Component: CLI
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: Anurag.Maskey at Sun.COM
QAContact: nwam-dev at opensolaris.org
There has been some confusion between ncu types and classes having to do with
nwamcfg and nwamadm.
nwamcfg takes ncu classes (e.g., select ncu phys bge0, create ncu ip e1000g0),
whereas nwamadm takes ncu types (e.g., nwamadm enable -t link bge0, nwamadm
list -t ip e1000g0). Note that IP is both type and class.
To avoid this confusion, we have decided to use ncu classes everywhere. Since
the ncu type can be inferred from the ncu class, the library API does not
change (i.e., nwam_ncu_create(), nwam_ncu_read(), etc. will take both type and
class). The CLI will use classes.
The grammar and usage of nwamcfg does not change. The usage for nwamadm will
be:
bash-3.2# nwamadm
usage: <subcommand> <args> ...
help
enable [-p <profile-type>] [-c <ncu-class>] <object-name>
disable [-p <profile-type>] [-c <ncu-class>] <object-name>
list [-p <profile-type>] [-c <ncu-class>] [<object-name>]
interact [-v]
Also, to avoid confusion in the spec/doc between IP types and classes, the type
will be renamed to "interface". Thus, the type is "interface" and class is
"ip".
This will require that a flag day be announced when this bug is integrated in
the build archives. Users will have to remove all previous configurations and
start of scratch. Notes for this were sent out to the mailing list a few weeks
ago.
There have been calls for the confusion of flags (-p, -t) in nwamadm and not in
nwamcfg. That will not change. Removing the flags from nwamadm and using the
keyword placement is frowned upon in CLI design. nwamcfg will not take flags
because is meant to be used as a language.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
