Bug 10781 - RFE - AI Needs to Support Name Service Configuration for Clients
: RFE - AI Needs to Support Name Service Configuration for Clients
Status: NEW
Product: nwam
ON misc
: unspecified
: ANY/Generic OpenSolaris
: P4 enhancement (vote)
: ---
Assigned To: NWAM Project
: NWAM Project
:
:
:
:
: 10783
  Show dependency treegraph
 
Reported: 2009-08-20 02:54 UTC by Octave Orgeron
Modified: 2009-09-11 18:38 UTC (History)
3 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Octave Orgeron 2009-08-20 02:54:32 UTC
AI needs support auto-configuration of name services for clients. This should
be configurable at the "create-service" level or at the "create-client" level
for installadm. It should support LDAP/AD, Keberos, and DNS. The name services
configuration should be part of the created services manifest or the client
manifest. The AI client upon first boot-up, should import this data and
configure the name services correctly. This would basically replace the
sysidcfg process used in Jumpstart in the area of name services.
Comment 1 Jan Damborsky 2009-08-24 09:48:50 UTC
As far as post installation configuration of client to be installed is
concerned,
the vision is to customize things via SMF properties provided in AI manifest.
AI itself is supposed to be as much agnostic as possible about what those
properties represent - it would just provide transfer mechanism to pass those
SMF properties to appropriate consumer.
Teams in charge of particular technologies are assumed to provide necessary
APIs (e.g. definition of SMF properties).
For instance, there is bug 10307 filed to track the request for being able to
configure installed system with static network configuration (as oppose
to DHCP one).
Transferring to the same network category as bug 10307.
Comment 2 Renee Danson Sommerfeld 2009-09-11 18:38:34 UTC
Marking this as an enhancement, in accordance with the synopsis.