ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    KVM / Red Hat Virtualization Management

    IT Discussion
    virtualization kvm red hat virtualization virtualization management
    13
    45
    2.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      DustinB3403
      last edited by

      Which XCP-ng has a gluster layer solution of their own now as well. Though I don't know if it's available as an OSS approach.

      1 Reply Last reply Reply Quote 0
      • M
        matteo nunziati @DustinB3403
        last edited by

        @DustinB3403 said in KVM / Red Hat Virtualization Management:

        @matteo-nunziati said in KVM / Red Hat Virtualization Management:

        @DustinB3403 it is like putting XO in a VM inside xcp. The major difference here is the gluster layer.

        Which a lot of people do all of the time. Could you install it as bare metal on a separate host, absolutely. Should you, meh depends on what you need.

        You can do the same with ovirt. The gluster layer is for redundancy. In a First lab you can directly put ovirt into a single Vm into a single node.

        M 1 Reply Last reply Reply Quote 0
        • M
          matteo nunziati @matteo nunziati
          last edited by

          @matteo-nunziati said in KVM / Red Hat Virtualization Management:

          @DustinB3403 said in KVM / Red Hat Virtualization Management:

          @matteo-nunziati said in KVM / Red Hat Virtualization Management:

          @DustinB3403 it is like putting XO in a VM inside xcp. The major difference here is the gluster layer.

          Which a lot of people do all of the time. Could you install it as bare metal on a separate host, absolutely. Should you, meh depends on what you need.

          You can do the same with ovirt. The gluster layer is for redundancy. In a First lab you can directly put ovirt into a single Vm into a single node.

          Just mind you have to put the orchestrator in a special state before node reboot. I didn't figured this out at the time and after the first reboot everything gone nuts.
          I Abandoned the idea in favor of virtmanager + vanilla kvm.

          1 Reply Last reply Reply Quote 0
          • D
            dyasny
            last edited by

            Red Hat has 2 (well, actually 4) products that manage KVM. The main ones are RHV/oVirt and RHOS/RDO (their Openstack distribution).

            Besides these two there is the localhost-oriented libvirt with virt-manager, cockpit and boxes, and kubernetes oriented kubevirt.

            So if you're looking for a vCenter cluster replacement, RHV is what you should be looking at (or if you prefer the less stable opensource version - oVirt). If you want to build something larger, at the scale of AWS, you need Openstack. For local stuff, e.g. virtualbox - virt-manager, boxes, and eventually cockpit will do the job, and if you want to run a VM in a k8s pod - kubevirt is for you.

            1 Reply Last reply Reply Quote 0
            • D
              dyasny @scottalanmiller
              last edited by

              @scottalanmiller RHV now, after a rebrand in 2016-ish

              1 Reply Last reply Reply Quote 0
              • 1
              • 2
              • 3
              • 3 / 3
              • First post
                Last post