Sites and agents
Admin 3 · 3:49
A new site joins your Weik.io installation by enrolling its agent, and the agent's capabilities decide which deployments placement puts on it. Until a matching agent is online, a production deploy is refused.
What it covers
- A production deploy refused because no online agent matches it
- Sites, leaf nodes and the one outward link to the hub
- Writing a site bundle with
weikio agent enrol fi-01 - Capabilities on agents and requirements on deployments
- The agent's page in the admin UI, with its capabilities, projects and environments under Configuration
- Taking an agent out of placement with
weikio agent drain, and back withweikio agent undrain
Commands in this video
Terminal
$ weikio deploy sandbox/hello --env production --version 0.1.0
$ weikio agent enrol fi-01 --host linux-compose --capabilities os=linux,region=fi,environment=production --projects sandbox,finance --via public
$ weikio get agents
$ weikio agent drain fi-01
$ weikio agent undrain fi-01Transcript
- 0:01This video connects a new agent to the hub, so hello can also run in production.
- 0:10The hub is the platform's central server, with agent dev online.
- 0:15hello runs in the devtest environment of project sandbox, at version 0.1.0.
- 0:25The published address is the hub's public name.
- 0:30Production is protected and empty.
- 0:37The production deploy of hello is the next step.
- 0:41No online agent matches it, so the platform refuses the deploy.
- 0:46The error names the command that would fix it.
- 0:53A site is a host with an agent and a leaf node.
- 0:56The leaf node keeps one outward link to the hub.
- 0:59It links to the published address, so the site needs no inbound port.
- 1:04The agent at this site is fi-01.
- 1:11weikio agent enrol fi-01 writes the site bundle to its own folder.
- 1:18The bundle holds eight files, the compose file and the credentials among them.
- 1:24The setup step runs off camera. It installs the agent and starts it.
- 1:32weikio get agents lists fi-01 as online.
- 1:40The admin UI has the same fields in its Enrol agent dialog.
- 1:48A capability is a key and value pair an admin writes on an agent.
- 1:53The operating system an agent reports never becomes a capability.
- 1:57A requirement is what a deployment needs, and its environment is one of them.
- 2:02Placement puts it on every agent that matches,
- 2:05so the production deploy runs on fi-01.
- 2:13The agent's own page is the one to read.
- 2:16Its Overview names the agent, its host and its status, and the integrations it runs.
- 2:22Under Configuration, Placement lists what is placed here and the capabilities,
- 2:27projects and environments the agent serves.
- 2:34To take an agent out of placement, drain it.
- 2:39The drain confirms it,
- 2:40then prints what keeps running and the lines that move or stop it.
- 2:48Undrain clears the draining state, and the agent is back in its placement.
- 2:57The hub is the platform's central server.
- 3:00The published address is its public name.
- 3:02The site connects through its leaf node.
- 3:05The site's agent is fi-01, and the hub's is dev.
- 3:10hello's production deployment runs on fi-01.
- 3:15Environments are devtest and production.
Next in this track
Admin 4 · 3:00 Watching the whole installation Watched