Inductor and its structure
Inductor, as explained earlier, forms the link between the design and deployments. The inductor is responsible for collecting the two types of order, WorkOrder and ActionOrder, from the controller from various queues by zone. It then executes various actions based on the type of order. Remember that WorkOrder always results in a physical change of a CI-like deployment or in a teardown of CI, whereas ActionOrder will result in the change of the state of a CI-like stop, start, or restart. The inductor consumes these orders and acts on them by executing them either locally or remotely. The local execution is done via an Chef-solo cookbooks, and the remote execution is handled via SSH Chef-solo execution.
By default, the inductor component gets installed in /opt/oneops/inductor.
Although you can set up your own inductor, it is highly recommended that you retain the default inductor setup that comes with OneOps. A single inductor can manage multiple clouds and multiple...
