Looking at latest recommendations - http://www.oracle.com/technetwork/server-storage/vm/ovmsparc-best-practices-2334546.pdf - specifically regarding domain roles.
At the moment, we just have a physical host, primary control domain and then guest ldoms. We then export things like vdisks,vnet etc from control domain to ldom. We don't have any additional service/IO domain.
Should we? Document doesn't really make it clear where and when you need to do this.
Some of our hosts are solaris 10, some 11.2, some 11.3. Ldoms can be anything from solaris 8 upwards.
Hardware wise, we've got some T3s, some T4s, but mainly T5s. And one new S7.
This is mostly used for monster servers such as t5-8 or t7-4, if at all.
Corner cases include regulatory/security demands, where such separation can enable you to run test and production on the same box and still be compliant
It is used for hardware separation, creating 2 (or more) servers (root/service domains) from existing hardware.
This increases the configuration complexity significantly.
For models you specify, depending on the requirements, a one root/service domain is enough for most use cases.
By creating a root/service domain, you are basically assigning a part of your box (one network card, one cpu socket + memory etc.) to serve ldoms independent of each other.
Since you have many servers in your environment, i see no need for having additional complexity of multiple service domains in one box.
Just stick to one naming policy - same vsw/vdsdev names everywhere, save your configs somewhere from all boxes and you are good to go.
Keep firmware and patch level of hypervisors on the same level.
Minimum guest ldom is solaris 10, in which you can create legacy zones if required.
Hope that helps
Regards
Peasant.
2 Likes
Thanks for the excellent answer.