You can reboot a cloudpipe vpn through the api
if something goes wrong (using nova
reboot for example), but if you
generate a new crl, you will have to terminate it
and start it again using the cloudpipe extension.
The cloudpipe instance always gets the first ip in
the subnet and if force_dhcp_release is not set it
takes some time for the ip to be recovered. If you
try to start the new vpn instance too soon, the
instance will fail to start because of a
"NoMoreAddresses" error. It is therefore
recommended to use
force_dhcp_release.
The keypair that was used to launch the
cloudpipe instance should be in the
keys/
folder. You can use this key to log into the
cloudpipe instance for debugging purposes. If you
are running multiple copies of nova-api this key
will be on whichever server used the original
request. To make debugging easier, you may want to
put a common administrative key into the cloudpipe
image that you create.<project_id>
