delete port forwarding when VM is deleted#469
Conversation
|
incubator-brooklyn-pull-requests #692 FAILURE |
33b94a8 to
5ea091f
Compare
|
incubator-brooklyn-pull-requests #696 FAILURE |
5ea091f to
6507550
Compare
|
incubator-brooklyn-pull-requests #698 FAILURE |
6507550 to
9680a02
Compare
|
incubator-brooklyn-pull-requests #703 SUCCESS |
|
An additional test which creates two machines, releases one machine then checks if the port mappings for the other machine are still around would be nice. Other than that, LGTM, tests pass |
- Adds JcloudsPortForwarderExtension.closePortForwarding - Adds PortForwardManager.forgetPortMappings(publicIpId) - Fix jcloudsSshMachineLocation.getSshHostAndPort() - Replace JcloudsPortforwardingLiveTest with JcloudsPortForwardingStubbedLiveTest
9680a02 to
e1b35c5
Compare
|
Thanks @nakomis - I've rebased, then added a test for two VMs (ensuring that releasing first does not impact second). Merging. |
|
incubator-brooklyn-pull-requests #711 SUCCESS |
This includes commits from #468 - please review+merge that first.