Cloud deployments

MeghHA^TM Middleware works in the following technologies and we provide help in deploying MeghHA^TM Middleware for specific use cases:

1. MeghHA^TM Middleware provides High Availability(HA) in Cloud and Virtualization Technologies, Cloud Infrastructure (like openstack and VMware).

2. MeghHA^TM Middleware is being used as High Availability as a Service(HAaaS) in Network Function Virtualization (NFV) Technology, where it provides High Availability(HA) for

    - Applications inside Virtual Machines(VMs),

    - Virtual Machines(VMs),

    - Hypervisor,

    - Hardware,

    - Element Management,

    - Network Function Virtualization Orchestrator(NFVO),

    - Virtual Network Function Manager(VNFM) and

    - Virtual Infrastructure Manager(VIM).

3. MeghHA^TM Middleware is used for making Software Defined Networking (SDN) (OpenDaylight's) components (SDN Controller) highly available.

4. MeghHA^TM Middleware provides High Availability (HA) in Containers and Applications inside the Containers (Docker containers).

5. MeghHA^TM Middleware provides High Availability (HA) in Microservices.

6. MeghHA^TM Middleware provides High Availability (HA) in Continuous Integration/Continuous Delivery(CI/CD), Internet of Things(IoT) and Industrial Internet of Things (IIoT).

We support customization/enhancement of  MeghHA^TM Middleware for Cloud deployments or Cloud use cases. The telecom software services used to run in closed cluster and provide the desired services. Now a day, with the advent of the NFV, Microservices, CI/CD and Cloud, telecom software is moving from closed cluster deployments to the Cloud deployments. This brings lots of challenges for telecom software. From High Availability point of view, the most important challenges are:

• Microservices: Breaking a monolithic service into multiple loosely coupled light weight services, brought a new set of requirements in addition to traditional HA solutions. More components need to be monitored with care of coupled services.

• Continuous Integration/Continuous Delivery (CI/CD): This needs a robust, automatic, quick, rolling upgrade at scale.

• VM Migration: If the faults happens in hardware where the software is running, then the complete VM need to be migrated to another healthy hardware. This was not a requirement in traditional telecom software.

• Scale-in/Scale-out: This was not a requirement for telecom software in closed cluster. In Cloud, this has becomes a challenge for both telecom software and high availability solutions to adopt with this change.

• Enterprise Way: The telecom software now runs like enterprise software in a cloud, where there could be links breaks, split-brain situations, cluster partitioning, etc. These are real challenges for telecom software.

• Geo-redundancy: If the data centres, where telecom software is running, then how to redirect complete work load on another data centres at another locations. This brings challenge in syncing Active component data with a geographically distant located Standby component.

• Hardware or virtualized layer fault detection time: Since the telecom software are not running on purpose built hardware and the hardware can’t be monitored by software so easily, fault information propagation from lower layer till software layer is a real challenge. It looks more challenging if we think about fault detection time (< 1 sec) for carrier grade systems. As of now, the fault detection and propagation from hypervisors to software takes few seconds of time, which is not acceptable by carrier grade systems.

There could be telecom software specific requirements or use cases as well, which needs to be supported for Cloud deployments. These kinds of requirements are mostly derived from VNFs when single box software is distributed into multiple VNFs.

What do we do in Cloud deployment support?

• Study of Products and its Cloud deployment needs/use-case,

• Derive the High Availability requirements,

• Implementation of the use cases/requirements