Regarding GCP, the process for deploying the server is creating a new instance with our ready-made image (see https://allegro.ai/docs/deploying_trains/trains_server_gcp/ ) - you'll have an up-and-running server which you can than configure according to your needs.
Alternatively, you can always just start a new empty instance with Ubuntu OS and manually install Trains Server using our https://allegro.ai/docs/deploying_trains/trains_server_linux_mac/ .

SuccessfulKoala55 I looked back into my configuration settings for the VM(I already created a VM instance from the custom image yesterday) and thats where I got my external IP from. I checked "Allow HTTP access" but it's giving me a gateway timeout error now and telling me that the server at the IP is unreachable at the moment.

SuccessfulKoala55 At the time, yes it was v0.15.1. How do I actually launch trains server from the custom image? Do I use the external IP associated with the VM or are there any other steps I have to take?

SuccessfulKoala55 Actually- just resolved this. I had to allow access from all ports(not secure but will fix that asap) but everything seems to be running now, thanks for the help!

Regarding the trains server SDK, the end of the documentation for GCP says 'Next step, configuring trains for trains server' where the first step is running trains-init setup wizard

GiddyTurkey39 , GCP image for 0.16.1 is now available (use https://storage.googleapis.com/allegro-files/trains-server/trains-server-0-16-1.tar.gz )

Yeah, you should run trains-init on your development machine to set up the Trains SDK for using your new server

Regarding the server, the new v0.16.1 version is not yet available as an image for GCP (it will probably be available today or tomorrow), so I guess you installed v0.15.1?

Hi GiddyTurkey39 , are we talking about two different issues? One is the Trains Server on GCP, the other is installing trains on your machine?

Of course, no matter which path you choose, you'll need to make sure it's possible to access Trains Server ports ( 8080 , 8081 , 8008 ) using the server's external IP.
In GCP, you can do that by choosing " Allow HTTP Access " when creating a new instance (easy, but less secure), or set up a more detailed and secure firewall rules that will only allow access to ports 8080 , 8081 and 8008 (you can consult GCP documentation for that).

GiddyTurkey39 , trains-init is related to configuring the Trains Python SDK, not for configuring the server.
You can read more on server configuration https://allegro.ai/docs/deploying_trains/trains_server_config/ .

As for the IP not being reachable - this seems like an infrastructure issue - I recommend simply creating a new instance and using the new 0.16.1 image

The path for setting up trains-server on GCP is deploying the server, and then configuring the trains server, from my understanding. I'm unable to run trains-init to setup, as it tells me the command isn't found.