Purpose of this feature

This new feature allows Furioos organizations to use their own cloud GPU server infrastructure for streaming applications, instead of relying on the GPU servers provided by Furioos.
This allows for greater flexibility and customization in terms of GPU power, CPU power, RAM, choice of Cloud Provider, number of concurrent users, and machine availability.

With this feature, you can install a Furioos streaming server on any compatible device and connect it to the Furioos session manager to make it visible on your Furioos account.
When a user starts an application, one of your servers will be used to stream the application.

It’s worth noting that during the BETA phase, Furioos is not charging for this service, but you will be responsible for the server costs.

Disclaimer

⚠️ BETA feature – Please read before using ⚠️

The ‘Bring Your Own Infrastructure’ BETA feature, when activated on an application, disables the Virtual Machines provisioning and orchestration provided by Furioos for that application.

You will be responsible for running your application on your own Cloud GPU server infrastructure (one GPU Virtual Machine per user).

It’s important to note that you will be responsible for ensuring the compatibility, latency, bandwidth, geographical proximity, and operation of your GPU server fleet to your users.
You will also be responsible for orchestrating your GPU servers (startup, shutdown, etc.) as well as any associated usage costs.
For instance, remember to shut down your cloud servers when not in use to avoid being charged by your Cloud Provider.

It’s important to note that using this feature requires knowledge in virtual machine administration.
Before proceeding with this feature, it’s necessary to be proficient in managing cloud servers, disk images, and other cloud administration related tasks.Please also keep in mind that we will not be providing support for tasks related to the management of your cloud provider.

Your Cloud Provider will handle the billing for your Cloud GPU server usage.

Furioos will not launch a session on its GPU server infrastructure if your traffic exceeds your server capacity.

As a general rule, use this BETA feature ONLY FOR TESTING PURPOSES.
Please be aware that this feature may be unstable and will be updated regularly.
If you encounter any issues please contact support or check the troubleshooting guide for assistance. 

Server(s) Requirements

The ‘Bring your Own Infrastructure’ feature is available for all servers meeting these requirements:

Hardware requirement

• Windows 10, Windows Server 2019, or Windows Server 2022
• NVIDIA Graphics Card
• Cloud Virtual Machines must have the latest Nvidia GRID drivers installed (please read your Cloud Provider’s documentation)
• Port 8084 must be open (Egress)
• Port 80 must be open (Ingress)
• Port 443 must be open (Ingress)
• Your Virtual Machine(s) must be accessible through RDP, VNC or similar Remote Desktop app.

Unique Furioos Server Name

Each server you bring through the BYOI feature will be given a unique Furioos server name.
It’s important to note that you have the ability to customize the base name of each server, and a unique ID will be added to it.

Please be aware that the Furioos Server name is different from the name you may have assigned to the server through your cloud provider’s interface.

Unique public IP address

For the proper functioning of this feature, it’s necessary that each server is equipped with a unique public IP address.
This means that servers that are part of a local network, which typically possess different private IP addresses, will not be able to connect to the orchestrator at this time.
However, Virtual Machines obtained from a Cloud Provider are expected to work properly as they are assigned unique public IP addresses.

💡TIP: Not sure you make the difference between Public and Private IP? Read this article or ask your DevOps Administrator.

Client Requirements

All devices that are compatible with Furioos can receive a stream from a server that is brought in through the ‘Bring Your Own Infrastructure’ feature.
To ensure your device is compatible with Furioos, you can use our Furioos Troubleshooter tool.
It’s important to note that the bandwidth, latency and network rules are determined by the server you bring in through the ‘Bring Your Own Infrastructure’ feature.

Current limitations

At this time, servers using the Bring Your Own Infrastructure feature are unable to stream audio. However, we are actively working towards including this feature in the near future.

Persistent Storage

Unlike the default behavior proposed by Furioos, BYOI sessions do not reset virtual machines at the end of the session.

This means that the data stored on the hard disk during the session is preserved for subsequent sessions on the same virtual machine.

The main advantage is that an application that has been launched once will be much faster to launch in the next session on the same machine.
The progress in a game or the modification of configuration settings will also be preserved from one session to another on the same machine.

Don’t forget to take this into account when creating your BYOI applications.

Installation

Set up your Furioos Account

Generate a BYOI Token

Make sure you are part of the Furioos’ ‘Bring Your Own Infrastructure’ Beta program

• From your Furioos Settings page, click on the ‘Bring Your Own Infrastructure’ menu (1)
• Then, click on the ‘+’ button to generate a new BYOI Token (2)

Download the Streaming Server Installation Scripts

• The Streaming Server Installation Scripts can be downloaded from your BYOI interface on Furioos (1).

If the Streaming Server Installation Scripts are updated, the latest version can be obtained through the link provided.
Keep in mind that updating the Streaming Server may require reinstalling the package on all your Virtual Machines, which in turn may necessitate rebuilding your disk images.

Create virtual machines (Google Cloud Platform)

⚠️ The following is for information purposes only. Please make sure you ask your DevOps Administrator to create Virtual Machines properly ⚠️

Create your VM Instance

• From your GCP Console, click on ‘Create Instance’ (1)

Set Up your VM Instance

• Give your VM a name (1)
• Choose the region where your Virtual Machine will run
  Make sure this region has GPU Virtual Machines available (2)
• Make sure you create a GPU Virtual Machine and select which type of GPU you need (3)
• Make sure ‘Enable Virtual Workstation (NVIDIA GRID)’ is checked (4)
  ⚠️ Please note Nvidia GRID is not available for all GPU types ⚠️
• Choose your Virtual Machine type (vCPU, RAM) (5)
  Make sure you select a Machine capable of handling your 3D applications properly (use the Furioos Stats panel to monitor your VM performances)
• On GCP, make sure you check ‘Enable display device’ (6)
• Set up your Boot Disk (7) (See next section)
• Click ‘Create’ to create your Virtual Machine

Set up your Boot Disk

• Select ‘Public Image’ (1)
• Select Windows Server as the Operating System (2)
• Select the version of Windows Server you want to install (Furioos supports either Windows Server 2022 or Windows Server 2019) (3)
  ⚠️Windows Server CORE is not supported ⚠️
• Select your Boot Disk type (ideally SSD persistent disk) (4)
• Configure the size of your Boot Disk depending on the size of your applications (ideally > 200 GB) (5)
• Validate by clicking ‘Select’

Create virtual machines (Microsoft Azure)

⚠️ The following is for information purposes only. Please make sure you ask your DevOps Administrator to create Virtual Machines properly ⚠️

Create your VM Instance

• From the Microsoft Azure Console, click on (1) New, then (2) Azure Virtual Machine

Set Up your VM Instance

• (1) Give a name to your BYOI server
• (2) Choose the region where your BYOI will run (make sure the region has available GPU servers)
• (3) Make sure you select a Windows Server 2022 disk image for your BYOI server
• (4) Make sure you select a Virtual Machine with NVIDIA GPU ( for instance NC4as_T4 models)
• (5) Give your Virtual Machine a name and a password
• (6) Make sure you can access the VM via RDC (or similar technology) to continue the Furioos BYOI installation process.

• (1) From the Azure Portal, select the Virtual Machine you created during the previous step and click on the “Networking” button in the settings.
• (2) Click on the “Add Inbound Port Rule” button
• (3) Add port 80 – TCP – Any Source
• (4) Add port 443 – TCP – Any Source

Setting up your GPU server as a Furioos server

First, connect to your virtual machine (Usine RDP or the Remote Desktop tool of your choice), and paste the Streaming Server installation Script you downloaded in the previous steps.

Click on the first .bat file (1-InstallFurioosPrerequisites) to start the installation 

Let the Script install all the prerequisites

Currently, only one action is required (Microsoft Xbox 360 Accessories Setup)
Accept the agreement (1) and click next (2)

Once prompted, click enter to restart your Virtual Machine

Click on the second .bat file (2-InstallFurioosGCP) to continue the installation

Let the script install all the required files and drivers

Once prompted, press enter to restart

Connect again to your Virtual Machine
Open byoi-config.ini in C:/Furioos/config (1) (2)

Give your virtual machine a name:

• This name is different than the Virtual Machine name you gave to your cloud provider.
• This name will be displayed in your Furioos BYOI admin panel
• Furioos will automatically add a random identifier at the end of the machine name, making it possible for Disk Images to be used more easily.
• Paste your BYOI Token 
• Save and Restart the Virtual Machine

Once your Virtual Machine is restarted, it is now visible from the BYOI Admin Panel
This Virtual Machine can now be used to create a Disk Image you can reuse for your future Virtual Machines.

Start / Stop your Virtual Machine(s)

⚠️ Please be aware that if you choose to use the ‘Bring Your Own Infrastructure’ feature, you will be responsible for managing your fleet of Virtual Machines.

Furioos does not offer server orchestration for this feature yet
You will need to manually turn on and off your Virtual Machines from your Cloud Provider’s console or any other orchestrator you might use. ⚠️

You can manage your Virtual Machine Fleet from your Cloud Provider’s Console (1) (2)

Check the connection and start streaming

Check your server(s) status

To check your Streaming Server(s) status, from your Organization’s Setting page, go to the ‘Bring Your Own Infrastructure’ category (1) and click on the ‘BYOI Virtual Machines’ Tab (2)

You will find a list of your Streaming Servers in a table with different rows:

• Machine Name: The prefix name you gave to your Streaming Server in the config.ini file, plus a random suffix we generate to keep every machine name unique.
• IP Address: The PUBLIC IP address of your Streaming Server.
• Started: The date and time your Streaming Server started.
• Status: Your Streaming Server’s current status (updated automatically)
• Available Slots: The number of Concurrent Users your Streaming Server can support. (Currently, Furioos supports only one user per Streaming Server)
• Application Name: The name of the application running on your Streaming Server.

💡TIP: Don’t hesitate to add useful information to your Streaming Server’s name, such as which Cloud Provider the Server is running from, information about the Server’s GPU type, etc.

Streaming Server’s Status List

Set up your application to use your GPU servers

Click on the ‘Edit’ button of one of your applications hosted on Furioos (1)

Then go to the ‘Virtual Machine Configuration’ from the Edit page and enable ‘Use my own GPU Server Infrastructure (1)

Once the ‘Use my own GPU Server Infrastructure’ is enabled (1), don’t forget to validate by clicking the ‘Save’ button (2)
Your application is now set up to use your GPU server fleet instead of the Virtual Machines provided by default by Furioos.

To check if one of your applications is set to use the ‘Bring Your Own Infrastructure’ feature, check the Virtual Machine type from your application’s card.
If the VM type is set to ‘custom’, your app will use your GPU servers fleet only (1)

Start streaming your application

You can now start streaming your application as usual.
Either by clicking the ‘Start’ button (1) or by creating and sharing iFrames or Share Links. (2)