XCP-ng project
-
@scottalanmiller said in XCP-ng project:
@warren-stanley said in XCP-ng project:
@olivier said in XCP-ng project:
True, it's still over 9000
Thanks a lot for your support guys. Now, we start a new adventure
So, how is the adventure going ? any updates Oliver ?
It got mentioned on
today.On where?!
-
-
How to get my coffee mug?
I didnt register a username or any address info except CC. -
Yeah, I missed the kickstarter but would love to support and buy a mug and some stickers!
-
I said Q1 for the first release. On schedule. https://xcp-ng.github.io/news/2018/03/31/first-xcp-ng-release.html
-
@olivier said in XCP-ng project:
I said Q1 for the first release. On schedule. https://xcp-ng.github.io/news/2018/03/31/first-xcp-ng-release.html
Whoo hoo, congrats!
-
Know what I'll be doing Tuesday when I'm back in work
-
@olivier said in XCP-ng project:
I said Q1 for the first release. On schedule. https://xcp-ng.github.io/news/2018/03/31/first-xcp-ng-release.html
Very exciting news.
-
@olivier said in XCP-ng project:
I said Q1 for the first release. On schedule. https://xcp-ng.github.io/news/2018/03/31/first-xcp-ng-release.html
Gratz guys!
-
Congrats on beating the deadline @olivier and xcp-ng team
-
I am going to try and upgrade my XS 7.2 test lab today.
-
@momurda Please let us know how it goes.
-
Upgrade works. Xencenter 7.4 refuses connetion to xcp-ng. Installing XO from the xcp-ng console.
The deployed xoa vm is working just fine. When you deploy this it doesnt ask when interface you want to use and wants to use dhcp. If your Network0 interface doesnt do dhcp assign a IP here for XO vm. You can change network interface and IP later.
From what i can tell there is no issue other than XenCenter not working and my lack of xp with XO.Currently trying to make a vm and i get some instructions about changing a template to a vm after i have created one and try to boot the installer ISO from remote repo. Probably just missed a checkbox when making the vm.
-
@momurda said in XCP-ng project:
Upgrade works. Xencenter 7.4 refuses connetion to xcp-ng. Installing XO from the xcp-ng console.
The deployed xoa vm is working just fine. When you deploy this it doesnt ask when interface you want to use and wants to use dhcp. If your Network0 interface doesnt do dhcp assign a IP here for XO vm. You can change network interface and IP later.
From what i can tell there is no issue other than XenCenter not working and my lack of xp with XO.Currently trying to make a vm and i get some instructions about changing a template to a vm after i have created one and try to boot the installer ISO from remote repo. Probably just missed a checkbox when making the vm.
XenCenter is really the only thing that Citrix holds a license for. So it's not surprising that XC doesn't work with XCP-ng.
Awesome to hear that the upgrade went without issue.
-
@dustinb3403 That isn't correct. Source is available on GH -- https://github.com/xenserver/xenadmin
-
@danp Right, they've talked about cloning (whatever the proper Github terminology is) the XC code and removing the copyrighted stuff, which I don't think XCP-ng is prepared to maintain as of now because they'll obviously want you to use XO anyway. The other option is to get Citrix to merge a commit allowing XCP-ng to work, which likely wont happen.
-
Regardless of XC not working, I'll probably update on my homelab, but I am a little scared of something going wrong with my XO VM and not having XC to fall back on. I might actually have to use a UUID for the first time ever.
-
@bnrstnr said in XCP-ng project:
The other option is to get Citrix to merge a commit allowing XCP-ng to work, which likely wont happen.
Or just fork the repo and build from your own modified source. First step would be to identify why XC is refusing to connect.
I am a little scared of something going wrong with my XO VM and not having XC to fall back on
Good point. I've had to run XC on several occasions when XO was inaccessible.
-
@danp said in XCP-ng project:
Good point. I've had to run XC on several occasions when XO was inaccessible.
I guess you could run the XOA command line installer and that should work to get you back up and running. Maybe it's not as big of an issue as I was originally thinking.
