Merge lp:~kim0/serverguide/serverguide-review-ch19 into lp:~ubuntu-core-doc/serverguide/oneiric
- serverguide-review-ch19
- Merge into oneiric
Proposed by
Ahmed Kamal
| Status: | Rejected |
|---|---|
| Rejected by: | Doug Smythies |
| Proposed branch: | lp:~kim0/serverguide/serverguide-review-ch19 |
| Merge into: | lp:~ubuntu-core-doc/serverguide/oneiric |
| Diff against target: |
1212 lines (+13/-1152) 2 files modified
serverguide/C/installation.xml (+0/-5) serverguide/C/virtualization.xml (+13/-1147) |
| To merge this branch: | bzr merge lp:~kim0/serverguide/serverguide-review-ch19 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Scott Kitterman | Needs Information | ||
| Ubuntu Documentation Committers | Pending | ||
|
Review via email:
|
|||
Commit message
Description of the change
Changelog:
package kvm is now called qemu-kvm
Updating KVM homepage URL
Deleting all UEC information, UEC is obsolete, new Ubuntu Cloud product is based on OpenStack not Eucalyptus. The new OpenStack based Ubuntu Cloud will get its own chapter
To post a comment you must log in.
- 11. By Ahmed Kamal
-
Removing references to UEC from installation chapter, the validator script is happy now
Revision history for this message
| Ahmed Kamal (kim0) wrote : | # |
UEC as a product no longer exists, only the upstream eucalyptus project exists in universe. The docs were targeting UEC though. Note that the for eucalyptus users, lots of docs remain at https:/
I will be merging (in a few weeks) a chapter for serverguide targeting the new Ubuntu Cloud product that's based on OpenStack
Revision history for this message
| Scott Kitterman (kitterman) wrote : | # |
> UEC as a product no longer exists, only the upstream eucalyptus project exists
> in universe. The docs were targeting UEC though. Note that the for eucalyptus
> users, lots of docs remain at https:/
> I will be merging (in a few weeks) a chapter for serverguide targeting the new
> Ubuntu Cloud product that's based on OpenStack
Then the documentation should be updated to say this and point to Eucalyptus documentation and give any needed information on the upgrade path from UEC/Natty to Eucalpytus/Oneiric. I don't think just deleting UEC is the right change.
Revision history for this message
| Connor Imes (ckimes) wrote : | # |
Is the documentation that was removed still valid even though UEC is obsolete? If the directions are going to cause problems, then it should be removed, even if no Ubuntu Cloud documentation is available yet.
Otherwise I think they should be updated to describe an upgrade path from UEC to Ubuntu Cloud as Scott suggested (whether this is done here or in the new chapter you are working on). Let's see if we can decide on an approach before String Freeze this coming week. Thanks.
Revision history for this message
| Ahmed Kamal (kim0) wrote : | # |
Trying to answer a few of Connor's questions:
- No the docs are not valid since UEC as a whole no longer exists. So yes for 11.10 these docs would be meaningless, and IMO should be removed
- Ubuntu Cloud (new product based on openstack) docs will hopefully be made available before Oneiric release. I will be compiling most of it (however I am now blocked since the product itself is not exactly ready yet)
- AFAIK, there is no upgrade path from UEC to UC. This had been discussed at previous UDS, and since the two cloud products are based on completely different technologies (eucalyptus vs openstack) the upgrade story was too complex, and AFAIK does not exist
So IMO, old UEC docs should be removed. And perhaps a note should be added that "If you are using UEC, a product that shipped with earlier versions of Ubuntu server, you can view docs about it here <help.ubuntu.
Does that make sense?
Revision history for this message
| Connor Imes (ckimes) wrote : | # |
That makes sense, Ahmed, thanks for posting back. Since we do not have system documentation available yet for Ubuntu Cloud, let's add a note that UEC is no longer available and post a link to online documentation about Ubuntu Cloud (even if it's still a placeholder). Right now I see http://
Revision history for this message
| Scott Kitterman (kitterman) wrote : | # |
I'd like to see some guidance for existing UEC users, even if it's "Don't
upgrade because you're screwed if you do". Ideally there are Eucalyptus
packages in Oneiric that they can upgrade to use even if UEC as a product
isn't provided anymore. I don't think just rm -rf all mention of UEC is the
right thing to do.
Revision history for this message
| Ahmed Kamal (kim0) wrote : | # |
I just checked and the server team is pretty confident eucalyptus will not be usable in 11.10, so the advice is pretty much going to be ""Don't upgrade because you're screwed if you do"
I'll add that warning, a link to the help.u.c UEC docs, a link to the natty serverguide and a link to the yet-to-be-written new ubuntu-cloud chapter in a later commit
- 12. By Ahmed Kamal
-
Adding UEC deprecation warning
Revision history for this message
| Dave Walker (davewalker) wrote : | # |
Things have changed since the latest advice we provided we provided to Ahmed. With thanks to upstream, it seems to be functional. This being said, Eucalyptus hasn't received the same level of testing and QA that previous Ubuntu releases had. Therefore, I think it's reasonable guidance to suggest staying with Natty (where it is still in Main) - but upgrading /should/ work.
Thanks.
Revision history for this message
| Doug Smythies (dsmythies) wrote : | # |
This merge proposal is obsolete is it not? Can it be set to "REJECTED" and deleted?
We are no longer edting oneric anyhow, and any good carry forward edits I think have been done. (line 61, for example)
Revision history for this message
| Doug Smythies (dsmythies) wrote : | # |
There were a couple of single lines changes (43, 52) herein that I have added to an edit being done now for raring. As mentioned before the line 61 change has already been done. The rest is obsolete or already done, and this will be set to REJECTED to get it off the list.
Unmerged revisions
- 12. By Ahmed Kamal
-
Adding UEC deprecation warning
- 11. By Ahmed Kamal
-
Removing references to UEC from installation chapter, the validator script is happy now
- 10. By Ahmed Kamal
-
Deleting all UEC information, UEC is obsolete, new Ubuntu Cloud product is based on OpenStack not Eucalyptus. The new OpenStack based Ubuntu Cloud will get its own chapter
- 9. By Ahmed Kamal
-
Updating KVM homepage URL
- 8. By Ahmed Kamal
-
Removing virt-viewer command since it has its own section
- 7. By Ahmed Kamal
-
Adding virt-viewer command
- 6. By Ahmed Kamal
-
package kvm is now called qemu-kvm
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
| 1 | === modified file 'serverguide/C/installation.xml' |
| 2 | --- serverguide/C/installation.xml 2011-08-16 12:03:04 +0000 |
| 3 | +++ serverguide/C/installation.xml 2011-10-04 16:22:23 +0000 |
| 4 | @@ -58,11 +58,6 @@ |
| 5 | as file/print services, web hosting, email hosting, etc. |
| 6 | </para> |
| 7 | |
| 8 | - <para> |
| 9 | - The requirements for UEC are slightly different for Front End requirements see <xref linkend="uec-frontend-requirements"/> and for |
| 10 | - UEC Node requirements see <xref linkend="uec-node-requirements"/>. |
| 11 | - </para> |
| 12 | - |
| 13 | </sect2> |
| 14 | |
| 15 | <sect2 id="intro-server-differences" status="review"> |
| 16 | |
| 17 | === modified file 'serverguide/C/virtualization.xml' |
| 18 | --- serverguide/C/virtualization.xml 2011-06-01 14:48:29 +0000 |
| 19 | +++ serverguide/C/virtualization.xml 2011-10-04 16:22:23 +0000 |
| 20 | @@ -23,7 +23,16 @@ |
| 21 | For hardware without virtualization extensions <application>Xen</application> and |
| 22 | <application>Qemu</application> are popular solutions. |
| 23 | </para> |
| 24 | - <sect1 id='libvirt' status='review'> |
| 25 | + <warning> |
| 26 | + <para> |
| 27 | + Ubuntu Enterprise Cloud (UEC), a private cloud eucalyptus-based product offered during earlier Ubuntu releases has |
| 28 | + been deprecated. Starting the Ubuntu server Oneiric 11.10 release, a replacement openstack-based product "Ubuntu Cloud |
| 29 | + Infrastructure" is Ubuntu's official private cloud solution. There is no formal migration path from UEC to |
| 30 | + Ubuntu Cloud Infrastructure. New installations and UEC upgrades to Eucalyptus on 11.10 (Oneiric) should be functional, however since it has been moved to the Universe repository; the same level of QA hasn't been conducted. It is thought that 11.04 UEC provides a more known stability for those wishing to use Eucalyptus. For information regarding UEC, see <ulink url="https://help.ubuntu.com/community/UEC">UEC community help</ulink> and |
| 31 | + <ulink url="https://help.ubuntu.com/11.04/serverguide/C/index.html">Ubuntu Natty server guide</ulink> |
| 32 | + </para> |
| 33 | + </warning> |
| 34 | +<sect1 id='libvirt' status='review'> |
| 35 | <title>libvirt</title> |
| 36 | <para> |
| 37 | The <application>libvirt</application> library is used to interface with different |
| 38 | @@ -39,7 +48,7 @@ |
| 39 | </para> |
| 40 | <note> |
| 41 | <para> |
| 42 | - On most computer whose processor supports virtualization, it is |
| 43 | + On many computers with processors supporting hardware assisted virtualization, it is |
| 44 | necessary to activate an option in the BIOS to enable it. |
| 45 | </para> |
| 46 | </note> |
| 47 | @@ -64,7 +73,7 @@ |
| 48 | To install the necessary packages, from a terminal prompt enter: |
| 49 | </para> |
| 50 | <screen> |
| 51 | -<command>sudo apt-get install kvm libvirt-bin</command> |
| 52 | +<command>sudo apt-get install qemu-kvm libvirt-bin</command> |
| 53 | </screen> |
| 54 | <para> |
| 55 | After installing <application>libvirt-bin</application>, the user used to manage virtual machines will need to be added to |
| 56 | @@ -369,7 +378,7 @@ |
| 57 | <itemizedlist> |
| 58 | <listitem> |
| 59 | <para> |
| 60 | - See the <ulink url="http://kvm.qumranet.com/kvmwiki">KVM</ulink> home page for more details. |
| 61 | + See the <ulink url="http://www.linux-kvm.org/page/Main_Page">KVM</ulink> home page for more details. |
| 62 | </para> |
| 63 | </listitem> |
| 64 | <listitem> |
| 65 | @@ -1073,1147 +1082,4 @@ |
| 66 | </itemizedlist> |
| 67 | </sect2> |
| 68 | </sect1> |
| 69 | - <sect1 id="uec" status="review"> |
| 70 | - <title>UEC</title> |
| 71 | - |
| 72 | - <sect2 id="uec-overview" status="review"> |
| 73 | - <title>Overview</title> |
| 74 | - |
| 75 | - <para> |
| 76 | - This tutorial covers <application>UEC</application> installation from the Ubuntu &distro-rev; Server Edition CD, and assumes a basic network topology, |
| 77 | - with a single system serving as the <emphasis>"all-in-one controller"</emphasis>, and one or more nodes attached. |
| 78 | - </para> |
| 79 | - |
| 80 | - <para> |
| 81 | - From this Tutorial you will learn how to install, configure, register and perform several operations on a basic <application>UEC</application> |
| 82 | - setup that results in a cloud with a one controller <emphasis>"front-end"</emphasis> and one or several node(s) for running Virtual Machine (VM) |
| 83 | - instances. You will also use examples to help get you started using your own private compute cloud. |
| 84 | - </para> |
| 85 | - |
| 86 | - </sect2> |
| 87 | - <sect2 id="uec-prerequisites" status="review"> |
| 88 | - <title>Prerequisites</title> |
| 89 | - |
| 90 | - <para> |
| 91 | - To deploy a minimal cloud infrastructure, you’ll need at least <emphasis>two</emphasis> dedicated systems: |
| 92 | - </para> |
| 93 | - |
| 94 | - <itemizedlist> |
| 95 | - <listitem> |
| 96 | - <para> |
| 97 | - A front end. |
| 98 | - </para> |
| 99 | - </listitem> |
| 100 | - <listitem> |
| 101 | - <para> |
| 102 | - One or more node(s). |
| 103 | - </para> |
| 104 | - </listitem> |
| 105 | - </itemizedlist> |
| 106 | - |
| 107 | - <para> |
| 108 | - The following are recommendations, rather than fixed requirements. However, our experience in developing this documentation indicated the following suggestions. |
| 109 | - </para> |
| 110 | - |
| 111 | - <sect3 id="uec-frontend-requirements" status="review"> |
| 112 | - <title>Front End Requirements</title> |
| 113 | - |
| 114 | - <para> |
| 115 | - Use the following table for a system that will run one or more of: |
| 116 | - </para> |
| 117 | - |
| 118 | - <itemizedlist> |
| 119 | - <listitem><para>Cloud Controller (CLC)</para></listitem> |
| 120 | - <listitem><para>Cluster Controller (CC)</para></listitem> |
| 121 | - <listitem><para>Walrus (the S3-like storage service)</para></listitem> |
| 122 | - <listitem><para>Storage Controller (SC)</para></listitem> |
| 123 | - </itemizedlist> |
| 124 | - |
| 125 | - <literallayout> |
| 126 | - |
| 127 | - |
| 128 | - |
| 129 | - |
| 130 | - |
| 131 | - |
| 132 | - |
| 133 | - |
| 134 | - </literallayout> |
| 135 | - |
| 136 | - <table> |
| 137 | - <title>UEC Front End Requirements</title> |
| 138 | - <tgroup cols="4" rowsep="1"> |
| 139 | - <colspec colname="1"/> |
| 140 | - <colspec colname="2"/> |
| 141 | - <colspec colname="3"/> |
| 142 | - <colspec colname="4"/> |
| 143 | - <thead> |
| 144 | - <row> |
| 145 | - <entry valign="middle"><para>Hardware</para></entry> |
| 146 | - <entry valign="middle"><para>Minimum</para></entry> |
| 147 | - <entry valign="middle"><para>Suggested</para></entry> |
| 148 | - <entry valign="middle"><para>Notes</para></entry> |
| 149 | - </row> |
| 150 | - </thead> |
| 151 | - <tbody> |
| 152 | - <row> |
| 153 | - <entry><para>CPU</para></entry> |
| 154 | - <entry><para>1 GHz</para></entry> |
| 155 | - <entry><para>2 x 2 GHz</para></entry> |
| 156 | - <entry><para>For an <emphasis>all-in-one</emphasis> front end, it helps to have at least a dual core processor.</para></entry> |
| 157 | - </row> |
| 158 | - <row> |
| 159 | - <entry><para>Memory</para></entry> |
| 160 | - <entry><para>2 GB</para></entry> |
| 161 | - <entry><para>4 GB</para></entry> |
| 162 | - <entry><para>The Java web front end benefits from lots of available memory.</para></entry> |
| 163 | - </row> |
| 164 | - <row> |
| 165 | - <entry><para>Disk</para></entry> |
| 166 | - <entry><para>5400 RPM IDE</para></entry> |
| 167 | - <entry><para>7200 RPM SATA</para></entry> |
| 168 | - <entry><para>Slower disks will work, but will yield much longer instance startup times.</para></entry> |
| 169 | - </row> |
| 170 | - <row> |
| 171 | - <entry><para>Disk Space</para></entry> |
| 172 | - <entry><para>40 GB</para></entry> |
| 173 | - <entry><para>200 GB</para></entry> |
| 174 | - <entry><para>40GB is only enough space for only a single image, cache, etc., Eucalyptus does not like to run out of disk space.</para></entry> |
| 175 | - </row> |
| 176 | - <row> |
| 177 | - <entry><para>Networking</para></entry> |
| 178 | - <entry><para>100 Mbps</para></entry> |
| 179 | - <entry><para>1000 Mbps</para></entry> |
| 180 | - <entry><para>Machine images are hundreds of MB, and need to be copied over the network to nodes.</para></entry> |
| 181 | - </row> |
| 182 | - </tbody> |
| 183 | - </tgroup> |
| 184 | - </table> |
| 185 | - |
| 186 | - <literallayout> |
| 187 | - |
| 188 | - |
| 189 | - |
| 190 | - |
| 191 | - |
| 192 | - |
| 193 | - |
| 194 | - |
| 195 | - </literallayout> |
| 196 | - </sect3> |
| 197 | - <sect3 id="uec-node-requirements" status="review"> |
| 198 | - <title>Node Requirements</title> |
| 199 | - |
| 200 | - <para> |
| 201 | - The other system(s) are <emphasis>nodes</emphasis>, which will run: |
| 202 | - </para> |
| 203 | - |
| 204 | - <itemizedlist> |
| 205 | - <listitem><para>the Node Controller (NC)</para></listitem> |
| 206 | - </itemizedlist> |
| 207 | - |
| 208 | - <table> |
| 209 | - <title>UEC Node Requirements</title> |
| 210 | - <tgroup cols="4" rowsep="1"> |
| 211 | - <colspec colname="1"/> |
| 212 | - <colspec colname="2"/> |
| 213 | - <colspec colname="3"/> |
| 214 | - <colspec colname="4"/> |
| 215 | - <thead> |
| 216 | - <row> |
| 217 | - <entry valign="middle"><para>Hardware</para></entry> |
| 218 | - <entry valign="middle"><para>Minimum</para></entry> |
| 219 | - <entry valign="middle"><para>Suggested</para></entry> |
| 220 | - <entry valign="middle"><para>Notes</para></entry> |
| 221 | - </row> |
| 222 | - </thead> |
| 223 | - <tbody> |
| 224 | - <row> |
| 225 | - <entry><para>CPU</para></entry> |
| 226 | - <entry><para>VT Extensions</para></entry> |
| 227 | - <entry><para>VT, 64-bit, Multicore</para></entry> |
| 228 | - <entry><para>64-bit can run both i386, and amd64 instances; by default, Eucalyptus will only run 1 VM per CPU core on a Node.</para></entry> |
| 229 | - </row> |
| 230 | - <row> |
| 231 | - <entry><para>Memory</para></entry> |
| 232 | - <entry><para>1 GB</para></entry> |
| 233 | - <entry><para>4 GB</para></entry> |
| 234 | - <entry><para>Additional memory means more, and larger guests.</para></entry> |
| 235 | - </row> |
| 236 | - <row> |
| 237 | - <entry><para>Disk</para></entry> |
| 238 | - <entry><para>5400 RPM IDE</para></entry> |
| 239 | - <entry><para>7200 RPM SATA or SCSI</para></entry> |
| 240 | - <entry><para>Eucalyptus nodes are disk-intensive; I/O wait will likely be the performance bottleneck.</para></entry> |
| 241 | - </row> |
| 242 | - <row> |
| 243 | - <entry><para>Disk Space</para></entry> |
| 244 | - <entry><para>40 GB</para></entry> |
| 245 | - <entry><para>100 GB</para></entry> |
| 246 | - <entry><para>Images will be cached locally, Eucalyptus does not like to run out of disk space.</para></entry> |
| 247 | - </row> |
| 248 | - <row> |
| 249 | - <entry><para>Networking</para></entry> |
| 250 | - <entry><para>100 Mbps</para></entry> |
| 251 | - <entry><para>1000 Mbps</para></entry> |
| 252 | - <entry><para>Machine images are hundreds of MB, and need to be copied over the network to nodes.</para></entry> |
| 253 | - </row> |
| 254 | - </tbody> |
| 255 | - </tgroup> |
| 256 | - </table> |
| 257 | - |
| 258 | - </sect3> |
| 259 | - |
| 260 | - </sect2> |
| 261 | - <sect2 id="uec-frontend-installation" status="review"> |
| 262 | - <title>Installing the Cloud/Cluster/Storage/Walrus Front End Server</title> |
| 263 | - |
| 264 | - <procedure> |
| 265 | - <step> |
| 266 | - <para> |
| 267 | - Download the Ubuntu &distro-rev; Server ISO file, and burn it to a CD. |
| 268 | - </para> |
| 269 | - </step> |
| 270 | - <step> |
| 271 | - <para> |
| 272 | - When you boot, select <emphasis>“Install Ubuntu Enterprise Cloud”</emphasis>. The installer will detect if any other Eucalyptus components are present. |
| 273 | - </para> |
| 274 | - </step> |
| 275 | - <step> |
| 276 | - <para> |
| 277 | - You can then choose which components to install, based on your chosen <ulink url="https://help.ubuntu.com/community/UEC/Topologies">topology</ulink>. |
| 278 | - </para> |
| 279 | - </step> |
| 280 | - <step> |
| 281 | - <para> |
| 282 | - When asked whether you want a <emphasis>“Cluster”</emphasis> or a <emphasis>“Node”</emphasis> install, select |
| 283 | - <emphasis>“Cluster”</emphasis>. |
| 284 | - </para> |
| 285 | - </step> |
| 286 | - <step> |
| 287 | - <para> |
| 288 | - It will ask two other cloud-specific questions during the course of the install: |
| 289 | - </para> |
| 290 | - <itemizedlist> |
| 291 | - <listitem> |
| 292 | - <para> |
| 293 | - Name of your cluster. |
| 294 | - </para> |
| 295 | - <itemizedlist><listitem><para>e.g. <emphasis>cluster1</emphasis>.</para></listitem></itemizedlist> |
| 296 | - </listitem> |
| 297 | - <listitem> |
| 298 | - <para> |
| 299 | - A range of public IP addresses on the LAN that the cloud can allocate to instances. |
| 300 | - </para> |
| 301 | - <itemizedlist><listitem><para>e.g. <emphasis>192.168.1.200-192.168.1.249</emphasis>.</para></listitem></itemizedlist> |
| 302 | - </listitem> |
| 303 | - </itemizedlist> |
| 304 | - </step> |
| 305 | - </procedure> |
| 306 | - |
| 307 | - </sect2> |
| 308 | - <sect2 id="uec-node-installation" status="review"> |
| 309 | - <title>Installing the Node Controller(s)</title> |
| 310 | - |
| 311 | - <para> |
| 312 | - The node controller install is even simpler. Just make sure that you are connected to the network on which the cloud/cluster controller is already running. |
| 313 | - </para> |
| 314 | - |
| 315 | - <procedure> |
| 316 | - <step> |
| 317 | - <para> |
| 318 | - Boot from the same ISO on the node(s). |
| 319 | - </para> |
| 320 | - </step> |
| 321 | - <step> |
| 322 | - <para> |
| 323 | - When you boot, select <emphasis>“Install Ubuntu Enterprise Cloud”</emphasis>. |
| 324 | - </para> |
| 325 | - </step> |
| 326 | - <step> |
| 327 | - <para> |
| 328 | - Select <emphasis>“Install Ubuntu Enterprise Cloud”</emphasis>. |
| 329 | - </para> |
| 330 | - </step> |
| 331 | - <step> |
| 332 | - <para> |
| 333 | - It should detect the Cluster and preselect <emphasis>“Node”</emphasis> install for you. |
| 334 | - </para> |
| 335 | - </step> |
| 336 | - <step> |
| 337 | - <para> |
| 338 | - Confirm the partitioning scheme. |
| 339 | - </para> |
| 340 | - </step> |
| 341 | - <step> |
| 342 | - <para> |
| 343 | - The rest of the installation should proceed uninterrupted; complete the installation and reboot the node. |
| 344 | - </para> |
| 345 | - </step> |
| 346 | - </procedure> |
| 347 | - |
| 348 | - </sect2> |
| 349 | - <sect2 id="uec-register-nodes" status="review"> |
| 350 | - <title>Register the Node(s)</title> |
| 351 | - |
| 352 | - <procedure> |
| 353 | - <step> |
| 354 | - |
| 355 | - <para> |
| 356 | - Nodes are the physical systems within <application>UEC</application> that actually run the virtual machine instances of the cloud. |
| 357 | - </para> |
| 358 | - |
| 359 | - <para> |
| 360 | - All component registration should be automatic, assuming: |
| 361 | - </para> |
| 362 | - |
| 363 | - <orderedlist numeration="loweralpha"> |
| 364 | - <listitem> |
| 365 | - <para> |
| 366 | - Public SSH keys have been exchanged properly. |
| 367 | - </para> |
| 368 | - </listitem> |
| 369 | - <listitem> |
| 370 | - <para> |
| 371 | - The services are configured properly. |
| 372 | - </para> |
| 373 | - </listitem> |
| 374 | - <listitem> |
| 375 | - <para> |
| 376 | - The appropriate <emphasis>uec-component-listener</emphasis> is running. |
| 377 | - </para> |
| 378 | - </listitem> |
| 379 | - <listitem> |
| 380 | - <para> |
| 381 | - Verify Registration. |
| 382 | - </para> |
| 383 | - </listitem> |
| 384 | - </orderedlist> |
| 385 | - |
| 386 | - <para> |
| 387 | - Steps a to e should only be required if you're using the <ulink url="https://help.ubuntu.com/community/UEC/PackageInstall">UEC/PackageInstall</ulink> method. |
| 388 | - Otherwise, if you are following this guide, these steps should already be completed automatically for you, and therefore you can skip <emphasis>"a"</emphasis> |
| 389 | - to <emphasis>"e"</emphasis>. |
| 390 | - </para> |
| 391 | - |
| 392 | - </step> |
| 393 | - <step> |
| 394 | - <para>Exchange Public Keys</para> |
| 395 | - |
| 396 | - <para> |
| 397 | - The Cloud Controller's <emphasis>eucalyptus</emphasis> user needs to have SSH access to the Walrus Controller, Cluster Controller, and Storage Controller |
| 398 | - as the eucalyptus user. |
| 399 | - </para> |
| 400 | - |
| 401 | - <para> |
| 402 | - Install the Cloud Controller's <emphasis>eucalyptus</emphasis> user's public ssh key by: |
| 403 | - </para> |
| 404 | - |
| 405 | - <itemizedlist> |
| 406 | - <listitem> |
| 407 | - <para> |
| 408 | - On the target controller, temporarily set a password for the eucalyptus user: |
| 409 | - </para> |
| 410 | -<screen> |
| 411 | -<command>sudo passwd eucalyptus</command> |
| 412 | -</screen> |
| 413 | - </listitem> |
| 414 | - <listitem> |
| 415 | - <para> |
| 416 | - Then, on the Cloud Controller: |
| 417 | - </para> |
| 418 | -<screen> |
| 419 | -<command>sudo -u eucalyptus ssh-copy-id -i ~eucalyptus/.ssh/id_rsa.pub eucalyptus@<IP_OF_NODE></command> |
| 420 | -</screen> |
| 421 | - </listitem> |
| 422 | - <listitem> |
| 423 | - <para> |
| 424 | - You can now remove the password of the eucalyptus account on the target controller, if you wish: |
| 425 | - </para> |
| 426 | -<screen> |
| 427 | -<command>sudo passwd -d eucalyptus</command> |
| 428 | -</screen> |
| 429 | - </listitem> |
| 430 | - </itemizedlist> |
| 431 | - |
| 432 | - </step> |
| 433 | - <step> |
| 434 | - <para>Configuring the Services</para> |
| 435 | - |
| 436 | - <para> |
| 437 | - On the <emphasis>Cloud Controller</emphasis>: |
| 438 | - </para> |
| 439 | - |
| 440 | - <itemizedlist> |
| 441 | - <listitem> |
| 442 | - <para> |
| 443 | - For the <emphasis>Cluster Controller</emphasis> Registration: |
| 444 | - </para> |
| 445 | - <itemizedlist> |
| 446 | - <listitem><para>Define the shell variable CC_NAME in <filename>/etc/eucalyptus/eucalyptus-cc.conf</filename></para></listitem> |
| 447 | - <listitem> |
| 448 | - <para> |
| 449 | - Define the shell variable CC_IP_ADDR in <filename>/etc/eucalyptus/eucalyptus-ipaddr.conf</filename>, as a space separated list of one or more IP addresses. |
| 450 | - </para> |
| 451 | - </listitem> |
| 452 | - </itemizedlist> |
| 453 | - </listitem> |
| 454 | - <listitem> |
| 455 | - <para> |
| 456 | - For the <emphasis>Walrus Controller</emphasis> Registration: |
| 457 | - </para> |
| 458 | - <itemizedlist> |
| 459 | - <listitem><para>Define the shell variable WALRUS_IP_ADDR in <filename>/etc/eucalyptus/eucalyptus-ipaddr.conf</filename>, as a single IP address.</para></listitem> |
| 460 | - </itemizedlist> |
| 461 | - </listitem> |
| 462 | - </itemizedlist> |
| 463 | - |
| 464 | - <para> |
| 465 | - On the <emphasis>Cluster Controller</emphasis>: |
| 466 | - </para> |
| 467 | - |
| 468 | - <itemizedlist> |
| 469 | - <listitem> |
| 470 | - <para> |
| 471 | - For <emphasis>Storage Controller</emphasis> Registration: |
| 472 | - </para> |
| 473 | - <itemizedlist> |
| 474 | - <listitem><para>Define the shell variable CC_NAME in <filename>/etc/eucalyptus/eucalyptus-cc.conf</filename></para></listitem> |
| 475 | - <listitem> |
| 476 | - <para> |
| 477 | - Define the shell variable SC_IP_ADDR in <filename>/etc/eucalyptus/eucalyptus-ipaddr.conf</filename>, as a space separated list of one or more IP addresses. |
| 478 | - </para> |
| 479 | - </listitem> |
| 480 | - </itemizedlist> |
| 481 | - </listitem> |
| 482 | - </itemizedlist> |
| 483 | - |
| 484 | - </step> |
| 485 | - <step> |
| 486 | - <para>Publish</para> |
| 487 | - |
| 488 | - <para> |
| 489 | - Now start the publication services. |
| 490 | - </para> |
| 491 | - |
| 492 | - <itemizedlist> |
| 493 | - <listitem> |
| 494 | - <para><emphasis>Walrus Controller:</emphasis></para> |
| 495 | -<screen> |
| 496 | -<command>sudo start eucalyptus-walrus-publication</command> |
| 497 | -</screen> |
| 498 | - </listitem> |
| 499 | - <listitem> |
| 500 | - <para><emphasis>Cluster Controller:</emphasis></para> |
| 501 | -<screen> |
| 502 | -<command>sudo start eucalyptus-cc-publication</command> |
| 503 | -</screen> |
| 504 | - </listitem> |
| 505 | - <listitem> |
| 506 | - <para><emphasis>Storage Controller:</emphasis></para> |
| 507 | -<screen> |
| 508 | -<command>sudo start eucalyptus-sc-publication</command> |
| 509 | -</screen> |
| 510 | - </listitem> |
| 511 | - <listitem> |
| 512 | - <para><emphasis>Node Controller:</emphasis></para> |
| 513 | -<screen> |
| 514 | -<command>sudo start eucalyptus-nc-publication</command> |
| 515 | -</screen> |
| 516 | - </listitem> |
| 517 | - </itemizedlist> |
| 518 | - |
| 519 | - </step> |
| 520 | - <step> |
| 521 | - <para>Start the Listener</para> |
| 522 | - |
| 523 | - <para> |
| 524 | - On the <emphasis>Cloud Controller</emphasis> and the <emphasis>Cluster Controller(s)</emphasis>, run: |
| 525 | - </para> |
| 526 | - |
| 527 | -<screen> |
| 528 | -<command>sudo start uec-component-listener</command> |
| 529 | -</screen> |
| 530 | - |
| 531 | - </step> |
| 532 | - <step> |
| 533 | - <para>Verify Registration</para> |
| 534 | - |
| 535 | -<screen> |
| 536 | -<command>cat /var/log/eucalyptus/registration.log</command> |
| 537 | -<computeroutput>2010-04-08 15:46:36-05:00 | 24243 -> Calling node cluster1 node 10.1.1.75 |
| 538 | -2010-04-08 15:46:36-05:00 | 24243 -> euca_conf --register-nodes returned 0 |
| 539 | -2010-04-08 15:48:47-05:00 | 25858 -> Calling walrus Walrus 10.1.1.71 |
| 540 | -2010-04-08 15:48:51-05:00 | 25858 -> euca_conf --register-walrus returned 0 |
| 541 | -2010-04-08 15:49:04-05:00 | 26237 -> Calling cluster cluster1 10.1.1.71 |
| 542 | -2010-04-08 15:49:08-05:00 | 26237 -> euca_conf --register-cluster returned 0 |
| 543 | -2010-04-08 15:49:17-05:00 | 26644 -> Calling storage cluster1 storage 10.1.1.71 |
| 544 | -2010-04-08 15:49:18-05:00 | 26644 -> euca_conf --register-sc returned 0</computeroutput> |
| 545 | -</screen> |
| 546 | - |
| 547 | - <note> |
| 548 | - <para> |
| 549 | - The output on your machine will vary from the example above. |
| 550 | - </para> |
| 551 | - </note> |
| 552 | - |
| 553 | - </step> |
| 554 | - </procedure> |
| 555 | - |
| 556 | - </sect2> |
| 557 | - <sect2 id="uec-obtain-credentials" status="review"> |
| 558 | - <title>Obtain Credentials</title> |
| 559 | - |
| 560 | - <para> |
| 561 | - After installing and booting the <emphasis>Cloud Controller</emphasis>, users of the cloud will need to retrieve their credentials. |
| 562 | - This can be done either through a web browser, or at the command line. |
| 563 | - </para> |
| 564 | - |
| 565 | - <sect3 id="uec-creds-browser" status="review"> |
| 566 | - <title>From a Web Browser</title> |
| 567 | - |
| 568 | - <procedure> |
| 569 | - <step> |
| 570 | - <para> |
| 571 | - From your web browser (either remotely or on your Ubuntu server) access the following URL: |
| 572 | - </para> |
| 573 | -<programlisting> |
| 574 | -https://<cloud-controller-ip-address>:8443/ |
| 575 | -</programlisting> |
| 576 | - |
| 577 | - <warning> |
| 578 | - <para> |
| 579 | - You must use a secure connection, so make sure you use "https" not "http" in your URL. You will get a security |
| 580 | - certificate warning. You will have to add an exception to view the page. If you do not accept it you will not |
| 581 | - be able to view the Eucalyptus configuration page. |
| 582 | - </para> |
| 583 | - </warning> |
| 584 | - </step> |
| 585 | - <step> |
| 586 | - <para> |
| 587 | - Use username <emphasis>'admin'</emphasis> and password <emphasis>'admin'</emphasis> for the first time login |
| 588 | - (you will be prompted to change your password). |
| 589 | - </para> |
| 590 | - </step> |
| 591 | - <step> |
| 592 | - <para> |
| 593 | - Then follow the on-screen instructions to update the admin password and email address. |
| 594 | - </para> |
| 595 | - </step> |
| 596 | - <step> |
| 597 | - <para> |
| 598 | - Once the first time configuration process is completed, click the <emphasis>'credentials'</emphasis> tab |
| 599 | - located in the top-left portion of the screen. |
| 600 | - </para> |
| 601 | - </step> |
| 602 | - <step> |
| 603 | - <para> |
| 604 | - Click the <emphasis>'Download Credentials'</emphasis> button to get your certificates. |
| 605 | - </para> |
| 606 | - </step> |
| 607 | - <step> |
| 608 | - <para> |
| 609 | - Save them to <filename>~/.euca</filename>. |
| 610 | - </para> |
| 611 | - </step> |
| 612 | - <step> |
| 613 | - <para> |
| 614 | - Unzip the downloaded zip file into a safe location (<filename>~/.euca</filename>). |
| 615 | - </para> |
| 616 | -<screen> |
| 617 | -<command>unzip -d ~/.euca mycreds.zip</command> |
| 618 | -</screen> |
| 619 | - </step> |
| 620 | - </procedure> |
| 621 | - |
| 622 | - </sect3> |
| 623 | - <sect3 id="uec-creds-cli" status="review"> |
| 624 | - <title>From a Command Line</title> |
| 625 | - |
| 626 | - <procedure> |
| 627 | - <step> |
| 628 | - <para> |
| 629 | - Alternatively, if you are on the command line of the <emphasis>Cloud Controller</emphasis>, you can run: |
| 630 | - </para> |
| 631 | -<screen> |
| 632 | -<command>mkdir -p ~/.euca</command> |
| 633 | -<command>chmod 700 ~/.euca</command> |
| 634 | -<command>cd ~/.euca</command> |
| 635 | -<command>sudo euca_conf --get-credentials mycreds.zip</command> |
| 636 | -<command>unzip mycreds.zip</command> |
| 637 | -<command>ln -s ~/.euca/eucarc ~/.eucarc</command> |
| 638 | -<command>cd -</command> |
| 639 | -</screen> |
| 640 | - </step> |
| 641 | - </procedure> |
| 642 | - |
| 643 | - </sect3> |
| 644 | - <sect3 id="uec-creds-usage" status="review"> |
| 645 | - <title>Extracting and Using Your Credentials</title> |
| 646 | - |
| 647 | - <para> |
| 648 | - Now you will need to setup EC2 API and AMI tools on your server using X.509 certificates. |
| 649 | - </para> |
| 650 | - |
| 651 | - <procedure> |
| 652 | - <step> |
| 653 | - <para> |
| 654 | - Install the required cloud user tools: |
| 655 | - </para> |
| 656 | -<screen> |
| 657 | -<command>sudo apt-get install euca2ools</command> |
| 658 | -</screen> |
| 659 | - </step> |
| 660 | - <step> |
| 661 | - <para> |
| 662 | - To validate that everything is working correctly, get the local cluster availability details: |
| 663 | - </para> |
| 664 | -<screen> |
| 665 | -<command>. ~/.euca/eucarc</command> |
| 666 | -<command>euca-describe-availability-zones verbose</command> |
| 667 | -<computeroutput>AVAILABILITYZONE myowncloud 192.168.1.1 |
| 668 | -AVAILABILITYZONE |- vm types free / max cpu ram disk |
| 669 | -AVAILABILITYZONE |- m1.small 0004 / 0004 1 128 2 |
| 670 | -AVAILABILITYZONE |- c1.medium 0004 / 0004 1 256 5 |
| 671 | -AVAILABILITYZONE |- m1.large 0002 / 0002 2 512 10 |
| 672 | -AVAILABILITYZONE |- m1.xlarge 0002 / 0002 2 1024 20 |
| 673 | -AVAILABILITYZONE |- c1.xlarge 0001 / 0001 4 2048 20</computeroutput> |
| 674 | -</screen> |
| 675 | - |
| 676 | - <note> |
| 677 | - <para> |
| 678 | - Your output from the above command will vary. |
| 679 | - </para> |
| 680 | - </note> |
| 681 | - </step> |
| 682 | - </procedure> |
| 683 | - |
| 684 | - </sect3> |
| 685 | - </sect2> |
| 686 | - <sect2 id="uec-image-installation" status="review"> |
| 687 | - <title>Install an Image from the Store</title> |
| 688 | - |
| 689 | - <para> |
| 690 | - The following is by far the simplest way to install an image. However, advanced users may be interested in learning how to |
| 691 | - <ulink url="https://help.ubuntu.com/community/UEC/BundlingImages">Bundle their own image</ulink>. |
| 692 | - </para> |
| 693 | - |
| 694 | - <para> |
| 695 | - The simplest way to add an image to <application>UEC</application> is to install it from the Image Store on the UEC web interface. |
| 696 | - </para> |
| 697 | - |
| 698 | - <procedure> |
| 699 | - <step> |
| 700 | - <para> |
| 701 | - Access the web interface at the following URL (Make sure you specify https): |
| 702 | - </para> |
| 703 | -<programlisting> |
| 704 | -https://<cloud-controller-ip-address>:8443/ |
| 705 | -</programlisting> |
| 706 | - </step> |
| 707 | - <step> |
| 708 | - <para> |
| 709 | - Enter your login and password (if requested, as you may still be logged in from earlier). |
| 710 | - </para> |
| 711 | - </step> |
| 712 | - <step> |
| 713 | - <para> |
| 714 | - Click on the <emphasis>Store</emphasis> tab. |
| 715 | - </para> |
| 716 | - </step> |
| 717 | - <step> |
| 718 | - <para> |
| 719 | - Browse available images. |
| 720 | - </para> |
| 721 | - </step> |
| 722 | - <step> |
| 723 | - <para> |
| 724 | - Click on <emphasis>install</emphasis> for the image you want. |
| 725 | - </para> |
| 726 | - </step> |
| 727 | - </procedure> |
| 728 | - |
| 729 | - <para> |
| 730 | - Once the image has been downloaded and installed, you can click on <emphasis>"How to run?"</emphasis> that will be displayed |
| 731 | - below the image button to view the command to execute to instantiate (start) this image. The image will also appear on the |
| 732 | - list given on the <emphasis>Image</emphasis> tab. |
| 733 | - </para> |
| 734 | - |
| 735 | - </sect2> |
| 736 | - <sect2 id="uec-image-running" status="review"> |
| 737 | - <title>Run an Image</title> |
| 738 | - |
| 739 | - <para> |
| 740 | - There are multiple ways to instantiate an image in UEC: |
| 741 | - </para> |
| 742 | - |
| 743 | - <itemizedlist> |
| 744 | - <listitem><para>Use the command line.</para></listitem> |
| 745 | - <listitem><para>Use one of the UEC compatible management tools such as <emphasis>Landscape</emphasis>.</para></listitem> |
| 746 | - <listitem> |
| 747 | - <para> |
| 748 | - Use the <ulink url="https://help.ubuntu.com/community/UEC/ElasticFox">ElasticFox</ulink> extension to Firefox. |
| 749 | - </para> |
| 750 | - </listitem> |
| 751 | - </itemizedlist> |
| 752 | - |
| 753 | - <para> |
| 754 | - Here we will describe the process from the command line: |
| 755 | - </para> |
| 756 | - |
| 757 | - <procedure> |
| 758 | - <step> |
| 759 | - <para> |
| 760 | - Before running an instance of your image, you should first create a <emphasis>keypair</emphasis> (ssh key) that you can |
| 761 | - use to log into your instance as root, once it boots. The key is stored, so you will only have to do this once. |
| 762 | - </para> |
| 763 | - <para> |
| 764 | - Run the following command: |
| 765 | - </para> |
| 766 | -<programlisting> |
| 767 | -if [ ! -e ~/.euca/mykey.priv ]; then |
| 768 | - mkdir -p -m 700 ~/.euca |
| 769 | - touch ~/.euca/mykey.priv |
| 770 | - chmod 0600 ~/.euca/mykey.priv |
| 771 | - euca-add-keypair mykey > ~/.euca/mykey.priv |
| 772 | -fi |
| 773 | -</programlisting> |
| 774 | - <note> |
| 775 | - <para> |
| 776 | - You can call your key whatever you like (in this example, the key is called <emphasis>'mykey'</emphasis>), but remember what it is called. |
| 777 | - If you forget, you can always run <command>euca-describe-keypairs</command> to get a list of created keys stored in the system. |
| 778 | - </para> |
| 779 | - </note> |
| 780 | - </step> |
| 781 | - <step> |
| 782 | - <para> |
| 783 | - You must also allow access to port 22 in your instances: |
| 784 | - </para> |
| 785 | -<screen> |
| 786 | -<command>euca-authorize default -P tcp -p 22 -s 0.0.0.0/0</command> |
| 787 | -</screen> |
| 788 | - </step> |
| 789 | - <step> |
| 790 | - <para> |
| 791 | - Next, you can create instances of your registered image: |
| 792 | - </para> |
| 793 | -<screen> |
| 794 | -<command>euca-run-instances $EMI -k mykey -t m1.small</command> |
| 795 | -</screen> |
| 796 | - <note> |
| 797 | - <para> |
| 798 | - If you receive an error regarding <emphasis>image_id</emphasis>, you may find it by viewing Images page or click |
| 799 | - <emphasis>"How to Run"</emphasis> on the <emphasis>Store</emphasis> page to see the sample command. |
| 800 | - </para> |
| 801 | - </note> |
| 802 | - </step> |
| 803 | - <step> |
| 804 | - <para> |
| 805 | - The first time you run an instance, the system will be setting up caches for the image from which it will be created. |
| 806 | - This can often take some time the first time an instance is run given that VM images are usually quite large. |
| 807 | - </para> |
| 808 | - <para> |
| 809 | - To monitor the state of your instance, run: |
| 810 | - </para> |
| 811 | -<screen> |
| 812 | -<command>watch -n5 euca-describe-instances</command> |
| 813 | -</screen> |
| 814 | - <para> |
| 815 | - In the output, you should see information about the instance, including its state. While first-time caching is being performed, |
| 816 | - the instance's state will be <emphasis>'pending'</emphasis>. |
| 817 | - </para> |
| 818 | - </step> |
| 819 | - <step> |
| 820 | - <para> |
| 821 | - When the instance is fully started, the above state will become <emphasis>'running'</emphasis>. Look at the IP address assigned |
| 822 | - to your instance in the output, then connect to it: |
| 823 | - </para> |
| 824 | -<screen> |
| 825 | -<command>IPADDR=$(euca-describe-instances | grep $EMI | grep running | tail -n1 | awk '{print $4}')</command> |
| 826 | -<command>ssh -i ~/.euca/mykey.priv ubuntu@$IPADDR</command> |
| 827 | -</screen> |
| 828 | - </step> |
| 829 | - <step> |
| 830 | - <para> |
| 831 | - And when you are done with this instance, exit your SSH connection, then terminate your instance: |
| 832 | - </para> |
| 833 | -<screen> |
| 834 | -<command>INSTANCEID=$(euca-describe-instances | grep $EMI | grep running | tail -n1 | awk '{print $2}')</command> |
| 835 | -<command>euca-terminate-instances $INSTANCEID</command> |
| 836 | -</screen> |
| 837 | - </step> |
| 838 | - </procedure> |
| 839 | - |
| 840 | - <sect3 id="uec-first-boot" status="review"> |
| 841 | - <title>First Boot</title> |
| 842 | - |
| 843 | - <para> |
| 844 | - The <application>cloud-init</application> package provides "first boot" functionality for the Ubuntu UEC images. |
| 845 | - It is in charge of taking the generic filesystem image that is booting and customizing it for this particular instance. |
| 846 | - That includes things like: |
| 847 | - </para> |
| 848 | - |
| 849 | - <itemizedlist> |
| 850 | - <listitem> |
| 851 | - <para> |
| 852 | - Setting the hostname. |
| 853 | - </para> |
| 854 | - </listitem> |
| 855 | - <listitem> |
| 856 | - <para> |
| 857 | - Putting the provided ssh public keys into <filename>~ubuntu/.ssh/authorized_keys</filename>. |
| 858 | - </para> |
| 859 | - </listitem> |
| 860 | - <listitem> |
| 861 | - <para> |
| 862 | - Running a user provided script, or otherwise modifying the image. |
| 863 | - </para> |
| 864 | - </listitem> |
| 865 | - </itemizedlist> |
| 866 | - |
| 867 | - <para> |
| 868 | - Setting hostname and configuring a system so the person who launched it can actually log into it are not terribly interesting. |
| 869 | - The interesting things that can be done with <application>cloud-init</application> are made possible by data provided at launch |
| 870 | - time called <ulink url="http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1085">user-data</ulink>. |
| 871 | - </para> |
| 872 | - |
| 873 | - <para> |
| 874 | - First, install the <application>cloud-init</application> package: |
| 875 | - </para> |
| 876 | - |
| 877 | -<screen> |
| 878 | -<command>sudo apt-get install cloud-init</command> |
| 879 | -</screen> |
| 880 | - |
| 881 | - <para> |
| 882 | - If the user-data starts with <emphasis>'#!'</emphasis>, then it will be stored and executed as root late in the boot process of the |
| 883 | - instance's first boot (similar to a traditional 'rc.local' script). Output from the script is directed to the console. |
| 884 | - </para> |
| 885 | - |
| 886 | - <para> |
| 887 | - For example, create a file named <filename>ud.txt</filename> containing: |
| 888 | - </para> |
| 889 | - |
| 890 | -<programlisting> |
| 891 | -#!/bin/sh |
| 892 | -echo ========== Hello World: $(date) ========== |
| 893 | -echo "I have been up for $(cut -d\ -f 1 < /proc/uptime) sec" |
| 894 | -</programlisting> |
| 895 | - |
| 896 | - <para> |
| 897 | - Now start an instance with the <emphasis>--user-data-file</emphasis> option: |
| 898 | - </para> |
| 899 | - |
| 900 | -<screen> |
| 901 | -<command>euca-run-instances $EMI -k mykey -t m1.small --user-data-file=ud.txt</command> |
| 902 | -</screen> |
| 903 | - |
| 904 | - <para> |
| 905 | - Wait now for the system to come up and console to be available. To see the result of the data file commands enter: |
| 906 | - </para> |
| 907 | - |
| 908 | -<screen> |
| 909 | -<command>euca-get-console-output $EMI | grep --after-context=1 Hello</command> |
| 910 | -<computeroutput>========== Hello World: Mon Mar 29 18:05:05 UTC 2010 ========== |
| 911 | -I have been up for 28.26 sec</computeroutput> |
| 912 | -</screen> |
| 913 | - |
| 914 | - <note> |
| 915 | - <para> |
| 916 | - Your output may vary. |
| 917 | - </para> |
| 918 | - </note> |
| 919 | - |
| 920 | - <para> |
| 921 | - The simple approach shown above gives a great deal of power. The user-data can contain a script in any language where an interpreter already exists |
| 922 | - in the image (#!/bin/sh, #!/usr/bin/python, #!/usr/bin/perl, #!/usr/bin/awk ... ). |
| 923 | - </para> |
| 924 | - |
| 925 | - <para> |
| 926 | - For many cases, the user may not be interested in writing a program. For this case, cloud-init provides <emphasis>"cloud-config"</emphasis>, a configuration based approach |
| 927 | - towards customization. To utilize the cloud-config syntax, the supplied user-data must start with a <emphasis>'#cloud-config'</emphasis>. |
| 928 | - </para> |
| 929 | - |
| 930 | - <para> |
| 931 | - For example, create a text file named <filename>cloud-config.txt</filename> containing: |
| 932 | - </para> |
| 933 | - |
| 934 | -<programlisting> |
| 935 | -#cloud-config |
| 936 | -apt_upgrade: true |
| 937 | -apt_sources: |
| 938 | -- source: "ppa:ubuntu-server-edgers/server-edgers-apache " |
| 939 | - |
| 940 | -packages: |
| 941 | -- build-essential |
| 942 | -- pastebinit |
| 943 | - |
| 944 | -runcmd: |
| 945 | -- echo ======= Hello World ===== |
| 946 | -- echo "I have been up for $(cut -d\ -f 1 < /proc/uptime) sec" |
| 947 | -</programlisting> |
| 948 | - |
| 949 | - <para> |
| 950 | - Create a new instance: |
| 951 | - </para> |
| 952 | - |
| 953 | -<screen> |
| 954 | -<command>euca-run-instances $EMI -k mykey -t m1.small --user-data-file=cloud-config.txt</command> |
| 955 | -</screen> |
| 956 | - |
| 957 | - <para> |
| 958 | - Now, when the above system is booted, it will have: |
| 959 | - </para> |
| 960 | - |
| 961 | - <itemizedlist> |
| 962 | - <listitem><para>Added the Apache Edgers PPA.</para></listitem> |
| 963 | - <listitem><para>Run an upgrade to get all updates available</para></listitem> |
| 964 | - <listitem><para>Installed the 'build-essential' and 'pastebinit' packages</para></listitem> |
| 965 | - <listitem><para>Printed a similar message to the script above</para></listitem> |
| 966 | - </itemizedlist> |
| 967 | - |
| 968 | - <warning> |
| 969 | - <para> |
| 970 | - The <emphasis>Apache Edgers PPA</emphasis>, in the above example, contains the latest version of Apache from upstream source repositories. |
| 971 | - Package versions in the PPA are unsupported, and depending on your situation, this may or may not be desirable. See the |
| 972 | - <ulink url="https://launchpad.net/~ubuntu-server-edgers">Ubuntu Server Edgers</ulink> web page for more details. |
| 973 | - </para> |
| 974 | - </warning> |
| 975 | - |
| 976 | - <para> |
| 977 | - The <emphasis>'runcmd'</emphasis> commands are run at the same point in boot that the <emphasis>'#!'</emphasis> script would run in the previous example. |
| 978 | - It is present to allow you to get the full power of a scripting language if you need it without abandoning <emphasis>cloud-config</emphasis>. |
| 979 | - </para> |
| 980 | - |
| 981 | - <para> |
| 982 | - For more information on what kinds of things can be done with <application>cloud-config</application>, see |
| 983 | - <ulink url="http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/doc/examples/">doc/examples</ulink> in the source. |
| 984 | - </para> |
| 985 | - |
| 986 | - </sect3> |
| 987 | - |
| 988 | - </sect2> |
| 989 | - <sect2 id="uec-more-info" status="review"> |
| 990 | - <title>More Information</title> |
| 991 | - |
| 992 | - <para> |
| 993 | - How to use the <ulink url="https://help.ubuntu.com/community/UEC/StorageController">Storage Controller</ulink> |
| 994 | - </para> |
| 995 | - |
| 996 | - <para> |
| 997 | - Controlling eucalyptus services: |
| 998 | - </para> |
| 999 | - |
| 1000 | - <itemizedlist> |
| 1001 | - <listitem><para>sudo service eucalyptus [start|stop|restart] (on the CLC/CC/SC/Walrus side)</para></listitem> |
| 1002 | - <listitem><para>sudo service eucalyptus-nc [start|stop|restart] (on the Node side)</para></listitem> |
| 1003 | - </itemizedlist> |
| 1004 | - |
| 1005 | - <para> |
| 1006 | - Locations of some important files: |
| 1007 | - </para> |
| 1008 | - |
| 1009 | - <itemizedlist> |
| 1010 | - <listitem> |
| 1011 | - <para> |
| 1012 | - <emphasis>Log files:</emphasis> |
| 1013 | - </para> |
| 1014 | - <itemizedlist> |
| 1015 | - <listitem><para>/var/log/eucalyptus</para></listitem> |
| 1016 | - </itemizedlist> |
| 1017 | - </listitem> |
| 1018 | - <listitem> |
| 1019 | - <para> |
| 1020 | - <emphasis>Configuration files:</emphasis> |
| 1021 | - </para> |
| 1022 | - <itemizedlist> |
| 1023 | - <listitem><para>/etc/eucalyptus</para></listitem> |
| 1024 | - </itemizedlist> |
| 1025 | - </listitem> |
| 1026 | - <listitem> |
| 1027 | - <para> |
| 1028 | - <emphasis>Database:</emphasis> |
| 1029 | - </para> |
| 1030 | - <itemizedlist> |
| 1031 | - <listitem><para>/var/lib/eucalyptus/db</para></listitem> |
| 1032 | - </itemizedlist> |
| 1033 | - </listitem> |
| 1034 | - <listitem> |
| 1035 | - <para> |
| 1036 | - <emphasis>Keys:</emphasis> |
| 1037 | - </para> |
| 1038 | - <itemizedlist> |
| 1039 | - <listitem><para>/var/lib/eucalyptus</para></listitem> |
| 1040 | - <listitem><para>/var/lib/eucalyptus/.ssh</para></listitem> |
| 1041 | - </itemizedlist> |
| 1042 | - </listitem> |
| 1043 | - </itemizedlist> |
| 1044 | - |
| 1045 | - <note> |
| 1046 | - <para> |
| 1047 | - Don't forget to source your <filename>~/.euca/eucarc</filename> before running the client tools. |
| 1048 | - </para> |
| 1049 | - </note> |
| 1050 | - |
| 1051 | - </sect2> |
| 1052 | - <sect2 id="uec-references" status="review"> |
| 1053 | - <title>References</title> |
| 1054 | - |
| 1055 | - <itemizedlist> |
| 1056 | - <listitem> |
| 1057 | - <para> |
| 1058 | - For information on loading instances see the <ulink url="https://help.ubuntu.com/community/Eucalyptus">Eucalyptus Wiki</ulink> page. |
| 1059 | - </para> |
| 1060 | - </listitem> |
| 1061 | - <listitem> |
| 1062 | - <para> |
| 1063 | - <ulink url="http://open.eucalyptus.com/">Eucalyptus Project Site (forums, documentation, downloads)</ulink>. |
| 1064 | - </para> |
| 1065 | - </listitem> |
| 1066 | - <listitem> |
| 1067 | - <para> |
| 1068 | - <ulink url="https://launchpad.net/eucalyptus/">Eucalyptus on Launchpad (bugs, code)</ulink>. |
| 1069 | - </para> |
| 1070 | - </listitem> |
| 1071 | - <listitem> |
| 1072 | - <para> |
| 1073 | - <ulink url="http://open.eucalyptus.com/wiki/EucalyptusTroubleshooting_v1.5">Eucalyptus Troubleshooting (1.5)</ulink>. |
| 1074 | - </para> |
| 1075 | - </listitem> |
| 1076 | - <listitem> |
| 1077 | - <para> |
| 1078 | - <ulink url="http://support.rightscale.com/2._References/02-Cloud_Infrastructures/Eucalyptus/03-Administration_Guide/Register_with_RightScale"> |
| 1079 | - Register your cloud with RightScale</ulink>. |
| 1080 | - </para> |
| 1081 | - </listitem> |
| 1082 | - <listitem> |
| 1083 | - <para> |
| 1084 | - You can also find help in the <emphasis>#ubuntu-virt</emphasis>, <emphasis>#eucalyptus</emphasis>, and |
| 1085 | - <emphasis>#ubuntu-server</emphasis> IRC channels on <ulink url="http://freenode.net">Freenode</ulink>. |
| 1086 | - </para> |
| 1087 | - </listitem> |
| 1088 | - </itemizedlist> |
| 1089 | - |
| 1090 | - </sect2> |
| 1091 | - <sect2 id="uec-glossary" status="review"> |
| 1092 | - <title>Glossary</title> |
| 1093 | - |
| 1094 | - <para> |
| 1095 | - The Ubuntu Enterprise Cloud documentation uses terminology that might be unfamiliar to some readers. |
| 1096 | - This page is intended to provide a glossary of such terms and acronyms. |
| 1097 | - </para> |
| 1098 | - |
| 1099 | - <itemizedlist> |
| 1100 | - <listitem> |
| 1101 | - <para> |
| 1102 | - <emphasis>Cloud</emphasis> - A federated set of physical machines that offer computing resources through virtual machines, |
| 1103 | - provisioned and recollected dynamically. |
| 1104 | - </para> |
| 1105 | - </listitem> |
| 1106 | - <listitem> |
| 1107 | - <para> |
| 1108 | - <emphasis>Cloud Controller (CLC)</emphasis> - Eucalyptus component that provides the web UI (an https server on port 8443), |
| 1109 | - and implements the Amazon EC2 API. There should be only one Cloud Controller in an installation of UEC. This service is |
| 1110 | - provided by the Ubuntu <application>eucalyptus-cloud</application> package. |
| 1111 | - </para> |
| 1112 | - </listitem> |
| 1113 | - <listitem> |
| 1114 | - <para> |
| 1115 | - <emphasis>Cluster</emphasis> - A collection of nodes, associated with a Cluster Controller. There can be more than one |
| 1116 | - Cluster in an installation of UEC. Clusters are sometimes physically separate sets of nodes. (e.g. floor1, floor2, floor2). |
| 1117 | - </para> |
| 1118 | - </listitem> |
| 1119 | - <listitem> |
| 1120 | - <para> |
| 1121 | - <emphasis>Cluster Controller (CC)</emphasis> - Eucalyptus component that manages collections of node resources. |
| 1122 | - This service is provided by the Ubuntu <application>eucalyptus-cc</application> package. |
| 1123 | - </para> |
| 1124 | - </listitem> |
| 1125 | - <listitem> |
| 1126 | - <para> |
| 1127 | - <emphasis>EBS</emphasis> - Elastic Block Storage. |
| 1128 | - </para> |
| 1129 | - </listitem> |
| 1130 | - <listitem> |
| 1131 | - <para> |
| 1132 | - <emphasis>EC2</emphasis> - Elastic Compute Cloud. Amazon's pay-by-the-hour, pay-by-the-gigabyte public cloud computing offering. |
| 1133 | - </para> |
| 1134 | - </listitem> |
| 1135 | - <listitem> |
| 1136 | - <para> |
| 1137 | - <emphasis>EKI</emphasis> - Eucalyptus Kernel Image. |
| 1138 | - </para> |
| 1139 | - </listitem> |
| 1140 | - <listitem> |
| 1141 | - <para> |
| 1142 | - <emphasis>EMI</emphasis> - Eucalyptus Machine Image. |
| 1143 | - </para> |
| 1144 | - </listitem> |
| 1145 | - <listitem> |
| 1146 | - <para> |
| 1147 | - <emphasis>ERI</emphasis> - Eucalyptus Ramdisk Image. |
| 1148 | - </para> |
| 1149 | - </listitem> |
| 1150 | - <listitem> |
| 1151 | - <para> |
| 1152 | - <emphasis>Eucalyptus</emphasis> - Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems. |
| 1153 | - An open source project originally from the University of California at Santa Barbara, now supported by Eucalyptus Systems, |
| 1154 | - a Canonical Partner. |
| 1155 | - </para> |
| 1156 | - </listitem> |
| 1157 | - <listitem> |
| 1158 | - <para> |
| 1159 | - <emphasis>Front-end</emphasis> - Physical machine hosting one (or more) of the high level Eucalyptus components (cloud, |
| 1160 | - walrus, storage controller, cluster controller). |
| 1161 | - </para> |
| 1162 | - </listitem> |
| 1163 | - <listitem> |
| 1164 | - <para> |
| 1165 | - <emphasis>Node</emphasis> - A node is a physical machine that's capable of running virtual machines, running a node controller. |
| 1166 | - Within Ubuntu, this generally means that the CPU has VT extensions, and can run the KVM hypervisor. |
| 1167 | - </para> |
| 1168 | - </listitem> |
| 1169 | - <listitem> |
| 1170 | - <para> |
| 1171 | - <emphasis>Node Controller (NC)</emphasis> - Eucalyptus component that runs on nodes which host the virtual machines that comprise |
| 1172 | - the cloud. This service is provided by the Ubuntu package <application>eucalyptus-nc</application>. |
| 1173 | - </para> |
| 1174 | - </listitem> |
| 1175 | - <listitem> |
| 1176 | - <para> |
| 1177 | - <emphasis>S3</emphasis> - Simple Storage Service. Amazon's pay-by-the-gigabyte persistent storage solution for EC2. |
| 1178 | - </para> |
| 1179 | - </listitem> |
| 1180 | - <listitem> |
| 1181 | - <para> |
| 1182 | - <emphasis>Storage Controller (SC)</emphasis> - Eucalyptus component that manages dynamic block storage services (EBS). |
| 1183 | - Each 'cluster' in a Eucalyptus installation can have its own Storage Controller. This component is provided by the |
| 1184 | - <application>eucalyptus-sc</application> package. |
| 1185 | - </para> |
| 1186 | - </listitem> |
| 1187 | - <listitem> |
| 1188 | - <para> |
| 1189 | - <emphasis>UEC</emphasis> - Ubuntu Enterprise Cloud. Ubuntu's cloud computing solution, based on Eucalyptus. |
| 1190 | - </para> |
| 1191 | - </listitem> |
| 1192 | - <listitem> |
| 1193 | - <para> |
| 1194 | - <emphasis>VM</emphasis> - Virtual Machine. |
| 1195 | - </para> |
| 1196 | - </listitem> |
| 1197 | - <listitem> |
| 1198 | - <para> |
| 1199 | - <emphasis>VT</emphasis> - Virtualization Technology. An optional feature of some modern CPUs, allowing for accelerated virtual machine hosting. |
| 1200 | - </para> |
| 1201 | - </listitem> |
| 1202 | - <listitem> |
| 1203 | - <para> |
| 1204 | - <emphasis>Walrus</emphasis> - Eucalyptus component that implements the Amazon S3 API, used for storing VM images and user storage using |
| 1205 | - S3 bucket put/get abstractions. |
| 1206 | - </para> |
| 1207 | - </listitem> |
| 1208 | - </itemizedlist> |
| 1209 | - |
| 1210 | - </sect2> |
| 1211 | - </sect1> |
| 1212 | </chapter> |
Isn't UEC still in Universe? Rather than delete, maybe it should stay for people already using UEC that upgrade?