Skip to content

add clouds.yaml and update instructions for accessing ironic #791

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
russellb merged 1 commit into from
Sep 5, 2019
Merged

add clouds.yaml and update instructions for accessing ironic #791

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 19 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,26 +124,36 @@ master-2 Ready master 20m v1.12.4+50c2f2340a

## Interacting with Ironic directly

For manual debugging via openstackclient, you can use the following, noting that the IP address is that of the bootstrap VM which is ephemeral and won't be available once the masters have been deployed:
The dev-scripts repository contains a `clouds.yaml` file with
connection settings for both instances of Ironic. The copy of Ironic
that runs on the bootstrap node during installation can be accessed by
using the cloud name `metal3-bootstrap` and the copy running inside
the cluster once deployment is finished can be accessed by using the
cloud name `metal3`.

The openstack command line tool will look for `clouds.yaml` in the
current directory or you can copy it to
`~/.config/openstack/clouds.yaml`.

For manual debugging via the openstack client connecting to the bootstrap
VM, which is ephemeral and won't be available once the masters have
been deployed:

```
export OS_AUTH_TYPE=none
export OS_ENDPOINT=http://172.22.0.2:6385/
export OS_CLOUD=metal3-bootstrap
openstack baremetal node list
...
```

Note that the OS_ENDPOINT above refers to the provisioning network IP of the bootstrap VM, configured by `openshift-install` on the provisioning host. After the initial bootstrapping has completed this VM is destroyed, and Ironic services are started on the deployed cluster inside the baremetal operator.

To access this instance, update OS_ENDPOINT to the provisioning network IP on the master node that is running the baremetal-operator pod:
To access the Ironic instance running in the baremetal-operator pod:

```
export OS_AUTH_TYPE=none
export OS_ENDPOINT=http://172.22.0.3:6385
export OS_CLOUD=metal3
Copy link
Copy Markdown
Member

@dtantsur dtantsur Sep 6, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're not creating a metal3 cloud, are you? It's called metal3-test.

openstack baremetal node list
```

This references the provisioning network IP on the master node that is running the baremetal-operator pod.
NOTE: If you use a provisioning network other than the default, you
may need to modify the IP addresses used in

## Cleanup

Expand Down
9 changes: 9 additions & 0 deletions clouds.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
clouds:
metal3-bootstrap:
auth_type: none
baremetal_endpoint_override: http://172.22.0.2:6385
baremetal_introspection_endpoint_override: http://172.22.0.2:5050
metal3-test:
auth_type: none
baremetal_endpoint_override: http://172.22.0.3:6385
baremetal_introspection_endpoint_override: http://172.22.0.3:5050