Readers' comments (4) 
Posted by Mr. Robert Blizard on 16 December 2008 at 8:36 I was quite excited when I saw this title; I'm working hard to sell m-t in our organization. I was disappointed to find out that this addresses only the hardware piece of the pie. I was hoping to see a discussion of multi-tenancy at both the hardware and OS level. Still, this is a good start. As drafts go, this one is very rough from the spelling, grammar, and punctuation aspect. It needs a lot of editing to bring it up to the usual level of RedBook polish. |
Posted by Chris Almond on 17 December 2008 at 7:46 Robert - thanks for your feedback. I'm very curious about what your expectations were for this topic beyond what we covered... "the hardware piece of the pie". Please share details on what you would have liked to see. Your input could help guide content strategy for future versions. |
Posted by Mr. Jason Meiers on 24 December 2008 at 8:18 Multitenant in regards to software-as-a-service vendors providing software to customers leveraging the same hardware and purchasing based on actual demand. For example, adding resources based on performance data extracted from the system, autonomics to allow AIX server virtulization to add instances and remove instances based on actual demand. Utility Computing for AIX based on actual elased CPU time consumed by the utility consumer. |
Posted by Mr. Robert Blizard on 23 February 2009 at 9:34 My take on multitenancy falls somewhere in the first two levels you offer as examples - application or middleware. We already do lots of hardware mulitenancy, and do application by stacking Oracle DBs within a single LPAR, but I'm interested in how WPAR can help us be more efficient, have better isolation/control of resources, etc. I'll hope to see a follow-on Redbook that explores this aspect. |