Get started | 6 - Create an allocation
To scale the server hardware (the number of bare-metal machines and cloud servers) your game uses, you need to set up an allocation. An allocation is a set of rules which include payload definition, hardware configuration and scaling strategy, as well as the geographic regions to which the rules apply. Note that the Test project allocation below assumes you are using cloud server only.
To create allocations in the zeuz control panel:
In the zeuz control panel, go to the Allocations page (Orchestration > Allocations).
Click + ADD ALLOCATION to open the fields on the page.
Complete the fields as follows for Basic Information, Payload Definition, and Hardware Configuration.
There are two fields to complete in this section, Description and Region.
|Region||Select the region you are in|
There are two fields to complete in this section, Image and Command.
|Image||Select: zeuz test project:0.0.1|
|Command||Delete the default text and enter:|
INFO: About Payload Definition
In the Payload Definition : Image field:
- You select the version of the image you want to use. For this tutorial, it’s zeuz test project:0.0.1.
In the Payload Definition : Command field:
binaryactivenameis the game server’s executable file name which zeuz uses to check what game servers are running (this content is required).
- If the game server has a launch script, this is the path and file name of the script.
- If the game server does not have a launch script, this is the path to the game server’s executable (binary) file.
execargsare additional settings that zeuz uses to pass connecting clients to the game server, including ports (these are required), and identification variables (this are required).
Find out more:
- Payload definition in the Glossary
- Game executable file to payload definition in Payload lifecycle
There are no fields to complete, leave them all as the default.
|Hardware configuration||Min. machine spec||Payload quota|
|Core count||Leave as default||Leave as default|
|Clock rate (Mhz)||Leave as default||Leave as default|
|Memory (MB)||Leave as default||Leave as default|
|Storage (GB)||Leave as default||Leave as default|
|IO bandwidth (MBps)||Leave as default||Leave as default|
|Internet bandwidth (MBps)||Leave as default||Leave as default|
|Payloads per machine||Uneditable field|
INFO: About Hardware Configuration
The Hardware configuration : Min machine spec column:
- This is where you add the specification of bare-metal machines you are using.
- If you are using cloud server only, this does not apply, so do not change the default values.
- If you are using bare-metal machines, you get this information from zeuz support.
The Hardware configuration : Payload quota column:
- This is where you set the number of payload instances you want to run on your server hardware (bare-metal machines and cloud server).
- You can leave it as the default for this tutorial or change the values.
With zeuz, you can set up the most efficient configuration to get the maximum payload instances running per server hardware machine (bare-metal machines and cloud server).
The Hardware configuration : Payloads per machine field:
- The zeuz orchesration service uses your settings in this field to calculate the payloads per server hardware machine (bare-metal machines or cloud server).
- For maximum efficiency, you want as many payload instances per server hardware machine as possible, depending on the requirements of your game server.
Find out more:
There is one field to complete in this section, Max amount of cloud machines (at the bottom). Leave the rest as the default.
|Free payload capacity|
|Max amount of bare-metal machines||Uneditable field|
(When you use cloud server only.)
|Max amount of cloud machines|
Note: Make sure you change this setting from the default of 0.
INFO: About Scaling Rules
The scaling rules you set up tell the zeuz scaler what server hardware machines (bare-metal machines or cloud servers) to allocate. The scaler bases this on the number of game server instances (measured in “payloads”) you have running and the number you have on standby.
Find out more:
- Scaler documentation for an introduction to unreserved payloads and free payload capacity
- Documentation on Payloads in an allocation in Payload lifecycle for an introduction to allocation set up and scaling rules
- Scaling rules
- Payload scaling
After you have completed the fields, make sure you save your updates: click SAVE in the top right of the page.
Note: The allocation might take a few seconds to display on the page.
On the same page, enable the allocation: toggle STATUS : DISABLED to ENABLED.
(Click OK in the Enable Allocation confirmation dialog box.)
zeuz now assigns your server hardware machines. (For this Test project tutorial, zeuz assigns cloud servers but if you are setting up your own game, zeuz assigns bare-metal machines and/or cloud servers, depending on how you have set up your allocation.)
Go to the Machines page (Orchestration > Machines) to see the server hardware machine’s CPU usage.
Note: When you use cloud server, this can take several minutes to display on the page. This is due to the time it takes for cloud servers to spin up. If you don’t see any active machines CPU usage on the page after five minutes, check Troubleshooting: No Active Machines, below.
Image: the Machines page on the zeuz control panel, showing CPU usage
- You might need to refresh the page.
- Make sure you copied the text correctly in the Payload Definition : Command field on the Allocations page.
If you can see data under Active Machines on this page, you have successfully set up zeuz orchestration.
zeuz is ready to spin up a game server of your game. Now you can test your client-server connection.
Now go to 7 - Test the client-server connection.
2021-sep-09 Page updated with editorial review: execdelay command setting deprecated.
2021-jun-30 Page updated: updated url for ZCP.
2021-may-19 Page updated with editorial review: clarification of zeuz terms.