Instead of running an instance on a network, we can also explicitly
create the port first, and then launch the instance on that port.
In this case, we give the port a name, which is not mandatory.
At this point, the port doesn't have a device owner,
because nothing uses this port; however, it does have addresses,
an IP address and a MAC address. Now we can launch an instance on that port.
The option here is port-id instead of net-id.
I pick up the ports ID, and paste it in here.
Let me check the instance, and it's running.
In the Network Topology, you can see the two instances, and of course
right now our titan network is not yet connected to the public network.
Note also that the network topology does not really show us the ports.
To see them, we either have to go back to the commandline,
let me check again the details of our new port, port-titan2.
You can see that it now has a device owner, and as expected, it's an instance.
You can do the same on the GUI, I click now here on the titan network,
and look at its details. You can see here the Ports tab, and here as
well, we can see the list of the ports. These are the ports of the
titan network only. And a bit further down, we also see the device owner.
As the last step, let's see how we can delete all these things that we created.
I'm going to start with the servers. And now that no server is using
the network anymore, I should be able to delete the network as well.
That didn't work, and the error message is not very conclusive, I think.
Perhaps I first have to delete the subnet, that's the same.
Well, the answer here is that we still have a port that we created.
The DHCP port, that's the second port in this list, will be deleted
automatically when I delete the network, but the port that I created,
port-titan2, will not, so I have to delete it explicitly.
And after that, I can remove the network without any problem.
A quick check in the GUI whether that was successful, and you can see
we are back to square one, only the public network remains.