Deploying Public Services

Deploying Public Services

DC/OS agent nodes can be designated as public or private during advanced or cloud installations. Public agent nodes provide public access to your DC/OS applications. By default apps are launched on private agent nodes. To launch an app on a public node, you must create a Marathon app definition with the "acceptedResourceRoles":["slave_public"] parameter specified.

  1. Install DC/OS and DC/OS CLI by using the advanced installation or cloud installation instructions. You must declare at least one agent node as public.

    For example, with advanced installation you can designate an agent node with this command:

    sudo bash slave_public

    For example, with the AWS cloud installation, you can specify a public agent node with the PublicSlaveInstanceCount box:

    alt text

  2. Create a Marathon app definition with the "acceptedResourceRoles":["slave_public"] parameter specified. For example:

        "id": "/product/service/myApp",
        "container": {
        "type": "DOCKER",
        "docker": {
              "image": "group/image",
              "network": "BRIDGE",
              "portMappings": [
                { "hostPort": 80, "containerPort": 80, "protocol": "tcp"}
        "acceptedResourceRoles": ["slave_public"],
        "instances": 1,
        "cpus": 0.1,
        "mem": 64

    For more information about the acceptedResourceRoles parameter, see the Marathon REST API documentation.

  3. Add the your app to Marathon by using this command:

    dcos marathon app add myApp.json

    If this is added successfully, there is no output.

  4. Verify that the app is added:

    dcos marathon app list
    /myApp   64  0.1    0/1    ---      scale       DOCKER   None