Introduction
A project in ZEDEDA Cloud is a logical grouping of edge nodes, edge app policies, attestation policies, and others. These are grouped together so that when an edge node joins a project, the project has all the policies predefined, and the edge nodes can be more easily managed.
When you create an edge node in your enterprise, you are prompted to assign a project to the edge node. Some planning must be done in advance to determine which policies you want your project to contain before you apply it to your edge nodes.
This is a series of articles. You will likely follow them in this order.
- Projects Overview - You are here!
- Create a Project
- Configure the Project Policies
- Manage a Project
- Use the ZEDEDA CLI to Manage a Project
Prerequisites
- You must have at least the SysManager role in your enterprise.
- You have already onboarded an edge node to ZEDEDA Cloud.
Projects: Grouping Edge Nodes for Ease of Management
When you create an edge node in your enterprise, ZEDEDA prompts you to assign that edge node to one of your projects. All the app instance deployment, network instance creation, and volume instance creation will happen automatically, according to the policies defined in that project.
Projects and Enterprises
Each project in ZEDEDA Cloud belongs to a single enterprise. When you create your enterprise, it will contain a single empty project. You may create many projects within the same enterprise.
Project Types
There are two types of projects:
- Standard: Standard project types may be used with a ‘regular’ profile, or they can be configured to use an Azure cloud profile. These types are best used for simple environments where only one edge application must be deployed to the edge nodes.
- Deployment: Deployment project types are always configured in conjunction with the ‘Regular’ profile. The “Deployment” project type is often used for ‘tiered deployments’ where more than one edge app must be deployed to a fleet of edge nodes.
NOTE: Administration of your projects is easier when you use symmetrical edge nodes, meaning that they share the same brand, model, and hardware configurations. However, symmetry is suggested but not mandatory.
Policies available under Standard and Deployment projects
When configuring a project, you are prompted to select the project type. The policies that are available under each project type differ slightly. The table below shows which types of policies are available under the different project types. Standard projects can be used to support older setups, and different profiles like Azure. Deployment projects, on the other hand, are intended for newer, more highly-automated workflows like ZTD.
| Policy Type | Standard | Deployment |
| Edge Node Attestation Policy | Yes | Yes |
| Configuration Lock Policy | Yes | No |
| Network Instances Policy | Yes | Yes |
| Edge Apps Policy | Yes | Yes |
| Edge View Policy | Yes | Yes |
| Edge Sync Policy | Yes | No |
| Edge Nodes Policy | No | Yes |
| Volume Instances Policy | No | Yes |
Access Projects in the GUI
You can access the Projects page to view details for your projects.
- Log into the GUI.
- Hover on the Administration dropdown menu.
- Select Projects from the options.
- Observe the Summary dropdown panel with infographic donuts.
- Donuts display info on Status, Profile Distribution, and Type.
- The list of projects appears in the lower portion of the table.
- In addition to Name, the table also displays project Type (standard or deployment), Profile (regular or azure), attestation status, and more. For details on the meaning of these column headings see create a project.
Next Steps
This is a series of articles. You will likely follow them in this order.
- Projects Overview - You are here!
- Create a Project
- Configure the Project Policies
- Manage a Project
- Use the ZEDEDA CLI to Manage a Project
After you’ve completed the series, you might be interested in the following articles:
- If you’re adding a project while onboarding an edge node, then you may be interested in adding an edge app from the Marketplace.
- If you’re adding a project independent of the edge node onboarding workflow, then then you may be interested in adding an edge node.