1
=== modified file 'doc/source/docbkx/openstack-compute-admin/computeadmin.xml'
2
--- doc/source/docbkx/openstack-compute-admin/computeadmin.xml	2011-09-01 14:09:41 +0000
3
+++ doc/source/docbkx/openstack-compute-admin/computeadmin.xml	2011-09-07 09:19:27 +0000
4
@@ -1,33 +1,33 @@
5
1
<?xml version="1.0" encoding="UTF-8"?>
1
<?xml version="1.0" encoding="UTF-8"?>
7
2
<!DOCTYPE chapter [
2
<!DOCTYPE chapter[
8
3
<!-- Some useful entities borrowed from HTML -->
3
<!-- Some useful entities borrowed from HTML -->
11
4
<!ENTITY ndash  "&#x2013;">
4
<!ENTITY ndash "&#x2013;">
12
5
<!ENTITY mdash  "&#x2014;">
5
<!ENTITY mdash "&#x2014;">
13
6
<!ENTITY hellip "&#x2026;">
6
<!ENTITY hellip "&#x2026;">
14
7
<!ENTITY nbsp "&#160;">
7
<!ENTITY nbsp "&#160;">
16
8
<!ENTITY CHECK  '<inlinemediaobject xmlns="http://docbook.org/ns/docbook">
8
<!ENTITY CHECK '<inlinemediaobject xmlns="http://docbook.org/ns/docbook">
17
9
<imageobject>
9
<imageobject>
18
10
<imagedata fileref="img/Check_mark_23x20_02.svg"
10
<imagedata fileref="img/Check_mark_23x20_02.svg"
19
11
format="SVG" scale="60"/>
11
format="SVG" scale="60"/>
20
12
</imageobject>
12
</imageobject>
21
13
</inlinemediaobject>'>
13
</inlinemediaobject>'>
22
14
14
24
15
<!ENTITY ARROW  '<inlinemediaobject xmlns="http://docbook.org/ns/docbook">
15
<!ENTITY ARROW '<inlinemediaobject xmlns="http://docbook.org/ns/docbook">
25
16
<imageobject>
16
<imageobject>
26
17
<imagedata fileref="img/Arrow_east.svg"
17
<imagedata fileref="img/Arrow_east.svg"
27
18
format="SVG" scale="60"/>
18
format="SVG" scale="60"/>
28
19
</imageobject>
19
</imageobject>
29
20
</inlinemediaobject>'>
20
</inlinemediaobject>'>
30
21
]>
21
]>
33
22
<chapter xmlns="http://docbook.org/ns/docbook"
22
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
32
23
    xmlns:xi="http://www.w3.org/2001/XInclude"
34
24
    xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
23
    xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
35
25
    <?dbhtml filename="ch_system-administration-for-openstack-compute.html" ?>
24
    <?dbhtml filename="ch_system-administration-for-openstack-compute.html" ?>
36
26
    <title>System Administration</title>
25
    <title>System Administration</title>
37
27
    <para>By understanding how the different installed nodes interact with each other you can
26
    <para>By understanding how the different installed nodes interact with each other you can
38
28
        administer the OpenStack Compute installation. OpenStack Compute offers many ways to install
27
        administer the OpenStack Compute installation. OpenStack Compute offers many ways to install
41
29
        using multiple servers but the general idea is that you can have multiple compute nodes that 
28
        using multiple servers but the general idea is that you can have multiple compute nodes that
42
30
        control the virtual servers and a cloud controller node that contains the remaining Nova services. </para>
29
        control the virtual servers and a cloud controller node that contains the remaining Nova
43
30
        services. </para>
44
31
    <para>The OpenStack Compute cloud works via the interaction of a series of daemon processes
31
    <para>The OpenStack Compute cloud works via the interaction of a series of daemon processes
45
32
        named nova-* that reside persistently on the host machine or machines. These binaries can
32
        named nova-* that reside persistently on the host machine or machines. These binaries can
46
33
        all run on the same machine or be spread out on multiple boxes in a large deployment. The
33
        all run on the same machine or be spread out on multiple boxes in a large deployment. The
47
@@ -77,113 +77,179 @@
48
77
            <para><literallayout class="monospaced">nova-network --network_manager=nova.network.manager.FlatManager</literallayout></para>
77
            <para><literallayout class="monospaced">nova-network --network_manager=nova.network.manager.FlatManager</literallayout></para>
49
78
        </listitem>
78
        </listitem>
50
79
    </itemizedlist>
79
    </itemizedlist>
55
80
    <section><?dbhtml filename="starting-images.html" ?>
80
    <section>
56
81
        <title>Starting Images</title><para>Once you have an installation, you want to get images that you can use in your Compute cloud. We've created a basic Ubuntu image for testing your installation. First you'll download the image, then use uec-publish-tarball to publish it:</para>
81
        <?dbhtml filename="starting-images.html" ?>
57
82
            
82
        <title>Starting Images</title>
58
83
           <para><literallayout class="monospaced">image="ubuntu1010-UEC-localuser-image.tar.gz"
83
        <para>Once you have an installation, you want to get images that you can use in your Compute
59
84
            cloud. We've created a basic Ubuntu image for testing your installation. First you'll
60
85
            download the image, then use uec-publish-tarball to publish it:</para>
61
86
62
87
        <para><literallayout class="monospaced">image="ubuntu1010-UEC-localuser-image.tar.gz"
63
84
wget http://c0179148.cdn1.cloudfiles.rackspacecloud.com/ubuntu1010-UEC-localuser-image.tar.gz
88
wget http://c0179148.cdn1.cloudfiles.rackspacecloud.com/ubuntu1010-UEC-localuser-image.tar.gz
64
85
uec-publish-tarball $image [bucket-name] [hardware-arch]</literallayout></para>
89
uec-publish-tarball $image [bucket-name] [hardware-arch]</literallayout></para>
85
86
                
90
86
87
               <para>Here's an example of what this command looks like with data:</para>
91
        <para>Here's an example of what this command looks like with data:</para>
87
88
                
92
88
89
               <para><literallayout class="monospaced"> uec-publish-tarball ubuntu1010-UEC-localuser-image.tar.gz dub-bucket x86_64</literallayout></para>
93
        <para><literallayout class="monospaced"> uec-publish-tarball ubuntu1010-UEC-localuser-image.tar.gz dub-bucket x86_64</literallayout></para>
89
90
                
94
90
91
        <para>The command in return should output three references: emi, eri and eki. You need to use the emi value (for example, “ami-zqkyh9th″) for the euca-run-instances command.</para>
95
        <para>The command in return should output three references: emi, eri and eki. You need to
91
92
                
96
            use the emi value (for example, “ami-zqkyh9th″) for the euca-run-instances
92
93
       
97
            command.</para>
93
94
        <para>Now you can schedule, launch and connect to the instance, which you do with tools from the Euca2ools on the command line. Create the emi value from the uec-publish-tarball command, and then you can use the euca-run-instances command.</para>
98
94
95
                <para>One thing to note here, once you publish the tarball, it has to untar before you can launch an image from it. Using the 'euca-describe-images' command, wait until the state turns to "available" from "untarring.":</para>
99
95
96
                
100
        <para>Now you can schedule, launch and connect to the instance, which you do with tools from
96
97
                <para><literallayout class="monospaced">euca-describe-images</literallayout></para>
101
            the Euca2ools on the command line. Create the emi value from the uec-publish-tarball
97
98
                
102
            command, and then you can use the euca-run-instances command.</para>
98
99
        <para>Depending on the image that you're using, you need a public key to connect to it. Some images have built-in accounts already created. Images can be shared by many users, so it is dangerous to put passwords into the images. Nova therefore supports injecting ssh keys into instances before they are
103
        <para>One thing to note here, once you publish the tarball, it has to untar before you can
99
100
            booted. This allows a user to login to the instances that he or she creates securely.
104
            launch an image from it. Using the 'euca-describe-images' command, wait until the state
100
101
            Generally the first thing that a user does when using the system is create a keypair.
105
            turns to "available" from "untarring.":</para>
101
102
            Keypairs provide secure authentication to your instances. As part of the first boot of a
106
102
103
            virtual image, the private key of your keypair is added to root’s authorized_keys file.
107
        <para><literallayout class="monospaced">euca-describe-images</literallayout></para>
103
104
            Nova generates a public and private key pair, and sends the private key to the user. The
108
104
105
            public key is stored so that it can be injected into instances. </para>
109
        <para>Depending on the image that you're using, you need a public key to connect to it. Some
105
110
            images have built-in accounts already created. Images can be shared by many users, so it
106
111
            is dangerous to put passwords into the images. Nova therefore supports injecting ssh
107
112
            keys into instances before they are booted. This allows a user to login to the instances
108
113
            that he or she creates securely. Generally the first thing that a user does when using
109
114
            the system is create a keypair. Keypairs provide secure authentication to your
110
115
            instances. As part of the first boot of a virtual image, the private key of your keypair
111
116
            is added to root’s authorized_keys file. Nova generates a public and private key pair,
112
117
            and sends the private key to the user. The public key is stored so that it can be
113
118
            injected into instances. </para>
114
106
        <para>Keypairs are created through the api and you use them as a parameter when launching an
119
        <para>Keypairs are created through the api and you use them as a parameter when launching an
115
107
            instance. They can be created on the command line using the euca2ools script
120
            instance. They can be created on the command line using the euca2ools script
116
108
            euca-add-keypair. Refer to the man page for the available options. Example usage:</para>
121
            euca-add-keypair. Refer to the man page for the available options. Example usage:</para>
119
109
                    
122
120
110
                    <literallayout class="monospaced">euca-add-keypair test > test.pem
123
        <literallayout class="monospaced">euca-add-keypair test > test.pem
121
111
chmod 600 test.pem</literallayout>
124
chmod 600 test.pem</literallayout>
123
112
        
125
124
113
        <para>Now, you can run the instances:</para>
126
        <para>Now, you can run the instances:</para>
126
114
                    <literallayout class="monospaced">euca-run-instances -k test -t m1.tiny ami-zqkyh9th</literallayout>
127
        <literallayout class="monospaced">euca-run-instances -k test -t m1.tiny ami-zqkyh9th</literallayout>
127
115
        <para>Here's a description of the parameters used above:</para>
128
        <para>Here's a description of the parameters used above:</para>
128
116
        <para>-t what type of image to create</para>
129
        <para>-t what type of image to create</para>
129
117
        <para>-k name of the key to inject in to the image at launch </para>
130
        <para>-k name of the key to inject in to the image at launch </para>
130
118
        <para>Optionally, you can use the -n parameter to indicate how many images of this type to
131
        <para>Optionally, you can use the -n parameter to indicate how many images of this type to
131
119
            launch. </para>
132
            launch. </para>
151
120
                
133
152
121
                
134
153
122
                <para>The instance will go from “launching” to “running” in a short time, and you should be able to connect via SSH using the 'ubuntu' account, with the password 'ubuntu': (replace $ipaddress with the one you got from euca-describe-instances):</para>
135
        <para>The instance will go from “launching” to “running” in a short time, and you should be
154
123
                
136
            able to connect via SSH using the 'ubuntu' account, with the password 'ubuntu': (replace
155
124
                <para><literallayout class="monospaced">ssh ubuntu@$ipaddress</literallayout></para>
137
            $ipaddress with the one you got from euca-describe-instances):</para>
156
125
                <para>The 'ubuntu' user is part of the sudoers group, so you can escalate to 'root'
138
157
126
            via the following command:</para>
139
        <para><literallayout class="monospaced">ssh ubuntu@$ipaddress</literallayout></para>
158
127
                
140
        <para>The 'ubuntu' user is part of the sudoers group, so you can escalate to 'root' via the
159
128
               <para><literallayout class="monospaced">sudo -i</literallayout></para>
141
            following command:</para>
160
129
                </section>
142
161
130
                <section>
143
        <para><literallayout class="monospaced">sudo -i</literallayout></para>
162
131
                    <?dbhtml filename="deleting-instances.html" ?>
144
    </section>
163
132
                    <title>Deleting Instances</title>
145
    <section>
164
133
                
146
        <?dbhtml filename="deleting-instances.html" ?>
165
134
                <para>When you are done playing with an instance, you can tear the instance down
147
        <title>Deleting Instances</title>
166
135
            using the following command (replace $instanceid with the instance IDs from above or
148
167
136
            look it up with euca-describe-instances):</para>
149
        <para>When you are done playing with an instance, you can tear the instance down using the
168
137
                
150
            following command (replace $instanceid with the instance IDs from above or look it up
169
138
                <para><literallayout class="monospaced">euca-terminate-instances $instanceid</literallayout></para></section>
151
            with euca-describe-instances):</para>
170
152
171
153
        <para><literallayout class="monospaced">euca-terminate-instances $instanceid</literallayout></para>
172
154
    </section>
173
139
    <section>
155
    <section>
174
140
        <?dbhtml filename="creating-custom-images.html" ?>
156
        <?dbhtml filename="creating-custom-images.html" ?>
191
141
        <info><author>
157
        <info>
192
142
            <orgname>CSS Corp-  Open Source Services</orgname>
158
            <author>
193
143
        </author><title>Image management</title></info>
159
                <orgname>CSS Corp- Open Source Services</orgname>
194
144
        <para>by <link xlink:href="http://www.csscorp.com/">CSS Corp Open Source Services</link> </para>
160
            </author>
195
145
        <para>There are several pre-built images for OpenStack available from  various sources. You can download such images and use them to get familiar with OpenStack. You can refer to  <link xlink:href="http://docs.openstack.org/cactus/openstack-compute/admin/content/starting-images.html">http://docs.openstack.org/cactus/openstack-compute/admin/content/starting-images.html</link> for details on using such images.</para>
161
            <title>Image management</title>
196
146
        <para>For any production deployment,  you may like to have the ability to bundle custom images, with a custom set of applications or configuration. This chapter will guide you through the process of creating Linux images of Debian and Redhat based distributions from scratch. We have also covered an approach to bundling Windows images.</para>
162
        </info>
197
147
        <para>There are some minor differences in the way you would bundle a Linux image, based on the distribution. Ubuntu makes it very easy by providing cloud-init package, which can be used to take care of the instance configuration at the time of launch. cloud-init handles importing ssh keys for password-less login, setting hostname etc. The instance acquires the instance specific configuration from Nova-compute by connecting to a meta data interface running on 169.254.169.254.</para>
163
        <para>by <link xlink:href="http://www.csscorp.com/">CSS Corp Open Source Services</link>
198
148
        <para>While creating the image of a distro that does not have cloud-init or an equivalent package, you may need to take care of importing the keys etc. by running a set of commands at boot time from rc.local.</para>
164
        </para>
199
149
        <para>The process used for Ubuntu and Fedora is largely the same with a few minor differences, which are explained below.</para>
165
        <para>There are several pre-built images for OpenStack available from various sources. You
200
150
        
166
            can download such images and use them to get familiar with OpenStack. You can refer to
201
151
        <para>In both cases, the documentation below assumes that you have a working KVM installation to use for creating the images. We are using the machine called &#8216;client1&#8242; as explained in the chapter on &#8220;Installation and Configuration&#8221; for this purpose.</para>
167
                <link
202
152
        <para>The approach explained below will give you disk images that represent a disk without any partitions. Nova-compute can resize such disks ( including resizing the file system) based on the instance type chosen at the time of launching the instance. These images cannot have &#8216;bootable&#8217; flag and hence it is mandatory to have associated kernel and ramdisk images. These kernel and ramdisk images need to be used by nova-compute at the time of launching the instance.</para>
168
                xlink:href="http://docs.openstack.org/cactus/openstack-compute/admin/content/starting-images.html"
203
153
        <para>However, we have also added a small section towards the end of the chapter about creating bootable images with multiple partitions that can be be used by nova to launch an instance without the need for  kernel and ramdisk images. The caveat is that while nova-compute can re-size such disks at the time of launching the instance, the file system size is not altered and hence, for all practical purposes, such disks are not re-sizable.</para>
169
                >http://docs.openstack.org/cactus/openstack-compute/admin/content/starting-images.html</link>
204
154
        <section><?dbhtml filename="creating-a-linux-image.html" ?><title>Creating a Linux Image &#8211; Ubuntu &amp; Fedora</title>
170
            for details on using such images.</para>
205
155
            
171
        <para>For any production deployment, you may like to have the ability to bundle custom
206
156
            <para>The first step would be to create a raw image on Client1. This will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need.</para>
172
            images, with a custom set of applications or configuration. This chapter will guide you
207
173
            through the process of creating Linux images of Debian and Redhat based distributions
208
174
            from scratch. We have also covered an approach to bundling Windows images.</para>
209
175
        <para>There are some minor differences in the way you would bundle a Linux image, based on
210
176
            the distribution. Ubuntu makes it very easy by providing cloud-init package, which can
211
177
            be used to take care of the instance configuration at the time of launch. cloud-init
212
178
            handles importing ssh keys for password-less login, setting hostname etc. The instance
213
179
            acquires the instance specific configuration from Nova-compute by connecting to a meta
214
180
            data interface running on 169.254.169.254.</para>
215
181
        <para>While creating the image of a distro that does not have cloud-init or an equivalent
216
182
            package, you may need to take care of importing the keys etc. by running a set of
217
183
            commands at boot time from rc.local.</para>
218
184
        <para>The process used for Ubuntu and Fedora is largely the same with a few minor
219
185
            differences, which are explained below.</para>
220
186
221
187
        <para>In both cases, the documentation below assumes that you have a working KVM
222
188
            installation to use for creating the images. We are using the machine called
223
189
            &#8216;client1&#8242; as explained in the chapter on &#8220;Installation and
224
190
            Configuration&#8221; for this purpose.</para>
225
191
        <para>The approach explained below will give you disk images that represent a disk without
226
192
            any partitions. Nova-compute can resize such disks ( including resizing the file system)
227
193
            based on the instance type chosen at the time of launching the instance. These images
228
194
            cannot have &#8216;bootable&#8217; flag and hence it is mandatory to have associated
229
195
            kernel and ramdisk images. These kernel and ramdisk images need to be used by
230
196
            nova-compute at the time of launching the instance.</para>
231
197
        <para>However, we have also added a small section towards the end of the chapter about
232
198
            creating bootable images with multiple partitions that can be be used by nova to launch
233
199
            an instance without the need for kernel and ramdisk images. The caveat is that while
234
200
            nova-compute can re-size such disks at the time of launching the instance, the file
235
201
            system size is not altered and hence, for all practical purposes, such disks are not
236
202
            re-sizable.</para>
237
203
        <section>
238
204
            <?dbhtml filename="creating-a-linux-image.html" ?>
239
205
            <title>Creating a Linux Image &#8211; Ubuntu &amp; Fedora</title>
240
206
241
207
            <para>The first step would be to create a raw image on Client1. This will represent the
242
208
                main HDD of the virtual machine, so make sure to give it as much space as you will
243
209
                need.</para>
244
157
            <literallayout class="monospaced">
210
            <literallayout class="monospaced">
245
158
211
246
159
kvm-img create -f raw server.img 5G
212
kvm-img create -f raw server.img 5G
247
160
</literallayout>
213
</literallayout>
251
161
            
214
252
162
            <simplesect><title>OS Installation</title>
215
            <simplesect>
253
163
                <para>Download the iso file of the Linux distribution you want installed in the image. The instructions below are tested on Ubuntu 11.04 Natty Narwhal 64-bit server and Fedora 14 64-bit. Most of the instructions refer to Ubuntu. The points of difference between Ubuntu and Fedora are mentioned wherever required.</para>
216
                <title>OS Installation</title>
254
217
                <para>Download the iso file of the Linux distribution you want installed in the
255
218
                    image. The instructions below are tested on Ubuntu 11.04 Natty Narwhal 64-bit
256
219
                    server and Fedora 14 64-bit. Most of the instructions refer to Ubuntu. The
257
220
                    points of difference between Ubuntu and Fedora are mentioned wherever
258
221
                    required.</para>
259
164
                <literallayout class="monospaced">
222
                <literallayout class="monospaced">
260
165
223
261
166
wget http://releases.ubuntu.com/natty/ubuntu-11.04-server-amd64.iso
224
wget http://releases.ubuntu.com/natty/ubuntu-11.04-server-amd64.iso
262
167
</literallayout>
225
</literallayout>
278
168
                <para>Boot a KVM Instance with the OS installer ISO in the virtual CD-ROM. This will start the installation process. The command below also sets up a VNC display at port 0</para>
226
                <para>Boot a KVM Instance with the OS installer ISO in the virtual CD-ROM. This will
279
169
                <literallayout class="monospaced">
227
                    start the installation process. The command below also sets up a VNC display at
280
170
228
                    port 0</para>
281
171
sudo kvm -m 256 -cdrom ubuntu-11.04-server-amd64.iso -drive   file=server.img,if=scsi,index=0 -boot d -net nic -net user -nographic  -vnc :0
229
                <literallayout class="monospaced">
282
172
</literallayout>
230
283
173
                <para>Connect to the VM through VNC (use display number :0) and finish the installation.</para>
231
sudo kvm -m 256 -cdrom ubuntu-11.04-server-amd64.iso -drive file=server.img,if=scsi,index=0 -boot d -net nic -net user -nographic -vnc :0
284
174
                <para>For Example,  where 10.10.10.4 is the IP address of client1:</para>
232
</literallayout>
285
175
                <literallayout class="monospaced">
233
                <para>Connect to the VM through VNC (use display number :0) and finish the
286
176
234
                    installation.</para>
287
177
 vncviewer 10.10.10.4 :0
235
                <para>For Example, where 10.10.10.4 is the IP address of client1:</para>
288
178
</literallayout>
236
                <literallayout class="monospaced">
289
179
                <para>During the installation of Ubuntu, create a single ext4 partition mounted on &#8216;/&#8217;. Do not create a swap partition.</para>
237
290
180
                <para>In the case of Fedora 14, the installation will not progress unless you create a swap partition. Please go ahead and create a swap partition.</para>
238
vncviewer 10.10.10.4 :0
291
181
                
239
</literallayout>
292
182
                <para>After finishing the installation, relaunch the VM by executing the following command.</para>
240
                <para>During the installation of Ubuntu, create a single ext4 partition mounted on
293
241
                    &#8216;/&#8217;. Do not create a swap partition.</para>
294
242
                <para>In the case of Fedora 14, the installation will not progress unless you create
295
243
                    a swap partition. Please go ahead and create a swap partition.</para>
296
244
297
245
                <para>After finishing the installation, relaunch the VM by executing the following
298
246
                    command.</para>
299
183
                <literallayout class="monospaced">
247
                <literallayout class="monospaced">
300
184
sudo kvm -m 256 -drive file=server.img,if=scsi,index=0,boot=on -boot c -net nic -net user -nographic -vnc :0
248
sudo kvm -m 256 -drive file=server.img,if=scsi,index=0,boot=on -boot c -net nic -net user -nographic -vnc :0
301
185
</literallayout>
249
</literallayout>
303
186
                <para>At this point, you can add all the packages you want to have installed, update the installation, add users and make any configuration changes you want in your image.</para>
250
                <para>At this point, you can add all the packages you want to have installed, update
304
251
                    the installation, add users and make any configuration changes you want in your
305
252
                    image.</para>
306
187
                <para>At the minimum, for Ubuntu you may run the following commands</para>
253
                <para>At the minimum, for Ubuntu you may run the following commands</para>
307
188
                <literallayout class="monospaced">
254
                <literallayout class="monospaced">
308
189
255
309
@@ -202,18 +268,23 @@
310
202
268
311
203
chkconfig sshd on
269
chkconfig sshd on
312
204
</literallayout>
270
</literallayout>
314
205
                <para>Also remove the network persistence rules from /etc/udev/rules.d as their presence will result in the network interface in the instance coming up as an interface other than eth0.</para>
271
                <para>Also remove the network persistence rules from /etc/udev/rules.d as their
315
272
                    presence will result in the network interface in the instance coming up as an
316
273
                    interface other than eth0.</para>
317
206
                <literallayout class="monospaced">
274
                <literallayout class="monospaced">
318
207
275
319
208
sudo rm -rf /etc/udev/rules.d/70-persistent-net.rules
276
sudo rm -rf /etc/udev/rules.d/70-persistent-net.rules
320
209
</literallayout>
277
</literallayout>
321
210
                <para>Shutdown the Virtual machine and proceed with the next steps.</para>
278
                <para>Shutdown the Virtual machine and proceed with the next steps.</para>
322
211
            </simplesect>
279
            </simplesect>
325
212
            <simplesect><title>Extracting the EXT4 partition</title>
280
            <simplesect>
326
213
                <para>The image that needs to be uploaded to OpenStack needs to be an ext4 filesystem image. Here are the steps to create a ext4 filesystem image from the raw image i.e server.img</para>
281
                <title>Extracting the EXT4 partition</title>
327
282
                <para>The image that needs to be uploaded to OpenStack needs to be an ext4
328
283
                    filesystem image. Here are the steps to create a ext4 filesystem image from the
329
284
                    raw image i.e server.img</para>
330
214
                <literallayout class="monospaced">
285
                <literallayout class="monospaced">
331
215
286
333
216
sudo losetup  -f  server.img
287
sudo losetup -f server.img
334
217
288
335
218
sudo losetup -a
289
sudo losetup -a
336
219
290
337
@@ -223,14 +294,15 @@
338
223
294
339
224
/dev/loop0: [0801]:16908388 ($filepath)
295
/dev/loop0: [0801]:16908388 ($filepath)
340
225
</literallayout>
296
</literallayout>
342
226
                <para>Observe the name of the loop device ( /dev/loop0 in our setup) when $filepath is the path to the mounted .raw file.</para>
297
                <para>Observe the name of the loop device ( /dev/loop0 in our setup) when $filepath
343
298
                    is the path to the mounted .raw file.</para>
344
227
                <para>Now we need to find out the starting sector of the partition. Run:</para>
299
                <para>Now we need to find out the starting sector of the partition. Run:</para>
345
228
                <literallayout class="monospaced">
300
                <literallayout class="monospaced">
346
229
301
347
230
sudo fdisk -cul /dev/loop0
302
sudo fdisk -cul /dev/loop0
348
231
</literallayout>
303
</literallayout>
349
232
                <para>You should see an output like this:</para>
304
                <para>You should see an output like this:</para>
351
233
                
305
352
234
                <literallayout class="monospaced">
306
                <literallayout class="monospaced">
353
235
307
354
236
Disk /dev/loop0: 5368 MB, 5368709120 bytes
308
Disk /dev/loop0: 5368 MB, 5368709120 bytes
355
@@ -245,17 +317,21 @@
356
245
317
357
246
Disk identifier: 0x00072bd4
318
Disk identifier: 0x00072bd4
358
247
319
360
248
Device Boot      Start         End      Blocks   Id  System
320
Device Boot Start End Blocks Id System
361
249
321
363
250
/dev/loop0p1   *        2048    10483711     5240832   83  Linux
322
/dev/loop0p1 * 2048 10483711 5240832 83 Linux
364
251
</literallayout>
323
</literallayout>
366
252
                <para>Make a note of the starting sector of the /dev/loop0p1 partition i.e the partition whose ID is 83. This number should be multiplied by 512 to obtain the correct value. In this case: 2048 x 512 = 1048576</para>
324
                <para>Make a note of the starting sector of the /dev/loop0p1 partition i.e the
367
325
                    partition whose ID is 83. This number should be multiplied by 512 to obtain the
368
326
                    correct value. In this case: 2048 x 512 = 1048576</para>
369
253
                <para>Unmount the loop0 device:</para>
327
                <para>Unmount the loop0 device:</para>
370
254
                <literallayout class="monospaced">
328
                <literallayout class="monospaced">
371
255
329
372
256
sudo losetup -d /dev/loop0
330
sudo losetup -d /dev/loop0
373
257
</literallayout>
331
</literallayout>
375
258
                <para>Now mount only the partition(/dev/loop0p1) of server.img which we had previously noted down, by adding the -o parameter with value previously calculated value</para>
332
                <para>Now mount only the partition(/dev/loop0p1) of server.img which we had
376
333
                    previously noted down, by adding the -o parameter with value previously
377
334
                    calculated value</para>
378
259
                <literallayout class="monospaced">
335
                <literallayout class="monospaced">
379
260
336
380
261
sudo losetup -f -o 1048576 server.img
337
sudo losetup -f -o 1048576 server.img
381
@@ -268,42 +344,53 @@
382
268
344
383
269
/dev/loop0: [0801]:16908388 ($filepath) offset 1048576
345
/dev/loop0: [0801]:16908388 ($filepath) offset 1048576
384
270
</literallayout>
346
</literallayout>
386
271
                <para>Make a note of the mount point of our device(/dev/loop0 in our setup) when $filepath is the path to the mounted .raw file.</para>
347
                <para>Make a note of the mount point of our device(/dev/loop0 in our setup) when
387
348
                    $filepath is the path to the mounted .raw file.</para>
388
272
                <para>Copy the entire partition to a new .raw file</para>
349
                <para>Copy the entire partition to a new .raw file</para>
389
273
                <literallayout class="monospaced">
350
                <literallayout class="monospaced">
390
274
351
391
275
sudo dd if=/dev/loop0 of=serverfinal.img
352
sudo dd if=/dev/loop0 of=serverfinal.img
392
276
</literallayout>
353
</literallayout>
393
277
                <para>Now we have our ext4 filesystem image i.e serverfinal.img</para>
354
                <para>Now we have our ext4 filesystem image i.e serverfinal.img</para>
395
278
                
355
396
279
                <para>Unmount the loop0 device</para>
356
                <para>Unmount the loop0 device</para>
397
280
                <literallayout class="monospaced">
357
                <literallayout class="monospaced">
398
281
358
399
282
sudo losetup -d /dev/loop0
359
sudo losetup -d /dev/loop0
400
283
</literallayout>
360
</literallayout>
401
284
            </simplesect>
361
            </simplesect>
404
285
            <simplesect><title>Tweaking /etc/fstab</title>
362
            <simplesect>
405
286
                <para>You will need to tweak /etc/fstab to make it suitable for a cloud instance. Nova-compute may resize the disk at the time of launch of instances based on the instance type chosen. This can make the UUID of the disk invalid. Hence we have to use File system label as the identifier for the partition instead of the UUID.</para>
363
                <title>Tweaking /etc/fstab</title>
406
364
                <para>You will need to tweak /etc/fstab to make it suitable for a cloud instance.
407
365
                    Nova-compute may resize the disk at the time of launch of instances based on the
408
366
                    instance type chosen. This can make the UUID of the disk invalid. Hence we have
409
367
                    to use File system label as the identifier for the partition instead of the
410
368
                    UUID.</para>
411
287
                <para>Loop mount the serverfinal.img, by running</para>
369
                <para>Loop mount the serverfinal.img, by running</para>
412
288
                <literallayout class="monospaced">
370
                <literallayout class="monospaced">
413
289
371
414
290
sudo mount -o loop serverfinal.img /mnt
372
sudo mount -o loop serverfinal.img /mnt
415
291
</literallayout>
373
</literallayout>
418
292
                <para>Edit /mnt/etc/fstab and modify the line for mounting root partition(which may look like the following)</para>
374
                <para>Edit /mnt/etc/fstab and modify the line for mounting root partition(which may
419
293
                
375
                    look like the following)</para>
420
376
421
294
                <literallayout class="monospaced">
377
                <literallayout class="monospaced">
422
295
378
424
296
UUID=e7f5af8d-5d96-45cc-a0fc-d0d1bde8f31c  /               ext4    errors=remount-ro  0       1
379
UUID=e7f5af8d-5d96-45cc-a0fc-d0d1bde8f31c / ext4 errors=remount-ro 0 1
425
297
</literallayout>
380
</literallayout>
426
298
                <para>to</para>
381
                <para>to</para>
427
299
                <literallayout class="monospaced">
382
                <literallayout class="monospaced">
428
300
383
430
301
LABEL=uec-rootfs              /          ext4           defaults     0    0
384
LABEL=uec-rootfs / ext4 defaults 0 0
431
302
</literallayout>
385
</literallayout>
432
303
            </simplesect>
386
            </simplesect>
436
304
            <simplesect><title>Fetching Metadata in Fedora</title>
387
            <simplesect>
437
305
                <para>Since, Fedora does not ship with cloud-init or an equivalent, you will need to take a few steps to have the instance  fetch the meta data like ssh keys etc.</para>
388
                <title>Fetching Metadata in Fedora</title>
438
306
                <para>Edit the /etc/rc.local file and add the following lines before the line “touch /var/lock/subsys/local”</para>
389
                <para>Since, Fedora does not ship with cloud-init or an equivalent, you will need to
439
390
                    take a few steps to have the instance fetch the meta data like ssh keys
440
391
                    etc.</para>
441
392
                <para>Edit the /etc/rc.local file and add the following lines before the line “touch
442
393
                    /var/lock/subsys/local”</para>
443
307
                <literallayout class="monospaced">
394
                <literallayout class="monospaced">
444
308
395
445
309
depmod -a
396
depmod -a
446
@@ -318,10 +405,14 @@
447
318
cat /root/.ssh/authorized_keys
405
cat /root/.ssh/authorized_keys
448
319
echo &quot;************************&quot;
406
echo &quot;************************&quot;
449
320
</literallayout>
407
</literallayout>
454
321
            </simplesect></section>
408
            </simplesect>
455
322
        <simplesect><title>Kernel and Initrd for OpenStack</title>
409
        </section>
456
323
            
410
        <simplesect>
457
324
            <para>Copy the kernel and the initrd image from /mnt/boot to user home directory. These will be used later for creating and uploading a complete virtual image to OpenStack.</para>
411
            <title>Kernel and Initrd for OpenStack</title>
458
412
459
413
            <para>Copy the kernel and the initrd image from /mnt/boot to user home directory. These
460
414
                will be used later for creating and uploading a complete virtual image to
461
415
                OpenStack.</para>
462
325
            <literallayout class="monospaced">
416
            <literallayout class="monospaced">
463
326
417
464
327
sudo cp /mnt/boot/vmlinuz-2.6.38-7-server /home/localadmin
418
sudo cp /mnt/boot/vmlinuz-2.6.38-7-server /home/localadmin
465
@@ -331,348 +422,789 @@
466
331
            <para>Unmount the Loop partition</para>
422
            <para>Unmount the Loop partition</para>
467
332
            <literallayout class="monospaced">
423
            <literallayout class="monospaced">
468
333
424
470
334
sudo umount  /mnt
425
sudo umount /mnt
471
335
</literallayout>
426
</literallayout>
472
336
            <para>Change the filesystem label of serverfinal.img to &#8216;uec-rootfs&#8217;</para>
427
            <para>Change the filesystem label of serverfinal.img to &#8216;uec-rootfs&#8217;</para>
473
337
            <literallayout class="monospaced">
428
            <literallayout class="monospaced">
474
338
429
475
339
sudo tune2fs -L uec-rootfs serverfinal.img
430
sudo tune2fs -L uec-rootfs serverfinal.img
476
340
</literallayout>
431
</literallayout>
478
341
            <para>Now, we have all the components of the image ready to be uploaded to OpenStack imaging server.</para>
432
            <para>Now, we have all the components of the image ready to be uploaded to OpenStack
479
433
                imaging server.</para>
480
342
        </simplesect>
434
        </simplesect>
483
343
        <simplesect><title>Registering with OpenStack</title>
435
        <simplesect>
484
344
            <para>The last step would be to upload the images to Openstack Imaging Server glance. The files that need to be uploaded for the above sample setup of Ubuntu are: vmlinuz-2.6.38-7-server, initrd.img-2.6.38-7-server, serverfinal.img</para>
436
            <title>Registering with OpenStack</title>
485
437
            <para>The last step would be to upload the images to Openstack Imaging Server glance.
486
438
                The files that need to be uploaded for the above sample setup of Ubuntu are:
487
439
                vmlinuz-2.6.38-7-server, initrd.img-2.6.38-7-server, serverfinal.img</para>
488
345
            <para>Run the following command</para>
440
            <para>Run the following command</para>
489
346
            <literallayout class="monospaced">
441
            <literallayout class="monospaced">
490
347
442
491
348
uec-publish-image -t image --kernel-file vmlinuz-2.6.38-7-server --ramdisk-file initrd.img-2.6.38-7-server amd64 serverfinal.img bucket1
443
uec-publish-image -t image --kernel-file vmlinuz-2.6.38-7-server --ramdisk-file initrd.img-2.6.38-7-server amd64 serverfinal.img bucket1
492
349
</literallayout>
444
</literallayout>
495
350
            <para>For Fedora, the process will be similar. Make sure that you use the right kernel and initrd files extracted above.</para>
445
            <para>For Fedora, the process will be similar. Make sure that you use the right kernel
496
351
            <para>uec-publish-image, like  several other commands from euca2ools, returns the prompt back immediately. However,  the upload process takes some time and the images will be usable only after the process is complete. You can keep checking the status using the command &#8216;euca-describe-images&#8217; as mentioned below.</para>
446
                and initrd files extracted above.</para>
497
447
            <para>uec-publish-image, like several other commands from euca2ools, returns the prompt
498
448
                back immediately. However, the upload process takes some time and the images will be
499
449
                usable only after the process is complete. You can keep checking the status using
500
450
                the command &#8216;euca-describe-images&#8217; as mentioned below.</para>
501
352
        </simplesect>
451
        </simplesect>
504
353
        <simplesect><title>Bootable Images</title>
452
        <simplesect>
505
354
            <para>You can register bootable disk images without associating kernel and ramdisk images. When you do not want the flexibility of using the same disk image with different kernel/ramdisk images, you can go for bootable disk images. This greatly simplifies the process of bundling and registering the images. However, the caveats mentioned in the introduction to this chapter apply.  Please note that the instructions below use server.img and you can skip all the cumbersome steps related to extracting the single ext4 partition.</para>
453
            <title>Bootable Images</title>
506
454
            <para>You can register bootable disk images without associating kernel and ramdisk
507
455
                images. When you do not want the flexibility of using the same disk image with
508
456
                different kernel/ramdisk images, you can go for bootable disk images. This greatly
509
457
                simplifies the process of bundling and registering the images. However, the caveats
510
458
                mentioned in the introduction to this chapter apply. Please note that the
511
459
                instructions below use server.img and you can skip all the cumbersome steps related
512
460
                to extracting the single ext4 partition.</para>
513
355
            <literallayout class="monospaced">
461
            <literallayout class="monospaced">
514
356
euca-bundle-image -i server.img
462
euca-bundle-image -i server.img
515
357
euca-upload-bundle -b mybucket -m /tmp/server.img.manifest.xml
463
euca-upload-bundle -b mybucket -m /tmp/server.img.manifest.xml
516
358
euca-register mybucket/server.img.manifest.xml
464
euca-register mybucket/server.img.manifest.xml
517
359
</literallayout>
465
</literallayout>
518
360
        </simplesect>
466
        </simplesect>
522
361
    <simplesect><title>Image Listing</title>
467
        <simplesect>
523
362
        <para>The status of the images that have been uploaded can be viewed by using euca-describe-images command. The output should like this:</para>
468
            <title>Image Listing</title>
524
363
        <literallayout class="monospaced">
469
            <para>The status of the images that have been uploaded can be viewed by using
525
470
                euca-describe-images command. The output should like this:</para>
526
471
            <literallayout class="monospaced">
527
364
472
528
365
localadmin@client1:~$ euca-describe-images
473
localadmin@client1:~$ euca-describe-images
529
366
474
535
367
IMAGE   ari-7bfac859    bucket1/initrd.img-2.6.38-7-server.manifest.xml  css     available           private         x86_64       ramdisk
475
IMAGE ari-7bfac859 bucket1/initrd.img-2.6.38-7-server.manifest.xml css available private x86_64 ramdisk
536
368
476
537
369
IMAGE   ami-5e17eb9d    bucket1/serverfinal.img.manifest.xml       css     available               private         x86_64  machine      aki-3d0aeb08    ari-7bfac859
477
IMAGE ami-5e17eb9d bucket1/serverfinal.img.manifest.xml css available private x86_64 machine aki-3d0aeb08 ari-7bfac859
538
370
478
539
371
IMAGE   aki-3d0aeb08    bucket1/vmlinuz-2.6.38-7-server.manifest.xml     css     available           private         x86_64       kernel
479
IMAGE aki-3d0aeb08 bucket1/vmlinuz-2.6.38-7-server.manifest.xml css available private x86_64 kernel
540
372
480
541
373
localadmin@client1:~$
481
localadmin@client1:~$
542
374
</literallayout>
482
</literallayout>
547
375
    </simplesect></section>
483
        </simplesect>
548
376
        <section><?dbhtml filename="creating-a-windows-image.html" ?><title>Creating a Windows Image</title>
484
    </section>
549
377
            <para>The first step would be to create a raw image on Client1, this will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need.</para>
485
    <section>
550
378
            <literallayout class="monospaced">
486
        <?dbhtml filename="creating-a-windows-image.html" ?>
551
487
        <title>Creating a Windows Image</title>
552
488
        <para>The first step would be to create a raw image on Client1, this will represent the main
553
489
            HDD of the virtual machine, so make sure to give it as much space as you will
554
490
            need.</para>
555
491
        <literallayout class="monospaced">
556
379
kvm-img create -f raw windowsserver.img 20G
492
kvm-img create -f raw windowsserver.img 20G
557
380
</literallayout>
493
</literallayout>
563
381
            <para>OpenStack presents the disk using aVIRTIO interface while launching the instance. Hence the OS needs to have drivers for VIRTIO. By default, the Windows Server 2008 ISO does not have the drivers for VIRTIO. Sso download a virtual floppy drive containing VIRTIO drivers from the following location</para>
494
        <para>OpenStack presents the disk using aVIRTIO interface while launching the instance.
564
382
            <para><link xlink:href="http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/">http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/</link></para>
495
            Hence the OS needs to have drivers for VIRTIO. By default, the Windows Server 2008 ISO
565
383
            <para>and attach it during the installation</para>
496
            does not have the drivers for VIRTIO. Sso download a virtual floppy drive containing
566
384
            <para>Start the installation by running</para>
497
            VIRTIO drivers from the following location</para>
567
385
            <literallayout class="monospaced">
498
        <para><link xlink:href="http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/"
568
499
                >http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/</link></para>
569
500
        <para>and attach it during the installation</para>
570
501
        <para>Start the installation by running</para>
571
502
        <literallayout class="monospaced">
572
386
sudo kvm -m 1024 -cdrom win2k8_dvd.iso -drive file=windowsserver.img,if=virtio,boot=on -fda virtio-win-1.1.16.vfd -boot d -nographic -vnc :0
503
sudo kvm -m 1024 -cdrom win2k8_dvd.iso -drive file=windowsserver.img,if=virtio,boot=on -fda virtio-win-1.1.16.vfd -boot d -nographic -vnc :0
573
387
504
574
388
</literallayout>
505
</literallayout>
580
389
            <para>When the installation prompts you to choose  a hard disk device you won’t see any devices available. Click on “Load drivers” at the bottom left and load the drivers from A:\i386\Win2008</para>
506
        <para>When the installation prompts you to choose a hard disk device you won’t see any
581
390
            <para>After the Installation is over, boot into it once and install any additional applications you need to install and make any configuration changes you need to make.  Also ensure that RDP is enabled as that would be the only way you can connect to a running instance of Windows. Windows firewall needs to be configured to allow incoming ICMP and RDP connections.</para>
507
            devices available. Click on “Load drivers” at the bottom left and load the drivers from
582
391
            <para>For OpenStack to allow incoming RDP Connections, use euca-authorize command to open up port 3389 as described in the chapter  on &#8220;Security&#8221;.</para>
508
            A:\i386\Win2008</para>
583
392
            <para>Shut-down the VM and upload the image to OpenStack</para>
509
        <para>After the Installation is over, boot into it once and install any additional
584
393
            <literallayout class="monospaced">
510
            applications you need to install and make any configuration changes you need to make.
585
511
            Also ensure that RDP is enabled as that would be the only way you can connect to a
586
512
            running instance of Windows. Windows firewall needs to be configured to allow incoming
587
513
            ICMP and RDP connections.</para>
588
514
        <para>For OpenStack to allow incoming RDP Connections, use euca-authorize command to open up
589
515
            port 3389 as described in the chapter on &#8220;Security&#8221;.</para>
590
516
        <para>Shut-down the VM and upload the image to OpenStack</para>
591
517
        <literallayout class="monospaced">
592
394
euca-bundle-image -i windowsserver.img
518
euca-bundle-image -i windowsserver.img
593
395
euca-upload-bundle -b mybucket -m /tmp/windowsserver.img.manifest.xml
519
euca-upload-bundle -b mybucket -m /tmp/windowsserver.img.manifest.xml
594
396
euca-register mybucket/windowsserver.img.manifest.xml
520
euca-register mybucket/windowsserver.img.manifest.xml
595
397
</literallayout>
521
</literallayout>
597
398
        </section>
522
    </section>
598
399
    <section>
523
    <section>
599
400
        <?dbhtml filename="understanding-the-compute-service-architecture.html" ?>
524
        <?dbhtml filename="understanding-the-compute-service-architecture.html" ?>
600
401
        <title>Understanding the Compute Service Architecture</title>
525
        <title>Understanding the Compute Service Architecture</title>
645
402
        <para>These basic categories describe the service architecture and what's going on within the cloud controller.</para>
526
        <para>These basic categories describe the service architecture and what's going on within
646
403
        <simplesect><title>API Server</title>
527
            the cloud controller.</para>
647
404
            
528
        <simplesect>
648
405
            <para>At the heart of the cloud framework is an API Server. This API Server makes command and control of the hypervisor, storage, and networking programmatically available to users in realization of the definition of cloud computing.
529
            <title>API Server</title>
649
406
            </para>
530
650
407
            <para>The API endpoints are basic http web services which handle authentication, authorization, and basic command and control functions using various API interfaces under the Amazon, Rackspace, and related models. This enables API compatibility with multiple existing tool sets created for interaction with offerings from other vendors. This broad compatibility prevents vendor lock-in.
531
            <para>At the heart of the cloud framework is an API Server. This API Server makes
651
408
            </para> </simplesect>
532
                command and control of the hypervisor, storage, and networking programmatically
652
409
        <simplesect><title>Message Queue</title>
533
                available to users in realization of the definition of cloud computing. </para>
653
410
            <para>
534
            <para>The API endpoints are basic http web services which handle authentication,
654
411
            A messaging queue brokers the interaction between compute nodes (processing), volumes (block storage), the networking controllers (software which controls network infrastructure), API endpoints, the scheduler (determines which physical hardware to allocate to a virtual resource), and similar components. Communication to and from the cloud controller is by HTTP requests through multiple API endpoints.</para>
535
                authorization, and basic command and control functions using various API interfaces
655
412
            
536
                under the Amazon, Rackspace, and related models. This enables API compatibility with
656
413
<para>            A typical message passing event begins with the API server receiving a request from a user. The API server authenticates the user and ensures that the user is permitted to issue the subject command. Availability of objects implicated in the request is evaluated and, if available, the request is routed to the queuing engine for the relevant workers. Workers continually listen to the queue based on their role, and occasionally their type hostname. When such listening produces a work request, the worker takes assignment of the task and begins its execution. Upon completion, a response is dispatched to the queue which is received by the API server and relayed to the originating user. Database entries are queried, added, or removed as necessary throughout the process.
537
                multiple existing tool sets created for interaction with offerings from other
657
414
</para>            
538
                vendors. This broad compatibility prevents vendor lock-in. </para>
658
415
</simplesect>
539
        </simplesect>
659
416
        <simplesect><title>Compute Worker</title>
540
        <simplesect>
660
417
            
541
            <title>Message Queue</title>
661
418
            <para>Compute workers manage computing instances on host machines. Through the API, commands are dispatched to compute workers to:</para>
542
            <para> A messaging queue brokers the interaction between compute nodes (processing),
662
419
            
543
                volumes (block storage), the networking controllers (software which controls network
663
420
            <itemizedlist>
544
                infrastructure), API endpoints, the scheduler (determines which physical hardware to
664
421
            <listitem><para>Run instances</para></listitem>
545
                allocate to a virtual resource), and similar components. Communication to and from
665
422
            <listitem><para>Terminate instances</para></listitem>
546
                the cloud controller is by HTTP requests through multiple API endpoints.</para>
666
423
            <listitem><para>Reboot instances</para></listitem>
547
667
424
            <listitem><para>Attach volumes</para></listitem>
548
            <para> A typical message passing event begins with the API server receiving a request
668
425
            <listitem><para>Detach volumes</para></listitem>
549
                from a user. The API server authenticates the user and ensures that the user is
669
426
            <listitem><para>Get console output</para></listitem></itemizedlist>
550
                permitted to issue the subject command. Availability of objects implicated in the
670
427
            </simplesect>
551
                request is evaluated and, if available, the request is routed to the queuing engine
671
428
            <simplesect><title>Network Controller</title>
552
                for the relevant workers. Workers continually listen to the queue based on their
672
429
            
553
                role, and occasionally their type hostname. When such listening produces a work
673
430
            <para>The Network Controller manages the networking resources on host machines. The API server dispatches commands through the message queue, which are subsequently processed by Network Controllers. Specific operations include:</para>
554
                request, the worker takes assignment of the task and begins its execution. Upon
674
431
            
555
                completion, a response is dispatched to the queue which is received by the API
675
432
            <itemizedlist><listitem><para>Allocate fixed IP addresses</para></listitem>
556
                server and relayed to the originating user. Database entries are queried, added, or
676
433
            <listitem><para>Configuring VLANs for projects</para></listitem>
557
                removed as necessary throughout the process. </para>
677
434
            <listitem><para>Configuring networks for compute nodes</para></listitem></itemizedlist>
558
        </simplesect>
678
435
            </simplesect>
559
        <simplesect>
679
436
<simplesect><title>Volume Workers</title>
560
            <title>Compute Worker</title>
680
437
            
561
681
438
            <para>Volume Workers interact with iSCSI storage to manage LVM-based instance volumes. Specific functions include:
562
            <para>Compute workers manage computing instances on host machines. Through the API,
682
439
            </para>
563
                commands are dispatched to compute workers to:</para>
683
440
            <itemizedlist>
564
684
441
                <listitem><para>Create volumes</para></listitem>
565
            <itemizedlist>
685
442
            <listitem><para>Delete volumes</para></listitem>
566
                <listitem>
686
443
            <listitem><para>Establish Compute volumes</para></listitem></itemizedlist>
567
                    <para>Run instances</para>
687
444
            
568
                </listitem>
688
445
    <para>Volumes may easily be transferred between instances, but may be attached to only a single instance at a time.</para></simplesect></section>
569
                <listitem>
689
570
                    <para>Terminate instances</para>
690
571
                </listitem>
691
572
                <listitem>
692
573
                    <para>Reboot instances</para>
693
574
                </listitem>
694
575
                <listitem>
695
576
                    <para>Attach volumes</para>
696
577
                </listitem>
697
578
                <listitem>
698
579
                    <para>Detach volumes</para>
699
580
                </listitem>
700
581
                <listitem>
701
582
                    <para>Get console output</para>
702
583
                </listitem>
703
584
            </itemizedlist>
704
585
        </simplesect>
705
586
        <simplesect>
706
587
            <title>Network Controller</title>
707
588
708
589
            <para>The Network Controller manages the networking resources on host machines. The API
709
590
                server dispatches commands through the message queue, which are subsequently
710
591
                processed by Network Controllers. Specific operations include:</para>
711
592
712
593
            <itemizedlist>
713
594
                <listitem>
714
595
                    <para>Allocate fixed IP addresses</para>
715
596
                </listitem>
716
597
                <listitem>
717
598
                    <para>Configuring VLANs for projects</para>
718
599
                </listitem>
719
600
                <listitem>
720
601
                    <para>Configuring networks for compute nodes</para>
721
602
                </listitem>
722
603
            </itemizedlist>
723
604
        </simplesect>
724
605
        <simplesect>
725
606
            <title>Volume Workers</title>
726
607
727
608
            <para>Volume Workers interact with iSCSI storage to manage LVM-based instance volumes.
728
609
                Specific functions include: </para>
729
610
            <itemizedlist>
730
611
                <listitem>
731
612
                    <para>Create volumes</para>
732
613
                </listitem>
733
614
                <listitem>
734
615
                    <para>Delete volumes</para>
735
616
                </listitem>
736
617
                <listitem>
737
618
                    <para>Establish Compute volumes</para>
738
619
                </listitem>
739
620
            </itemizedlist>
740
621
741
622
            <para>Volumes may easily be transferred between instances, but may be attached to only a
742
623
                single instance at a time.</para>
743
624
        </simplesect>
744
625
    </section>
745
446
    <section>
626
    <section>
746
447
        <?dbhtml filename="managing-the-cloud.html" ?>
627
        <?dbhtml filename="managing-the-cloud.html" ?>
754
448
        <title>Managing the Cloud</title><para>There are two main tools that a system administrator will find useful to manage their cloud;
628
        <title>Managing the Cloud</title>
755
449
            the nova-manage command or the Euca2ools command line commands. </para>
629
        <para>There are two main tools that a system administrator will find useful to manage their
756
450
        <para>With the Diablo release, the nova-manage command has been deprecated and you must
630
            cloud; the nova-manage command or the Euca2ools command line commands.</para>
757
451
            specify if you want to use it by using the --use_deprecated_auth flag in nova.conf. You
631
        <para> The nova-manage command may only be run by users with admin privileges. Commands for
751
452
            must also use the modified middleware stack that is commented out in the default
752
453
            paste.ini file.</para>
753
454
        <para>The nova-manage command may only be run by users with admin privileges. Commands for
758
455
            euca2ools can be used by all users, though specific commands may be restricted by Role
632
            euca2ools can be used by all users, though specific commands may be restricted by Role
762
456
            Based Access Control in the deprecated nova auth system. </para>
633
            Based Access Control. </para>
763
457
        <simplesect><title>Using the nova-manage command</title>
634
        <simplesect>
764
458
        <para>The nova-manage command may be used to perform many essential functions for
635
            <title>Using the nova-manage command</title>
765
636
            <para>The nova-manage command is used to perform many essential functions for
766
459
                administration and ongoing maintenance of nova, such as user creation, vpn
637
                administration and ongoing maintenance of nova, such as user creation, vpn
767
460
                management, and much more.</para>
638
                management, and much more.</para>
770
461
        
639
771
462
        <para>The standard pattern for executing a nova-manage command is: </para>
640
            <para>The standard pattern for executing a nova-manage command is: </para>
772
463
            <literallayout class="monospaced">nova-manage category command [args]</literallayout>
641
            <literallayout class="monospaced">nova-manage category command [args]</literallayout>
774
464
            
642
775
465
            <para>For example, to obtain a list of all projects: nova-manage project list</para>
643
            <para>For example, to obtain a list of all projects: nova-manage project list</para>
784
466
            
644
785
467
            <para>Run without arguments to see a list of available command categories: nova-manage</para>
645
            <para>Run without arguments to see a list of available command categories:
786
468
            
646
                nova-manage</para>
787
469
            <para>Command categories are: account, agent, config, db, fixed, flavor, floating, host,
647
788
470
                instance_type, image, network, project, role, service, shell, user, version, vm,
648
            <para>Command categories are: user, project, role, shell, vpn, and floating. </para>
789
471
                volume, and vpn. </para>
649
            <para>You can also run with a category argument such as user to see a list of all
790
472
            <para>You can also run with a category argument such as user to see a list of all commands in that category: nova-manage user</para>
650
                commands in that category: nova-manage user</para>
791
473
            </simplesect></section>
651
        </simplesect>
792
652
    </section>
793
474
    <section>
653
    <section>
794
475
        <?dbhtml filename="managing-compute-users.html" ?>
654
        <?dbhtml filename="managing-compute-users.html" ?>
795
476
        <title>Managing Compute Users</title>
655
        <title>Managing Compute Users</title>
802
477
        
656
803
478
            <para>Access to the Euca2ools (ec2) API is controlled by an access and secret key. The
657
        <para>Access to the Euca2ools (ec2) API is controlled by an access and secret key. The
804
479
                user’s access key needs to be included in the request, and the request must be
658
            user’s access key needs to be included in the request, and the request must be signed
805
480
                signed with the secret key. Upon receipt of API requests, Compute will verify the
659
            with the secret key. Upon receipt of API requests, Compute will verify the signature and
806
481
                signature and execute commands on behalf of the user. </para>
660
            execute commands on behalf of the user. </para>
807
482
            <para>In order to begin using nova, you will need to create a user. This can be easily
661
        <para>In order to begin using nova, you will need to create a user. This can be easily
808
483
            accomplished using the user create or user admin commands in nova-manage. user create
662
            accomplished using the user create or user admin commands in nova-manage. user create
809
484
            will create a regular user, whereas user admin will create an admin user. The syntax of
663
            will create a regular user, whereas user admin will create an admin user. The syntax of
856
485
            the command is nova-manage user create username [access] [secretword]. For example: </para>
664
            the command is nova-manage user create username [access] [secret]. For example: </para>
857
486
            <literallayout class="monospaced">nova-manage user create john my-access-key a-super-secret-key</literallayout>
665
        <literallayout class="monospaced">nova-manage user create john my-access-key a-super-secret-key</literallayout>
858
487
            <para>If you do not specify an access or secret key, a random uuid will be created
666
        <para>If you do not specify an access or secret key, a random uuid will be created
859
488
                automatically.</para>
667
            automatically.</para>
860
489
     
668
861
490
        <simplesect><title>Credentials</title>
669
        <simplesect>
862
491
        
670
            <title>Credentials</title>
863
492
        <para>Nova can generate a handy set of credentials for a user. These credentials include a CA for bundling images and a file for setting environment variables to be used by euca2ools. If you don’t need to bundle images, just the environment script is required. You can export one with the project environment command. The syntax of the command is nova-manage project environment project_id user_id [filename]. If you don’t specify a filename, it will be exported as novarc. After generating the file, you can simply source it in bash to add the variables to your environment:</para>
671
864
493
        
672
            <para>Nova can generate a handy set of credentials for a user. These credentials include
865
494
        <literallayout class="monospaced">
673
                a CA for bundling images and a file for setting environment variables to be used by
866
495
        nova-manage project environment john_project john
674
                euca2ools. If you don’t need to bundle images, just the environment script is
867
496
        . novarc</literallayout>
675
                required. You can export one with the project environment command. The syntax of the
868
497
        
676
                command is nova-manage project environment project_id user_id [filename]. If you
869
498
        <para>If you do need to bundle images, you will need to get all of the credentials using project zipfile. Note that zipfile will give you an error message if networks haven’t been created yet. Otherwise zipfile has the same syntax as environment, only the default file name is nova.zip. Example usage:
677
                don’t specify a filename, it will be exported as novarc. After generating the file,
870
499
        </para>
678
                you can simply source it in bash to add the variables to your environment:</para>
871
500
        <literallayout class="monospaced">
679
872
501
        nova-manage project zipfile john_project john
680
            <literallayout class="monospaced">
873
502
        unzip nova.zip
681
nova-manage project environment john_project john
874
503
        . novarc
682
. novarc</literallayout>
875
504
        </literallayout></simplesect>
683
876
505
        <simplesect><title>Role Based Access Control</title>
684
            <para>If you do need to bundle images, you will need to get all of the credentials using
877
506
        
685
                project zipfile. Note that zipfile will give you an error message if networks
878
507
        <para>Roles control the API actions that a user is allowed to perform. For example, a user
686
                haven’t been created yet. Otherwise zipfile has the same syntax as environment, only
879
508
                cannot allocate a public ip without the netadmin role. It is important to remember
687
                the default file name is nova.zip. Example usage: </para>
880
509
                that a users de facto permissions in a project is the intersection of user (global)
688
            <literallayout class="monospaced">
881
510
                roles and project (local) roles. So for john to have netadmin permissions in his
689
nova-manage project zipfile john_project john
882
511
                project, he needs to separate roles specified. You can add roles with role add. The
690
unzip nova.zip
883
512
                syntax is nova-manage role add user_id role [project_id]. Let’s give john the
691
. novarc
884
513
                netadmin role for his project:</para>
692
</literallayout>
885
514
        
693
        </simplesect>
886
515
        <literallayout class="monospaced">        nova-manage role add john netadmin
694
        <simplesect>
887
516
        nova-manage role add john netadmin john_project</literallayout>
695
            <title>Role Based Access Control</title>
888
517
        
696
889
518
        <para>Role-based access control (RBAC) is an approach to restricting system access to authorized users based on an individual's role within an organization. Various employee functions require certain levels of system access in order to be successful. These functions are mapped to defined roles and individuals are categorized accordingly. Since users are not assigned permissions directly, but only acquire them through their role (or roles), management of individual user rights becomes a matter of assigning appropriate roles to the user. This simplifies common operations, such as adding a user, or changing a user’s department.
697
            <para>Roles control the API actions that a user is allowed to perform. For example, a
890
519
        </para>
698
                user cannot allocate a public ip without the netadmin role. It is important to
891
520
        <para>Nova’s rights management system employs the RBAC model and currently supports the following five roles:</para>
699
                remember that a users de facto permissions in a project is the intersection of user
892
521
        
700
                (global) roles and project (local) roles. So for john to have netadmin permissions
893
522
        <itemizedlist>
701
                in his project, he needs to separate roles specified. You can add roles with role
894
523
            <listitem><para>Cloud Administrator. (cloudadmin) Users of this class enjoy complete system access.</para></listitem>
702
                add. The syntax is nova-manage role add user_id role [project_id]. Let’s give john
895
524
        <listitem><para>IT Security. (itsec) This role is limited to IT security personnel. It permits role holders to quarantine instances.</para></listitem>
703
                the netadmin role for his project:</para>
896
525
        <listitem><para>System Administrator. (sysadmin)The default for project owners, this role affords users the ability to add other users to a project, interact with project images, and launch and terminate instances.</para></listitem>
704
897
526
        <listitem><para>Network Administrator. (netadmin) Users with this role are permitted to allocate and assign publicly accessible IP addresses as well as create and modify firewall rules.</para></listitem>
705
            <literallayout class="monospaced"> nova-manage role add john netadmin
898
527
        <listitem><para>Developer. This is a general purpose role that is assigned to users by default.</para></listitem>
706
nova-manage role add john netadmin john_project</literallayout>
899
528
            <listitem><para>Project Manager. (projectmanager) This is a role that is assigned upon project creation and can't be added or removed, but this role can do anything a sysadmin can do.</para></listitem></itemizedlist>
707
900
529
        
708
            <para>Role-based access control (RBAC) is an approach to restricting system access to
901
530
        <para>RBAC management is exposed through the dashboard for simplified user management.</para></simplesect></section>
709
                authorized users based on an individual's role within an organization. Various
902
710
                employee functions require certain levels of system access in order to be
903
711
                successful. These functions are mapped to defined roles and individuals are
904
712
                categorized accordingly. Since users are not assigned permissions directly, but only
905
713
                acquire them through their role (or roles), management of individual user rights
906
714
                becomes a matter of assigning appropriate roles to the user. This simplifies common
907
715
                operations, such as adding a user, or changing a user’s department. </para>
908
716
            <para>Nova’s rights management system employs the RBAC model and currently supports the
909
717
                following five roles:</para>
910
718
            <itemizedlist>
911
719
                <listitem>
912
720
                    <para>Cloud Administrator. (cloudadmin) Users of this class enjoy complete
913
721
                        system access.</para>
914
722
                </listitem>
915
723
                <listitem>
916
724
                    <para>IT Security. (itsec) This role is limited to IT security personnel. It
917
725
                        permits role holders to quarantine instances.</para>
918
726
                </listitem>
919
727
                <listitem>
920
728
                    <para>System Administrator. (sysadmin)The default for project owners, this role
921
729
                        affords users the ability to add other users to a project, interact with
922
730
                        project images, and launch and terminate instances.</para>
923
731
                </listitem>
924
732
                <listitem>
925
733
                    <para>Network Administrator. (netadmin) Users with this role are permitted to
926
734
                        allocate and assign publicly accessible IP addresses as well as create and
927
735
                        modify firewall rules.</para>
928
736
                </listitem>
929
737
                <listitem>
930
738
                    <para>Developer. This is a general purpose role that is assigned to users by
931
739
                        default.</para>
932
740
                </listitem>
933
741
                <listitem>
934
742
                    <para>Project Manager. (projectmanager) This is a role that is assigned upon
935
743
                        project creation and can't be added or removed, but this role can do
936
744
                        anything a sysadmin can do.</para>
937
745
                </listitem>
938
746
            </itemizedlist>
939
747
940
748
            <para>RBAC management is exposed through the dashboard for simplified user
941
749
                management.</para>
942
750
        </simplesect>
943
751
    </section>
944
531
    <section>
752
    <section>
945
532
        <?dbhtml filename="managing-volumes.html" ?>
753
        <?dbhtml filename="managing-volumes.html" ?>
953
533
        <title>Managing Volumes</title><para>Nova-volume is the service that allows you to give extra block level storage to your OpenStack
754
        <title>Managing Volumes</title>
954
534
            Compute instances. You may recognize this as a similar offering that Amazon EC2 offers,
755
        <para>Nova-volume is the service that allows you to give extra block level storage to your
955
535
            Elastic Block Storage (EBS). However, nova-volume is not the same implementation that
756
            OpenStack Compute instances. You may recognize this as a similar offering that Amazon
956
536
            EC2 uses today. Nova-volume is an iSCSI solution that employs the use of Logical Volume
757
            EC2 offers, Elastic Block Storage (EBS). However, nova-volume is not the same
957
537
            Manager (LVM) for Linux. Note that a volume may only be attached to one instance at a
758
            implementation that EC2 uses today. Nova-volume is an iSCSI solution that employs the
958
538
            time. This is not a ‘shared storage’ solution like a SAN which multiple servers can
759
            use of Logical Volume Manager (LVM) for Linux. Note that a volume may only be attached
959
539
            attach to.</para>
760
            to one instance at a time. This is not a ‘shared storage’ solution like a SAN of NFS on
960
761
            which multiple servers can attach to.</para>
961
762
        <para> Before going any further ; let's present the nova-volume implementation into Open
962
763
            stack : </para>
963
764
        <para>The nova-volumes service uses iscsi-exposed LVM volumes to the compute nodes which run
964
765
            instances. Thus, there are two components involved : </para>
965
766
        <para>- lvm2, which works with a VG called "nova-volumes" (Reffer to
966
767
            http://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux) for further details) </para>
967
768
        <para>- open-iscsi, the iscsi implementation which manages iscsi sessions on the compute
968
769
            nodes. </para>
969
770
        <para>Here is what happens from the volume creation to it's attachment (we use here the
970
771
            euca2ools, but the same explanation goes with the API): </para>
971
772
        <orderedlist>
972
773
            <listitem>
973
774
                <para>The volume is created via $euca-create-volume; which creates an LV into the VG
974
775
                    "nova-volumes" </para>
975
776
            </listitem>
976
777
            <listitem>
977
778
                <para>The volume is attached to an instance via $euca-attach-volume; which creates a
978
779
                    unique iscsi IQN that will be exposed to the compute node. </para>
979
780
            </listitem>
980
781
            <listitem>
981
782
                <para>The compute node which run the concerned instance has now an active ISCSI
982
783
                    session; and a new local storage (usually a /dev/sdX disk) </para>
983
784
            </listitem>
984
785
            <listitem>
985
786
                <para>libvirt uses that local storage as a storage for the instance; the instance
986
787
                    get a new disk (usually a /dev/vdX disk) </para>
987
788
            </listitem>
988
789
        </orderedlist>
989
540
        <para>For this particular walkthrough, there is one cloud controller running nova-api,
790
        <para>For this particular walkthrough, there is one cloud controller running nova-api,
995
541
            nova-compute, nova-scheduler, nova-objectstore, and nova-network. There are two
791
            nova-compute, nova-scheduler, nova-objectstore, nova-network and nova-volumes. There are
996
542
            additional compute nodes running both nova-compute and nova-volume. The walkthrough uses
792
            two additional compute nodes running nova-compute. The walkthrough uses a custom
997
543
            a custom partitioning scheme that carves out 60GB of space and labels it as LVM. The
793
            partitioning scheme that carves out 60GB of space and labels it as LVM. The network is a
998
544
            network is a /28 .80-.95, and FlatManger is the NetworkManager setting for OpenStack
794
            /28 .80-.95, and FlatManger is the NetworkManager setting for OpenStack Compute (Nova). </para>
999
545
            Compute (Nova). </para>
795
        <para>Please note that the network mode doesn't interfere at all the way nova-volumes work,
1000
796
            but it is essential for nova-volumes to work that the mode you are currently using is
1001
797
            set up. Please reffer to the Section 7 "Networking" for much details.</para>
1002
546
        <para>To set up Compute to use volumes, ensure that nova-volume is installed along with
798
        <para>To set up Compute to use volumes, ensure that nova-volume is installed along with
1004
547
            lvm2. </para>
799
            lvm2. The guide will be split in four parts : </para>
1005
548
        <para>
800
        <para>
1007
549
            <literallayout class="monospaced">apt-get install lvm2 nova-volume</literallayout>
801
            <itemizedlist>
1008
802
                <listitem>
1009
803
                    <para>A- Installing nova-volumes on the cloud controller.</para>
1010
804
                </listitem>
1011
805
                <listitem>
1012
806
                    <para>B- Configuring nova-volumes on the compute nodes.</para>
1013
807
1014
808
                </listitem>
1015
809
                <listitem>
1016
810
                    <para>C- Troubleshoot your nova-volumes installation.</para>
1017
811
                </listitem>
1018
812
                <listitem>
1019
813
                    <para>D- Advanced tips : Disaster Recovery Process, Backup your nova-volumes,
1020
814
                        Browse your nova-volumes from the cloud-controller </para>
1021
815
                </listitem>
1022
816
            </itemizedlist>
1023
550
        </para>
817
        </para>
1106
551
        <simplesect><title>Configure Volumes for use with nova-volume</title>
818
1107
552
            <para>If you do not already have LVM volumes on hand, but have free drive space, you
819
        <simplesect>
1108
553
                will need to create a LVM volume before proceeding.</para>
820
            <title>A- Install nova-volumes on the cloud controller.</title>
1109
554
            <para>Here is a short run down of how you would create a LVM from free drive space on your system.</para>
821
            <para> This is simply done by installing the two components on the cloud controller : <literallayout class="monospaced"><code>apt-get install lvm2 nova-volume</code></literallayout><itemizedlist>
1110
555
            <para>Start off by issuing an fdisk command to your drive with the free space:</para>
822
                    <listitem>
1111
556
            <para>
823
                        <para>
1112
557
                <literallayout class="monospaced">fdisk /dev/sda</literallayout></para>
824
                            <emphasis role="bold">Configure Volumes for use with
1113
558
            <para>Once in fdisk, perform the following commands:</para>
825
                                nova-volumes</emphasis></para>
1114
559
            <orderedlist>
826
                        <para> If you do not already have LVM volumes on hand, but have free drive
1115
560
                <listitem><para>Press ‘<code>n'</code> to create a new disk partition,</para></listitem>
827
                            space, you will need to create a LVM volume before proceeding. Here is a
1116
561
                <listitem><para>Press <code>'p'</code> to create a primary disk partition,</para></listitem>
828
                            short run down of how you would create a LVM from free drive space on
1117
562
                <listitem><para>Press <code>'1'</code> to denote it as 1st disk partition,</para></listitem>
829
                            your system. Start off by issuing an fdisk command to your drive with
1118
563
                
830
                            the free space:
1119
564
                <listitem><para>Either press ENTER twice to accept the default of 1st and last cylinder – to convert the remainder of hard disk to a single disk partition
831
                            <literallayout class="monospaced"><code>fdisk /dev/sda</code></literallayout>
1120
565
                    -OR-
832
                            Once in fdisk, perform the following commands: <orderedlist>
1121
566
                        press ENTER once to accept the default of the 1st, and then choose how big you want the partition to be by specifying +size{K,M,G} e.g. +5G or +6700M.</para></listitem>
833
                                <listitem>
1122
567
                <listitem><para>Press <code>'t', then</code> select the new partition you made.</para></listitem>
834
                                    <para>Press ‘<code>n'</code> to create a new disk
1123
568
                
835
                                        partition,</para>
1124
569
                <listitem><para>Press <code>'8e'</code> change your new partition to 8e, i.e. Linux LVM partition type.</para></listitem>
836
                                </listitem>
1125
570
                <listitem><para>Press ‘<code>p'</code> to display the hard disk partition setup. Please take note that the first partition is denoted as /dev/sda1 in Linux.</para></listitem>
837
                                <listitem>
1126
571
                <listitem><para>Press <code>'w'</code> to write the partition table and exit fdisk upon completion.</para></listitem>
838
                                    <para>Press <code>'p'</code> to create a primary disk
1127
572
            </orderedlist>
839
                                        partition,</para>
1128
573
            <para>Refresh your partition table to ensure your new partition shows up, and verify
840
                                </listitem>
1129
574
                with fdisk.</para>
841
                                <listitem>
1130
575
            
842
                                    <para>Press <code>'1'</code> to denote it as 1st disk
1131
576
            <para><literallayout class="monospaced">partprobe
843
                                        partition,</para>
1132
577
fdisk -l (you should see your new partition in this listing)</literallayout></para>
844
                                </listitem>
1133
578
            <para>Here is how you can set up partitioning during the OS install to prepare for this
845
                                <listitem>
1134
579
                nova-volume configuration:</para>
846
                                    <para>Either press ENTER twice to accept the default of 1st and
1135
580
            <para>root@osdemo03:~# fdisk -l</para>
847
                                        last cylinder – to convert the remainder of hard disk to a
1136
581
            <para><literallayout class="monospaced">
848
                                        single disk partition -OR- press ENTER once to accept the
1137
582
                Device Boot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; End&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Blocks&nbsp;&nbsp; Id&nbsp; System
849
                                        default of the 1st, and then choose how big you want the
1138
583
                
850
                                        partition to be by specifying +size{K,M,G} e.g. +5G or
1139
584
                /dev/sda1&nbsp;&nbsp;&nbsp; * &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 12158&nbsp;&nbsp;&nbsp; 97280&nbsp;&nbsp; 83&nbsp; Linux
851
                                        +6700M.</para>
1140
585
                /dev/sda2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 12158&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24316&nbsp;&nbsp;&nbsp; 97655808&nbsp;&nbsp; 83&nbsp; Linux
852
                                </listitem>
1141
586
                        
853
                                <listitem>
1142
587
                /dev/sda3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24316&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24328&nbsp;&nbsp;&nbsp;&nbsp; 97654784&nbsp;&nbsp;&nbsp;&nbsp; 83&nbsp; Linux
854
                                    <para>Press <code>'t', then</code> select the new partition you
1143
588
                /dev/sda4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24328&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 42443&nbsp;&nbsp; 145507329&nbsp;&nbsp;&nbsp; 5&nbsp; Extended
855
                                        made.</para>
1144
589
                                
856
                                </listitem>
1145
590
                /dev/sda5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24328&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 32352&nbsp;&nbsp;&nbsp; 64452608&nbsp;&nbsp; 8e&nbsp; Linux LVM
857
                                <listitem>
1146
591
                /dev/sda6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 32352&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 40497&nbsp;&nbsp;&nbsp; 65428480&nbsp;&nbsp; 8e&nbsp; Linux LVM
858
                                    <para>Press <code>'8e'</code> change your new partition to 8e,
1147
592
                                        
859
                                        i.e. Linux LVM partition type.</para>
1148
593
                /dev/sda7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 40498&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 42443&nbsp;&nbsp;&nbsp; 15624192&nbsp;&nbsp; 82&nbsp; Linux swap / Solaris
860
                                </listitem>
1149
594
</literallayout></para>
861
                                <listitem>
1150
595
            <para>Now that you have identified a partition has been labeled for LVM use, perform the
862
                                    <para>Press ‘<code>p'</code> to display the hard disk partition
1151
596
                following steps to configure LVM and prepare it as nova-volume. You must name your
863
                                        setup. Please take note that the first partition is denoted
1152
597
                volume group ‘nova-volumes’ or things will not work as expected:</para>
864
                                        as /dev/sda1 in Linux.</para>
1153
598
            <literallayout class="monospaced">
865
                                </listitem>
1154
599
                pvcreate /dev/sda5 
866
                                <listitem>
1155
600
                vgcreate nova-volumes /dev/sda5 </literallayout></simplesect><simplesect><title>Configure iscsitarget</title>        <para>If you have a multinode installation of Compute, you may want nova-volume on the same node as nova-compute, although it is not required.</para><para>By default, when the ‘iscsitarget’ package is installed, it is not started, nor enabled by
867
                                    <para>Press <code>'w'</code> to write the partition table and
1156
601
                default. You need to perform the following two steps to configure the iscsitarget
868
                                        exit fdisk upon completion.</para>
1157
602
                service in order for nova-volume to work.</para>
869
                                    <para>Refresh your partition table to ensure your new partition
1158
603
            <para>
870
                                        shows up, and verify with fdisk. We then inform the OS about
1159
604
            <literallayout class="monospaced">
871
                                        the table partition update : </para>
1160
605
            sed -i ‘s/false/true/g’ /etc/default/iscsitarget
872
                                    <para>
1161
606
            service iscsitarget start</literallayout></para></simplesect><simplesect><title>Configure nova.conf Flag File</title>
873
                                        <literallayout class="monospaced"><code>partprobe</code>
1162
607
        <para>Edit your nova.conf to include a new flag, –iscsi_ip_prefix=192.168. The value of this flag needs to be set to something that will differentiate the IP addresses, to ensure it uses IP addresses that are route-able, such as a prefix on the private network. </para></simplesect>
874
1163
608
    <simplesect><title>Start nova-volume and Create Volumes</title>
875
Again :
1164
609
    
876
<code>fdisk -l (you should see your new partition in this listing)</code></literallayout>
1165
610
    <para>You are now ready to fire up nova-volume, and start creating volumes!</para>
877
                                    </para>
1166
611
    
878
                                    <para>Here is how you can set up partitioning during the OS
1167
612
    <para><literallayout class="monospaced">service nova-volume start</literallayout></para>
879
                                        install to prepare for this nova-volume
1168
613
    
880
                                        configuration:</para>
1169
614
    <para>Once the service is started, login to your controller and ensure you’ve properly sourced your ‘novarc’ file.  You will use the following commands to interface with nova-volume:</para>
881
                                    <para>root@osdemo03:~# fdisk -l </para>
1170
615
    
882
                                    <para>
1171
616
<para><literallayout class="monospaced">    euca-create-volume
883
                                        <programlisting>
1172
617
    euca-attach-volume
884
Device Boot Start End Blocks Id System
1173
618
    euca-detach-volume
885
1174
619
    euca-delete-volume</literallayout></para>
886
/dev/sda1 * 1 12158 97280 83 Linux
1175
620
        
887
/dev/sda2 12158 24316 97655808 83 Linux
1176
621
        <para>One of the first things you should do is make sure that nova-volume is checking in as expected.&nbsp; You can do so using nova-manage:</para>
888
1177
622
        <para><literallayout class="monospaced">nova-manage service list</literallayout></para>
889
/dev/sda3 24316 24328 97654784 83 Linux
1178
623
        <para>If you see a ‘nova-volume’ in there, you are looking good.&nbsp; Now create a new volume:</para>
890
/dev/sda4 24328 42443 145507329 5 Extended
1179
624
        <para><literallayout class="monospaced">euca-create-volume -s 7 -z nova&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (-s refers to the size of the volume in GB, and -z is the default zone (usually nova))</literallayout></para>
891
1180
625
        
892
<emphasis role="bold">/dev/sda5 24328 32352 64452608 8e Linux LVM</emphasis>
1181
626
        <para>You should get some output similar to this:</para>
893
<emphasis role="bold">/dev/sda6 32352 40497 65428480 8e Linux LVM</emphasis>
1182
627
        <para><literallayout class="monospaced">VOLUME&nbsp; vol-0000000b&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; creating (wayne, None, None, None)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2011-02-11 06:58:46.941818</literallayout></para>
