Author: tomaz
Date: Sat Mar 16 03:54:15 2013
New Revision: 1457197
URL: http://svn.apache.org/r1457197
Log:
CMS commit to libcloud by tomaz
Modified:
libcloud/site/trunk/content/docs/compute-deployment.mdtext
Modified: libcloud/site/trunk/content/docs/compute-deployment.mdtext
URL:
http://svn.apache.org/viewvc/libcloud/site/trunk/content/docs/compute-deployment.mdtext?rev=1457197&r1=1457196&r2=1457197&view=diff
==============================================================================
--- libcloud/site/trunk/content/docs/compute-deployment.mdtext (original)
+++ libcloud/site/trunk/content/docs/compute-deployment.mdtext Sat Mar 16
03:54:15 2013
@@ -13,7 +13,9 @@ We assume that a node has been fully sta
Keep in mind that Libcloud is not a replacement for a configuration management
tool so it shouldn't be used as such.
-*Note: Deployment functionality depends on the `paramiko` library which can be
installed using pip - `pip install paramiko`.*
+*Note 1: Deployment functionality depends on the `paramiko` library which can
be installed using pip - `pip install paramiko`.*
+
+*Note 2: Libcloud user `root` username when running a command on the remote
server. A lot of images use a different default username (e.g. `ubuntu` for
some ubuntu Amazon AMI's, etc.). This means deployment will fail if you won't
specify a correct username using the `ssh_username` keyword argument like it's
shown in the example 2.
### Example 1 - Deploying a Rackspace Node using password authentication and
installing your SSH key and Puppet on it ###
