aboutsummaryrefslogtreecommitdiffstats
path: root/samples/vnf_samples/nsut/cgnapt/cgnapt-tg-topology-ixia-multi-port.yaml
blob: 91d257fd4287ba25d6546f2fe9d378d52b2501e2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
# Copyright (c) 2016-2017 Intel Corporation
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

nsd:nsd-catalog:
    nsd:
    -   id: 2tg-topology
        name: 2tg-topology
        short-name: 2tg-topology
        description: 2tg-topology
        constituent-vnfd:
        - member-vnf-index: '0'
          vnfd-id-ref: tg__0
          VNF model: ../../vnf_descriptors/ixia_rfc2544_tpl.yaml
        - member-vnf-index: '1'
          vnfd-id-ref: vnf__0
          VNF model: ../../vnf_descriptors/cgnapt_vnf.yaml      #VNF type

        vld:
{% for vnf_num in range(num_vnfs|int) %}
          - id: uplink_{{ vnf_num }}
            name: "tg__0 to vnf__0 link {{ (vnf_num * 2) }}"
            type: ELAN
            vnfd-connection-point-ref:
              - member-vnf-index-ref: '0'
                vnfd-connection-point-ref: xe{{ vnf_num * 2}}
                vnfd-id-ref: tg__0
              - member-vnf-index-ref: '1'
                vnfd-connection-point-ref: xe{{ vnf_num * 2}}
                vnfd-id-ref: vnf__0
          - id: downlink_{{ vnf_num }}
            name: "vnf__0 to tg__0 link {{ (vnf_num * 2) + 1}}"
            type: ELAN
            vnfd-connection-point-ref:
              - member-vnf-index-ref: '1'
                vnfd-connection-point-ref: xe{{ (vnf_num * 2) + 1}}
                vnfd-id-ref: vnf__0
              - member-vnf-index-ref: '0'
                vnfd-connection-point-ref: xe{{ (vnf_num * 2) + 1}}
                vnfd-id-ref: tg__0
{% endfor %}
--+--------------------------------------------------------------+ |test tool | Developed by the project. Please see folder: | | | "yardstick/benchmark/scenarios/availability/ha_tools" | | | | +--------------+--------------------------------------------------------------+ |references | ETSI NFV REL001 | | | | +--------------+--------------------------------------------------------------+ |configuration | This test case needs two configuration files: | | | 1) test case file: opnfv_yardstick_tc089.yaml | | | -Attackers: see above "attackers" description | | | -waiting_time: which is the time (seconds) from the process | | | being killed to stopping monitors the monitors | | | -Monitors: see above "monitors" description | | | -SLA: see above "metrics" description | | | | | | 2)POD file: pod.yaml | | | The POD configuration should record on pod.yaml first. | | | the "host" item in this test case will use the node name in | | | the pod.yaml. | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | do attacker: connect the host through SSH, and then execute | | | the kill process script with param value specified by | | | "process_name" | | | | | | Result: Process will be killed. | | | | +--------------+--------------------------------------------------------------+ |step 2 | start monitors: | | | each monitor will run with independently process | | | | | | Result: The monitor info will be collected. | | | | +--------------+--------------------------------------------------------------+ |step 3 | create a new instance to check whether the nova conductor | | | works normally. | | | | +--------------+--------------------------------------------------------------+ |step 4 | stop the monitor after a period of time specified by | | | "waiting_time" | | | | | | Result: The monitor info will be aggregated. | | | | +--------------+--------------------------------------------------------------+ |post-action | It is the action when the test cases exist. It will check the| | | status of the specified process on the host, and restart the | | | process if it is not running for next test cases | | | | +--------------+--------------------------------------------------------------+ |test verdict | Fails only if SLA is not passed, or if there is a test case | | | execution problem. | | | | +--------------+--------------------------------------------------------------+