Code Repositories #
All Deevnet projects are hosted on GitHub: github.com/deevnet
The tenants that live in Deevnet for good have repositories of their own: see Tenants.
deevnet.builder
Ansible collection for workstations, artifact servers, PXE boot.
deevnet.mgmt
Management plane and centralized services.
deevnet.net
Network-focused Ansible collection (OPNsense, Omada).
ansible-inventory
Central inventory for platform infrastructure.
provisioning-api
The Deevnet API: the service tenants build themselves through.
terraform-provider
The deevnet/deevnet Terraform provider.
image-factory
Packer builds for Raspberry Pi and Proxmox templates.
tenant-fabric
The tenant fabric, the reusable tenant module, and the index registry. Substrate side — tenants themselves live elsewhere.
tenant-tdemo
The tdemo tenant as Terraform — the demonstration tenant built from the tenant factory's reference implementation.
deevnet-docs
This documentation site.
Repository Layout #
dvnt/
├── ansible-collection-deevnet.builder/
├── ansible-collection-deevnet.mgmt/
├── ansible-collection-deevnet.net/
├── ansible-inventory-deevnet/
├── deevnet-image-factory/
├── deevnet-provisioning-api/
├── terraform-provider-deevnet/
├── deevnet-tenant-fabric/
├── deevnet-tenant-tdemo/ the demo tenant
├── deevnet-tenant-<name>/ one per tenant
└── deevnet-docs/
The API and the provider publish their own documentation: Deevnet API and Deevnet Terraform Provider.
All repositories are designed to be cloned into a common parent directory (typically ~/dvnt/ or /srv/dvnt/).
Tenants get their own repositories #
A tenant is not a directory inside a substrate repo. Each one is
deevnet-tenant-<name>, and that repository is the tenant: its network, its workloads and its DNS
records are declared there and rebuilt from there
(
ADR-0006).
The split is what makes the tenant contract real rather than aspirational — a tenant’s recurring
lifecycle touches no substrate repository at all. New tenants are created by copying
examples/tenant/ out of the tenant factory, never by copying a live tenant.
Getting Started #
# Clone all repositories
mkdir -p ~/dvnt && cd ~/dvnt
git clone git@github.com:deevnet/ansible-collection-deevnet.builder.git
git clone git@github.com:deevnet/ansible-collection-deevnet.mgmt.git
git clone git@github.com:deevnet/ansible-collection-deevnet.net.git
git clone git@github.com:deevnet/ansible-inventory-deevnet.git
git clone git@github.com:deevnet/deevnet-image-factory.git
git clone git@github.com:deevnet/deevnet-tenant-fabric.git
git clone git@github.com:deevnet/deevnet-tenant-tdemo.git
git clone git@github.com:deevnet/deevnet-docs.git
Standards Authority #
deevnet-docs is authoritative — if a project conflicts with standards defined here, standards win.
Other repos may include it as a git submodule at docs/deevnet/.