facilitates the migration of servers without disrupting the existing workload or services.
The managed
flag needs to be set as false
.
By default, it is set as true
indicating that the server is managed by .
Once the server is onboarded, all tasks such as editing server configuration, viewing server inventory, deleting servers and so on can be performed.
- Establish a CLI session on the Bare Metal Orchestrator VM and log in. For high availability configurations, establish a CLI session using the virtual IP (VIP) of the Load Balancers for the Bare Metal Orchestrator cluster.
- Edit the <server-id>.yaml file with Vim or a similar editor.
For example:
vim dell_server.yaml
- Configure the managed flag as false. For attribute definitions, see Brownfield server onboarding attribute definition.
Optional: Add the installedOsConfig details. For more information about configuring OS inventory, see OS inventory attribute definition
---
apiVersion: mw.dell.com/v4
kind: Server
metadata:
name: dell-os-inventory
labels:
model: dell
site: gc
spec:
# Add fields here
bmcEndPoint: "https://1.2.3.4"
userName: root
password: "REPLACE_THIS"
managed: false
installedOsConfig:
osIP: "1.2.3.5"
userName: root
password: "REPLACE_THIS" - Save the file and quit the editor.
- Create the server instance. Run the following command.
bmo create server -f <new-server-id>.yaml
For example:
When thebmo create server -f dell_server_new.yaml
Provisioning Status
transitions fromBusy
toReady
state, the server configuration is successful.Note:- If the server IP is not accessible, then the server enters into an OS inventory failed state. You need to check and resolve any IP connectivity issues.
- Bulk onboarding, DHCP onboarding, and onboarding through hardware profile of servers are not supported. To discover multiple devices with a CSV file - bulk discovery, see Bare Metal Orchestrator Web User Interface Guide.
- While onboarding a server, if an invalid user name is provided and the
managed
flag is set asfalse
, the server enters into the Failed state. To recover the server, you need to delete the server and create it again by updating correct credentials in the server specifications. - If
installedOsConfig
details are provided andPasswordAuthentication
is set as no, then the server onboarding fails. - When onboarding a brownfield server from one instance to another , ensure that the server is in
READY
state in the older instance and no critical operations are in progress.
- To continue with further provisioning of the server, configure the managed flag as
true
using command:bmo edit server -f <server-id>.yaml
The normal onboarding process with initialization and reconciliation will continue. If the managed flag is
false
, initialization and reconciliation are not triggered.