Hi Randall,
Indeed there are some environments where the split network/service
macro design could be contentious. However, the thought is a DHCP admin
will only need to update one service macro, per-service in a multihomed
environment opposed to as many macros as they have services (potentially
a big win).
If you have other net-booting devices on your network it would
likely be best advised that you not provide them with your AI server as a
BootSrvA. However, other than routers and a few other application specific
devices, not much netboots. If using ISC's DHCP server, one can limit the
provisions of the BootSrvA record even more[1] to avoid affecting other
devices.
Yet, with a shared JumpStart and AI environment, unless your AI
server also happens to be your JumpStart server, you would be best advised
to leave the BootSrvA option in client or service macros. One can overlay
macros[2] so that a network wide BootSrvA is replaced by a client specific
macro too which if you only have a hand-full AI or JumpStart hosts could
still save you time. Lastly, perhaps you could split your network into
having an AI DHCP server and JumpStart DHCP server, etc. Perhaps this can
provide some good food for growing a solution? If not, I'd be happy to
discuss your situation more in-depth.
The worst that happens with a JumpStart client getting the AI boot
server is one AI's when they expected JumpStart or vice versa.
Unfortunately, this can lead to data loss if one overwrites a system
unexpectedly. Of course, both technologies have devices built-in to
attempt preventing this.
Thank you,
Clay
[1]: Some instructions for ISC DHPC with AI
http://blogs.sun.com/clayb/entry/how_to_use_isc_dhcp
[2]: Macro overlays
http://docs.sfbay.sun.com/app/docs/doc/816-4554/dhcp-overview-10?l=en&a=view
On Tue, 13 Jul 2010, Randall Chuck wrote:
Hi Clay,
At first glance, I see a possible conflict with a "subnet" named macro.
I have an environment where I have two DHCP servers using a shared data store.
One DHCP server runs on my JET server, the other on my AI server.
I have existing "subnet" macros for basic host (like system processors)
configuration with Subnet, Router, and Broadcst symbols defined.
I'm not sure what affect adding a BootSrvA symbol to the existing macro would
do.
--
Randall Chuck
----- Original Message -----
From: [email protected]
To: [email protected], [email protected]
Cc: [email protected]
Sent: Tuesday, July 13, 2010 4:06:31 AM GMT -08:00 US/Canada Pacific
Subject: [caiman-discuss] code-review for AI multihomed
Hi all,
Could Joe and John please look this over and anyone else who might
be interested? This is the wad of changes for introducing multihomed
support to AI. Please get me your impressions by Monday 7/19.
There is a known bug right now that create-client for X86 doesn't use the
$serverIP keyword as it should yet, so please be cautious of that in your
review.
The code review is posted at:
http://cr.opensolaris.org/~clayb/webrev.multihomed/
Thank you,
Clay
Example Outputs:
----------------
SPARC Service Create (as a DHCP server):
--------------------------------------
Setting up the target image at /var/ai/install_test_ai_sparc ...
Registering the service install_test_ai_sparc._OSInstall._tcp.local
Service discovery fallback mechanism set up
Creating SPARC configuration file
SPARC Service Create (not a DHCP server):
-----------------------------------------
r...@jumprope:/var/ai/install_test_ai_sparc# installadm delete-service -x
install_test_ai_sparc; installadm create-service -n install_test_ai_sparc
-s /tmp/clay_ai_sp
arc_070610.iso /var/ai/install_test_ai_sparc
Detected that DHCP is not set up on this machine. To delete the DHCP
macro, run the following on your DHCP server:
/usr/sbin/dhtadm -D -m dhcp_macro_install_test_ai_sparc
Setting up the target image at /var/ai/install_test_ai_sparc ...
If not already configured, please create a DHCP macro
named 172.20.24.0 with:
Boot server IP (BootSrvA) : 172.20.24.78
If you are running the Solaris DHCP Server, use the following
command to add the DHCP macro, 172.20.24.0:
/usr/sbin/dhtadm -g -A -m 172.20.24.0 -d :BootSrvA=172.20.24.78:
Note: Be sure to assign client IP address(es) if needed
(e.g., if running the Solaris DHCP Server, run pntadm(1M)).
Setting up the target image at /var/ai/install_test_ai_sparc ...
If not already configured, please create a DHCP macro
named 192.168.1.0 with:
Boot server IP (BootSrvA) : 192.168.1.1
If you are running the Solaris DHCP Server, use the following
command to add the DHCP macro, 192.168.1.0:
/usr/sbin/dhtadm -g -A -m 192.168.1.0 -d :BootSrvA=192.168.1.1:
Note: Be sure to assign client IP address(es) if needed
(e.g., if running the Solaris DHCP Server, run pntadm(1M)).
Service discovery fallback mechanism set up
Creating SPARC configuration file
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
