Partition 1) Production programs and data - runs the business and is not
exposed to the world.
Partition 2) Website hosting for our dealers - Exposed to the rest of the
world and keeps the production system isolated
Partition 3) Test environment with data where the programmers can update
and blow away data that is similar to the production.
Partition 4) HA MIMIX target of the Production partition.
Partition 5) HA MIMIX target of the Website partition.
Having it all on 2 physical sets of hardware makes it easier to contain,
maintain, and cool in the server rooms.
Western Power Sports
On Mon, Jun 9, 2014 at 10:33 AM, Nathan Andelin <nandelin@xxxxxxxxx> 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
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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives