Our organisation is considering Proxmox for VM orchestration, but we have stakeholders that are worried about AGPL. Specifically how AGPL might require us to release internal source code public. Can we please get some guidance?
Three or more proxmox hypervisors running an unmodified proxmox VE 6.1+ in one datacenter. Used for internal VMs and LXC Containers running: web servers, kubernetes-clusters, ldap-servers and in house developed software.
The proxmox cluster(s) is not available for any entity outside the company, we do not provide a PaaS based on proxmox. We are running internal and public services in VMs orchestrated by Proxmox. We do not provide VMs to customers, everything is for our own services only.
We will interact with proxmox through the provided API with our own ansible playbooks to spin up and shut down VMs and containers.
Will our ansible code and automation be affected by the AGPL license?
Three or more proxmox hypervisors running an unmodified proxmox VE 6.1+ in one datacenter. Used for internal VMs and LXC Containers running: web servers, kubernetes-clusters, ldap-servers and in house developed software.
The proxmox cluster(s) is not available for any entity outside the company, we do not provide a PaaS based on proxmox. We are running internal and public services in VMs orchestrated by Proxmox. We do not provide VMs to customers, everything is for our own services only.
We will interact with proxmox through the provided API with our own ansible playbooks to spin up and shut down VMs and containers.
Will our ansible code and automation be affected by the AGPL license?