a891252ae5
Moved k8S Container and OpenStack VNF sections into respective subdirs following "kubernetes" and "openstack" conventions under guest_integration and added shared index. This follows pattern used for other docs. Rebase merge conflicts, formatting corrections and removed 2x NA files Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ic56322108cdb03ab1f9e4dadf5f50fe20cd7b2d6 Signed-off-by: Ron Stone <ronald.stone@windriver.com>
42 lines
1006 B
ReStructuredText
42 lines
1006 B
ReStructuredText
|
|
.. nie1614092105640
|
|
.. _remove-ptp-notifications:
|
|
|
|
========================
|
|
Remove PTP Notifications
|
|
========================
|
|
|
|
You can remove all pods and Kubernetes resources created during the Armada
|
|
application deployment.
|
|
|
|
|
|
Use the following procedure to remove |PTP| notifications.
|
|
|
|
|
|
.. rubric:: |proc|
|
|
|
|
|
|
.. _remove-ptp-notifications-steps-klx-gnf-t4b:
|
|
|
|
#. Remove all pods and other Kubernetes resources created during the Armada
|
|
deployment, using the following command:
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)]$ system application-remove ptp-notification
|
|
|
|
#. Delete the ptp-notification from sysinv.
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)]$ system application-delete ptp-notification
|
|
|
|
#. Remove labels applied to controller-0, using the following commands, for example:
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)]$ system host-label-remove controller-0 ptp-notification
|
|
~(keystone_admin)]$ system host-label-remove controller-0 ptp-registration
|
|
|
|
|