|
|
|
It is possible that during development, a VNF was deployed, but not properly cleaned up. This can result in the port having been allocated in ETSI Openstack VIM, but never removed. While this should not be any issue, the following procedure can be used to remove ports that have been left in this state.
|
|
|
|
|
|
|
|
Note: the `vnfonb_admin` tenant is being used for all Openstack access.
|
|
|
|
|
|
|
|
## Removal of Floating IPs
|
|
|
|
|
|
|
|
Typically the osm-ext network provides direct access to the VM, but it is possible a floating ip was allocated and given to a VM that was on a private network is routed from osm-ext. These floating IPs should be removed periodically. To search for floating IPs, use the following:
|
|
|
|
|
|
|
|
```
|
|
|
|
openstack floating ip list --long | grep DOWN
|
|
|
|
```
|
|
|
|
|
|
|
|
All of these floating IP ports can be removed:
|
|
|
|
|
|
|
|
```
|
|
|
|
openstack floating ip list --long | grep DOWN | awk '{print $2}' | xargs openstack floating ip delete
|
|
|
|
```
|
|
|
|
|
|
|
|
## Removal of Unused Ports
|
|
|
|
|
|
|
|
The full list of all ports that are not in use can be seen with this command
|
|
|
|
|
|
|
|
```
|
|
|
|
openstack port list --long | grep DOWN
|
|
|
|
```
|
|
|
|
|
|
|
|
Using this, all unused ports can be cleaned up
|
|
|
|
|
|
|
|
```
|
|
|
|
openstack port list --long | grep DOWN | awk '{print $2}' | xargs openstack port delete
|
|
|
|
``` |
|
|
\ No newline at end of file |