Re: Volumes directory on secondary storage

[Nitin Mehta]

Reply inline.

On 24/11/13 6:52 AM, "Lennert den Teuling"  wrote:

>Hi,
>
>I currently got a directory of 1.1TB on my secondary storage called
>volumes. I'm
>familiar with the template and snapshot directory, but not really with the
>volume directory.
>
>After some investigation seems that this directory in my case has been
>used for:
>1. Storing volumes of VM's that the customer wants to download using http.
>2. Temporally storing volumes that have been uploaded trough the GUI.
>3. Temporally storing volumes that are moved between clusters (storage
>migration).
>
>But it seems like some files have been there for a really long time, and
>delete
>commands only seems to be running for case 1 or 2. It looks like that all
>volumes that have been used in case 3 are still there.

This would be a bug I presume. Please file a bug with right version, logs
environment information.
That said, there has been major refactoring done in 4.2 release, so things
might have changed. Please do test and see if you can.

>
>I'm using CS 4.1 on this system, i did not test  this on 4.2 yet.
>
>Could this be normal behavior in any way or is this a bug?
>
>Thanks!
>
>Met vriendelijke groet / Kind regards,
>
>Lennert den Teuling
>Tel direct: +31 (0)118 700 210

RE: Unable add instance after update on CS4.2

[Sanjay Tripathi]

Hi Diego,

>From the listClusters response, it looks like your cluster doesn't have enough 
>CPU capacity to deploy a new VM.

Type = 1 is for CPU resource.
{
  "capacitytotal": 576000,
  "capacityused": 701250,
  "percentused": "121.74",
  "type": 1
}

--Sanjay

> -Original Message-
> From: Diego Spinola Castro [mailto:spinolacas...@gmail.com]
> Sent: Monday, November 25, 2013 1:11 AM
> To: users@cloudstack.apache.org
> Subject: Unable add instance after update on CS4.2
> 
> Hi guys, i'm running into a issue on  a vmware 4.1 cluster after update CS to
> 4.2.
> 
> When i try create a instance i get the following error:
> 
> 2013-11-24 17:37:43,817 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-11:null) ===START===  187.37.35.156 -- GET
>  command=deployVirtualMachine&zoneId=83a1d5a6-6534-4600-b8b4-
> c1bd240eb711&templateId=227&hypervisor=VMware&serviceOfferingId=32
> &networkIds=0749b01c-9dbe-4008-a388-
> c6cb82988852&response=json&sessionkey=%2BrE4mGxi%2Bnqu2r7FxFj8QE
> V9%2FFA%3D&_=1385321825263
> 2013-11-24 17:37:43,858 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-11:null) InfrastructureEntity name
> is:com.cloud.offering.ServiceOffering
> 2013-11-24 17:37:43,858 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-11:null) ControlledEntity name
> is:com.cloud.template.VirtualMachineTemplate
> 2013-11-24 17:37:43,863 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-11:null) ControlledEntity name is:com.cloud.network.Network
> 2013-11-24 17:37:43,869 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-11:null) Access to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
> DomainChecker_EnhancerByCloudStack_560d9237
> 2013-11-24 17:37:43,873 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-11:null) Access to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
> DomainChecker_EnhancerByCloudStack_560d9237
> 2013-11-24 17:37:43,878 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-11:null) Access to Ntwk[358|Guest|6] granted to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
> DomainChecker_EnhancerByCloudStack_560d9237
> 2013-11-24 17:37:43,881 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-11:null) Access to
> Tmpl[227-OVA-227-2-150da313-1018-3320-becd-9dc003c96374 granted to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
> DomainChecker_EnhancerByCloudStack_560d9237
> 2013-11-24 17:37:43,884 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-11:null) Access to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
> DomainChecker_EnhancerByCloudStack_560d9237
> 2013-11-24 17:37:43,913 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-11:null) Access to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
> Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
> DomainChecker_EnhancerByCloudStack_560d9237
> 2013-11-24 17:37:43,964 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-11:null) Service SecurityGroup is not supported in the network
> id=358
> 2013-11-24 17:37:44,144 DEBUG [cloud.vm.UserVmManagerImpl]
> (catalina-exec-11:null) Allocating in the DB for vm
> 2013-11-24 17:37:44,224 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-11:null) Allocating entries for VM:
> VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
> 2013-11-24 17:37:44,238 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-11:null) Allocating nics for VM[User|ab62df84-e398-4e02-
> 8a55-9319ed694998]
> 2013-11-24 17:37:44,240 DEBUG [cloud.network.NetworkManagerImpl]
> (catalina-exec-11:null) Allocating nic for vm VM[User|ab62df84-e398-4e02-
> 8a55-9319ed694998] in network Ntwk[358|Guest|6] with requested profile
> NicProfile[0-0-null-null-null
> 2013-11-24 17:37:44,358 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-11:null) Service SecurityGroup is not supported in the network
> id=358
> 2013-11-24 17:37:44,361 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-11:null) Allocating disks for VM[User|ab62df84-e398-4e02-
> 8a55-9319ed694998]
> 2013-11-24 17:37:44,389 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-11:null) Allocation completed for VM:
> VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
> 2013-11-24 17:37:44,389 DEBUG [cloud.vm.UserVmManagerImpl]
> (catalina-exec-11:null) Successfully allocated DB entry for
> VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
> 2013-11-24 17:37:44,566 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-11:null) Service SecurityGroup is not supported in the network
> id=358
> 2013-11-24 17:37:44,573 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-11:null) Service SecurityGroup is not supported in the network
> id=358
> 2013-11-24 17:37:44,968 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-11:null) submit async job-470 = [ 066b7455-3b86-4b85-9954-
> 7caf6ddb710e ], details: Asyn

