Hi Vivek We currently have one Adv Zone that was originally setup with KVM hosts and we are trying to add a new VMware cluster to an existing Pod. We have added the relevant traffic labels to the VMWare sections on the physical adapters on the Zone and added the VMware cluster but then when trying to add the Datastore Cluster as new Primary storage we are not seeing the 'PreSetup' , 'VMFS' or 'DataCluster' options in the add primary storage wizard - its really odd.
We set the vmware.management.portgroup global setting to "Management Network" and have split the ACS traffic types into 3 VLAN's (the same way we have for the KVM hosts) and created vmware vswitches called cloudbr0 (mgmt., sec storage), cloudbr1 (guest) and cloudbr2 (public) and added these vswitch names as the relevant traffic labels on the correct physical adapters in ACS. We use the vcenter full administrator account when adding to Vsphere datacenter to ACS and are using the eval license in vcenter - which is meant to be fully functional for a short period. Any assistance in resolving this would greatly be appreciated BR Gary Gary Dixon Senior Technical Consultant T: +44 161 537 4990 E: v...@quadris-support.com W: www.quadris.co.uk The information contained in this e-mail from Quadris may be confidential and privileged for the private use of the named recipient. The contents of this e-mail may not necessarily represent the official views of Quadris. If you have received this information in error you must not copy, distribute or take any action or reliance on its contents. Please destroy any hard copies and delete this message. -----Original Message----- From: Vivek Kumar <vivek.ku...@indiqus.com.INVALID> Sent: Monday, July 10, 2023 5:45 PM To: users@cloudstack.apache.org Subject: Re: ACS with vmware hypervisors Did you choose right zone/pod/cluster, because I am also using 4.15.2 and it’s giving me option PreSetup, do you have option called - vmfs ? Vivek Kumar Sr. Manager - Cloud & DevOps TechOps | Indiqus Technologies vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> http://www.indiqus.com/ <https://www.indiqus.com/> > On 10-Jul-2023, at 3:34 PM, Gary Dixon <gary.di...@quadris.co.uk.INVALID> > wrote: > > Hi Jithin > > This is the odd thing - when we try and add the vcenter datastore to ACS as > Primary storage - we do not have the 'preSetup' protocol option in the "add > primary storage" UI ? > > > Gary Dixon > Senior Technical Consultant > T: +44 161 537 4990 > E: v <tel:+44%207989717661>ms@quadris‑support.com > W: > http://www.q/ > uadris.co.uk%2F&data=05%7C01%7CGary.Dixon%40quadris.co.uk%7Cd2644af9a4 > 524ceecad408db81650536%7Cf1d6abf3d3b44894ae16db0fb93a96a2%7C0%7C0%7C63 > 8246043116409605%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VLMK7Hji4a > 8DH5MK0qurmLivru2LFr9e%2F%2BnOTm66jhU%3D&reserved=0 > > The information contained in this e-mail from Quadris may be confidential and > privileged for the private use of the named recipient. The contents of this > e-mail may not necessarily represent the official views of Quadris. If you > have received this information in error you must not copy, distribute or take > any action or reliance on its contents. Please destroy any hard copies and > delete this message. > -----Original Message----- > From: Jithin Raju <jithin.r...@shapeblue.com> > Sent: Monday, July 10, 2023 10:54 AM > To: users@cloudstack.apache.org > Subject: Re: ACS with vmware hypervisors > > Hi Gary, > > I am unable to tell the cause of the VM deployment failures with the log > snippets below. > Could you try adding the storage as a datastore in vCenter and add it to > CloudStack as ‘presetup’ ? > > -Jithin > > From: Gary Dixon <gary.di...@quadris.co.uk.INVALID> > Date: Monday, 10 July 2023 at 2:12 PM > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: RE: ACS with vmware hypervisors Hi Jithin > > We are using ACS 4.15.2 and vsphere esxi v7.0.3 > > This is the log output for job-42701: > > 2023-07-07 14:10:48,968 INFO [o.a.c.f.j.i.AsyncJobMonitor] > (API-Job-Executor-13:ctx-36699a50 job-42701) (logid:717a5506) Add > job-42701 into job monitoring > 2023-07-07 14:10:49,189 INFO [o.a.c.a.c.u.v.StartVMCmd] > (API-Job-Executor-13:ctx-36699a50 job-42701 ctx-a057c849) > (logid:96c5f242) > com.cloud.exception.InsufficientServerCapacityException: Unable to > create a deployment for VM[User|i-2-3207-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 > 2023-07-07 14:10:49,189 INFO [o.a.c.a.c.u.v.StartVMCmd] > (API-Job-Executor-13:ctx-36699a50 job-42701 ctx-a057c849) > (logid:96c5f242) Unable to create a deployment for > VM[User|i-2-3207-VM] > 2023-07-07 14:10:49,210 INFO [o.a.c.f.j.i.AsyncJobMonitor] > (API-Job-Executor-13:ctx-36699a50 job-42701) (logid:96c5f242) Remove > job-42701 from job monitoring > > Do we also need to add the iSCSI datatstore in vcenter as Primary storage to > cloudstack UI? > > BR > > Gary > Gary Dixon > Senior Technical Consultant > T: +44 161 537 4990 > E: v<tel:+44%207989717661>ms@quadris‑support.com > W: > http://www.q/ > uadris.co.uk%2F&data=05%7C01%7CGary.Dixon%40quadris.co.uk%7Cd2644af9a4 > 524ceecad408db81650536%7Cf1d6abf3d3b44894ae16db0fb93a96a2%7C0%7C0%7C63 > 8246043116409605%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VLMK7Hji4a > 8DH5MK0qurmLivru2LFr9e%2F%2BnOTm66jhU%3D&reserved=0 > [cid:image458271.png@D68BB0C8.6CA2D3B5] > The information contained in this e-mail from Quadris may be confidential and > privileged for the private use of the named recipient. The contents of this > e-mail may not necessarily represent the official views of Quadris. If you > have received this information in error you must not copy, distribute or take > any action or reliance on its contents. Please destroy any hard copies and > delete this message. > > > > -----Original Message----- > From: Jithin Raju <jithin.r...@shapeblue.com> > Sent: Monday, July 10, 2023 5:12 AM > To: users@cloudstack.apache.org > Subject: Re: ACS with vmware hypervisors > > Hi Gary, > > What are the ACS and Vmware ESXi versions you are using? Could you share the > entire logs for this day or job-42701? > > -Jithin > > From: Gary Dixon <gary.di...@quadris.co.uk.INVALID> > Date: Friday, 7 July 2023 at 8:49 PM > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: ACS with vmware hypervisors > > > > > > > I was wondering if anyone has any experience with ACS and vmware ESXi as the > hypervisor? I'm facing a problem when trying to deploy a new/fresh instance. > > I've deployed a vCenter appliance, created a data centre, cluster(s) and the > hosts have all been added to ACS. When I attempt to deploy a fresh instance > to the vmware cluster/hosts to build the OS from an ISO, the following errors > are displayed/logged: > > UI Error: > > Unable to create a deployment for VM[User|i-2-3207-VM] > > Management Log: > > ..about 1/2 way into the error " at > com.sun.proxy.$Proxy181.startVirtualMachine(Unknown Source)" is logged. > > 023-07-07 14:10:49,189 INFO [o.a.c.a.c.u.v.StartVMCmd] > (API-Job-Executor-13:ctx-36699a50 job-42701 ctx-a057c849) > (logid:96c5f242) Unable to create a deployment for > VM[User|i-2-3207-VM] > com.cloud.exception.InsufficientServerCapacityException: Unable to > create a deployment for VM[User|i-2-3207-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.rese > rveVirtualMachine(VMEntityManagerImpl.java:225) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl > .reserve(VirtualMachineEntityImpl.java:202) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.j > ava:4937) at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.j > ava:2897) at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeM > ethodAccessorImpl.java:62) at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Del > egatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflectio > n(AopUtils.java:344) at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoi > npoint(ReflectiveMethodInvocation.java:198) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(R > eflectiveMethodInvocation.java:163) > at > org.apache.cloudstack.network.contrail.management.EventUtils$EventInte > rceptor.invoke(EventUtils.java:107) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(R > eflectiveMethodInvocation.java:175) > at > com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.j > ava:51) at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(R > eflectiveMethodInvocation.java:175) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke > (ExposeInvocationInterceptor.java:97) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(R > eflectiveMethodInvocation.java:186) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamic > AopProxy.java:215) at > com.sun.proxy.$Proxy181.startVirtualMachine(Unknown Source) at > org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCm > d.java:169) at > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156) > at > com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java: > 108) at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInC > ontext(AsyncJobManagerImpl.java:620) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Man > agedContextRunnable.java:48) at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.cal > l(DefaultManagedContext.java:55) at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callW > ithContext(DefaultManagedContext.java:102) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWi > thContext(DefaultManagedContext.java:52) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(Manag > edContextRunnable.java:45) at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(As > yncJobManagerImpl.java:568) at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executor > s.java:515) at > java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool > Executor.java:1128) at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo > lExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) > > Gary Dixon > Senior Technical Consultant > T: +44 161 537 4990 > E: v<tel:+44%207989717661>ms@quadris‑support.com > W: > http://www.q/ > uadris.co.uk%2F&data=05%7C01%7CGary.Dixon%40quadris.co.uk%7Cd2644af9a4 > 524ceecad408db81650536%7Cf1d6abf3d3b44894ae16db0fb93a96a2%7C0%7C0%7C63 > 8246043116409605%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VLMK7Hji4a > 8DH5MK0qurmLivru2LFr9e%2F%2BnOTm66jhU%3D&reserved=0 > [cid:image013124.png@F2392D3B.75942D07] > The information contained in this e-mail from Quadris may be confidential and > privileged for the private use of the named recipient. The contents of this > e-mail may not necessarily represent the official views of Quadris. If you > have received this information in error you must not copy, distribute or take > any action or reliance on its contents. Please destroy any hard copies and > delete this message. > > > -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.