894
1183
628
        <para>You can view that status of the volumes creation using ‘euca-describe-volumes’.&nbsp; Once that status is ‘available,’ it is ready to be attached to an instance:</para>
895
/dev/sda7 40498 42443 15624192 82 Linux swap / Solaris
1184
629
        <para><literallayout class="monospaced">euca-attach-volume vol-00000009 -i i-00000008 -d /dev/vdb</literallayout></para>
896
</programlisting>
1185
630
        
897
                                    </para>
1186
631
        <para>If you do not get any errors, it is time to login to instance ‘i-00000008′ and see if the new space is there.&nbsp; Here is the output from ‘fdisk -l’ from i-00000008:</para>
898
                                    <para>Now that you have identified a partition has been labeled
1187
632
        <para><literallayout class="monospaced">Disk /dev/vda: 10.7 GB, 10737418240 bytes
899
                                        for LVM use, perform the following steps to configure LVM
1188
900
                                        and prepare it as nova-volume. <emphasis role="bold">You
1189
901
                                            must name your volume group ‘nova-volumes’ or things
1190
902
                                            will not work as expected</emphasis>:</para>
1191
903
                                    <literallayout class="monospaced"><code>pvcreate /dev/sda5
1192
904
vgcreate nova-volumes /dev/sda5</code> </literallayout>
1193
905
                                </listitem>
1194
906
                            </orderedlist></para>
1195
907
                    </listitem>
1196
908
                </itemizedlist></para>
1197
909
        </simplesect>
1198
910
        <simplesect>
1199
911
            <title> B- Configuring nova-volumes on the compute nodes</title>
1200
912
            <para> Since you have created the VG, you will be able to use the following tools for
1201
913
                managing your volumes : </para>
1202
914
            <simpara><code>euca-create-volume</code></simpara>
1203
915
            <simpara><code>euca-attach-volume</code></simpara>
1204
916
            <simpara><code>euca-detach-volume</code></simpara>
1205
917
            <simpara><code>euca-delete-volume</code></simpara>
1206
918
            <itemizedlist>
1207
919
                <listitem>
1208
920
                    <para>
1209
921
                        <emphasis role="bold">Installing and Configure the iscsi
1210
922
                            initiator</emphasis></para>
1211
923
                    <para> Remember that every node will act as the iscsi initiator while the server
1212
924
                        running nova-volumes will act as the iscsi target. So make sure, before
1213
925
                        going further that your nodes can communicate with you nova-volumes server.
1214
926
                        If you have a firewall running on it, make sure that the port 3260 (tcp)
1215
927
                        accepts incoming connections. </para>
1216
928
                    <para>First install the open-iscsi package <emphasis role="bold">on your
1217
929
                            compute-nodes only :</emphasis>
1218
930
                        <literallayout class="monospaced"><code>apt-get install open-iscsi</code> </literallayout></para>
1219
931
                    <para>You have to enable it so the startut script (/etc/init.d/open-iscsi) will
1220
932
                        work :
1221
933
                        <literallayout class="monospaced"><code>sed -i ‘s/false/true/g’ /etc/default/iscsitarget</code></literallayout>
1222
934
                        Then run :
1223
935
                        <literallayout class="monospaced"><code>service iscsitarget start</code></literallayout></para>
1224
936
                </listitem>
1225
937
                <listitem>
1226
938
                    <para><emphasis role="bold">Configure nova.conf Flag File</emphasis></para>
1227
939
                    <para>Edit your nova.conf to include a new flag, "–iscsi_ip_prefix=192.168." The
1228
940
                        flag will be used by the compute node when the iscsi discovery will be
1229
941
                        performed and the session created. The prefix based on the two first bytes
1230
942
                        will allows the iscsi discovery to use all the available routes (also known
1231
943
                        as multipathing) to the iscsi server (eg. nova-volumes) into your network.
1232
944
                        We will see into the "Troubleshooting" section how to deal with ISCSI
1233
945
                        sessions.</para>
1234
946
                </listitem>
1235
947
                <listitem>
1236
948
                    <para>
1237
949
                        <emphasis role="bold">Start nova-volume and Create Volumes</emphasis></para>
1238
950
                    <para>You are now ready to fire up nova-volume, and start creating
1239
951
                        volumes!</para>
1240
952
1241
953
                    <para><literallayout class="monospaced"><code>service nova-volume start</code></literallayout></para>
1242
954
1243
955
                    <para>Once the service is started, login to your controller and ensure you’ve
1244
956
                        properly sourced your ‘novarc’ file. You will be able to use the euca2ools
1245
957
                        related to volumes interactions (see above).</para>
1246
958
                    <para/>
1247
959
1248
960
                    <para>One of the first things you should do is make sure that nova-volume is
1249
961
                        checking in as expected. You can do so using nova-manage:</para>
1250
962
                    <para><literallayout class="monospaced"><code>nova-manage service list</code></literallayout></para>
1251
963
                    <para>If you see a smiling ‘nova-volume’ in there, you are looking good. Now
1252
964
                        create a new volume:</para>
1253
965
                    <para><literallayout class="monospaced"><code>euca-create-volume -s 7 -z nova </code> (-s refers to the size of the volume in GB, and -z is the default zone (usually nova))</literallayout></para>
1254
966
1255
967
                    <para>You should get some output similar to this:</para>
1256
968
                    <para>
1257
969
                        <programlisting>VOLUME vol-0000000b 7 creating (wayne, None, None, None) 2011-02-11 06:58:46.941818</programlisting>
1258
970
                    </para>
1259
971
                    <para>You can view that status of the volumes creation using
1260
972
                        ‘euca-describe-volumes’. Once that status is ‘available,’ it is ready to be
1261
973
                        attached to an instance:</para>
1262
974
                    <para><literallayout class="monospaced"><code>euca-attach-volume -i i-00000008 -d /dev/vdb vol-00000009</code> (-i reffers to the instance you will attach the volume to, -d is the mountpoint<emphasis role="bold"> (on the compute-node !</emphasis> and then the volume name.)</literallayout></para>
1263
975
                    <para>By doing that, the compute-node which runs the instance basically performs
1264
976
                        an iscsi connection and creates a session. You can ensure that the session
1265
977
                        has been created by running : </para>
1266
978
                    <para><code>iscsciadm -m session </code></para>
1267
979
                    <para>Which should output : </para>
1268
980
                    <para>
1269
981
                        <programlisting>root@nova-cn1:~# iscsiadm -m session
1270
982
tcp: [1] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-0000000b</programlisting>
1271
983
                    </para>
1272
984
1273
985
                    <para>If you do not get any errors, it is time to login to instance ‘i-00000008′
1274
986
                        and see if the new space is there. You can check the volume attachemnt by
1275
987
                        running : </para>
1276
988
                    <para><code>dmesg | tail </code></para>
1277
989
                    <para>You should from there see a new disk. Here is the output from ‘fdisk -l’
1278
990
                        from i-00000008:</para>
1279
991
                    <programlisting>Disk /dev/vda: 10.7 GB, 10737418240 bytes
1280
633
16 heads, 63 sectors/track, 20805 cylinders
992
16 heads, 63 sectors/track, 20805 cylinders
1281
634
Units = cylinders of 1008 * 512 = 516096 bytes
993
Units = cylinders of 1008 * 512 = 516096 bytes
1282
635
Sector size (logical/physical): 512 bytes / 512 bytes
994
Sector size (logical/physical): 512 bytes / 512 bytes
1283
636
I/O size (minimum/optimal): 512 bytes / 512 bytes
995
I/O size (minimum/optimal): 512 bytes / 512 bytes
1316
637
Disk identifier: 0×00000000</literallayout></para>
996
Disk identifier: 0×00000000
1317
638
            <literallayout>Disk /dev/vda doesn’t contain a valid partition table</literallayout>
997
Disk /dev/vda doesn’t contain a valid partition table
1318
639
        
998
<emphasis role="bold">Disk /dev/vdb: 21.5 GB, 21474836480 bytes &lt;—–Here is our new volume!</emphasis>
1319
640
        <para>
999
16 heads, 63 sectors/track, 41610 cylinders
1320
641
                <literallayout>Disk /dev/vdb: 21.5 GB, 21474836480 bytes&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;—–Here is our new volume!&nbsp;
1000
Units = cylinders of 1008 * 512 = 516096 bytes
1321
642
16 heads, 63 sectors/track, 41610 cylinders 
1001
Sector size (logical/physical): 512 bytes / 512 bytes
1322
643
Units = cylinders of 1008 * 512 = 516096 bytes 
1002
I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0×00000000 </programlisting>
1323
644
Sector size (logical/physical): 512 bytes / 512 bytes 
1003
1324
645
I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0×00000000</literallayout>
1004
                    <para>Now with the space presented, let’s configure it for use:</para>
1325
646
            </para>
1005
                    <para><literallayout class="monospaced"><code>fdisk /dev/vdb</code></literallayout></para>
1326
647
        <para>Disk /dev/vdb doesn’t contain a valid partition table</para>
1006
                    <orderedlist>
1327
648
        
1007
                        <listitem>
1328
649
        <para>Now with the space presented, let’s configure it for use:</para>
1008
                            <para>Press ‘<code>n'</code> to create a new disk partition.</para>
1329
650
        <para><literallayout class="monospaced">fdisk /dev/vdb</literallayout></para>
1009
                        </listitem>
1330
651
        <orderedlist>
1010
                        <listitem>
1331
652
            <listitem><para>Press ‘<code>n'</code> to create a new disk partition.</para></listitem>
1011
                            <para>Press <code>'p'</code> to create a primary disk partition.</para>
1332
653
            <listitem><para>Press <code>'p'</code> to create a primary disk partition.</para></listitem>
1012
                        </listitem>
1333
654
            <listitem><para>Press <code>'1'</code> to denote it as 1st disk partition.</para></listitem>
1013
                        <listitem>
1334
655
            
1014
                            <para>Press <code>'1'</code> to denote it as 1st disk partition.</para>
1335
656
            <listitem><para>Press ENTER twice to accept the default of 1st and last cylinder – to convert the remainder of
1015
                        </listitem>
1336
657
                        hard disk to a single disk partition.</para></listitem>
1016
1337
658
            <listitem><para>Press <code>'t', then</code> select the new partition you made.</para></listitem>
1017
                        <listitem>
1338
659
            <listitem><para>Press <code>'83'</code> change your new partition to 83, i.e. Linux partition type.</para></listitem>
1018
                            <para>Press ENTER twice to accept the default of 1st and last cylinder –
1339
660
            <listitem><para>Press ‘<code>p'</code> to display the hard disk partition setup. Please take note that the
1019
                                to convert the remainder of hard disk to a single disk
1340
661
                        first partition is denoted as /dev/vda1 in your instance.</para></listitem>
1020
                                partition.</para>
1341
662
            
1021
                        </listitem>
1342
663
            <listitem>
1022
                        <listitem>
1343
664
                    <para>Press <code>'w'</code> to write the partition table and exit fdisk upon
1023
                            <para>Press <code>'t', then</code> select the new partition you
1344
665
                        completion.</para>
1024
                                made.</para>
1345
666
                </listitem>
1025
                        </listitem>
1346
667
                <listitem>
1026
                        <listitem>
1347
668
                    <para>Lastly, make a file system on the partition and mount it.</para><literallayout class="monospaced">mkfs.ext3 /dev/vdb1
1027
                            <para>Press <code>'83'</code> change your new partition to 83, i.e.
1348
1028
                                Linux partition type.</para>
1349
1029
                        </listitem>
1350
1030
                        <listitem>
1351
1031
                            <para>Press ‘<code>p'</code> to display the hard disk partition setup.
1352
1032
                                Please take note that the first partition is denoted as /dev/vda1 in
1353
1033
                                your instance.</para>
1354
1034
                        </listitem>
1355
1035
1356
1036
                        <listitem>
1357
1037
                            <para>Press <code>'w'</code> to write the partition table and exit fdisk
1358
1038
                                upon completion.</para>
1359
1039
                        </listitem>
1360
1040
                        <listitem>
1361
1041
                            <para>Lastly, make a file system on the partition and mount it.
1362
1042
                                <programlisting>mkfs.ext3 /dev/vdb1
1363
669
mkdir /extraspace
1043
mkdir /extraspace
1370
670
mount /dev/vdb1 /extraspace</literallayout>
1044
mount /dev/vdb1 /extraspace </programlisting></para>
1371
671
                </listitem></orderedlist>
1045
1372
672
        <para>Your new volume has now been successfully mounted, and is ready for use! The ‘euca’
1046
                        </listitem>
1373
673
                commands are pretty self-explanatory, so play around with them and create new
1047
                    </orderedlist>
1374
674
                volumes, tear them down, attach and reattach, and so on.  </para>
1048
                    <para>Your new volume has now been successfully mounted, and is ready for use!
1375
675
    </simplesect></section>        
1049
                        The ‘euca’ commands are pretty self-explanatory, so play around with them
1376
1050
                        and create new volumes, tear them down, attach and reattach, and so on.
1377
1051
                    </para>
1378
1052
                </listitem>
1379
1053
            </itemizedlist>
1380
1054
        </simplesect>
1381
1055
        <simplesect>
1382
1056
            <title>C- Troubleshoot your nova-volumes installation</title>
1383
1057
            <para>If the volume attachement doesn't work, you should be able to perform different
1384
1058
                checks in order to see where the issue is. The nova-volumes.log and nova-compute.log
1385
1059
                will help you to diagnosis the errors you could encounter : </para>
1386
1060
            <para><emphasis role="bold">nova-compute.log / nova-volumes.log</emphasis></para>
1387
1061
            <para>
1388
1062
                <itemizedlist>
1389
1063
                    <listitem>
1390
1064
                        <para><emphasis role="italic">ERROR "15- already exists"</emphasis>
1391
1065
                            <programlisting>"ProcessExecutionError: Unexpected error while running command.\nCommand: sudo iscsiadm -m node -T iqn.2010-10.org.openstack:volume-00000001 -p
1392
1066
10.192.12.34:3260 --login\nExit code: 255\nStdout: 'Logging in to [iface: default, target: iqn.2010-10.org.openstack:volume-00000001, portal:
1393
1067
10.192.12.34,3260]\\n'\nStderr: 'iscsiadm: Could not login to [iface: default, target: iqn.2010-10.org.openstack:volume-00000001,
1394
1068
portal:10.192.12.34,3260]: openiscsiadm: initiator reported error (15 - already exists)\\n'\n"] </programlisting></para>
1395
1069
                        <para> This errors happens sometimes when you run an euca-dettach-volume and
1396
1070
                            euca-attach-volume and/ or try to attach another volume to an instance.
1397
1071
                            It happens when the compute node has a running session while you try to
1398
1072
                            attach a volume by using the same IQN. You could check that by running : </para>
1399
1073
                        <para><literallayout class="monospaced"><code>iscsiadm -m session</code></literallayout>
1400
1074
                            You should have a session with the same name that the compute is trying
1401
1075
                            to open. Actually, it seems to be related to the several routes
1402
1076
                            available for the iscsi exposition, those routes could be seen by
1403
1077
                            running on the compute node :
1404
1078
                            <literallayout class="monospaced"><code>iscsiadm -m discovery -t st -p $ip_of_nova-volumes</code></literallayout>
1405
1079
                            You should see for a volume multiple addresses to reach it. The only
1406
1080
                            known workaround to that is tha change the "–iscsi_ip_prefix" flag and
1407
1081
                            use the 4 bytes (full IP) of the nova-volumes server, eg : </para>
1408
1082
                        <para><literallayout class="monospaced"><code>"–iscsi_ip_prefix=192.168.2.1</code></literallayout>
1409
1083
                            You'll have then to restart both nova-compute and nova-volumes services. </para>
1410
1084
                        <para/>
1411
1085
                    </listitem>
1412
1086
                    <listitem>
1413
1087
                        <para><emphasis role="italic">ERROR "Cannot resolve host"</emphasis>
1414
1088
                            <programlisting>(nova.root): TRACE: ProcessExecutionError: Unexpected error while running command.
