Author: buildbot
Date: Sat Mar 16 03:58:00 2013
New Revision: 854691
Log:
Staging update by buildbot for libcloud
Modified:
websites/staging/libcloud/trunk/content/ (props changed)
websites/staging/libcloud/trunk/content/docs/compute-deployment.html
Propchange: websites/staging/libcloud/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Mar 16 03:58:00 2013
@@ -1 +1 @@
-1457197
+1457198
Modified: websites/staging/libcloud/trunk/content/docs/compute-deployment.html
==============================================================================
--- websites/staging/libcloud/trunk/content/docs/compute-deployment.html
(original)
+++ websites/staging/libcloud/trunk/content/docs/compute-deployment.html Sat
Mar 16 03:58:00 2013
@@ -95,6 +95,7 @@
<div id="main" class="span-16 last">
<h2 id="deployment">Deployment</h2>
+<p><em>This functionality depends on the <code>paramiko</code> library which
is not installed by default when installing <code>apache-libcloud</code>
package. You can be install it manually using pip - <code>pip install
paramiko</code>.</em></p>
<p>Deployment functionality allows you to create a node and after it has been
started install an SSH key and / or run arbitrary shell commands on it. It
works by first calling <code>create_node</code> and then after the node has
been
@@ -103,8 +104,10 @@ fully started SSHing into the node and r
<code>NodeState.RUNNING</code> and when it has a public IP address
assigned.</p>
<p>Keep in mind that Libcloud is not a replacement for a configuration
management
tool so it shouldn't be used as such.</p>
-<p><em>Note 1: Deployment functionality depends on the <code>paramiko</code>
library which can be installed using pip - <code>pip install
paramiko</code>.</em></p>
-<p>*Note 2: Libcloud user <code>root</code> username when running a command on
the remote server. A lot of images use a different default username (e.g.
<code>ubuntu</code> for some ubuntu Amazon AMI's, etc.). This means deployment
will fail if you won't specify a correct username using the
<code>ssh_username</code> keyword argument like it's shown in the example 2.</p>
+<h3 id="provider-images-and-default-usernames">Provider Images and Default
Usernames</h3>
+<p>Libcloud uses <code>root</code> username when running a command on the
remote server.
+A lot of images use a different default username (e.g. <code>ubuntu</code> for
some ubuntu AWS AMI's, <code>bitnatmi</code> for some Bitnami AWS AMI's,
etc.).</p>
+<p>This means deployment will fail if you don't specify a correct username
using the <code>ssh_username</code> keyword argument like it's shown in the
example 2.</p>
<h3
id="example-1-deploying-a-rackspace-node-using-password-authentication-and-installing-your-ssh-key-and-puppet-on-it">Example
1 - Deploying a Rackspace Node using password authentication and installing
your SSH key and Puppet on it</h3>
<div class="codehilite"><pre><span class="kn">from</span> <span
class="nn">libcloud.compute.types</span> <span class="kn">import</span> <span
class="n">Provider</span>
<span class="kn">from</span> <span
class="nn">libcloud.compute.providers</span> <span class="kn">import</span>
<span class="n">get_driver</span>
