Varnish Cloud

GCP Marketplace

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 five products and eleven types of VM images accessible at the current stage.

  • Varnish Cache 4.1 (Red Hat)
  • Varnish Cache 4.1 (Ubuntu)
  • Varnish Cache 5.2 (Red Hat)
  • Varnish Cache 5.2 (Ubuntu)
  • Varnish Cache 6.1 (Red Hat)
  • Varnish Cache 6.1 (Ubuntu)
  • Varnish Cache Plus 4.1 (Red Hat)
  • Varnish Cache Plus 4.1 (Ubuntu)
  • Varnish Custom Statistics (Red Hat)
  • Varnish Custom Statistics (Ubuntu)
  • Varnish Enterprise 6 (Red Hat)

Installing the Varnish Software VM

To quickly set up a Varnish Software environment on the Google Cloud Platform using GCP Marketplace:

  1. Access the Varnish Software 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.


    Figure 1. Product page

  2. If you are not in a project, you will be asked to Select or create a project.

  3. If you have not registered your billing information, you will be asked to Enable free trial.

  4. The GCP Marketplace Preview window opens to deploy the solution. Specify Deployment name, Zone, Machine type, Boot Disk, Networking, External IP and IP forwarding.

    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.


    Figure 2. Deployment page

  5. Click the Deploy button. 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.


    Figure 3. Varnish Software deployment

  6. 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).


    Figure 4. To verify that VCS is working as expected

  7. 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.

General information regarding the configuration of the software

The configuration files are located in different places based on what kind of instances you are running, Varnish Cache (VC), Varnish Cache Plus (VCP) or Varnish Custom Statistics (VCS)

In this section, we cover configuration basics. For more details and advanced configuration possibilities, please select the links below.

Varnish Cache (VC)

By default, varnishd process should be running on TCP 6081. Note: as of November 2018, “Varnish Cache 5.2” is not yet compatible with other products provided by Varnish Software. Development on compatibility is underway.

  • Default VCL configuration
    • /etc/varnish/default.vcl
  • Varnish Cache (VC)
    • Red Hat
      • /etc/varnish/varnish.params
    • Ubuntu
      • /etc/default/varnish

Varnish Cache Plus (VCP) and Varnish Enterprise (VE)

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.

  • Default VCL configuration
    • /etc/varnish/default.vcl
  • Varnish-agent
    • Red Hat
      • /etc/varnish/varnish.params
    • Ubuntu
      • /etc/default/varnish-agent
  • Varnish Plus Addon SSL
    • Red Hat
      • /etc/hitch/hitch.params
      • /etc/hitch/hitch.conf
    • Ubuntu
      • /etc/default/hitch
      • /etc/hitch/hitch.conf
  • Varnish Cache Plus (VCP)
    • Red Hat
      • /etc/varnish/varnish.params
    • Ubuntu
      • /etc/default/varnish
  • Varnish Plus HA
    • Red Hat
      • /etc/varnish/vha-agent.params
      • /etc/vha-agent/nodes.conf
    • Ubuntu
      • /etc/default/vha-agent
      • /etc/vha-agent/nodes.conf
  • Varnish Custom Statistics probe
    • Red Hat 7
      • /etc/varnish/vstatdprobe.params
    • Ubuntu
      • /etc/default/vstatdprobe

Varnish Custom Statistics (VCS)

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.

  • Varnish Custom Statistics (VCS)
    • Red Hat 7
      • /etc/varnish/vstatd.params
    • Ubuntu
      • /etc/default/vstatd

Where is Varnish Administration Console (VAC) on the Google Cloud Platform?

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.

Please visit Amazon Web Services (AWS) or Microsoft Azure Marketplace to purchase a VAC instance.

What if you need help?

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.

What’s next?

Please visit the Post Configuration for more information you can do with Varnish Cloud products. For example:

  • How to configure varnish-agent to comunicate with VAC
  • How to configure vstatdprobe to forward data to VCS for analysis
  • etc.