5 Commits (285ff6940ef3cfb26fbaf407f305b8f7f4e08832)

Author	SHA1	Message	Date
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