systems: Fix top level build_base_machine script to use ID

Modified top level build_base_machine.sh script to use ID
instead of Name from os-release file. Renamed folders to
adapt to this change.

* Modified ID variable assignment from echo to straight assignment.

JIRA: VSPERF-257

Change-Id: I22a7d5a1f191418cbc8fc9fd7d85b013e51b49bc
Signed-off-by: Christian Trautman <ctrautma@redhat.com>

1 files changed, 34 insertions, 0 deletions

diff --git a/systems/rhel/7.2/prepare_python_env.sh b/systems/rhel/7.2/prepare_python_env.sh
new file mode 100755
index 00000000..1d51380a
--- /dev/null
+++ b/systems/rhel/7.2/prepare_python_env.sh
@@ -0,0 +1,34 @@
+#!/bin/bash
+#
+# Prepare Python environment for vsperf execution on Red Hat 7.2 systems.
+#
+# Copyright 2016 OPNFV, Intel Corporation, Red Hat Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+if [ -d "$VSPERFENV_DIR" ] ; then
+    echo "Directory $VSPERFENV_DIR already exists. Skipping python virtualenv \
+creation."
+    exit
+fi
+
+# enable virtual environment in a subshell, so QEMU build can use python 2.7
+# Also make sure we know which virtualenv was installed. I've seen the file
+# name change pending on what type of installation was done.
+virtualenv_file=$(ls /usr/local/bin | awk '/virtualenv/')
+
+($virtualenv_file "$VSPERFENV_DIR"
+source "$VSPERFENV_DIR"/bin/activate
+pip3.4 install -r ../requirements.txt
+pip3.4 install pylint
+)
\ No newline at end of file