Platform Blueprint, Create Cluster Option
Platform Manager 1.4 introduces the Create Cluster option.
When you select Create Cluster, Platform Manager prepares the MiVoice Business, and joins MiVoice Business and MiCollab resources into a MiVoice Business SDS Cluster. (For detailed information about using SDS, see Using System Data Synchronization). You can select one of the resources as SDS Master and the other cluster members as Slaves. For most MiVoice Business Multi Instance-based 1 and 2-node MiVoice Business configurations, Management Portal requires that clustering be enabled.
Cluster members consists of only the resources with an indicated SDS Role in the 'Resource Details' section of the Platform Blueprint form.
A MiCollab type resource should have its SDS Role set to Slave on the Platform Blueprint page.
Platform Manager can create many application groups from a single group of golden databases. These golden databases may include IP addresses of the network from which the golden database was created. During Platform Manager instance creation, when the MiVB instances are being clustered, the MiVB db/embedded addresses (which originated from the golden database) are updated to match the IP addresses used in the new platform instance.
The following is a summary of MiVoice Business configuration changes made when Create Cluster is selected, the following MiVoice Business changes are made. The UI elements mentioned here refer to menus and forms in the MiVoice Business System Administration Tool.
-
Voice Network > Network Elements: Every SDS Master and Slave resource in the Platform Blueprint are included as a Network Element in this table. The resource Network Element is added, or if it already exists, its IP address is updated.
-
If a MiVoice Business Network Element already exists, its name is unchanged.
-
If a MiCollab Network element already exists, its name is changed to match the MiCollab host name.
-
If the same golden database is used for multiple resources, the PBX Number is modified to ensure uniqueness.
-
-
Voice Network > Cluster Elements: If there is already a cluster in the golden database, the cluster is used. If not, a cluster is created. Every resource Network Element is added or updated in the Cluster Members table.
-
IP/XNET Trunk Groups > ICP/PBX Networking: Every resource Network Element is added or updated in the ICP/PBX Networking table. The IP and ISDN Networking IP addresses are corrected as needed.
-
Voice Mail > VM Network Servers: If there is a MiCollab in the resource list, an entry is added. If an entry is found with matching Voice Mail type (3300 ICP or NuPoint), its IP address is updated. If an entry is added, then default values are used for DNS Name and Time Zone. If the default is not appropriate, place an appropriate entry in the golden database of the resource that is assigned the SDS Master role.
-
Voice Mail > External Visual Voice Mail: If a MiCollab is found in the resource list, its IP address is set as the Visual Voicemail Server IP address.
Caution
Stand-alone MBG resources: PM can do license/deploy/restore-golden operations on an MBG but cannot further configure. You may need to manually configure SIP Trunk and other options on the MBG.
Clustering scenarios
In general, Platform Manager can support the following Blueprint scenarios
Cookie-cutter model
Many customers can be created from the same Platform Blueprint with little post-deployment customization required. All of these customers have the same MiVoice Business and MiCollab default databases. Platform Manager updates the IP addresses and ensures that each of the nodes is added to the SDS cluster automatically.
Restrictions:
-
Each node (MiVoice Business or MiCollab) must have a unique golden database in the Blueprint. However, the Blueprint itself can be reapplied for use by other customers.
-
Cluster programming is enabled on Platform Manager for that Blueprint.
Fully-flexible model (clustering is not enabled)
Every customer has a unique configuration. There is little commonality between nodes (MiVoice Business or MiCollab) and the Blueprint is customer-specific.
Restrictions:
-
In the Resource Blueprints, golden databases are not supplied for any resource.
-
Cluster programming is disabled on Platform Manager for that Blueprint.
Hybrid Model
In this scenario, you have an optional MiCollab, a primary MiVB, and more than 2 MiVB slave nodes. You have a golden database for the Primary MiVB and a golden database for the secondary MiVB. If there are multiple secondary MiVB, then each uses the same golden database. In this case, you can use the same Resource Blueprint for every secondary MiVB.