[OO Support Tip] What is meant by the term "OO-ONode"?
Using Operations Orchestration (OO), what is meant by the term "OO-ONode"?
Definition of an O-Node:
1. OO touches the O-Node : in this case an O-node license is needed for each O-Node device. <any flow that directly touches a device requires an OO O-Node license at a 1:1 ratio>
2. OO used for integration only : No license needed. When is OO used for integration Only? If OO is only used to integrate (which is not usually the case as OO typically is doing other things in the Data Center) to an HP product or 3rd party product. An OO O-Node license is not needed for the HP integration but an OO O-Node license is needed for the 3rd party integration>
3. OO orchestrates the entities behind the Server Automation (SA), an example would be in a 1:10 ration. Definition of "orchestrating", orchestration basically means that it coordinates the activity, i.e. process – what this means is that even though an OO flow only communicates with the domain manger (SA in this case) OO provides additional value to those SA servers thusly, the 10:1 ratio.
4. Definition of touching? “Directly touching” means that the OO flow communicates to that device directly i.e. not through a domain manager.
5. Further explaination of when to use OO for integration only? In terms of OO integration – as mentioned above, OO is typically doing other things in the environment – for instance, the OO content and Web Services would be needed to integrate OO to another product such as SA or OMi.
Direct link to the document here:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.