build, deploy: Remove obsolete Fuel@Openstack code

JIRA: FUEL-278

Change-Id: I30c04c325de5ac97aee172386de43201988646c5
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

1 files changed, 0 insertions, 89 deletions

diff --git a/deploy/scenario/ha_heat_ceilometer_scenario.yaml b/deploy/scenario/ha_heat_ceilometer_scenario.yaml
deleted file mode 100644
index 6b032bfdd..000000000
--- a/deploy/scenario/ha_heat_ceilometer_scenario.yaml
+++ /dev/null
@@ -1,89 +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: OpenStack-only, 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: congress
-    module-config-name: fuel-congress
-    module-config-version: 1.0.0
-
-##############################################################################
-# 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, congress
-  - id: 2
-    interfaces: interfaces_1
-    role: mongo, controller
-  - id: 3
-    interfaces: interfaces_1
-    role: ceph-osd,controller
-  - id: 4
-    interfaces: interfaces_1
-    role: ceph-osd,compute
-  - id: 5
-    interfaces: interfaces_1
-    role: ceph-osd,compute
-
-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: