libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From to...@apache.org
Subject svn commit: r1457198 - /libcloud/site/trunk/content/docs/compute-deployment.mdtext
Date Sat, 16 Mar 2013 03:57:50 GMT
Author: tomaz
Date: Sat Mar 16 03:57:50 2013
New Revision: 1457198

URL: http://svn.apache.org/r1457198
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=1457198&r1=1457197&r2=1457198&view=diff
==============================================================================
--- libcloud/site/trunk/content/docs/compute-deployment.mdtext (original)
+++ libcloud/site/trunk/content/docs/compute-deployment.mdtext Sat Mar 16 03:57:50 2013
@@ -2,6 +2,8 @@ title: Compute -> Deployment
 
 ## Deployment ##
 
+*This functionality depends on the `paramiko` library which is not installed by default when
installing `apache-libcloud` package. You can be install it manually using pip - `pip install
paramiko`.*
+
 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 `create_node` and then after the node has been
@@ -13,9 +15,12 @@ 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 1: Deployment functionality depends on the `paramiko` library which can be installed
using pip - `pip install paramiko`.*
+### Provider Images and Default Usernames ###
+
+Libcloud uses `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 AWS AMI's,
`bitnatmi` for some Bitnami AWS AMI's, etc.).
 
-*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.
+This means deployment will fail if you don'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 ###
 
@@ -81,4 +86,4 @@ tool so it shouldn't be used as such.
                             ssh_username='ubuntu', ssh_key=key_path,
                             ex_keyname=key_name)
     # <Node: uuid=..., name=test, state=3, public_ip=['1.1.1.1'], provider=EC2 ...>
-    # the node is now booted, with puppet installed.
+    # the node is now booted, with puppet installed.
\ No newline at end of file



Mime
View raw message