...
We have already detailed why you would want to use a VoipNow system installed on multiple computers.
To keep things short, it looks like you need massive scalability that goes beyond the possibilities of the possibilities of a single hardware machine and you still want to have a single system to manage, not multiple autonomous systems.
...
The current document does not aim at describing how a reliable infrastructure should be built. This is not its purpose. We will only be looking at the container, as the computing entity that runs the software. Since this is a virtual machine, it is highly abstracted and standardized, so we do not care what lies behind it. Basically, it is the same philosophy you adopt when buying many IaaS services.
Container
The Container represents a virtual computing instance, with its own computing power, memory, storage, network addresses and operating system. The Containers are a logical unit, provided by the virtualization software.
Containers are:
- Flexible: they they can be started and stopped and resources can be changed (even without reboot), etc.
- Part of the infrastructure: In In many cases the only exposed part of it.
- Given at least a network address (only private, only public, or both types).
...
Think of the Infrastructure and Software like a courier company. Each company has many employees delivering stuff. Some are specialized in delivering to customers, others are delivering between hubs, contractors, etc. The employee is responsible with delivering the packages. Usually one drives a car, but the car might be shared between shifts, the car might break down, etc. It is just a method to fulfill to fulfill the goal, it can be replaced, taken out of service, etc.
...
- Red Hat Enterprise Linux 6 Update 6 and newer newer (x86_64)
- Red Hat Enterprise Linux 7 Update and newer (x86_64)
- CentOS 6.6 (x86_64)
- CentOS 7.1 (x86_64)
...
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.