Re: ACS 4.4.1 network.throttling.rate - Advance Zone- XenServer 6.2
2015.01.02. 19:14 keltezéssel, Motty Cruz írta: Hello Erdosi, you're right I see QoS limitiation in XenCenter, can you tell me the best approach to change to unlimited? For testing purpose, you can switch off the QoS with xencenter, if the VM running. You just need to reconfigure the interface (mine went down), and check the result. As I mentioned this one is good for testing, but after reboot, the interface will be recreated, and QoS limit goes back. To workaround that, I made a network offering, which QoS limit is 10Gb/s, and it's looks good. Regards, Peter
Re: Ansible CloudStack modules
great job thanks 2015-01-03 23:19 GMT+08:00 Rene Moser : > Hi again > > On 12/18/2014 03:44 PM, Sebastien Goasguen wrote: > >> Thanks for Sharing René, I tested the VM one couple days ago and it works >> perfect. >> I'd love to see one for key paris and secruitygroups. > > Security group management (group and rules) has been added, e.g.: > > - name: ensure security group default exist > cloudstack_sg: > name: default > > - name: add inbound SSH to security group default > cloudstack_sg_rule: > name: default > start_port: 22 > end_port: 22 > > I made a small example playbook [1] which installs yacy [2] from scratch > on exoscale. > > > [1] https://github.com/resmo/ansible-cloudstack-example > [2] http://www.yacy.net/en/ > > > -- 白清杰 (Born Bai) Mail: linux...@gmail.com
Re: XenServer Creedence support
cloud ACS support XenServer Creedence + ceph 2015-01-03 18:04 GMT+08:00 Daan Hoogland : > We will have to patch and release at minimum. not out of the box. > > On Fri, Jan 2, 2015 at 8:22 PM, Matthew Midgett > wrote: >> Will ACS 4.4 support Xenserver Creedence when it is released? >> > > > > -- > Daan -- 白清杰 (Born Bai) Mail: linux...@gmail.com
Re: Ansible CloudStack modules
Hi again On 12/18/2014 03:44 PM, Sebastien Goasguen wrote: > Thanks for Sharing René, I tested the VM one couple days ago and it works > perfect. > I'd love to see one for key paris and secruitygroups. Security group management (group and rules) has been added, e.g.: - name: ensure security group default exist cloudstack_sg: name: default - name: add inbound SSH to security group default cloudstack_sg_rule: name: default start_port: 22 end_port: 22 I made a small example playbook [1] which installs yacy [2] from scratch on exoscale. [1] https://github.com/resmo/ansible-cloudstack-example [2] http://www.yacy.net/en/ signature.asc Description: OpenPGP digital signature
Re: Unable to Create An Instance
hi all, And when i check agent's log i get this. 2015-01-04 01:23:20,320 ERROR [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) Internal error occurred when attempting to moun$ 2015-01-04 01:23:20,320 ERROR [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) Failed to create netfs mount: 10.8.100.201: /mnt$ org.libvirt.LibvirtException: internal error: Child process (/bin/mount 10.8.100.201:/mnt/secondary/template/tmpl/2/201 /mnt/0b82d60b-611d-320c$ at org.libvirt.ErrorHandler.processError(Unknown Source) at org.libvirt.Connect.processError(Unknown Source) at org.libvirt.Connect.processError(Unknown Source) at org.libvirt.Connect.storagePoolCreateXML(Unknown Source) at com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createNetfsStoragePool(LibvirtStorageAdaptor.java:136) at com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:500) at com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:277) at com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePoolByURI(KVMStoragePoolManager.java:233) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVbd(LibvirtComputingResource.java:3917) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3789) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1333) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 2015-01-04 01:23:20,321 ERROR [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) [Ljava.lang.StackTraceElement;@3854e123 2015-01-04 01:23:20,321 DEBUG [kvm.storage.KVMStoragePoolManager] (agentRequest-Handler-4:null) Disconnecting disk 26e85233-20dc-4cb1-99a0-751e$ 2015-01-04 01:23:20,352 WARN [cloud.agent.Agent] (agentRequest-Handler-4:null) Caught: com.cloud.utils.exception.CloudRuntimeException: org.libvirt.LibvirtException: internal error: Child process (/bin/mount 10.8.100.201:/mnt/seco$ Thank you On 3 January 2015 at 19:14, Mohamed Infaz wrote: > Hi All, > > I am running cloudstack 4.4.1 in ubuntu 14.04 with three kvm Hosts. I was > successfully able to start the system virtual machines. And i was > successful in running the health script and no errors occurred. Now when i > am trying to create and instance i am getting two exceptions. > > 2015-01-04 02:45:06,605 ERROR [c.c.v.VirtualMachineManagerImpl] > (Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Failed to > start instance VM[User|i-2-16-VM] > com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that > is of class com.cloud.agent.api.StartAnswer > at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80) > at > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1020) > at > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5195) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > at > com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5340) > at > com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > j
Unable to Create An Instance
Hi All,
I am running cloudstack 4.4.1 in ubuntu 14.04 with three kvm Hosts. I was
successfully able to start the system virtual machines. And i was
successful in running the health script and no errors occurred. Now when i
am trying to create and instance i am getting two exceptions.
2015-01-04 02:45:06,605 ERROR [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Failed to
start instance VM[User|i-2-16-VM]
com.cloud.utils.exception.CloudRuntimeException: Unable to get answer that
is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1020)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5195)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5340)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2015-01-04 02:45:06,688 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Cleaning up
resources for the vm VM[User|i-2-16-VM] in Starting state
2015-01-04 02:45:06,690 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Seq
6-3627649499846934559: Sending { Cmd , MgmtId: 248795600505608, via:
6(virtualops-h4), Ver: v1, Flags: 100011,
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"checkBeforeCleanup":false,"vmName":"i-2-16-VM","wait":0}}]
}
2015-01-04 02:45:06,828 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-13:null) Seq 6-3627649499846934559: Processing: {
Ans: , MgmtId: 248795600505608, via: 6, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.StopAnswer":{"result":true,"wait":0}}] }
2015-01-04 02:45:06,828 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Seq
6-3627649499846934559: Received: { Ans: , MgmtId: 248795600505608, via: 6,
Ver: v1, Flags: 10, { StopAnswer } }
2015-01-04 02:45:06,836 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Changing
active number of nics for network id=204 on -1
2015-01-04 02:45:07,043 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Asking
VirtualRouter to release
NicProfile[30-16-a82c2881-1c14-4494-89fa-cde39b406313-10.8.100.27-vlan://untagged
2015-01-04 02:45:07,045 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Asking
SecurityGroupProvider to release
NicProfile[30-16-a82c2881-1c14-4494-89fa-cde39b406313-10.8.100.27-vlan://untagged
2015-01-04 02:45:07,045 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Successfully
released network resources for the vm VM[User|i-2-16-VM]
2015-01-04 02:45:07,045 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) Successfully
cleanued up resources for the vm VM[User|i-2-16-VM] in Starting state
2015-01-04 02:45:07,298 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-23:ctx-afbc7bf5 job-97/job-98 ctx-8772bf32) VM state
transitted from :Starting to Stopped with event: OperationFailedvm's
original host id: null new host id: null host id before state transition: 6
2015-01-04 02:45:07,304 DEBUG [c.c.c.CapacityManagerImpl]
(Wo
Re: XenServer Creedence support
We will have to patch and release at minimum. not out of the box. On Fri, Jan 2, 2015 at 8:22 PM, Matthew Midgett wrote: > Will ACS 4.4 support Xenserver Creedence when it is released? > -- Daan
