Merge lp:~dsmythies/serverguide/lp1129649_plus into lp:~ubuntu-core-doc/serverguide/raring
- lp1129649_plus
- Merge into raring
Status: | Merged | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Approved by: | Doug Smythies | ||||||||||||
Approved revision: | 120 | ||||||||||||
Merged at revision: | 120 | ||||||||||||
Proposed branch: | lp:~dsmythies/serverguide/lp1129649_plus | ||||||||||||
Merge into: | lp:~ubuntu-core-doc/serverguide/raring | ||||||||||||
Diff against target: |
325 lines (+57/-55) 7 files modified
serverguide/C/dm-multipath.xml (+10/-10) serverguide/C/installation.xml (+9/-2) serverguide/C/lamp-applications.xml (+1/-1) serverguide/C/network-auth.xml (+13/-14) serverguide/C/network-config.xml (+1/-1) serverguide/C/security.xml (+1/-1) serverguide/C/virtualization.xml (+22/-26) |
||||||||||||
To merge this branch: | bzr merge lp:~dsmythies/serverguide/lp1129649_plus | ||||||||||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Doug Smythies | Approve | ||
Review via email: mp+156227@code.launchpad.net |
Commit message
Description of the change
This MP addresses:
LP: #1129649
LP: #1103870 (although not to the extent that was desired by the poster)
I thought maybe LP: #922251 , but some inforomation was just added to the bug report, so no.
Some odd strange garbage bytes in the .xml files were removed.
All non single byte UTF-8 characters in the .xml files were removed, and now this:
grep --color='auto' -P -n "[\x80-\xFF]" *.xml
doesn't find anything. Now the only multi byte UTF-8 characters in the master source files are two in ubuntu.xsl defining the double >> character used in the link trails, and such is consitent with other Ubuntu docs.
Some other minor edits.
I am looking for peer review for this merge proposal, but will not wait long for it, as time is running out.
Doug Smythies (dsmythies) wrote : | # |
Doug Smythies (dsmythies) wrote : | # |
I'm going ahead and merging this.
Preview Diff
1 | === modified file 'serverguide/C/dm-multipath.xml' | |||
2 | --- serverguide/C/dm-multipath.xml 2013-03-14 21:49:37 +0000 | |||
3 | +++ serverguide/C/dm-multipath.xml 2013-03-29 23:04:23 +0000 | |||
4 | @@ -173,8 +173,8 @@ | |||
5 | 173 | <sect2 id="multipath-dm-multipath-components"> | 173 | <sect2 id="multipath-dm-multipath-components"> |
6 | 174 | <title>&DMM; components</title> | 174 | <title>&DMM; components</title> |
7 | 175 | 175 | ||
10 | 176 | <para>Table <link linkend="multipath-components-table">“DM-Multipath | 176 | <para>Table <link linkend="multipath-components-table">DM-Multipath |
11 | 177 | Components”</link> describes the components of the DM-Multipath package.</para> | 177 | Components</link> describes the components of the DM-Multipath package.</para> |
12 | 178 | <xi:include href="multipath-components-table.xml" | 178 | <xi:include href="multipath-components-table.xml" |
13 | 179 | xmlns:xi="http://www.w3.org/2001/XInclude"/> | 179 | xmlns:xi="http://www.w3.org/2001/XInclude"/> |
14 | 180 | </sect2> | 180 | </sect2> |
15 | @@ -272,16 +272,16 @@ | |||
16 | 272 | defaults, including the <emphasis role="bold"><link | 272 | defaults, including the <emphasis role="bold"><link |
17 | 273 | linkend="attribute-user_friendly_names">user_friendly_names</link></emphasis> | 273 | linkend="attribute-user_friendly_names">user_friendly_names</link></emphasis> |
18 | 274 | configuration option, see Section , <link | 274 | configuration option, see Section , <link |
21 | 275 | linkend="multipath-config-defaults">“Configuration File | 275 | linkend="multipath-config-defaults">Configuration File |
22 | 276 | Defaults”</link>. You can also set the name of a multipath device to a | 276 | Defaults</link>. You can also set the name of a multipath device to a |
23 | 277 | name of your choosing by using the <emphasis role="bold"><link | 277 | name of your choosing by using the <emphasis role="bold"><link |
24 | 278 | linkend="attribute-alias">alias</link></emphasis> option in the | 278 | linkend="attribute-alias">alias</link></emphasis> option in the |
25 | 279 | <emphasis role="bold">multipaths</emphasis> section of the multipath | 279 | <emphasis role="bold">multipaths</emphasis> section of the multipath |
26 | 280 | configuration file. For information on the <emphasis | 280 | configuration file. For information on the <emphasis |
27 | 281 | role="bold">multipaths</emphasis> section of the multipath configuration | 281 | role="bold">multipaths</emphasis> section of the multipath configuration |
28 | 282 | file, see Section, <link | 282 | file, see Section, <link |
31 | 283 | linkend="multipath-config-multipath">“Multipaths Device Configuration | 283 | linkend="multipath-config-multipath">Multipaths Device Configuration |
32 | 284 | Attributes”</link>.</para> | 284 | Attributes</link>.</para> |
33 | 285 | </sect2> | 285 | </sect2> |
34 | 286 | 286 | ||
35 | 287 | <sect2 id="multipath-device-names-in-cluster"> | 287 | <sect2 id="multipath-device-names-in-cluster"> |
36 | @@ -518,8 +518,8 @@ | |||
37 | 518 | role="bold">/dev/sda</emphasis>, in the multipath map. For further | 518 | role="bold">/dev/sda</emphasis>, in the multipath map. For further |
38 | 519 | information on the <emphasis role="bold">multipath</emphasis> | 519 | information on the <emphasis role="bold">multipath</emphasis> |
39 | 520 | command output, see Section <link | 520 | command output, see Section <link |
42 | 521 | linkend="multipath-command-output">“Multipath Command | 521 | linkend="multipath-command-output">Multipath Command |
43 | 522 | Output”</link>.</para> | 522 | Output</link>.</para> |
44 | 523 | 523 | ||
45 | 524 | <screen> | 524 | <screen> |
46 | 525 | # multipath -v2 | 525 | # multipath -v2 |
47 | @@ -602,8 +602,8 @@ | |||
48 | 602 | <command>multipath -ll</command> command to display the current | 602 | <command>multipath -ll</command> command to display the current |
49 | 603 | multipath configuration. For information on the <command>multipath | 603 | multipath configuration. For information on the <command>multipath |
50 | 604 | -ll</command> command, see Section <link | 604 | -ll</command> command, see Section <link |
53 | 605 | linkend="multipath-queries-and-commands">“Multipath Queries with | 605 | linkend="multipath-queries-and-commands">Multipath Queries with |
54 | 606 | multipath Command”</link>. To check that the blacklisted device was | 606 | multipath Command</link>. To check that the blacklisted device was |
55 | 607 | not added back, you can run the multipath command, as in the | 607 | not added back, you can run the multipath command, as in the |
56 | 608 | following example. The multipath command defaults to a verbosity | 608 | following example. The multipath command defaults to a verbosity |
57 | 609 | level of <emphasis role="bold">v2</emphasis> if you do not specify a | 609 | level of <emphasis role="bold">v2</emphasis> if you do not specify a |
58 | 610 | 610 | ||
59 | === modified file 'serverguide/C/installation.xml' | |||
60 | --- serverguide/C/installation.xml 2012-10-10 11:20:12 +0000 | |||
61 | +++ serverguide/C/installation.xml 2013-03-29 23:04:23 +0000 | |||
62 | @@ -1,4 +1,4 @@ | |||
64 | 1 | <?xml version="1.0" encoding="UTF-8"?> | 1 | <?xml version="1.0" encoding="UTF-8"?> |
65 | 2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" | 2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" |
66 | 3 | "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ | 3 | "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ |
67 | 4 | <!ENTITY % globalent SYSTEM "../../libs/global.ent"> | 4 | <!ENTITY % globalent SYSTEM "../../libs/global.ent"> |
68 | @@ -53,13 +53,20 @@ | |||
69 | 53 | <row> | 53 | <row> |
70 | 54 | <entry><para>Server (Minimal)</para></entry> | 54 | <entry><para>Server (Minimal)</para></entry> |
71 | 55 | <entry><para>300 megahertz</para></entry> | 55 | <entry><para>300 megahertz</para></entry> |
73 | 56 | <entry><para>256 megabytes</para></entry> | 56 | <entry><para>128 megabytes</para></entry> |
74 | 57 | <entry><para>700 megabytes</para></entry> | 57 | <entry><para>700 megabytes</para></entry> |
75 | 58 | <entry><para>1.4 gigabytes</para></entry> | 58 | <entry><para>1.4 gigabytes</para></entry> |
76 | 59 | </row> | 59 | </row> |
77 | 60 | </tbody> | 60 | </tbody> |
78 | 61 | </tgroup> | 61 | </tgroup> |
79 | 62 | </table> | 62 | </table> |
80 | 63 | |||
81 | 64 | <note> | ||
82 | 65 | <para> | ||
83 | 66 | A virtual installation requires a minimum of 256 megabytes of RAM during the installation phase. | ||
84 | 67 | </para> | ||
85 | 68 | </note> | ||
86 | 69 | |||
87 | 63 | <para> | 70 | <para> |
88 | 64 | The Server Edition provides a common base for all sorts of server applications. | 71 | The Server Edition provides a common base for all sorts of server applications. |
89 | 65 | It is a minimalist design providing a platform for the desired services, such | 72 | It is a minimalist design providing a platform for the desired services, such |
90 | 66 | 73 | ||
91 | === modified file 'serverguide/C/lamp-applications.xml' | |||
92 | --- serverguide/C/lamp-applications.xml 2013-03-05 01:04:42 +0000 | |||
93 | +++ serverguide/C/lamp-applications.xml 2013-03-29 23:04:23 +0000 | |||
94 | @@ -381,7 +381,7 @@ | |||
95 | 381 | </listitem> | 381 | </listitem> |
96 | 382 | <listitem> | 382 | <listitem> |
97 | 383 | <para> | 383 | <para> |
99 | 384 | The <ulink url="http://www.packtpub.com/Mediawiki/book">MediaWiki Administrators’ Tutorial Guide</ulink> | 384 | The <ulink url="http://www.packtpub.com/Mediawiki/book">MediaWiki Administrators' Tutorial Guide</ulink> |
100 | 385 | contains a wealth of information for new MediaWiki administrators. | 385 | contains a wealth of information for new MediaWiki administrators. |
101 | 386 | </para> | 386 | </para> |
102 | 387 | </listitem> | 387 | </listitem> |
103 | 388 | 388 | ||
104 | === modified file 'serverguide/C/network-auth.xml' | |||
105 | --- serverguide/C/network-auth.xml 2013-03-18 23:44:19 +0000 | |||
106 | +++ serverguide/C/network-auth.xml 2013-03-29 23:04:23 +0000 | |||
107 | @@ -200,20 +200,19 @@ | |||
108 | 200 | <screen> | 200 | <screen> |
109 | 201 | <computeroutput> | 201 | <computeroutput> |
110 | 202 | /etc/ldap/slapd.d/ | 202 | /etc/ldap/slapd.d/ |
125 | 203 | 203 | /etc/ldap/slapd.d/cn=config | |
126 | 204 | ├── cn=config | 204 | /etc/ldap/slapd.d/cn=config/cn=module{0}.ldif |
127 | 205 | │ ├── cn=module{0}.ldif | 205 | /etc/ldap/slapd.d/cn=config/cn=schema |
128 | 206 | │ ├── cn=schema | 206 | /etc/ldap/slapd.d/cn=config/cn=schema/cn={0}core.ldif |
129 | 207 | │ │ ├── cn={0}core.ldif | 207 | /etc/ldap/slapd.d/cn=config/cn=schema/cn={1}cosine.ldif |
130 | 208 | │ │ ├── cn={1}cosine.ldif | 208 | /etc/ldap/slapd.d/cn=config/cn=schema/cn={2}nis.ldif |
131 | 209 | │ │ ├── cn={2}nis.ldif | 209 | /etc/ldap/slapd.d/cn=config/cn=schema/cn={3}inetorgperson.ldif |
132 | 210 | │ │ └── cn={3}inetorgperson.ldif | 210 | /etc/ldap/slapd.d/cn=config/cn=schema.ldif |
133 | 211 | │ ├── cn=schema.ldif | 211 | /etc/ldap/slapd.d/cn=config/olcBackend={0}hdb.ldif |
134 | 212 | │ ├── olcBackend={0}hdb.ldif | 212 | /etc/ldap/slapd.d/cn=config/olcDatabase={0}config.ldif |
135 | 213 | │ ├── olcDatabase={0}config.ldif | 213 | /etc/ldap/slapd.d/cn=config/olcDatabase={-1}frontend.ldif |
136 | 214 | │ ├── olcDatabase={-1}frontend.ldif | 214 | /etc/ldap/slapd.d/cn=config/olcDatabase={1}hdb.ldif |
137 | 215 | │ └── olcDatabase={1}hdb.ldif | 215 | /etc/ldap/slapd.d/cn=config.ldif |
124 | 216 | └── cn=config.ldif | ||
138 | 217 | </computeroutput> | 216 | </computeroutput> |
139 | 218 | </screen> | 217 | </screen> |
140 | 219 | 218 | ||
141 | 220 | 219 | ||
142 | === modified file 'serverguide/C/network-config.xml' | |||
143 | --- serverguide/C/network-config.xml 2012-08-20 08:09:16 +0000 | |||
144 | +++ serverguide/C/network-config.xml 2013-03-29 23:04:23 +0000 | |||
145 | @@ -959,7 +959,7 @@ | |||
146 | 959 | </varlistentry> | 959 | </varlistentry> |
147 | 960 | </variablelist> | 960 | </variablelist> |
148 | 961 | <para> | 961 | <para> |
150 | 962 | The last two methods can be considered “automatic” because in each case the DHCP server | 962 | The last two methods can be considered "automatic" because in each case the DHCP server |
151 | 963 | assigns an address with no extra intervention needed. The only difference between them | 963 | assigns an address with no extra intervention needed. The only difference between them |
152 | 964 | is in how long the IP address is leased, in other words whether a client's address varies | 964 | is in how long the IP address is leased, in other words whether a client's address varies |
153 | 965 | over time. | 965 | over time. |
154 | 966 | 966 | ||
155 | === modified file 'serverguide/C/security.xml' | |||
156 | --- serverguide/C/security.xml 2012-09-20 15:06:36 +0000 | |||
157 | +++ serverguide/C/security.xml 2013-03-29 23:04:23 +0000 | |||
158 | @@ -1644,7 +1644,7 @@ | |||
159 | 1644 | <title>eCryptfs</title> | 1644 | <title>eCryptfs</title> |
160 | 1645 | 1645 | ||
161 | 1646 | <para> | 1646 | <para> |
163 | 1647 | <emphasis>eCryptfs</emphasis> is a POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux. Layering on | 1647 | <emphasis>eCryptfs</emphasis> is a POSIX-compliant enterprise-class stacked cryptographic filesystem for Linux. Layering on |
164 | 1648 | top of the filesystem layer <emphasis>eCryptfs</emphasis> protects files no matter the underlying filesystem, partition | 1648 | top of the filesystem layer <emphasis>eCryptfs</emphasis> protects files no matter the underlying filesystem, partition |
165 | 1649 | type, etc. | 1649 | type, etc. |
166 | 1650 | </para> | 1650 | </para> |
167 | 1651 | 1651 | ||
168 | === modified file 'serverguide/C/virtualization.xml' | |||
169 | --- serverguide/C/virtualization.xml 2013-03-23 22:09:27 +0000 | |||
170 | +++ serverguide/C/virtualization.xml 2013-03-29 23:04:23 +0000 | |||
171 | @@ -38,7 +38,7 @@ | |||
172 | 38 | </para> | 38 | </para> |
173 | 39 | <note> | 39 | <note> |
174 | 40 | <para> | 40 | <para> |
176 | 41 | On most computer whose processor supports virtualization, it is | 41 | On many computers with processors supporting hardware assisted virtualization, it is |
177 | 42 | necessary to activate an option in the BIOS to enable it. | 42 | necessary to activate an option in the BIOS to enable it. |
178 | 43 | </para> | 43 | </para> |
179 | 44 | </note> | 44 | </note> |
180 | @@ -46,13 +46,14 @@ | |||
181 | 46 | <title>Virtual Networking</title> | 46 | <title>Virtual Networking</title> |
182 | 47 | 47 | ||
183 | 48 | <para> | 48 | <para> |
186 | 49 | There are a few different ways to allow a virtual machine access to the external network. The default virtual network configuration is | 49 | There are a few different ways to allow a virtual machine access to the external network. The default virtual network configuration includes |
187 | 50 | <emphasis>usermode</emphasis> networking, which uses the SLIRP protocol and traffic is NATed through the host interface to the outside network. | 50 | <emphasis>bridging</emphasis> and <emphasis>iptables</emphasis> rules implementing <emphasis>usermode</emphasis> networking, which uses the |
188 | 51 | SLIRP protocol. Traffic is NATed through the host interface to the outside network. | ||
189 | 51 | </para> | 52 | </para> |
190 | 52 | 53 | ||
191 | 53 | <para> | 54 | <para> |
194 | 54 | To enable external hosts to directly access services on virtual machines a <emphasis>bridge</emphasis> needs to be configured. This allows | 55 | To enable external hosts to directly access services on virtual machines a different type of <emphasis>bridge</emphasis> than the default needs |
195 | 55 | the virtual interfaces to connect to the outside network through the physical interface, making them appear as normal hosts to the rest | 56 | to be configured. This allows the virtual interfaces to connect to the outside network through the physical interface, making them appear as normal hosts to the rest |
196 | 56 | of the network. For information on setting up a bridge see <xref linkend="bridging"/>. | 57 | of the network. For information on setting up a bridge see <xref linkend="bridging"/>. |
197 | 57 | </para> | 58 | </para> |
198 | 58 | 59 | ||
199 | @@ -63,7 +64,7 @@ | |||
200 | 63 | To install the necessary packages, from a terminal prompt enter: | 64 | To install the necessary packages, from a terminal prompt enter: |
201 | 64 | </para> | 65 | </para> |
202 | 65 | <screen> | 66 | <screen> |
204 | 66 | <command>sudo apt-get install kvm libvirt-bin</command> | 67 | <command>sudo apt-get install qemu-kvm libvirt-bin</command> |
205 | 67 | </screen> | 68 | </screen> |
206 | 68 | <para> | 69 | <para> |
207 | 69 | After installing <application>libvirt-bin</application>, the user used to manage virtual machines will need to be added to | 70 | After installing <application>libvirt-bin</application>, the user used to manage virtual machines will need to be added to |
208 | @@ -116,8 +117,8 @@ | |||
209 | 116 | <screen> | 117 | <screen> |
210 | 117 | <command>sudo virt-install -n web_devel -r 256 \ | 118 | <command>sudo virt-install -n web_devel -r 256 \ |
211 | 118 | --disk path=/var/lib/libvirt/images/web_devel.img,bus=virtio,size=4 -c \ | 119 | --disk path=/var/lib/libvirt/images/web_devel.img,bus=virtio,size=4 -c \ |
214 | 119 | jeos.iso --accelerate --network network=default,model=virtio \ | 120 | jeos.iso --network network=default,model=virtio \ |
215 | 120 | --connect=qemu:///system --vnc --noautoconsole -v</command> | 121 | --graphics vnc,listen=0.0.0.0 --noautoconsole -v</command> |
216 | 121 | </screen> | 122 | </screen> |
217 | 122 | <itemizedlist> | 123 | <itemizedlist> |
218 | 123 | <listitem> | 124 | <listitem> |
219 | @@ -145,18 +146,14 @@ | |||
220 | 145 | </listitem> | 146 | </listitem> |
221 | 146 | <listitem> | 147 | <listitem> |
222 | 147 | <para> | 148 | <para> |
223 | 148 | <emphasis>--accelerate:</emphasis> enables the kernel's acceleration technologies. | ||
224 | 149 | </para> | ||
225 | 150 | </listitem> | ||
226 | 151 | <listitem> | ||
227 | 152 | <para> | ||
228 | 153 | <emphasis>--network</emphasis> provides details related to the VM's network interface. Here the <emphasis>default</emphasis> | 149 | <emphasis>--network</emphasis> provides details related to the VM's network interface. Here the <emphasis>default</emphasis> |
229 | 154 | network is used, and the interface model is configured for <emphasis>virtio</emphasis>. | 150 | network is used, and the interface model is configured for <emphasis>virtio</emphasis>. |
230 | 155 | </para> | 151 | </para> |
231 | 156 | </listitem> | 152 | </listitem> |
232 | 157 | <listitem> | 153 | <listitem> |
233 | 158 | <para> | 154 | <para> |
235 | 159 | <emphasis>--vnc:</emphasis> exports the guest's virtual console using VNC. | 155 | <emphasis>--graphics vnc,listen=0.0.0.0:</emphasis> exports the guest's virtual console using VNC and on all host interfaces. |
236 | 156 | Typically servers have no GUI, so another GUI based computer on the Local Area Network (LAN) can connect via VNC to complete the installation. | ||
237 | 160 | </para> | 157 | </para> |
238 | 161 | </listitem> | 158 | </listitem> |
239 | 162 | <listitem> | 159 | <listitem> |
240 | @@ -172,7 +169,7 @@ | |||
241 | 172 | </itemizedlist> | 169 | </itemizedlist> |
242 | 173 | <para> | 170 | <para> |
243 | 174 | After launching <application>virt-install</application> you can connect to the virtual machine's console either locally | 171 | After launching <application>virt-install</application> you can connect to the virtual machine's console either locally |
245 | 175 | using a GUI or with the <application>virt-viewer</application> utility. | 172 | using a GUI (if your server has a GUI), or via a remote VNC client from a GUI based computer. |
246 | 176 | </para> | 173 | </para> |
247 | 177 | </sect2> | 174 | </sect2> |
248 | 178 | <sect2 id="libvirt-virt-clone" status="review"> | 175 | <sect2 id="libvirt-virt-clone" status="review"> |
249 | @@ -730,7 +727,7 @@ | |||
250 | 730 | line of the partition file should specify (root first): | 727 | line of the partition file should specify (root first): |
251 | 731 | mountpoint size | 728 | mountpoint size |
252 | 732 | where size is in megabytes. You can have up to 4 virtual disks, a new disk starts | 729 | where size is in megabytes. You can have up to 4 virtual disks, a new disk starts |
254 | 733 | on a line with ’---’. ie : | 730 | on a line with '---'. ie : |
255 | 734 | root 1000 | 731 | root 1000 |
256 | 735 | /opt 1000 | 732 | /opt 1000 |
257 | 736 | swap 256 | 733 | swap 256 |
258 | @@ -939,7 +936,7 @@ | |||
259 | 939 | <para> | 936 | <para> |
260 | 940 | By default, <application>apt-mirror</application> uses the configuration file in <filename>/etc/apt/mirror.list</filename>. | 937 | By default, <application>apt-mirror</application> uses the configuration file in <filename>/etc/apt/mirror.list</filename>. |
261 | 941 | As it is set up, it will replicate only the architecture of the local machine. If you would like to support other | 938 | As it is set up, it will replicate only the architecture of the local machine. If you would like to support other |
263 | 942 | architectures on your mirror, simply duplicate the lines starting with “deb”, replacing the deb keyword by /deb-{arch} | 939 | architectures on your mirror, simply duplicate the lines starting with "deb", replacing the deb keyword by /deb-{arch} |
264 | 943 | where arch can be i386, amd64, etc... For example, on an amd64 machine, to have the i386 archives as well, you will have | 940 | where arch can be i386, amd64, etc... For example, on an amd64 machine, to have the i386 archives as well, you will have |
265 | 944 | (some lines have been split to fit the format of this document): | 941 | (some lines have been split to fit the format of this document): |
266 | 945 | </para> | 942 | </para> |
267 | @@ -1115,7 +1112,7 @@ | |||
268 | 1115 | <sect2 id="ubuntu-cloud-prerequisites" status="review"> | 1112 | <sect2 id="ubuntu-cloud-prerequisites" status="review"> |
269 | 1116 | <title>Prerequisites</title> | 1113 | <title>Prerequisites</title> |
270 | 1117 | <para> | 1114 | <para> |
272 | 1118 | To deploy a minimal Ubuntu Cloud infrastructure, you’ll need at least: | 1115 | To deploy a minimal Ubuntu Cloud infrastructure, you'll need at least: |
273 | 1119 | </para> | 1116 | </para> |
274 | 1120 | 1117 | ||
275 | 1121 | <itemizedlist> | 1118 | <itemizedlist> |
276 | @@ -1153,8 +1150,8 @@ | |||
277 | 1153 | time server (ntp). This will assure that we have instantiated machines and hosts in sync. | 1150 | time server (ntp). This will assure that we have instantiated machines and hosts in sync. |
278 | 1154 | </para> | 1151 | </para> |
279 | 1155 | <para> | 1152 | <para> |
282 | 1156 | In this example the “private network” will be in the 10.0.0.0/24 range on eth1. All the internal communication between instances will happen | 1153 | In this example the "private network" will be in the 10.0.0.0/24 range on eth1. All the internal communication between instances will happen |
283 | 1157 | there while the “public network” will be in the 10.153.107.0/29 range on eth0. | 1154 | there while the "public network" will be in the 10.153.107.0/29 range on eth0. |
284 | 1158 | </para> | 1155 | </para> |
285 | 1159 | 1156 | ||
286 | 1160 | <sect3 id="ubuntu-cloud-config-bridge" status="review"> | 1157 | <sect3 id="ubuntu-cloud-config-bridge" status="review"> |
287 | @@ -1225,7 +1222,7 @@ | |||
288 | 1225 | <command>sudo service libvirt-bin restart</command> | 1222 | <command>sudo service libvirt-bin restart</command> |
289 | 1226 | </screen> | 1223 | </screen> |
290 | 1227 | <para> | 1224 | <para> |
292 | 1228 | Install RabbitMQ – Advanced Message Queuing Protocol (AMQP) | 1225 | Install RabbitMQ - Advanced Message Queuing Protocol (AMQP) |
293 | 1229 | </para> | 1226 | </para> |
294 | 1230 | <screen> | 1227 | <screen> |
295 | 1231 | <command>sudo apt-get install rabbitmq-server</command> | 1228 | <command>sudo apt-get install rabbitmq-server</command> |
296 | @@ -1293,7 +1290,7 @@ | |||
297 | 1293 | <command>sudo nova-manage service list</command> | 1290 | <command>sudo nova-manage service list</command> |
298 | 1294 | <command>sudo nova-manage version list</command> | 1291 | <command>sudo nova-manage version list</command> |
299 | 1295 | </screen> | 1292 | </screen> |
301 | 1296 | <para>If nova services don’t show up correctly restart OpenStack services as described previously. For more information please | 1293 | <para>If nova services don't show up correctly restart OpenStack services as described previously. For more information please |
302 | 1297 | refer to the troubleshooting section on this guide.</para> | 1294 | refer to the troubleshooting section on this guide.</para> |
303 | 1298 | 1295 | ||
304 | 1299 | </sect2> | 1296 | </sect2> |
305 | @@ -1353,9 +1350,8 @@ | |||
306 | 1353 | 1350 | ||
307 | 1354 | <para>Download, register and publish an Ubuntu cloud image</para> | 1351 | <para>Download, register and publish an Ubuntu cloud image</para> |
308 | 1355 | <screen> | 1352 | <screen> |
312 | 1356 | <command>distro=lucid</command> | 1353 | <command>wget http://cloud-images.ubuntu.com/&distro-short-codename;/current/&distro-short-codename;-server-cloudimg-amd64.tar.gz</command> |
313 | 1357 | <command>wget http://cloud-images.ubuntu.com/$distro/current/$distro-server-cloudimg-amd64.tar.gz</command> | 1354 | <command>cloud-publish-tarball &distro-short-codename;-server-cloudimg-amd64.tar.gz &distro-short-codename;_amd64</command> |
311 | 1358 | <command>cloud-publish-tarball "$distro"-server-cloudimg-amd64.tar.gz "$distro"_amd64</command> | ||
314 | 1359 | </screen> | 1355 | </screen> |
315 | 1360 | <para>Create a key pair and start an instance</para> | 1356 | <para>Create a key pair and start an instance</para> |
316 | 1361 | <screen> | 1357 | <screen> |
317 | @@ -1509,7 +1505,7 @@ | |||
318 | 1509 | </listitem> | 1505 | </listitem> |
319 | 1510 | <listitem> | 1506 | <listitem> |
320 | 1511 | <para> | 1507 | <para> |
322 | 1512 | <emphasis>IaaS</emphasis> - Infrastructure as a Service — Cloud infrastructure services, whereby a virtualized | 1508 | <emphasis>IaaS</emphasis> - Infrastructure as a Service -- Cloud infrastructure services, whereby a virtualized |
323 | 1513 | environment is delivered as a service over the Internet by the provider. The infrastructure can include servers, | 1509 | environment is delivered as a service over the Internet by the provider. The infrastructure can include servers, |
324 | 1514 | network equipment, and software. | 1510 | network equipment, and software. |
325 | 1515 | </para> | 1511 | </para> |
I forgot:
Also a slight change related to LP: #1050595
And several of the multibyte UTF-8 characters in dm-multipath.xml were for quotes characters that were not needed anyhow as both the PDF and the HTML differentiate the text anyhow, so I took them out.
Note: the colored diff used herein might make some line changes difficult to see. The non-colored "bzr diff" display gets really confused by multi-byte UTF-8 characters.