Production zones enable serving from various locations, with a CI/CD pipeline for safe deployments. This guide goes through the minimal steps for a production deployment - in short:
There are alternative ways of deploying at the end of this guide, too.
Add deployment.xml to the application package root (next to services.xml):
Modify services.xml - minimal example:
For production deployments, at least 2 nodes are required for each
cluster to ensure availability during maintenance tasks and upgrades.
nodes-section is also where you specify your required resources:
Also note the minimum redundancy requirement of 2:
To help ensure a reliable service, there is a minimum resource requirement for nodes in the production environment. The minimum is currently 0.5 vcpu, 8Gb of memory, and for disk, 2 x memory for stateless nodes, or 3 x memory for content nodes. As the disk resource is very cheap, we recommend it should be allocated generously to ensure it does not limit the use of more expensive cpu and memory resources.
Give the deployment a name and log in:
$ vespa config set target cloud $ vespa config set application mytenant.myapp $ vespa auth login
The tenant name is found in the console, the application is something unique within your organization - see tenants, applications and instances.
Just as in the getting started guide, the application package needs the public key in the security directory. You might already have a pair, if not generate it:
$ vespa auth cert -f Success: Certificate written to security/clients.pem Success: Certificate written to /Users/me/.vespa/mytenant.myapp.default/data-plane-public-cert.pem Success: Private key written to /Users/me/.vespa/mytenant.myapp.default/data-plane-private-key.pem
Observe that the files are put in $HOME/.vespa. The content from data-plane-public-cert.pem is copied to security/clients.pem. More details on data-plane access control permissions.
Package the application and deploy it to a production zone:
$ vespa prod deploy
Find alternative deployment procedures in the next sections.
vespa prod deploy command to prod zones,
which uses deployment.xml
differs from the
vespa deploy command used for dev/perf zones - see
Instead of using the Vespa CLI, one can build an application package for production deployment using zip only:
$ zip -r application.zip . \ -x application.zip "ext/*" README.md .gitignore ".idea/*"
Deploying an application with Components is a little different from above:
See Getting started java for prerequisites. Procedure:
$ mvn vespa:compileVersion \ -Dtenant=mytenant \ -Dapplication=myapp
$ mvn -U package -Dvespa.compile.version="$(cat target/vespa.compile.version)"