openstack/bifrost
Code Issues Proposed changes

Merge "Add README and Troubleshooting updates for SSH keys"

Browse Source
This commit is contained in:
Jenkins 2015-07-07 14:57:09 +00:00 committed by Gerrit Code Review
commit e4d58054bb
2 changed files with 34 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.rst
View File

@ -299,8 +299,11 @@ How this works?
After the nodes are enrolled, they can be deployed upon. Bifrost is geared to After the nodes are enrolled, they can be deployed upon. Bifrost is geared to
utilize configuration drives to convey basic configuration information to the utilize configuration drives to convey basic configuration information to the
each host. This case is the same between the newer deploy-dynamic.yaml each host. This configuration information includes an SSH key to allow a user
playbook and the older legacy deploy.yaml playbook. to login to the system.
This case is the same between the newer deploy-dynamic.yaml playbook and the
older legacy deploy.yaml playbook.
To utilize the newer dynamic inventory based deployment:: To utilize the newer dynamic inventory based deployment::

29
troubleshooting.rst
View File

@ -73,3 +73,32 @@ If you wish to SSH into the node in order to perform any sort of post-mortem, yo
2) You will need to short circuit the ironic conductor process. An ideal place to do so is in ironic/drivers/modules/agent.py in the reboot_to_instance method. Temporarily short circuiting this step will force you to edit the MySQL database if you wish to re-deploy the node, but the node should stay online after IPA has completed deployment. 2) You will need to short circuit the ironic conductor process. An ideal place to do so is in ironic/drivers/modules/agent.py in the reboot_to_instance method. Temporarily short circuiting this step will force you to edit the MySQL database if you wish to re-deploy the node, but the node should stay online after IPA has completed deployment.
3) ssh -l core <ip-address-of-node> 3) ssh -l core <ip-address-of-node>
********************************
ssh_public_key_path is not valid
********************************
Bifrost requires that the user who executes bifrost have an SSH key in
their user home, or that the user defines a variable to tell bifrost where
to identify this file. Once this variable is defined to a valid file, the
deployment playbook can be re-run.
Generating a new ssh key
========================
See the manual page for the ssh-keygen command.
Defining a specific public key file
===================================
A user can define a specific public key file by utilizing the
ssh_public_key_path variable. This can be set in the
group_vars/inventory/all file, or on the ansible-playbook command
line utilizing the -e command line parameter.
Example::
ansible-playbook -i inventory/bifrost_inventory.py deploy-dynamic.yaml -e ssh_public_key_path=~/path/to/public/key/id_rsa.pub
NOTE: The matching private key will need to be utilized to login to the
machine deployed.