You can install DC/OS on bare metal, virtual machines and every cloud. With the custom installers, you have the flexibility to configure each installation of DC/OS exactly how you like it.
You can use a simple graphical interface to configure and install DC/OS on your cluster. This method takes care of installing all the prerequisites on each instance along with everything required for DC/OS. Note that only a subset of the configuration options are available with this method. It is, however the fastest way to try out DC/OS on your own cluster.
For those who’d like a little bit more opportunity to configure things, the CLI installer is a great choice. It can take care of installing all the system requirements, just like the GUI installer. The advantage is that you’re able to pick more options as to exactly how your cluster is configured. An example of this would be the storage Exhibitor uses to bootstrap.
When you’re ready to integrate DC/OS with your configuration management tools or create an image to roll out datacenter wide, the advanced installer is for you. This method provides you with all the flexibility you need to pick the actual installation process, every configuration option available and a simple way to consistently add agents to the cluster on a regular basis.
The automated GUI installer provides a simple graphical interface that guides you through the installation of DC/OS. The automated installer provides a basic installation that is suitable for demonstrations and POCs. Only a subset of the configuration options are available with the GUI method. This is the fastest way to get started with DC/OS.
With this installation method, you package the DC/OS distribution yourself and connect to every node manually to run the DC/OS installation commands. This installation method is recommended if you want to integrate with an existing system or if you don’t have SSH access to your cluster.
In DC/OS, agent nodes that are publicly accessible are designated as public and those that are not are designated as private. By default, agent nodes are designated as private during GUI or CLI installation.
By default the DC/OS Universe repository is hosted on the internet. The DC/OS OAuth Service must have access to dcos.auth0.com to fetch the required public key via HTTPS to validate access tokens. If your DC/OS cluster is behind a corporate proxy, you must update your configuration post-installation to fetch the Universe packages and OAuth service to work.