Been happily and very successfully using the official binpkgs, it works really well, sometimes there's a slight delay for the binary versions of the source packages to appear in the repositories, but that's about it. I guess it's kind of running Arch, but with portage <3! And the occasional compilation because your use flags didn't really match the binaries
this is correct, there's even a precompiled kernel (dist-kernel), it works great! and when packages doesn't match your system settings, portage will pull the source and compile them. it's great!
I think some older instance types are still on xen, later types run kvm (code named nitro.. perhaps?). I can’t remember the exact type but last year we ran into some weird issues related to some kernel regression that only affected some instances in our fleet, turns out they where all the same type and apparently ran on xen according to aws support
If you’re using AWS there’s ImageBuilder, it’s by no means a drop-in replacement for packer and a closer look hints at just being ansible behind the scenes. You could probably achieve the same results with pure ansible and some cloud provider modules if needed. Ansible was bought by Redhat though, so still IBM, the licence is unchanged though
Leons daughter Vera talked a bit about her father, his relationship to Kubrick, art and family in “Sommar i P1”, a Swedish national radio show where people in “public interest” talk about whatever for an hour or so. It’s pretty interesting and provide some insights, but unfortunately it’s only in Swedish
I really hope the crazy prize increase of vmware products will end the use of esxi and the rest of the vsphere suite, it is one of the worst applications and apis i have ever had the displeasure of working with!
VMware has a track record of pretty great reliability across a vast array of hardware. Yes, the APIs suck, but they're a case study on tech debt: vSphere is basically the Windows equivalent of datacenter APIs. They chose the best technology at the time (2009, which meant SOAP, Powershell, XML, etc) and had too much inertia to rework it.
Not to mention how flakey it is at scale. There is always some vmware guy who replies to me saying how good it is, but if you have thousands of VMs it is a random crapshoot. Something you just don't see with say AWS and Azure at similar scale. It reaks of old age and hack on hack over many years, and that is saying something when compared to AWS.
The VMWare APIs are indeed pretty bad, even the ones on their modern products for some reason (i.e. NSX etc.) where they did adopt more modern methods but still managed to pull a Microsoft with 'one API for you, a different API for us'.
Being pretty bad doesn't mean they don't work of course, but when the best a product has to offer is clickops, they have missed the boat about 15 years ago.
I really hope that the price increase creates a business opportunity for new technology. This space has been plagued by subpar "free" alternatives (Openstack, Kubernetes) for a decade.
I can't concur. VMware was the leader in virtualization technology for a long time, and honestly nothing is quite as simple to start with as ESXi if you've never used a type 1 hypervisor before. I'm not so familiar with the APIs, so perhaps you're correct in that sense.
> nothing is quite as simple to start with as ESXi if you've never used a type 1 hypervisor before
Not sure about where ESXi is at lately on that level, but latest proxmox is really, really simple to start with if you've never used an hypervisor. You boot on the usb drive, press yes a few times, open the ip:port they give you and then you can click "create vm", next next next here is the iso to boot from and that's it.
Any tech user who has some vague knowledge about virtual machine or even run virtualbox on his computer could do it, and the more advanced fonctions (from proper backups and snapshot to multi node replication and load balancing) are absurdly simple to figure out in the UI.
I can't talk about the performance or quality of one against the other, but in pure difficulty to approach proxmox is doing very very good.
It’s not in a different league. I’ve used both in production. As others have said vSphere breaks down with thousands of VM’s, and worse the vSwitch implementation is buggy and unreliable as soon as you add more than a couple to a cluster.
> the vSwitch implementation is buggy and unreliable as soon as you add more than a couple to a cluster.
Next time try dSwitch (distributed switch) instead of vSwitch. It's designed for cluster use and much more powerful (and easier to manage across hosts). Manually managing vSwitches across a cluster sounds like torture.
i would disagree with you there, especially because there is very little on the sdn front which matches NSX-T in terms of SDN capabilities, this is something in which vmware has been ahead, the only other people with the same capabilities seem to be hyperscalers.
I think it comes pretty close - close enough for probably most but the very largest of users, who, I think, should probably have tried to become hyperscalers themselves, instead of betting the farm and all the land around it on VMware (by Broadcom).
NSX-T and what hyperscalers do is essentially orchestration of things that already exist anyway. The load balancing in NSX is mostly just some openresty and Lua which as been around for quite a while. Classic Q-in-Q and bridging also does practically all of the classic L2 & L3 networking that tends to be touted as 'new', while you could even do that fully orchestrated when Puppet was the hot new thing back in the day.
Some things (that were created before NSX) may have come from internet exchanges and hyperscalers, like openflow, P4, and FRR, but were really not missing parts that were required to do software defined networking. If anything, the only thing you really needed for SDN was Linux, and the only real distinction between SDN and non-SDN was hardwired ASICs in the network fabric (well, not hard-hardwired, but with limited programmability or 'secret' APIs).
Second this, it’s simple, made with bash, git and gpg. Been using it for years myself, I’ve also used it as a shared password store at different workplaces with ease.
Running dos, win9x and others was quite a lot of fixing stuff as well. Getting your hardware to work with games and is took some patience and a lot of trial and error “back in the days”.
Anyone who's used Windows recently can say it happens a _lot_ less now. And also, I see not a "Blue" screen of death, but other screens of death on my work macbook all the time (all official 2019 MBP, no customizations). :| .. It just suddenly restarts and then opens up a 'white window of death' to make me report the kernel problems to Apple. I have saved a few screenshots as well.
It’s been quite a while since I played around with encoders, video streams etc. It seems the old doom9 forums (http://forum.doom9.net) are still somewhat active, even if the site tagline mentions dvd, the video encoding/decoding concepts probably haven’t changed much and the forums seem to cover later technologies than mpeg2. Protocols and methods for transferring the product is most likely out of scope for d9.
