From fa4235b9a549d8947b9ebab7d86c00da0953aa83 Mon Sep 17 00:00:00 2001 From: Peter Barabas Date: Thu, 28 Apr 2016 10:32:02 +0200 Subject: Clean up scenario files - remove release from scenario files - remove old versions of scenario files - remove versions from scenario file names and update scenario.yaml - update README Change-Id: I5203ea0794b96fb44f6a9db25b33e5066c1d9574 Signed-off-by: Peter Barabas --- deploy/scenario/README | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'deploy/scenario/README') diff --git a/deploy/scenario/README b/deploy/scenario/README index aebeb40ee..3472f6630 100644 --- a/deploy/scenario/README +++ b/deploy/scenario/README @@ -20,7 +20,7 @@ Creating a new plugin --------------------- Creating a new plugin involves creating a plugin config yaml file in /deploy/config/plugins. The filename should comply to following structure: -fuel-_.yaml. +fuel-.yaml. The plugin configuration must include plugin configuration metadata as below: plugin-config-metadata: @@ -42,7 +42,7 @@ Creating a new deployment scenario ---------------------------------- Creating a new deployment scenario involve creating a deployment scenario yaml file under deploy/scenario/. The filename should comply to following -format: ___...__.yaml +format: ___..._.yaml The deployment configuration file must contain configuration metadata as stated below: @@ -89,7 +89,6 @@ dea-override-config: environment: mode: ha net_segment_type: tun - wanted_release: Kilo on Ubuntu 14.04 nodes: - id: 1 interfaces: interfaces_1 @@ -162,4 +161,4 @@ and one or several deployment scenario configuration yaml files. Other ----- These configuration files are used by deploy.sh provided by Fuel@OPNFV, e.g. -deploy.sh will clone this repo when deploying. \ No newline at end of file +deploy.sh will clone this repo when deploying. -- cgit 1.2.3-korg