Hi Andrea, For 16 cores, it uses image id 22400 going through the Softlayer CLI sl cci create --cpu=16 --memory=32768 --os=REDHAT_6_64 --test --hostname=leons --domain=softlayer.com --hourly --debug=3
...
<member>
<name>id</name>
<value>
<int>22400</int>
</value>
</member>
...
<member>
<name>item</name>
<value>
<struct>
<member>
<name>description</name>
<value>
<string>Red Hat Enterprise Linux 6 - Minimal Install (64 bit)
(5 - 100 Core)</string>
</value>
</member>
</struct>
</value>
</member>
...
For 4 cores, it uses image id 13799 going through the Softlayer CLI
sl cci create --cpu=4 --memory=32768 --os=REDHAT_6_64 --test
--hostname=leons --domain=softlayer.com --hourly --debug=3
...
<member>
<name>id</name>
<value>
<int>13799</int>
</value>
</member>
...
<member>
<name>item</name>
<value>
<struct>
<member>
<name>description</name>
<value>
<string>Red Hat Enterprise Linux 6 - Minimal Install (64 bit)
(1 - 4 Core)</string>
</value>
</member>
</struct>
</value>
</member>
...
Why does jclouds see image id 13799 as an option but does not see image id
22400? What Softlayer API call does jclouds use to compile its list of
Softlayer images?
I'm wondering if maybe jclouds gets confused by REDHAT_6_64 being used to
refer to more than one image. Softlayer CLI lists REDHAT_6_64 more than
once:
sl cci create-options
: os (REDHAT) :
REDHAT_5_32
:
: :
REDHAT_5_32
:
: :
REDHAT_5_64
:
: :
REDHAT_5_64
:
: :
REDHAT_6_32
:
: :
REDHAT_6_32
:
: :
REDHAT_6_64
:
: :
REDHAT_6_64
:
CLI doc:
http://softlayer.github.io/softlayer-api-python-client/cli.html#configuration-setup
http://softlayer.github.io/softlayer-api-python-client/install.html#using-pip
Thanks,
- Leons
From: Andrea Turli <[email protected]>
To: [email protected]
Date: 12/03/2013 07:17 AM
Subject: Re: Problem provisioning RHEL image on Softlayer
Hi Leons,
I can confirm you that using imageId("13799").hardwareId
("2235,22422,13887") I get the same error you described
"error":"Red Hat Enterprise Linux 6 - Minimal Install (64 bit) (1-4 Core),
price ID# 13799, has a CORE capacity restriction that does not match the
capacity of 16 x 2.0 GHz Cores, price ID# 2235. Please submit prices that
are compatible.",
To me, this is a server side restriction, so my question is why this is not
happening using the UI?
Could you confirm that manually creating the CCI will then use those ids?
It seems to me that the validation order is doing something more clever on
the UI side to avoid these restrictions.
Thanks,
Andrea<<inline: graycol.gif>>
