Relationship to DevOps
DevOps is an important evolution in the field of application delivery and management practices and is gaining favour globally as a way to improve both application quality and availability.
The term ‘DevOps’ refers to a philosophy of operations automation in which the opportunity for slow or error-prone hands-on involvement in the build, test, packaging, deployment and monitoring steps for complex application resources is either reduced or removed.
ArenaCore embraces this philosophy and creates opportunities for better visibility & integration of architecture design changes into the DevOps flow.
The importance of visibility during architecture changes is critical. As new and changed application architectures are planned and designed the evolution and visibility of these changes can be managed across relevant team members so that unexpected impacts can be identified and actioned ahead of time.
Whilst ArenaCore does not aim to overlay all activities within the DevOps domain, it can act as a helpful addition to the DevOps philosophy by improving overall team design awareness.
Established configuration management products such as Puppet, Chef and Ansible all depend on accurate inventory data and can all be automated, potentially making them good candidates for integration against the relevant ArenaCore (TMForum) OpenAPIs. Likewise, other types of configuration management products such as Cloudify or Terraform can also be integrated with ArenaCore.
An interesting opportunity is here therefore to explore how DevOps practices may be further empowered by a resource automation management approach as is supported on the ArenaCore platform!
Development of integration support in this area is written in the Go language, using NATS Streaming as a transport mechanism, and the relevant TMForum API(s) as the application layer model. Stay tuned for further updates regarding this!
Please continue to the Relationship to the Open Source community section.