Installing the Triton head node

Modified: 22 Nov 2017 17:37 UTC

When Triton DataCenter is installed, the configuration program prompts for values to configure the system. This page explains the guided configuration process which will use the values defined in the earlier sections of this guide. If you have not already read through them, please review the previous steps at Installing Triton DataCenter.

Initial boot

Insert the USB key containing the installation media into a USB port. As mentioned previously, it is strongly recommended to use an internal port for the USB key to reduce the risk of it being unseated from the port.

Boot the head node from the USB key.

By default, Triton will use the second serial port for it's SOL console. This can be changed at the GRUB menu by setting the os_console variable:

  1. Scroll down to the Live 64 Bit menu option.
  2. Press the c key to open a command window.
  3. Enter one of the following:

    Console Device Details Command
    ttya First serial port variable os_console ttya
    ttyb Second serial port (default) variable os_console ttyb
    ttyc Third serial port variable os_console ttyc
    vga VGA + Keyboard variable os_console vga
  4. Press enter after entering the command.
  5. Press escape to return to the main menu.

At the Grub Menu select Live 64 Bit and boot.

Triton Installer

Once the system has booted, the Triton installation program starts automatically and will ask a series of questions that are used to generate the configuration file used for installation.

The configuration of general variables uses information collected in Triton deployment planning.

```
Smart Data Center (SDC) Setup
Data Center Information                       http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------
The following questions will be used to configure your headnode identity.
This identity information is used to uniquely identify your headnode as well
as help with management of distributed systems.

The data center *region* and *name* will be used in DNS names. Typically
the region will be a part of data center name, e.g. region_name=us-west,
datacenter_name=us-west-1, but this isn't required.
```

| Entry          | Description                     | Examples
| :----          | :----                           | :----
| company name   | The name of your company.| `Acme, Inc.` <br /> `Massive Dynamics` <br /> `Communications Division` |
| data center region | The region the data center is in.| `us-west` <br /> `us-east` <br /> `eu-central` |
| data center name | The name of your data center. Do not use spaces or uppercase. This describes the collection of systems that will be handled by the head node. | `us-west-1` <br /> `myregion-2`
| City and State | The location of your data center. This information is used only to identify the location.| `San Francisco, CA` <br /> `Mexico, DF`  <br /> `Building 7`

The configuration of Admin networking variables uses information collected in Triton initial network configuration.

```
Smart Data Center (SDC) Setup
Networking                                   http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------
Several applications will be made available on these networks using IP
addresses which are automatically incremented based on the headnode IP.
In order to determine what IP addresses have been assigned to SDC, you can
either review the configuration prior to its application, or you can run
'sdc-netinfo' after the install.

Press [enter] to continue
```

```
Smart Data Center (SDC) Setup
Networking - Admin                           http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------
The admin network is used for management traffic and other information that
flows between the Compute Nodes and the headnode in an SDC cluster. This
network will be used to automatically provision new compute nodes and there are
several application zones which are assigned sequential IP addresses on this
network. It is important that this network be used exclusively for SDC
management. Note that DHCP traffic will be present on this network following
the installation and that this network is connected in VLAN ACCESS mode only.

Number Link      MAC Address        State   Network
1      bnx0      78:2b:cb:0a:77:e1  up      -
2      bnx2      78:2b:cb:0a:77:e5  down    -
3      bnx1      78:2b:cb:0a:77:e3  down    -
4      bnx3      78:2b:cb:0a:77:e7  down    -
5      igb0      00:1b:21:91:a5:e0  unknown -
6      igb2      00:1b:21:91:95:20  unknown -
7      igb1      00:1b:21:91:a5:e1  unknown -
8      igb3      00:1b:21:91:95:21  unknown -
Enter the number of the NIC for the *admin* interface: 1
(admin) headnode IP address: 10.0.3.7
(admin) headnode netmask [255.255.255.0]:
(admin) Zone's starting IP address [10.0.3.8]:
```

Configuration of External networking variables uses information collected in Triton initial network configuration.

```
Smart Data Center (SDC) Setup
Networking - External                        http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------
The external network is used by the headnode and its applications to connect to
external networks. That is, it can be used to communicate with either the
Internet, an intranet, or any other WAN. This is optional when your system does
not need access to an external network, or where you want to connect to an
external network later.

Add external network now? [Y/n]:
Number Link      MAC Address        State   Network
1      bnx0      78:2b:cb:0a:77:e1  up      *admin*
2      bnx2      78:2b:cb:0a:77:e5  down    -
3      bnx1      78:2b:cb:0a:77:e3  down    -
4      bnx3      78:2b:cb:0a:77:e7  down    -
5      igb0      00:1b:21:91:a5:e0  unknown -
6      igb2      00:1b:21:91:95:20  unknown -
7      igb1      00:1b:21:91:a5:e1  unknown -
8      igb3      00:1b:21:91:95:21  unknown -
Enter the number of the NIC for the *external* interface: 5
(external) headnode IP address: 151.1.224.130
(external) headnode netmask [255.255.255.0]: 255.255.255.192
(external) gateway IP address: 151.1.224.129
(external) VLAN ID [press enter for none]: 102
Starting provisionable IP address [151.1.224.131]:
Ending provisionable IP address [151.1.224.190]:
```

