@olivierlambert ok, that did work
cluster deployed ok it seems, ill validate it all in the morning. thanks.

debian@cp-1:~$ kubectl get pods --all-namespaces
NAMESPACE      NAME                           READY   STATUS    RESTARTS      AGE
kube-flannel   kube-flannel-ds-h2vj2          1/1     Running   0             34s
kube-flannel   kube-flannel-ds-j8s5t          1/1     Running   0             56s
kube-flannel   kube-flannel-ds-k2x5g          1/1     Running   0             107s
kube-flannel   kube-flannel-ds-nvl97          1/1     Running   0             11m
kube-flannel   kube-flannel-ds-qk748          1/1     Running   0             95s
kube-flannel   kube-flannel-ds-rqrgq          1/1     Running   0             48s
kube-flannel   kube-flannel-ds-ss7hx          1/1     Running   0             14m
kube-flannel   kube-flannel-ds-t5xt8          1/1     Running   0             6m2s
kube-system    coredns-5dd5756b68-rb82f       1/1     Running   0             14m
kube-system    coredns-5dd5756b68-rr9hb       1/1     Running   0             14m
kube-system    etcd-cp-1                      1/1     Running   0             14m
kube-system    etcd-cp-2                      1/1     Running   0             11m
kube-system    etcd-cp-3                      1/1     Running   0             6m1s
kube-system    kube-apiserver-cp-1            1/1     Running   0             14m
kube-system    kube-apiserver-cp-2            1/1     Running   0             11m
kube-system    kube-apiserver-cp-3            1/1     Running   0             5m59s
kube-system    kube-controller-manager-cp-1   1/1     Running   1 (11m ago)   14m
kube-system    kube-controller-manager-cp-2   1/1     Running   0             11m
kube-system    kube-controller-manager-cp-3   1/1     Running   0             5m58s
kube-system    kube-proxy-2w2df               1/1     Running   0             14m
kube-system    kube-proxy-6g7tt               1/1     Running   0             6m2s
kube-system    kube-proxy-h2mjc               1/1     Running   0             34s
kube-system    kube-proxy-lgvc9               1/1     Running   0             107s
kube-system    kube-proxy-pnvtg               1/1     Running   0             11m
kube-system    kube-proxy-rbg2l               1/1     Running   0             56s
kube-system    kube-proxy-v27b5               1/1     Running   0             95s
kube-system    kube-proxy-v5l7t               1/1     Running   0             48s
kube-system    kube-scheduler-cp-1            1/1     Running   1 (11m ago)   14m
kube-system    kube-scheduler-cp-2            1/1     Running   0             11m
kube-system    kube-scheduler-cp-3            1/1     Running   0             5m58s
kube-system    kube-vip-cp-1                  1/1     Running   1 (11m ago)   14m
kube-system    kube-vip-cp-2                  1/1     Running   0             11m
kube-system    kube-vip-cp-3                  1/1     Running   0             5m46s
debian@cp-1:~$ kubectl get nodes
NAME       STATUS   ROLES           AGE    VERSION
cp-1       Ready    control-plane   15m    v1.28.8
cp-2       Ready    control-plane   11m    v1.28.8
cp-3       Ready    control-plane   6m6s   v1.28.8
worker-1   Ready    <none>          99s    v1.28.8
worker-2   Ready    <none>          60s    v1.28.8
worker-3   Ready    <none>          52s    v1.28.8
worker-4   Ready    <none>          38s    v1.28.8
worker-5   Ready    <none>          111s   v1.28.8

@AlexanderK dont think you follow, i own, meaning they are my machines, 4 large bare metal hosts on public ip space, each has only 1 nic ..... with xcp-ng installed,
id like to use CS to provision them, but cant get my head around the public / private ip spaces, when all my ips are public on a /26 ... each box does have a second nic, but it is not wired to the switch, only 1 nic is, and they are in a colo, so i have only 1 port per machine.

@AlexanderK im basically trying to deploy cs with 8.2.1 where im limited in interfaces, and im on public ip space.

@olivierlambert ok, that did work
cluster deployed ok it seems, ill validate it all in the morning. thanks.

