Bare Metal Orchestrator generates events that help you to respond to state changes in the Bare Metal Orchestrator resources. An event could be a create, update, or delete operation, a resource life-cycle state change, or a system event impacting a resource.
A BMO event can be a successful execution of an operation or a failed operation. Error codes are part of the Bare Metal Orchestrator logs and error messages.
Events with descriptive error messages and error codes are generated when there is a failure in Bare Metal Orchestrator operations. The event message includes an actual error string and resolution that helps you to troubleshoot a failed Bare Metal Orchestrator operation. In applicable cases, HTTPStatusCode
and ManagedElementErrorCode
are also included.
In a success scenario, the event messages, Busy for running operation
and Ready after completing
appear without any error codes.
For example, the following event is generated for an Initialization success scenario:
s1 status changed: Busy for running operation: Initialize
s1 status changed to: Ready after completing: Initialize
In a failure scenario, an event is generated with failure specific error code and error message. For a list of error codes with descriptions, see Bare Metal Orchestrator error codes.
Add tab test continuous loop animated GIF
Add tab test 4x loop animated GIF
Add tab test no loop animated GIF
Create and manage tenants
Ensure sites are created for your Bare Metal Orchestrator cluster. For example, you could create a different site for each geographical region in the cluster. | |
Create a user with a user YAML file Operator users can access the tenants to which they are assigned as a Tenant Admin. Global Admins and Global Readers can access all tenants in a multi-tenant setup. For more information about user roles, see Identity and access management overview. | |
You can have different regional sites defined as separate tenants. Specific Operator users (one or more than one?) can be assigned as a Tenant Admin during tenant creation. For more information about multi-tenancy, see Multi-tenancy overview. | |
After the tenant is created, you can assign users and roles. | |
You are done! Optionally, proceed to manage your tenants. |
Create and manage tenants
Ensure sites are created for your Bare Metal Orchestrator cluster. For example, you could create a different site for each geographical region in the cluster. | |
Create a user with a user YAML file Operator users can access the tenants to which they are assigned as a Tenant Admin. Global Admins and Global Readers can access all tenants in a multi-tenant setup. For more information about user roles, see Identity and access management overview. | |
You can have different regional sites defined as separate tenants. Specific Operator users (one or more than one?) can be assigned as a Tenant Admin during tenant creation. For more information about multi-tenancy, see Multi-tenancy overview. | |
After the tenant is created, you can assign users and roles. | |
You are done! Optionally, proceed to manage your tenants. |