As you likely guessed I do this a lot. And like anything that you do a
lot, it's not hard at all. As an example while sitting in the COMMON
opening session I built 30 partitions on the COMMON lab server. (Ask
Steve Will and Dave Nelson, they were peeking!)
We have virtualization options available with more coming from IBM and
we also have built scripts to do this.
Be very careful when comparing the questions on a list like this one
that are going to lean heavily to first time practitioners or those
curious about the process vs talking to Jim or Pete or Rob or others
that do this all the time.
- Larry "DrFranken" Bolhuis
On 6/9/2014 12:33 PM, Nathan Andelin wrote:
Based on prior discussions on this list, there appears to be quite a bit of
effort involved in setting up partitions, virtual I/O, applying PTFs and
Technology Refreshes, and just general support. What drives people to do it?
Are there certain aspects about certain types of workloads that are driving
this? If so, then what, specifically?
I think I already understand the business case for using separate
partitions for separate tenants. Individual organizations may need
completely separate virtual machine instances to keep their environments
But why are some organizations partitioning their servers for internal use
Another related, but somewhat different question, is what it might take to
streamline the process for creating IBM i partitions, similar to the
platform-as-a-service offerings from organizations such as the following:
IBM i on Power appears to be left behind in a rush toward cloud services
from organizations such as Amazon Web Services, Google App Engine,
Salesforce, IBM Bluemix, which appear to make it very easy to create VM
environments for Windows and Linux platforms.