Axton, Thanks again for the configuration recommendations and based on BMC's unconfirmed support for LDOM's within their compatibility matrix, we have decided not to configure the servers with LDOMs.
-David Smith From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Axton Sent: Wednesday, September 15, 2010 9:17 PM To: arslist@ARSLIST.ORG Subject: Re: ARS 7.6 - Solaris LDOMs ** If you can afford it, you should use separate physical hardware for your production and non-production infrastructure. There are still things that you will have to deal with that LDOMs do not isolate you from, such as firmware/PROM updates (which are usually bundled as OS patches), load balancer configuration changes, network configuration changes that separate physical hardware does provide. If you had separate hardware, then you could test your patches, firmware updates, network changes, etc. without disrupting your production operations. It is easy to move images in zones as well; flar (flash archive) is the method I use. I can create a new zone, cloned from an existing zone, in less than an hour using this technique. If you want a clean installation on the host OS, consider using jumpstart (SUNWJet) with a custom template. This will give you an exact clone that you can rebuild on any system/architecture (sun4u/v) by booting off the network, and you can build them with the patches/patch level you want, what services run, local accounts, network configuration, local configuration, etc. I'm always leery about sharing hardware between production and non-production. It makes scaling hard to calculate when considering DR, people sometimes do bad things in non-production environments, that no matter how hard one tries to contain through virtualization, ends up impacting production. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Wed, Sep 15, 2010 at 3:10 PM, Smith, David A <da...@email.unc.edu<mailto:da...@email.unc.edu>> wrote: ** Axton, Thanks for your advice. Our system administrator mentioned that with two LDOMs you can configure cpus/disk/memory between the two on the fly running Solaris 10 update 9, and better isolation so we can test OS patches which you really can't do if you mix production/development on the same global zone. Also, since we have two dedicated T5120's in different machine rooms for disaster recovery it is easier to flash the OS image from one server to the other. Wish we had the funding for a couple of T5440s:-) -David Smith From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Axton Sent: Wednesday, September 15, 2010 11:03 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: ARS 7.6 - Solaris LDOMs ** There shouldn't be any technical reason that will stop you from doing this. Can I ask why you are moving towards LDOM instead of zones? The higher models, like T5440, support i/o domains, which are really cool and have some real benefits because the machine can be partitioned at the bus layer with a cpu crossbar, but the T5120 does not support this. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Tue, Sep 14, 2010 at 12:48 PM, Smith, David A <da...@email.unc.edu<mailto:da...@email.unc.edu>> wrote: ** Hello all, We our running our ARS production environment on a Sun enterprise 5120 server (Solaris 10) and are considering configuring the server with two LDOMs; possibility setting them up in a server group or production/development. I've contacted BMC support to find out if this configuration is supported and their response was only Solaris Zones (whole root and sparse), basically only what is listed in the Compatibility matrix. However, they did say they have tested ARS configured in a LDOM, but couldn't provide information on why it did not make the Compatibility Matrix. My question is.... anyone running a production ARS instance within a Solaris LDOM? If so any issues you would be willing to share? Thanks, David Smith Remedy Lead Developer/Administrator University of North Carolina Chapel Hill _attend WWRUG10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