debian@cp-1:~$ kubectl get pods --all-namespaces
NAMESPACE      NAME                           READY   STATUS    RESTARTS      AGE
kube-flannel   kube-flannel-ds-h2vj2          1/1     Running   0             34s
kube-flannel   kube-flannel-ds-j8s5t          1/1     Running   0             56s
kube-flannel   kube-flannel-ds-k2x5g          1/1     Running   0             107s
kube-flannel   kube-flannel-ds-nvl97          1/1     Running   0             11m
kube-flannel   kube-flannel-ds-qk748          1/1     Running   0             95s
kube-flannel   kube-flannel-ds-rqrgq          1/1     Running   0             48s
kube-flannel   kube-flannel-ds-ss7hx          1/1     Running   0             14m
kube-flannel   kube-flannel-ds-t5xt8          1/1     Running   0             6m2s
kube-system    coredns-5dd5756b68-rb82f       1/1     Running   0             14m
kube-system    coredns-5dd5756b68-rr9hb       1/1     Running   0             14m
kube-system    etcd-cp-1                      1/1     Running   0             14m
kube-system    etcd-cp-2                      1/1     Running   0             11m
kube-system    etcd-cp-3                      1/1     Running   0             6m1s
kube-system    kube-apiserver-cp-1            1/1     Running   0             14m
kube-system    kube-apiserver-cp-2            1/1     Running   0             11m
kube-system    kube-apiserver-cp-3            1/1     Running   0             5m59s
kube-system    kube-controller-manager-cp-1   1/1     Running   1 (11m ago)   14m
kube-system    kube-controller-manager-cp-2   1/1     Running   0             11m
kube-system    kube-controller-manager-cp-3   1/1     Running   0             5m58s
kube-system    kube-proxy-2w2df               1/1     Running   0             14m
kube-system    kube-proxy-6g7tt               1/1     Running   0             6m2s
kube-system    kube-proxy-h2mjc               1/1     Running   0             34s
kube-system    kube-proxy-lgvc9               1/1     Running   0             107s
kube-system    kube-proxy-pnvtg               1/1     Running   0             11m
kube-system    kube-proxy-rbg2l               1/1     Running   0             56s
kube-system    kube-proxy-v27b5               1/1     Running   0             95s
kube-system    kube-proxy-v5l7t               1/1     Running   0             48s
kube-system    kube-scheduler-cp-1            1/1     Running   1 (11m ago)   14m
kube-system    kube-scheduler-cp-2            1/1     Running   0             11m
kube-system    kube-scheduler-cp-3            1/1     Running   0             5m58s
kube-system    kube-vip-cp-1                  1/1     Running   1 (11m ago)   14m
kube-system    kube-vip-cp-2                  1/1     Running   0             11m
kube-system    kube-vip-cp-3                  1/1     Running   0             5m46s
debian@cp-1:~$ kubectl get nodes
NAME       STATUS   ROLES           AGE    VERSION
cp-1       Ready    control-plane   15m    v1.28.8
cp-2       Ready    control-plane   11m    v1.28.8
cp-3       Ready    control-plane   6m6s   v1.28.8
worker-1   Ready    <none>          99s    v1.28.8
worker-2   Ready    <none>          60s    v1.28.8
worker-3   Ready    <none>          52s    v1.28.8
worker-4   Ready    <none>          38s    v1.28.8
worker-5   Ready    <none>          111s   v1.28.8

@olivierlambert Current version: 5.92.1 - XOA build: 20240401, XCP-
NG 8.3, yes, everything by dhcp, what else can i say... its a brand new deployment

freshly installed XCP-NG 8.3 and XOA deployed on it it, tried to deploy a simple k8s cluster from the Hub recipes for k8s, and it fails.

it does deploy a master node, and then does nothing else, just sits there and spins for hours....

any ideas ?

@olivierlambert said in Xcp-ng 8.2 no more recognized with Cloudstack since last update:

ill review the new pricing, but xcp-ng / cloud stack documentation is quite lacking. it used to be pretty much plug and play back in the day

It should be plug and play, but as I said, we always been very friendly with CS devs and we even participated to a CS event in last November. If the integration is less good nowadays, you should tell CS people, because our API is stable since it exists. We can't be blamed if it works less well (if it's even confirmed) because that's not on us

for the lazy XOA dfrom sources doesnt have alot of the features needed, like deploying K8s clusters, or templates and thats just an example

So you want turnkey and cheap/free

no, i want working and affordable, just checked the new pricing model, yes, now it appears affordable. bonus points.

i installed a fresh 8.3 the other day and got XOA on it, tried to deploy a k8s cluster, it failed. only deployed a master did nothing else, second to this i added a ssh-key to debian and installed from a template, could not login to debian, it did seem to work on almaLinux just fine

If it fails and you don't report it (or nobody does), I don't see how we could help

i have another deployment at home, ill test the k8s again in the lab, as for the ssh keys, i did mentioned it on the channel, just in case its not a bug but i did something wrong.

Yupp, thats me being frustrated.. trying to get something to work so i can move forward.

Please try to be nice, because even if you are frustrated, being not nice won't help to get assistance for free on a community forum

@olivierlambert said in Xcp-ng 8.2 no more recognized with Cloudstack since last update:

seems to me that youve moved away from CS a bit

What? We always worked with CS devs when they needed info on XCP-ng. I never used CloudStack myself, so I can't answer a specific CloudStack question, why would you would think "we moved away"?

ill review the new pricing, but xcp-ng / cloud stack documentation is quite lacking. it used to be pretty much plug and play back in the day

it forces me to use something like CS just based on costs

What x2? Why not using XO from the sources? It's 100% free. Also, we have a new pricing model that is even cheaper including everything.

for the lazy XOA dfrom sources doesnt have alot of the features needed, like deploying K8s clusters, or templates and thats just an example

seems templates and ssh-keys, appear a bit disfunnctional, as well as deploying k8s

Can you be more specific? We have many users relying on it and I'm not aware of current issues at the moment?

i installed a fresh 8.3 the other day and got XOA on it, tried to deploy a k8s cluster, it failed. only deployed a master did nothing else, second to this i added a ssh-key to debian and installed from a template, could not login to debian, it did seem to work on almaLinux just fine

bus XOA needs to die or be cost effective and functional

That's nice of you

Yupp, thats me being frustrated.. trying to get something to work so i can move forward.

@olivierlambert seems to me that youve moved away from CS a bit, it used to be quite a nice combination years back, though now probably a different story. easily with the XOA lite on 8.3 itll most likely break any integrations, gotta say kudos for xcp-ng great work, sad that the xoa pricing model is so steep, so it forces me to use something like CS just based on costs, and the latest XOA, seems templates and ssh-keys, appear a bit disfunnctional, as well as deploying k8s, all the more reasons im forced to use CS. great work on xcp-ng as i said, bus XOA needs to die or be cost effective and functional

@stormi so i got my XCP-NG on CS 4.19 following your direction, its a fresh install of both, however i seem to be missing something, there are no templates showing to boot anything in the way of compute, i thought it would pull the XCP templates, but it seems not, how to proceed? do i need to upload isos to xcp-ng for them to appear in cs ??