Install a basic cluster
From the CLI
To start a basic test cluster , run the following command on the DC/OS CLI.
This command creates a new instance with the default name percona-server-mongodb
. Two instances cannot share the same name, so installing additional instances beyond the default instance requires customizing the name
at install time for each additional instance.
All dcos percona-server-mongodb
CLI commands have a --name
argument allowing you to specify which instance to query. If you do not specify a service name, the CLI assumes a default value matching the package name, percona-server-mongodb
. The default value for --name
can be customized via the DC/OS CLI configuration:
From the web interface
Alternatively, you can install from the DC/OS web interface. If you install Percona Server for MongoDB from the DC/OS web interface, the dcos percona-server-mongodb
CLI commands are not automatically installed to your workstation. They may be manually installed using the DC/OS CLI:
After running the package install
command, the service will begin installing.
Enterprise DC/OS installation
Depending on the security mode of the Enterprise DC/OS cluster, Enterprise DC/OS users may need to create a custom .json file and use it to install Percona Server for MongoDB.
Create a Configuration File
Create a custom configuration file that will be used to install Percona Server for MongoDB, and save it as config.json
. Specify the service account (<service_account_id>
) and a secret path (percona-server-mongodb/<secret-name>
) .
Installing with a custom config file
Use the custom configuration file you just created to install Percona Server for MongoDB with this command:
Installing with external volumes enabled
Create a custom configuration file that will be used to install Percona Server for MongoDB, and save it as config.json
.
Use the custom configuration file you just created to install Percona Server for MongoDB with this command:
Service Deployment
To monitor the deployment of your test instance, install the package cli (see command above) and run the command:
Once the deploy plan has a status of Complete
, the service is fully deployed.
Service Discovery
To connect a client, query the service for its endpoints.
Select an endpoint from the list to see the available connections.
Working with the Service
Using the endpoint information, you can connect a client to the service from within the DC/OS cluster (for example, a Marathon app running a client application). See the other sections of the documentation for more details on configuration, operation, and service capabilities.