MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » May 2014

Re: Guest Partition OS Requirements on Power8



fixed

VIOS best practices i've seen say between 0,5 and 1 core (power6 cores)
depending on TOPAS performance data so i doubt that an IBM i hosting can
get by with less. I leave it to the Dr to have better data on that side as
unfortunately all my data is always 2 or 3 generations behind...


On Tue, May 13, 2014 at 2:41 PM, <rob@xxxxxxxxx> wrote:

Let's just say that my machine is rather temporary and per core licensing
hasn't really been a concern of mine.
And just how much processor does it really take to be a host partition?
.10?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 05/13/2014 12:09 PM
Subject: RE: Guest Partition OS Requirements on Power8
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

Are you stating that the IBM I core licensing is different when using VIOS
compared to non VIOS.
How many active cores do you have?.
How many IBM I core licenses do you have?

I have 8 active cores, but only 3 IBM I licenses.

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Roberto José Etcheverry Romero
Sent: Tuesday, May 13, 2014 12:03 PM
To: Midrange Systems Technical Discussion
Subject: Re: Guest Partition OS Requirements on Power8

I would say that not having to buy the IBM i per-core license for the
hosting partition is a very good reason to use VIOS (VIOS uses at least
0,5 core each, more if it had a lot of resources)... but the DCR is a good
idea anyways.


On Tue, May 13, 2014 at 12:35 PM, <rob@xxxxxxxxx> wrote:

IDK. My boss still thinks VIOS is some "wave of the future". But if
we can do all of our virtualization necessary from IBM i then that
significantly reduces the expense by not tying up hardware for VIOS,
not having to support vios and learning all that stuff. and so on.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 05/13/2014 11:28 AM
Subject: RE: Guest Partition OS Requirements on Power8
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

If and when your DCR would be completed, would you no longer use VIOS
for partitioning?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, May 13, 2014 10:15 AM
To: Midrange Systems Technical Discussion
Subject: RE: Guest Partition OS Requirements on Power8

I am using fiber. I was using SCSI with LTO3 back on Power 6's but
even all those switched to fiber LTO4's.
Description: 8 Gigabit PCI Express Dual Port Fibre Channel Adapter
Feature
code: 5735 Right now it's virtualized from VIOS to four lpars of IBM i.
I've submitted a design change request to allow me to bypass vios.



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 05/13/2014 09:37 AM
Subject: RE: Guest Partition OS Requirements on Power8
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Sue / Rob,

Am I correct that if the tape library was SAS attached as opposed to
fiber, then it could be virtualized, Rob I believe this is your config.
From a performance standpoint, I've always opted with fiber over SAS
attached.

From a future roadmap viewpoint, what are the options available for
tape virtualization, fiber or SAS?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sue

Baker
Sent: Tuesday, May 13, 2014 9:20 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Guest Partition OS Requirements on Power8

"Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx> wrote on Sat, 10 May
2014 22:39:33 GMT:

What are the IBM I virtualization options (host and/or guest) for
fiber attached tape, 577D?


At the present time, fibre attached tape (577D is the CCIN for feature
5735) cannot be virtualized by IBM i to any i client.

DLPARing the adapter from one partition to another is still a
reasonable way to go for fibre attached tape. I used to do this on
our systems by sending SSH commands to the HMC from my batch job stream.

--
Sue
IBM Americas Advanced Technical Sales Support (ATS) Power Systems
Rochester, MN
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact