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 # http://artifacts.opnfv.org/octopus/docs/scenario-lifecycle/index.html
23 ##############################################################################
25 ##############################################################################
26 # scenario meta-data: Metadata describing this sdf.yaml file and the
27 # scenario history and purpose, like in any other scenario descriptor
29 name: orchestra-example
30 title: "orchestra main scenario"
31 generic-scenario: false
33 creation-date: 2017-07-13
34 # This scenario integrates the main open-baton NFVO components to OPNFV
36 # In the first step, no sdn controller scenarios are supported, but only
37 # os-nosdn-nofeature and os-nosdn-ovs, installed by compass.
38 opnfv-release: euphrates
41 owner: Ulrich Kleber, ulrich.kleber@huawei.com
43 ##############################################################################
45 ##############################################################################
51 # here a list of optional features or artifacts to deploy could follow
55 # juju doesn't have release name
58 - opnfv-infrastructure:
59 release: euphrates # this determines also ocata as openstack version
64 - availability: [HA, NOHA]
65 - tools: [compass, joid]
66 # this is for the example. In first step only joid will work
69 - availability: [HA, NOHA]
72 ##############################################################################
74 ##############################################################################
82 # $$$$ following proposal 2 from the template (patchset 6)
91 # this is in addition to the components defined in the
92 # opnfv-infrastructure scenario.
93 - compute-node: # no additional component to be deployed here
106 # Please note that the component "opnfv-infrastructure" specified their
107 # own deployment tools and options. Definition here is related only
108 # for the nfvo and vnfm components specified above.
123 ##############################################################################
125 ##############################################################################