A brief recap of the OneOps architecture

The OneOps architecture has been covered in detail in the previous chapters. However, when we covered the architecture we did not cover the components, their design, and how they fit in with the overall OneOps scheme. As we have already seen, the front end for OneOps is called display and is written in Ruby On Rails. Display serves as the front end through which OneOps users can configure clouds, build assemblies, and monitor deployments. OneOps also stores data in three main postgres databases. As described in Chapter 2, Understanding the OneOps Architecture, everything relevant to OneOps is stored in one of these databases. Besides these, OneOps runs a host of backend services that provide a lot of functionality. These services talk to each other over the ActiveMQ messaging service. Again, as described in detail in Chapter 2, Understanding the OneOps Architecture, these services act on two types of messages: a work order or an action order. A work...