Hi Todd,
On 03/05/09 07:37, Todd E. Moore wrote: > Is it possible to specify an alternate hostname as part of the AI > Server setup? > > To test the AI functionality I must operate on a private network since > the DHCP is controlled by others. I have multiple NICs in the system > and am able to setup a private network for the AI clients. When > setting up the AI Server it assumes that the 'hostname' that I want to > use is the same as the nodename and I haven't seen anything in the > documentation which would allow me to specify the hostname of the 2nd NIC. At the time being, installadm(1M) doesn't have appropriate API for setting up AI server on machine with multiple subnets - there is a bug filed for this issue: 6182 installadm tools doesn't support install servers which have mutiple subnets > > I also experimented creating the AI Server in a Solaris Container, but > my container didn't have external network access and the > SUNWinstalladm-tools pkgs didn't get populated during the install of > the container despite existing in the global zone. > > Another option I am considering to start educating customers involves > using VirtualBox's "internal network" option, but I think that I will > run into the same issues previously identified. In this scenario, I > would create NIC 1 with public network access and NIC 2 would be for > 'internal network". A second VM would be created in Virtual Box with > its primary NIC connected to the internal network of VBox and would > boot from the AI Server across this network. Seemed like a fairly > easy and self contained demo environment/sand box, but I'm not having > much success thus far. I was able to successfully use VB in the scenario you have described. My testing set up was slightly different - I configured NIC1 as NAT on guest serving as AI server - this assures that DHCP server will remain isolated from public network. AI server NIC2 was connected to VB's "internal network" along with AI client NIC - AI client was created as 2nd VB guest. DHCP, TFTP, HTTP protocols work correctly in this configuration. The only think which doesn't work is multicast DNS on VB's "internal network" and thus service discovery fails - there is a bug 6320 which will introduce support for fallback mechanism in cases when multicast DNS is not available - once that bug is fixed, then whole process of AI installation should work. > > Am I pushing the envelope a bit too far too early in the development > of AI? I don't think so :-) Thanks for trying this ! Jan
