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
..
artifact.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
artifact_test.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
builder.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
builder_test.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
config.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
config_test.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
ssh.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
step_configure_networking.go	Do not create a random public port (#4149)	2016-11-10 13:59:58 +01:00
step_create_instance.go	Do not create a random public port (#4149)	2016-11-10 13:59:58 +01:00
step_create_template.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
step_prepare_config.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00
step_shutdown_instance.go	Add a CloudStack Builder	2016-10-16 15:29:18 +02:00