@@ -497,39 +497,6 @@ An existing server-group may be passed as an instantiation parameter to be used
Where the `id` of the `affinity-or-anti-affinity-group` is the one in the descriptor, and the `vim-affinity-group-id` is the guid of the existing server-group in Openstack to be used (instead of being created).
## Migrating VDUs in a Network Service
OSM allows the migration of VDUs, that are part of a VNF, across compute hosts.
- The following scenarios are possible:
- Migrating a single, specific VDU
- Migrating a specific VDU that is part of a scaling group
- Migrating all VDU instances in a VNF
The VDUs can be migrated across compute hosts. But, the new compute host should belong to the same availability zone as the current compute host that the VDU belongs to before migration. This is enforced to ensure the validity of placement-groups configuration even after migration.
In case, the new compute host is not provided, then a compute host would be selected automatically from the same availability zone.
### Additional Notes
OSM currently supports migration of VDUs for OpenStack VIM type only.
### Performing Migration from UI
In Migration, 'Member VNF Index' is the only mandatory parameter and it is used to identify the VNF to be migrated. If no other parameters are provided, then all the VDUs in the VNF are migrated appropriately.
To migrate a specific VDU that is part of a scaling group, both the 'VDU Id' and 'Count Index' parameters are to be provided. For VDUs that are not scaled, VDU-Id parameter would suffice.
To migrate to a specific host, 'Migrate To Host' parameter has to be provided. If it is not provided, then a compute host would be selected automatically.
- From the UI:
- Go to 'NS Instances' on the 'Instances' menu to the left
- Next, in the NS instance where the VNF to be migrated is a part of, click on the 'Action' button.
- From the dropdown actions, click on 'Vm Migration'
- Fill in the form, adding at least the member vnf index:
## Understanding Day-1 and Day-2 Operations
VNF configuration is done in three "days":
@@ -1730,3 +1697,38 @@ __Step 2: See the notification in notification receiver.__
- Support for subscription and notification for VNFD.
- Cache to store subscribers.
## Migrating VDUs in a Network Service
OSM allows the migration of VDUs, that are part of a VNF, across compute hosts.
The following scenarios are possible:
- Migrating a single, specific VDU
- Migrating a specific VDU that is part of a scaling group
- Migrating all VDU instances in a VNF
The VDUs can be migrated across compute hosts. But, the new compute host should belong to the same availability zone as the current compute host that the VDU belongs to before migration. This is enforced to ensure the validity of placement-groups configuration even after migration.
In case the new compute host is not provided, then a compute host would be selected automatically from the same availability zone.
### Additional Notes
OSM currently supports migration of VDUs for OpenStack VIM type only.
### Performing Migration from UI
In Migration, 'Member VNF Index' is the only mandatory parameter and it is used to identify the VNF to be migrated. If no other parameters are provided, then all the VDUs in the VNF are migrated appropriately.
To migrate a specific VDU that is part of a scaling group, both the 'VDU Id' and 'Count Index' parameters are required. For VDUs that are not scaled, VDU-Id parameter would suffice.
To migrate to a specific host, 'Migrate To Host' parameter has to be provided. If it is not provided, then a compute host would be selected automatically.
From the UI:
- Go to 'NS Instances' on the 'Instances' menu to the left
- Next, in the NS instance where the VNF to be migrated is a part of, click on the 'Action' button.
- From the dropdown actions, click on 'Vm Migration'
- Fill in the form, adding at least the member vnf index:
