move up one more dependencies

move up all the dependencies so that there won't be any dependency
conflict. Kiloeyes and Monasca agent can co-exist now.

Change-Id: I4fe39b1f79ff12fbee03ea4327fe32f3eece5997

requirements.txt

@@ -15,7 +15,7 @@ pastedeploy>=1.3.3
 pbr>=1.6
 python-dateutil>=1.5
 six>=1.9.0
-stevedore>=0.14
+stevedore>=1.5.0
 ujson>=1.33
 eventlet!=0.18.3,>=0.18.2
 pyparsing==2.0.1

vagrant/README.md

@@ -25,14 +25,14 @@ required software to run kiloeyes.
 Usage:
 ======
 You can install everything onto one machine or you can choose install different
-components onto different servers. Currently python-keystonemiddleware which
-is used by kiloeyes for security, but its dependencies conflict with agent
-dependcies, so kiloeyes currently can not co-exist with agent on a signle
-machine. It is best to have kiloeyes and agent installed onto the separate
-machines to avoid the installation headaches. This vagrant project uses
-configuration files in directory vagrant/onvm/conf. File nodes.conf.yml is
-used to configure how many nodes to install various components, ids.conf.yml
-file is used to save credentials.
+components onto different servers. It is best to have kiloeyes and agent
+installed onto the separate machines. In a typical production environment, you
+would most likely install agents onto systems that you want Kiloeyes to monitor.
+For a development environment, you can simply install everything onto one
+machine. This vagrant project uses configuration files in directory
+vagrant/onvm/conf to install various components. File nodes.conf.yml is
+used to configure how many nodes to install and what to be installed on which
+nodes. ids.conf.yml file is used to save credentials.
 
 Here is an example::
 

vagrant/onvm/conf/nodes.conf.yml

@@ -5,7 +5,7 @@ controller:
 
 agent01:
   host_name: agent01.leap.dev
-  eth0: 192.168.1.88
+  eth0: 192.168.1.90
 
 logical2physical:
   kiloeyes: controller