All,
I spoke to Suse and they will be posting something to the forum later
today.  However, I will say at this point that the LPAR based pricing post
is incorrect.  Straight from Suse's mouth, the pricing will remain CPU
based for the mainframe.  So, if you have 4 LPARS all running off the same
CPU, you pay for Suse one time.

With pSeries and iSeries, you pay for a box with x number of CPUs.  In my
past post the example was up to 8.  They don't care how many instances you
run.

The confusion might be coming from their support pricing structure.  That
is based on the number of instances.  1 - 5, 6- 10,etc.

I hope this clears most of the fog.  Suse should be posting to the list
sometime today also.

- Kevin

(Embedded image moved to file: pic03929.jpg)
PLEASE NOTE NEW CONTACT INFORMATION!
Kevin Gates
DSG
Linux Solutions Specialist
__________________
office 480-471-8276
fax 480-452-1470
cell 480-734-1034
[EMAIL PROTECTED]
www.dsgroup.com



                      Adam Thornton
                      <[EMAIL PROTECTED]        To:       [EMAIL PROTECTED]
                      mine.net>                cc:
                      Sent by: Linux on        Subject:  Re: FW: IBM iSource -- U.S. 
Announcements
                      390 Port
                      <[EMAIL PROTECTED]
                      IST.EDU>


                      12/17/2003 10:26
                      PM
                      Please respond to
                      Linux on 390 Port






On Wed, 2003-12-17 at 18:05, Alan Cox wrote:
> Wouldn't this depend on the price per instance and the number of
> instances, as well as the availability of both options ?

Well, I believe that there are few (note: I'm *not* saying "no") good
reasons to run Linux/390 in any context other than VM.  And, so, no,
because if you're using Linux/390 in a cost-effective manner you're
almost certainly in a situation where you're using multiple instances
per CPU.

I suppose in theory the per-instance price could be low enough that this
wasn't a problem, but then, how do you ensure license compliance?  One
of the great things about VM is the ease with which you can set up and
then destroy instances.  How do you enforce a per-instance license in
that scenario, anyway?

Adam

<<attachment: pic03929.jpg>>

Reply via email to