Libvirt – The Unsung Hero of Cloud Computing (2013)
1–10 of 113 posts
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#2I really doubt that AWS is using libvirt. They almost certainly have their own abstraction.
But still, I agree that libvirt is great; I wrote about it here: http://catern.com/posts/libvirt.html
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#3While I respect the job that libvirt does (it works — high praise for software), it’s unfortunate that it is also the answer to the question “how can I represent all these virtualized things using XML?”, which was in fashion when libvirt was created.
It’s also a bit misleading to characterize cloud providers as building on libvirt. Libvirt is useful as an mostly hypervisor-agnostic wrapper, which is super useful for enterprise on-prem software, but kinda of the opposite of what big providers need and build for themselves.
I wonder what we will look back on as the XML of today. Everything is schemaless JSON and YAML; surely we’ll look back and wonder WTF everyone was thinking? But alas, it’s probably not a data format at all. Only time will tell.
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#4While I respect the job that libvirt does (it works — high praise for software), it’s unfortunate that it is also the answer to the question “how can I represent all these virtualized things using XML?”, which was in fashion when libvirt was created. It’s also a bit misleading to characterize cloud providers as building on libvirt. Libvirt is useful as an mostly hypervisor-agnostic wrapper, which is super useful for…
Yep, if people think XML has aged poorly, wait until these schema-less formats age...
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#5for the last month (v6.6.0 and v6.7.0) libvirt has been released with a new key 453B65310595562855471199CA68BE8010084C9C (first seen:2020-07-20).
It hasn't been signed or verified by any other source in libvirt / redhat yet.
https://www.redhat.com/archives/libvirt-announce/2020-July/m...
That is preventing downstream distros, like arch, from admitting these new releases into their package repos.
Critical infrastructure, indeed.
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#6While I respect the job that libvirt does (it works — high praise for software), it’s unfortunate that it is also the answer to the question “how can I represent all these virtualized things using XML?”, which was in fashion when libvirt was created. It’s also a bit misleading to characterize cloud providers as building on libvirt. Libvirt is useful as an mostly hypervisor-agnostic wrapper, which is super useful for…
The reason these schemaless and super simple formats are getting popular is because how easy it is to write various things on top of them.
You can essentially use typescript to put a schema on JSON.
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#7for the last month (v6.6.0 and v6.7.0) libvirt has been released with a new key 453B65310595562855471199CA68BE8010084C9C (first seen:2020-07-20). It hasn't been signed or verified by any other source in libvirt / redhat yet. https://www.redhat.com/archives/libvirt-announce/2020-July/m... That is preventing downstream distros, like arch, from admitting these new releases into their package repos. Critical infrastructu…
Key exists on pgp.ocf.berkeley.edu.
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#8While I respect the job that libvirt does (it works — high praise for software), it’s unfortunate that it is also the answer to the question “how can I represent all these virtualized things using XML?”, which was in fashion when libvirt was created. It’s also a bit misleading to characterize cloud providers as building on libvirt. Libvirt is useful as an mostly hypervisor-agnostic wrapper, which is super useful for…
JSON is a bad configuration format simply for the fact that it doesn't support comments. Some parsers do but most don't. XML for all its verbosity and complexity at least has comments where I can quickly try out configuration changes without needing to save the old configuration somewhere else.
Hell, even INI files had support for comments and were just as expressional as JSON. I wonder why we regressed in that regard. Was it just because of the success of JavaScript and readily available JSON parsers? Because I'd argue that an INI parser is just as easy to write.
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#9While I respect the job that libvirt does (it works — high praise for software), it’s unfortunate that it is also the answer to the question “how can I represent all these virtualized things using XML?”, which was in fashion when libvirt was created. It’s also a bit misleading to characterize cloud providers as building on libvirt. Libvirt is useful as an mostly hypervisor-agnostic wrapper, which is super useful for…
Yep, if people think XML has aged poorly, wait until these schema-less formats age...
Ha!
... that’s a laugh of bitter jealousy. I’ve dealt with XML, but I’ve never with XML that came with a schema, or which would have reliably followed one. Not saying schema-less formats are great, but at least I can eyeball them to see what is going on.
Re: Libvirt – The Unsung Hero of Cloud Computing (2013)
#10While I respect the job that libvirt does (it works — high praise for software), it’s unfortunate that it is also the answer to the question “how can I represent all these virtualized things using XML?”, which was in fashion when libvirt was created. It’s also a bit misleading to characterize cloud providers as building on libvirt. Libvirt is useful as an mostly hypervisor-agnostic wrapper, which is super useful for…
What's wrong with XML?