Inmanta recently released version 4.2.0 of our Service Orchestrator product, with a lot of new features. We highlight the most notable ones.
An automation roadmap has pre-requisites and implicit costs that have an impact on TCO: integration with existing systems, infrastructure, testing.
Two costs components drive the TCO and its evolution: the automation/orchestration software cost and the service modeling costs.
A business case is the best way to convince your executives. Hence it is important to ensure a good TCO calculation prior to the project kick-off.
The open-source graph module is an internal tool we use at Inmanta to turn models into pictures. In this blog post, we explain how you can use it.
Version 3.4.0 of Inmanta Service Orchestrator comes with following new features: root cause analysis, embedded entities, emergency stop, improved plugin modularity and more.
Most automation applies imperative programming as they execute in a specific sequence. This complicates the automation of multi-domain service delivery.
Multi-domain use cases are the new normal and require an end-to-end automation solution. Most tools in the market have a specific focus and do not suffice.
Ansible got very popular for network automation, but why is there still a large backlog of semi-manual network engineering and service provisioning tasks?
Open-source version 2020.1 of the Inmanta Orchestrator introduces major improvements to the compiler and the OpenAPI specification of the orchestrator.