Skip to main content

The aim of this project is to provide unified service modeling, management and visualization platform agnostic of delivery method. It creates virtual representations of any software services or physical resources and allows control over their entire life-cycle. The name of project comes from Architect program in Matrix movie series:

In the Matrix the Architect is a highly specialized, humorless program of the machine world as well as the creator of the Matrix. As the chief administrator of the system, he is possibly a collective manifestation, or at the very least a virtual representation of the entire Machine mainframe.

The The Architect project was started as part of my thesis “Visualization of cloud performace metrics”. Now we explore the possible implications of combining the relational models of infrastructures with quantitative data that relates to it.

Following figure shows high-level achitecture of Architect system.

./doc/source/static/scheme/high_level_arch.png

You can find installation instructions, getting started guides, and API documentation at https://architect-api.readthedocs.io/.

Architect Components

The Architect project consists of 4 core compontents (inventory, manager, monitor and document). A quick summary of properties, capabilities and integrations for each component.

Inventory Component

Inventory is the Architect’s metadata engine. It encapsulates and unifies data from various metadata sources to provide inventory metadata for various orchestration services. Basically serves as metadata proxy with clients. It works best integrated with http://salt-formulas.readthedocs.io/.

Currently supported metadata backends are:

The currently supported customers of metadata provided by Inventory using architect-api client library are:

  • SaltStack

  • Ansible

  • Puppet

  • Chef

Following orchestrators have direct support for injecting context metadata:

  • Heat

Manager Component

Manager is the Architect’s orchestration engine. The aim of this module is to enforce infrastructure topologies models and acquire live infrastructure topology data from any resource provider for further relational and quantitative analysis and visualisations.

The pull approach for querying endpoint APIs is supported at the moment, the processing push from target services is supported for SaltStack events.

Currently supported resource providers are:

  • Kubernetes clusters

  • OpenStack clouds

  • Heat templates

  • Amazon web services

  • SaltStack infrastructures

  • Terraform templates

  • Jenkins pipelines

Monitor Component

Monitor is the Architect’s monitoring engine. It can connect to multiple data endpoints and subject them for further analysis. We can define queries for quantitative data or time-series in Document component.

Currently supported time-series databases are:

  • Graphite

  • ElasticSearch

  • Prometheus

  • InfluxDB

Document Component

Document component is responsible for analysis and visualization of infrastructure resources in form of directed graph. We can perform several transformation functions on this graph data. The other part is analysis of quantitative data provided by monitoring solutions and corellating it to the relational structures provided by Manager component.

Currently supported relational visualization layouts:

  • Adjacency matrix

  • Arc diagram

  • Force-directed graph

  • Hierarchical edge bundling

  • Hive plot

  • Circle packing

  • Node-link tree (Reingold-Tilford tidy trees, dendrograms)

  • Partition layout (sunburst, icicle diagrams, treemaps)

  • Sankey diagram

Currently supported quatitative visualization layouts:

  • Line chart

  • Bar chart, stacked bar chart

  • Horizon chart

  • Donut chart, pie chart

Release files for architect-api 0.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for architect-api 0.4
File Size Uploaded
architect-api-0.4.tar.gz 286.8 kB Details

Release files / architect-api-0.4.tar.gz

Download URL architect-api-0.4.tar.gz
Size 286.8 kB
Tags Source
SHA-256 checksum
How to use checksums
3f68e8bdb1cd8b9c3147779c5714b71f108115919dfb85b45468918da75f4ead
BLAKE2b-256 checksum
How to use checksums
4be6e2c90f177ef048d76ea0a3612c7895d72c6c0ac787a451aa651e2841444b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release history Release notifications | RSS feed

This release

0.4 This release

1 release file

0.3

1 release file

0.2

1 release file

0.1

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page