Maat Features
Available as a free open-source solution under the Apache v2.0 license, Maat provide you with:
-
Open, standards-based API
- Full CRUD support offers automation and orchestration implementation out of the box.
- TMF638 Service management API
- TMF639 Resource management API
-
Scalable extensible architecture
- Single, consolidated database
- Integrated validation and logging
- Compose complex objects using two-way relationships
-
Extensible data model
- Industry compatible service and resource base model
- Endlessly customisable
- Model your own resources using templates
-
Modular structure
- Schema based non-SQL database
- Separate service and resource APIs
- Individual event management
-
Dynamic GUI
- Easy to use, intuitive design
- Adapts to your customised model definitions
- Supports different data views
-
Event Notification
- Separate notification engine
- Listen and react to events
- Log all activities
Maat Components
-
Physical Resources
Describe infrastructure elements and details of physical location and utilization (card distribution, allocation of physical ports, …)
-
Logical Resources
Describe virtual resources, connections and relationships between resources
-
Services
Collect detailed information about services and map them to logical and/or physical resources.
Optional extensions:
Event Listener
The Event Listener is an optional additional application that can be run together with Maat.
-
Notification Management
Subscribe to events of interest.
Use a standard API to receive information about different events (add/update/remove resources/services) in Maat. Register a listener and make queries with advanced filtering.
-
Historical Data
Keep history of all changes.
It enables keeping track of all events that happen in Maat in a historical archive. In this way you can have access to past services and removed resources enabling you to retrace your network evolution or revert back to an earlier state of the network.
AAA
-
Granular Authentication and Authorization
Define fine-grained rules and controls on who can do what in your Source of Truth. Use a two level authorization model defined in Keycloak that is based on a combination of user roles and resource/service filters.
-
Logging
Use Graylog or Grafana Loki to monitor Maat and/or Event Listener logs and ensure that you have a stable stable system in place.
Give it a Try
-
Run a demo in nmaas
Maat is available as a container application in nmaas. Test it's features in a ready to use environment.
