Maestro Application

Repository for bringing all the services together

Application Architecture

• Cloud Front End
  • Webex Bot
• On-prem orchestration
  • Conductor Service: Central point for coordinating configuration and operations of the lab orchestration.
  • Poller Service: Coordinates with bot front end to process commands and relay them to the conductor.
• Backend Storage
  • etcd, etcd docs
• Terraform Service (roadmap)
• Ansible Service (roadmap)

Deployment Technologies

• Kubernetes
  • Development environment: Rancher Desktop: containerd based
  • Production environment: Intersight Kubernetes Service
• Helm

Technologies employed in each services are explained in their respective repositories.

References Leveraged During Development

• Visual Studio Code
  • Python in a Container
• Rancher Desktop
  • Mac Global Unicast IP issue
• Git
  • Github CLI
  • pre-commit framework
• ArtifactHub for Helm Charts
• Operator Framework
• etcd
  • etcd Operator (archived)
  • 6 tips for etcd
• Helm Chart Docs
  • Charts
  • Template Guide
  • VS Code K8s Tool
• Helm Chart Example for etcd
• Bitnami Helm Chart
  • Artifact Hub Entry
  • Bitnami Docs
  • Bitnami Chart GitHub
  • Bitnami Docker Hub
• Quay.io container
• getent hosts name for DNS lookups without bind-utils
• Visibility
  • Pixie
• Webex
  • Bots and Messaging
  • Buttons and Cards
  • PyAdaptiveCards

Roadmap

• Automation Service: Configure, store, and apply specific automation actions to targeted project/scenario combinations
• Websocket based Bot: convert buffer/poller to websocket approach
• Proxy support
• Link related GitHub repositories together to this repo
• Pipeline
  • GitHub Actions
    • Autobuild containers in all repositories
    • Decide on mechanism for versioning and autopublish those containers
  • Push new versions of containers