1415
1089
(nova.root): TRACE: Command: sudo iscsiadm -m discovery -t sendtargets -p ubuntu03c
1416
1090
(nova.root): TRACE: Exit code: 255
1417
1091
(nova.root): TRACE: Stdout: ''
1418
1092
(nova.root): TRACE: Stderr: 'iscsiadm: Cannot resolve host ubuntu03c. getaddrinfo error: [Name or service not known]\n\niscsiadm: 
1419
1093
cannot resolve host name ubuntu03c\niscsiadm: Could not perform SendTargets discovery.\n'
1420
1094
(nova.root): TRACE:</programlisting>
1421
1095
                            This erros happens when the compute node is unable to resolve the
1422
1096
                            nova-volume server name. You could either add a record for the server if
1423
1097
                            you have a DNS server; or add it into the "/etc/hosts" file of the
1424
1098
                            nova-compute. </para>
1425
1099
                        <para/>
1426
1100
                    </listitem>
1427
1101
                    <listitem>
1428
1102
                        <para><emphasis role="italic">ERROR "No route to host"</emphasis>
1429
1103
                            <programlisting>iscsiadm: cannot make connection to 172.29.200.37: No route to host\niscsiadm: cannot make connection to 172.29.200.37</programlisting>
1430
1104
                            This error could be caused by several things, but<emphasis role="bold">
1431
1105
                                it means only one thing : openiscsi is unable to establish a
1432
1106
                                communication with your nova-volumes server</emphasis>.</para>
1433
1107
                        <para>The first thing you could do is running a telnet session in order to
1434
1108
                            see if you are able to reach the nova-volumes server. From the
1435
1109
                            compute-node, run :</para>
1436
1110
                        <literallayout class="monospaced"><code>telnet $ip_of_nova_volumes  3260</code></literallayout>
1437
1111
                        <para> If the session times out, check the server firewall ; or try to ping
1438
1112
                            it. You could also run a tcpdump session which will likely gives you
1439
1113
                            extra information : </para>
1440
1114
                        <literallayout class="monospaced"><code>tcpdump -nvv -i $iscsi_interface port dest $ip_of_nova_volumes</code></literallayout>
1441
1115
                        <para> Again, try to manually run an iscsi discovery via : </para>
1442
1116
                        <literallayout class="monospaced"><code>iscsiadm -m discovery -t st -p $ip_of_nova-volumes</code></literallayout>
1443
1117
                        <para/>
1444
1118
                    </listitem>
1445
1119
                    <listitem>
1446
1120
                        <para><emphasis role="italic">"I lost connectivity between nova-volumes and
1447
1121
                                node-compute ; how to restore a clean state ?"</emphasis>
1448
1122
                        </para>
1449
1123
                        <para>Network disconnection can happens, from an "iscsi view", loosing
1450
1124
                            connectivity could be seen as a physical removal of a server's disk. If
1451
1125
                            the instance runs a volume while you loose the network between them, you
1452
1126
                            won't be able to detach the volume. You would encounter several errors.
1453
1127
                            Here is how you could clean this : </para>
1454
1128
                        <para>First, from the nova-compute, close the active (but stalled) iscsi
1455
1129
                            session, reffer to the volume attached to get the session, and perform
1456
1130
                            the following command : </para>
1457
1131
                        <literallayout class="monospaced"><code>iscsiadm -m session -r $session_id -u</code></literallayout>
1458
1132
                        <para>Here is an <code>iscsi -m session</code> output : </para>
1459
1133
                        <programlisting>
1460
1134
tcp: [1] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-0000000e
1461
1135
tcp: [2] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000010
1462
1136
tcp: [3] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000011
1463
1137
tcp: [4] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-0000000a
1464
1138
tcp: [5] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000012
1465
1139
tcp: [6] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000007
1466
1140
tcp: [7] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000009
1467
1141
tcp: [9] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000014                        </programlisting>
1468
1142
                        <para>I would close the session number 9 if I want to free the volume
1469
1143
                            00000014. </para>
1470
1144
                        <para>The cloud-controller is actually unaware about the iscsi session
1471
1145
                            closing, and will keeps the volume state as "in-use":
1472
1146
                            <programlisting>VOLUME  vol-00000014     30     nova    in-use (nuage-and-co, nova-cc1, i-0000009a[nova-cn1], \/dev\/sdb)   2011-07-18T12:45:39Z</programlisting>
1473
1147
                            You now have to inform it that the disk can be used. Nova stores the
1474
1148
                            volumes info into the "volumes" table. You will have to update four
1475
1149
                            fields into the database nova uses (eg. MySQL). First, conect to the
1476
1150
                            database : </para>
1477
1151
                        <literallayout class="monospaced"><code>mysql -uroot -p$password nova</code></literallayout>
1478
1152
                        <para>Then, we get some infos from the table "volumes" : </para>
1479
1153
                        <programlisting>
1480
1154
 mysql> select id,created_at, size, instance_id, status, attach_status, display_name from volumes;
1481
1155
+----+---------------------+------+-------------+----------------+---------------+--------------+
1482
1156
| id | created_at          | size | instance_id | status         | attach_status | display_name |
1483
1157
+----+---------------------+------+-------------+----------------+---------------+--------------+
1484
1158
|  1 | 2011-06-08 09:02:49 |    5 |           0 | available      | detached      | volume1      |
1485
1159
|  2 | 2011-06-08 14:04:36 |    5 |           0 | available      | detached      | NULL         |
1486
1160
|  3 | 2011-06-08 14:44:55 |    5 |           0 | available      | detached      | NULL         |
1487
1161
|  4 | 2011-06-09 09:09:15 |    5 |           0 | error_deleting | detached      | NULL         |
1488
1162
|  5 | 2011-06-10 08:46:33 |    6 |           0 | available      | detached      | NULL         |
1489
1163
|  6 | 2011-06-10 09:16:18 |    6 |           0 | available      | detached      | NULL         |
1490
1164
|  7 | 2011-06-16 07:45:57 |   10 |         157 | in-use         | attached      | NULL         |
1491
1165
|  8 | 2011-06-20 07:51:19 |   10 |           0 | available      | detached      | NULL         |
1492
1166
|  9 | 2011-06-21 08:21:38 |   10 |         152 | in-use         | attached      | NULL         |
1493
1167
| 10 | 2011-06-22 09:47:42 |   50 |         136 | in-use         | attached      | NULL         |
1494
1168
| 11 | 2011-06-30 07:30:48 |   50 |           0 | available      | detached      | NULL         |
1495
1169
| 12 | 2011-06-30 11:56:32 |   50 |           0 | available      | detached      | NULL         |
1496
1170
| 13 | 2011-06-30 12:12:08 |   50 |           0 | error_deleting | detached      | NULL         |
1497
1171
| 14 | 2011-07-04 12:33:50 |   30 |         155 | in-use         | attached      | NULL         |
1498
1172
| 15 | 2011-07-06 15:15:11 |    5 |           0 | error_deleting | detached      | NULL         |
1499
1173
| 16 | 2011-07-07 08:05:44 |   20 |         149 | in-use         | attached      | NULL         |
1500
1174
| 20 | 2011-08-30 13:28:24 |   20 |         158 | in-use         | attached      | NULL         |
1501
1175
| 17 | 2011-07-13 19:41:13 |   20 |         149 | in-use         | attached      | NULL         |
1502
1176
| 18 | 2011-07-18 12:45:39 |   30 |         154 | in-use         | attached      | NULL         |
1503
1177
| 19 | 2011-08-22 13:11:06 |   50 |           0 | available      | detached      | NULL         |
1504
1178
| 21 | 2011-08-30 15:39:16 |    5 |        NULL | error_deleting | detached      | NULL         |
1505
1179
+----+---------------------+------+-------------+----------------+---------------+--------------+
1506
1180
21 rows in set (0.00 sec)</programlisting>
1507
1181
                        <para> Once you get the volume id, you will have to run the following sql
1508
1182
                            queries (let's say, my volume 14 as the id number 21 : </para>
1509
1183
                        <programlisting>
1510
1184
            mysql> update volumes set mountpoint=NULL where id=21;
1511
1185
            mysql> update volumes set status="available" where status "error_deleting" where id=21;
1512
1186
            mysql> update volumes set attach_status="detached" where id=21;
1513
1187
            mysql> update volumes set instance_id=0 where id=21;
1514
1188
                        </programlisting>
1515
1189
                        <para>Now if you run again <code>euca-describe-volumes</code>from the cloud
1516
1190
                            coontroller, you should see an available volume now : </para>
1517
1191
                        <programlisting>VOLUME  vol-00000014     30     nova    available (nuage-and-co, nova-cc1, None, None)  2011-07-18T12:45:39Z</programlisting>
1518
1192
                        <para>You can now proceed to the volume attachement again!</para>
1519
1193
                    </listitem>
1520
1194
                </itemizedlist>
1521
1195
            </para>
1522
1196
        </simplesect>
1523
1197
        <simplesect>
1524
1198
            <title> D- Advanced tips : Disaster Recovery Process, Backup your nova-volumes, Browse
1525
1199
                your nova-volumes from the cloud-controller </title>
1526
1200
            <para>
1527
1201
            <emphasis role="italic">
1528
1202
                WORK IN PROGRESS
1529
1203
            </emphasis>
1530
1204
            </para>
1531
1205
            <para/>
1532
1206
        </simplesect>
1533
1207
    </section>
1534
676
    <section>
1208
    <section>
1535
677
        <?dbhtml filename="live-migration-usage.html" ?>
1209
        <?dbhtml filename="live-migration-usage.html" ?>
1536
678
        <title>Using Live Migration</title>
1210
        <title>Using Live Migration</title>
1537
@@ -680,74 +1212,80 @@
1538
680
        <para>Live migration provides a scheme to migrate running instances from one OpenStack
1212
        <para>Live migration provides a scheme to migrate running instances from one OpenStack
1539
681
            Compute server to another OpenStack Compute server. No visible downtime and no
1213
            Compute server to another OpenStack Compute server. No visible downtime and no
1540
682
            transaction loss is the ideal goal. This feature can be used as depicted below. </para>
1214
            transaction loss is the ideal goal. This feature can be used as depicted below. </para>
1542
683
        
1215
1543
684
        <itemizedlist>
1216
        <itemizedlist>
1544
685
            <listitem>
1217
            <listitem>
1545
686
                <para>First, make sure any instances running on a specific server.</para>
1218
                <para>First, make sure any instances running on a specific server.</para>
1546
687
                <programlisting><![CDATA[
1219
                <programlisting><![CDATA[
1547
688
# euca-describe-instances
1220
# euca-describe-instances
1548
689
Reservation:r-2raqmabo
1221
Reservation:r-2raqmabo
1553
690
RESERVATION   r-2raqmabo    admin   default
1222
RESERVATION r-2raqmabo admin default
1554
691
INSTANCE      i-00000003    ami-ubuntu-lucid      a.b.c.d  e.f.g.h      running     testkey (admin, HostB)  0             m1.small     2011-02-15 07:28:32   nova
1223
INSTANCE i-00000003 ami-ubuntu-lucid a.b.c.d e.f.g.h running testkey (admin, HostB) 0 m1.small 2011-02-15 07:28:32 nova
1555
692
                 ]]></programlisting>
1224
]]></programlisting>
1556
693
                 <para> In this example, i-00000003 is running on HostB.</para>
1225
                <para> In this example, i-00000003 is running on HostB.</para>
1557
694
            </listitem>
1226
            </listitem>
1558
695
            <listitem>
1227
            <listitem>
1559
696
                <para>Second, pick up other server where instances are migrated to.</para>
1228
                <para>Second, pick up other server where instances are migrated to.</para>
1560
697
                <programlisting><![CDATA[
1229
                <programlisting><![CDATA[
1561
698
# nova-manage service list
1230
# nova-manage service list
1569
699
HostA nova-scheduler enabled  :-) None
1231
HostA nova-scheduler enabled :-) None
1570
700
HostA nova-volume enabled  :-) None
1232
HostA nova-volume enabled :-) None
1571
701
HostA nova-network enabled  :-) None
1233
HostA nova-network enabled :-) None
1572
702
HostB nova-compute enabled  :-) None
1234
HostB nova-compute enabled :-) None
1573
703
HostC nova-compute enabled  :-) None
1235
HostC nova-compute enabled :-) None
1574
704
                 ]]></programlisting>
1236
]]></programlisting>
1575
705
                 <para> In this example, HostC can be picked up because nova-compute is running onto it.</para>
1237
                <para> In this example, HostC can be picked up because nova-compute is running onto
1576
1238
                    it.</para>
1577
706
            </listitem>
1239
            </listitem>
1578
707
            <listitem>
1240
            <listitem>
1579
708
                <para>Third, check HostC has enough resource for live migration.</para>
1241
                <para>Third, check HostC has enough resource for live migration.</para>
1580
709
                <programlisting><![CDATA[
1242
                <programlisting><![CDATA[
1581
710
# nova-manage service update_resource HostC
1243
# nova-manage service update_resource HostC
1582
711
# nova-manage service describe_resource HostC
1244
# nova-manage service describe_resource HostC
1588
712
HOST             PROJECT     cpu   mem(mb) disk(gb)
1245
HOST PROJECT cpu mem(mb) disk(gb)
1589
713
HostC(total)                  16     32232     878
1246
HostC(total) 16 32232 878
1590
714
HostC(used)                   13     21284     442
1247
HostC(used) 13 21284 442
1591
715
HostC            p1            5     10240     150
1248
HostC p1 5 10240 150
1592
716
HostC            p2            5     10240     150
1249
HostC p2 5 10240 150
1593
717
.....
1250
.....
1596
718
                 ]]></programlisting>
1251
]]></programlisting>
1597
719
                 <para>Remember to use update_resource first, then describe_resource. Otherwise,
1252
                <para>Remember to use update_resource first, then describe_resource. Otherwise,
1598
720
                    Host(used) is not updated.</para>
1253
                    Host(used) is not updated.</para>
1619
721
                 <itemizedlist>
1254
                <itemizedlist>
1620
722
                     <listitem>
1255
                    <listitem>
1621
723
                         <para><emphasis role="bold">cpu:</emphasis>the nuber of cpu</para>
1256
                        <para><emphasis role="bold">cpu:</emphasis>the nuber of cpu</para>
1622
724
                     </listitem>
1257
                    </listitem>
1623
725
                     <listitem>
1258
                    <listitem>
1624
726
                         <para><emphasis role="bold">mem(mb):</emphasis>total amount of memory (MB)</para>
1259
                        <para><emphasis role="bold">mem(mb):</emphasis>total amount of memory
1625
727
                     </listitem>
1260
                            (MB)</para>
1626
728
                     <listitem>
1261
                    </listitem>
1627
729
                         <para><emphasis role="bold">disk(gb)</emphasis>total amount of NOVA-INST-DIR/instances(GB)</para>
1262
                    <listitem>
1628
730
                     </listitem>
1263
                        <para><emphasis role="bold">disk(gb)</emphasis>total amount of
1629
731
                     <listitem>
1264
                            NOVA-INST-DIR/instances(GB)</para>
1630
732
                         <para><emphasis role="bold">1st line shows </emphasis>total amount of resource physical server has.</para>
1265
                    </listitem>
1631
733
                     </listitem>
1266
                    <listitem>
1632
734
                     <listitem>
1267
                        <para><emphasis role="bold">1st line shows </emphasis>total amount of
1633
735
                         <para><emphasis role="bold">2nd line shows </emphasis>current used resource.</para>
1268
                            resource physical server has.</para>
1634
736
                     </listitem>
1269
                    </listitem>
1635
737
                     <listitem>
1270
                    <listitem>
1636
738
                         <para><emphasis role="bold">3rd line and under</emphasis> is used resource per project.</para>
1271
                        <para><emphasis role="bold">2nd line shows </emphasis>current used
1637
739
                     </listitem>
1272
                            resource.</para>
1638
740
                 </itemizedlist>
1273
                    </listitem>
1639
1274
                    <listitem>
1640
1275
                        <para><emphasis role="bold">3rd line and under</emphasis> is used resource
1641
1276
                            per project.</para>
1642
1277
                    </listitem>
1643
1278
                </itemizedlist>
1644
741
            </listitem>
1279
            </listitem>
1645
742
            <listitem>
1280
            <listitem>
1646
743
                <para>Finally, live migration</para>
1281
                <para>Finally, live migration</para>
