151 | | server1.example.com |
152 | | server2.example.com |
153 | | }}} |
154 | | or |
155 | | {{{ |
156 | | server1.example.com ansible_ssh_host=10.0.0.1 |
157 | | server2.example.com ansible_ssh_host=10.0.0.2 |
158 | | }}} |
159 | | Create an Ansible Hosts file for your slice. An example is here: |
160 | | {{{ |
161 | | pc12.utahddc.geniracks.net |
162 | | savi-server ansible_ssh_host=142.150.208.146 |
163 | | }}} |
| 151 | [group_name] |
| 152 | server1_spec |
| 153 | server2_spec |
| 154 | }}} |
| 155 | where group_name is a name for a group of nodes, and a server spec contains login information for a node. An example of a server specification is |
| 156 | {{{ |
| 157 | savi_toronto ansible_ssh_host=142.150.208.146 ansible_ssh_port=22 ansible_ssh_user=rickmcg_geni ansible_ssh_private_key=~/.ssh/id_rsa |
| 158 | }}} |
| 159 | An example ansible hosts file for a slice is: |
| 160 | {{{ |
| 161 | [nodes] |
| 162 | pc1.geni.it.cornell.edu ansible_ssh_port=34874 ansible_ssh_user=jbourne ansible_ssh_key=~/.ssh/geni_key_portal |
| 163 | sav-toronto 142.150.208.149 ansible_ssh_user=ubuntu ansible_ssh_key=~/.ssh/savi-tutorial |
| 164 | }}} |
| 165 | Create an Ansible Hosts file for your slice. You can use either an IP address or an FQDN as an ssh host; if the ansible_ssh_host parameter is omitted it defaults to the name of the machine |