User Tools

Site Tools


zededa:workshop:01_projects

This is an old revision of the document!


Projects

A Project is the top-level organizational unit in ZEDEDA Cloud. All resources (edge nodes, app instances, networks, volumes, images, datastores, and policies) are created and managed within a project context. Access control is scoped to a project: users and API tokens are granted access per-project.

What It Is

  • Groups edge nodes, applications, networks, datastores, and policies under one namespace
  • Controls access: users and API tokens are scoped and permissioned at the project level
  • Every resource created in ZEDEDA Cloud must belong to a project
  • Projects can have tags for filtering and reporting

Flow: ZEDUI to API to Edge Node

ZEDUI

  1. Navigate to Projects in the left sidebar
  2. Click Create Project
  3. Enter a project name, optional description, and tags
  4. Assign users and define their roles (Admin, Operator, Viewer)
  5. Click Save

Terraform

resource "zedcloud_project" "workshop" {
  name        = "workshop-project"
  title       = "Workshop Project"
  description = "EVE-KVM workshop project"
  tag {
    key   = "env"
    value = "workshop"
  }
}

API

POST /v1/projects
{
  "name": "workshop-project",
  "title": "Workshop Project",
  "tags": { "env": "workshop" }
}

What Happens on the Edge Node

  • The edge node receives its project assignment via the ZEDEDA controller at the next heartbeat interval (default 60 seconds)
  • The device config baseline (network policies, app allowlists, attestation requirements) is delivered as part of the project config bundle
  • No direct action is taken on the node during project creation; the node pulls its config on next check-in
zededa/workshop/01_projects.1780243497.txt.gz ยท Last modified: (external edit)