plam503711

11 ms·

1.
XCP-Ng/Xen on Arm with System76 and Ampere(xcp-ng.org)
3 points by plam503711 10mo ago|0 comments
2.
VMScape and why Xen dodged it(virtualize.sh)
123 points by plam503711 1y ago|38 comments
3.
Remote, Hybrid, Office? Yes(virtualize.sh)
13 points by plam503711 1y ago|0 comments
4.
by plam503711 1y ago
Vates is the company doing both XCP-ng and Xen Orchestra, and now selling support for both in a single "bundle" called Vates VMS.
5.
by plam503711 1y ago
I'm not sure you are aware about the cost of migrating from one virtualization platform to another, especially when you have 4000 VMs. I can tell you it's not exactly easy, and that's even our business now (migrating from VMw
6.
by plam503711 1y ago
It is not, but yeah, we also have NASA as customers. However, we do not chase specifically aerospace companies. We are simply an open source alternative to VMware. So doing an ad explaining how to literally git pull the product without even
7.
by plam503711 1y ago
"forgettable infrastructure component": this is what runs their entire IT. We build both the hypervisor and the backup/orchestration for it. Our stack could kill their entire operations if it's down because $whatever. 40
8.
by plam503711 1y ago
I'm open to discuss, please add me on LinkedIn :) (you can find it in the author icon at the end of the blog post)
9.
by plam503711 1y ago
Well, now I’ve seen it — and yes, lesson learned. But here’s the good news about humanity: they’re the only ones abusing it at this scale. So far, it seems most people still choose sanity over spreadsheets of throwaway emails.
10.
by plam503711 1y ago
We operate globally, and this company isn’t even on our continent. On top of that, it’s a semi state-operated entity — so you can probably imagine where any legal effort would end up: somewhere between bureaucratic limbo and /dev/
11.
by plam503711 1y ago
I first write my entire text and then after that I use a LLM to fix the grammar and have a better flow. I'm doing my best but I'm not a native US speaker. Before LLMs, people complained about the weird sentences or mistakes I made
12.
by plam503711 1y ago
I’m actually considering reaching out directly to the CEO and telling the full story. But honestly? There’s a good chance he’s fully aware — and totally fine with it. That’s part of what makes it so disappointing. We’re not rushing into leg
13.
by plam503711 1y ago
You're absolutely right that businesses act within whatever constraints exist — and yes, we were a bit naive. We assumed that if someone had a fully functional, free, open source version available (well-documented and easy to install),
14.
Ground control to Major Trial(virtualize.sh)
526 points by plam503711 1y ago|191 comments
15.
by plam503711 1y ago
Someone got the ref, finally ;)
16.
by plam503711 1y ago
We do not have any unpaid internship. So yes, I will hire them, until we reach a limit of mentors for them, because we cannot leave them alone.
17.
by plam503711 1y ago
That's entirely true (yeah I'm biased), frankly that's one of the best place in France for IT. And a lot cheaper/less stressful than Paris :p
18.
by plam503711 1y ago
100% agree and that's exactly what we do. Almost all of our juniors are near the office. Because they need to see what's working at a company means at least once in their life. There's few exception when we don't have th
19.
by plam503711 1y ago
I agree. If it's already hard for simpler stacks, you can imagine how hard it is for more critical or complex ones. And it's even worse if you inherited some of it (ie collecting technical debt that's not yours, which is th
20.
by plam503711 1y ago
Hi, I respectfully disagree with much of your comment. First, this wasn't intended as a promotional piece. It's a personal blog post where I share some of the challenges involved in building a full virtualization stack — a stack t
21.
by plam503711 1y ago
Because we cannot afford that, we aren't Google, and still a relatively small company vs the task of building a full-stack virtualization solution. Luckily, we have other strong points helping a lot (remote first, no micro-management,
22.
by plam503711 1y ago
Sure, let me explain it a bit better. It's more like in the sense of the "stack" is very deep now. Clearly, we have/hire Xen/hypervisors specialist, and we do not ask them to be CSS experts. However, deeper in the s
23.
by plam503711 1y ago
It's true but until some extent. When you are talking about a hypervisor (like Xen), and many many subtle things depending on your CPU brand/model, it's really really *hard*, even with an LLM (and even more with an LLM halluc
24.
by plam503711 1y ago
I agree but there's also the extra difficulty to do mentoring remotely (we are a remote first company). I *really* like being remote first and provide the choice if you want to work on site or wherever you want. But it does come with s
25.
by plam503711 1y ago
Hi! It's not a promotional piece of something, it's my personal experience as a CEO and co-founder of a company using Xen as the core of our stack. I like to share my views in a transparent fashion on how it's hard to do very
26.
You can't git clone a team(virtualize.sh)
115 points by plam503711 1y ago|111 comments
27.
by plam503711 1y ago
Nice catch! Fixing it now.
28.
by plam503711 1y ago
Hi, I’m the author of the blog post. The goal wasn’t to dive deep into technical internals this time, but rather to share some perspective on what it actually takes to master an entire virtualization stack — especially after years of workin
29.
by plam503711 1y ago
That's because of the confusing names. Xen is not XenServer: * Xen is the hypervisor, the "upstream" used by both XenServer & XCP-ng * XenServer or XCP-ng is the platform, using Xen and various other things, to deliver a
30.
Few build Hypervisors. We're one of them(virtualize.sh)
15 points by plam503711 1y ago|6 comments

More ›