Manual bulk server discovery is useful if you do not want to use automatic DHCP discovery. You can create a .yaml file containing a list of servers for Bare Metal Orchestrator to discover and onboard.
For each server you want to add, enter the following details in the cred.yaml file:
- Server name and labels
- BMC endpoint IP address
- BMC username
- BMC password
The BMC endpoint must be in http(s)://<IP address> format. Separate the details of each server with three dashes (---). To create servers, see Create a server or multiple servers and update configurations.
The following example cred.yaml file lists two servers for manual bulk discovery.
apiVersion: mw.dell.com/v4
kind: Server
metadata:
name: dell-r740-71
labels:
site: sclara
spec:
# Add fields here
bmcEndPoint: "https://<BMC-IP>"
userName: ""
password: ""
---
apiVersion: mw.dell.com/v4
kind: Server
metadata:
name: dell-r6515-05
labels:
site: sclara
spec:
# Add fields here
bmcEndPoint: "https://<BMC-IP>"
userName: ""
password: ""
Server profile YAML files can have empty userName
and password
attributes. If the attributes are empty, Bare Metal Orchestrator checks the default credentials in the default cred.yaml file in a trial and error method in an attempt to connect to a server, onboard it, and get its inventory. For more information about the default cred.yaml file, see Default credentials for device discovery.
If Bare Metal Orchestrator cannot find a matching set of credentials to connect to a server and the default credentials also do no work, the server is labeled as unable to onboard and the moved to a failed state.
userName
and password
fields must be blank for manual server discovery to work.