Re: RE: cloudstack 4.3.2 + xenserver 6.2 with all patchs,couldn't start system vm

[Pierre-Luc Dion]

4 scripts need to be recopy on all XenServer that have been patches. [1]
section 5.4

[1]
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/hypervisor/xenserver.html#upgrading-xenserver-versions

PL


On Wed, Dec 31, 2014 at 3:09 PM, Somesh Naidu 
wrote:

> Could you try restarting CS or unmange/mange the XS cluster to see if that
> fixes the issue.
>
> As an aside, one bad thing about this error is that most times it doesn’t
> explicitly say why the zone is not ready so we have to deduce. Following
> are few of the reasons why this could happen:
> 1. Storage is not ready
> 2. System VM template/ISO is not ready
> 3. Run out of IP (generally public)
>
> You might want to verify these. Try to look deeper in the logs to get a
> hint of what resource is causing the zone to be in this state.
>
> -Original Message-
> From: linux...@gmail.com [mailto:linux...@gmail.com]
> Sent: Tuesday, December 30, 2014 8:42 PM
> To: users@cloudstack.apache.org
> Subject: Re: RE: cloudstack 4.3.2 + xenserver 6.2 with all patchs,couldn't
> start system vm
>
> 1、we install xenserver 6.2 with no patch
> 2、we install cloudstack and the ssvm cpvm could running
> 3、we disable the zone,remove ssvm and cpvm
> 4、we install all the patchs of xenserver
> 5、after patched xenserver we enable the zone on cloudstack
>
> at this time,the log told us
>
> Zone 1 is not ready to launch console
> proxy yet
>
> 2014-12-30 23:54 GMT+08:00 Matthew Midgett
> :
> > Did you patch before or after installing cloudstack? I think some of
> files that acs puts on the hypervisors get overwritten. I saw someone
> talking about this on the mailing list before. I'm mobile today so can't
> provide the files and directories to be updated.
> >
> >  Original message From:
> linux...@gmail.com Date:12/30/2014  4:43 AM  (GMT-05:00)
> To: users@cloudstack.apache.org Subject: cloudstack
> 4.3.2 + xenserver 6.2 with all patchs,couldn't start
> >   system vm 
> > Hey ALL:
> >
> >we are testing cloustack 4.3.2 .our hypervisior is xenserver
> > 6.2 with all patchs
> > the system vm template is
> >
> http://download.cloud.com/templates/4.3/systemvm64template-2014-09-30-4.3-xen.vhd.bz2
> >
> > we have tryed basic network and advanced network
> >
> > when xenserver 6.2 is not patched ,it worked fine
> >
> > after we patched xenserver 6.2 with all patch,the systemvm couldn't
> running
> >
> > this is the log of management :
> >
> >
> >
> > 2014-12-30 17:17:47,512 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-28:ctx-52719350) Seq 4-417988800: Executing request
> >
> > 2014-12-30 17:17:47,722 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-28:ctx-52719350) Seq 4-417988800: Response Received:
> >
> > 2014-12-30 17:17:47,722 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
> > (DirectAgent-28:ctx-52719350) Seq 4-417988800: MgmtId 345051527296:
> > Resp: Routing to peer
> >
> > 2014-12-30 17:17:58,813 DEBUG
> > [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:ctx-b73976d7) Found 0 routers to update status.
> >
> > 2014-12-30 17:17:58,814 DEBUG
> > [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:ctx-b73976d7) Found 0 networks to update RvR
> > status.
> >
> > 2014-12-30 17:18:08,433 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-246:ctx-0222d7ab) Ping from 4(xenserver-101)
> >
> > 2014-12-30 17:18:08,820 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-143:ctx-3ae568b1) Seq 4-1243152388: Executing request
> >
> > 2014-12-30 17:18:09,008 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-143:ctx-3ae568b1) Seq 4-1243152388: Response Received:
> >
> > 2014-12-30 17:18:09,009 DEBUG [c.c.a.t.Request]
> > (DirectAgent-143:ctx-3ae568b1) Seq 4-1243152388: Processing:  { Ans: ,
> > MgmtId: 345051527295, via: 4, Ver: v1, Flags: 10,
> >
> [{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
> > }
> >
> > 2014-12-30 17:18:14,378 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> > (consoleproxy-1:ctx-04c0e3de) Zone 1 is not ready to launch console
> > proxy yet
> >
> > 2014-12-30 17:18:14,758 DEBUG [c.c.s.StatsCollector]
> > (StatsCollector-2:ctx-5f9e7528) VmStatsCollector is running...
> >
> > 2014-12-30 17:18:28,813 DEBUG
> > [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:ctx-2da8a4a0) Found 0 routers to update status.
> >
> > 2014-12-30 17:18:28,814 DEBUG
> > [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:ctx-2da8a4a0) Found 0 networks to update RvR
> > status.
> >
> > 2014-12-30 17:18:31,605 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-247:ctx-2929f84f) Seq 4-417988801: Executing request
> >
> > 2014-12-30 17:18:31,758 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-247:ctx-2929f84f) Seq 4-417988801: Response Received:
> >
> > 2014-12-30 17:18:31,759 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
> > (DirectAgent-247:ctx-2929f84f) Seq 4-417988801: MgmtId 34505152729

RE: RE: cloudstack 4.3.2 + xenserver 6.2 with all patchs,couldn't start system vm

[Somesh Naidu]

Could you try restarting CS or unmange/mange the XS cluster to see if that 
fixes the issue.

As an aside, one bad thing about this error is that most times it doesn’t 
explicitly say why the zone is not ready so we have to deduce. Following are 
few of the reasons why this could happen:
1. Storage is not ready
2. System VM template/ISO is not ready
3. Run out of IP (generally public)

You might want to verify these. Try to look deeper in the logs to get a hint of 
what resource is causing the zone to be in this state.

-Original Message-
From: linux...@gmail.com [mailto:linux...@gmail.com] 
Sent: Tuesday, December 30, 2014 8:42 PM
To: users@cloudstack.apache.org
Subject: Re: RE: cloudstack 4.3.2 + xenserver 6.2 with all patchs,couldn't 
start system vm

1、we install xenserver 6.2 with no patch
2、we install cloudstack and the ssvm cpvm could running
3、we disable the zone,remove ssvm and cpvm
4、we install all the patchs of xenserver
5、after patched xenserver we enable the zone on cloudstack

at this time,the log told us

Zone 1 is not ready to launch console
proxy yet

2014-12-30 23:54 GMT+08:00 Matthew Midgett
:
> Did you patch before or after installing cloudstack? I think some of files 
> that acs puts on the hypervisors get overwritten. I saw someone talking about 
> this on the mailing list before. I'm mobile today so can't provide the files 
> and directories to be updated.
>
>  Original message From: linux...@gmail.com 
> Date:12/30/2014  4:43 AM  (GMT-05:00) To: 
> users@cloudstack.apache.org Subject: cloudstack 4.3.2 + xenserver 
> 6.2 with all patchs,couldn't start
>   system vm 
> Hey ALL:
>
>we are testing cloustack 4.3.2 .our hypervisior is xenserver
> 6.2 with all patchs
> the system vm template is
> http://download.cloud.com/templates/4.3/systemvm64template-2014-09-30-4.3-xen.vhd.bz2
>
> we have tryed basic network and advanced network
>
> when xenserver 6.2 is not patched ,it worked fine
>
> after we patched xenserver 6.2 with all patch,the systemvm couldn't running
>
> this is the log of management :
>
>
>
> 2014-12-30 17:17:47,512 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-28:ctx-52719350) Seq 4-417988800: Executing request
>
> 2014-12-30 17:17:47,722 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-28:ctx-52719350) Seq 4-417988800: Response Received:
>
> 2014-12-30 17:17:47,722 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
> (DirectAgent-28:ctx-52719350) Seq 4-417988800: MgmtId 345051527296:
> Resp: Routing to peer
>
> 2014-12-30 17:17:58,813 DEBUG
> [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-b73976d7) Found 0 routers to update status.
>
> 2014-12-30 17:17:58,814 DEBUG
> [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-b73976d7) Found 0 networks to update RvR
> status.
>
> 2014-12-30 17:18:08,433 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-246:ctx-0222d7ab) Ping from 4(xenserver-101)
>
> 2014-12-30 17:18:08,820 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-143:ctx-3ae568b1) Seq 4-1243152388: Executing request
>
> 2014-12-30 17:18:09,008 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-143:ctx-3ae568b1) Seq 4-1243152388: Response Received:
>
> 2014-12-30 17:18:09,009 DEBUG [c.c.a.t.Request]
> (DirectAgent-143:ctx-3ae568b1) Seq 4-1243152388: Processing:  { Ans: ,
> MgmtId: 345051527295, via: 4, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
> }
>
> 2014-12-30 17:18:14,378 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> (consoleproxy-1:ctx-04c0e3de) Zone 1 is not ready to launch console
> proxy yet
>
> 2014-12-30 17:18:14,758 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-2:ctx-5f9e7528) VmStatsCollector is running...
>
> 2014-12-30 17:18:28,813 DEBUG
> [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-2da8a4a0) Found 0 routers to update status.
>
> 2014-12-30 17:18:28,814 DEBUG
> [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-2da8a4a0) Found 0 networks to update RvR
> status.
>
> 2014-12-30 17:18:31,605 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-247:ctx-2929f84f) Seq 4-417988801: Executing request
>
> 2014-12-30 17:18:31,758 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-247:ctx-2929f84f) Seq 4-417988801: Response Received:
>
> 2014-12-30 17:18:31,759 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
> (DirectAgent-247:ctx-2929f84f) Seq 4-417988801: MgmtId 345051527296:
> Resp: Routing to peer
>
> 2014-12-30 17:18:33,902 DEBUG [c.c.h.d.HostDaoImpl]
> (ClusteredAgentManager Timer:ctx-29831b59) Resetting hosts suitable
> for reconnect
>
> 2014-12-30 17:18:33,903 DEBUG [c.c.h.d.HostDaoImpl]
> (ClusteredAgentManager Timer:ctx-29831b59) Completed resetting hosts
> suitable for reconnect
>
> 2014-12-30 17:18:33,903 DEBUG [c.c.h.d.HostDaoImpl]
> (ClusteredAgentManager Timer:ctx-29831b59) Acquiring hosts for
> clusters already owned by this management server
>

RE: Unable to start VM due to concurrent operation

[Somesh Naidu]

You mean the system VMs for Zone 1 are running? Are they showing as connected 
in the DB?

If they are, can you stop these VMs and see if they start okay.

From: Mohamed Infaz [infaz...@cse.mrt.ac.lk]
Sent: Tuesday, December 30, 2014 21:26
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: Unable to start VM due to concurrent operation

systemvm64template-2014-01-14-master-kvm.qcow2.bz2 This is the template i used.


On 31 December 2014 at 07:49, Mohamed Infaz  wrote:

> Hi Somesh,
>
> Thank you for the reply. Well both of my system vm's are running and it is
> downloading the iso image. And i was able to ping them. The system vm
> template i am using is for the version 4.3 cloudstack.
>
> Thank you.
>
> On 30 December 2014 at 23:59, Somesh Naidu 
> wrote:
>
>> Mohamed,
>>
>> The log snippet you have shared doesn't seem to be relevant to the
>> concurrent operation exception (can't see that exception stack).
>>
>> The message that did catch my attention though is,
>> -
>> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
>> (secstorage-1:ctx-463d2f57) System vm template is not ready at data center
>> 1, wait until it is ready to launch secondary storage vm
>> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
>> (secstorage-1:ctx-463d2f57) Zone 1 is not ready to launch secondary storage
>> VM yet
>> -
>>
>> That's pointing to missing system VM template. Please verify that you
>> have correctly provisioned the secondary storage with the correct system VM
>> template (as per the docs).
>>
>> -Somesh
>>
>> -Original Message-
>> From: Mohamed Infaz [mailto:infaz...@cse.mrt.ac.lk]
>> Sent: Tuesday, December 30, 2014 11:03 AM
>> To: users@cloudstack.apache.org
>> Cc: d...@cloudstack.apache.org
>> Subject: Unable to start VM due to concurrent operation
>>
>> Hi All,
>>
>> I have successfully deployed cloudstack 4.3 with two hosts and the setup
>> runs the management server on another physical host. I had issues with
>> downloading an ISO but finally i was able to download an ISO image. When i
>> want to create an instance i get the following error message saying
>> "Unable
>> to start VM due to concurrent operation" i did some searching on the topic
>> and it said version 4.3 system template solved the issue. These are some
>> of
>> the MS logs that i collected what could be the issue?
>>
>> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
>> (secstorage-1:ctx-463d2f57) System vm template is not ready at data center
>> 1, wait until it is ready to launch secondary storage vm
>> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
>> (secstorage-1:ctx-463d2f57) Zone 1 is not ready to launch secondary
>> storage
>> VM yet
>> 2014-12-31 05:25:12,425 DEBUG [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-9:null) Ping from 4
>> 2014-12-31 05:25:12,834 DEBUG [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-5:null) SeqA 3-91695: Processing Seq 3-91695:  { Cmd
>> , MgmtId: -1, via: 3, Ver: v1, Flags: 11,
>>
>> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n
>> \"connections\": []\n}","wait":0}}] }
>> 2014-12-31 05:25:12,920 DEBUG [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-5:null) SeqA 3-91695: Sending Seq 3-91695:  { Ans: ,
>> MgmtId: 248795600505608, via: 3, Ver: v1, Flags: 100010,
>> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
>> 2014-12-31 05:25:15,239 DEBUG [c.c.n.ExternalDeviceUsageManagerImpl]
>> (ExternalNetworkMonitor-1:ctx-998a86df) External devices stats collector
>> is
>> running...
>> 2014-12-31 05:25:15,362 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
>> (RouterMonitor-1:ctx-dfdc73ce) Found 0 running routers.
>> 2014-12-31 05:25:15,366 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
>> (RouterStatusMonitor-1:ctx-79d58896) Found 0 routers to update status.
>> 2014-12-31 05:25:15,367 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
>> (RouterStatusMonitor-1:ctx-79d58896) Found 0 networks to update RvR
>> status.
>> 2014-12-31 05:25:15,393 DEBUG [c.c.s.s.SnapshotSchedulerImpl]
>> (SnapshotPollTask:ctx-ae761f6b) Snapshot scheduler.poll is being called at
>> 2014-12-30 23:55:15 GMT
>> 2014-12-31 05:25:15,393 DEBUG [c.c.s.s.SnapshotSchedulerImpl]
>> (SnapshotPollTask:ctx-ae761f6b) Got 0 snapshots to be executed at
>> 2014-12-30 23:55:15 GMT
>> 2014-12-31 05:25:18,535 DEBUG [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-14:null) Ping from 3
>> 2014-12-31 05:25:18,698 DEBUG [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-10:null) Ping from 2
>> 2014-12-31 05:25:19,834 INFO  [c.c.a.m.AgentManagerImpl]
>> (AgentMonitor-1:ctx-f10d32f0) Found the following agents behind on ping:
>> [1]
>> 2014-12-31 05:25:19,835 DEBUG [c.c.h.Status] (AgentMonitor-1:ctx-f10d32f0)
>> Ping timeout for host 1, do invstigation
>> 2014-12-31 05:25:19,837 INFO  [c.c.a.m.AgentManagerImpl]
>> (AgentTaskPoo

RE: CPU socket miss match !!! Urgent

[Kevin McCormick]

I believe this is an issue with NUMA. I think this is only a display issue and 
not actually causing any capacity issues.

We have this output from virsh nodeinfo on two identical hosts:
CPU model:   x86_64
CPU(s):  16
CPU frequency:   1600 MHz
CPU socket(s):   2 <--
Core(s) per socket:  4
Thread(s) per core:  2
NUMA cell(s):1 <--
Memory size: 74225672 KiB

CPU model:   x86_64
CPU(s):  16
CPU frequency:   1600 MHz
CPU socket(s):   1 <--
Core(s) per socket:  4
Thread(s) per core:  2
NUMA cell(s):2 <--
Memory size: 74225528 KiB

The first host is configured with NUMA interleave mode in the system BIOS, 
which we've found as a better fit for our workload. That makes it appear as 
only a single NUMA cell with two sockets. The second system hasn't been set to 
interleave mode, and it's able to see both NUMA cells, each of which has a 
single CPU socket.

Note that in both cases the total number of CPUs is detected correctly, and I 
believe that number is what ACS uses for capacity planning.

Abdul, you may want to look into the cpu.overprovisioning.factor setting. This 
is at a cluster-level and affects how much CPU is reserved for an instance.




Kevin McCormick
Director of Cloud Services


Intrinium
Tel: (509) 465-1234 x7080
Fax: (866) 565-4578
Lync / Skype: kevin.mccorm...@intrinium.com
Web: www.intrinium.com
-Original Message-
From: Nux! [mailto:n...@li.nux.ro]
Sent: Wednesday, December 31, 2014 03:55
To: users@cloudstack.apache.org
Subject: Re: CPU socket miss match !!! Urgent

Yes, I'm also seeing this on DELL PE R720... It seems like a libvirt fail, try 
to submit a bug upstream (redhat bugzilla).

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Abdul Rasool" 
> To: users@cloudstack.apache.org
> Sent: Wednesday, 31 December, 2014 07:49:37
> Subject: Re: CPU socket miss match !!! Urgent

> Hi Harikrishna,
>
> Thanks for your reply
>
> Here is the command out put.
>
> root@cloud-node001:~# dmidecode -t 4 |grep Socket
> Socket Designation: CPU1
> Upgrade: Socket LGA2011
> Socket Designation: CPU2
> Upgrade: Socket LGA2011
>
>
> root@cloud-node001:~# virsh nodeinfo
> CPU model:   x86_64
> CPU(s):  8
> CPU frequency:   2500 MHz
> CPU socket(s):   1
> Core(s) per socket:  4
> Thread(s) per core:  1
> NUMA cell(s):2
> Memory size: 32899468 kB
>
> When I check using dmidecode I am getting actual CPU sockets =2 whereas
> libvirt is picking only one socket. please help me to fix this issue.
>
> Thanks
> AR
>
>
>
> On 31 December 2014 at 11:27, Harikrishna Patnala <
> harikrishna.patn...@citrix.com> wrote:
>
>> Hi,
>>
>> This seems to me like a libvirt issue on KVM.
>> We read the socket count from the parameter ‘sockets’ in NodeInfo on KVM
>> host.
>> Can you check with the command “virsh nodeinfo” ?
>>
>> Thanks,
>> Harikrishna
>>
>>
>> On 31-Dec-2014, at 9:54 am, Abdul Rasool > rasool...@gmail.com>> wrote:
>>
>> Attachment is missing ... added the same.
>>
>> On 31 December 2014 at 09:50, Abdul Rasool > rasool...@gmail.com>> wrote:
>> Hi,
>>
>> In my test / dev environment I have total 2 Dell Poweredge M620 blade
>> servers configured as KVM hypervisor each has physical CPU of 2 sockets,
>> total number of CPU sockets available in my setup is 4 sockets. but in ACS
>> infrastructure shows only 2 physical sockets. for your reference I have
>> attached my infrastructure screenshot.
>>
>> could you please some one help me why ACS is showing only 2 CPU sockets
>> instead of 4 ? is there any configuration issue from my side. ? right now
>> this environment is used for our internal development purpose due to CPU
>> mismatch I am not able to add additional guest VM in my infrastructure it
>> is throwing me insufficient resources...!
>>
>> [Inline images 1]
>>
>> Regards,
>> AR
>>
>>
>>


This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.

RE: Can't create or deploy VMs

[Somesh Naidu]

> 2014-12-31 07:49:44,405 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
> (Job-Executor-22:ctx-f2bc1611 ctx-77cccfb5) No suitable pools found
> 2014-12-31 07:49:44,405 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
> (Job-Executor-22:ctx-f2bc1611 ctx-77cccfb5) No suitable storagePools found 
> under this Cluster: 1
> 2014-12-31 07:49:44,407 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
> (Job-Executor-22:ctx-f2bc1611 ctx-77cccfb5) Could not find suitable 
> Deployment Destination for this VM under any clusters, returning.

Apparently, you only have 1 cluster in Zone 1 where the VM is being deployed 
and the storage on that one is full. You need to provision more space.

-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com] 
Sent: Wednesday, December 31, 2014 8:18 AM
To: users@cloudstack.apache.org
Subject: Re: Can't create or deploy VMs

The log on mgmt is:

***
2014-12-31 07:49:44,138 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-de733770) 
===START===  172.30.1.107 -- GET  
command=deployVirtualMachine&response=json&sessionkey=ExqHTfNe1JVXnQXRkEpgjMoDqu0%3D&zoneid=80b7c240-9204-43eb-85c8-762c7d7f6a15&templateid=449e3489-292e-4888-9682-d57d58a0ea1a&hypervisor=VMware&serviceofferingid=a6e438f6-afce-4388-9498-78cf2525cac2&diskofferingid=3df3bee2-bdee-4b80-9a0b-5ef039c5194c&displayname=test&name=test&_=1420030300055
2014-12-31 07:49:44,150 DEBUG [c.c.a.ApiDispatcher] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) InfrastructureEntity name 
is:com.cloud.offering.ServiceOffering
2014-12-31 07:49:44,153 DEBUG [c.c.a.ApiDispatcher] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) ControlledEntity name 
is:com.cloud.template.VirtualMachineTemplate
2014-12-31 07:49:44,158 DEBUG [c.c.a.ApiDispatcher] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) InfrastructureEntity name 
is:com.cloud.offering.DiskOffering
2014-12-31 07:49:44,190 DEBUG [c.c.v.UserVmManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating in the DB for vm
2014-12-31 07:49:44,219 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating entries for VM: 
VM[User|test]
2014-12-31 07:49:44,221 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating nics for VM[User|test]
2014-12-31 07:49:44,222 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating nic for vm VM[User|test] 
in network Ntwk[204|Guest|6] with requested profile 
NicProfile[0-0-null-null-null
2014-12-31 07:49:44,233 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating disks for VM[User|test]
2014-12-31 07:49:44,244 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocation completed for VM: 
VM[User|test]
2014-12-31 07:49:44,244 DEBUG [c.c.v.UserVmManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Successfully allocated DB entry for 
VM[User|test]
2014-12-31 07:49:44,296 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) submit async job-419, details: 
AsyncJobVO {id:419, userId: 2, accountId: 2, instanceType: VirtualMachine, 
instanceId: 47, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, 
cmdInfo: 
{"serviceofferingid":"a6e438f6-afce-4388-9498-78cf2525cac2","sessionkey":"ExqHTfNe1JVXnQXRkEpgjMoDqu0\u003d","cmdEventType":"VM.CREATE","ctxUserId":"2","zoneid":"80b7c240-9204-43eb-85c8-762c7d7f6a15","httpmethod":"GET","templateid":"449e3489-292e-4888-9682-d57d58a0ea1a","response":"json","id":"47","hypervisor":"VMware","name":"test","_":"1420030300055","ctxAccountId":"2","diskofferingid":"3df3bee2-bdee-4b80-9a0b-5ef039c5194c","ctxStartEventId":"1099","displayname":"test"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 345050676845, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-12-31 07:49:44,297 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(Job-Executor-22:ctx-f2bc1611) Add job-419 into job monitoring
2014-12-31 07:49:44,297 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-de733770 
ctx-77cccfb5) ===END===  172.30.1.107 -- GET  
command=deployVirtualMachine&response=json&sessionkey=ExqHTfNe1JVXnQXRkEpgjMoDqu0%3D&zoneid=80b7c240-9204-43eb-85c8-762c7d7f6a15&templateid=449e3489-292e-4888-9682-d57d58a0ea1a&hypervisor=VMware&serviceofferingid=a6e438f6-afce-4388-9498-78cf2525cac2&diskofferingid=3df3bee2-bdee-4b80-9a0b-5ef039c5194c&displayname=test&name=test&_=1420030300055
2014-12-31 07:49:44,297 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Job-Executor-22:ctx-f2bc1611) Executing AsyncJobVO {id:419, userId: 2, 
accountId: 2, instanceType: VirtualMachine, instanceId: 47, cmd: 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: 
{"serviceofferingid":"a6e438f6-afce-4388-9498-78cf2525cac2","sessionkey":"ExqHTfNe1JVXnQXRkEpgjMoDqu0\u003d","cmdEventType":"VM.CREATE","ctxUserId":"2","zoneid":"80b7c240-9204-43eb-85c8-762c7d7f6a15","httpmethod"

Re: Can't create or deploy VMs

[José Egas López]

The log on mgmt is:

***
2014-12-31 07:49:44,138 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-de733770) 
===START===  172.30.1.107 -- GET  
command=deployVirtualMachine&response=json&sessionkey=ExqHTfNe1JVXnQXRkEpgjMoDqu0%3D&zoneid=80b7c240-9204-43eb-85c8-762c7d7f6a15&templateid=449e3489-292e-4888-9682-d57d58a0ea1a&hypervisor=VMware&serviceofferingid=a6e438f6-afce-4388-9498-78cf2525cac2&diskofferingid=3df3bee2-bdee-4b80-9a0b-5ef039c5194c&displayname=test&name=test&_=1420030300055
2014-12-31 07:49:44,150 DEBUG [c.c.a.ApiDispatcher] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) InfrastructureEntity name 
is:com.cloud.offering.ServiceOffering
2014-12-31 07:49:44,153 DEBUG [c.c.a.ApiDispatcher] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) ControlledEntity name 
is:com.cloud.template.VirtualMachineTemplate
2014-12-31 07:49:44,158 DEBUG [c.c.a.ApiDispatcher] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) InfrastructureEntity name 
is:com.cloud.offering.DiskOffering
2014-12-31 07:49:44,190 DEBUG [c.c.v.UserVmManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating in the DB for vm
2014-12-31 07:49:44,219 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating entries for VM: 
VM[User|test]
2014-12-31 07:49:44,221 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating nics for VM[User|test]
2014-12-31 07:49:44,222 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating nic for vm VM[User|test] 
in network Ntwk[204|Guest|6] with requested profile 
NicProfile[0-0-null-null-null
2014-12-31 07:49:44,233 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocating disks for VM[User|test]
2014-12-31 07:49:44,244 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Allocation completed for VM: 
VM[User|test]
2014-12-31 07:49:44,244 DEBUG [c.c.v.UserVmManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) Successfully allocated DB entry for 
VM[User|test]
2014-12-31 07:49:44,296 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(catalina-exec-2:ctx-de733770 ctx-77cccfb5) submit async job-419, details: 
AsyncJobVO {id:419, userId: 2, accountId: 2, instanceType: VirtualMachine, 
instanceId: 47, cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd, 
cmdInfo: 
{"serviceofferingid":"a6e438f6-afce-4388-9498-78cf2525cac2","sessionkey":"ExqHTfNe1JVXnQXRkEpgjMoDqu0\u003d","cmdEventType":"VM.CREATE","ctxUserId":"2","zoneid":"80b7c240-9204-43eb-85c8-762c7d7f6a15","httpmethod":"GET","templateid":"449e3489-292e-4888-9682-d57d58a0ea1a","response":"json","id":"47","hypervisor":"VMware","name":"test","_":"1420030300055","ctxAccountId":"2","diskofferingid":"3df3bee2-bdee-4b80-9a0b-5ef039c5194c","ctxStartEventId":"1099","displayname":"test"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 345050676845, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-12-31 07:49:44,297 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(Job-Executor-22:ctx-f2bc1611) Add job-419 into job monitoring
2014-12-31 07:49:44,297 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-de733770 
ctx-77cccfb5) ===END===  172.30.1.107 -- GET  
command=deployVirtualMachine&response=json&sessionkey=ExqHTfNe1JVXnQXRkEpgjMoDqu0%3D&zoneid=80b7c240-9204-43eb-85c8-762c7d7f6a15&templateid=449e3489-292e-4888-9682-d57d58a0ea1a&hypervisor=VMware&serviceofferingid=a6e438f6-afce-4388-9498-78cf2525cac2&diskofferingid=3df3bee2-bdee-4b80-9a0b-5ef039c5194c&displayname=test&name=test&_=1420030300055
2014-12-31 07:49:44,297 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Job-Executor-22:ctx-f2bc1611) Executing AsyncJobVO {id:419, userId: 2, 
accountId: 2, instanceType: VirtualMachine, instanceId: 47, cmd: 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: 
{"serviceofferingid":"a6e438f6-afce-4388-9498-78cf2525cac2","sessionkey":"ExqHTfNe1JVXnQXRkEpgjMoDqu0\u003d","cmdEventType":"VM.CREATE","ctxUserId":"2","zoneid":"80b7c240-9204-43eb-85c8-762c7d7f6a15","httpmethod":"GET","templateid":"449e3489-292e-4888-9682-d57d58a0ea1a","response":"json","id":"47","hypervisor":"VMware","name":"test","_":"1420030300055","ctxAccountId":"2","diskofferingid":"3df3bee2-bdee-4b80-9a0b-5ef039c5194c","ctxStartEventId":"1099","displayname":"test"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 345050676845, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-12-31 07:49:44,303 DEBUG [c.c.a.ApiDispatcher] 
(Job-Executor-22:ctx-f2bc1611 ctx-77cccfb5) InfrastructureEntity name 
is:com.cloud.offering.ServiceOffering
2014-12-31 07:49:44,305 DEBUG [c.c.a.ApiDispatcher] 
(Job-Executor-22:ctx-f2bc1611 ctx-77cccfb5) ControlledEntity name 
is:com.cloud.template.VirtualMachineTemplate
2014-12-31 07:49:44,307 DEBUG [c.c.a.ApiDispatcher] 
(Job-Executor-22:ctx-f2bc1611 ctx-77cccfb5) Inf

Re: Ubuntu 14.04 LXC Error - Host is not HVM enabled

[Nux!]

Hello,

The obvious question - is your host HVM capable?
I think it needs to be since it might be required to run system VMs.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Mitch.Fiorentini" 
> To: users@cloudstack.apache.org
> Sent: Wednesday, 31 December, 2014 02:10:03
> Subject: Ubuntu 14.04 LXC Error - Host is not HVM enabled

> Hello, I'm getting errors launching anything LXC. I get a HVM error when
> trying to launch LXC templates.
> 
> 
> 2014-12-30 19:09:31,826 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> (API-Job-Executor-21:ctx-fb3350a0 job-741 ctx-720f3f9c) Checking resources
> in Cluster: 3 under Pod: 1
> 
> 2014-12-30 19:09:31,827 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-21:ctx-fb3350a0 job-741 ctx-720f3f9c
> FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1  cluster:3
> 
> 2014-12-30 19:09:31,829 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-21:ctx-fb3350a0 job-741 ctx-720f3f9c
> FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for
> allocation: [Host[-8-Routing]]
> 
> 2014-12-30 19:09:31,831 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-21:ctx-fb3350a0 job-741 ctx-720f3f9c
> FirstFitRoutingAllocator) Not considering hosts: [Host[-8-Routing]]  to
> deploy template: Tmpl[206-ISO-206-2-0889cc90-5389-3b03-8619-3039dfd6bd6a as
> they are not HVM enabled
> 
> 2014-12-30 19:09:31,832 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-21:ctx-fb3350a0 job-741 ctx-720f3f9c
> FirstFitRoutingAllocator) Found 0 hosts for allocation after
> prioritization: []
> 
> 2014-12-30 19:09:31,833 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-21:ctx-fb3350a0 job-741 ctx-720f3f9c
> FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=512
> 
> 2014-12-30 19:09:31,833 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-21:ctx-fb3350a0 job-741 ctx-720f3f9c
> FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts

Re: CPU socket miss match !!! Urgent

[Nux!]

Yes, I'm also seeing this on DELL PE R720... It seems like a libvirt fail, try 
to submit a bug upstream (redhat bugzilla).

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Abdul Rasool" 
> To: users@cloudstack.apache.org
> Sent: Wednesday, 31 December, 2014 07:49:37
> Subject: Re: CPU socket miss match !!! Urgent

> Hi Harikrishna,
> 
> Thanks for your reply
> 
> Here is the command out put.
> 
> root@cloud-node001:~# dmidecode -t 4 |grep Socket
> Socket Designation: CPU1
> Upgrade: Socket LGA2011
> Socket Designation: CPU2
> Upgrade: Socket LGA2011
> 
> 
> root@cloud-node001:~# virsh nodeinfo
> CPU model:   x86_64
> CPU(s):  8
> CPU frequency:   2500 MHz
> CPU socket(s):   1
> Core(s) per socket:  4
> Thread(s) per core:  1
> NUMA cell(s):2
> Memory size: 32899468 kB
> 
> When I check using dmidecode I am getting actual CPU sockets =2 whereas
> libvirt is picking only one socket. please help me to fix this issue.
> 
> Thanks
> AR
> 
> 
> 
> On 31 December 2014 at 11:27, Harikrishna Patnala <
> harikrishna.patn...@citrix.com> wrote:
> 
>> Hi,
>>
>> This seems to me like a libvirt issue on KVM.
>> We read the socket count from the parameter ‘sockets’ in NodeInfo on KVM
>> host.
>> Can you check with the command “virsh nodeinfo” ?
>>
>> Thanks,
>> Harikrishna
>>
>>
>> On 31-Dec-2014, at 9:54 am, Abdul Rasool > rasool...@gmail.com>> wrote:
>>
>> Attachment is missing ... added the same.
>>
>> On 31 December 2014 at 09:50, Abdul Rasool > rasool...@gmail.com>> wrote:
>> Hi,
>>
>> In my test / dev environment I have total 2 Dell Poweredge M620 blade
>> servers configured as KVM hypervisor each has physical CPU of 2 sockets,
>> total number of CPU sockets available in my setup is 4 sockets. but in ACS
>> infrastructure shows only 2 physical sockets. for your reference I have
>> attached my infrastructure screenshot.
>>
>> could you please some one help me why ACS is showing only 2 CPU sockets
>> instead of 4 ? is there any configuration issue from my side. ? right now
>> this environment is used for our internal development purpose due to CPU
>> mismatch I am not able to add additional guest VM in my infrastructure it
>> is throwing me insufficient resources...!
>>
>> [Inline images 1]
>>
>> Regards,
>> AR
>>
>>
>>

Re: Cloudmonkey potential bug

[Ian Forde]

(Note for anyone remotely interested in this later, it’s actually an array
returned, not a hash.  My mistake.)

On 12/31/14, 2:28 AM, "Ian Forde"  wrote:

>Hi Rohit,
>
>From a bash perspective (since I started down this path from cloudmonkey),
>I think that’s a very strange feature, to be honest.  That would mean that
>any search for an object’s id would have to filter API call results for an
>exact match to the name.  Example:
>
>Existing objects:
>  zone: zone1
>cluster: xencluster1
>cluster: cluster1
>
>(bash example, assuming “display = default") cloudmonkey list clusters
>name=cluster1 filter=name,id
>
>Getting the output of that command pruned down to just what I need would
>be a bit of a pain, but a manageable one.
>
>That said, from a Ruby (or any other language that can consume json
>hashes) perspective, it would seem to be a “softer landing”, in that it’s
>much easier to parse.  So I suppose it makes sense.  It definitely
>reinforces the need to be careful with cloudmonkey though.  Thanks for the
>clarification.
>
>  -I
>
>On 12/31/14, 1:54 AM, "Rohit Yadav"  wrote:
>
>>Hi Ian,
>>
>>Now I understand your issue. Yes, the name parameter does not search for
>>exact cluster matching the “name” you pass but for any cluster name that
>>matches for the substring “ster1”.
>>
>>In short, it’s not a bug, but feature - searches for resource names
>>matching a passed substring.
>>
>>> On 31-Dec-2014, at 3:04 pm, Ian Forde  wrote:
>>>
>>> Note that “ster1” is a proper substring match with “cluster1”.  I
>>>tested
>>> it again on both 4.3.1 (RPMs on RHEL) and 4.4.2 (RPMs on CentOS) and
>>>got
>>> the same results.
>>>
>>> Also tried (in Cloudmonkey) “api listClusters name=ster1” and got a
>>>match
>>> on both 4.3.1 and 4.4.2.
>>>
>>> I also tried the CLI method.  Doing a “curl
>>> ‘http://localhost:8096/?command=listClusters&name=ster1'” also got
>>>matches
>>> on both 4.3.1 and 4.4.2.
>>>
>>> All of a sudden, this doesn’t really look like a Cloudmonkey problem as
>>> much as it could be an API parameter parsing issue in CS itself.
>>>Maybe?
>>> (Just guessing there.)
>>>
>>>  -I
>>>
>>> On 12/31/14, 12:32 AM, "Rohit Yadav"  wrote:
>>>
 Which version of CloudStack you’re on? On 4.3.1/4.3.2, if I list
clusters
 with a name that does not exist I get no results. Tested with both
 CloudMonkey 5.3.0 and 5.3.1 (voting candidate, since 5.3.1 has not
been
 released yet).

 If you run raw API in say browser, with and without the name arg do
you
 get the same result?

> On 31-Dec-2014, at 5:28 am, Ian Forde  wrote:
>
> Hi all -
>
>
> I’ve just detected some more strange behavior in Cloudmonkey.  If I
> have a cluster named, “cluster1”, in a zone named, “pod1” inside a
>zone
> named, “zone1”, I should be able to list it correctly, yes?
>
>
> (local) 🐵 > list clusters
>
> count = 1
>
> cluster:
>
> name = cluster1
>
> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>
> allocationstate = Enabled
>
> clustertype = CloudManaged
>
> cpuovercommitratio = 1.0
>
> hypervisortype = XenServer
>
> managedstate = Managed
>
> memoryovercommitratio = 1.0
>
> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>
> podname = pod1
>
> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>
> zonename = zone1
>
>
> So why does this happen?
>
>
> (local) 🐵 > list clusters name=ster1
>
> count = 1
>
> cluster:
>
> name = cluster1
>
> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>
> allocationstate = Enabled
>
> clustertype = CloudManaged
>
> cpuovercommitratio = 1.0
>
> hypervisortype = XenServer
>
> managedstate = Managed
>
> memoryovercommitratio = 1.0
>
> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>
> podname = pod1
>
> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>
> zonename = zone1
>
>
> Note that it appears to match the trailing characters of the object’s
> name.  I also verified that this happens for pods, but zones appear
>to
> manifest the correct behavior.  Tested with Cloudmonkey 5.3.0 and a
> fresh checkout from github (5.3.1) using the master branch.
>
>
> Can anyone else replicate this?
>
>
> -I
>

 Regards,
 Rohit Yadav
 Software Architect, ShapeBlue
 M. +91 88 262 30892 | rohit.ya...@shapeblue.com
 Blog: bhaisaab.org | Twitter: @_bhaisaab



 Find out more about ShapeBlue and our range of CloudStack related
services

 IaaS Cloud Design &
 Build
 CSForge – rapid IaaS deployment
framework
 CloudStack Consulting
 CloudStack Software
 Engineering

Re: Cloudmonkey potential bug

[Ian Forde]

Hi Rohit,

From a bash perspective (since I started down this path from cloudmonkey),
I think that’s a very strange feature, to be honest.  That would mean that
any search for an object’s id would have to filter API call results for an
exact match to the name.  Example:

Existing objects:
  zone: zone1
cluster: xencluster1
cluster: cluster1

(bash example, assuming “display = default") cloudmonkey list clusters
name=cluster1 filter=name,id

Getting the output of that command pruned down to just what I need would
be a bit of a pain, but a manageable one.

That said, from a Ruby (or any other language that can consume json
hashes) perspective, it would seem to be a “softer landing”, in that it’s
much easier to parse.  So I suppose it makes sense.  It definitely
reinforces the need to be careful with cloudmonkey though.  Thanks for the
clarification.

  -I

On 12/31/14, 1:54 AM, "Rohit Yadav"  wrote:

>Hi Ian,
>
>Now I understand your issue. Yes, the name parameter does not search for
>exact cluster matching the “name” you pass but for any cluster name that
>matches for the substring “ster1”.
>
>In short, it’s not a bug, but feature - searches for resource names
>matching a passed substring.
>
>> On 31-Dec-2014, at 3:04 pm, Ian Forde  wrote:
>>
>> Note that “ster1” is a proper substring match with “cluster1”.  I tested
>> it again on both 4.3.1 (RPMs on RHEL) and 4.4.2 (RPMs on CentOS) and got
>> the same results.
>>
>> Also tried (in Cloudmonkey) “api listClusters name=ster1” and got a
>>match
>> on both 4.3.1 and 4.4.2.
>>
>> I also tried the CLI method.  Doing a “curl
>> ‘http://localhost:8096/?command=listClusters&name=ster1'” also got
>>matches
>> on both 4.3.1 and 4.4.2.
>>
>> All of a sudden, this doesn’t really look like a Cloudmonkey problem as
>> much as it could be an API parameter parsing issue in CS itself.  Maybe?
>> (Just guessing there.)
>>
>>  -I
>>
>> On 12/31/14, 12:32 AM, "Rohit Yadav"  wrote:
>>
>>> Which version of CloudStack you’re on? On 4.3.1/4.3.2, if I list
>>>clusters
>>> with a name that does not exist I get no results. Tested with both
>>> CloudMonkey 5.3.0 and 5.3.1 (voting candidate, since 5.3.1 has not been
>>> released yet).
>>>
>>> If you run raw API in say browser, with and without the name arg do you
>>> get the same result?
>>>
 On 31-Dec-2014, at 5:28 am, Ian Forde  wrote:

 Hi all -


 I’ve just detected some more strange behavior in Cloudmonkey.  If I
 have a cluster named, “cluster1”, in a zone named, “pod1” inside a
zone
 named, “zone1”, I should be able to list it correctly, yes?


 (local) 🐵 > list clusters

 count = 1

 cluster:

 name = cluster1

 id = d2e79c24-88e4-40f8-9639-e262c6e85f03

 allocationstate = Enabled

 clustertype = CloudManaged

 cpuovercommitratio = 1.0

 hypervisortype = XenServer

 managedstate = Managed

 memoryovercommitratio = 1.0

 podid = d27ea9af-4228-482b-89ff-0f36f74e5a48

 podname = pod1

 zoneid = e362b144-04db-4540-aa53-75d9e2ffa832

 zonename = zone1


 So why does this happen?


 (local) 🐵 > list clusters name=ster1

 count = 1

 cluster:

 name = cluster1

 id = d2e79c24-88e4-40f8-9639-e262c6e85f03

 allocationstate = Enabled

 clustertype = CloudManaged

 cpuovercommitratio = 1.0

 hypervisortype = XenServer

 managedstate = Managed

 memoryovercommitratio = 1.0

 podid = d27ea9af-4228-482b-89ff-0f36f74e5a48

 podname = pod1

 zoneid = e362b144-04db-4540-aa53-75d9e2ffa832

 zonename = zone1


 Note that it appears to match the trailing characters of the object’s
 name.  I also verified that this happens for pods, but zones appear to
 manifest the correct behavior.  Tested with Cloudmonkey 5.3.0 and a
 fresh checkout from github (5.3.1) using the master branch.


 Can anyone else replicate this?


 -I

>>>
>>> Regards,
>>> Rohit Yadav
>>> Software Architect, ShapeBlue
>>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>>
>>>
>>>
>>> Find out more about ShapeBlue and our range of CloudStack related
>>>services
>>>
>>> IaaS Cloud Design &
>>> Build
>>> CSForge – rapid IaaS deployment
>>>framework
>>> CloudStack Consulting
>>> CloudStack Software
>>> Engineering
>>> CloudStack Infrastructure
>>> Support
>>> CloudStack Bootcamp Training
>>> Courses
>>>
>>> This email and any attachments to it may be confidential and are
>>>intended
>>> solely for the use of th

Re: Cloudmonkey potential bug

[Rohit Yadav]

Hi Ian,

Now I understand your issue. Yes, the name parameter does not search for exact 
cluster matching the “name” you pass but for any cluster name that matches for 
the substring “ster1”.

In short, it’s not a bug, but feature - searches for resource names matching a 
passed substring.

> On 31-Dec-2014, at 3:04 pm, Ian Forde  wrote:
>
> Note that “ster1” is a proper substring match with “cluster1”.  I tested
> it again on both 4.3.1 (RPMs on RHEL) and 4.4.2 (RPMs on CentOS) and got
> the same results.
>
> Also tried (in Cloudmonkey) “api listClusters name=ster1” and got a match
> on both 4.3.1 and 4.4.2.
>
> I also tried the CLI method.  Doing a “curl
> ‘http://localhost:8096/?command=listClusters&name=ster1'” also got matches
> on both 4.3.1 and 4.4.2.
>
> All of a sudden, this doesn’t really look like a Cloudmonkey problem as
> much as it could be an API parameter parsing issue in CS itself.  Maybe?
> (Just guessing there.)
>
>  -I
>
> On 12/31/14, 12:32 AM, "Rohit Yadav"  wrote:
>
>> Which version of CloudStack you’re on? On 4.3.1/4.3.2, if I list clusters
>> with a name that does not exist I get no results. Tested with both
>> CloudMonkey 5.3.0 and 5.3.1 (voting candidate, since 5.3.1 has not been
>> released yet).
>>
>> If you run raw API in say browser, with and without the name arg do you
>> get the same result?
>>
>>> On 31-Dec-2014, at 5:28 am, Ian Forde  wrote:
>>>
>>> Hi all -
>>>
>>>
>>> I’ve just detected some more strange behavior in Cloudmonkey.  If I
>>> have a cluster named, “cluster1”, in a zone named, “pod1” inside a zone
>>> named, “zone1”, I should be able to list it correctly, yes?
>>>
>>>
>>> (local) 🐵 > list clusters
>>>
>>> count = 1
>>>
>>> cluster:
>>>
>>> name = cluster1
>>>
>>> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>>>
>>> allocationstate = Enabled
>>>
>>> clustertype = CloudManaged
>>>
>>> cpuovercommitratio = 1.0
>>>
>>> hypervisortype = XenServer
>>>
>>> managedstate = Managed
>>>
>>> memoryovercommitratio = 1.0
>>>
>>> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>>>
>>> podname = pod1
>>>
>>> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>>>
>>> zonename = zone1
>>>
>>>
>>> So why does this happen?
>>>
>>>
>>> (local) 🐵 > list clusters name=ster1
>>>
>>> count = 1
>>>
>>> cluster:
>>>
>>> name = cluster1
>>>
>>> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>>>
>>> allocationstate = Enabled
>>>
>>> clustertype = CloudManaged
>>>
>>> cpuovercommitratio = 1.0
>>>
>>> hypervisortype = XenServer
>>>
>>> managedstate = Managed
>>>
>>> memoryovercommitratio = 1.0
>>>
>>> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>>>
>>> podname = pod1
>>>
>>> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>>>
>>> zonename = zone1
>>>
>>>
>>> Note that it appears to match the trailing characters of the object’s
>>> name.  I also verified that this happens for pods, but zones appear to
>>> manifest the correct behavior.  Tested with Cloudmonkey 5.3.0 and a
>>> fresh checkout from github (5.3.1) using the master branch.
>>>
>>>
>>> Can anyone else replicate this?
>>>
>>>
>>> -I
>>>
>>
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design &
>> Build
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software
>> Engineering
>> CloudStack Infrastructure
>> Support
>> CloudStack Bootcamp Training
>> Courses
>>
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views
>> or opinions expressed are solely those of the author and do not
>> necessarily represent those of Shape Blue Ltd or related companies. If
>> you are not the intended recipient of this email, you must neither take
>> any action based upon its contents, nor copy or show it to anyone. Please
>> contact the sender if you believe you have received this email in error.
>> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
>> Services India LLP is a company incorporated in India and is operated
>> under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is
>> a company incorporated in Brasil and is operated under license from Shape
>> Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
>> South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
>> is a registered trademark.
>

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our ra

Re: Cloudmonkey potential bug

[Ian Forde]

Note that “ster1” is a proper substring match with “cluster1”.  I tested
it again on both 4.3.1 (RPMs on RHEL) and 4.4.2 (RPMs on CentOS) and got
the same results.

Also tried (in Cloudmonkey) “api listClusters name=ster1” and got a match
on both 4.3.1 and 4.4.2.

I also tried the CLI method.  Doing a “curl
‘http://localhost:8096/?command=listClusters&name=ster1'” also got matches
on both 4.3.1 and 4.4.2.

All of a sudden, this doesn’t really look like a Cloudmonkey problem as
much as it could be an API parameter parsing issue in CS itself.  Maybe?
(Just guessing there.)

  -I

On 12/31/14, 12:32 AM, "Rohit Yadav"  wrote:

>Which version of CloudStack you’re on? On 4.3.1/4.3.2, if I list clusters
>with a name that does not exist I get no results. Tested with both
>CloudMonkey 5.3.0 and 5.3.1 (voting candidate, since 5.3.1 has not been
>released yet).
>
>If you run raw API in say browser, with and without the name arg do you
>get the same result?
>
>> On 31-Dec-2014, at 5:28 am, Ian Forde  wrote:
>>
>> Hi all -
>>
>>
>> I’ve just detected some more strange behavior in Cloudmonkey.  If I
>>have a cluster named, “cluster1”, in a zone named, “pod1” inside a zone
>>named, “zone1”, I should be able to list it correctly, yes?
>>
>>
>> (local) 🐵 > list clusters
>>
>> count = 1
>>
>> cluster:
>>
>> name = cluster1
>>
>> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>>
>> allocationstate = Enabled
>>
>> clustertype = CloudManaged
>>
>> cpuovercommitratio = 1.0
>>
>> hypervisortype = XenServer
>>
>> managedstate = Managed
>>
>> memoryovercommitratio = 1.0
>>
>> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>>
>> podname = pod1
>>
>> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>>
>> zonename = zone1
>>
>>
>> So why does this happen?
>>
>>
>> (local) 🐵 > list clusters name=ster1
>>
>> count = 1
>>
>> cluster:
>>
>> name = cluster1
>>
>> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>>
>> allocationstate = Enabled
>>
>> clustertype = CloudManaged
>>
>> cpuovercommitratio = 1.0
>>
>> hypervisortype = XenServer
>>
>> managedstate = Managed
>>
>> memoryovercommitratio = 1.0
>>
>> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>>
>> podname = pod1
>>
>> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>>
>> zonename = zone1
>>
>>
>> Note that it appears to match the trailing characters of the object’s
>>name.  I also verified that this happens for pods, but zones appear to
>>manifest the correct behavior.  Tested with Cloudmonkey 5.3.0 and a
>>fresh checkout from github (5.3.1) using the master branch.
>>
>>
>> Can anyone else replicate this?
>>
>>
>>  -I
>>
>
>Regards,
>Rohit Yadav
>Software Architect, ShapeBlue
>M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>Blog: bhaisaab.org | Twitter: @_bhaisaab
>
>
>
>Find out more about ShapeBlue and our range of CloudStack related services
>
>IaaS Cloud Design &
>Build
>CSForge – rapid IaaS deployment framework
>CloudStack Consulting
>CloudStack Software
>Engineering
>CloudStack Infrastructure
>Support
>CloudStack Bootcamp Training
>Courses
>
>This email and any attachments to it may be confidential and are intended
>solely for the use of the individual to whom it is addressed. Any views
>or opinions expressed are solely those of the author and do not
>necessarily represent those of Shape Blue Ltd or related companies. If
>you are not the intended recipient of this email, you must neither take
>any action based upon its contents, nor copy or show it to anyone. Please
>contact the sender if you believe you have received this email in error.
>Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
>Services India LLP is a company incorporated in India and is operated
>under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is
>a company incorporated in Brasil and is operated under license from Shape
>Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
>South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
>is a registered trademark.

Re: Cloudmonkey potential bug

[Rohit Yadav]

Which version of CloudStack you’re on? On 4.3.1/4.3.2, if I list clusters with 
a name that does not exist I get no results. Tested with both CloudMonkey 5.3.0 
and 5.3.1 (voting candidate, since 5.3.1 has not been released yet).

If you run raw API in say browser, with and without the name arg do you get the 
same result?

> On 31-Dec-2014, at 5:28 am, Ian Forde  wrote:
>
> Hi all -
>
>
> I’ve just detected some more strange behavior in Cloudmonkey.  If I have a 
> cluster named, “cluster1”, in a zone named, “pod1” inside a zone named, 
> “zone1”, I should be able to list it correctly, yes?
>
>
> (local) 🐵 > list clusters
>
> count = 1
>
> cluster:
>
> name = cluster1
>
> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>
> allocationstate = Enabled
>
> clustertype = CloudManaged
>
> cpuovercommitratio = 1.0
>
> hypervisortype = XenServer
>
> managedstate = Managed
>
> memoryovercommitratio = 1.0
>
> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>
> podname = pod1
>
> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>
> zonename = zone1
>
>
> So why does this happen?
>
>
> (local) 🐵 > list clusters name=ster1
>
> count = 1
>
> cluster:
>
> name = cluster1
>
> id = d2e79c24-88e4-40f8-9639-e262c6e85f03
>
> allocationstate = Enabled
>
> clustertype = CloudManaged
>
> cpuovercommitratio = 1.0
>
> hypervisortype = XenServer
>
> managedstate = Managed
>
> memoryovercommitratio = 1.0
>
> podid = d27ea9af-4228-482b-89ff-0f36f74e5a48
>
> podname = pod1
>
> zoneid = e362b144-04db-4540-aa53-75d9e2ffa832
>
> zonename = zone1
>
>
> Note that it appears to match the trailing characters of the object’s name.  
> I also verified that this happens for pods, but zones appear to manifest the 
> correct behavior.  Tested with Cloudmonkey 5.3.0 and a fresh checkout from 
> github (5.3.1) using the master branch.
>
>
> Can anyone else replicate this?
>
>
>  -I
>

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.