Overview
Key Concepts
Core Development
Content Development
- Index
- Add a New Component
- Add a Platform
- Add Monitors
- Add a New Chef Cookbook and Pack to OneOps
- Add a New Platform Pack
- CMS Sync
- Create a Custom Payload
- Create Parameterized Component Actions
- Default Monitor Thresholds
- How to Deprecate a Pack
- Content Development
- Content Development Introduction
- Metadata
- Modify existing component
- Monitor
- Override Platform Attributes
- Pack Development
- Pack policy
- Platform Management Pack
- Relationships
Integration Development
Home > developer > core development > Relations
Relations
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.
Design
In the Design aspect, we model the base application:
- No environmental
- No operational components
Transition
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 likeroute-53,dyndns,elb, etc. - Monitors: Use to customize monitors for each environment
Operations
In the Operations aspect, we create bom components for the manifest components with relation to the Binding (cloud provider).
