Home
HCL Sametime® Administration Guide 12
Planning
This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
Clustering and high availability
High availability and high capacity configuration for Sametime is achieved in different ways depending on which component is being configured for HA. See the topics below to learn more about chat, meetings and MongoDB.
Configure high capacity for meetings
High availability is supported for the front-end web traffic to the Kubernetes cluster. You can deploy multiple front-ends on different physical and virtual nodes pointing to the same back-end in order to distribute load and survive a node outage.
Configuring autoscaling for video
The Kubernetes autoscaler adjusts the use of video pods based on the configured values in the video.yaml file.

HCL Sametime® Administration Guide 12
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
  - Sametime versus Sametime Premium
    Depending on the Sametime product that is installed, detemines which Sametime features are available. HCL Sametime provides secure real-time communication across devices, and HCL Sametime Premium expands those features to include video and file sharing.
  - Prerequistes
    Before you being the install process, ensure that your environment includes all prerequistes and system requirements.
  - Platforms
  - Meeting server FAQ
    The Meeting server routes media traffic.
  - Planning the network topology and connectivity
    This topic explains how Sametime components are connected and the default ports that are used. There are also example topologies to illustrate how Sametime can be deployed in different scenarios.
  - Network planning for meetings
  - Clustering and high availability
    High availability and high capacity configuration for Sametime is achieved in different ways depending on which component is being configured for HA. See the topics below to learn more about chat, meetings and MongoDB.
    - Configure high capacity for chat
    - Configure high capacity for meetings
      High availability is supported for the front-end web traffic to the Kubernetes cluster. You can deploy multiple front-ends on different physical and virtual nodes pointing to the same back-end in order to distribute load and survive a node outage.
      - Configuring autoscaling for recorder
        A recorder is used when a meeting is being recorded and when live streaming a video. The Kubernetes autoscaler adjusts the use of recorder pods based on settings in the recorder.yaml file.
      - Configuring autoscaling for video
        The Kubernetes autoscaler adjusts the use of video pods based on the configured values in the video.yaml file.
    - Configuring MongoDB for high availability
  - Managing Sametime features
    HCL Domino users are entitled to limited use of HCL Sametime chat capabilities.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Configuring autoscaling for video

The Kubernetes autoscaler adjusts the use of video pods based on the configured values in the video.yaml file.

About this task

When Sametime is installed for the first time, you must deploy a HorizontalPodAutoscaler.

Procedure

Change directories to installation_directory/ /kubernetes/autoscaling directory. Where installation_directory is the directory the install package is located.
Open the file video.yaml for editing.
Configure the minimum number and maximum number of video pods by adjusting the following settings.
```
minReplicas: minimum_value
maxReplicas: maximum_value
```
For example:
```
minReplicas: 1 
maxReplicas: 3 
```
Save and close the video.yaml file.
To deploy the video autoscaler, run the following command from the autoscaling directory.
```
kubectl apply -f video.yaml 
```
If the autoscaler has already been deployed, you can adjust the number of video nodes available. The following command can be used to adjust the number of video nodes.
```
kubectl edit hpa video
```