date:20211126

Re: Unable to create a deployment for VM

2021-11-26 Thread technologyrss.mail


Yes, Thank you so much, You find out exact reason. Now I fix this issue.

:)

Thanks again.

On 11/27/2021 12:46 AM, Wei ZHOU wrote:

Hi,

This is indeed a capacity issue with memory (capacity Type : 0).

2021-11-26 18:47:42,550 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Searching all possible resources under this Zone: 1
2021-11-26 18:47:42,554 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Listing clusters in order of aggregate capacity, that have (at least 
one host with) enough CPU and RAM capacity under this Zone: 1
2021-11-26 18:47:42,561 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Removing from the clusterId list these clusters from avoid set: []
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Cannot allocate cluster list [1] for vm creation since their allocated 
percentage crosses the disable capacity threshold defined at each 
cluster/ at global value for capacity Type : 0, skipping these clusters
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
No clusters found after removing disabled clusters and clusters in 
avoid list, returning.
2021-11-26 18:47:42,590 DEBUG [c.c.v.UserVmManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Destroying vm VM[User|i-2-3-VM] as it failed to create on Host with 
Id:null


-Wei

On Fri, 26 Nov 2021 at 14:40, technologyrss.mail 
 wrote:


Please download and see full log from ACS


https://drive.google.com/file/d/1BEB6HYgI8VWTjg9rwk3BZlfLlpPaRzZL/view?usp=sharing

Thank you so much.

On 11/26/2021 7:18 PM, Wei ZHOU wrote:

Hi,

Normally it is not a capacity issue. It might be caused by the systemvm
template, VR, etc. Please share the full log (from job-16 is started).

-Wei

On Fri, 26 Nov 2021 at 14:12, technologyrss.mail <
technologyrss.m...@gmail.com> wrote:


*Hi, *

Please see error log:

(logid:9bd01412) Searching all possible resources under this Zone: 1
2021-11-26 18:47:42,554 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Listing clusters in order of aggregate capacity, that have (at least one
host with) enough CPU and RAM capacity under this Zone: 1
2021-11-26 18:47:42,561 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Removing from the clusterId list these clusters from avoid set: []
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Cannot allocate cluster list [1] for vm creation since their allocated
percentage crosses the disable capacity threshold defined at each
cluster/ at global value for capacity Type : 0, skipping these clusters
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
No clusters found after removing disabled clusters and clusters in avoid
list, returning.
2021-11-26 18:47:42,590 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Destroying vm VM[User|i-2-3-VM] as it failed to create on Host with Id:null
2021-11-26 18:47:42,626 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
VM state transitted from :Stopped to Error with event:
OperationFailedToErrorvm's original host id: null new host id: null host
id before state transition: null
2021-11-26 18:47:42,659 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = volume count for Account = 2 Operation =
decreasing Amount = 1
2021-11-26 18:47:42,680 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = primary_storage count for Account = 2 Operation
= decreasing Amount = (20.00 GB) 21474836480
2021-11-26 18:47:42,714 WARN  [c.c.a.AlertManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
AlertType:: 8 | dataCenterId:: 1 | podId:: null | clusterId:: null |
message:: Failed to deploy Vm with Id: 3, on Host with Id: null
2021-11-26 18:47:42,727 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = user_vm count for Account = 2 Operation =
decreasing Amount = 1
2021-11-26 18:47:42,737 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412

Re: Unable to create a deployment for VM

2021-11-26 Thread technologyrss.mail


Please download and see full log from ACS

https://drive.google.com/file/d/1BEB6HYgI8VWTjg9rwk3BZlfLlpPaRzZL/view?usp=sharing

Thank you so much.

On 11/26/2021 7:18 PM, Wei ZHOU wrote:

Hi,

Normally it is not a capacity issue. It might be caused by the systemvm
template, VR, etc. Please share the full log (from job-16 is started).

-Wei

On Fri, 26 Nov 2021 at 14:12, technologyrss.mail <
technologyrss.m...@gmail.com> wrote:


*Hi, *

Please see error log:

(logid:9bd01412) Searching all possible resources under this Zone: 1
2021-11-26 18:47:42,554 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Listing clusters in order of aggregate capacity, that have (at least one
host with) enough CPU and RAM capacity under this Zone: 1
2021-11-26 18:47:42,561 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Removing from the clusterId list these clusters from avoid set: []
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Cannot allocate cluster list [1] for vm creation since their allocated
percentage crosses the disable capacity threshold defined at each
cluster/ at global value for capacity Type : 0, skipping these clusters
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
No clusters found after removing disabled clusters and clusters in avoid
list, returning.
2021-11-26 18:47:42,590 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Destroying vm VM[User|i-2-3-VM] as it failed to create on Host with Id:null
2021-11-26 18:47:42,626 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
VM state transitted from :Stopped to Error with event:
OperationFailedToErrorvm's original host id: null new host id: null host
id before state transition: null
2021-11-26 18:47:42,659 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = volume count for Account = 2 Operation =
decreasing Amount = 1
2021-11-26 18:47:42,680 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = primary_storage count for Account = 2 Operation
= decreasing Amount = (20.00 GB) 21474836480
2021-11-26 18:47:42,714 WARN  [c.c.a.AlertManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
AlertType:: 8 | dataCenterId:: 1 | podId:: null | clusterId:: null |
message:: Failed to deploy Vm with Id: 3, on Host with Id: null
2021-11-26 18:47:42,727 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = user_vm count for Account = 2 Operation =
decreasing Amount = 1
2021-11-26 18:47:42,737 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = cpu count for Account = 2 Operation =
decreasing Amount = 1
2021-11-26 18:47:42,748 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Updating resource Type = memory count for Account = 2 Operation =
decreasing Amount = 1024
2021-11-26 18:47:42,768 INFO  [o.a.c.a.c.u.v.DeployVMCmd]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
com.cloud.exception.InsufficientServerCapacityException: Unable to
create a deployment for VM[User|i-2-3-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
2021-11-26 18:47:42,768 INFO  [o.a.c.a.c.u.v.DeployVMCmd]
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
Unable to create a deployment for VM[User|i-2-3-VM]
com.cloud.exception.InsufficientServerCapacityException: Unable to
create a deployment for VM[User|i-2-3-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
  at

org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:225)
  at

org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:202)
  at

com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4929)
  at

com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4466)
  at

com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4455)
  at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
  at