- **Note** if there is only one interface, it will skip the printing and prompting for the interface.

| Entry               | Description                  | Examples
| :----               | :----                        | :----
| number of NIC for the *external* interface | The number of the NIC in the list of NICs. Each NIC is identified by its MAC address and its interface number. | Choose the number of the NIC that is connected to the external network.
| (external) headnode IP address | The IP address of the head  node on the external network. | `151.1.224.7`
| (external) headnode netmask | The netmask that describes the address space of the external network. | `255.255.255.0`
| (external) VLAN ID [press enter for none]: | If your external network uses VLANs, provided its number here. | Press [enter] for no VLAN, otherwise and integer from 1 to 4095
| Starting provisionable IP address []:| The first available IP address to assign to a newly provisioned instance. This address must be in the network defined by the external network IP address and the external netmask.  | `10.88.88.50`
| Ending provisionable IP address []: | The last available IP address to assign to a newly provisioned instance. This address mus be in the network defined by the external network IP address and the external netmask. | `10.88.88.254`

The default gateway determines which network the head node zones use to connect to outside networks.

```
Smart Data Center (SDC) Setup
Networking - Continued                       http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------
The default gateway will determine which router will be used to connect to
other networks. This will almost certainly be the router connected to your
'External' network. Use 'none' if you have no gateway.

Enter the default gateway IP [151.1.224.129]:

The DNS servers set here will be used to provide name resolution abilities to
the SDC cluster itself. These will also be default DNS servers for zones
provisioned on the 'external' network.

Enter the Primary DNS server IP [8.8.8.8]:
Checking connectivity...OK
Enter the Secondary DNS server IP [8.8.4.4]:
Checking connectivity...OK
Enter the headnode domain name: joyent.us
Default DNS search domain: joyent.com

By default the headnode acts as an NTP server for the admin network. You can
set the headnode to be an NTP client to synchronize to another NTP server.
Enter an NTP server IP address or hostname [0.smartos.pool.ntp.org]:
Checking 0.smartos.pool.ntp.org connectivity...OK
```

Configuration of general variables uses information collected in Triton deployment planning.

```
Smart Data Center (SDC) Setup
Account Information                          http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------
There are two primary accounts for managing a Smart Data Center.  These are
'admin', and 'root'. Each account can have a unique password. Most of the
interaction you will have with SDC will be using the 'admin' user, unless
otherwise specified.  In addition, SDC has the ability to send notification
emails to a specific address. Each of these values will be configured below.

Enter root password:
Confirm password:
Enter admin password:
Confirm password:
Administrator email goes to [root@localhost]:
Support email should appear from [support@joyent.us]:
```

| Entry                  | Description                  | Examples
| :----                  | :----                        | :----
| root password          | The password used to access the `root` account on the head node and compute nodes. | `swordfish`
| admin password         | The password used to access  the `admin` account. | `your_dogs_name`
| Administrator email goes to   | The address that receives administrator mail. | `admin@example.com`
| Support email should appear from | The "From" address for mail generated by SDC. | `support@example.com`

```
Smart Data Center (SDC) Setup
Verify Configuration                         http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------

Share usage, health, and hardware data about your data center with
Joyent to help us make SmartDataCenter better.

Enable telemetry [false]:
```

After the configuration program runs, it gives a summary of all the entries made and asks for confirmation that they are correct.

```
Smart Data Center (SDC) Setup
Verify Configuration                         http://docs.joyent.com/sdc7
--------------------------------------------------------------------------------
Company name: Joyent Inc.
Datacenter Region: eu-central, Name: eu-central-1, Location: Milano, IT
Email Admin Address: root@localhost, From: support@joyent.us
Domain name: joyent.us, Gateway IP address: 151.1.224.129
    Net               MAC        IP addr.         Netmask         Gateway VLAN
Admin 78:2b:cb:0a:77:e1        10.0.3.7   255.255.255.0            none none
External 00:1b:21:91:a5:e0   151.1.224.130 255.255.255.192   151.1.224.129  102

Admin net zone IP addresses start at: 10.0.3.8
Provisionable IP range: 151.1.224.131 - 151.1.224.190
DNS Servers: (8.8.8.8, 8.8.4.4), Search Domain: joyent.com
NTP servers: 151.1.135.200

Is this correct? [y]:

Your configuration is about to be applied.
Would you like to edit the final configuration file? [n]:
```

