Skip to content

Instantly share code, notes, and snippets.

@jethrosun
Created June 7, 2016 02:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jethrosun/5e43d764509065a41561031c09b2f7cc to your computer and use it in GitHub Desktop.
Save jethrosun/5e43d764509065a41561031c09b2f7cc to your computer and use it in GitHub Desktop.
patch for INSTALL.rst
20c20
< yum install libvirt bridge-utils ipmitool telnet httpd mod_wsgi python-pip qemu-kvm python-virtinst virt-install python-psycopg2 vconfig net-tools
---
> yum install libvirt bridge-utils ipmitool telnet httpd mod_wsgi python-pip qemu-kvm python-virtinst virt-install python-psycopg2 vconfig net-tools gcc python-devel libxml2-devel libxslt-devel
51,66c51,52
< For simplicity we have provided default values:
< Copy the following lines in file ``haas_env``
<
< HAAS_USER=haas
<
< HAAS_DB_ROLE=haas
<
< HAAS_DB_PASSWORD=secret
<
< HAAS_ADMIN=haas
<
< HAAS_ADMIN_PASSWORD=secret
<
< HAAS_HOME_DIR=/var/lib/haas
<
<
---
> For simplicity we have provided default values, make sure to check or change
> content of ``haas_env``.
87c73
< sudo python setup.py install
---
> python setup.py install
108,109c94,95
< ``haas.cfg`` file contains sensitive administrative information and should not be exposed to clients or
< end_users. Therefore, after placing the file at ``/etc/haas.cfg`` its
---
> ``haas.cfg`` file contains sensitive administrative information and should not be exposed
> to clients or end_users. Therefore, after placing the file at ``/etc/haas.cfg`` its
111c97
< From source directory of haas as user root do the following::
---
> From source directory of haas as ``root`` to do the following::
182c168
< cd /var/lib/haas
---
> /var/lib/haas
218c204
< We must reconfigure ``libvirt`` to allow (some) unprivileged users access to
---
> You must reconfigure ``libvirt`` to allow (some) unprivileged users access to
241,243c227,229
< Now we must make a clonable base headnode. (One is required, and more are
< allowed.) First create a storage pool. Any kind can be used, but we will only
< document creating a directory-backed storage pool::
---
> Now make a clonable base headnode. (One is required, but more headnodes are
> allowed.) First create a storage pool. Any kind can be used, but here only
> documents creating a directory-backed storage pool::
264,265c250,251
< an ubuntu 14.04 or centos 7 disk image with a default root password. Read
< the README in that directory for more information.
---
> an Ubuntu 14.04 or CentOS 7 disk image with a default root password. Read
> the ``README`` in that directory for more information.
267,268c253,254
< Once the disk image is built, copy ito the storage pool directory (here we
< assume it is called ``base.img``)::
---
> Once the disk image is built, copy ito the storage pool directory (here
> assumed it is called ``base.img``)::
391c377
< Centos:
---
> CentOS:
394c380
< Centos uses systemd to controll all its processes.
---
> CentOS uses ``systemd`` to controll all its processes.
444,448d429
< Create a file ``client_env`` with following entries::
<
< export HAAS_ENDPOINT=http://127.0.0.1/
< export HAAS_USERNAME=<haas_admin_username>
< export HAAS_PASSWORD=<haas_admin_password>
455c436
< If you get an empty list ``[]`` as output then congratulations !!
---
> If you get an empty list ``[]`` as output then congratulations !!
458c439
< Describe datacenter resources
---
> Describe Datacenter resources
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment