Skip to main content

3 posts tagged with "orchestration"

View All Tags

ยท One min read
Dorian Jolivald

IMS zeuz already offers game server orchestration, plug and play with our IMS Matchmaker or your own backend. We now have introduced the ability to reach out to Quality of Service Ping Beacons to provide the best gaming experience to your players.

Each of our server region now deploys UDP-base Ping Beacons your game client can reach out to for latency measurement. Feed that information to your matchmaker backend to allow for dynamic QoS based region selection.

ยท One min read
Claus Strasburger

We are glad to announce the beta launch of our advanced DDoS protection for IMS game hosting.

Even though many game hosting providers come with some baseline DDoS attack protections, they are often ineffective against more sophisticated attacks. We have joined force with industry leading DDoS protection providers to give you a best-in-class solution.

The solution offers a network mitigation capacity of over 155 Tbps, instant threat detection, and a time to mitigate (TTM) under 3 seconds for most threats. It will protect your game against the most sophisticated and multi-vector DDoS attacks.

ยท 2 min read
Brooke Hatton

Allocation region ๐ŸŒโ€‹

Screenshot showing the allocation region dropdown, with 5 regions available

Gone are the days of remembering and manually entering cluster IDs. Creating an allocation just got easier. Now you just select from your available regions in the allocation form.

Clusters IDs are still used on the API side, so we have included the Cluster IDs in the UI making it easy to look up which cluster an allocation is running on.

Image manager API ๐Ÿ“ทโ€‹

Some of you like to build out your own internal tooling that allows you to deploy your game servers to IMS. One frequently requested feature was an API to view and manage game server images.

Today we have opened up access to the Game Image Inventory API, this allows you to perform common operations: list, get, and delete. It uses the same authentication flow as the IMS zeuz APIs so should plug straight into your workflows.

You can find out more in the OpenAPI spec

More consistent CLI output ๐Ÿ’…โ€‹

We know the IMS CLI hasn't always been the most consistent, so we recently overhauled the output over every command, resulting in a cleaner, more consistent output.

  • Log lines are categorized into Info, Warning, Success, and Error, and color is used to make these easy to differentiate.
  • The mix use of Lists and Tables has been replaced with just Table outputs. These tables have been designed to closely match the UI and be more consistent across commands
  • JSON output-type support has been added to all commands where appropriate (for example image publish)
  • Spinners are used to indicate tasks in progress.

When using the JSON output type we still output the pretty "human" log lines, these are forwarded to stderr so that your terminal still displays them, but they do not impact your ability to parse the JSON output which is forwarded to stdout.

Additionally, since the color and styled output may interfere with CI tooling such as Jenkins we default to plaintext output when the --ci flag is present. You can override this behavior with the --output-type flag.