XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. ilyazam
    3. Posts
    I
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 2
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: DevOps Megathread: what you need and how we can help!

      Hi,
      I use Ansible on XCP-ng hosts for a few things :

      • basic server configuration (hostname, syslog target, NTP, DNS, NUT service if needed, Dell OpenManage, ...)
      • network creation (with VLANs on existing PIFs)
      • storage creation (on local storage, it runs the xe sr-create command on a user-created partition)
      • VM creation (including bootstrap in a dedicated iPXE VLAN and network interfaces recreation after the initial iPXE boot to put the VM back on the right network). To do this my ansible playbook runs a lot of xe commands on the dom0 (vm-install/vm-memory-limits-set/vm-param-set/vdi-create/vdi-param-set/vif-create/...)

      Most of my pools are single-host pools with local storage. almost all my VMs are debian VMs.

      This process has worked well since XenServer 7.2, but it is not future-proof since Ansible dropped support for python 2.x / 3.6 in its latest release and XCP-ng doesn't provider a newer python3 release (yet ?).

      I understand that the goal is to do as few things in the dom0 as possible and use Xen Orchestra and its APIs for everything.

      I tried to use custom templates with cloud-init but I stopped using them, since they need to be stored on each pool, whereas a NFS ISO storage can be shared between pools, and iPXE boot doesn't need a "full template" with a VDI.

      I would like to have a few Ansible modules to manage VMs / hosts / storage through Xen Orchestra : to create / resize /delete VMs, create networks and storages.

      posted in Infrastructure as Code
      I
      ilyazam
    • RE: XO Community Edition - Ldap Plugin not working ?

      Hi,
      I have XO CE (built from sources on a 09/24 commit) and I use the LDAP plugin connected to a Samba4 AD controller running on Debian. I'm not sure how different it is from a real Windows AD DC.

      My config is working and looks like this :

      URI : ldap://IPv4:389
      check certificate : no
      use starttls : yes 
      Base : OU=MyOU,DC=company,DC=tld
      
      DN :
      username : CN=serviceaccount,OU=MyOU,DC=company,DC=tld
      password : the service account password
      
      user filter : (&(cn={{name}}) memberOf=CN=ADMIN_AD_GROUP,OU=Groups,DC=company,DC=tld)) 
      ID attribute : cn
      
      posted in Xen Orchestra
      I
      ilyazam