2 ##############################################################################
3 # Copyright (c) 2017 Huawei and others.
4 # ulrich.kleber@huawei.com
5 # All rights reserved. This program and the accompanying materials
6 # are made available under the terms of the Apache License, Version 2.0
7 # which accompanies this distribution, and is available at
8 # http://www.apache.org/licenses/LICENSE-2.0
9 ##############################################################################
11 ##############################################################################
13 # This is an example for a MANO scenario
14 # It illustrates how MANO components can test orchestration capabilities
15 # together with various infrastructure scenarios.
16 # This way, the SDF describes the MANO components (NFVO and VNFM) only. For
17 # the infrastructure (NFVI and VIM) part another scenario is just referenced;
18 # that scenario is deployed independently in a separate deployment step, and
19 # can be deployed even using a different installer tool.
21 # More details can be found in the scenario lifecycle document.
22 ##############################################################################
24 ##############################################################################
25 # scenario meta-data: Metadata describing this sdf.yaml file and the
26 # scenario history and purpose, like in any other scenario descriptor
28 name: orchestra-example
29 title: "orchestra main scenario"
30 generic-scenario: false
32 creation-date: 2017-07-13
33 # This scenario integrates the main open-baton NFVO components to OPNFV
35 # In the first step, no sdn controller scenarios are supported, but only
36 # os-nosdn-nofeature and os-nosdn-ovs, installed by compass.
37 opnfv-release: euphrates
40 owner: Ulrich Kleber, ulrich.kleber@huawei.com
42 ##############################################################################
44 ##############################################################################
50 # here a list of optional features or artifacts to deploy could follow
54 # juju doesn't have release name
57 - opnfv-infrastructure:
58 release: euphrates # this determines also ocata as openstack version
63 - availability: [HA, NOHA]
64 - tools: [compass, joid]
65 # this is for the example. In first step only joid will work
68 - availability: [HA, NOHA]
71 ##############################################################################
73 ##############################################################################
81 # $$$$ following proposal 2 from the template (patchset 6)
90 # this is in addition to the components defined in the
91 # opnfv-infrastructure scenario.
92 - compute-node: # no additional component to be deployed here
105 # Please note that the component "opnfv-infrastructure" specified their
106 # own deployment tools and options. Definition here is related only
107 # for the nfvo and vnfm components specified above.
122 ##############################################################################
124 ##############################################################################