You can launch your instances in GCP via the Marketplace. Simply search for "Continuent" to view all the listings available.
Once subscribed you can then start to configure your instance. When choosing the instance size there are a number of factors to take into account
Images do not deploy with a database installed, in most cases a t3.medium will be sufficient, however should you choose to install a database locally, then you should increase the instance size to suits the needs of the database you are configuring.
How much data are you replicating? Each instance launches with a 40Gb partition. Tungsten Replicator will store THL logs on this partition. A THL log is similar to a MySQL binary log and contains all the transactions and data we are replicating. These files are kept by default for 7 days. If you are replicating significant amounts of data you may need to increase this volume and/or consider reducing the THL retnetion which can be done during the instance configuration.
Quantity of instances and their Location
As mentioned earlier, you will need at least one "Tungsten Replicator for MySQL Extraction". Ideally this should reside in the same region and zone as the source database that you are extracting from.
You will need at least one "Tungsten Replicator for xxxx Appliers" where xxxx relates to the target type. Ideally this should reside in the same region and zone as the target database.
The source and target replicator instances do not have to reside in the same region, and can replicate globally. They can even be used to replicate into and out of GCP between on premise instances and other cloud providers.
For more details and to understand the different topologies, see Deploying MySQL Extractors and Deploying Appliers. Whilst the launch wizard on the launched VM will assist you to pre-configure a single extractor or applier service, users with advanced understanding of Tungsten Replicator can manually configure for more advanced topologies such as Fan-In and Fan-Out.
Based on your business rules, you will need to configure the appropriate network rules to allow you to access the host via your chosen terminal application, additionally you will need to allow communication between all nodes within the deployment, and to allow your instanes to communicate with the source and target database insances. A full breakdown of the network requirements can be found here: Configuring Network and SSH Environment
After luanching your instances, you can now proceed to configure them, see Chapter 4, Configuring Instances through the Launch Wizard for instructions