Fail to attach volume to VM

[Du Jun]

Hi guys,
Recently,I met a problem about attaching volume to VM that is running.The
error information is show below,
Failed to attach volume: volume-1 to VM: basic-inception-vm;
org.libvirt.LibvirtException: internal error unable to execute QEMU command
'device_add': Duplicate ID 'virtio-disk1' for device

Duplicate ID 'virtio-disk1' for device?What does it mean?

I can attach volume while VM is stopped,but I can't attach it while VM is
running.So,please help me .




Best regards,
Frank

ACS 4.2.1 - Multi-Zone vSphere Architecture

[Simon Murphy]

Hi all,

Im after some guidance on setting up ACS 4.2.1 with vSphere in a multi zone 
environment. The only way I have been able to successfully build a zone to this 
point is by having vSphere, ESXi console ports, ACS and the reserved system 
range on a single VLAN. This is OK for a small, single site deployment but how 
does this translate for multiple zones? The docs suggest that configuring a 
single /20 range for management is desired, does that imply that that range 
should be stretched across sites?

Should it be possible to have a dedicated VLAN at each site for vCenter, ESXi 
console ports and the system VM's, and then have the ACS server sitting in a 
separate VLAN that can route between both networks? I have been unsuccessful in 
getting his working to date so hopefully someone out there has some experience 
setting up a multi-site ACS/vSphere envoronment.

Any guidance would be greatly appreciated!


Simon Murphy
Solutions Architect

ViFX | Cloud Infrastructure
Level 7, 57 Fort Street, Auckland, New Zealand 1010
PO Box 106700, Auckland, New Zealand 1143
M +64 21 285 4519 | S simon_a_murphy
www.vifx.co.nz follow us on 
twitter
Auckland | Wellington | Christchurch

[cid:image003.jpg@01CDDF95.815BF160]

experience. expertise. execution.

This email and any files transmitted with it are confidential, without 
prejudice and may contain information that is subject to legal privilege. It is 
intended solely for the use of the individual/s to whom it is addressed in 
accordance with the provisions of the Privacy Act (1993). The content contained 
in this email does not, necessarily, reflect the official policy position of 
ViFX nor does ViFX have any responsibility for any alterations to the contents 
of this email that may occur following transmission. If you are not the 
addressee it may be unlawful for you to read, copy, distribute, disclose or 
otherwise use the information contained within this email. If you are not the 
intended recipient, please notify the sender prior to deleting this email 
message from your system. Please note ViFX reserves the right to monitor, from 
time to time, the communications sent to and from its email network.

Unable add instance after update on CS4.2

[Diego Spinola Castro]

Hi guys, i'm running into a issue on  a vmware 4.1 cluster after update CS
to 4.2.

When i try create a instance i get the following error:

2013-11-24 17:37:43,817 DEBUG [cloud.api.ApiServlet]
(catalina-exec-11:null) ===START===  187.37.35.156 -- GET
 
