Elastic clusters in BYO Cloud environments

For Bring-your-own (BYO) Cloud environments, you can configure the system to automatically size your Cameyo environment based on fluctuating or dynamic system needs.

Set up a primary server

You can set up a primary server with all apps, as you would for a single Cameyo server.

1. On the Cameyo Admin console, select Servers .
2. From the list of servers, click the server that you want to designate as the primary server.
3. On the server details page, select Details > Commands > Make Elastic.
4. Specify the basic settings for all dynamic created servers within that cluster. In general, you should use the same instance size for the cluster than what you've been using for the primary server. This can be changed later as needed:
   1. Region
   2. Instance size
   3. Snapshot
5. Click Create.

You are redirected to the elastic cluster page.

Set up your elastic cluster

You can define cluster features like Secure Sockets Layer (SSL), Solid State Drive (SSD), Graphics Processing Unit (GPU) based on your needs. Note that features like SSD and GPU will have an impact on the cost of your cloud instance.

To configure your elastic cluster:

1. Rename your cluster to a meaningful name.
2. Configure the Instance features. These features have icons, and the names appear on hover.
   1. For GPU, make sure the selected region supports GPU, otherwise the creation of elastic servers will fail. For more details, see GPU regions and zones | Compute Engine Documentation | Google Cloud.
   2. For SSL, each server will get a random name with the pattern: https://companyname-random.cameyo.net and the certificates will automatically be deployed.
3. Configure Power management.

   Note: Configure working days and times according to the time zone set on the left-hand side in the General section, followed by the inactivity shutdown timeouts for the server within and outside your work hours. Your elastic servers will be automatically shut down if no user is connected to the server for the specified amount of time. If you want your servers to automatically power on at the beginning of your workday (make sure you configure it a bit earlier than when users start to work), check Auto power-on.

   1. Working days 
   2. Workday start time
   3. Workday end time
   4. Inactivity shutdown timeout:
      1. During work hours
      2. Outside work hours
4. Customize Elasticity to decide how many servers you want to pre-create and whether you want to have a certain number of servers powered on automatically within work hours.

   1. For Baseline snapshot, select Dynamic snapshot.

   2. Set the number of instances (elastic servers).

   3. For Maximum instance capacity, define the maximum capacity at which instances still accept sessions. In most cases it should remain at 100%. The Rollover capacity threshold defines when the next server should start to spin up (by either reaching 80% of CPU or RAM). For example, when your server has 8GB RAM and the threshold is set to 75% and the overall used RAM of this server goes beyond 6GB RAM it starts up the next elastic server.

5. Click Save.

Perform server maintenance

Server maintenance keeps a server software updated and running smoothly so that a computer network functions properly and avoids downtime or loss of data. Regular server maintenance keeps the server running as expected and helps avoid a total or partial network failure.

Auto-maintenance Maintenance