Skip to content

Latest commit

 

History

History
62 lines (43 loc) · 3.37 KB

HeadlessDeployment.md

File metadata and controls

62 lines (43 loc) · 3.37 KB
Raw

Managed Grafana Deployment

  • The following steps assume the Moneo directory is located here: /opt/azurehpc/tools/Moneo
  • The following steps deploy Moneo workers using Moneo linux services, however Az CLI can also be used to deploy the Moneo workers. See managed prometheus guide for details on how.
  • Moneo CLI can be used in place of Moneo linux services to deploy Moneo workers

Deploy Infrastructure

To use this method you will need to deploy the managed infrastructure and managed user identity.

Follow steps outlined in Infrastructure deployment to setup Azure Managed Grafana and Prometheus resources.

Note: this only needs to be done once.

Deploy Moneo

  1. Assign the identity to your VMSS resource:

    • This can either be done via the portal or AZ CLI (below)

    • During VMSS creation:

      az vmss create --resource-group <RESOURCE GROUP> --name <VMSS NAME> --image <SKU Linux Image> --admin-username <USER NAME> --admin-password <PASSWORD> --assign-identity <USER ASSIGNED IDENTITY> --role <ROLE> --scope <SUBSCRIPTION>

    • Already existing VMSS:

          az vmss identity assign -g <RESOURCE GROUP> -n <VIRTUAL MACHINE SCALE SET NAME> --identities <USER ASSIGNED IDENTITY>

  2. You may choose to deploy Moneo services using moneo service deploy script. Other wise skip this step.

    1. Modify the following ENV variables with the appropriate data:
      • IDENTITY_CLIENT_ID: This will be the client ID of the user managed identity
      • INGESTION_ENDPOINT: This will be the URL to the ingestion endpoint
    2. Run the deploy script sudo ./moneo_service_deploy.sh. This will install, configure, and start Moneo services.
    3. Skip to step 5. Note: This step can be performed in parallel using pssh. Reference step 4 for start and stop commands.

  3. Modify the managed prometheus config file in Moneo/src/worker/publisher/config/managed_prom_config.json.

    • Reference the user managed identity created during infrastructure deployment to get the "identity client id"
    • Reference the Managed Prometheus resource created during infrastructure deployment to get the "metrics ingestion endpoint"
    • The config file modifcations must be distributed to the Moneo directories on all workers.
    {
    "IDENTITY_CLIENT_ID": "<identity client id>",
    "INGESTION_ENDPOINT": "<metrics ingestion endpoint>"
}

  4. Start Services (Assumes Azure marketplace AI/HPC Image): parallel-ssh -i -t 0 -h hostfile "sudo /opt/azurehpc/tools/Moneo/linux_service/start_moneo_services.sh true"

    • To stop services: parallel-ssh -i -t 0 -h hostfile "sudo /opt/azurehpc/tools/Moneo/linux_service/stop_moneo_services.sh"

    Note: If not using Azure AI/HPC market place image reference the "Deploying Linux services guide" for full instructions.

  5. At this point data collection should be on going and metrics streaming to the Azure managed Grafana setup during infrastructure.

    Note: In the infrastructure deployment step you have the option to use provided template dashboards or create your own.

  6. Check with Azure Grafana Dashboards to verify that the metrics are being ingested.

    image