From 29f5cf27d8b37d8fa177788742e0b0f8b6ed3dd1 Mon Sep 17 00:00:00 2001
From: Clark Boylan <clark.boylan@gmail.com>
Date: Thu, 16 Oct 2014 08:22:52 -0700
Subject: [PATCH] Teach Grenade to do Juno to Kilo upgrades

First step in doing Juno to Kilo upgrades with Grenade is setting the
new base and target branches. Note this should come after both devstack
and grenade have stable/juno branches.

Change-Id: I0a7c8b3273b25e9fe457d7073046ad8a7ee3f70a
---
 from-juno/README.rst | 10 ++++++++++
 grenaderc            |  4 ++--
 2 files changed, 12 insertions(+), 2 deletions(-)
 create mode 100644 from-juno/README.rst

diff --git a/from-juno/README.rst b/from-juno/README.rst
new file mode 100644
index 00000000..7ccf7329
--- /dev/null
+++ b/from-juno/README.rst
@@ -0,0 +1,10 @@
+===========================================
+ Juno to Kilo specific upgrade scripts
+===========================================
+This directory can house service scripts for upgrading from Juno
+to Kilo for individual services.
+
+To do this add ``upgrade-$servicename`` script to this directory and
+include a ``configure_$servicename_upgrade`` function in the file. All
+services that don't have a specific upgrade script will just use the
+generic one, which performs a db-sync and installs the updated code.
diff --git a/grenaderc b/grenaderc
index 37e040ff..103b2b2f 100644
--- a/grenaderc
+++ b/grenaderc
@@ -14,10 +14,10 @@ STACK_ROOT=/opt/stack
 DATA_DIR=${STACK_ROOT}/data
 
 # Release info
-BASE_RELEASE=icehouse
+BASE_RELEASE=juno
 BASE_RELEASE_DIR=${STACK_ROOT}/$BASE_RELEASE
 
-TARGET_RELEASE=juno
+TARGET_RELEASE=kilo
 TARGET_RELEASE_DIR=${STACK_ROOT}/$TARGET_RELEASE
 
 # DevStack sources