This is a detailed developer-focused documentation for the AMMOS Asynchronous Network Management System (ANMS).
Copyright (C) 2022-2025 The Johns Hopkins University Applied Physics Laboratory LLC.
[[TOC]]
This section details prerequisites to installing the ANMS from source on a development system and gives a brief explanation of the container configuration.
The setup of ANMS and demos listed in this README have been tested on macOS 11.6.4 (Big Sur), RHEL 9 and Ubuntu 20.04. To run the ANMS tool, you must also install Docker Engine version 20.10.10 or newer or Podman 5.2.2+. You will also need either Docker Compose version 1.29.2+ or podman-compose. Docker and podman can generally be used interchangeably.
The ANMS UI capability has been tested on Firefox version 96.0.1. There is no capability that should preclude operation on other modern browsers.
If your computer is behind a network proxy, this may cause issues related to using self-signed certificates when pulling dependencies to build Docker images. Though ANMS can be run behind a proxy; building the ANMS Docker images from behind a network proxy may result in errors.
The first steps in each of the container image Dockerfile is to attempt to download an APLNIS root CA to validate the APLNIS HTTPS proxy.
When building images outside of the APLNIS, this download will gracefully fail and the image will not be able to run within the APLNIS.
If upgrading from an earlier version, a few steps are necessary to clear out earlier state. The following command sequence uses standard Docker commands to stop all containers and remove all "dangling" images, networks, and volumes.
docker stop $(docker ps -q); docker rm $(docker ps --all -q); docker system prune -f; docker volume prune -f
The current ANMS capability is designed to run on localhost and on a development virtual machine.
This guide presumes that you can either connect via a VMRC remote console or with ssh tunnelling to the machine, hence the use of localhost in db connection information and in URLs.
If you deploy this to a VM, you will need to replace localhost with the hostname of the machine where it is deployed.
If not otherwise specified, most commands in this document allow podman and docker to be used interchangeably. It is also possible to install an alias (provided in most package managers) to map docker to podman if desired.
Podman, running as a standard user, is typically unable to bind to low-numbered ports. It is recommended to edit the .env file and uncomment the lines at top for AUTHNZ_PORT and AUTHNZ_HTTPS_PORT to remap those services to a higher port number. In the directions below, you would then use for example http://localhost:8084 and https://localhost:8443 instead of the default.
Note: If running on a system where SELinux is enabled, the system will not start if the appropriate security groups have not been defined. As an alternative, the security_opt sections can be commented out in the *-compose.yml files if required.
Choose the appropriate docker, podman or podman-compose commands in the directions below as appropriate for your system.
-
Select appropriate profile(s) as desired.
- If no profiles are set, a "light" deployment of the ANMS focused on browser-less API-only ANMS users.
- For a full deployment:
export COMPOSE_PROFILES=full - For a full deployment with additional developer tools:
export COMPOSE_PROFILES=full,dev
-
Clone this repository recursively (
git clone --recursive https://github.com/NASA-AMMOS/anms.git) -
Setup Volume containing PKI configuration (certificate chains and private keys):
./create_volume.sh ./puppet/modules/apl_test/files/anms/tls
-
Build Core Images using one of the following:
docker compose -f docker-compose.yml buildpodman compose -f docker-compose.yml buildpodman-compose --podman-build-args='--format docker' -f docker-compose.yml build- Note: The docker format argument here enables suppoort for HEALTHCHECK. If omitted, the system will run but will be unable to report the health of the system. This flag does not appear necessary when using the no-dash version of compose.
-
Build test environemnt images using one of the following:
docker compose -f testenv-compose.yml buildpodman compose -f testenv-compose.yml buildpodman-compose --podman-build-args='--format docker' -f testenv-compose.yml build
-
Start System using one of the following:
docker compose -f docker-compose.yml up -dpodman compose -f docker-compose.yml up -d
-
Start sample ION nodes for manager and test agents using one of the following:
docker compose -f testenv-compose.yml up -dpodman compose -f testenv-compose.yml up -d
To shutdown the system when needed:
docker|podman compose -f docker-compose.yml -f testenv-compose.yml down
To confirm that ANMS is running, open a browser and navigate to http://localhost/. If you changed AUTHNZ_PORT in the .env file, append the specified port to the URI, ie: http://localhost:8084.
There you should see the ANMS login via CAM emulator page (figure below). Default credentials is admin/admin when using the emulator.
NOTE: If you started ANMS with the 'full' profile, you will be brought to the UI after logging in. Otherwise, it is expected that you will be redirected to an error page, but should be able to subsequently access the REST API, such as http://localhost/nm/version.
To restart the system, use the 'up' and 'down' commands as described in the previous section.
The top-level docker-compose.yml uses the environment defined by the sibling file .env. Note: If using the legacy/deprecated build.sh script, that script may additionally override some environment variables.
Two principal options of the compose configuration, which are both defaulted to empty text, are:
DOCKER_IMAGE_PREFIXwhich controls any image name prefix added to all ANMS images. For a local build, this can be left empty, but for builds intended to be pushed to a Docker image registry this can be set to the full path on the registry before the image names (e.g.DOCKER_IMAGE_PREFIX=some.host.example.com:5000/path/to/images).
To see what is present in the underlying AMP database, you can use the adminer access
point. With ANMS running, go to localhost:8080 and log in to the database with:
- System:
PostgreSQL - Server:
postgres - Username:
root - Password:
root - Database
amp_core
Changes to ADMs are handled on the Manager by uploading a new version of the ADM via the Web UI. The manager will then be able to use the new ADM.
Changes to a test Agent are more complicated, and require auto-generated C sources built into the ION source tree.
The two output paths for ADM C files are:
ion/src/bpv7/nm/for BP-version-specific ADMs likeion_bp_adminion/src/nm/for all other ADMs
To regenerate agent source, scraping the pre-existing source to avoid clearing out agent implementations, run:
PYTHONPATH=deps/dtnma-ace/src/:deps/dtnma-camp/src/ python3 -m camp.tools.camp ion/src/nm/doc/adms/ion_bp_admin.json -o ion/src/bpv7/nm/ --only-ch --scrapeTo use the local AMP Manager directly via its REST API on the local host run similar to:
echo 'ari:/IANA:ltp_agent/CTRL.reset(UINT.3)' | PYTHONPATH=deps/dtnma-ace/src/ ADM_PATH=deps/dtnma-ace/tests/adms/ python3 -m ace.tools.ace_ari --log-level=warning --outform=cborhex --must-nickname | tr -d '[[:space:]]' | curl -v -XPUT -H 'Content-Type: text/plain' --data-binary @- http://localhost:8089/nm/api/agents/eid/ipn:2.6/hex; echo
A limitation in the current NM REST API disallows multiple controls in a single message, so each ARI must be iterated over for this method.
It is recommended to build all containers using the instructions in this document when practical for local deployment. To support other use cases, all images may also be built once and exported to a tar.gz using standard tools for offline deploments.
The script export.sh will create a single .tar.gz file suitable for import by Docker or Podman without requiring access to external resources.
The tar.gz file can be imported using podman|docker import anms-${VERSION}-images.tar.gz
The following table lists network services exposed by the compose containers. Users typically will not require direct access to all exposed ports for typical use cases. Usage of localhost is an example, however avaialbility from remote machines via hostname may also be subject to firewall configuration.
Note: Podman cannot bind to low-numbered ports (ie: the default for AUTHNZ). Different versions of *-compose may behave differently if an exposed port is already in use where associated containers may fail to start entirely or may start without the specified binding being available.
| Container | Description | Default Port/URL | .env variable | Details |
|---|---|---|---|---|
| authnz | Access to UI and all REST APIs | http://localhost (80) | AUTHNZ_PORT | Podman users may need to remap to a higher port number via .env file |
| authnz | " | https://localhost (443) | AUTHNZ_HTTPS_PORT | " |
| opensearch | 9200, 9600 | OPENSEARCH_PORT1, OPENSEARCH_PORT2 | ||
| opensearch-dashboards | 5601 | OPENSEARCH_DASH_PORT | ||
| postgres | Postgres SQL Database | 5432 | DB_PORT | |
| adminer | DB Management Web Tool | http://localhost:8080, 8080 | ADMINER_PORT | |
| mqtt-broker | 1883 | MQTT_PORT | ||
| grafana | http://localhost:3000, 3000 | GRAFANA_PORT | ||
| grafana-image-renderer | 8081 | RENDERER_PORT | ||
| redis | 6379 | REDIS_PORT | ||
| anms-ui | http://localhost:9030, 9030 | ANMS_UI_HTTP_PORT | ||
| anms-ui | https://localhost:9443, 9443 | ANMS_UI_HTTPS_PORT | ||
| anms-core | 5555 | ANMS_CORE_HTTP_PORT | ||
| ion-manager | ION DTN Network Manager (NM) REST API | http://localhost:8089, 8089 | ION_MGR_PORT | |
| ion-manager | DTN Bundle Protocol | 4556 | ION_BP_PORT | |
| ion-manager | Licklider Transmission Protocol (LTP) | 1113 | ION_LTP_PORT |
This signals that the anms-ui docker container is probably experiencing issues getting HTTP requests,
which is most likely related to firewall rules, the host or bind address specified in anms-ui/server/shared/config.py
or if there is an environment variable overriding this.
Refer to the .env file for port binding overrides, or docker-compose.yml for defaults. Consult with your system admin for any firewall issues.
Check the startup logs for any errors. If using podman, some port numbers may need to be remapped using the .env file to higher numbered ports, or the system configuration modified to adjust permissions (not recommended).
If you go to your browser and hostname:9030 (replace hostname with the server's hostname) and you see the ANMS UI,
but http://hostname does not render the same page, then Authnz is having an issue. You should look at the
docker-compose services list and see what it's status is. You may need to restart it via
docker-compose -f docker-compose.yml restart authnz.
This and related errors are typically caused by incomplete support or configuration of security settings. In older Docker & Podman releases these tags were ignored on systems where SELinux was not enabled.
If running certain versions of Podman, or sytems with SELinux features enabled, users may need to explicitly configure the appropriate security groups (see User Guide) or disable the security tags entirely. The latter can be done by commenting out the "security_opt" section in the *-compose.yml files.
The create_volume.sh script in the directions above automatically detects if docker or podman is available. If both are available (and are not aliased to each other), you must explicitly specify your chosen container type to ensure the volume is created appropriately.
This can be done by setting the DOCKER_CMD environment variable such as DOCKER_CMD=podman ./create_volume.sh ./puppet/modules/apl_test/files/anms/tls