In the FWIW department, I've now done four sites. Network thing I mentioned above took about an hour to figure out and was a bit confusing. Once I did one (and made a little cheat sheet on how I did it), the rest of the sites were easy.
Arch
In the FWIW department, I've now done four sites. Network thing I mentioned above took about an hour to figure out and was a bit confusing. Once I did one (and made a little cheat sheet on how I did it), the rest of the sites were easy.
Arch
@archw
Ignore that entire post...user error. I have two networks that are spelled very close to the same thing and I was using the wrong one.
Likely a dumb question:
I decided to see how NDB would affect backups.
As I understand it, you need to do it from teh command and teh command is this:
"xe network-param-add param-name=purpose param-key=nbd uuid=<network-uuid>"
I went to the command line and typed "xe network-list"
The network I use is this one:
uuid ( RO) : xxxxxxxx-yyyyy-88bc-b327-zzzzzzzzzzzz
name-label ( RW): Main Network
name-description ( RW): Active / Active (Balance-SLB)
bridge ( RO): xapi0
I then typed :
"xe network-param-add param-name=purpose param-key=nbd uuid=xxxxxxxx-yyyyy-88bc-b327-zzzzzzzzzzzz"
It accepted it without error.
If I run "xe network-list params=all" is see the field :
" purpose (SRW): nbd"
for the network above.
The only issue is that the "NBD" field does not appear in the XO screen (Master, commit f9220) for the network does not populate.
Thoughts ?
Thanks!
11 hosts and thirty something VMs (windows, linux, bsd mix) and update went fine.
I found them here:
https://pvupdates.vmd.citrix.com/
I thought installed them with all the update options. I just removed them and reinstalled with all teh options and they now show up!
Thanks!
Any updates coming for 8.3.? It seems like 8.2 had a slew come out last weekish. No biggie...all is well....just curious.
In the words of Ronald Reagan "I don't recall the answer to that question"
If I remember correctly (subject to the after effects of many happy hours since 5-12-24), I ended up rebooting the host that had that VM. It has never done it since.
Arch
I enabled automatic updates but my task scheduler doesn't show that?
@abudef Where is the task? I looked in the tasks in task scheduler and don't see it?
I moved four sites from Esxi to XCP-NG (there are about twenty ish virtual machines).
Once I figured out how to make XCP-NG work, it was relatively easy. I began by installing it on an unused old Dell.
My comments are from that standpoint of a general contractor (construction) that also does IT work so take some of my terminology with a grain (boulder) of salt.
Things that gave me some pause:
Figuring out how XOA works vs XO was somewhat confusing. I ended up watching two of Tom's videos at Lawrence Systems (shown below) to get me started.
https://lawrence.technology/xcp-ng-and-xen-orchestra-tutorials/
https://lawrence.technology/virtualization/getting-started-tutorial-building-an-open-source-xcp-ng-8-xen-orchestra-virtualization-lab/
NIC fallover - this was much easier in Esxi. It took me a night to figure out how to do the bonding thing.
The whole "NIC2:" has to be the same "NIC2:" on every machine was a pain in the a##. Again the way esxi does it is easier.
Figuring our the proper terminology to properly create a local repository
Find the disk ID of the βsdbβ or βcciss/c0d1βdisk
ll /dev/disk/by-id
use gdisk to create partions
"xe sr-create host-uuid=c691140b-966e-43b1-8022-1d1e05081b5b content-type=user name-label="Local EXT4 SR-SSD1" shared=false device-config:device=/dev/disk/by-id/scsi-364cd98f07c7ef8002d2c3c86296c4242-part1 type=ext"
Expanding an existing drive (i.e. after you grow a raid drive) was a tough (I have post on this site that shows how I did it).
Moving a VM from esxi to XCP-NG was just long and a few vomited in the process and had to be re-done. In some cases I used the built in XCP-NG migration and, in others (the huge VMs) I figured out how to do it via Clonezilla (much, much faster once I got the hang of it).
list item Having to shut down a running VM to increase the disk size is a bit of a PITA but its not that big of a deal.
Over committing memory...I still don't have a great grasp on the one.
Before I made the move, I did a ton of speed tests of esxi vs XCP-NG. About 60% were slightly faster on Esxi and 40% were faster on XCP-NG. In the end, the differences were negligible.
With all that said, I think XCP-NG is much easier to use than esxi and I like it better. Vcenter seemed to last about six months and then always died and had to be rebuilt (and the restore utility was about as reliable as gas station sushi). With XOA, it always works and is much faster than Vcenter.
The backup is awesome. With esxi I was using Nakivo.
Just my two cents!
Example of what a successful screen look like (even though it has fake work in it). Sort of like the shadow y'all put in the fields.
@rtjdamen
Boom - that worked!
I opened up an SCP session and let it take the defaults and it immediately connected. I noticed that WINSCP calls it "s3.amazonaws.com" so I changed :
AW s3 endpoint= "s3express-control.us-west-2.amazonaws.com"
-to-
AW s3 endpoint= "s3.amazonaws.com"
I also changed:
Directory="s3://mybucket123456-789-0123-4567-890123/mystuff/my-backups/"
-to-
Directory="mystuff/my-backups/"
Thanks!!
@rtjdamen
Oh...that...yeah...I've got another piece of software that pushes the info to S3 however it doesn't use a "user name". Instead it uses the S3 access key ID and secret key. Is that what you meant?
I called it the same bucket name that shows up on the S3 log in page (this is the fake name but "mybucket123456-789-0123-4567-890123" but I used the actual name of the bucket).
Oops..forgot to post that: "Xen Orchestra, commit 990c2"
Lets say this is the info for the account:
Bucket name : mybucket123456-789-0123-4567-890123
Region is US West (Oregon) us-west-2
s3 info = s3://mybucket123456-789-0123-4567-890123/mystuff/my-backups/
When setting up the remote, I set the fields as follows:
Type = "Amazon Webservices S3"
Name="Amazon Stuff"
Use HTTPS=yes
Allow unauthorized="no"
AW s3 endpoint= "s3express-control.us-west-2.amazonaws.com"
Region=<blank>
AWS3 bucket name="mybucket123456-789-0123-4567-890123"
Directory="s3://mybucket123456-789-0123-4567-890123/mystuff/my-backups/"
Set access key ID and secret key.
Since I posted the error last night, I noticed that I had the AW s3 endpoint field was incorrectly set to "US West (Oregon) us-west-2" and corrected it to "s3express-control.us-west-2.amazonaws.com"
When I finished it, I clicked ok and got a new error message that says "AccessDenied":
remote.test
{
"id": "c7b8699a-447e-4fbf-850c-04546ce9a5eb"
}
{
"name": "AccessDenied",
"$fault": "client",
"$metadata": {
"httpStatusCode": 403,
"requestId": "0299B4704E01018FBA850D1B040020ECDCE58C02",
"extendedRequestId": "JM7bWZAg",
"attempts": 1,
"totalRetryDelay": 0
},
"Code": "AccessDenied",
"RequestId": "0299B4704E01018FBA850D1B040020ECDCE58C02",
"HostId": "JM7bWZAg",
"message": "Access Denied",
"stack": "AccessDenied: Access Denied
at throwDefaultError (/opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@smithy/smithy-client/dist-cjs/index.js:838:20)
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@smithy/smithy-client/dist-cjs/index.js:847:5
at de_CommandError (/opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4748:14)
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@aws-sdk/middleware-signing/dist-cjs/index.js:226:18
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:174:18
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:98:20
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:121:14
at /opt/xo/xo-builds/xen-orchestra-202405231838/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:34:22
at S3Handler._createReadStream (/opt/xo/xo-builds/xen-orchestra-202405231838/@xen-orchestra/fs/src/s3.js:289:15)"
}
I also tried changing the Directory to:
Directory="//mybucket123456-789-0123-4567-890123/mystuff/my-backups/"
Directory="/mystuff/my-backups/"
But neither worked
Can anyone shed light on what is supposed to go in the diff fields when setting up and Amazon S3 remote?
I opened the storage at Amazon S3 and click on "Copy S3 uri" and then pasted it in the directory field. The directory field starts with "s3://"
When I try to save theremote, it gives this error.
remote.test
{
"id": "c7b8699a-447e-4fbf-850c-04546ce9a5eb"
}
{
"message": "Cannot read properties of undefined (reading 'httpStatusCode')",
"name": "TypeError",
"stack": "TypeError: Cannot read properties of undefined (reading 'httpStatusCode')
at S3Handler._sync (/opt/xo/xo-builds/xen-orchestra-202405231838/@xen-orchestra/fs/src/s3.js:462:27)"
}
I'm the president of a general contractor in the South. I've also been our IT person for 30+ years.
Last fall, when the winds of change at VMware began blowing, I started looking into alternatives for esxi. I happened upon videos about XCP-NG from Tom at Lawrence Systems and I decided to install it on a test system.
Its a great product and I've enjoyed getting to know it!