Creating Server Fleets

Last updated: 2021-06-28 10:09:36

    Overview

    This document describes how to create a server fleet, which is a group of managed resources in the form of CVM instances, to deploy game servers. The fleet size is subject to the number of instances you assign, and can be manually or automatically scaled to meet players' needs.

    Directions

    1. Log in to the GSE console and click Fleet on the left sidebar to enter the server fleet page.
    2. Select the service region in the top-left corner and click Create.
    3. On the Create Fleet page, enter information such as basic info, process management, deployment configuration, and internet.

    Basic info

    To create a server fleet, you can use asset package or image according to the resource type:

    • Asset package

      • Name: enter the server fleet name. We recommend you use a meaningful fleet name, so that it can be easily identified in the list.
      • Resource Type: select asset package or image from the drop-down list.
      • Asset Package Name: select a valid asset package from the drop-down list or create one first.
      • Description: enter the server fleet description, which is optional and used to help identify the fleet.
      • Asset Package ID, Asset Package Size, and OS will be automatically entered based on the selected asset package name.
    • Image

      • Name: enter the server fleet name. We recommend you use a meaningful fleet name, so that it can be easily identified in the list.
      • Resource Type: select asset package or image from the drop-down list.
      • Image Name: select a valid image from the drop-down list or create one first.
      • Description: enter the server fleet description, which is optional and used to help identify the fleet.
      • Image ID, Image Size and Image OS will be automatically entered based on the selected image name.
        Note:

        Using Image to create a server fleet requires authorization, which means you need to authorize the image resources to GSE. To do so, click Share > Go to CAM > Authorize.

    Process management

    Configure how server processes run on each CVM instance.

    • Launch Path: enter the path of a server executable file in the asset package. Download the asset package to the /local/game/ path on the Linux platform and to the C:\game\ path on the Windows platform. The decompressed full path of the server process is as follows
      • Liunx: /local/game/YourGameServerBuild
      • Windows: C:\game\YourGameServerBuild.exe
    • Launch Parameter: enter the information to be delivered to the server executable file during launch. It is in the format of a set of command line parameters and is optional.
    • Concurrent processes allowed: specify this configuration allows how many processes concurrently run on each CVM instance in the server fleet.
    • Max Concurrent Game Server Session Activation: set the number of game server sessions that can be concurrently activated on a CVM instance. You can select Unlimited or Limited (the maximum value is 20,000). When multiple new game server sessions are launched on one CVM instance, this limit can reduce their performance impact on each other.
    • Game Server Session Activation Timeout: enter the maximum time period for a new game server session to be activated. You can set the timeout period to be no more than 600s.

    Note:

    • Concurrent processes allowed: the total number of game processes that need to be launched for a launch path binary
    • Max Concurrent Game Server Session Activation: the number of instantaneous concurrencies of the game server sessions in “activating” state.

    Deployment configuration

    • Server Instance Type: server model of the server fleet to be created.

    • Enable VPC: after enabling access to Tencent Cloud VPC, you can access the servers and other resources in your VPC.

    Internet

    • Network Security Group: you can define the access permission to inbound traffic of your server processes. Before allowing access, you must set at least one port for the fleet.

      • Port range: specify the range of numbers of the ports that can be opened for inbound connections to the game servers. The range must be 1025–60000.
      • Protocol: select TCP or UDP as the communication protocol of the fleet.
      • IP range: specify the valid IP range for CVM instances in the fleet. You can use a CIDR block to represent a range (such as 0.0.0.0/0, which indicates that access requests from any user can be allowed).
    • Number of instances: refers to the number of CVM instances. After the server fleet is created successfully, this number can be modified on the scaling policy page in the server fleet details.

    • Protection Policy: includes time-period protection, full protection, and no protection.
      When you call the process termination API, the process will be actively terminated. If you do not call this API, one of the following protection policies will be executed accordingly:

      • Time-period protection: in case of a scaling-in or an unhealthy process, the system will terminate the process after a period of time between 5 to 1,440 minutes (60 minutes by default).
      • Full protection: the process can be terminated only when there are no processes running on the CVM instance.
      • No protection: in case of a scaling-in or an unhealthy process, the system will terminate the process after up to 5 minutes.

    1. After configuring the information above, click Create to create a server fleet.
    2. After the server fleet is successfully created, you can view, delete, or perform other operations on the server fleet page. You can also click the server fleet ID to view information such as basic information, events, instance list, scaling, game sessions, process management, ports and protocols, asset packages, and VPC.