As we saw in the previous chapter, a platform is a single component or a collection of components grouped together for reusability. A platform not only defines what the component is and where it belongs but also its dependencies and relationships to other components. Platforms also allow components to be grouped together via inheritance, dependencies, or other methods to create a pack so that an appropriate software state is maintained. So, let's look at our component and see how we can turn it into a platform.
We start by going to the directory called packs under our default circuit. Under that directory, you will notice there are already files for all the applications that are currently available as platforms under OneOps.
Each file defines the type of component, its description, its category, the resources it offers, and its dependencies. We start by creating a brand-new file here called orientdb.rb. The very first thing we will add to it is extending the generic...