Embed Size (px)
Citation preview
2.6 | May 2016 | 3725-69502-001/BDEPLOYMENT GUIDE
Polycom® RealPresence® Media Suite on Amazon Web Services
ii
Copyright© 2016, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc.
6001 America Center DriveSan Jose, CA 95002 USA
Trademarks Polycom®, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries.
All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom.
Java is a registered trademark of Oracle America, Inc., and/or its affiliates.
Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document.
Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages.
End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. The EULA for this product is available on the Polycom Support page for the product.
Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc.
Open Source Software Used in this Product This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by email at [email protected].
Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. Email your opinions and comments to [email protected].
Polycom Support Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more.
Content
Polycom, Inc. 3
Content
Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services . . . 1RealPresence Media Suite AMI Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Hardware Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Resource and License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Set Up RealPresence Media Suite on Amazon Web Services by CloudFormation . . . . . . . . . 2
Set up RealPresence Media Suite on Amazon Web Services Manually . . . . . . . . . . . . . . . . . . 4
Accessing RealPresence Media Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Access RealPresence Media Suite from an Intranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Access RealPresence Media Suite from the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change the Role of the RealPresence Media Suite in Scalability Mode . . . . . . . . . . . . . . . . . . 8
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 1
Deploying Polycom® RealPresence®
Media Suite on Amazon Web Services
Check the following when you install a Polycom® RealPresence® Media Suite Amazon Machine Image (AMI):
● RealPresence Media Suite AMI Installation Prerequisites
● Accessing RealPresence Media Suite
● Set up RealPresence Media Suite on Amazon Web Services Manually
RealPresence Media Suite AMI Installation PrerequisitesRealPresence Media Suite AMI supports a deployment on Amazon Web Services (AWS). Before you install and configure the RealPresence Media Suite system, you need the following:
● An AWS account to login AWS.
● A web browser where you access the Viewer Portal. See the Accessing RealPresence Media Suite for the supported versions.
Hardware SpecificationThe following table shows the hardware specifications for the RealPresence Media Suite on AWS.
Resource and License ManagementFor the first installation of RealPresence Media Suite AMI, the 90-day trial license provides 6/3 capacity and Platinum functionality. To permanently enable the RealPresence Media Suite system, a RealPresence Media Suite license is required.
RealPresence Media Suite AMI Hardware Specification
Simultaneous Recording Ports
Live Stream
Instance Type vCPUs Memory (GiB)
Minimum Accessible Storage
Software Requirements
2 1 m4.xlarge 4 16GB 80GB AWS
6 3 m4.2xlarge 8 32GB
12 6 c4.4xlarge 16 30GB
18 9 c3.8xlarge 32 60GB
40 0 c3.8xlarge 32 60GB
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 2
Set Up RealPresence Media Suite on Amazon Web Services by CloudFormationThe following steps assume you are familiar with deploying AMI into an AWS environment.
For more information about deploying AMI on AWS, see the AWS Support Center.
To check the RealPresence Media Suite AMI:
1 Log in the Amazon Web Service on http://aws.amazon.com/.
2 Select EC2 under Compute.
3 Click Launch Instance under Create Instance to launch RealPresence Media Suite AMI.
4 Check Shared with me under Ownership, and click My AMIs from the left panel.
5 Make sure the MediaSuite AMI is under the folder.
To create a key pair:
1 Log in the Amazon Web Service on http://aws.amazon.com/.
2 Select EC2 under Compute.
3 Select Key Pairs from the left panel under Network & Security.
4 Click Create Key Pair.
5 Enter the name of the key pair, and click Create. A new key pair is created, and deliver the key to you local PC.
To deploy the RealPresence Media Suite by CloudFormation:
1 Get and record the RealPresence Media Suite template URL from the Polycom.
2 Log in the Amazon Web Service on http://aws.amazon.com/.
3 Select Service > CloudFormation.
4 Click Create Stack.
5 Select Specify an Amazon S3 template URL, and enter RealPresence Media Suite template URL.
6 Click Next to create a new stack.
7 Configure the following settings:
Stack Parameters
Parameter Description
Stack name Specify a stack name. The instance name is the same as the stack name.
MediaDiskCapacity Specify the size of the disk for media storage. Polycom recommends to set the size larger than 120 GB.
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 3
8 Click Next.
9 Specify the key value of the key to specify the instance, and click Next.
10 Check all the configuration information of the instance.
MediaSuiteAllocateEIP Specify whether allocate an Elastic IP to the stack.
Since the Public IP and Public DNS are changed automatically after the instance is restarted, Elastic IP must be created for Media Suite Center to keep IP address and RealPresence Media Suite FQDN stable.
The number of Elastic IP for one account is limited by AWS. Polycom recommends to set Elastic IP for Media Suite Center, and use private IP for Media Node.
In Scalability Mode, if the Public DNS is changed for IP address change, the FQDN of Media Node updates automatically, but the FQDN of Media Suite Center must be updated in Admin Portal manually.
Polycom recommends selecting Yes for Media Suite Center, and No for Media Node.
MediaSuiteAvailableZone Select the zone that you want to add the RealPresence Media Suite.
MediaSuiteKeyName Select the Media Suite Key that you created.
MediaSuiteLicenseType Select the license type. The license type is used to determine the EC2 instance hardware type. The license should be activated from RealPresence Media Suite Admin Portal.
MediaSuiteMasterIP Do not enter the value for Media Suite Center. Enter Media Suite Center private IP for creating the Media Node instance.
MediaSuiteNodeRole Specify the role of the RealPresence Media Suite. Select Center for the Media Suite Center and Slave for the Media Node.
MediaSuiteRelease Select the version of software that is being installed.
MediaSuiteVpcId Select the Virtual Private Cloud (VPC) where you want to deploy the RealPresence Media Suite.
Note: Media Suite Center and Media Nodes must be in the same region
In scalability mode, Media Suite Center and Media Nodes must be in the same region, but can deploy in the different zones.
Stack Parameters
Parameter Description
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 4
11 Check I acknowledge that this template might cause AWS CloudFormation to create IAM resources, and Click Create.
A new instance is created after the status changes use from CREATE_IN_PROGRESS to CREATE_COMPLETE.
You can get the stack information from Outputs tab.
Set up RealPresence Media Suite on Amazon Web Services ManuallyPolycom recommends to deploy RealPresence Media Suite by template. If deploy by template failed, using the following way to deploy RealPresence Media Suite manually.
To deploy the RealPresence Media Suite AMI on AWS:
1 Log in the Amazon Web Service on http://aws.amazon.com/.
2 Select EC2 under Compute.
3 Click Launch Instance under Create Instance to launch RealPresence Media Suite AMI.
4 Check Shared with me under Ownership, and click My AMIs from the left panel.
5 Find your MediaSuite AMI, and click Select.
6 Choose an instance type for MediaSuite AMI.
The vCPUs and Memory (GiB) must meet the RealPresence Media Suite hardware requirements. See the Hardware Specification for more about hardware requirements.
Choose EBS only for Instance Storage (GB).
7 Click Next: Configure Instance Details to configure instance information.
8 Select MediaSuite Role for IAM role.
9 (For Media Node only) Click Advanced Details to configure Media Suite Center information:
1 Select As text.
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 5
2 Enter the following information in the text box:
ROLE=SLAVE
CENTER_IP=x.x.x.x (the private IP of the Media Suite Center)
10 Click Next: Add Storage.
11 Click Add New Volume to add storage for storing media files, and specify the size of the new volume in Size. For Volume Type, only General Purpose SSD(GP2) is supported.
If you want to delete the volume when the instance is terminated, check the box Delete on Termination.If the Delete on Termination is selected, all media files stored in volume are deleted at the same time when the instance is terminated. You must backup the media files before terminating the instance.
12 Click Next: Tag Instance.
13 Specify the key value of the key to specify the instance, and click Create Tag.
14 Click Next: Configure Security Group to configure firewall rules.
15 Create a new security group, or select an existing security group from the list. A security group defines the firewall rules for the instance. The ports used for RealPresence Media Suite refer to the Polycom RealPresence Media Suite 2.6 Release Notes.
You can create a new security group before launching an instance by selecting NETWORK & SECURITY > Security Groups > Create Security Group on the left panel. For more information, refer to AWS Support Center.
16 Click Review and Launch to check all the configuration information of instance, and click Launch.
17 Select an existing key pair or create a new key pair for entering in the RealPresence Media Suite console from the pop-up window.
18 Check the agreement, and click Launch Instance to launch the RealPresence Media Suite instance.
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 6
19 Go through all the help information on the page, and click View Instance to check the instance status. The instance is in initializing status, and the initial progress will takes several minutes.
When the instance status is changed to running, AWS assigns two IP addresses: a public IP and a private IP to instance. The private IP can be used for internal communication, and the public IP is for portal access.
20 Use the following steps to assign the Elastic IP to the instance. Since the Public IP and Public DNS will be changed automatically after the instance is restarted, the Elastic IP must be created for the instance to keep the IP address and RealPresence Media Suite FQDN stable.
In Scalability Mode, if the Public DNS is changed, the FQDN of Media Node updates automatically, but the FQDN of Media Suite Center must be updated in Admin Portal manually.
1 Click Elastic IPs under Network & Security from the left panel.
2 Click Allocate New Address, and click Yes, Allocate to allocate a new Elastic IP.
3 Right click the new address, and select Associate Address.
4 Select the Media Suite Center instance from the Instance drop-down list.
5 Click Associate.
21 Access the RealPresence Media Suite Admin Portal using the Elastic IP.
For first-time start up, use the RealPresence Media Suite Fast Configuration Wizard to get you up and running as soon as possible. For more information about the Fast Configuration Wizard, refer to System Initialization Using the Fast Configuration Wizard in the Polycom RealPresence Media Suite Administrator Guide.
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 7
Accessing RealPresence Media SuiteAfter RealPresence Media Suite is deployed on AWS, the users or endpoints can access the RealPresence Media Suite from Internet and Intranet, as shown on the following network diagram.
Access RealPresence Media Suite from an IntranetWhen RealPresence Media Suite is deployed on AWS, if the users or endpoints are in the Intranet inside a company firewall, IT administrator must configure the mapping policy on the company firewall to implement the call and live streaming. For the ports used for configuration, refer to the Polycom RealPresence Media Suite 2.6 Release Notes.
For H.323 or SIP recording, RealPresence Media Suite must register to Polycom® RealPresence® DMA 7000 through Polycom® RealPresence® Access Director™. For H.323 or SIP settings, refer to Configure Signaling Settings in the Polycom RealPresence Media Suite Administrator Guide.
Deploying Polycom® RealPresence® Media Suite on Amazon Web Services
Polycom, Inc. 8
Endpoints or Polycom® RealPresence® Collaboration Server (RMX®) in the Intranet call or receive the call from RealPresence Media Suite through RealPresence Access Director.
Access RealPresence Media Suite from the InternetWhen RealPresence Media Suite is deployed on AWS, the users on the Internet can access user portal of RealPresence Media Suite directly.
For H.323 or SIP recording, endpoints in the Internet and RealPresence Media Suite must register to RealPresence DMA 7000 through RealPresence Access Director. For H.323 or SIP settings, refer to Configure Signaling Settings in the Polycom RealPresence Media Suite Administrator Guide.
Endpoints in the Internet can call or receive the call from RealPresence Media Suite through RealPresence Access Director.
Change the Role of the RealPresence Media Suite in Scalability Mode
To change the RealPresence Media Suite role:
1 Right-click the desired instance, and select Instance State > Stop from the menu to stop the running instance.
2 Right-click the stopped instance, and select Instance Settings > View/Change User Data from the menu.
3 Add or change the parameters in the pop-up window:
Change role from Media Node to Media Suite Center:
ROLE=CENTER
Change role from Media Suite Center to Media Node:
ROLE=SLAVE
CENTER_IP=x.x.x.x (the private IP of the Media Suite Center)
4 Click Save to save the setting.
5 Right-click the instance, and select Instance State > Start from the menu to restart the instance.
Caution: Change of role may cause data loss
In scalability mode, you can change the RealPresence Media Suite role when the instance is stopped which may cause data loss.
