Add or Remove a CNF to a Running or Failed-Temp Network Service

Operators can modify a running service by adding or removing a CNF to a service in the RUNNING or FAILED-TEMP state. While adding a CNF, it is possible to edit the VNF with specific customizations.

  1. On the Launchpad menu, click SERVICES > FULL LIST to open the list of NS instances.

  2. Click next to the NS that you want to see in more detail. The VIEWPORT screen opens.

  3. Click to open the Service Update widget and provide the select-update details.

  4. In the Update Operation Choice drop-down menu, either choose instantiate-cnf or remove-cnf.

Insert a CNF into a Running or Failed-Temp Service

The steps and screenshots in this section are based on the ping pong sample application. This specific workflow is determined by the selected CNFD and NSD associated with the running service.

  1. After choosing instantiate-cnf, additional fields appear. Provide the select-update details to insert a VNF into a Running Service:

    • CNFD - CNFD to insert. The options include the CNFDs from the project’s catalog.

    • Member - ID for the CNF. This is the member-id-ref field.

    Note: The YAML configuration appears on the right side of the screen for each section.

  2. Click Next>> to provide the following details in the Scripts step to identify which scripts that you want to add to the service:

    • File Path 1 - File including the relative path in the package. After you type the file name, additional fields appear.

      Note: You must specify the script folder in this field. 

    • External URL - BROWSE or type the URL: URL to download. You can either browse or type your URL and add the script to the subfolder that you defined in the File path field.

    • Username - Username if the url uses authentication.

    • Password - Password if the url uses authentication.

    • Overwrite - Overwrite the username and password in this field by choosing False (True or False)

    Note: If you have additional scripts, then type the path in File Path 2 and the same fields will appear for the subsequent scripts.

  3. Click Next>> to provide the following details in the Connections step:

    The fields listed in the Connections section are the VLDs in the NSD. If you add connections, then the connections points are linked to a VL. 

    Note: When you choose a connection point in the first drop-down, it will not appear in the second drop-down section.

  4. Click Next>> to provide the following details in the initial-service-primitive step:

    Note: This step is optional.

    • Name 1 - Name of the configuration primitive. After you type the configuration name, additional fields appear.

    • Seq - Sequence number for the configuration primitive.

    • User Defined Script - Select the script file to be executed from the drop-down menu. The options include:

      • script files that are already included in the NSD.

      • any script files added using this update process (file path scripts)

    • Parameter - List of parameter settings (param=value).

    Note: If you have additional initial-service-primitive, then type the name in Name 2 and the same fields will appear for the subsequent initial-service-primitives.

  5. Click Next>> to provide details in the terminate-service-primitive, add-vnf-service-primitive and service-primitive steps. These steps include all same details as the initial-service-primitive step.

    Note: These steps are optional.

  6. Click Next>> to provide the following details in the Placement step:

    • Datacenter - A datacenter select box appears if there is more than one available datacenter to pick in this option. The options in this section are dependent on the configuration of the selected datacenter. You may be able to specify a region, an availability zone and host aggregate meta-data.

    Note: This step only appears if the CNFD had defined a placement group. The options in this step can also change slightly depending on your selected datacenter.

  7. Click Next>> to provide the following details in the config-input step:

    • Xpath 1 - Select the CNFD property to set from the drop-down menu. After you choose the xpath, additional fields appear. The xpath options are dependent on the definition of the CNF that you are adding to your NS. These options are the same as the options available if you configure an input-parameter-xpath in the NSD designer.

    • Value - Value to set on property.

    Note: If you have additional xpaths, then choose the xpath in the Xpath 2 drop-down menu and the same fields will appear for the subsequent xpaths.

  8. Click Next>> to provide the following details in the monitoring-params step:

    • Id 1 - Id of monitoring parameter. After you type the ID, additional fields appear.

    • CNFD Monitoring Param - Select the VNFD monitoring parameters to connect from the drop-down menu.

    • Aggregation Type - Select the aggregation type from the drop-down menu. The options include:

      • AVERAGE

      • MINIMUM

      • MAXIMM

      • COUNT

      • SUM

    • Value Type - Select the value type from the drop-down menu. The options include:

      • INT

      • DECIMAL

      • STRING

    • Value Integer - Current value for an integer parameter.

    • Value Decimal - Current value for a decimal parameter.

    • Value String - Current value for a string parameter.

    • Description - Type the description for the monitoring parameter.

    • Group Tag - A tag to group monitoring parameters.

    • Widget Type - Select the widget type to define the UI display variant of measured counters. The options include:

      • COUNTER

      • GAUGE

      • TEXTBOX

      • SLIDER

      • HISTOGRAM

      • BAR

    • Units - Measured Counter Units (e.g., Packets, Kbps, Mbps, etc.)

      Note: If you have additional monitoring parameter IDs, then type the ID in the ID 2 field and the same fields will appear for the subsequent monitoring parameters.

  9. Click UPDATE. The Service > Viewport shows the progress of the heal operation under the service name. The new CNF appears on the Viewport screen.

  10. If the instantiate-cnf attempt fails, then an Insert Failure error message appears in the Service Update widget. The CNF will also indicate that the attempt failed on the Viewport screen.

Remove a CNF from a Running or Failed-Temp Service

  1. Choose remove-cnfthen click on which Constituent CNF to remove. The constituent CNF options include the CNFs that are currently part of the running Service.

  2. Click Next>> to provide the following details in the Scripts step to identify which scripts that you want to remove from the service:

    • File Path 1 - File including the relative path in the package. After you type the file name, additional fields appear.

      Note: You must specify the script folder in this field. 

    • External URL - BROWSE or type the URL: URL to download. You can either browse or type your URL and add the script to the subfolder that you defined in the File path field.

    • Username - Username if the url uses authentication.

    • Password - Password if the url uses authentication.

    • Overwrite - Overwrite the username and password in this field by choosing False (True or False)

    Note: If you have additional scripts, then type the path in File Path 2 and the same fields will appear for the subsequent scripts.

  3. Click Next>> to provide the following details in the initial-service-primitive step:

    Note: This step is optional.

    • Name 1 - Name of the configuration primitive. After you type the configuration name, additional fields appear.

    • Seq - Sequence number for the configuration primitive.

    • User Defined Script - Select the script file to be executed.

    • Parameter - List of parameter settings (param=value).

      Note: If you have additional initial-service-primitive, then type the name in Name 2 and the same fields will appear for the subsequent initial-service-primitives.

  4. Click Next>> to provide the details in the terminate-service-primitive and remove-nf-service-primitive steps. These steps include all same details as the initial-service-primitive step.

    Note: This step is optional.

  5. Click UPDATE. The Service > Viewport shows the progress of the update operation under the service name. The CNF no longer appears on the Viewport screen.

    If the remove-cnf attempt fails, then an Insert Failure error message appears in the Service Update widget. The CNF will also indicate that the attempt failed on the Viewport screen.