command=deployVirtualMachine&zoneId=83a1d5a6-6534-4600-b8b4-c1bd240eb711&templateId=227&hypervisor=VMware&serviceOfferingId=32&networkIds=0749b01c-9dbe-4008-a388-c6cb82988852&response=json&sessionkey=%2BrE4mGxi%2Bnqu2r7FxFj8QEV9%2FFA%3D&_=1385321825263
2013-11-24 17:37:43,858 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-11:null) InfrastructureEntity name
is:com.cloud.offering.ServiceOffering
2013-11-24 17:37:43,858 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-11:null) ControlledEntity name
is:com.cloud.template.VirtualMachineTemplate
2013-11-24 17:37:43,863 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-11:null) ControlledEntity name is:com.cloud.network.Network
2013-11-24 17:37:43,869 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-11:null) Access to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
DomainChecker_EnhancerByCloudStack_560d9237
2013-11-24 17:37:43,873 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-11:null) Access to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
DomainChecker_EnhancerByCloudStack_560d9237
2013-11-24 17:37:43,878 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-11:null) Access to Ntwk[358|Guest|6] granted to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
DomainChecker_EnhancerByCloudStack_560d9237
2013-11-24 17:37:43,881 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-11:null) Access to
Tmpl[227-OVA-227-2-150da313-1018-3320-becd-9dc003c96374 granted to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
DomainChecker_EnhancerByCloudStack_560d9237
2013-11-24 17:37:43,884 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-11:null) Access to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
DomainChecker_EnhancerByCloudStack_560d9237
2013-11-24 17:37:43,913 DEBUG [cloud.user.AccountManagerImpl]
(catalina-exec-11:null) Access to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] granted to
Acct[8bcd7766-9361-40a9-b660-eb2b0694d7a4-diego] by
DomainChecker_EnhancerByCloudStack_560d9237
2013-11-24 17:37:43,964 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-11:null) Service SecurityGroup is not supported in the
network id=358
2013-11-24 17:37:44,144 DEBUG [cloud.vm.UserVmManagerImpl]
(catalina-exec-11:null) Allocating in the DB for vm
2013-11-24 17:37:44,224 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-11:null) Allocating entries for VM:
VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
2013-11-24 17:37:44,238 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-11:null) Allocating nics for
VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
2013-11-24 17:37:44,240 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-11:null) Allocating nic for vm
VM[User|ab62df84-e398-4e02-8a55-9319ed694998] in network Ntwk[358|Guest|6]
with requested profile NicProfile[0-0-null-null-null
2013-11-24 17:37:44,358 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-11:null) Service SecurityGroup is not supported in the
network id=358
2013-11-24 17:37:44,361 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-11:null) Allocating disks for
VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
2013-11-24 17:37:44,389 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-11:null) Allocation completed for VM:
VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
2013-11-24 17:37:44,389 DEBUG [cloud.vm.UserVmManagerImpl]
(catalina-exec-11:null) Successfully allocated DB entry for
VM[User|ab62df84-e398-4e02-8a55-9319ed694998]
2013-11-24 17:37:44,566 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-11:null) Service SecurityGroup is not supported in the
network id=358
2013-11-24 17:37:44,573 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-11:null) Service SecurityGroup is not supported in the
network id=358
2013-11-24 17:37:44,968 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-470 = [
066b7455-3b86-4b85-9954-7caf6ddb710e ], details: AsyncJobVO {id:470,
userId: 343, accountId: 165, sessionKey: null, instanceType:
VirtualMachine, instanceId: 1074, cmd:
org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdOriginator: null,
cmdInfo:
{"sessionkey":"+rE4mGxi+nqu2r7FxFj8QEV9/FA\u003d","cmdEventType":"VM.CREATE","ctxUserId":"343","serviceOfferingId":"32","httpmethod":"GET","zoneId":"83a1d5a6-6534-4600-b8b4-c1bd240eb711","templateId":"227","response":"json","id":"1074","networkIds":"0749b01c-9dbe-4008-a388-c6cb82988852","hypervisor":"VMware","_":"1385321825263","ctxAccountId":"165","ctxStartEventId":"193267"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0,

Volumes directory on secondary storage

[Lennert den Teuling]

Hi,

I currently got a directory of 1.1TB on my secondary storage called volumes. I'm
familiar with the template and snapshot directory, but not really with the
volume directory.

After some investigation seems that this directory in my case has been used for:
1. Storing volumes of VM's that the customer wants to download using http.
2. Temporally storing volumes that have been uploaded trough the GUI.
3. Temporally storing volumes that are moved between clusters (storage
migration).

But it seems like some files have been there for a really long time, and delete
commands only seems to be running for case 1 or 2. It looks like that all
volumes that have been used in case 3 are still there.

I'm using CS 4.1 on this system, i did not test  this on 4.2 yet.

Could this be normal behavior in any way or is this a bug?

Thanks!

Met vriendelijke groet / Kind regards,

Lennert den Teuling
Tel direct: +31 (0)118 700 210

Re: How to take snapshot for KVM instance

[Nux!]

On 24.11.2013 12:30, Du Jun wrote:

Hi all,
Does cloudstack4.2 support snapshot for KVM instance?How can I take
snapshot for KVM instance?


You can't take a snapshot of the VM, but you can snapshot the 
individual ROOT and DATA disks in the Storage section if you enable "KVM 
snapshots" in Global Settings.


This is one of the more frequent complaints I see on the ML, hopefully 
it will receive some dev attention.


--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

#Cloudstack: Finally guest VMs are up running

[jitendra shelar]

Thanks all cloudstackers for your excellent help and support.

In past, I have worked on Opentstack and IBM Smart Cloud Enterprise.
Feels happy to see the excellent UI and the ease of configuration in
Cloudstack. It's really awesome.

How to take snapshot for KVM instance

[Du Jun]

Hi all,
Does cloudstack4.2 support snapshot for KVM instance?How can I take
snapshot for KVM instance?

-
Best regards,
Frank