1647
744
                <programlisting><![CDATA[
1282
                <programlisting><![CDATA[
1648
745
# nova-manage vm live_migration i-00000003 HostC
1283
# nova-manage vm live_migration i-00000003 HostC
1649
746
Migration of i-00000001 initiated. Check its progress using euca-describe-instances.
1284
Migration of i-00000001 initiated. Check its progress using euca-describe-instances.
1654
747
                 ]]></programlisting>
1285
]]></programlisting>
1655
748
                 <para>Make sure instances are migrated successfully with euca-describe-instances.
1286
                <para>Make sure instances are migrated successfully with euca-describe-instances. If
1656
749
                    If instances are still running on HostB, check logfiles( src/dest nova-compute
1287
                    instances are still running on HostB, check logfiles( src/dest nova-compute and
1657
750
                    and nova-scheduler)</para>
1288
                    nova-scheduler)</para>
1658
751
            </listitem>
1289
            </listitem>
1659
752
        </itemizedlist>
1290
        </itemizedlist>
1660
753
1291
1661
@@ -756,12 +1294,12 @@
1662
756
    <section>
1294
    <section>
1663
757
        <?dbhtml filename="reference-for-flags-in-nova-conf.html" ?>
1295
        <?dbhtml filename="reference-for-flags-in-nova-conf.html" ?>
1664
758
        <title>Reference for Flags in nova.conf</title>
1296
        <title>Reference for Flags in nova.conf</title>
1669
759
                <para>For a complete list of all available flags for each OpenStack Compute service,
1297
        <para>For a complete list of all available flags for each OpenStack Compute service, run
1670
760
            run bin/nova-&lt;servicename> --help. </para>
1298
            bin/nova-&lt;servicename> --help. </para>
1671
761
            
1299
1672
762
                <table rules="all">
1300
        <table rules="all">
1673
763
            <caption>Description of common nova.conf flags (nova-api, nova-compute)</caption>
1301
            <caption>Description of common nova.conf flags (nova-api, nova-compute)</caption>
1675
764
          
1302
1676
765
            <thead>
1303
            <thead>
1677
766
                <tr>
1304
                <tr>
1678
767
                    <td>Flag</td>
1305
                    <td>Flag</td>
1679
@@ -901,17 +1439,22 @@
1680
901
                <tr>
1439
                <tr>
1681
902
                    <td>--flat_injected</td>
1440
                    <td>--flat_injected</td>
1682
903
                    <td>default: 'false'</td>
1441
                    <td>default: 'false'</td>
1684
904
                    <td>Indicates whether Compute (Nova) should use attempt to inject IPv6 network configuration information into the guest. It attempts to modify /etc/network/interfaces and currently only works on Debian-based systems.  </td>
1442
                    <td>Indicates whether Compute (Nova) should use attempt to inject IPv6 network
1685
1443
                        configuration information into the guest. It attempts to modify
1686
1444
                        /etc/network/interfaces and currently only works on Debian-based systems.
1687
1445
                    </td>
1688
905
                </tr>
1446
                </tr>
1689
906
                <tr>
1447
                <tr>
1690
907
                    <td>--fixed_ip_disassociate_timeout</td>
1448
                    <td>--fixed_ip_disassociate_timeout</td>
1691
908
                    <td>default: '600'</td>
1449
                    <td>default: '600'</td>
1693
909
                    <td>Integer: Number of seconds after which a deallocated ip is disassociated. </td>
1450
                    <td>Integer: Number of seconds after which a deallocated ip is disassociated.
1694
1451
                    </td>
1695
910
                </tr>
1452
                </tr>
1696
911
                <tr>
1453
                <tr>
1697
912
                    <td>--fixed_range</td>
1454
                    <td>--fixed_range</td>
1698
913
                    <td>default: '10.0.0.0/8'</td>
1455
                    <td>default: '10.0.0.0/8'</td>
1700
914
                    <td>Fixed IP address block of addresses from which a set of iptables rules is created</td>
1456
                    <td>Fixed IP address block of addresses from which a set of iptables rules is
1701
1457
                        created</td>
1702
915
                </tr>
1458
                </tr>
1703
916
                <tr>
1459
                <tr>
1704
917
                    <td>--fixed_range_v6</td>
1460
                    <td>--fixed_range_v6</td>
1705
@@ -921,7 +1464,8 @@
1706
921
                <tr>
1464
                <tr>
1707
922
                    <td>--[no]flat_injected</td>
1465
                    <td>--[no]flat_injected</td>
1708
923
                    <td>default: 'true'</td>
1466
                    <td>default: 'true'</td>
1710
924
                    <td>Indicates whether to attempt to inject network setup into guest; network injection only works for Debian systems</td>
1467
                    <td>Indicates whether to attempt to inject network setup into guest; network
1711
1468
                        injection only works for Debian systems</td>
1712
925
                </tr>
1469
                </tr>
1713
926
                <tr>
1470
                <tr>
1714
927
                    <td>--flat_interface</td>
1471
                    <td>--flat_interface</td>
1715
@@ -936,7 +1480,8 @@
1716
936
                <tr>
1480
                <tr>
1717
937
                    <td>--flat_network_dhcp_start</td>
1481
                    <td>--flat_network_dhcp_start</td>
1718
938
                    <td>default: '10.0.0.2'</td>
1482
                    <td>default: '10.0.0.2'</td>
1720
939
                    <td>Starting IP address for the DHCP server to start handing out IP addresses when using FlatDhcp </td>
1483
                    <td>Starting IP address for the DHCP server to start handing out IP addresses
1721
1484
                        when using FlatDhcp </td>
1722
940
                </tr>
1485
                </tr>
1723
941
                <tr>
1486
                <tr>
1724
942
                    <td>--flat_network_dns</td>
1487
                    <td>--flat_network_dns</td>
1725
@@ -948,7 +1493,7 @@
1726
948
                    <td>default: '4.4.4.0/24'</td>
1493
                    <td>default: '4.4.4.0/24'</td>
1727
949
                    <td>Floating IP address block </td>
1494
                    <td>Floating IP address block </td>
1728
950
                </tr>
1495
                </tr>
1730
951
              
1496
1731
952
                <tr>
1497
                <tr>
1732
953
                    <td>--[no]fake_network</td>
1498
                    <td>--[no]fake_network</td>
1733
954
                    <td>default: 'false'</td>
1499
                    <td>default: 'false'</td>
1734
@@ -996,15 +1541,17 @@
1735
996
                <tr>
1541
                <tr>
1736
997
                    <td>--image_service</td>
1542
                    <td>--image_service</td>
1737
998
                    <td>default: 'nova.image.s3.S3ImageService'</td>
1543
                    <td>default: 'nova.image.s3.S3ImageService'</td>
1740
999
                    <td><para>The service to use for retrieving and searching for images. Images must be registered using
1544
                    <td><para>The service to use for retrieving and searching for images. Images
1741
1000
                            euca2ools. Options: </para><itemizedlist>
1545
                            must be registered using euca2ools. Options: </para><itemizedlist>
1742
1001
                            <listitem>
1546
                            <listitem>
1743
1002
                                <para>nova.image.s3.S3ImageService</para>
1547
                                <para>nova.image.s3.S3ImageService</para>
1744
1003
                                <para>S3 backend for the Image Service.</para>
1548
                                <para>S3 backend for the Image Service.</para>
1745
1004
                            </listitem>
1549
                            </listitem>
1746
1005
                            <listitem>
1550
                            <listitem>
1747
1006
                                <para>nova.image.local.LocalImageService</para>
1551
                                <para>nova.image.local.LocalImageService</para>
1749
1007
                                <para>Image service storing images to local disk. It assumes that image_ids are integers.  This is the default setting if no image manager is defined here.</para>
1552
                                <para>Image service storing images to local disk. It assumes that
1750
1553
                                    image_ids are integers. This is the default setting if no image
1751
1554
                                    manager is defined here.</para>
1752
1008
                            </listitem>
1555
                            </listitem>
1753
1009
                            <listitem>
1556
                            <listitem>
1754
1010
                                <para>nova.image.glance.GlanceImageService</para>
1557
                                <para>nova.image.glance.GlanceImageService</para>
1755
@@ -1022,7 +1569,8 @@
1756
1022
                <tr>
1569
                <tr>
1757
1023
                    <td>--libvirt_type</td>
1570
                    <td>--libvirt_type</td>
1758
1024
                    <td>default: kvm</td>
1571
                    <td>default: kvm</td>
1760
1025
                    <td>String: Name of connection to a hypervisor through libvirt. Supported options are kvm, qemu, uml, and xen.</td>
1572
                    <td>String: Name of connection to a hypervisor through libvirt. Supported
1761
1573
                        options are kvm, qemu, uml, and xen.</td>
1762
1026
                </tr>
1574
                </tr>
1763
1027
                <tr>
1575
                <tr>
1764
1028
                    <td>--lock_path</td>
1576
                    <td>--lock_path</td>
1765
@@ -1195,7 +1743,8 @@
1766
1195
                <tr>
1743
                <tr>
1767
1196
                    <td>--routing_source_ip</td>
1744
                    <td>--routing_source_ip</td>
1768
1197
                    <td>default: '10'</td>
1745
                    <td>default: '10'</td>
1770
1198
                    <td>IP address; Public IP of network host. When instances without a floating IP hit the Internet, traffic is snatted to this IP address.</td>
1746
                    <td>IP address; Public IP of network host. When instances without a floating IP
1771
1747
                        hit the Internet, traffic is snatted to this IP address.</td>
1772
1199
                </tr>
1748
                </tr>
1773
1200
                <tr>
1749
                <tr>
1774
1201
                    <td>--s3_dmz</td>
1750
                    <td>--s3_dmz</td>
1775
@@ -1250,15 +1799,18 @@
1776
1250
                    <td>default: '/usr/lib/pymodules/python2.6/nova/../'</td>
1799
                    <td>default: '/usr/lib/pymodules/python2.6/nova/../'</td>
1777
1251
                    <td>Top-level directory for maintaining Nova's state</td>
1800
                    <td>Top-level directory for maintaining Nova's state</td>
1778
1252
                </tr>
1801
                </tr>
1786
1253
                <tr><td>--use_deprecated_auth</td>
1802
                <tr>
1787
1254
                    <td>default: 'false'</td>
1803
                    <td>--use_ipv6</td>
1788
1255
                    <td>Set to 1 or true to turn on; Determines whether to use the deprecated nova auth system or Keystone as the auth system </td></tr>
1804
                    <td>default: 'false'</td>
1789
1256
                <tr><td>--use_ipv6</td>
1805
                    <td>Set to 1 or true to turn on; Determines whether to use IPv6 network
1790
1257
                    <td>default: 'false'</td>
1806
                        addresses </td>
1791
1258
                    <td>Set to 1 or true to turn on; Determines whether to use IPv6 network addresses </td></tr>
1807
                </tr>
1792
1259
                <tr><td>--use_s3</td>
1808
                <tr>
1793
1809
                    <td>--use_s3</td>
1794
1260
                    <td>default: 'true'</td>
1810
                    <td>default: 'true'</td>
1796
1261
                    <td>Set to 1 or true to turn on; Determines whether to get images from s3 or use a local copy </td></tr>
1811
                    <td>Set to 1 or true to turn on; Determines whether to get images from s3 or use
1797
1812
                        a local copy </td>
1798
1813
                </tr>
1799
1262
                <tr>
1814
                <tr>
1800
1263
                    <td>--verbose</td>
1815
                    <td>--verbose</td>
1801
1264
                    <td>default: 'false'</td>
1816
                    <td>default: 'false'</td>
1802
@@ -1267,7 +1819,8 @@
1803
1267
                <tr>
1819
                <tr>
1804
1268
                    <td>--vlan_interface</td>
1820
                    <td>--vlan_interface</td>
1805
1269
                    <td>default: 'eth0'</td>
1821
                    <td>default: 'eth0'</td>
1807
1270
                    <td>This is the interface that VlanManager uses to bind bridges and vlans to. </td>
1822
                    <td>This is the interface that VlanManager uses to bind bridges and vlans to.
1808
1823
                    </td>
1809
1271
                </tr>
1824
                </tr>
1810
1272
                <tr>
1825
                <tr>
1811
1273
                    <td>--vlan_start</td>
1826
                    <td>--vlan_start</td>
1812
@@ -1282,39 +1835,47 @@
1813
1282
                <tr>
1835
                <tr>
1814
1283
                    <td>--vpn_key_suffix</td>
1836
                    <td>--vpn_key_suffix</td>
1815
1284
                    <td>default: '-vpn'</td>
1837
                    <td>default: '-vpn'</td>
1851
1285
                    <td>This is the interface that VlanManager uses to bind bridges and VLANs to.</td>
1838
                    <td>This is the interface that VlanManager uses to bind bridges and VLANs
1852
1286
                </tr>
1839
                        to.</td>
1853
1287
            </tbody>
1840
                </tr>
1854
1288
                </table>
1841
            </tbody>
1855
1289
                <table rules="all">
1842
        </table>
1856
1290
                    <caption>Description of nova.conf flags specific to nova-volume</caption>
1843
        <table rules="all">
1857
1291
                    
1844
            <caption>Description of nova.conf flags specific to nova-volume</caption>
1858
1292
                    <thead>
1845
1859
1293
                        <tr>
1846
            <thead>
1860
1294
                            <td>Flag</td>
1847
                <tr>
1861
1295
                            <td>Default</td>
1848
                    <td>Flag</td>
1862
1296
                            <td>Description</td>
1849
                    <td>Default</td>
1863
1297
                        </tr>
1850
                    <td>Description</td>
1864
1298
                    </thead>
1851
                </tr>
1865
1299
                    <tbody>
1852
            </thead>
1866
1300
                        <tr><td>--iscsi_ip_prefix</td>
1853
            <tbody>
1867
1301
                            <td>default: ''</td>
1854
                <tr>
1868
1302
                            
1855
                    <td>--iscsi_ip_prefix</td>
1869
1303
                            <td>IP address or partial IP address; Value that differentiates the IP
1856
                    <td>default: ''</td>
1870
1304
                                addresses using simple string matching, so if all of your hosts are on the 192.168.1.0/24 network you could use --iscsi_ip_prefix=192.168.1</td></tr>
1857
1871
1305
                        
1858
                    <td>IP address or partial IP address; Value that differentiates the IP addresses
1872
1306
                        <tr>
1859
                        using simple string matching, so if all of your hosts are on the
1873
1307
                            <td>--volume_manager</td>
1860
                        192.168.1.0/24 network you could use --iscsi_ip_prefix=192.168.1</td>
1874
1308
                            <td>default: 'nova.volume.manager.VolumeManager'</td>
1861
                </tr>
1875
1309
                            <td>String value; Manager to use for nova-volume</td>
1862
1876
1310
                        </tr>
1863
                <tr>
1877
1311
                        <tr>
1864
                    <td>--volume_manager</td>
1878
1312
                            <td>--volume_name_template</td>
1865
                    <td>default: 'nova.volume.manager.VolumeManager'</td>
1879
1313
                            <td>default: 'volume-%08x'</td>
1866
                    <td>String value; Manager to use for nova-volume</td>
1880
1314
                            <td>String value; Template string to be used to generate volume names</td>
1867
                </tr>
1881
1315
                        </tr><tr>
1868
                <tr>
1882
1316
                            <td>--volume_topic</td>
1869
                    <td>--volume_name_template</td>
1883
1317
                            <td>default: 'volume'</td>
1870
                    <td>default: 'volume-%08x'</td>
1884
1318
                            <td>String value; Name of the topic that volume nodes listen on</td>
1871
                    <td>String value; Template string to be used to generate volume names</td>
1885
1319
                        </tr></tbody></table></section>
1872
                </tr>
1886
1873
                <tr>
1887
1874
                    <td>--volume_topic</td>
1888
1875
                    <td>default: 'volume'</td>
1889
1876
                    <td>String value; Name of the topic that volume nodes listen on</td>
1890
1877
                </tr>
1891
1878
            </tbody>
1892
1879
        </table>
1893
1880
    </section>
1894
1320
</chapter>
1881
</chapter>
Reviewer	Review Type	Date Requested	Status
Anne Gentle		2011-09-07	Approve on 2011-09-07
Review via email: mp+74369@code.launchpad.net