| Entry                            | Description
| :----                            | :----
| Is this correct?                 | Answer 'no'and the installer configuration program runs again, using the previous entries as defaults. Answer 'yes' and the following question will be displayed.
| Would you like to edit the final configuration file? | If you answer 'no', the configuration program ends and head node setup begins. If you answer 'yes', the configuration program is first loaded into a vi editor, which when quit, then setup will begin. You must select this option if you are configuring link aggregation for the head node.

These instructions explain how to configure the Triton head node to use link aggregation. If link aggregation is not being used for the head node, this step can be skipped.

Adding link aggregation to the head node currently requires the editing of the configuration file; a future update to the installer will render this step unnecessary. Additionally, it assumes that an answer of Y to the Would you like to edit the final configuration file? question in the installer process.

Once you have made your changes, save the file and quit the editor.

Adding link aggregation to the head node post-setup

Please note is it possible to add link aggregation post-setup; in order to do this, you will need to mount the USB key and edit the configuration file directly:

Mount the USB key using

headnode# sdc-usbkey mount

Bring up the config file in the editor

headnode#  vi /mnt/usbkey/config

Exit the editor.

Unmount the USB key.

headnode# sdc-usbkey unmount

Reboot the head node.

headnode# reboot

Once the head node reboots the aggregate bundles will be active.

Setup and reboots

Once you have finished the installation steps, the head node will reboot in order to apply your configuration to the head node.

