Design: Where an application’s architecture is described
Transition: Where an application design is realized in an environment
Operations: Where instances are managed and monitored
OneOps Continuous Lifecycle
With OneOps, your design becomes much more than a simple template. It’s a continually maintained dataset where the
notion of change is always recognized.
In fact, OneOps was created from the ground up to manage the issues that arise with continuous change. In
addition, OneOps automatically scales and repairs your application to ensure high availability and optimal
utilization of your cloud infrastructure.
The following diagram describes how Platforms, Components, and Instances relate to each other in the different
lifecycle phases: Design, Transition, and Operations.
OneOps streamlines the three phases of the lifecycle – design, transition and operations.
Design in OneOps
Design is an area within an assembly where the application architecture is described. The application
comprises of platforms containing optional or required components.
Transition is an area within an Assembly where the application Design is realized in an Environment. You can
have multiple Environments derived from a single Design.
Provision environments by mapping the design output against operational requirements.
Create and customize multiple environments
Specify availability requirements
Bind to your cloud provider of choice
Deploy with effortless automation
An environment is a realization of the application Design after its operational requirements (e.g. single for dev
/redundant for qa and prod) are applied. It is an abstract layer of configuration, no real instances exist until
an Environment is deployed.
Operations is an area within an Assembly where instances are managed and monitored. Each Environment is
represented in Operations.
Monitor and control your environments to maintain the required operational levels.
Monitor the health of your application
View configuration, metrics and logs
Enable auto repair, auto scale and auto replace
Perform manual control actions
Clouds in OneOps is logical collection of supply side services which satisfy business requirements of
Organization. Some examples of cloud services
Compute service (supplied by private openstack , Azure, AWS, Rackspace)
An Assembly is an independent workspace where Applications are managed. One Organization can have multiple
Assemblies. Each Assembly has corresponding subspaces for Design, Transition and Operations.
Platforms, Platform Links and Components
A Platform is a building block of an application. Each Platform type is backed by metadata which defines its
required and optional Component sets, along with its operational behavior.
Within an Assembly, the end user can set links to dependencies between Platforms. These dependencies are used to
generate a proper deployment sequence for the Platforms. For example, when you link a web Platform to a database
Platform, the database deploys first. Then, when the web Platform comes up, the database Platform is ready.
Each Platform is comprised of Components which are the lowest-level building blocks in the OneOps system. Some
Component examples are compute, storage, Cassandra, PHP, and available components.
When you add a Platform to your application design, a set of required Components with default attribute values
are automatically created within the Platform. You can modify the attribute values for required Components and you
can add optional Components. A Component has model and control logic to manage its lifecycle, such as add,
update, repair, and more.
There are Dependencies between Components within a platform. These Dependencies are used to generate a proper
sequence of deployment steps. The end user can add lateral Dependencies between neighboring optional
Components. For example: If you have a Build that depends on another Build, you can set a Component Dependency
You can bootstrap your design using pre-loaded application templates called Catalogs. OneOps provides Catalogs for
common commercial and open-source applications. There are different categories of Catalogs, such as content
management (e.g. WordPress).You can also create custom Designs and save them in a private Catalog. This enables
you to share Designs, which helps to drive architectural consistency within your organization.
The OneOps Software as a Service (SaaS) solution is a multi-tenant application. An Organization is an isolated
entity within which all related Operations are performed.
Environment profiles are templates that are used to derive concrete environments based on pre-defined
templates. Environment profiles are abstract environment definitions that allow environments to be categorized or
classified by associating a given environment with an underlying environment profile. Typical examples of profiles
include prod, QA, etc.