https://alwaldend.com/tags/xcp-ng/ Recent content in Xcp-Ng on Alwaldend Hugo en https://alwaldend.com/docs/third_party/org_xcp_ng/ Mon, 01 Jan 0001 00:00:00 +0000 https://alwaldend.com/docs/third_party/org_xcp_ng/ <h2 id="links">Links<a class="td-heading-self-link" href="#links" aria-label="Heading self-link"></a></h2><ul> <li>Download: <a href="https://updates.xcp-ng.org/isos/8.3/">https://updates.xcp-ng.org/isos/8.3/</a></li> </ul> https://alwaldend.com/docs/infra/xcp_ng/ Mon, 01 Jan 0001 00:00:00 +0000 https://alwaldend.com/docs/infra/xcp_ng/ <p>The dc1 DNS configuration maps <code>xcp-ng.alwaldend.com</code> and <code>host1.xcp-ng.alwaldend.com</code> to <code>192.168.1.213</code>.</p> <p>Terraform lives in <code>internal/tf</code> and declares the pinned <a href="https://docs.xen-orchestra.com/automation/terraform-provider"><code>vatesfr/xenorchestra</code> provider</a>. It includes empty provider and HTTP backend blocks, with no resources, endpoints, or credentials. The provider requires Xen Orchestra connected to the XCP-ng pool when resources are added.</p> <p><code>al.lua</code> authenticates with the <code>src_infra_xcp_ng</code> Vault AppRole and configures the HTTP backend using <code>secrets/alwaldend.com/vault1/approles/src_infra_xcp_ng/tf_backend</code>. The AppRole is declared in <code>infra/vault/tf</code> and must be provisioned before running the Terraform commands. Provider connection settings are left to the operator.</p>