You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Charles Moulliard <ch...@gmail.com> on 2012/12/07 16:20:34 UTC
Cloudstack - jclouds
Hi,
I use jclouds Java api to create a new instance. Using the web interface
with DevCloud2 running in VirtualBox and Apache CloudStack 4.1.0-SNAPSHOT
(management server), that works fine but when I tries to create it using
the following parameters and jclouds, I get an insufficient capacity error.
jclouds:node-create --provider cloudstack --identity
4LJ9B23kX5LswWnSHQDgjmQyXLXziyu1uxBc8GSXAzi3PrLXRbGT36D4oixxFAZGxiXPFJgXFcdC8EbFpSOdAA
--credential
M1p2PrsPSW6i9mdl1XwQyKBGoX6GdDBo6_y5SVl15h02K1xC6pj2eRMGLWGgehqD9fiCeYLfh3kWqUJCx1AZ2g
--hardwareId b73f6946-f4a7-4181-b308-29f17a772700 --imageId
293cf203-88f2-486f-b85b-188ab305b9b7 fabric
identity = apikey of admin
credential = secretkey of admin
hardwareid = tinyOffering (500MH, 500MB Ram, Local Storage)
imageId = CentOS 5.3 proposed by default (= tiny Linux Offering)
Failed to create nodes:error running 1 node group(fabric)
location(ee6fff52-4dc4-42c6-864d-663a9a7de333)
image(293cf203-88f2-486f-b85b-188ab305b9b7)
size(b73f6946-f4a7-4181-b308-29f17a772700) options({})
Execution failures:
1) ExecutionException on fabric-1:
java.util.concurrent.ExecutionException:
org.jclouds.cloudstack.AsyncJobException: job
AsyncJob{accountId=88662cb2-7f68-4795-be14-6360c4b224b8,
cmd=com.cloud.api.commands.DeployVMCmd, created=Fri Dec 07 16:05:41 CET
2012, id=52e74850-214e-4575-b5dd-1a71cc72b771, instanceId=null,
instanceType=null, progress=0, result=null, resultCode=FAIL,
resultType=object, status=FAILED,
userId=e5fa31c0-43f2-41a5-b9d5-c11d8a45180b,
error=AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable
to create a deployment for VM[User|fabric-1]}} failed with exception
AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable to
create a deployment for VM[User|fabric-1]}
at
com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:294)
at
com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:281)
at
com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:138)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Here is the config of an instance created successfully through the web
interface
Hypervisor : XenServer
Template : tiny Linux
OS Type : CentOS 5.3 (64-bit)
Attached ISO :
Compute offering : tinyOffering2
HA Enabled : No
Group :
Zone name : DevCloud0
Host : devcloud
Domain : ROOT
Account : admin
Created : 07 Dec 2012 14:23:37
ID : b860d1c3-4416-4ab5-8233-bd3d1c92064f
And the config using the command but reporting incapacity error
Hypervisor : XenServer
Template : tiny Linux
OS Type : CentOS 5.3 (64-bit)
Attached ISO :
Compute offering : tinyOffering2
HA Enabled : No
Group :
Zone name : DevCloud0
Host :
Domain : ROOT
Account : admin
Created : 07 Dec 2012 15:17:32
ID : ca75b67e-cb30-4c43-9cc3-4dc05b867470
If I compare what is created using command line and through the web
interface, the only difference is that host is not defined using command
Somebody can tell me why we have a different response from cloudstack if we
use command line vs web interface ?
Regards,
--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
RE: Cloudstack - jclouds
Posted by "Musayev, Ilya" <im...@webmd.net>.
We've created a wiki page here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI
-----Original Message-----
From: Charles Moulliard [mailto:ch007m@gmail.com]
Sent: Friday, December 07, 2012 4:17 PM
To: cloudstack-dev
Subject: Re: Cloudstack - jclouds
Do you have an example using cloudmonkey ?
On Fri, Dec 7, 2012 at 7:31 PM, Rohit Yadav <ro...@citrix.com> wrote:
> Not sure about jclouds api, can you try doing the same using cloudmonkey?
> If it does not work, probably it's a api bug.
>
> Regards.
>
> On 07-Dec-2012, at 7:20 AM, Charles Moulliard <ch...@gmail.com> wrote:
>
> > Hi,
> >
> > I use jclouds Java api to create a new instance. Using the web
> > interface with DevCloud2 running in VirtualBox and Apache CloudStack
> > 4.1.0-SNAPSHOT (management server), that works fine but when I tries
> > to create it using the following parameters and jclouds, I get an
> > insufficient capacity
> error.
> >
> > jclouds:node-create --provider cloudstack --identity
> >
> 4LJ9B23kX5LswWnSHQDgjmQyXLXziyu1uxBc8GSXAzi3PrLXRbGT36D4oixxFAZGxiXPFJ
> gXFcdC8EbFpSOdAA
> > --credential
> >
> M1p2PrsPSW6i9mdl1XwQyKBGoX6GdDBo6_y5SVl15h02K1xC6pj2eRMGLWGgehqD9fiCeY
> Lfh3kWqUJCx1AZ2g
> > --hardwareId b73f6946-f4a7-4181-b308-29f17a772700 --imageId
> > 293cf203-88f2-486f-b85b-188ab305b9b7 fabric
> >
> > identity = apikey of admin
> > credential = secretkey of admin
> > hardwareid = tinyOffering (500MH, 500MB Ram, Local Storage) imageId
> > = CentOS 5.3 proposed by default (= tiny Linux Offering)
> >
> > Failed to create nodes:error running 1 node group(fabric)
> > location(ee6fff52-4dc4-42c6-864d-663a9a7de333)
> > image(293cf203-88f2-486f-b85b-188ab305b9b7)
> > size(b73f6946-f4a7-4181-b308-29f17a772700) options({}) Execution
> > failures:
> >
> > 1) ExecutionException on fabric-1:
> > java.util.concurrent.ExecutionException:
> > org.jclouds.cloudstack.AsyncJobException: job
> > AsyncJob{accountId=88662cb2-7f68-4795-be14-6360c4b224b8,
> > cmd=com.cloud.api.commands.DeployVMCmd, created=Fri Dec 07 16:05:41
> > CET 2012, id=52e74850-214e-4575-b5dd-1a71cc72b771, instanceId=null,
> > instanceType=null, progress=0, result=null, resultCode=FAIL,
> > resultType=object, status=FAILED,
> > userId=e5fa31c0-43f2-41a5-b9d5-c11d8a45180b,
> > error=AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR,
> errorText=Unable
> > to create a deployment for VM[User|fabric-1]}} failed with exception
> > AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR,
> > errorText=Unable to create a deployment for VM[User|fabric-1]} at
> >
> com.google.common.util.concurrent.AbstractFuture$Sync.getValue(Abstrac
> tFuture.java:294)
> > at
> >
> com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFutu
> re.java:281)
> > at
> >
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.ja
> va:116)
> > at
> > org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:13
> > 8)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
> ava:1110)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:603)
> > at java.lang.Thread.run(Thread.java:722)
> >
> > Here is the config of an instance created successfully through the
> > web interface
> >
> > Hypervisor : XenServer
> > Template : tiny Linux
> > OS Type : CentOS 5.3 (64-bit)
> > Attached ISO :
> > Compute offering : tinyOffering2
> > HA Enabled : No
> > Group :
> > Zone name : DevCloud0
> > Host : devcloud
> > Domain : ROOT
> > Account : admin
> > Created : 07 Dec 2012 14:23:37
> > ID : b860d1c3-4416-4ab5-8233-bd3d1c92064f
> >
> > And the config using the command but reporting incapacity error
> >
> >
> > Hypervisor : XenServer
> > Template : tiny Linux
> > OS Type : CentOS 5.3 (64-bit)
> > Attached ISO :
> > Compute offering : tinyOffering2
> > HA Enabled : No
> > Group :
> > Zone name : DevCloud0
> > Host :
> > Domain : ROOT
> > Account : admin
> > Created : 07 Dec 2012 15:17:32
> > ID : ca75b67e-cb30-4c43-9cc3-4dc05b867470
> >
> > If I compare what is created using command line and through the web
> > interface, the only difference is that host is not defined using
> > command
> >
> > Somebody can tell me why we have a different response from
> > cloudstack if
> we
> > use command line vs web interface ?
> >
> > Regards,
> >
> >
> >
> > --
> > Charles Moulliard
> > Apache Committer / Sr. Enterprise Architect (RedHat) Twitter :
> > @cmoulliard | Blog : http://cmoulliard.blogspot.com
>
>
--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Cloudstack - jclouds
Posted by Charles Moulliard <ch...@gmail.com>.
Do you have an example using cloudmonkey ?
On Fri, Dec 7, 2012 at 7:31 PM, Rohit Yadav <ro...@citrix.com> wrote:
> Not sure about jclouds api, can you try doing the same using cloudmonkey?
> If it does not work, probably it's a api bug.
>
> Regards.
>
> On 07-Dec-2012, at 7:20 AM, Charles Moulliard <ch...@gmail.com> wrote:
>
> > Hi,
> >
> > I use jclouds Java api to create a new instance. Using the web interface
> > with DevCloud2 running in VirtualBox and Apache CloudStack 4.1.0-SNAPSHOT
> > (management server), that works fine but when I tries to create it using
> > the following parameters and jclouds, I get an insufficient capacity
> error.
> >
> > jclouds:node-create --provider cloudstack --identity
> >
> 4LJ9B23kX5LswWnSHQDgjmQyXLXziyu1uxBc8GSXAzi3PrLXRbGT36D4oixxFAZGxiXPFJgXFcdC8EbFpSOdAA
> > --credential
> >
> M1p2PrsPSW6i9mdl1XwQyKBGoX6GdDBo6_y5SVl15h02K1xC6pj2eRMGLWGgehqD9fiCeYLfh3kWqUJCx1AZ2g
> > --hardwareId b73f6946-f4a7-4181-b308-29f17a772700 --imageId
> > 293cf203-88f2-486f-b85b-188ab305b9b7 fabric
> >
> > identity = apikey of admin
> > credential = secretkey of admin
> > hardwareid = tinyOffering (500MH, 500MB Ram, Local Storage)
> > imageId = CentOS 5.3 proposed by default (= tiny Linux Offering)
> >
> > Failed to create nodes:error running 1 node group(fabric)
> > location(ee6fff52-4dc4-42c6-864d-663a9a7de333)
> > image(293cf203-88f2-486f-b85b-188ab305b9b7)
> > size(b73f6946-f4a7-4181-b308-29f17a772700) options({})
> > Execution failures:
> >
> > 1) ExecutionException on fabric-1:
> > java.util.concurrent.ExecutionException:
> > org.jclouds.cloudstack.AsyncJobException: job
> > AsyncJob{accountId=88662cb2-7f68-4795-be14-6360c4b224b8,
> > cmd=com.cloud.api.commands.DeployVMCmd, created=Fri Dec 07 16:05:41 CET
> > 2012, id=52e74850-214e-4575-b5dd-1a71cc72b771, instanceId=null,
> > instanceType=null, progress=0, result=null, resultCode=FAIL,
> > resultType=object, status=FAILED,
> > userId=e5fa31c0-43f2-41a5-b9d5-c11d8a45180b,
> > error=AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR,
> errorText=Unable
> > to create a deployment for VM[User|fabric-1]}} failed with exception
> > AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable to
> > create a deployment for VM[User|fabric-1]}
> > at
> >
> com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:294)
> > at
> >
> com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:281)
> > at
> >
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> > at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:138)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> > at java.lang.Thread.run(Thread.java:722)
> >
> > Here is the config of an instance created successfully through the web
> > interface
> >
> > Hypervisor : XenServer
> > Template : tiny Linux
> > OS Type : CentOS 5.3 (64-bit)
> > Attached ISO :
> > Compute offering : tinyOffering2
> > HA Enabled : No
> > Group :
> > Zone name : DevCloud0
> > Host : devcloud
> > Domain : ROOT
> > Account : admin
> > Created : 07 Dec 2012 14:23:37
> > ID : b860d1c3-4416-4ab5-8233-bd3d1c92064f
> >
> > And the config using the command but reporting incapacity error
> >
> >
> > Hypervisor : XenServer
> > Template : tiny Linux
> > OS Type : CentOS 5.3 (64-bit)
> > Attached ISO :
> > Compute offering : tinyOffering2
> > HA Enabled : No
> > Group :
> > Zone name : DevCloud0
> > Host :
> > Domain : ROOT
> > Account : admin
> > Created : 07 Dec 2012 15:17:32
> > ID : ca75b67e-cb30-4c43-9cc3-4dc05b867470
> >
> > If I compare what is created using command line and through the web
> > interface, the only difference is that host is not defined using command
> >
> > Somebody can tell me why we have a different response from cloudstack if
> we
> > use command line vs web interface ?
> >
> > Regards,
> >
> >
> >
> > --
> > Charles Moulliard
> > Apache Committer / Sr. Enterprise Architect (RedHat)
> > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>
>
--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Cloudstack - jclouds
Posted by Rohit Yadav <ro...@citrix.com>.
Not sure about jclouds api, can you try doing the same using cloudmonkey? If it does not work, probably it's a api bug.
Regards.
On 07-Dec-2012, at 7:20 AM, Charles Moulliard <ch...@gmail.com> wrote:
> Hi,
>
> I use jclouds Java api to create a new instance. Using the web interface
> with DevCloud2 running in VirtualBox and Apache CloudStack 4.1.0-SNAPSHOT
> (management server), that works fine but when I tries to create it using
> the following parameters and jclouds, I get an insufficient capacity error.
>
> jclouds:node-create --provider cloudstack --identity
> 4LJ9B23kX5LswWnSHQDgjmQyXLXziyu1uxBc8GSXAzi3PrLXRbGT36D4oixxFAZGxiXPFJgXFcdC8EbFpSOdAA
> --credential
> M1p2PrsPSW6i9mdl1XwQyKBGoX6GdDBo6_y5SVl15h02K1xC6pj2eRMGLWGgehqD9fiCeYLfh3kWqUJCx1AZ2g
> --hardwareId b73f6946-f4a7-4181-b308-29f17a772700 --imageId
> 293cf203-88f2-486f-b85b-188ab305b9b7 fabric
>
> identity = apikey of admin
> credential = secretkey of admin
> hardwareid = tinyOffering (500MH, 500MB Ram, Local Storage)
> imageId = CentOS 5.3 proposed by default (= tiny Linux Offering)
>
> Failed to create nodes:error running 1 node group(fabric)
> location(ee6fff52-4dc4-42c6-864d-663a9a7de333)
> image(293cf203-88f2-486f-b85b-188ab305b9b7)
> size(b73f6946-f4a7-4181-b308-29f17a772700) options({})
> Execution failures:
>
> 1) ExecutionException on fabric-1:
> java.util.concurrent.ExecutionException:
> org.jclouds.cloudstack.AsyncJobException: job
> AsyncJob{accountId=88662cb2-7f68-4795-be14-6360c4b224b8,
> cmd=com.cloud.api.commands.DeployVMCmd, created=Fri Dec 07 16:05:41 CET
> 2012, id=52e74850-214e-4575-b5dd-1a71cc72b771, instanceId=null,
> instanceType=null, progress=0, result=null, resultCode=FAIL,
> resultType=object, status=FAILED,
> userId=e5fa31c0-43f2-41a5-b9d5-c11d8a45180b,
> error=AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable
> to create a deployment for VM[User|fabric-1]}} failed with exception
> AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable to
> create a deployment for VM[User|fabric-1]}
> at
> com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:294)
> at
> com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:281)
> at
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
>
> Here is the config of an instance created successfully through the web
> interface
>
> Hypervisor : XenServer
> Template : tiny Linux
> OS Type : CentOS 5.3 (64-bit)
> Attached ISO :
> Compute offering : tinyOffering2
> HA Enabled : No
> Group :
> Zone name : DevCloud0
> Host : devcloud
> Domain : ROOT
> Account : admin
> Created : 07 Dec 2012 14:23:37
> ID : b860d1c3-4416-4ab5-8233-bd3d1c92064f
>
> And the config using the command but reporting incapacity error
>
>
> Hypervisor : XenServer
> Template : tiny Linux
> OS Type : CentOS 5.3 (64-bit)
> Attached ISO :
> Compute offering : tinyOffering2
> HA Enabled : No
> Group :
> Zone name : DevCloud0
> Host :
> Domain : ROOT
> Account : admin
> Created : 07 Dec 2012 15:17:32
> ID : ca75b67e-cb30-4c43-9cc3-4dc05b867470
>
> If I compare what is created using command line and through the web
> interface, the only difference is that host is not defined using command
>
> Somebody can tell me why we have a different response from cloudstack if we
> use command line vs web interface ?
>
> Regards,
>
>
>
> --
> Charles Moulliard
> Apache Committer / Sr. Enterprise Architect (RedHat)
> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Cloudstack - jclouds
Posted by Rohit Yadav <ro...@citrix.com>.
Not sure about jclouds api, can you try doing the same using cloudmonkey? If it does not work, probably it's a api bug.
Regards.
On 07-Dec-2012, at 7:20 AM, Charles Moulliard <ch...@gmail.com> wrote:
> Hi,
>
> I use jclouds Java api to create a new instance. Using the web interface
> with DevCloud2 running in VirtualBox and Apache CloudStack 4.1.0-SNAPSHOT
> (management server), that works fine but when I tries to create it using
> the following parameters and jclouds, I get an insufficient capacity error.
>
> jclouds:node-create --provider cloudstack --identity
> 4LJ9B23kX5LswWnSHQDgjmQyXLXziyu1uxBc8GSXAzi3PrLXRbGT36D4oixxFAZGxiXPFJgXFcdC8EbFpSOdAA
> --credential
> M1p2PrsPSW6i9mdl1XwQyKBGoX6GdDBo6_y5SVl15h02K1xC6pj2eRMGLWGgehqD9fiCeYLfh3kWqUJCx1AZ2g
> --hardwareId b73f6946-f4a7-4181-b308-29f17a772700 --imageId
> 293cf203-88f2-486f-b85b-188ab305b9b7 fabric
>
> identity = apikey of admin
> credential = secretkey of admin
> hardwareid = tinyOffering (500MH, 500MB Ram, Local Storage)
> imageId = CentOS 5.3 proposed by default (= tiny Linux Offering)
>
> Failed to create nodes:error running 1 node group(fabric)
> location(ee6fff52-4dc4-42c6-864d-663a9a7de333)
> image(293cf203-88f2-486f-b85b-188ab305b9b7)
> size(b73f6946-f4a7-4181-b308-29f17a772700) options({})
> Execution failures:
>
> 1) ExecutionException on fabric-1:
> java.util.concurrent.ExecutionException:
> org.jclouds.cloudstack.AsyncJobException: job
> AsyncJob{accountId=88662cb2-7f68-4795-be14-6360c4b224b8,
> cmd=com.cloud.api.commands.DeployVMCmd, created=Fri Dec 07 16:05:41 CET
> 2012, id=52e74850-214e-4575-b5dd-1a71cc72b771, instanceId=null,
> instanceType=null, progress=0, result=null, resultCode=FAIL,
> resultType=object, status=FAILED,
> userId=e5fa31c0-43f2-41a5-b9d5-c11d8a45180b,
> error=AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable
> to create a deployment for VM[User|fabric-1]}} failed with exception
> AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable to
> create a deployment for VM[User|fabric-1]}
> at
> com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:294)
> at
> com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:281)
> at
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
>
> Here is the config of an instance created successfully through the web
> interface
>
> Hypervisor : XenServer
> Template : tiny Linux
> OS Type : CentOS 5.3 (64-bit)
> Attached ISO :
> Compute offering : tinyOffering2
> HA Enabled : No
> Group :
> Zone name : DevCloud0
> Host : devcloud
> Domain : ROOT
> Account : admin
> Created : 07 Dec 2012 14:23:37
> ID : b860d1c3-4416-4ab5-8233-bd3d1c92064f
>
> And the config using the command but reporting incapacity error
>
>
> Hypervisor : XenServer
> Template : tiny Linux
> OS Type : CentOS 5.3 (64-bit)
> Attached ISO :
> Compute offering : tinyOffering2
> HA Enabled : No
> Group :
> Zone name : DevCloud0
> Host :
> Domain : ROOT
> Account : admin
> Created : 07 Dec 2012 15:17:32
> ID : ca75b67e-cb30-4c43-9cc3-4dc05b867470
>
> If I compare what is created using command line and through the web
> interface, the only difference is that host is not defined using command
>
> Somebody can tell me why we have a different response from cloudstack if we
> use command line vs web interface ?
>
> Regards,
>
>
>
> --
> Charles Moulliard
> Apache Committer / Sr. Enterprise Architect (RedHat)
> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Cloudstack - jclouds
Posted by Charles Moulliard <ch...@gmail.com>.
As jclouds is used here with karaf, the info that I copy / paste comes from
Karaf log. So I don't have more info.
On Mon, Dec 10, 2012 at 5:46 AM, Anshul Gangwar
<an...@citrix.com>wrote:
> Hi Charles,
> Can you send jclouds-wire and management server logs?
> Thanks,
> Anshul
> On 07/12/12 20:50, Charles Moulliard wrote:
> > Hi,
> >
> > I use jclouds Java api to create a new instance. Using the web interface
> > with DevCloud2 running in VirtualBox and Apache CloudStack 4.1.0-SNAPSHOT
> > (management server), that works fine but when I tries to create it using
> > the following parameters and jclouds, I get an insufficient capacity
> error.
> >
> > jclouds:node-create --provider cloudstack --identity
> >
> 4LJ9B23kX5LswWnSHQDgjmQyXLXziyu1uxBc8GSXAzi3PrLXRbGT36D4oixxFAZGxiXPFJgXFcdC8EbFpSOdAA
> > --credential
> >
> M1p2PrsPSW6i9mdl1XwQyKBGoX6GdDBo6_y5SVl15h02K1xC6pj2eRMGLWGgehqD9fiCeYLfh3kWqUJCx1AZ2g
> > --hardwareId b73f6946-f4a7-4181-b308-29f17a772700 --imageId
> > 293cf203-88f2-486f-b85b-188ab305b9b7 fabric
> >
> > identity = apikey of admin
> > credential = secretkey of admin
> > hardwareid = tinyOffering (500MH, 500MB Ram, Local Storage)
> > imageId = CentOS 5.3 proposed by default (= tiny Linux Offering)
> >
> > Failed to create nodes:error running 1 node group(fabric)
> > location(ee6fff52-4dc4-42c6-864d-663a9a7de333)
> > image(293cf203-88f2-486f-b85b-188ab305b9b7)
> > size(b73f6946-f4a7-4181-b308-29f17a772700) options({})
> > Execution failures:
> >
> > 1) ExecutionException on fabric-1:
> > java.util.concurrent.ExecutionException:
> > org.jclouds.cloudstack.AsyncJobException: job
> > AsyncJob{accountId=88662cb2-7f68-4795-be14-6360c4b224b8,
> > cmd=com.cloud.api.commands.DeployVMCmd, created=Fri Dec 07 16:05:41 CET
> > 2012, id=52e74850-214e-4575-b5dd-1a71cc72b771, instanceId=null,
> > instanceType=null, progress=0, result=null, resultCode=FAIL,
> > resultType=object, status=FAILED,
> > userId=e5fa31c0-43f2-41a5-b9d5-c11d8a45180b,
> > error=AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR,
> errorText=Unable
> > to create a deployment for VM[User|fabric-1]}} failed with exception
> > AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable to
> > create a deployment for VM[User|fabric-1]}
> > at
> >
> com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:294)
> > at
> >
> com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:281)
> > at
> >
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> > at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:138)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> > at java.lang.Thread.run(Thread.java:722)
> >
> > Here is the config of an instance created successfully through the web
> > interface
> >
> > Hypervisor : XenServer
> > Template : tiny Linux
> > OS Type : CentOS 5.3 (64-bit)
> > Attached ISO :
> > Compute offering : tinyOffering2
> > HA Enabled : No
> > Group :
> > Zone name : DevCloud0
> > Host : devcloud
> > Domain : ROOT
> > Account : admin
> > Created : 07 Dec 2012 14:23:37
> > ID : b860d1c3-4416-4ab5-8233-bd3d1c92064f
> >
> > And the config using the command but reporting incapacity error
> >
> >
> > Hypervisor : XenServer
> > Template : tiny Linux
> > OS Type : CentOS 5.3 (64-bit)
> > Attached ISO :
> > Compute offering : tinyOffering2
> > HA Enabled : No
> > Group :
> > Zone name : DevCloud0
> > Host :
> > Domain : ROOT
> > Account : admin
> > Created : 07 Dec 2012 15:17:32
> > ID : ca75b67e-cb30-4c43-9cc3-4dc05b867470
> >
> > If I compare what is created using command line and through the web
> > interface, the only difference is that host is not defined using command
> >
> > Somebody can tell me why we have a different response from cloudstack if
> we
> > use command line vs web interface ?
> >
> > Regards,
> >
> >
> >
>
--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Cloudstack - jclouds
Posted by Anshul Gangwar <an...@citrix.com>.
Hi Charles,
Can you send jclouds-wire and management server logs?
Thanks,
Anshul
On 07/12/12 20:50, Charles Moulliard wrote:
> Hi,
>
> I use jclouds Java api to create a new instance. Using the web interface
> with DevCloud2 running in VirtualBox and Apache CloudStack 4.1.0-SNAPSHOT
> (management server), that works fine but when I tries to create it using
> the following parameters and jclouds, I get an insufficient capacity error.
>
> jclouds:node-create --provider cloudstack --identity
> 4LJ9B23kX5LswWnSHQDgjmQyXLXziyu1uxBc8GSXAzi3PrLXRbGT36D4oixxFAZGxiXPFJgXFcdC8EbFpSOdAA
> --credential
> M1p2PrsPSW6i9mdl1XwQyKBGoX6GdDBo6_y5SVl15h02K1xC6pj2eRMGLWGgehqD9fiCeYLfh3kWqUJCx1AZ2g
> --hardwareId b73f6946-f4a7-4181-b308-29f17a772700 --imageId
> 293cf203-88f2-486f-b85b-188ab305b9b7 fabric
>
> identity = apikey of admin
> credential = secretkey of admin
> hardwareid = tinyOffering (500MH, 500MB Ram, Local Storage)
> imageId = CentOS 5.3 proposed by default (= tiny Linux Offering)
>
> Failed to create nodes:error running 1 node group(fabric)
> location(ee6fff52-4dc4-42c6-864d-663a9a7de333)
> image(293cf203-88f2-486f-b85b-188ab305b9b7)
> size(b73f6946-f4a7-4181-b308-29f17a772700) options({})
> Execution failures:
>
> 1) ExecutionException on fabric-1:
> java.util.concurrent.ExecutionException:
> org.jclouds.cloudstack.AsyncJobException: job
> AsyncJob{accountId=88662cb2-7f68-4795-be14-6360c4b224b8,
> cmd=com.cloud.api.commands.DeployVMCmd, created=Fri Dec 07 16:05:41 CET
> 2012, id=52e74850-214e-4575-b5dd-1a71cc72b771, instanceId=null,
> instanceType=null, progress=0, result=null, resultCode=FAIL,
> resultType=object, status=FAILED,
> userId=e5fa31c0-43f2-41a5-b9d5-c11d8a45180b,
> error=AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable
> to create a deployment for VM[User|fabric-1]}} failed with exception
> AsyncJobError{errorCode=INSUFFICIENT_CAPACITY_ERROR, errorText=Unable to
> create a deployment for VM[User|fabric-1]}
> at
> com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:294)
> at
> com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:281)
> at
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
>
> Here is the config of an instance created successfully through the web
> interface
>
> Hypervisor : XenServer
> Template : tiny Linux
> OS Type : CentOS 5.3 (64-bit)
> Attached ISO :
> Compute offering : tinyOffering2
> HA Enabled : No
> Group :
> Zone name : DevCloud0
> Host : devcloud
> Domain : ROOT
> Account : admin
> Created : 07 Dec 2012 14:23:37
> ID : b860d1c3-4416-4ab5-8233-bd3d1c92064f
>
> And the config using the command but reporting incapacity error
>
>
> Hypervisor : XenServer
> Template : tiny Linux
> OS Type : CentOS 5.3 (64-bit)
> Attached ISO :
> Compute offering : tinyOffering2
> HA Enabled : No
> Group :
> Zone name : DevCloud0
> Host :
> Domain : ROOT
> Account : admin
> Created : 07 Dec 2012 15:17:32
> ID : ca75b67e-cb30-4c43-9cc3-4dc05b867470
>
> If I compare what is created using command line and through the web
> interface, the only difference is that host is not defined using command
>
> Somebody can tell me why we have a different response from cloudstack if we
> use command line vs web interface ?
>
> Regards,
>
>
>