java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at

java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.base/java.lang.reflect.Method.invoke(Method.java:566)
  at

org.spri

Re: Unable to create a deployment for VM

2021-11-26 Thread Wei ZHOU

Hi,

Normally it is not a capacity issue. It might be caused by the systemvm
template, VR, etc. Please share the full log (from job-16 is started).

-Wei

On Fri, 26 Nov 2021 at 14:12, technologyrss.mail <
technologyrss.m...@gmail.com> wrote:

> *Hi, *
>
> Please see error log:
>
> (logid:9bd01412) Searching all possible resources under this Zone: 1
> 2021-11-26 18:47:42,554 DEBUG [c.c.d.FirstFitPlanner]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Listing clusters in order of aggregate capacity, that have (at least one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2021-11-26 18:47:42,561 DEBUG [c.c.d.FirstFitPlanner]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Removing from the clusterId list these clusters from avoid set: []
> 2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Cannot allocate cluster list [1] for vm creation since their allocated
> percentage crosses the disable capacity threshold defined at each
> cluster/ at global value for capacity Type : 0, skipping these clusters
> 2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> No clusters found after removing disabled clusters and clusters in avoid
> list, returning.
> 2021-11-26 18:47:42,590 DEBUG [c.c.v.UserVmManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Destroying vm VM[User|i-2-3-VM] as it failed to create on Host with Id:null
> 2021-11-26 18:47:42,626 DEBUG [c.c.c.CapacityManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> VM state transitted from :Stopped to Error with event:
> OperationFailedToErrorvm's original host id: null new host id: null host
> id before state transition: null
> 2021-11-26 18:47:42,659 DEBUG [c.c.r.ResourceLimitManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Updating resource Type = volume count for Account = 2 Operation =
> decreasing Amount = 1
> 2021-11-26 18:47:42,680 DEBUG [c.c.r.ResourceLimitManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Updating resource Type = primary_storage count for Account = 2 Operation
> = decreasing Amount = (20.00 GB) 21474836480
> 2021-11-26 18:47:42,714 WARN  [c.c.a.AlertManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> AlertType:: 8 | dataCenterId:: 1 | podId:: null | clusterId:: null |
> message:: Failed to deploy Vm with Id: 3, on Host with Id: null
> 2021-11-26 18:47:42,727 DEBUG [c.c.r.ResourceLimitManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Updating resource Type = user_vm count for Account = 2 Operation =
> decreasing Amount = 1
> 2021-11-26 18:47:42,737 DEBUG [c.c.r.ResourceLimitManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Updating resource Type = cpu count for Account = 2 Operation =
> decreasing Amount = 1
> 2021-11-26 18:47:42,748 DEBUG [c.c.r.ResourceLimitManagerImpl]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Updating resource Type = memory count for Account = 2 Operation =
> decreasing Amount = 1024
> 2021-11-26 18:47:42,768 INFO  [o.a.c.a.c.u.v.DeployVMCmd]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a deployment for VM[User|i-2-3-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2021-11-26 18:47:42,768 INFO  [o.a.c.a.c.u.v.DeployVMCmd]
> (API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412)
> Unable to create a deployment for VM[User|i-2-3-VM]
> com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a deployment for VM[User|i-2-3-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
>  at
>
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:225)
>  at
>
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:202)
>  at
>
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4929)
>  at
>
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4466)
>  at
>
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4455)
>  at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>  at
>
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at
>
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>  at
>
> org.springframework.aop.support.A

Unable to create a deployment for VM

2021-11-26 Thread technologyrss.mail


*Hi, *

Please see error log:

(logid:9bd01412) Searching all possible resources under this Zone: 1
2021-11-26 18:47:42,554 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Listing clusters in order of aggregate capacity, that have (at least one 
host with) enough CPU and RAM capacity under this Zone: 1
2021-11-26 18:47:42,561 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Removing from the clusterId list these clusters from avoid set: []
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Cannot allocate cluster list [1] for vm creation since their allocated 
percentage crosses the disable capacity threshold defined at each 
cluster/ at global value for capacity Type : 0, skipping these clusters
2021-11-26 18:47:42,582 DEBUG [c.c.d.FirstFitPlanner] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
No clusters found after removing disabled clusters and clusters in avoid 
list, returning.
2021-11-26 18:47:42,590 DEBUG [c.c.v.UserVmManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Destroying vm VM[User|i-2-3-VM] as it failed to create on Host with Id:null
2021-11-26 18:47:42,626 DEBUG [c.c.c.CapacityManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
VM state transitted from :Stopped to Error with event: 
OperationFailedToErrorvm's original host id: null new host id: null host 
id before state transition: null
2021-11-26 18:47:42,659 DEBUG [c.c.r.ResourceLimitManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Updating resource Type = volume count for Account = 2 Operation = 
decreasing Amount = 1
2021-11-26 18:47:42,680 DEBUG [c.c.r.ResourceLimitManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Updating resource Type = primary_storage count for Account = 2 Operation 
= decreasing Amount = (20.00 GB) 21474836480
2021-11-26 18:47:42,714 WARN  [c.c.a.AlertManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
AlertType:: 8 | dataCenterId:: 1 | podId:: null | clusterId:: null | 
message:: Failed to deploy Vm with Id: 3, on Host with Id: null
2021-11-26 18:47:42,727 DEBUG [c.c.r.ResourceLimitManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Updating resource Type = user_vm count for Account = 2 Operation = 
decreasing Amount = 1
2021-11-26 18:47:42,737 DEBUG [c.c.r.ResourceLimitManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Updating resource Type = cpu count for Account = 2 Operation = 
decreasing Amount = 1
2021-11-26 18:47:42,748 DEBUG [c.c.r.ResourceLimitManagerImpl] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Updating resource Type = memory count for Account = 2 Operation = 
decreasing Amount = 1024
2021-11-26 18:47:42,768 INFO  [o.a.c.a.c.u.v.DeployVMCmd] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|i-2-3-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
2021-11-26 18:47:42,768 INFO  [o.a.c.a.c.u.v.DeployVMCmd] 
(API-Job-Executor-8:ctx-dfeedfec job-16 ctx-0f3c8323) (logid:9bd01412) 
Unable to create a deployment for VM[User|i-2-3-VM]
com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|i-2-3-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
    at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:225)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:202)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4929)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4466)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4455)
    at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
    at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
    at 
org.apache.cloudstack.network.contrail.management.EventUtils$Event

Re: host cache

2021-11-26 Thread Suresh Anaparti

Hi Piotr,

These options are supported for KVM only (in 4.16). Details below.

vm.configdrive.primarypool.enabled: zone level configuration -  if enabled, the 
config drives are created and hosted on a primary storage pool.

vm.configdrive.force.host.cache.use: zone level configuration - if enabled, 
host cache path is used for the config drives.

vm.configdrive.use.host.cache.on.unsupported.pool: zone level configuration -  
if enabled, host cache path is used for config drives when 
'vm.configdrive.primarypool.enabled' is enabled and the storage pool doesn't 
support config drive (mainly managed storages).


The host cache path can be specified using "host.cache.location" parameter in 
/etc/cloudstack/agent/agent.properties file on the KVM host(s). The cache 
directory path will be used to host config drive ISOs for VMs, in configdrive 
directory in it. The default path is '/var/cache/cloud'.

 
Regards,
Suresh

On 25/11/21, 11:20 PM, "Piotr Pisz"  wrote:

Hi,



I noticed new options in 4.16:




vm.configdrive.force.host.cache.use













vm.configdrive.primarypool.enabled













vm.configdrive.use.host.cache.on.unsupported.pool







Could someone write more about what these options do?



Regards,

Piotr

Re: Setting up a DNS Name for console proxy ssl connection

2021-11-26 Thread Rohit Yadav

Hi Mevludin,

You need to define the consoleproxy.sslEnabled and consoleproxy.url.domain 
global settings and upload the SSL certificate via Infra -> SSL certificate 
form. Upon uploading of your certificate the CPVM should restart/reconfigure. 
Also make sure that the domain (if not a wildcard) is resolved to the public IP 
address of the CPVM. You don't need any port-specific configuration, but make 
sure to restart mgmt server after changing global settings, if necessary 
destroy the old CPVM after restart.

You can read more here: 
https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/

With 4.16, when the consoleproxy.sslEnabled is false but domain is defined then 
the CPVM url will open the console proxy url without enforcing https:// 
(however the https:// scheme will be enforced is mgmt server is accessed over 
https://). This can be used for doing out-of-band SSL termination, for ex. 
using a nginx proxy.


Regards.


From: Mevludin Blazevic 
Sent: Thursday, November 25, 2021 23:56
To: users@cloudstack.apache.org 
Subject: Setting up a DNS Name for console proxy ssl connection

Hi all,

is it enough to define just a DNS name for the console proxys public ip
address for enabling SSL? Let's say you define cpvm.mydomain.com as the
DNS name for the console proxy and also set this in the configs
"consoleproxy.url.domain" and "consoleproxy.sslEnabled" and upload an
appropriate certificate via the GUI, which is not a wildcard
certificate. When trying to access the console I get a 404 error. Did I
miss a redirection configuration somewhere from port 8080 to 443 (or 8443)?

Regards

Mevludin

Re: Unable to create a deployment for VM

Re: Unable to create a deployment for VM

Re: Unable to create a deployment for VM

Unable to create a deployment for VM

Re: host cache

Re: Setting up a DNS Name for console proxy ssl connection

6 matches

Site Navigation

Mail list logo

Footer information