Hello Ex-Sun fellows,
i've been tasked to install a bran spanking new AI Solaris 11.1 server for our Oracle park.
With the documentation this is what's running and what's working.
T5120 2 oracle VM's (one ldom on each disk)
One with a Solaris 11.1 repo, AI server.
One for testing (mainly jumpstarting the ldom)
- T5120 one VM with mirror disks
One Solaris 11.1 (testing jumpstart with mirror disks)
I'm able to install Solaris 11.1 on either the oracle VM (first T5120) or directly on the metal of the T5120 (mirror disk, blablabla)
My question is regarding installadm.... how to you guys manage it? I mean i have 2 servers right now with only one type of hardware and only one build of solaris 11.1 but i can't imagine going into production with a 50 pages long installadm -c -p -m.
root@server001a:~# installadm list -c -p -m
Service Name Client Address Arch Image Path
------------ -------------- ---- ----------
default_service 00:14:4F:F9:53:65 sparc /export/auto_install/default_service
00:21:28:18:0B:FA sparc /export/auto_install/default_service
Service/Manifest Name Status Criteria
--------------------- ------ --------
default_service
onedisk_manifest mac = 00:14:4F:F9:53:65
default_manifest Default None
Service/Profile Name Criteria
-------------------- --------
default_service
server1_profile mac = 00:21:28:18:0B:FA
server2_profile mac = 00:14:4F:F9:53:65
Default service manifest covers:
Disk, Datasets, Locale, Publishers, Build
Default profile manifest covers:
Accounts, Network, Timezone, Env, Identity, DNS
Seems like everytime i'll pull off another build i'll have to redo everything again (service/manifest/profile/client). Everytime i'll bring another hardware.. same thing. Our Oracle park is only 120 servers but with metal, vm's AND zones it will be a nightmare to manage.
There must be a simpler way... how do you guys pull it off with a big park?
Maybe i should write a build script (or web service) that customizes the manifests and does everything automaticly ... i don't know.