You must mention
start, stop or reboot in the operation field.
Start VNF: Starts
all VMs, enables monitoring, and reassigns thresholds according the KPI
details. The VMs start running and move to VM_ALIVE_STATE. The service will be
in service_active state. Only undeploy can interrupt the start VNF workflow.
Stop VNF: Once the
service is stopped, monitoring is disabled and all the VM services are stopped.
The VMs are no longer available. The service will be in service_stopped_state.
VM will be in shutoff_state. You cannot perform any recovery, scale up, scale
down. You can only undeploy the VNFs.
Disables monitoring, reboots all VMs, that is stop and then start in OpenStack,
enables monitoring, and reassigns thresholds according to KPI details. The VM
is in VM_ALIVE_STATE and the service is in service_alive_state. Only undeploy
can interrupt the reboot operation.
You cannot start
monitoring a VNF which is already running. After a reboot, logging back into
the VM must indicate the reboot, update and monitoring details. It must also
Similar to VNF
operations, you can start, stop and reboot individual VMs.
A payload is
required for VM operations: