Creating a node
A node represents a baremetal host on the SC//Reliant™ platform. When you create a new node, you specify a node group which defines the settings for the node. For more information about node groups, see Node Groups.
Creating a new node
- Access and log in to the SC//Reliant Platform Manager at https://platform.reliant.io/.
- From the left navigation menu, choose Nodes.
- On the Nodes page, choose Actions, + New Node.
- Complete the node fields. Group and Node Number are required; all other fields are optional. See the node property reference below.
- Verify the values and then choose Save to create the node.
Node property reference
The properties available on a node are defined by the Node Group you associate with it. The table below lists the base fields set directly on a node. Beyond those, a node group's Node Properties setting selects which additional properties are exposed on the nodes in that group, for example Cluster Docker Resources, Activation Date, Bridge0 Ip, and Network Configurations. When you choose a node group while creating a node, the form displays the additional properties defined by that group so you can set values specific to this node.
Because of this, the typical workflow is:
- Create the node group and select the Node Properties it should expose. See Creating a node group and the Node group property reference.
- Create the node and associate it with that node group. The node inherits the group's settings, and the node form shows the group's node properties so you can set node-specific values.
The following table describes the base node fields.
| Field | Description | Required |
|---|---|---|
| Group | The node group assigned to this node. The node group defines the settings for the node. | Yes |
| Node Number | Typically associated with the store location. In all cases, it is used to create a unique node hostname. | Yes |
| Node Name | The node alias. | No |
| Instance Number | Represents the number of nodes in a given edge location (or store). For clustered nodes, 0 or 1 are the required values. Defaults to 0. | No |
| Serial Number | Commonly provided by the device manufacturer and configured in BIOS. Used to bootstrap the node during the build. | No |
| Puppet Environment | The code branch used for Puppet agent runs. When left blank, the default value is Production. | No |
| Masterless Puppet | Enables Puppet to run in masterless mode (Enabled or Disabled). Before enabling this option, ensure that all prerequisites are met. | No |
| Level of Hierarchy | Assigns attribute definitions to nodes or virtual nodes in a tree-like fashion, which allows certain tasks to be performed or the ability to categorize nodes. | No |
| Type Of Server | The type of server this node is. | No |
| RJE Environment | Designates the set of Remote Job Execution (RJE) certificates and middleware infrastructure to use. Typically left blank. | No |
| Available Docker Images | A read-only list of the Docker images available to the node. | No |
| DNS | The DNS configuration hash. Hash properties become editable after the node is created. | No |
| DNS Alt Names | Alternate names for Puppet's SSL script, typically set to puppet for puppet and build servers. | No |
| Hostip Puppet | The DHCP setting or IP address of the Puppet server. | No |
| Hostip PuppetCA | The DHCP setting or IP address of the Puppet CA. | No |
| Hostname Puppet | The hostname of the puppetserver. | No |
| Hostname PuppetCA | The hostname of the Puppet CA. | No |
| Puppetserver Configurations | The puppetserver configuration hash. Hash properties become editable after the node is created. | No |
| Puppet profiles | The Puppet profiles to be used. | No |
Note: Hash properties (such as DNS and Puppetserver Configurations) are editable only after the node is created.