XCP-ng

jmccoy555

So after parking CoreOS for nearly a year, and after noticing some edits and commits had been made I decided to give it another go; this time with success…. Yipppeee

XCP-ng 8.0.0 with latest patches
CoreOS version is Container Linux 2303.3.0
XO from sources - xo-server 5.54.0

There are a few buts and pointers though!!

Deploying the VM did not work from XO (from sources, just a homelabber here); the config disc was not created.

So reverting to XCP-ng Centre…….

Following https://github.com/xcp-ng/xcp/wiki/Docker-in-XCP-ng for general guidance – BUT I was unable to log in with my SSH key.

This is fixed by enclosing the key in “ “ thus, my cloud-config was

#cloud-config

hostname: %VMNAMETOHOSTNAME%
ssh_authorized_keys:
  - “ssh-rsa AAAAB3NzaC……………………..syQ4cJYnG70BqQJZVqo5fGcIQP9j5UY1 user@host"
  # - ssh-rsa <Your public key>
  # The following entry will automatically be replaced with a public key
  # generated by container management plugin. The key-entry must exist,
  # in order to enable container management for this VM.
  - ssh-rsa %CONTAINERRSAPUB%
coreos:
  units:
    - name: etcd-member.service
      command: start

    # Hypervisor Linux Guest Agent
    - name: xe-linux-distribution.service
      command: start
      content: |
        [Unit]
        Description=Hypervisor Linux Guest Agent
        After=docker.service

        [Service]
        ExecStartPre=/media/configdrive/agent/xe-linux-distribution /var/cache/xe-linux-distribution
        ExecStart=/media/configdrive/agent/xe-daemon
  etcd:
    name: %VMNAMETOHOSTNAME%
    # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3
    # specify the initial cluster size using ?size=X
    # discovery: "https://discovery.etcd.io/<token>"
write_files:
  # Enable ARP notifications for smooth network recovery after migrations
  - path: /etc/sysctl.d/10-enable-arp-notify.conf
    permissions: 0644
    owner: root
    content: |
      net.ipv4.conf.all.arp_notify = 1


# Template loaded from /usr/lib/python2.7/site-packages/xscontainer/data/cloud-config.template

Following the rest of the guide everything appeared to go well.

Launching a container and then the next issue, it doesnt show in XO or XCP-ng Centre. Following this post https://xcp-ng.org/forum/topic/1679/how-to-fix-coreos-docker-container-tree-view-in-xcp-ng-center/2 and vola, all working.

Now I have a working mater a fast clone avoids any of these issues for additioanl hosts.

Creating a container without –restart always does not allow me to start / restart / stop it from XO, not the end of the world, looks like this has been found https://xcp-ng.org/forum/topic/2148/can-t-start-docker-container-from-xoa

Happy to try and help resolve any of these 'issues', test and provide logs etc. etc.

jmccoy555

@pnunn I fixed this by enclosing the key in “ “

https://xcp-ng.org/forum/topic/2404/coreos-docker-on-xcp-ng-working-ish-hopefully-this-helps-someone?_=1582131856476

Not tried with Flatcar Linux.

jmccoy555

@kcah427 did you do anything special to pass through the USB card?

I'm trying with a ASM1142 but can not boot the VM once it is assigned.

Is there a particular reason why you chose the card that you used?

Thanks.

jmccoy555

@olivierlambert said in HA questions:

except if you have an external "arbiter"

By that do you mean another install of XCP-ng on a low power machine or something that doesn't actually run any VMs?

jmccoy555

https://www.ebay.co.uk/ulk/itm/132562388180

Flash it into IT mode and problem solved in 30mins for £20 and you get the best of both worlds; XCP-ng and FreeNAS

Is SMAPIv3 needed for reliable individual disk passthrough? I always thought that this ended in desaster?? Waiting patiently so I can play with Ceph......

jmccoy555