Varnish Software’s Varnish Cloud offering is available on Google Cloud Platform as a single virtual machine (VM), pay-as-you-go (PAYG) solution. Each VM image contains the latest version of each Varnish Software product, optimized for use with the Google Cloud Platform Compute Engine.
There are four products and eight types of VM images accessible at the current stage.
To quickly set up a Varnish Software environment on the Google Cloud Platform using GCP Marketplace:
Access the Varnish Software Inc page in the GCP Marketplace, select the product you want to try, and click the
LAUNCH ON COMPUTE ENGINE button.
In this tutorial, we deploy Varnish Custom Statistics (Red Hat) as an example.
If you are not in a project, you will be asked to Select or create a project.
If you have not registered your billing information, you will be asked to Enable free trial.
The GCP Marketplace Preview window opens to deploy the solution. Specify
External IP and
Note that: In the Firewall section, we recommended that you leave the suggested TCP port traffic checkboxes in order to allow the solution to work properly with default configurations. For more information on controlling incoming traffic, click the gray help button, which takes you to Firewalls in the Google Cloud Platform Compute Engine documentation.
The GCP Marketplace confirms that the selected Varnish Software product was deployed (see Figure 3).
As soon as the new VM launches, the main component of each product starts automatically and serves a default configuration.
There is also a small snippet on
Suggested next steps for each product to help you discover what more you can do with your instance.
To verify that VCS is working properly, point a web browser to access the public
Site address and a default VCS port and view the displayed page (see Figure 4).
Finally, configure each Varnish Cache (VC), Varnish Cache Plus (VCP) or Varnish Enterprise (VE) installation to send data to this VCS instance.
For that, you configure
vstatdprobe as explained here.
The configuration files are located in different places based on what kind of instances you are running, Varnish Enterprise (VE), Varnish Cache Plus (VCP), Varnish Cache (VC) or Varnish Custom Statistics (VCS)
In this section, we cover configuration basics. For more details and advanced configuration possibilities, please select the links below.
VCP or VE is the enterprise version of Varnish Cache (VC). Apart from ease-of-use improvements and performance enhancements, VCP also provides additional functionality, such as Varnish Massive Storage Engine (MSE), Varnish High Availability (VHA) and SSL/TLS backend support. Customers can also enable frontend SSL/TLS by using Varnish Plus Addon SSL (Hitch), which is also included with the image.
varnishd process should be running on
TCP 80 and 8443. Hitch will be running on port 443. If you have a VAC instance running in your environment, you can configure
varnish-agent to talk to VAC to see some graphs and be able to deploy Varnish Configuration Language (VCL) files to all registered Varnish Cache nodes via the VAC RESTful API.
Your Varnish instance has been pre-configured with the default settings, which suits most Varnish users. We advise you to have a look and update the configuration according to your needs.
Our documentation site has a reference section with all available runtime options. This will help you to properly configure the Varnish process.
To look at the system parameters run this command:
sudo systemctl cat varnish.service
To change the runtime options, run the following command on your Varnish instance so that you can override the default values:
sudo systemctl edit varnish.service
Edit accordingly and save the file.
And finally, restart Varnish, by running the following command:
sudo systemctl restart varnish.service
You can do the same for hitch.service
VCS should run out of the box without any additional effort. Point a web browser to the public DNS name and the default TCP port and view the page.
Due to the Google’s Open Source Program Office (OSPO) policy, we cannot make the VAC on Google Cloud Platform because VAC relies on one AGPL component. Varnish Software developers are fully aware of the problem and are working on a permanent solution.
If you encounter any problems with configuring our products, online user documentation is available here.
Customers who purchase VCP, VE or VCS VM images on the Google Cloud Platform are eligible for Varnish Cloud support and software updates provided by the Varnish Software, Inc. engineering team. To contact support, please submit the Varnish Cloud Support Activation form.
Please visit the Post Configuration for more information about what you can do with Varnish Cloud products. For example:
varnish-agentto communicate with
vstatdprobeto forward data to