On Apr 9, 2010, at 9:13 AM, [email protected] wrote:
> Thanks Jerry. [2] references using ssh keys, but unless I'm mistaken,
> new Rackspace nodes don't have any non-password ssh access or a known
> key (at least Fedora 11 doesn't - maybe the other flavors do?).
Indeed you are correct -- I wasn't suggesting that specific solution but that
post just came to mind as far as deployment goes.
> My
> current Rackspace "automation" is to read the password out of the
> email that Rackspace sends, and use Pexpect to login with that
> password and transfer my ssh keys & authorized_keys files. (It's
> kinda brittle; e.g. Rackspace changed the format of their email
> recently.)
Scraping is never fun. However the good news is for Rackspace, you should be
able to retrieve the password upon creation; in test/test_rackspace.py,
test_create_node() has:
node = self.driver.create_node(name='racktest', image=image, size=size)
self.assertEqual(node.extra.get('password'), 'racktestvJq7d3')
...so you should be able to retrieve the password through node.extra.get().
> For amazon node creation, I've been using the boto library
> — it works well. I hope libcloud driver is able to expose that PUT
> method to change the password sometime.
To add a request, you can hit up JIRA [3] (with or without a patch).
> Thanks again to the libcloud team for this new project - I'll be
> watching it closely!
Feel free to drop by IRC, #libcloud on Freenode.
[3] https://issues.apache.org/jira/browse/LIBCLOUD
Cheers,
Jerry