The headnode will now finish configuration and reboot. Please wait...
2014-02-17T15:26:28.853517+00:00 headnode rsyslogd3: No files configured to be monitored [try http://www.rsyslog.com/e/-3 ]
2014-02-17T15:26:28.855293+00:00 headnode genunix: [ID 540533 kern.notice] #015SunOS Release 5.11 Version joyent_20150820-20150829T195911Z 64-bit
2014-02-17T15:26:28.855307+00:00 headnode genunix: [ID 588371 kern.notice] Copyright (c) 2010-2014, Joyent Inc. All rights reserved.
2014-02-17T15:26:28.855517+00:00 headnode acpica: [ID 361365 kern.notice] ACPI: RSDP f11a0 00024 (v2 DELL  )
2014-02-17T15:26:28.855522+00:00 headnode acpica: [ID 135650 kern.notice] ACPI: XSDT f12a4 0009C (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855528+00:00 headnode acpica: [ID 473354 kern.notice] ACPI: FACP 7f3b3f9c 000F4 (v3 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855534+00:00 headnode acpica: [ID 836996 kern.notice] ACPI: DSDT 7f38f000 03D72 (v1 DELL   PE_SC3   00000001 INTL 20050624)
2014-02-17T15:26:28.855540+00:00 headnode acpica: [ID 871577 kern.notice] ACPI: FACS 7f3b6000 00040
2014-02-17T15:26:28.855546+00:00 headnode acpica: [ID 233916 kern.notice] ACPI: APIC 7f3b3478 0015E (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855552+00:00 headnode acpica: [ID 218462 kern.notice] ACPI: SPCR 7f3b35d8 00050 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855558+00:00 headnode acpica: [ID 358574 kern.notice] ACPI: HPET 7f3b362c 00038 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855564+00:00 headnode acpica: [ID 558911 kern.notice] ACPI: DMAR 7f3b3668 001C0 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855570+00:00 headnode acpica: [ID 848976 kern.notice] ACPI: MCFG 7f3b38c4 0003C (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855580+00:00 headnode acpica: [ID 423410 kern.notice] ACPI: WD__ 7f3b3904 00134 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855587+00:00 headnode acpica: [ID 819069 kern.notice] ACPI: SLIC 7f3b3a3c 00024 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855594+00:00 headnode acpica: [ID 340909 kern.notice] ACPI: ERST 7f392ef4 00270 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855600+00:00 headnode acpica: [ID 652589 kern.notice] ACPI: HEST 7f393164 003A8 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855612+00:00 headnode acpica: [ID 301466 kern.notice] ACPI: BERT 7f392d74 00030 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855624+00:00 headnode acpica: [ID 500178 kern.notice] ACPI: EINJ 7f392da4 00150 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855636+00:00 headnode acpica: [ID 404043 kern.notice] ACPI: SRAT 7f3b3bc0 00370 (v1 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855644+00:00 headnode acpica: [ID 777293 kern.notice] ACPI: TCPA 7f3b3f34 00064 (v2 DELL   PE_SC3   00000001 DELL 00000001)
2014-02-17T15:26:28.855660+00:00 headnode acpica: [ID 797947 kern.notice] ACPI: SSDT 7f3b7000 03E04 (v1  INTEL PPM RCM  80000001 INTL 20061109)
2014-02-17T15:26:28+00:00 headnode savecore: [ID 467324 auth.error] open(""): No such file or directory
2014-02-17T15:26:28+00:00 headnode savecore: [ID 467324 auth.error] open(""): No such file or directory
             _____
          ____   ____
         _____   _____        .                   .
         __         __        | .-. .  . .-. :--. |-
         _____   _____        ;|   ||  |(.-' |  | |
          ____   ____     `--'  `-' `;-| `-' '  ' `-'
             _____                  /  ; Joyent Live Image v0.147+
                                    `-'   build: 20150820T062843Z

headnode ttyb login:
creating pool: zones                                    done
adding volume: dump                                     done
adding volume: config                                   done
adding volume: usbkey                                   done
adding volume: cores                                    done
adding volume: opt                                      done
adding volume: var                                      done
adding volume: swap                                     done

The ...headnode acpica... messages are hardware dependent and may not appear on your systems.

There will be a pause of several minutes at this point as data is read off the USB key.

The head node will then reboot and commences set up of the Triton software and services. This process takes between 10 and 20 minutes. During this time you will see messages as the core service zones are imported and the zones are created.

SunOS Release 5.11 Version joyent_20150820-20150829T195911Z 64-bit
Copyright (c) 2010-2014, Joyent Inc. All rights reserved.

             _____
          ____   ____
         _____   _____        .                   .
         __         __        | .-. .  . .-. :--. |-
         _____   _____        ;|   ||  |(.-' |  | |
          ____   ____     `--'  `-' `;-| `-' '  ' `-'
             _____                  /  ; Joyent Live Image v0.147+
                                    `-'   build: 20150820T062843Z
              --> Welcome to SDC7! <--
preparing for setup...                                    done (0s)
installing tools to /opt/smartdc/bin...                   done (0s)
installing sdcadm                                         done (3s)
installing agents-master-20150820-20150829t073457z-g77ec6fd.sh...  done (92s)
importing: assets-zfs-master-20150820-20150829t194437z-g1dc8d46    done (58s)
creating zone assets...                                   done (11s)
importing: sapi-zfs-master-20150820-20150829t200202z-g56a7eec      done (4s)
creating zone sapi...                                     done (11s)
importing: binder-zfs-master-20150820-20150829t230454z-gd954fc2    done (7s)
creating zone binder...                                   done (14s)
importing: manatee-zfs-master-20150820-20150829t222942z-gdd0afa6   done (8s)
creating zone manatee...                                  done (18s)

...snip...

creating zone fwapi...                                    done (14s)
importing: vmapi-zfs-master-20150820-20150829t001019z-gedd83f7     done (4s)
creating zone vmapi...                                    done (14s)
importing: ca-zfs-master-20150820-20150829t194052z-gd39e0d0        done (5s)
creating zone ca...                                       done (22s)
importing: adminui-zfs-master-20150820-20150829t171315z-g5fd1444   done (4s)
creating zone adminui...                                  done (21s)
completing setup...                                       done (84s)

==> Setup complete (in 723 seconds). Press [enter] to get login prompt.

At this point you can press the [enter] key and log into the head node.

Adding external access to adminui and imgapi

The final step in the initial head node installation and configuration is to add external access to the adminui and imgapi core service zones.

Adding an external NIC to the adminui zone allows access to the operator portal from the external network. The addition of an external NIC to the imgapi zone allows for downloading of images from the Joyent update servers.

The process of adding these interfaces is accomplished by using the sdcadm post-setup command as shown below:

headnode# sdcadm post-setup common-external-nics

Once this command completes, you will need to note the IP address that has been assigned to the adminui service in order to connect to the Operations Portal. This can be gathered by running the command below:

headnode# sdc-vmadm ips -p $(sdc-vmname adminui)

Adding the cloudapi core service zone

In order to use either the smartdc or triton you will need to install the cloudapi zone. Additionally, this is required if you will be running the end-user portal.

The creation of this zone is accomplished via the sdcadm post-setup shown below:

headnode# sdcadm post-setup cloudapi

Once this command completes, you will need to note the IP address that has been assigned to the cloudapi service in order to connect to the correct API endpoint. This can be gathered by running the command below:

headnode# sdc-vmadm ips -p $(sdc-vmname cloudapi)

Adding proxy support to Triton

Triton supports the use of both authenticated and unauthenticated proxies; please see Configuring Triton to use a proxy for setup details.

Linking Triton data centers

Triton supports UFDS linking, which allows two data center to share key user data, including ssh keys, passwords, and RBAC information. UFDS or Data Center Linking must be done after installing the head node in second and subsequent Triton Installations; to link two data centers, please follow the instructions at Linking Triton data centers.

Important notes: