Deploying a Local Universe

Installing and running DC/OS services on a local Universe datacenter

You can install and run DC/OS services on a datacenter without internet access with a local Universe. You can deploy a local Universe that includes all Certified packages (easiest), or a local Universe that includes selected packages (advanced).

Use secure copy to transfer the Universe and registry files to a master node, replacing <master-IP> with the public IP address of a master before issuing the following commands. (You can find the public IP address of a master in the top left corner of the DC/OS web interface.)

Configuring multiple masters

If you only have one master, skip to Linking local Universe to master below. If you have multiple masters, continue with the following procedure.

Use the following command to discover the private IP addresses of all of your masters. Identify the private IP address of the master you are SSHed into right now from the list. It will match the path shown after core@ip- in your prompt, where the hyphens become periods.

host master.mesos

Use secure copy to transfer the Universe and registry files to one of the other masters. Replace <master-IP> with the IP address of the other master.

Repeat this section until you have completed this procedure for all of your masters. Then continue to the Linking local Universe to master section below.

Linking local Universe to master

Close the SSH session by typing exit or open a new terminal prompt. You may have to exit more than one SSH session if you have multiple masters.

(Optional) Use the following command to remove the references to the default Universe from your cluster. If you want to leave the default Universe in place and just add the local Universe as an additional repository, skip to the next step. You can also remove the references to the default Universe repository from Settings > Package Repositories in the DC/OS web interface.

dcos package repo remove Universe

Use the following command to add a reference to the local Universes that you added to each master.

Close the SSH session by typing exit or open a new terminal prompt. Repeat steps 28-30 on each agent node.

To verify your success, log into the DC/OS web interface and click the Catalog tab. You should see a list of Certified packages. Install one of the packages.

FAQ

I can’t install CLI subcommands

Packages are hosted at master.mesos:8082. If you cannot resolve or connect to master.mesos:8082 from your DC/OS CLI install, you cannot install CLI subcommands. If you can connect to port 8082 on your masters, add the IP for one of the masters to /etc/hosts.

The images are broken

All Universe components are hosted inside of your cluster, including the images. The components are served up by master.mesos:8082. If you have connectivity to that IP, you can add it to /etc/hosts and get the images working.

I don’t see the package I was looking for

By default, only Certified packages are bundled. If you’d like to get something else, use the instructions in the next section.

Build the mesosphere/universe Docker image and compress it to the local-universe.tar.gz
file. Specify a comma-separated list of package names and versions using the DCOS_PACKAGE_INCLUDE
variable. To minimize the container size and download time, you can select only what you need. If you do not use the DCOS_PACKAGE_INCLUDE variable, all Certified Universe packages are
included. To view which packages are Certified, click the Catalog tab in the DC/OS web
interface.