# Systems Configuration

The software that makes up the terraref system runs on different VM's. Some of the services leveraged by the systems runs in a replicated mode so that the overall system will not stop working if any of the underlying VM's goes down.

Following is the overview of the system as it is running now:

![](/files/-LnFMmkexL34uKorycLt)

* terraref is the frontend for everything, runs nginx
* terra-clowder runs the data management system clowder, connected to terra-mongo-\[123], terra-es-\[123], terra-postgres and the [NCSA storage condo](https://wiki.ncsa.illinois.edu/display/NRE/About+NCSA#AboutNCSA-StorageCondo) (using NFS mount)
* terra-geodashboard runs the geodashboard software, connected to terra-clowder
* terra-thredds runs the thredds server (experimental), connected to roger filesystem (using NFS moutn)
* terra-es-\[123] run elasticsearch 2.4 and for a cluster
* terra-mongo-\[123] run mongo 3.6 in a replicated cluster, terra-mongo-3 is an arbiter and does not hold any data
* terra-postgres runs postgres 9.5


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.terraref.org/revisions/technical-documentation/systems-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.