4 Commits

Author	SHA1	Message	Date
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.	2016-11-10 13:59:58 +01:00
nyankichi820	d1eadd91bb	Fix cloudstack builder (#4139) ... * add zone id when associate ip address in cloudstack * configure keypair * fix bug firewall port	2016-11-10 13:21:08 +01:00
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.	2016-11-04 09:56:49 +01:00
Sander van Harmelen	dbf3bf56d4	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00