Installation¶
This document holds instructions on installing Vintner.
Script¶
Vintner can be installed on Linux x64/ arm64 and Windows x64 using our installation scripts.
Install a specific version as follows.
Install a specific version as follows.
NPM¶
Vintner can be installed using npm
, see opentosca-vintner.
Ensure, that npm bin -g
is in your $PATH
.
Yarn (Classic)¶
Vintner can be installed using yarn
(classic), see opentosca-vintner.
Ensure, that yarn global bin
is in your $PATH
.
Yarn (Modern)¶
Vintner can be installed using yarn
(modern), see opentosca-vintner.
However, this will not install Vintner permanently but only temporary.
Choco¶
Vintner can be installed using choco
, see opentosca-vintner
You might specify the latest version explicitly if this version is still under moderation.
Docker¶
Vintner can be installed using Docker, see ghcr.io/opentosca/opentosca-vintner. The Image is about 3GB large and contains tools, such as xOpera, Unfurl, Ansible, Terraform, and all of our examples.
GitHub Container Registry¶
Pull the latest image from the GitHub Container Registry.
Starting the Container¶
First, we create directories for persisting data.
Next, we start the container.
The command consists of the following aspects.
--detach
starts the container in the background.--volume ${PWD}/data:/vintner/data
persists all data written by Vintner.--volume ${PWD}/shared:/vintner/shared
should be used to share data between the host and the container, e.g., CSARs or GCP credentials.--network host
uses the host network, e.g., for ipv6 support.--name vintner
is the container name.ghcr.io/opentosca/opentosca-vintner:latest
pulls the latest Docker Image
Inside the container, the following directories are of interest.
/vintner/data
holds all data written by Vintner./vintner/shared
should be used to share data between the host and the container, e.g., CSARs or GCP credentials./vintner/examples
holds the examples directory of the repository.
Executing a Command¶
The container runs in the background. Vintner is executed as follows.
On Linux, we set an alias to directly use Vintner as command in the terminal on the docker host.
To persist the alias, add the alias, e.g., to ~/.bashrc
(requires reloading the session).
Now, Vintner is available as follows.
xOpera¶
xOpera is already installed inside the container and Vintner is already correctly configured to connect to xOpera. By default, xOpera is already enabled. Enable xOpera as follows.
Unfurl¶
Unfurl is already installed inside the container and Vintner is already correctly configured to connect to Unfurl. Enable Unfurl as follows.
Stopping the Container¶
Ensure to only stop Vintner, once Vintner is idle. Otherwise, data and deployments will be corrupted. Stop the container as follows.
Watching the Logs of the Container¶
Watch the logs of the container as follows.
Debugging the Container¶
In case we need to debug something inside the container or perform any administrative ./tasks, we can exec into the container as follows. This starts a shell inside the container.
Manual¶
Install Vintner manually by downloading the binary for your system and adding it to $PATH
.
There are no other dependencies required.
The following example shows the installation on selected platforms and architectures.
First, create the directory $env:USERPROFILE\bin
and add it to your PATH.
We recommend to do this manually.
Next, install vintner.
The following binaries are available:
Platform | Architecture | Binary | Archive | Signature | Checksum |
---|---|---|---|---|---|
Alpine | x64 | link | link | link | link |
Linux | arm64 | link | link | link | link |
Linux | x64 | link | link | link | link |
Windows | x64 | link | link | link | link |
Checksum¶
To verify the integrity of a binary, proceed as follows.
The following is a walkthrough for vintner-linux-x64
.
We assume that vintner-linux-x64
is present in the current working directory.
Signature¶
Every binary is cryptographically signed.
Verification¶
To verify a signature of a binary, first import our public key and download the respective signature.
The following is a walkthrough for vintner-linux-x64
using gpg
.
We assume that vintner-linux-x64
is present in the current working directory.
First, we import the public key.
Next, we download the signature.
Next, we verify the signature.
The output should be something as follows.
Public Key¶
The following public key shall be used for verifying signatures. The public key is also available as download.