I don't know anything about this particular site, but I presume it's one of the new mega gpu sites.
I'm seeing many people in the comments with an early 2000's era concept of datacenters. The scale of these new sites is mind boggling. Take your idea of a typical datacenter building. Make it 4x bigger. Then put 4 of them together into a cluster. Then imagine 10 of those clusters at the site.
There's going to be continued support from local electricians, low voltage wiring vendors, various facilities service companies, HVAC, and now plumbers.. lots of plumbers. So many leaks. A site like this is going to have probably a few hundred full time people on site all the time in addition to the contracted folks.
A DC does not have a few hundred full time people on site 24/7, it's going to be less than a dozen. It takes much, much less people to run a data center than people think.
I would imagine there aren't too many electricians in Yeehaw, Minnesota, trained and qualified to do gigawatt data center installs. So they'll freight in contractors to do that work, and maybe temporarily employ a few locals for a month or two for auxiliary stuff.
More generally, this is the universal playbook when someone wants to dump some megaproject on a community that doesn't want it: This will create X jobs and inject $Y into the local economy. Can you name one case where this actually happened? It's usually very few additional permanent jobs and, particularly for public-works stuff, millions or even billions in extra debt to pay off. But don't worry, this next thing we're working on once we get the local council to issue a permit to bulldoze your forest park, that will bring in jobs, we promise.
There's no zfs grenade. It's CDDL, feel free to use it wherever you want. Oracle can't come after you for violating the gpl even if somehow using zfs on linux violates the gpl.
Everything I have read is that the cddl is not compatible with binary deployments of zfs on linux so actually wouldnt that mean yes they could press that if you bundled it with gpl? Actual lawyers have said yes it could which is what I am refering to, however I think the actual answer is that Oracle has created a latch by inaction on this subject for so long now.
CDDL is more permissive than gpl. It's not a violation of cddl to intermingle with code under a different license. GPL is the issue and it's the individual contributors to linux that _could_ sue.
I'm not a lawyer. I don't k is what Oracle's lawyers can and can't do. Even if I'm legally in the right, Oracle's lawyers could break me if they wanted. I can't know if there is a ZFS grenade, and neither can you. But we can choose to not deal with Oracle.
At that point, if they wanted to, they could sue mort96 for saying something bad about Oracle. It's unlikely they'll do that and perhaps a bit less unlikely they'll sue over ZFS.
Most of their legal shenanigans appear to be restricted to companies that already license some software from them.
AWS loop a long while back wanted me to design a playlist system so my dumbass brain snapped to m3u files or w/e people were using back then and designed a system to host/share playlist files. The teenager (ok probably in their 20s) interviewing me seemed more and more confused as we went on but he never tried to redirect me to what he really intended.
What are your discovery mechanisms? I don't know what exists for automatic peer management with wg. If you're doing bgp evpn for vxlan endpoint discovery then I'd think WG over vxlan would be the easier to manage option.
If you actually want to use vxlan ids to isolate l2 domains, like if you want multiple hypervisors separated by public networks to run groups of VMs on distinct l2 domains, then vxlan over WG seems like the way to go.
> This leads to authors having to re-explain their thinking in detail, covering points that they’d omitted for brevity or because they are obvious to those with a good understanding of the problem.
There's nothing wrong with this. Being able to explain your thinking in detail to someone that doesn't necessarily understand the problem is a pretty good exercise to make sure you yourself fully understand the problem _and your thinking._ Of course, this can't turn in to a lecture on basic things people should know or have looked up before commenting.
Sure, now imagine answering 10 different people to all of their questions? It's the largest hindrance I have ever seen but I agree with the above comment that it largely depends on the team.
My take is that an RFC should be very early in the engineering process, like as part of a proof of concept phase, and should not block progress towards completing a design proposal. The design proposal should list any legitimate alternatives to overall or component designs discussed during RFC along with the reasoning for not using them in a "designs not chosen" appendix. This at least gives your engineering leadership an opportunity to evaluate the general design ideas before anyone is prepared to die on the hill of those ideas.
Architecture / Design review happens post proof of concept but still before any significant development work and major action items are blockers to beginning development. Further discussion about designs not chosen can happen here, especially when a flaw is uncovered that would be addressed by one of those not chosen.
I'm seeing many people in the comments with an early 2000's era concept of datacenters. The scale of these new sites is mind boggling. Take your idea of a typical datacenter building. Make it 4x bigger. Then put 4 of them together into a cluster. Then imagine 10 of those clusters at the site.
reply