.
Thanks,
Pearl
From: Daan Hoogland
Sent: Friday, January 28, 2022 9:29 PM
To: dev
Cc: us...@cloudstack.apache.org
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0
+1 (binding)
performed similar tests as Rohit but in a dual zone and
+1 (binding)
I’m basing my vote on Vladi’s testing because I did not had a chance to look at
it.
From: Vladimir Petrov
Date: Monday, 31 January 2022, 18:34
To: us...@cloudstack.apache.org ,
dev@cloudstack.apache.org
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0
+1
+1
I tested all resources (create/modify/destroy operations) on KVM, XCPNG 8.2 and
VMWare 6.7u3 and ACS versions 4.14. 4.15 and 4.16. I think it's working pretty
fine and it will be a great milestone in the ACS - Terraform integration.
Best wishes,
Vladimir
Harikrishna Patnala wrote:
Hi Al
land
Sent: Friday, January 28, 2022 9:29 PM
To: dev
Cc: us...@cloudstack.apache.org
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0
+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 zo
c: us...@cloudstack.apache.org
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0
+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
+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
+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
Hi all,
I'm updating links of the git commit SHA and release tag to point to the Apache
repository (https://github.com/apache/cloudstack-terraform-provider).
We had previously agreed to develop and publish releases on
apache/cloudstack-terraform-provider repository and use
cloudstack/terraform
