User Tools

Site Tools


khaleesi_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
khaleesi_guide [2015/03/10 15:48]
Tim Rozet
khaleesi_guide [2015/04/07 22:22]
Daniel Farrell [Installation] Trivial code MD fix
Line 14: Line 14:
 Khaleesi can be installed on your provisioning server. ​ First you need EPEL and some other packages: Khaleesi can be installed on your provisioning server. ​ First you need EPEL and some other packages:
  
-''​sudo rpm -i http://​dl.fedoraproject.org/​pub/​epel/​7/​x86_64/​e/​epel-release-7-5.noarch.rpm''​ +<​code>​ 
- +sudo rpm -i http://​dl.fedoraproject.org/​pub/​epel/​7/​x86_64/​e/​epel-release-7-5.noarch.rpm 
-''​sudo yum -y install python-pip python-virtualenv gcc git''​ +sudo yum -y install python-pip python-virtualenv gcc git \ 
- +                    python-keystoneclient python-novaclient ​
-''​sudo yum -y install ​python-keystoneclient python-novaclient python-glanceclient python-neutronclient python-keystoneclient''​ +                    ​python-glanceclient python-neutronclient ​
- +                    ​python-keystoneclient ​sshpass 
-''​sudo yum -y install sshpass''​+</​code>​
  
 Now clone Khaleesi where you like: Now clone Khaleesi where you like:
  
-''​git clone -b foreman https://​github.com/​trozet/​khaleesi.git''​+<​code>​git clone -b foreman https://​github.com/​trozet/​khaleesi.git</​code>​
  
 Khaleesi recommeds using a virtual environment provided by python-virtualenv. ​ Follow these steps to setup your virtualenv: Khaleesi recommeds using a virtual environment provided by python-virtualenv. ​ Follow these steps to setup your virtualenv:
  
 <​code>​ <​code>​
-virtualenv ​venv +virtualenv ​khaleesi_venv 
-source ​venv/​bin/​activate+source ​khaleesi_venv/​bin/​activate
 pip install ansible pip install ansible
-cd khaleesi +cd khaleesi/tools/ksgen
-cd tools/ksgen+
 python setup.py develop python setup.py develop
 cd ../.. cd ../..
 </​code>​ </​code>​
  
-From the above you can see that "source ​venv/​bin/​activate" ​will activate your virtual environment. ​ Simply use deactivate to exit.  Now we need to create a default Ansible config:+From the above you can see that ''​source ​khaleesi_venv/​bin/​activate'' ​will activate your virtual environment. ​ Simply use deactivate to exit.  Now we need to create a default Ansible config:
  
 <​code>​ <​code>​
Line 53: Line 52:
 Khaleesi uses a ksgen_settings.yml file for directing Khaleesi'​s execution. ​ It is a YAML file that contains variables and topology information. ​ This file can either be edited manually or can be autogenerated using another project called [[https://​github.com/​redhat-openstack/​khaleesi-settings | khaleesi-settings]]. Khaleesi uses a ksgen_settings.yml file for directing Khaleesi'​s execution. ​ It is a YAML file that contains variables and topology information. ​ This file can either be edited manually or can be autogenerated using another project called [[https://​github.com/​redhat-openstack/​khaleesi-settings | khaleesi-settings]].
  
-For our purposes it is easier to just modify an existing ksgen_settings file.  Please use this as a template: [[ksgen_settings Intel example| ​https://​gist.github.com/​trozet/​c5bde608822d8e6b063a]]. ​ The configuration make look like a lot at first, but you only need to modify two pieces:+For our purposes it is easier to just modify an existing ksgen_settings file.  Please use this as a template: [[https://​gist.github.com/​trozet/​c5bde608822d8e6b063a| ksgen_settings Intel example]].  The configuration make look like a lot at first, but you only need to modify two pieces:
  
 === Modify External Network === === Modify External Network ===
 You will notice part of the config that looks like this: You will notice part of the config that looks like this:
-<​code>​+<​code ​yaml>
   public_allocation_end:​ 10.2.84.71   public_allocation_end:​ 10.2.84.71
   skip:   skip:
Line 74: Line 73:
 The second piece of the configuration you need to change is the nodes dictionary. ​ This configuration provides your Host inventory to ansible: The second piece of the configuration you need to change is the nodes dictionary. ​ This configuration provides your Host inventory to ansible:
  
-<​code>​+<​code ​yaml>
 nodes: nodes:
   compute:   compute:
Line 144: Line 143:
  
 The first line will give you the overall execution summary, followed by individual results: The first line will give you the overall execution summary, followed by individual results:
-<​code>​+<​code ​xml>
 <​testsuite errors="​0"​ failures="​179"​ name=""​ tests="​2141"​ time="​880.284">​ <​testsuite errors="​0"​ failures="​179"​ name=""​ tests="​2141"​ time="​880.284">​
 <​testcase classname=""​ name="​setUpClass (tempest.api.compute.flavors.test_flavors.FlavorsV3Test)"​ time="​0.000">​ <​testcase classname=""​ name="​setUpClass (tempest.api.compute.flavors.test_flavors.FlavorsV3Test)"​ time="​0.000">​
khaleesi_guide.txt · Last modified: 2015/04/07 22:23 by Daniel Farrell