DC/OS includes a service packaging specification and a repository that catalogs those packages. This section describes what is necessary to package and provide your own service on DC/OS.
The DC/OS Universe contains all of the services that are installable on DC/OS. For more information on DC/OS Universe, see the GitHub Universe repository. Our general recommendation is to use the DC/OS CLI rather than the DC/OS web interface throughout the process of creating a package for the Universe.
DC/OS service structure
Each DC/OS service in the Universe is comprised of JSON configuration files. These files are used create the packages that are installed on DC/OS.
||Specifies the supported configuration properties, represented as a JSON-schema.||No|
||Specifies a mustache template that creates a Marathon app definition capable of running your service.||No|
||Specifies the high level metadata about the package.||Yes|
||Specifies all of the required externally hosted resources (e.g. Docker images, HTTP objects and images).||No|
For more information, see Creating a DC/OS Package.
Publishing a package
All packaged services are required to meet a certain standard as defined by Mesosphere. For details on publishing a DC/OS service, see Publish the package.
The DC/OS command-line interface (CLI) is a utility to manage cluster nodes, install and manage packages, inspect the cluster state, and manage services and tasks.…Read More
Access by Proxy and VPN using DC/OS Tunnel
When developing services on DC/OS, you may find it helpful to access your cluster from your local machine via SOCKS proxy, HTTP proxy, or VPN. For instance, you can work from your own development environment and immediately test against your DC/OS cluster.…Read More