aboutsummaryrefslogtreecommitdiffstats
path: root/puppet/services/manila-share.yaml
blob: 6ac0d2cfbbdde4de218012036f9a216205d09ada (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
52
53
54
heat_template_version: ocata

description: >
  Manila-share service configured with Puppet

parameters:
  ServiceNetMap:
    default: {}
    description: Mapping of service_name -> network name. Typically set
                 via parameter_defaults in the resource registry.  This
                 mapping overrides those in ServiceNetMapDefaults.
    type: json
  DefaultPasswords:
    default: {}
    type: json
  EndpointMap:
    default: {}
    description: Mapping of service endpoint -> protocol. Typically set
                 via parameter_defaults in the resource registry.
    type: json
  MonitoringSubscriptionManilaShare:
    default: 'overcloud-manila-share'
    type: string
  ManilaPassword:
    description: The password for the manila service account.
    type: string
    hidden: true

resources:
  ManilaBase:
    type: ./manila-base.yaml
    properties:
      ServiceNetMap: {get_param: ServiceNetMap}
      DefaultPasswords: {get_param: DefaultPasswords}
      EndpointMap: {get_param: EndpointMap}

outputs:
  role_data:
    description: Role data for the Manila-share role.
    value:
      service_name: manila_share
      monitoring_subscription: {get_param: MonitoringSubscriptionManilaShare}
      config_settings:
        map_merge:
          - get_attr: [ManilaBase, role_data, config_settings]
          - manila::volume::cinder::cinder_admin_tenant_name: 'service'
            manila::keystone::authtoken::password: {get_param: ManilaPassword}
            manila::keystone::authtoken::auth_uri: {get_param: [EndpointMap, KeystoneInternal, uri]}
            manila::keystone::authtoken::auth_url: { get_param: [EndpointMap, KeystoneInternal, uri_no_suffix] }
            manila::keystone::authtoken::project_name: 'service'
      service_config_settings:
        get_attr: [ManilaBase, role_data, service_config_settings]
      step_config: |
        include ::tripleo::profile::base::manila::share
l send the given number of packets | | | without pausing | | | * runner: | | | duration: 30 # Total test duration 30 seconds. | | | | | | * SLA (optional): | | | jitter: 10 (ms) # The maximum amount of jitter that is | | | accepted. | | | | +--------------+--------------------------------------------------------------+ |applicability | Test can be configured with different: | | | | | | * bandwidth: Test case can be configured with different | | | bandwidth. | | | | | | * duration: The test duration can be configured. | | | | | | * jitter: SLA is optional. The SLA in this test case | | | serves as an example. | | | | +--------------+--------------------------------------------------------------+ |usability | This test case is one of Yardstick's generic test. Thus it | | | is runnable on most of the scenarios. | | | | +--------------+--------------------------------------------------------------+ |references | iperf3_ | | | | | | ETSI-NFV-TST001 | | | | +--------------+--------------------------------------------------------------+ |pre-test | The test case image needs to be installed into Glance | |conditions | with iperf3 included in the image. | | | | | | No POD specific requirements have been identified. | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | Two host VMs with iperf3 installed are booted, as server and | | | client. | | | | +--------------+--------------------------------------------------------------+ |step 2 | Yardstick is connected with the host VM by using ssh. | | | A iperf3 server is started on the server VM via the ssh | | | tunnel. | | | | +--------------+--------------------------------------------------------------+ |step 3 | iperf3 benchmark is invoked. Jitter is calculated and check | | | against the SLA. Logs are produced and stored. | | | | | | Result: Logs are stored. | | | | +--------------+--------------------------------------------------------------+ |step 4 | The host VMs are deleted. | | | | +--------------+--------------------------------------------------------------+ |test verdict | Test should not PASS if any jitter is above the optional SLA | | | value, or if there is a test case execution problem. | | | | +--------------+--------------------------------------------------------------+