Platform Manager supports two application infrastructure types: MiVoice Business Multi-Instance servers and VMware vCenter. Each infrastructure type also has a pre-configured Resource Manager:
• | MiVB-MI for the MiVoice Business Multi-Instance infrastructure |
• | vCenter for the VMware® vCenter infrastructure |
From Platform Manager Configuration > Infrastructures, click Register Infrastructure.
An Infrastructure refers to a single MiVoice Business Multi-Instance or a VMware vCenter instance, running MiVoice Business Express.
MiVoice Business Multi Instance provides the infrastructure and management to run multiple MiVoice Business Instances.
MiVoice Business Express provides a complete communications solution for small to medium-sized businesses. It runs as a virtual appliance on a VMware vSphere infrastructure, and includes MiVoice Business, MiCollab, and MiVoice Border Gateway, all in one package.
Before adding the first server, you must setup a MiVoice Business Multi-Instance server pool. Then register the MiVoice Business Multi-Instance servers, grouped into one or more pools.
A server pool is a grouping of MiVoice Business Multi-Instance servers. When the Platform Manager builds a platform from a blueprint, the blueprint indicates the pool from which the MiVoice Business Multi-Instance server is to be obtained. If the pool is unable to fulfill the request, the creation operation will fail.
Pools are used to indicate a hardware location preference. Pools are used to force resilient pairs of MiVoice Business Multi-Instance instances to be built on different servers, possibly in different data centers.
You should have at least two MiVoice Business Multi-Instance pools. MiVoice Business Multi-Instance pools are referenced by the resource blueprints, and are used to indicate the geography in which you want the resource instances located. For example: twp pools, named east and west; place your east coast MiVoice Business Multi-Instance servers in pool east; west coast in west. You make two resource blueprints, each referencing a different MiVoice Business Multi-Instance pool. In the Platform Blueprint, link in both of the resource blueprints. The resulting platform will contain one instance in each pool, east and west, resulting in geographic separation of the instances.
Note: A MiVoice Business Multi-Instance server cannot be removed from a pool, and it cannot be moved to another server pool.
Use pool names that describe their location or planned use so that other admins will be able to choose accurately from them. Some examples:
• | East Coast |
• | West Coast |
• | East-Primary |
• | East-Secondary |
When adding a MiVoice Business Multi-Instance server, you must supply the following information:
• | Server IP address |
• | Mitel Standard Linux (MSL) administrator log in name |
• | MSL administrator password |
• | The server pool into which this MiVoice Business Multi-Instance server is to be placed |
You can add a MiVoice Business Multi-Instance server at any time. You may delete a MiVoice Business Multi-Instance server only if there are no Platform Manager-managed instances on that server.
Tenants on a MiVoice Business Multi-Instance server that has been added to Platform Manager should be managed using Platform Manager. You can still log into MiVoice Business Multi-Instance, but any tenants created using the MiVoice Business Multi-Instance web panel will not be managed by Platform Manager. If you stop or start a Platform Manager-managed tenant from the MiVoice Business Multi-Instance web panel, the change will not be reflected on the Platform Manager web panels.
If you delete tenants from the MiVoice Business Multi-Instance web panel, you should also delete the corresponding resources and platforms on Platform Manager. These changes are not reflected on Platform Manager automatically.
Platform Manager does not create the MiVoice Business Multi-Instance ARID. You must manually install and license a MiVoice Business Multi-Instance server prior to registering the server with Platform Manager.
You must prepare a MiVoice Business Multi-Instance server before Platform Manager can create tenants on it.
1. Create an IP address pool.
2. Create associated Media Server Manager instances.
You do not need to load any golden databases or MiVoice Business software images onto the MiVoice Business Multi-Instance server. Any necessary files will be automatically downloaded during creation of the MiVoice Business Multi-Instance tenants.
If there are tenants on the MiVoice Business Multi-Instance server when you register it with Platform Manager, these tenants will not be managed by Platform Manager.
When Platform Manager instructs a MiVoice Business Multi-Instance server to build a tenant, the tenant IP address is pulled from an address pool that was previously configured on that MiVoice Business Multi-Instance server.
The MiVoice Business Multi-Instance server has two IP address configuration modes known as VLAN and non-VLAN mode. The default is non-VLAN mode. If you want VLAN features then you must put the MiVoice Business Multi-Instance into VLAN-mode before to configuring the Network Pool. See the MiVoice Business Multi-Instance documentation for details.
Note: If the MiVoice Business Multi-Instance server has existing tenants, do not add the IP addresses used by these tenants to the network pool.
Note: If you are building MiVoice Business Multi-Instance tenants manually using the MiVoice Business Multi-Instance GUI, do not use IP addresses that have already been added to the network pool. This will cause failures when Platform Manager tries to use these IP addresses when creating a tenant.
Capacity calculation: Platform Manager considers the tenant capacity of the MiVoice Business Multi-Instance server to be the lesser of:
You can use the network pool to limit the number of tenants created by the Platform Manager on a particular server. To see the server capacity in the utilization widget on the Platform Manager, navigate to Configuration > MiVB-MI Pools.
Use the MiVoice Business Multi-Instance server CLI command mcdnetpool
to create and view the network pool. You add sets of IP addresses that will be appropriate for a MiVoice Business instance on this server. The output of the mcdnetpool
command differs depending on whether the server is in VLAN mode or not. Use the –h
option to view help. If you use the MiVoice Business Multi-Instance web panel to create instances, do not use an address from the network pool. Each MiVoice Business Multi-Instance server registered with Platform Manager has an address pool dedicated for use by Platform Manager.
Example:
List the contents of the network pool. A yes in the "record allocated" column indicates that the pool record is in use.
The listing shown here is from a system that is not in VLAN mode.
[root@triale mcd]# mcdnetpool -l Net Pool
is record system ID allocated IP
184 yes 10.40.184.41
185 yes 10.40.184.45
179 yes 10.40.184.21
183 yes 10.40.184.37
188 yes 10.40.184.57
186 yes 10.40.184.49
182 yes 10.40.184.33
180 yes 10.40.184.25
178 yes 10.40.184.17
181 no 10.40.184.29
Add entries to network pool (VLAN mode):
This example creates 214 address records in the network pool on a MiVoice Business Multi-Instance server that is in VLAN mode. For non-VLAN mode omit mgmtip, vlan, mask, and gateway options.
mcdnetpool -c 214 --sysip=3.50.0.4 2 --mgmtip=192.2.8.4 1 -- gateway=3.50.0.1 0 --mask=255.255.254.0 0 --vlan=3500 0 [root@MiVoice Business Multi-Instance ~]# mcdnetpool -l |head -10
You create media server instances manually, at the same time as you are populating the MiVoice Business Multi-Instance network pool. Create and start one media server instance for every IP address in the MiVoice Business Multi-Instance network pool. These instances wait for their assigned MiVoice Business instance to appear. During this wait time, you will see the media server instance state indicate down or starting; this is normal.
:MiVoice Business Multi-Instance server usage:
You can see tenant capacity per server and per pool. See the MiVB-MI Pools page for a list of pools and their respective utilization. Click the pool name to see a list of MiVoice Business Multi-Instance servers and their specific utilization figures.
The server capacity is the lesser of MiVoice Business Multi-Instance tenant capacity and network pool size.
Before adding the first server:
You must register Platform Manager as a vCenter extension to be able to manage the IP pools, so the user name must have all the extension privileges enabled.
You can configure all of the privileges in one role, or you can split the privileges into several different roles.
When you add a VMware vCenter infrastructure to Platform Manager, you receive a user name and password to allow access to the vCenter. The user name is added as a permission to the vCenter level with the role of “Extension User,” for example, and added as a permission to one of the virtual data centers that the vCenter manages. In this example, this role is called “Virtual resource manager administrator”. These roles give Platform Manager access to one of the virtual data centers in the vCenter (which may have multiple virtual data centers).
Important: The username must have permissions added at the vCenter level with a role that enables the extension privileges.
Assign the following privileges in vCenter, as a minimum, to enable instance management in Platform Manager.
Extension privileges |
Enable:
|
Datastore | Allocate space |
Network | Assign network |
Resource | Assign virtual machine to resource pool |
vApp | Import |
Virtual machine |
Configuration
|
Virtual machine |
Interaction
|
Virtual machine |
Provisioning
|
If you prefer to create one role that holds all of the required permissions, assign the following privileges:
Extension
Datastore
Network
Resource
vApp
Virtual machine
Configure vCenter to use the vSphere API. Have the following information ready before you start:
• | server address |
• | user name |
• | password |
You can add IP address pools to vCenter so that you have IP addresses and related information available when it is needed. In VMware, an IP pool is associated with a VMware network. If there is no IP address available when a resource is created, Platform Manager tries to obtain an IP address from the network.
The VMware Network is defined either in the Blueprint or when you deploy it. If the IP address pool is added to vCenter successfully, an IP address will be available.
The File Servers hold the files referred to by the Blueprints, and distribute them to infrastructure during creation of an instance. All files referred to in a Resource Blueprint must already be uploaded to an File Server. You upload these files from the Platform Manager user interface.
The only file server supported is the File Server, which is installed using a separate Mitel application Blade.
Register a file server in Platform Manager with the following data:
• | Server name |
• | Server IP address: If File Server is on the same server as Platform Manager, this IP must be the IP address of the server. Do not use localhost or 127.0.0.1. |
• | File Server super-user account name and password. You can get these from the File Server dashboard web portal. |
You may consider moving files to another File Server if you have multiple File Servers registered. If you would like to remove a File Server, but it still contains file that are referred to by blueprints, deletion will be blocked.
You can move files to another File Server, which will allow you to remove the original File Server.
Both File Servers must be registered in Platform Manager.
1. Copy the files manually from source to destination file server.
2. Update the file assignment in Platform Manager.
In the following example, there are two File Servers, OFS-1 and OFS-2. You want to remove OFS-1, but it contains files that are assigned to blueprints, so you want to move these files from OFS-1 to OFS-2
Assume that both OFS-1 and OFS-2 are registered with the same Platform Manager.
1. Manually copy the desired files from OFS-1 to the user file location of OFS-2.
2. After you have copied the files, restart OFS-2. This makes the OFS-2 database discover the new files.
3. To copy all files from super-user named PM_da16 on local File Server to user PM _da15 on a remote File Server.
4. Log in to the Linux CLI of the source File Server and run the following command (replace the IP address with the address of the destination File Server):
scp /home/tomcat/OFS1/files/PM_da16/* 10.46.27.15:/home/tomcat/OFS1/files/PM_da15
Where:
PM_da16
is the local super userPM _da15
is the remote super user OFS-1
is the source File ServerOFS-2
is the destination File Server5. Click Configuration > File Servers and select the source server name in the table. At the bottom of the page is a link to assign files to another server: Use this link to assign files on this server to another server.
6. On the Reassign File Server Files page, confirm your source File Server.
7. Select the destination File Server (OFS-2), and click Start File Reassignment. This command checks all files on the source File Server and, after confirming that the file now exists on the destination File Server, updates the database to change the assignment to the destination File Server.
CAUTION: Only files that exist on the destination server will be reassigned in Platform Manager. Files listed on the source server that cannot be found on the destination server (have not been physically moved) are skipped.
To confirm the file reassignment has occurred as intended, check the system logs and look at the associated File Server listed in the file table.
• | Navigate to Configuration > Files. |
Resource blueprints require that certain files be registered with the Platform Manager. They are then supplied to the infrastructure, as needed.
• | Upload a file. |
• | Indicate its type. |
• | Choose a file server to upload the file to. |
For every uploaded file, you can click the filename to see detailed information about the file, including size and MD5 checksum. On the Platform Manager web panel, navigate to Configuration > Files. You can also delete a file on this page.
Your file supplier should provide you with its MD5 checksum. After uploading any file, verify the MD5 checksum found on the File Server with the MD5 that came with the file. If it does not match, confirm that your local copy of the file has the correct MD5. Then delete the file on Platform Manager and do the upload again.
CAUTION: If the File Server is using a Self-Signed Certificate, the file upload may fail because your browser does not trust this certificate. In the failure message, follow the links to trust the server. Then retry the file upload. You do not need to log into the File Server for this operation.
When a file is associated with a Blueprint it becomes locked and you will not be able to delete it. You may delete any file that is not associated with a blueprint, so deleting a blueprint will unlock any associated files.
File names must be unique. When uploading a file, Platform Manager verifies that this file name is not already listed in the Platform Manager database. If a match is found, the upload will not be permitted.
When uploading a file, you indicate the file type. These types are used to categorize files for presentation in the Blueprint builder. Supported types are:
MiVoice Business (MiVB) image: This is a specially packaged version of the MiVoice Business installation software, available on Mitel OnLine. These files are referred to by MiVoice Business Multi-Instance resource blueprints. An example filename is ICP3300_13.2.1.33.tar.gz.
A MiVoice Business image file contains a MiVoice Business software image suitable for installation into the software inventory of a MiVoice Business Multi-Instance server. You need a tar file containing the MiVoice Business installation software and an md5sum file containing the MD5 checksum of the file. Mitel supplies these files.
After uploading the file to Platform Manager (File Server), verify that the MD5 checksum of the file, as it exists in Platform Manager, matches the MD5 checksum supplied with the file.
MiVoice Business (MiVB) backup file: This is a backup file produced by MiVoice Business in .tar format. These files are used by MiVoice Business Multi-Instance resource blueprints.
A MiVoice Business Multi-Instance Backup file is a golden MiVoice Business database file for use on MiVoice Business Multi-Instance servers. Following the creation of a resource on a MiVoice Business Multi-Instance server, this golden database can be restored to the MiVoice Business Multi-Instance tenant. This results in a configured MiVoice Business instance.
Mitel Integrated Configuration Wizard (MiCW) config file: This is an MiCW-produced configuration file in either .xml or .zip format. These files are used by MiVoice Business Multi-Instance resource blueprints, They typically contain an initial MiVoice Business configuration for application to a newly created MiVoice Business instance.
You can apply a configuration wizard file during creation of MiVoice Business Multi-Instance tenants. This results in creation of a configured MiVoice Business instance.
ICP3300_13.2.1.27.tar.gz
ICP3300_13.2.1.27.tar.gz.md5sum
In MiCloud Business Small Business Topology (SB), Unified Communication applications are provided by a MiCollab Client Multi-Tenant server. The MiCollab Multi-Tenant server handles UC connectivity for multiple customers. The server allows connections from users with standard phones plus mobile devices, soft phones, and smart phone devices. Connections are established over PSTN, cell phone networks and public Internet connections, allowing multiple call-paths for more mobile end-customers.
Platform Manager Platform instances may be assigned a single enterprise tenant of a MiCollab Multi-Tenant server. These enterprise tenants will be created by as needed.
When Platform Manager creates a platform instance, it allocates the appropriate UCC user licenses to the ARID of the MiCollab Multi-Tenant.
Platform Manager organizes MiCollab Multi-Tenant servers into pools based on hardware location. When Platform Manager builds a platform from a blueprint, the blueprint may indicate a MiCollab Multi-Tenant pool from which the MiCollab Multi-Tenant server is to be obtained. If the pool is unable to fulfill the request due to lack of capacity, the create operation fails. You use pools to indicate a hardware location preference. If you have no location preference, all of the MiCollab Multi-Tenant servers can be placed in one pool.
Platform Manager does not create a base license ARID for MiCollab Multi-Tenant. You must manually create an ARID with appropriate base parts and add it to the MiCollab Multi-Tenant configuration. After the MiCollab Multi-Tenant server is configured and licensed, you register it with Platform Manager. Platform Manager adds the UCC License Manager (ULM) user parts to the MiCollab Multi-Tenant ARID when creating platform instances from blueprints that specify the use of MiCollab.
When a MiCollab Multi-Tenant is registered with Platform Manager, you must supply the ARID for the MiCollab Multi-Tenant server. Platform Manager checks whether the ARID is in a ULM. If the ARID is not in a ULM, Platform Manager creates a ULM and adds the MiCollab Multi-Tenant ARID to the new ULM.
Every MiCollab Multi-Tenant ARID is in a unique ULM. When Platform Manager generates platform instances, if a platform requires MiCollab, the MiVoice Business ARIDs are placed in the same ULM as the MiCollab with which they are associated.
The Service Provider must register one or more shared MiCollab Multi-Tenant servers with Platform Manager. For each MiCollab Multi-Tenant server, you must have the following information:
• | The IP address and login credentials of MiCollab Multi-Tenant. |
• | The maximum number of enterprises supported. Platform Manager will generate up to this number of enterprises on the MiCollab Multi-Tenant. |
• | The MiCollab Multi-Tenant ARID. This ARID may already be in a ULM. If the MiCollab Multi-Tenant ARID is not in a ULM, Platform Manager creates a ULM and places the MiCollab Multi-Tenant ARID in it. |
• | The server must be licensed with a Base kit. Platform Manager does not provide base licensing to shared servers. |