MAAS Project Definition

Monitoring As A Service

Oracle 12C Cloud Control on Amazon’s EC2 web services

Project Goals

1.      Personal educational environment for the suite of Amazon Web Service (AWS) tools

2.      Personal educational environment for 12c Could Control

3.      Proof of concept for a marketable cloud based monitoring system – Monitoring As A Service (MAAS)

Project Phases

1.      Initial Installation, Configuration & Discovery

2.      Detailed Feature Exploration & Feature-Level Testing

3.      System and Architectural Tuning

4.      Cost Analysis & Business Case Evaluation

5.      Automation & Packaging

Project Synopsis

Installation, Configuration & Discovery – This phase will iterate through several installs and reconfigures until a stable and functionally complete environment it built for Oracle Enterprise Manager (OEM) on AWS. Because the total feature set is very extensive this phase will be ongoing for several months and will merge into phase two.

Detailed Feature Exploration & Testing – This phase will focus on exploration, building, and testing of features deemed necessary for a production OEM system. Features will be tested for stability and robustness, and also on the ease of support and cost effectiveness on the AWS architecture. This phase will run from 2 to six months

System and Architectural Tuning – The results of phases one and two will provide the background to build, test, and tune the MAAS architectural design. The design will adhere to Oracle’s Maximum Availability Architecture, AWS’s architecture best practices and OEM configuration standards. The final system must be stable, cost effective, and offer flexible service offerings through OEM. This phase will run 3 months.

Cost Analysis & Business Case Evaluation – OEM has a very extensive level of system, application, and business-level services. These services delivered via MAAS must be at a substantial cost reduction. This phase will focus on packaging these services into Service Level Agreements (SLA). Each SLA will have associated business requirement, cost, metric, review and report, and where applicable thresholds, response, and actions. This phase will run 2 months.

Automation & Packaging – Cost effectiveness is the primary goal of the project. OEM must be configured for automation of tasks at every opportunity.  Cost will rise significantly where automation is not ‘out of the box’ or has to be developed and refined over time. OEM and the overall Oracle and AWS architecture must be designed to be as ‘lights out’ as possible. The end result will be an Amazon Machine Image (AMI) which contains a deployable MAAS infrastructure. The AMI can be quickly installed for each new business customer and subsequently customized through the SLA creation process. This phase will run three months.