The Components in NEST and Karousels Managed NEST Services

1. A NEST - Conceptually is a docker-based server/VM where one or more SPAN endpoints can run
   – Can be locally managed with a range of credentials
   – Credentials can range from automatic SpanEndpoint binding to advanced credentials
   – Passive monitoring attaches a ‘FireFly’ for a heartbeat and lightweight telemetry of Prometheus metrics
   – Active Monitoring runs ‘NestMon’ as a single docker container with K9-derived monitoring/credentials
   – Actively Managed runs a ‘NestRunner’. See below.

2. NestManager - A docker-service that serves as the orchestration point for a collection of Nests
   - Typically runs in cloud
   - Can access NESTs in its collection via SPAN (if a path exists) or directly across the internet

3. NestMonitor - A docker container that runs on NEST as a passive monitor and reports health of NEST to the Karousels Ledger service via NestManager

4. NestRunner - A docker container that ACTIVELY manages the NEST by deploying SpanEndpoint services via docker engine. MUST have docker priviledge to deploy docker-compose service

5. Firefly – separate entity. Ignore for now

6. NestNews – Nest related pubsub messages. In FLM they are published on the same SQS as ledger. Collection of topics. Avro schema defs coming.

---