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.
    • DustinB3403D
      DustinB3403
      last edited by

      Also just as an aside, the screenshot functionality of Fedora is so damn simple.

      Shift+Alt+PrntScrn and you get the active window, saved to Pictures

      How easy is that! Thank you Linux Devs

      ♥

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

        @EddieJennings said in KVM / Red Hat Virtualization Management:

        @black3dynamite said in KVM / Red Hat Virtualization Management:

        oVirt web management UI looks very similar to what RHEV uses.

        I'm surprised Red Hat doesn't seem to be promoting whatever they use for managing RHEV. I figured they'd try to lure folks away from VMware or Hyper-V with a slick interface 🙂

        Ovirt is the upstream of RHEV.

        DustinB3403D scottalanmillerS 2 Replies Last reply Reply Quote 2
        • DustinB3403D
          DustinB3403 @matteo nunziati
          last edited by

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

          @EddieJennings said in KVM / Red Hat Virtualization Management:

          @black3dynamite said in KVM / Red Hat Virtualization Management:

          oVirt web management UI looks very similar to what RHEV uses.

          I'm surprised Red Hat doesn't seem to be promoting whatever they use for managing RHEV. I figured they'd try to lure folks away from VMware or Hyper-V with a slick interface 🙂

          Ovirt is the upstream of RHEV.

          So you'd install 1-300 oVirt nodes (on your physical and individual servers) and create a gluster pool out of them?

          I actually looked at this a while ago and got frustrated with their documentation because and very specifically it jumps across all of the options to getting ovirt to work.

          FATeknollogeeF matteo nunziatiM 2 Replies Last reply Reply Quote 0
          • FATeknollogeeF
            FATeknollogee @DustinB3403
            last edited by

            @DustinB3403 said in KVM / Red Hat Virtualization Management:

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

            @EddieJennings said in KVM / Red Hat Virtualization Management:

            @black3dynamite said in KVM / Red Hat Virtualization Management:

            oVirt web management UI looks very similar to what RHEV uses.

            I'm surprised Red Hat doesn't seem to be promoting whatever they use for managing RHEV. I figured they'd try to lure folks away from VMware or Hyper-V with a slick interface 🙂

            Ovirt is the upstream of RHEV.

            So you'd install 1-300 oVirt nodes (on your physical and individual servers) and create a gluster pool out of them?

            I actually looked at this a while ago and got frustrated with their documentation because and very specifically it jumps across all of the options to getting ovirt to work.

            Ah no, that's not how oVirt works.

            DustinB3403D 1 Reply Last reply Reply Quote 0
            • FATeknollogeeF
              FATeknollogee @black3dynamite
              last edited by FATeknollogee

              @black3dynamite said in KVM / Red Hat Virtualization Management:

              oVirt web management UI looks very similar to what RHEV uses.

              Guess why...they're pretty much one & the same, kinda like CentOS/RHEL/Fedora.

              1 Reply Last reply Reply Quote 0
              • EddieJenningsE
                EddieJennings @wrx7m
                last edited by

                @wrx7m said in KVM / Red Hat Virtualization Management:

                @EddieJennings said in KVM / Red Hat Virtualization Management:

                @DustinB3403 said in KVM / Red Hat Virtualization Management:

                @EddieJennings said in KVM / Red Hat Virtualization Management:

                This link lists several options, but I'm curious if there's a de facto standard for managing a KVM cluster?

                Looks like the answer is "no" 🙂

                The default answer does exist, Virt-Manager. Cockpit works, but as @travisdh1 mentioned is lacking a few features to make it the solidified "go-to" solution.

                If you need more or want something different then you'd look at alternatives.

                The feature I see missing from Virt-Manage is the click-to-make-this-vm-a-template button and then click-to-deploy-a-vm-from-template button. What I do instead is just make a VM, power it down, and clone it, which, for the most part, seems behave the same.

                So, by your description, you can't make templates of VMs?

                Not that I’ve seen with Virt-Manager GUI. I might can from the command line.

                1 Reply Last reply Reply Quote 0
                • DustinB3403D
                  DustinB3403 @FATeknollogee
                  last edited by

                  @FATeknollogee said in KVM / Red Hat Virtualization Management:

                  @DustinB3403 said in KVM / Red Hat Virtualization Management:

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

                  @EddieJennings said in KVM / Red Hat Virtualization Management:

                  @black3dynamite said in KVM / Red Hat Virtualization Management:

                  oVirt web management UI looks very similar to what RHEV uses.

                  I'm surprised Red Hat doesn't seem to be promoting whatever they use for managing RHEV. I figured they'd try to lure folks away from VMware or Hyper-V with a slick interface 🙂

                  Ovirt is the upstream of RHEV.

                  So you'd install 1-300 oVirt nodes (on your physical and individual servers) and create a gluster pool out of them?

                  I actually looked at this a while ago and got frustrated with their documentation because and very specifically it jumps across all of the options to getting ovirt to work.

                  Ah no, that's not how oVirt works.

                  Can you explain then?

                  Ovirt has their own iso. So presumably you'd install that on your hardware as a node over and over.

                  FATeknollogeeF 1 Reply Last reply Reply Quote 0
                  • FATeknollogeeF
                    FATeknollogee @DustinB3403
                    last edited by

                    @DustinB3403 said in KVM / Red Hat Virtualization Management:

                    @FATeknollogee said in KVM / Red Hat Virtualization Management:

                    @DustinB3403 said in KVM / Red Hat Virtualization Management:

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

                    @EddieJennings said in KVM / Red Hat Virtualization Management:

                    @black3dynamite said in KVM / Red Hat Virtualization Management:

                    oVirt web management UI looks very similar to what RHEV uses.

                    I'm surprised Red Hat doesn't seem to be promoting whatever they use for managing RHEV. I figured they'd try to lure folks away from VMware or Hyper-V with a slick interface 🙂

                    Ovirt is the upstream of RHEV.

                    So you'd install 1-300 oVirt nodes (on your physical and individual servers) and create a gluster pool out of them?

                    I actually looked at this a while ago and got frustrated with their documentation because and very specifically it jumps across all of the options to getting ovirt to work.

                    Ah no, that's not how oVirt works.

                    Can you explain then?

                    Ovirt has their own iso. So presumably you'd install that on your hardware as a node over and over.

                    If you're talking Gluster, that usually refers to a "hyperconverged" install with HE (Hosted Engine).
                    Recommended start point "out of Box" is 3 nodes per cluster using Cockpit UI for the setup.
                    This'll give you some idea: https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-gluster-storage.html

                    scottalanmillerS DustinB3403D 2 Replies Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @DustinB3403
                      last edited by

                      @DustinB3403 said in KVM / Red Hat Virtualization Management:

                      @JaredBusch said in KVM / Red Hat Virtualization Management:

                      @DustinB3403 said in KVM / Red Hat Virtualization Management:

                      RHEL is based on KVM.

                      Umm what? RHEL is not based on KVM. RHEL is the OS.

                      Doh words.

                      I meant RHEL Virtualization is based on KVM

                      That's RHEV, or at least it used to be.

                      D 1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @matteo nunziati
                        last edited by

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

                        @EddieJennings said in KVM / Red Hat Virtualization Management:

                        @black3dynamite said in KVM / Red Hat Virtualization Management:

                        oVirt web management UI looks very similar to what RHEV uses.

                        I'm surprised Red Hat doesn't seem to be promoting whatever they use for managing RHEV. I figured they'd try to lure folks away from VMware or Hyper-V with a slick interface 🙂

                        Ovirt is the upstream of RHEV.

                        Yup, oVirt is what RHEV's interface comes from.

                        1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @FATeknollogee
                          last edited by

                          @FATeknollogee said in KVM / Red Hat Virtualization Management:

                          @DustinB3403 said in KVM / Red Hat Virtualization Management:

                          @FATeknollogee said in KVM / Red Hat Virtualization Management:

                          @DustinB3403 said in KVM / Red Hat Virtualization Management:

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

                          @EddieJennings said in KVM / Red Hat Virtualization Management:

                          @black3dynamite said in KVM / Red Hat Virtualization Management:

                          oVirt web management UI looks very similar to what RHEV uses.

                          I'm surprised Red Hat doesn't seem to be promoting whatever they use for managing RHEV. I figured they'd try to lure folks away from VMware or Hyper-V with a slick interface 🙂

                          Ovirt is the upstream of RHEV.

                          So you'd install 1-300 oVirt nodes (on your physical and individual servers) and create a gluster pool out of them?

                          I actually looked at this a while ago and got frustrated with their documentation because and very specifically it jumps across all of the options to getting ovirt to work.

                          Ah no, that's not how oVirt works.

                          Can you explain then?

                          Ovirt has their own iso. So presumably you'd install that on your hardware as a node over and over.

                          If you're talking Gluster, that usually refers to a "hyperconverged" install with HE (Hosted Engine).

                          These days, yeah. Didn't used to.

                          1 Reply Last reply Reply Quote 0
                          • DustinB3403D
                            DustinB3403 @FATeknollogee
                            last edited by

                            @FATeknollogee said in KVM / Red Hat Virtualization Management:

                            If you're talking Gluster, that usually refers to a "hyperconverged" install with HE (Hosted Engine).

                            Yes that is what I'm specifically talking about.

                            @FATeknollogee said in KVM / Red Hat Virtualization Management:

                            This'll give you some idea: https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-gluster-storage.html

                            In the guide, he specifically installs oVirt Node on his 3 "physical" boxes, as I mentioned above.

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

                              @DustinB3403 ovirt has an orchestrator an a number of virtualization nodes.

                              Orchestrator is like XO, nodes are like xcp. You add the node iso on compute nodes and then you run the orchestrator either as a physical box a vm on a node or a number of nodes.

                              Gluster is used for SDS. You can use it with iscsi target as VSAN but this is an extra feature. It is not required to run ovirt.

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

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

                                @DustinB3403 ovirt has an orchestrator an a number of virtualization nodes.

                                Orchestrator is like XO, nodes are like xcp. You add the node iso on compute nodes and then you run the orchestrator either as a physical box a vm on a node or a number of nodes.

                                Gluster is used for SDS. You can use it with iscsi target as VSAN but this is an extra feature. It is not required to run ovirt.

                                So in all of the documentation on their websites, when they are discussing installing a Node, they mean to create a new hypervisor.

                                And on any one of those hypervisors, setup Orchestrator to manage the whole thing with vSAN (since we're discussing hyperconvergence).

                                matteo nunziatiM 2 Replies Last reply Reply Quote 0
                                • matteo nunziatiM
                                  matteo nunziati @DustinB3403
                                  last edited by

                                  @DustinB3403 yes. Exactly. Installing a node= put the virt engine on the node. Like installing xcp or so.
                                  Hyperconverged means each or some nodes exposes a gluster brick to create shared storage.
                                  Than on that storage (couple of years ago exposed via iscsi, dont know anything about current setup) you create a special VM which is the orchestrator (XO)

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

                                    @matteo-nunziati simple enough.

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

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

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

                                        @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.

                                        matteo nunziatiM 1 Reply Last reply Reply Quote 0
                                        • DustinB3403D
                                          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
                                          • matteo nunziatiM
                                            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.

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