Hi All,
If you don't use the Solaris Automated Installer (AI) you can safely
ignore this message. Otherwise, with the integration of:
changeset: 925:2735806e3776
tag: tip
user: Clay Baenziger <[email protected]>
date: Sat Nov 13 03:26:34 2010 -0700
description:
6182 installadm tools doesn't support install servers which have
mutiple subnets
6448 installadm scripts should use full pathnames
6922 installadm create-service should have option to specify ip address
passed to dhcp config
7148 installadm should give correct dhcp macro for the subnet being
configured on the server
7149 installadm should allow user to choose which subnets to use
11061 create-service: is kind of like ground-hog day...
16124 setup-service.sh list_service is dead
16798 installadm-common.sh remove_vfstab_entry() and setup-tftp-links
remove are unused
16799 setup-service.sh does not successfully check that the service
registered was unique
17399 disabling the last install service via installadm disable does
not kill Apache
6993344 messages printed by AI have extraneous space
Changes were made to AI which constitute a flag day for users. Specifically the
changes are:
- AI servers now support multiple network interfaces
- The -i/-c flags to create-service only work on single-homed
servers
- DHCP macros are now provided for all configured networks on the
AI server
- One needs to use a build 153 or newer client for servers which
have multiple interfaces[1]
[1] There is a workaround for those who must serve older builds from
multihomed machines see [1] below.
Design specification:
http://hub.opensolaris.org/bin/view/Project+caiman/Multi-homed+AI+server+support
*Installadm changes*
Changes have been made to installadm(1M) in support of multihomed servers.
The server now advertises the AI service on all interfaces and accepts
requests on all interfaces by default; further. default AI DHCP macros
have been changed to support multiple networks. However, there is backward
support for older install images which do not support multihomed servers.
*Where to ask questions*
email: [email protected] for questions and help
Bugs found should be filed as follows:
For internal users, use bugster
Product: Solaris
Category: install
Subcategory: autoinstall
For External users, use defect.opensolaris.org
development/installer/autoinstall
---------------------------------------------------
[1] Details of Compatibility with older AI services
The updated installadm(1M) tool in build 153, will by default serve AI on all
subnets (as shown by ipadm(1) with the show-addr subcommand). However, to serve
an older image, one must only serve on a single subnet -- if you server only
has one subnet listed by 'ipadm show-addr' then your work is done.
If you have more than one subnet, as shown by ipadm show-addr:
Then you will need to configure your AI server to use only the desired subnet.
This can be done with the SMF svccfg(1) command. For example, if one only wants
to serve on the 192.168.1.1/24 subnet -- before service creation -- one
would run:
svccfg -s svc:/system/install/server:default setprop all_services/networks =
192.168.1.1/24
Then, the normal installadm create-service commands can be run to create a
backwards compatible service.
If these steps are not followed, one will see a failure of the AI client
downloading the solaris.zlib archive saying:
Resolving $serverip... failed: node name or service name not known.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
