Revision 92e4d1c6 docs/quick-install-admin-guide.rst

b/docs/quick-install-admin-guide.rst
1057 1057
                      libghc6-parallel-dev libghc6-curl-dev \
1058 1058
                      libghc-quickcheck2-dev hscolour hlint
1059 1059
                      python-support python-paramiko \
1060
                      python-fdsend python-ipaddr python-bitarray libjs-jquery fping
1060
                      python-fdsend python-ipaddr python-bitarray libjs-jquery fping pandoc
1061 1061

  
1062
Now let try to build the package:
1062
Now lets try to build the package:
1063 1063

  
1064 1064
.. code-block:: console
1065 1065

  
......
1070 1070
                   --git-export=INDEX \
1071 1071
                   --git-ignore-new
1072 1072

  
1073
To be able to sign the packages a key must be found in the system to comply to the
1074
name and email of the last debian/changelog entry in debian branch. Please note
1075
that signing is optional.
1076

  
1073 1077
This will create two deb packages in build-area. You should then run in both
1074 1078
nodes:
1075 1079

  
1076 1080
.. code-block:: console
1077 1081

  
1078
   # dpkg -i ../build-area/snf-ganeti.*deb
1079 1082
   # dpkg -i ../build-area/ganeti-htools.*deb
1083
   # dpkg -i ../build-area/snf-ganeti.*deb
1080 1084
   # apt-get install -f
1081 1085

  
1082 1086
We assume that Ganeti will use the KVM hypervisor. After installing Ganeti on
1083
both nodes, choose a domain name that resolves to a valid floating IP (let's say
1084
it's ``ganeti.node1.example.com``). Make sure node1 and node2 have root access
1085
between each other using ssh keys and not passwords. Also, make sure there is an
1086
lvm volume group named ``ganeti`` that will host your VMs' disks. Finally, setup
1087
a bridge interface on the host machines (e.g: br0). Then run on node1:
1087
both nodes, choose a domain name that resolves to a valid floating IP (let's
1088
say it's ``ganeti.node1.example.com``). Make sure node1 and node2 have same
1089
dsa/rsa keys and authorised_keys for password-less root ssh between each other.
1090
If not then skip passing --no-ssh-init but be aware that it will replace
1091
/root/.ssh/* related files and you might lose access to master node. Also,
1092
make sure there is an lvm volume group named ``ganeti`` that will host your
1093
VMs' disks. Finally, setup a bridge interface on the host machines (e.g: br0).
1094
Then run on node1:
1088 1095

  
1089 1096
.. code-block:: console
1090 1097

  
......
1096 1103
   root@node1:~ # gnt-cluster modify --hypervisor-parameters kvm:kernel_path=
1097 1104
   root@node1:~ # gnt-cluster modify --hypervisor-parameters kvm:vnc_bind_address=0.0.0.0
1098 1105

  
1099
   root@node1:~ # gnt-node add --no-node-setup --master-capable=yes \
1106
   root@node1:~ # gnt-node add --no-ssh-key-check --master-capable=yes \
1100 1107
                               --vm-capable=yes node2.example.com
1101 1108
   root@node1:~ # gnt-cluster modify --disk-parameters=drbd:metavg=ganeti
1102 1109
   root@node1:~ # gnt-group modify --disk-parameters=drbd:metavg=ganeti default
......
1829 1836
                               --subnet6=2001:648:2FFC:1322::/64 \
1830 1837
                               --gateway6=2001:648:2FFC:1322::1 \
1831 1838
                               --public --dhcp --flavor=CUSTOM \
1839
                               --link=br0 --mode=bridged \
1832 1840
                               --name=public_network \
1833 1841
                               --backend-id=1
1834 1842

  
......
2007 2015
   $ kamaki config set image.url "https://node1.example.com/plankton"
2008 2016
   $ kamaki config set store.url "https://node2.example.com/v1"
2009 2017
   $ kamaki config set global.account "user@example.com"
2010
   $ kamaki config set global.token "bdY_example_user_tokenYUff=="
2018
   $ kamaki config set store.enable on
2019
   $ kamaki config set store.pithos_extensions on
2020
   $ kamaki config set store.url "https://node2.example.com/v1"
2021
   $ kamaki config set store.account USER_UUID
2022
   $ kamaki config set global.token USER_TOKEN
2011 2023

  
2012
The token at the last kamaki command is our user's (``user@example.com``) token,
2013
as it appears on the user's `Profile` web page on the Astakos Web UI.
2024
The USER_TOKEN and USER_UUID appear on the user's (``user@example.com``) `Profile` web
2025
page on the Astakos Web UI.
2014 2026

  
2015 2027
You can see that the new configuration options have been applied correctly, by
2016 2028
running:
......
2061 2073
.. code-block:: console
2062 2074

  
2063 2075
   $ kamaki image register "Debian Base" \
2064
                           pithos://user@example.com/images/debian_base-6.0-7-x86_64.diskdump \
2076
                           pithos://USER_UUID/images/debian_base-6.0-7-x86_64.diskdump \
2065 2077
                           --public \
2066 2078
                           --disk-format=diskdump \
2067 2079
                           --property OSFAMILY=linux --property ROOT_PARTITION=1 \

Also available in: Unified diff