BULK ON-BOARDING SERVERS
In this section, we will look into bulk on-boarding new servers into DivineCloud.
Please make sure you have read the On-boarding guide section first, before reading this sub-section.
If you need to on-board 10s or 100s of servers, than the fastest way to do that is using bulk import of nodes.
Figure below shows the Bulk Nodes Import Form:
Following node details fields are allowed for bulk import:
|ID||Node Display ID. Should be 5 alpha-numeric characters or less. Highly recommended but not required.|
|HOST or HOST:PORT||HOST IP Address. PORT number is optional. If not set will be set to 22.|
|NAME||Node Display Name.|
|CREDENTIALS_NAME||Node Credentials Name. The name should be the same one that was used when creating the node credentials.|
|TAGS||Comma separated list of Tag Names.|
|GROUP_PATH||Logical folder structure for organizing the nodes as per user's preference.|
|JUMP_HOST||IP address of the jump host. The Jump host should be part of the same batch when doing the bulk loading.|
|M||M stands for Multi-factor authentication. If the server requires multi-factor authentication, then this field should be set to M.|
Example data set for Bulk Node Import is shown below along with the screenshot:
192.168.1.4, Sample Server 1, rs_cred
192.168.2.1, Sample Server 2, rs_cred, APP_SERVER DB_SERVER
192.168.3.1, Sample Server 3, pwd_cred, APP_SERVER DB_SERVER, servers/backend
ID:SRV10, 192.168.1.45, Sample Server 10, rs_cred
ID:SRV20, 192.168.2.4, Sample Server 20, pwd_cred, APP_SERVER DB_SERVER
ID:SRV26, 192.168.2.6, Sample Server 26, pwd_cred, APP_SERVER DB_SERVER, servers/backend
Once all the nodes are added, it's a good idea to verify all the node information is correct, by, selecting the Inventory, and clicking on the Ping button located on the top of Inventory Panel, as shown in the figure below.