11 Commits (d9b404fa00a52c8d02660008ffd73fcc0fe902bc)

Author	SHA1	Message	Date
Rickard von Essen	1bf8a0c6a1	cloudstack: Move ipaddress and host port to state	9 years ago
Rickard von Essen	44089b2f55	cloudstack: Improved error reporting ... Ensure that errors are shown when they happens.	9 years ago
Sander van Harmelen	3f444997b2	Make expunge optional and improve logging output (#5099)	9 years ago
Sander van Harmelen	c4ef9bcd3f	Make sure we always print and return any errors	9 years ago
Yamashita, Yuu	ab4636ae0f	Explicitly specify `zoneid` in CloudStack's `associateIpAddress` call (#4995) ... Generally speaking, this must be harmless since the IP address and the virtual machine need to be deployed to the same zone.	9 years ago
Matthew Hooker	81522dced0	move packer to hashicorp	9 years ago
Sander van Harmelen	285ff6940e	Revert some changes made in #4149 (#4175) ... After some more research and testing it turns out we can support the use case where you want to reuse an associated IP address that already has port 22 or 5985 forwarded, by using a random public port. The correct port to open in the firewall is different for the type of firewall used. The standard firewall requires the public port to be opened and the network ACL requires the private port to be opened. So by partially reverting this code and updating which ports to open in which cases, we can support all use cases again.	9 years ago
Sander van Harmelen	68c6835bb5	Do not create a random public port (#4149) ... This is meant to be a gentle solution for a very specific use case, but is causing more issues then it solves. If you have a port conflict when trying to use an already associated public IP, the easiest way around it is to let the builder associate a new temporary public IP address.	9 years ago
nyankichi820	d1eadd91bb	Fix cloudstack builder (#4139) ... * add zone id when associate ip address in cloudstack * configure keypair * fix bug firewall port	9 years ago
Sander van Harmelen	33f430bf25	Use the private port for the firewall rules (#4114) ... Because of how CloudStack configures the firerwall on the router VM, you need to allow traffic to the private port instead of the public port.	9 years ago
Sander van Harmelen	dbf3bf56d4	Add a CloudStack Builder	9 years ago