Server Admin Guide: A Tale of Two Servers: BIOS, GPU, and NUMA Tuning for XCP-ng: Preserving the valuable work done by Tobias Kreidl (@tjkreidl)
-
That GitHub HTML-bundle pain is real, especially when whatever exported the pages dragged in half the surrounding site CSS and sidebar widgets along with the article. You spent the time writing the originals; the file-wrangling shouldn't be what costs you another evening.
If it's useful, I'm up for taking the cleanup off your hands. Concretely:
- pull the HTML you saved from the repo (or a zip / branch you point me at)
- strip out the noise: scripts, sidebars, navigation, anything that isn't the article body and its images
- convert to markdown, one file per article, images kept alongside
- open a PR against tobiaskreidl/Citrix-Tobias-Kreidl-Collection (https://github.com/tobiaskreidl/Citrix-Tobias-Kreidl-Collection) so you stay the owner and only have to review and merge
If the saved bundles are too far gone, I'd fall back to the Citrix URLs @john.c surfaced and pull clean copies via the Wayback Machine. Same end result on your repo.
Separately, and only if that lands cleanly, I'd love to talk to Thomas Moraine and the docs team at Vates about whether parts of this could find a home on docs.xcp-ng.org, linked back to your repo with full credit. The NUMA-affinity page I pointed at earlier is shallow next to what you wrote, and the BIOS / GPU-scheduler material has no current equivalent at all. Whether the 2019 specifics still map cleanly onto current XCP-ng versions and hardware is a separate conversation; even as an archived reference, it's more than what's there today.
No pressure, no obligation. If you'd rather keep iterating on the repo yourself, that's fine too. But if a clean-the-HTML-and-PR-it pass would save you a week of GitHub-tool frustration, I'm genuinely up for it. Just point me at the bundle.
-
@poddingue Good evening. Honestly, I'd be totally fine with your taking over a full copy of everything over to XCP-ng and augmenting it over time as new information becomes available. It'd stand a better change of longevity there than in my hands, and all I'd ask for is acknowledgement for the original work. There's no real need for me to keep a totally separate copy of the materials, which would only lead to confusion as things likely would diverse over time.
As mentioned above, there are more forum articles and such out there, and when I have time, I'll see if I can hunt some more of those down, as well.
I really appreciate what you folks are doing at XCP-ng and the time and effort you're putting into your products. Above all, the feedback and communication have been better than pretty much anyone else I've ever dealt with in the IT industry.
P.S. @johnnezero did a super summarizing job with his "Series Overview & Quick Reference" that includes some of the most useful commands in addition to a synopsis of each of the articles. Very impressive! -
Folks, I made the effort to convert the first blog article from PDF to MS Word .docx format where I was able to much more easily edit it and clean it up. It's now there along with the messier PDF version on the Github site. When I get a chance. I plan to tackle the other two articles. Thank you for your patience. Note that to see the Word Doc, you have to download it as Github itself doesn't render it.
-
I saw you'd started converting Part 1 to Word for editing. You can skip the other two if you want. I went ahead and did all three.
I pulled the originals from the Wayback Machine captures of the old mycugc.org posts (the archive still had your screenshots and the data tables intact), converted them to Markdown, and opened a PR on your repo:
https://github.com/tobiaskreidl/Citrix-Tobias-Kreidl-Collection/pull/1
It adds one
.mdper article alongside your existing PDFs, with the images pulled out into a folder and the GPU scheduler and cache-latency tables kept as real tables. The point is they render inline on GitHub now, so no more downloading a file just to read it. Nothing of yours is touched, and you stay the owner: review and merge, or tell me what to move around. I made a few calls on file names and layout that are easy to change if you'd rather have them another way.If it lands cleanly and you're up for it, I'd be glad to talk to the docs team about whether any of it could also live on
docs.xcp-ng.org, linked back to you with full credit. No rush on that, and entirely your call. -
@poddingue Wow, fantastic! Your time and efforts are most appreciated. And I'd be more that willing to have the contents put on the docs.xcp-ng.org site. I'm just pleased that the information still can be found useful and will be able to serve the community for some time to come.
My only question is with these additions, is it possible to view the full articles similar to how the PDF and improved Word documents I hacked render that first article? I'm afraid I'm not savvy enough about Github to understand this. Many thanks again!
-
@tjkreidl Hi,
You can see how it renders in branch view, part 1 for example: https://github.com/gounthar/Citrix-Tobias-Kreidl-Collection/blob/add-markdown-versions/tale-of-two-servers-part-1-bios.md -
@pierrebrunet Yes, that looks very good. Some of the images are stacked instead of side-by-side, but who cares?
Thanks ever so much again! -
@tjkreidl My pleasure.
-
@poddingue I am confused is how your updated articles can be accessed somewhere on my main Github page. I only see them if I follow your "pull" link. What needs to be done to commit them?
Thank you! -
Honestly, the confusion makes total sense; GitHub does a great job of hiding this stuff. Here's what's going on: those markdown files only exist right now as a proposed change sitting on a branch. That's the whole reason you can only get to them through the pull link, and nowhere else. They become a real, permanent part of the repo the moment you merge them in. And since it's your repo, that merge is yours to do, no special GitHub-fu required. Open the PR page (https://github.com/tobiaskreidl/Citrix-Tobias-Kreidl-Collection/pull/1), scroll down a bit, and click the green Merge pull request button. That's the "commit" step you were asking about.
There's one wrinkle worth knowing about, and it's the real reason none of this shows up on your main repo page. Your repository has a couple of branches. Your existing PDFs and the Word doc live on a branch called XenServer-Articles, so I pointed my PR at that same branch to drop the markdown right next to them. But the page GitHub shows when someone visits your repo is a different branch called main, which at the moment only holds a README. So even after you merge, the articles will sit on XenServer-Articles, not on that front page. That's actually been true of your PDFs all along; it's nothing my PR changed.
If you'd like the articles to show up on the landing page too, there are two easy ways, and I'm happy to do either one for you. We can change the repo's default branch to XenServer-Articles in Settings > Branches, so that one becomes the front page. Or I open a second small PR copying everything over to main. Just tell me which you'd rather have.
So the short version: merge the PR to make the markdown real, then we can decide whether you also want the front page pointing at the articles. No rush at all on that second part.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login