Repository navigation
Expand file tree
/
Copy path.env.example
More file actions
70 lines (61 loc) · 4.13 KB
/
Copy path.env.example
File metadata and controls
70 lines (61 loc) · 4.13 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
# =============================================================================
# NeOps Lab - Environment Configuration
# =============================================================================
# Copy this file to .env and adjust values for your environment. docker compose
# reads .env automatically; the Makefile greps it (it never sources it).
# `make lab-env` never overwrites an existing .env, so compare yours against
# this file after pulling.
# -----------------------------------------------------------------------------
# Local Lab Images (optional)
# -----------------------------------------------------------------------------
# A locally-built image (no registry host, e.g. neops-web-client:latest) is not
# pullable: docker resolves it as docker.io/library/... Both paths already
# handle that, so an override here needs no extra flags:
# * `make local-env-{init,up}` pull with `--ignore-pull-failures`, so the
# unpullable local tag is warned about instead of aborting the target;
# * `docker compose up -d` reads `pull_policy: missing` from the compose
# files and uses the local image without contacting a registry at all.
# Override the web client image used by the local lab stack, e.g. to run a
# locally-built image instead of the published one.
# Defaults to quay.io/zebbra/neops-web-client:develop
# NEOPS_WEB_CLIENT_IMAGE=neops-web-client:latest
# Override the CMS image, e.g. to run a locally-built core instead of the
# published one. Build it with `make -C ../neops-core build-docker flavor=cms-free`.
# Defaults to quay.io/zebbra/neops-cms-free:develop. The pin below holds the CMS
# at neops-core 2.4.0, the first with network zones: engine 0.46.0 refuses every
# worker until it has read the zones from the CMS, so the two move together.
# NEOPS_CMS_IMAGE=neops-cms-free:latest
NEOPS_CMS_IMAGE=quay.io/zebbra/neops-cms-free:2.4.0
# Tag of the developer preview, used by the engine and the monitor app alike.
# Unset, it is `develop`; the pin holds the engine at the release the worker
# pin below needs. The image override below wins over it.
NEOPS_ENGINE_TAG=0.46.0
# Override the workflow engine image (also used for the monitor app service).
# Unset, it is the public developer preview, or the full licensed engine for a
# scenario whose scenario.json asks for it (network-zones does); the licensed
# engine needs `docker login quay.io`. Set, it wins over the scenario, e.g. to
# point at a local build:
# NEOPS_WORKFLOW_ENGINE_IMAGE=quay.io/zebbra/neops-workflow-engine:develop
# NEOPS_WORKFLOW_ENGINE_IMAGE=neops-workflow-engine:latest
# Override the worker image. The lab runs the published worker SDK image; point
# this at a locally-built neops-worker-sdk:latest to exercise SDK changes here
# before they are released. `pull_policy: missing` finds the local image and
# skips the registry.
# Defaults to quay.io/zebbra/neops-worker-sdk:develop. The pin below holds the lab
# on the 0.5.0 release instead, which needs engine 0.46.0 or later. Discovery
# names global_discover_network 0.2.0, which ships first in 0.5.0; an older
# worker carries 0.1.0 only and `wait_ready` times out. When you pin another
# tag, check it carries that block, apply_configuration 0.1.1, which the SPIE
# scenario names, and device_update_device 0.2.0, which network-zones names:
# docker run --rm --entrypoint sh <image> -c 'grep -n "version=(0, 2, 0)" neops/fb/base/global/discover_network.py'
# docker run --rm --entrypoint sh <image> -c 'grep -n "version=(0, 1, 1)" neops/fb/base/network_device/apply_configuration.py'
# docker run --rm --entrypoint sh <image> -c 'grep -n "version=(0, 2, 0)" neops/fb/base/device/update_device.py'
NEOPS_WORKER_SDK_IMAGE=quay.io/zebbra/neops-worker-sdk:0.5.0
# -----------------------------------------------------------------------------
# Scenario
# -----------------------------------------------------------------------------
# Which lab the compose files mount. The Makefile exports this for every target,
# so it is only needed when you run `docker compose` by hand. `make scenarios`
# lists what is available, and `make scenario-resolve SCENARIO=<name>` has to
# have run before the mounts below resolve.
# SCENARIO=wan-and-fabric