diff options
Diffstat (limited to 'deploy/scenario/ha_odl-l3_heat_ceilometer_scenario_0.0.3.yaml')
| -rw-r--r-- | deploy/scenario/ha_odl-l3_heat_ceilometer_scenario_0.0.3.yaml | 107 |
1 files changed, 0 insertions, 107 deletions
diff --git a/deploy/scenario/ha_odl-l3_heat_ceilometer_scenario_0.0.3.yaml b/deploy/scenario/ha_odl-l3_heat_ceilometer_scenario_0.0.3.yaml deleted file mode 100644 index 96623309b..000000000 --- a/deploy/scenario/ha_odl-l3_heat_ceilometer_scenario_0.0.3.yaml +++ /dev/null @@ -1,107 +0,0 @@ -############################################################################## -# Copyright (c) 2015 Ericsson AB and others. -# jonas.bjurel@ericsson.com -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Apache License, Version 2.0 -# which accompanies this distribution, and is available at -# http://www.apache.org/licenses/LICENSE-2.0 -############################################################################## - -############################################################################### # Description: -# This .yaml configuration file defines the configuration of the fuel -# deployment and is passed as an argument to deploy.sh -# eg. deploy.sh -c https://artifact.opnfv.org/fuel/config -# This will make build.sh fetch this configuration file and configure the -# deployment accordingly. -# After the deployment, a copy of this file gets uploaded to fuel: -# /root/deploy-config.yaml, as well as the sha-1 sum of this file: -# /root/deploy-config.sha1 -############################################################################## - -############################################################################## -# deployment configuration meta-data -deployment-scenario-metadata: - title: ODL-L3 HA deployment - version: 0.0.3 - created: Jan 26 2016 - comment: Rebased to Fuel8 - -############################################################################## -# Stack extentions are opnfv added value features in form of a fuel-plugin -# plug-ins listed below will be enabled and configured according to the -# <module-config-base-uri>/<module-config-name>_<module-config-version>.yaml -# It does so by copying the config file to the local plugin config directory -stack-extensions: - - module: opendaylight - module-config-name: fuel-odl - module-config-version: 0.0.2 - module-config-override: - # Module config overrides - rest_api_port: - value: '8282' - enable_gbp: - value: false - enable_l3_odl: - value: true - enable_sfc: - value: false - -############################################################################## -# By editing the override-config sections below, you can override arbitrary -# configuration name-space settings -dea-override-config: - nodes: - - id: 1 - interfaces: interfaces_1 - role: controller,opendaylight - transformations: transformations_1 - - id: 2 - interfaces: interfaces_1 - role: mongo,controller - transformations: transformations_1 - - id: 3 - interfaces: interfaces_1 - role: ceph-osd,controller - transformations: transformations_1 - - id: 4 - interfaces: interfaces_1 - role: ceph-osd,compute - transformations: transformations_1 - - id: 5 - interfaces: interfaces_1 - role: ceph-osd,compute - transformations: transformations_1 - settings: - editable: - public_network_assignment: - assign_to_all_nodes: - value: true -dha-override-config: - nodes: - - id: 1 - libvirtName: controller1 - libvirtTemplate: templates/virtual_environment/vms/controller.xml - - id: 2 - libvirtName: controller2 - libvirtTemplate: templates/virtual_environment/vms/controller.xml - - id: 3 - libvirtName: controller3 - libvirtTemplate: templates/virtual_environment/vms/controller.xml - - id: 4 - libvirtName: compute1 - libvirtTemplate: templates/virtual_environment/vms/compute.xml - - id: 5 - libvirtName: compute2 - libvirtTemplate: templates/virtual_environment/vms/compute.xml - - id: 6 - libvirtName: fuel-master - libvirtTemplate: templates/virtual_environment/vms/fuel.xml - isFuel: yes - username: root - password: r00tme - -############################################################################## -# The verification pipeline may populate the section below with arbitrary -# testing information, which post deploy can be retreived from the fuel master: -# /root/deploy-config.yaml -test: |