You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! So I'm working on a PR that adds a Rax-specific example of this driver, and I've tripped over something. This driver uses servers#create which requires a named keypair already be created on the account.
Taking a survey of what other tools use to create nodes at Rackspace using fog, I found two different behaviors:
knife-rackspace uses passworded SSH with an optional ability to provide a key name, but you must create the key yourself (not unlike the requirement currently in chef-provisioning-fog)
It seems like the recommended 'fog best practice' way to bootstrap a Rackspace server using SSH keys is to use the bootstrap method, according to their docs. chef-provisioning-fog currently uses the create server method. I'm not sure this is an urgent fix, but I wanted to at least raise an issue so folks who try to do what I did are aware.
The text was updated successfully, but these errors were encountered:
martinb3
added a commit
to martinb3/chef-provisioning-rackspace-example
that referenced
this issue
Oct 4, 2015
Hey! So I'm working on a PR that adds a Rax-specific example of this driver, and I've tripped over something. This driver uses servers#create which requires a named keypair already be created on the account.
Taking a survey of what other tools use to create nodes at Rackspace using fog, I found two different behaviors:
I also found that the fog Rackspace compute v1 provider had a similar bootstrap implementation.
It seems like the recommended 'fog best practice' way to bootstrap a Rackspace server using SSH keys is to use the bootstrap method, according to their docs. chef-provisioning-fog currently uses the create server method. I'm not sure this is an urgent fix, but I wanted to at least raise an issue so folks who try to do what I did are aware.
The text was updated successfully, but these errors were encountered: