The Micro Focus Network Operations Management team has implemented additional containerized and cloud deployment options in Network Operations Manager (NOM) 2021.05 and 2021.08.
Deployment in the cloud provides all the typical advantages of cloud – OPEX becomes CAPEX, the cloud provider is responsible for the infrastructure, and more. Specific to NOM is easier and faster deployment because of the new AppHub which uses the HELM package manager, the use of cloud provided services such as PostgreSQL, and the ability to continue to use your existing on-prem deployment as regional network management stations. The results you are up faster with less effort and can maintain your existing investment.
NOM consists of a set of components. We are steadily progressing toward having all components built as microservices deploy in the cloud and on-premises. Here’s where we are currently (see Fig 1).
- Network Node Manager i – cloud deployment AWS/Azure in a VM or on-premises
- Network Automation – cloud deployment AWS/Azure in a VM or on-premises
- Performance Troubleshooter – container deployment using Docker with Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service AKS or on-premises
- OPTIC Data Lake (formerly COSO) – container deployment using Docker with Amazon Kubernetes AKE, Azure Kubernetes AKS or on-premises
- OPTIC Reporting (Business Value Dashboard – BVD) – container deployment using Docker with EKS, AKS or on-premises
NOM Cloud Deployment
Figure 1: Deployment of NOM, NNMi, or NOM in the cloud
Figure 1 shows the block diagram of deployment in the cloud. I’ll start on the left. OPTIC Data Lake, BVD, and Performance Troubleshooter are containerized. Vertica, the column store database OPTIC Data Lake uses, is in a VM. Postgres is a native cloud service. NOM is, primarily, a combination of NNMi and NA (and some other components that aren’t relevant for this discussion). Both run in VMs.
The optional GNM designation is for Global Network Manager, which applies in environments where you have monitoring at remote or regional sites that feed data to a global manager.
The components in the cloud communicate with your network devices via a direct connection (ex: AWS Direct Connect) or through a VPN.
Moving to the right side of the diagram, we are on-premises with your network components. At the top, you can see the optional Regional Network Management system and an optional NA Satellite. If you have one or both onsite, it will talk to the network devices and send the information up to the system in the cloud. If you don’t have the remote components onsite, the communication is directly from the cloud to the network device.
Figure 2: Improving TTV and reducing TCO by leverage cloud PaaS
Network Operations Manager Express edition is the first completely cloud-native containerized release for the Network Operations Management product line, as you’ll see under NOM Apps. It runs either on AWS or Azure.
Figure 3: Cloud-Native Application Lifecycle via Helm charts
To make installation simpler, the ITOM team created AppHub. As you can see, it includes all the ITOM products. Click the NOM button in AppHub, and you’ll be taken through installation options. Behind the AppHub is the Helm package manager. On the left, you can see the AppHub capabilities; on the right are the NOM component installation options.
To learn more about deploying NOM, see the NOM Install page
Recent and upcoming Network Operations Management events
- On-demand - Rethink Network Management
- On-demand - Network Operations Management – Accelerating the AIOps Revolution
See all the Micro Focus events Worldwide
Read all our news on the Network Operations Management blog.