Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configure Paragon Automation to Route API Calls to Anuta ATOM

After Anuta ATOM is added as an external EMS, you can route certain API requests made to Paragon Automation to Anuta ATOM; for example, to access resources in Anuta ATOM through calls made to Paragon Automation APIs. To enable Anuta ATOM to service Paragon Automation API requests, you must configure Anuta ATOM API credentials in Paragon Automation. After the Anuta ATOM API credentials are saved in Paragon Automation, all requests made to https://paragon/anuta/restconf are forwarded to https://anuta/restconf. You can also configure additional endpoint mappings.

To configure Anuta ATOM API credentials in Paragon Automation, you must configure a Kubernetes secret to provide the credentials. The credentials include username, password, client_id, and client_secret.

To configure the Kubernetes secret:

  1. Log in to the primary node of Paragon Automation.
  2. Create a *.yml file with name anuta-secret and assign appropriate values for the Anuta ATOM API credentials. The following is a sample of the anuta-secret.yml file:
  3. Apply the secret using kubectl:
    kubectl apply -f anuta-secret.yml
  4. You can delete the anuta-secret.yml file as it is no longer required.

After this configuration, by default, all requests made to https://paragon/anuta/restconf is forwarded to https://anuta/restconf.

You can also configure additional API endpoint mappings by using Kubernetes ConfigMaps. The following example shows how you can access the Anuta ATOM device resources through Paragon Automation.

To access an Anuta ATOM device resource from Paragon Automation:

  1. Log in to the primary node of the Paragon Automation installation.

  2. Create a file anuta-cmap-ctrldev.yml with a ConfigMap to forward requests matching https://paragon/restconf/data/controller:devices to https://anuta/restconf/data/controller:devices. The following is a sample of the anuta-cmap-ctrldev.yml file.

  3. For any custom mappings, modify the prefix and rewrite sections as required, where prefix specifies the Paragon Automation URL prefix to match, and rewrite specifies the Anuta ATOM URL to where API requests must be forwarded.

  4. Apply the ConfigMap using kubectl:

After you configure the credentials and endpoints, you can send API requests to a Paragon Automation endpoint. The following example is a request for device information that is fulfilled by Anuta ATOM.

By configuring API credentials for Anuta ATOM in Paragon Automation, you can use an API service using Paragon Automation credentials to make requests to both Paragon Automation and Anuta ATOM endpoints.

Delete the ConfigMap if you no longer need the endpoint configuration.

kubectl delete -f anuta-cmap-ctrldev.yml

Related Documentation