Step A: Gather Information - AWS Elemental Delta

This is version 2.3 of the AWS Elemental Delta documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Delta Documentation.

Step A: Gather Information

Before you configure the leader-secondary-egress node cluster, obtain the following information:

  • The models and IP addresses (or hostnames) for all of the nodes. Note that:

    • The leader and secondary nodes must always be identical models.

    • The egress nodes can be different models from the leader and secondary nodes.

    • If you have more than one egress node, each node can be a different model.

    Make sure that you know which models are for which role!

  • A list of Ethernet devices (for all nodes) and their IP addresses, including traffic rules such as:

    • Which IP addresses are intended to handle management and monitoring traffic.

    • Which IP addresses are intended to handle only incoming traffic (content ingest).

    • Which IP addresses are intended to handle only outgoing traffic (egress).

    Keep in mind that the egress nodes handle only management traffic (typically on eth0) and outgoing traffic.

  • A list of Ethernet devices (on all nodes) that are bonded, and the IP addresses for those bonds.

  • A list of the Ethernet devices that were configured with IP addresses during installation of AWS Elemental Delta. The eth0 device is always configured during installation; other devices may or may not be. You need this information to determine which devices you need to figure in this configuration process and which you can assume are already configured.

  • The addresses of any additional DNS servers and/or NTP servers the nodes access.

  • The IP addresses of remote storage servers (CIFS, NFS or DAVFS) where ingested content is stored.

  • The IP address of the remote server for AWS Elemental Delta database backups.

  • The user credentials for Amazon (AWS) S3 storage, if applicable.

  • A list of ports that you want to open beyond the ports that AWS Elemental Delta automatically opens.

  • The IP addresses of VIPs on your network that are assigned to AWS Elemental Delta. These VIPs are associated with all of the Ethernet devices on all of the nodes.

  • The user credentials for users if you are setting up with user authentication.