b85688864f
* Group all topics related to other services under one heading * Move multitenancy configuration to the install-guide * Remove useless page on configuring port groups * Fix titles to be more consistent (e.g. when talking about services) * Use separate pages instead of includes. * Move deploy ramdisk section up, as it's used in enrollment Change-Id: I675d201b0acf1cf3acb4eafeafb8eb9628fd10f5
3.9 KiB
Configure the Identity service for the Bare Metal service
Create the Bare Metal service user (for example,
ironic). The service uses this to authenticate with the Identity service. Use theservicetenant and give the user theadminrole:$ openstack user create --password IRONIC_PASSWORD \ --email ironic@example.com ironic $ openstack role add --project service --user ironic adminYou must register the Bare Metal service with the Identity service so that other OpenStack services can locate it. To register the service:
$ openstack service create --name ironic --description \ "Ironic baremetal provisioning service" baremetalUse the
idproperty that is returned from the Identity service when registering the service (above), to create the endpoint, and replaceIRONIC_NODEwith your Bare Metal service's API node:$ openstack endpoint create --region RegionOne \ baremetal admin http://$IRONIC_NODE:6385 $ openstack endpoint create --region RegionOne \ baremetal public http://$IRONIC_NODE:6385 $ openstack endpoint create --region RegionOne \ baremetal internal http://$IRONIC_NODE:6385If only keystone v2 API is available, use this command instead:
$ openstack endpoint create --region RegionOne \ --publicurl http://$IRONIC_NODE:6385 \ --internalurl http://$IRONIC_NODE:6385 \ --adminurl http://$IRONIC_NODE:6385 \ baremetalYou may delegate limited privileges related to the Bare Metal service to your Users by creating Roles with the OpenStack Identity service. By default, the Bare Metal service expects the "baremetal_admin" and "baremetal_observer" Roles to exist, in addition to the default "admin" Role. There is no negative consequence if you choose not to create these Roles. They can be created with the following commands:
$ openstack role create baremetal_admin $ openstack role create baremetal_observerIf you choose to customize the names of Roles used with the Bare Metal service, do so by changing the "is_member", "is_observer", and "is_admin" policy settings in
/etc/ironic/policy.json.More complete documentation on managing Users and Roles within your OpenStack deployment are outside the scope of this document, but may be found here.
You can further restrict access to the Bare Metal service by creating a separate "baremetal" Project, so that Bare Metal resources (Nodes, Ports, etc) are only accessible to members of this Project:
$ openstack project create baremetalAt this point, you may grant read-only access to the Bare Metal service API without granting any other access by issuing the following commands:
$ openstack user create \ --domain default --project-domain default --project baremetal \ --password PASSWORD USERNAME $ openstack role add \ --user-domain default --project-domain default --project baremetal \ --user USERNAME baremetal_observerFurther documentation is available elsewhere for the
openstackcommand-line client and the Identity service. A policy.json.sample file, which enumerates the service's default policies, is provided for your convenience with the Bare Metal Service.