The following model diagrams describe the relationships for Design, Transition, and Operations in the OneOps UI.
Relationships also have attributes, some of which are used to scale.
In the Design aspect, we model the base application:
- No environmental
- No operational components
In the Transition aspect, we model two additional objects:
- IaaS components: Can be load balancers (
haproxy) or DNS (
djbdns). Can also use provider-based ones like
- Monitors: Use to customize monitors for each environment
In the Operations aspect, we create
bom components for the manifest components with relation to the Binding (cloud provider).