On 21/07/2020 17:17, Maciej Delmanowski wrote:
<cut>
Very nice breakdown of the various virtualization models. The SAN/NAS storage
can definitely be something else like Synology or NetApp devices which you can
connect to your hypervisor infrastructure using NFS, iSCSI or similar
technologies. On the other side, your hypervisors can then be thin blade
servers with only so much storage to start the hypervisor OS - after all
virtual machine storage is hosted elsewhere. There's where the compute/storage
split comes from.
I thought of something more exotic but turns out it's just splitting
responsabilities among machines specialized for a specific task. Correct?
> it’s an auto allocations based on the controllers etc. controlling
> what/where etc. and you typically only have block storage you write to… the
> challenge here: BIG FAT back end network links, as every disk io goes out on
> the network
Using 10 GBit/s or more FibreChannel connections definitely helps. In such
case your hypervisors usually have separate network cards that connect to the
storage network, and a different set of cards that are used for normal VM
traffic. Add to that separate VLANs or even entire software-defined networking
like VXLAN overlays to keep your tenants in their own separate networks and we
can start talking about offering cloud services to third parties... Kind of
like our own AWS/OVH/Hetzner/DigitalOcean cloud. Suddenly your IT department
can become a source of revenue instead of being only a cost center. But that's
a topic for another discussion. :)
very interesting. Definitely a discussion that has to happen because I
see a nice picture when I connect the dots.
<cut>
>>> In the end, I think that DebOps as a solid base to deploy
OpenStack,
>>> OpenNebula or Kubernetes in production environment is a good target to aim
>>> for. Many of the underlying components are shared, which should make things
>>> a bit easier.
> I do not disagree, I would rather advise that this be a tad sideline
> project, instead of a full blown DebOps path, unless there are real needs
> and people having the budgets for those equipment “sponsoring” this part of
> the project ;)
I know that DebOps is used in very diverse environments, from cloud providers
to local installations with their own hardware. I want to use it to manage
on-premises infrastructure of a large university I'm working at, so focus on
on-premises and clustered environments is definitely on point for me.
agreed