Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

2022-01-28 Thread Rohit Yadav
+1 (binding) I checked the source tarball checksum and gpg signature, and using the RC1 build was able to test a simple VM deployment in a zone in an isolated network with some firewall rules applied, against a KVM based ACS 4.16.0.0 env. (note: in my testing, in the first run the firewall appl

Re: [!!Mass Mail]Re: Dynamically scalable VM

2022-01-28 Thread Harikrishna Patnala
You can check the host-param-list details to get the CPU sockets information on the XCP host. # xe host-param-list uuid= | grep -i cpu As mentioned below, if host's CPU sockets value is less than xen.vm.vcpu.max value, then host's CPU socket value is used to set max vCPUs of VM. Regards, Harik

[PROPOSE] RM for 4.17

2022-01-28 Thread Nicolas Vazquez
Dear All, I would like to put myself forward as the release manager for 4.17.0.0. I propose we have a window of at least 6 weeks to allow the community and users to test and report issues, I will propose the timeline details soon. I hope to have your support. Please let me know if you have any

Re: Duplicate device_id of datadisk

2022-01-28 Thread Daan Hoogland
Mikako, yes, I think you hit a bug. I am not sure if your application will be hurt by it, but of course it might well be. On Thu, Jan 27, 2022 at 2:13 PM 小林 美佳子 wrote: > > Hi. > I am using CloudStack 4.14. > I used importUnmanagedinstance to register the VM to CloudStack. > When there are multip

Re: [PROPOSE] RM for 4.17

2022-01-28 Thread Ivet Petrova
Nicolas, Just to mention you did a great job last time! Kind regards, On 28 Jan 2022, at 16:05, Nicolas Vazquez mailto:[email protected]>> wrote: Dear All, I would like to put myself forward as the release manager for 4.17.0.0. I propose we have a window of at least 6 weeks to

Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

2022-01-28 Thread Daan Hoogland
+1 (binding) performed similar tests as Rohit but in a dual zone and with a vpc in one of the zones. Two different configurations one with one zone and one with both. destroy went fine ;) in the vpc firewall rules would not create. I am not sure this is a known issue, but the error message is clea