Are there any issues running oVirt at a remote location than the oVirt-node machines?<br><br>I have a site-to-site VPN, ovirt-node machines at one end and an ovirt machine at the other.<br><br>Is there a lot of traffic (bandwidth) use between ovirt and ovirt-node machines? My iSCSI NAS is with my ovirt-node machines.<br>
<br>I have 10mbit down and 1 mbit up at my remote site running the ovirt server... my ovirt-nodes and nas are at a colocation centre.<br><br>Much appreciated!<br><br><br><br><br><div class="gmail_quote">On Sun, Sep 23, 2012 at 9:34 AM, Keith Robertson <span dir="ltr">&lt;<a href="mailto:kroberts@redhat.com" target="_blank">kroberts@redhat.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><div class="im">
    <div>On 09/22/2012 05:35 PM, Nicolas Chenier
      wrote:<br>
    </div>
    <blockquote type="cite"><b>Question 1 - if oVirt goes down... do the
        ovirt-nodes and VMs remain up?</b> Can someone answer this
      please? :-)<br>
    </blockquote></div>
    If the oVirt manager (ie. the web application running inside AS7)
    loses connectivity to the node, the VM&#39;s on that node will keep
    running.  You should know; however, that the general design is for
    the manager to remain in contact with the nodes. <br><div class="im">
    <blockquote type="cite"><br>
      Due to budget and space constraints, I currently have 2 servers
      total.<br>
      <br>
      What if I did the following:<br>
      <br>
      Server 1) Fedora 17 with KVM/Virt-manager... running oVirt as a VM
      (through virt-manager) off the iSCSI NAS.<br>
    </blockquote></div>
    Fine<div class="im"><br>
    <blockquote type="cite"> Server 2) oVirt-node machine - one and only host
      machine for oVirt running on Server 1).<br>
    </blockquote></div>
    Again fine.<div class="im"><br>
    <blockquote type="cite"><br>
      With this setup I can run VMs from iSCSI on oVirt-node Server 2).
      <br>
    </blockquote></div>
    Yes, nearly identical to my setup.<div class="im"><br>
    <blockquote type="cite"><br>
      In the event that oVirt-node Server 2) goes down... is anything
      stopping me from setting up my VMs on Server 1) with the iSCSI
      storage from the NAS and run my VMs without oVirt through
      virt-manager?<br>
    </blockquote></div>
    Yes, I don&#39;t think that will work out of the box.  It could probably
    be done but it would require some manual steps.<div class="im"><br>
    <blockquote type="cite"> <br>
      This would give me some form of redundancy (requiring manual
      intervention) in the event that my ovirt-node went down... is this
      a feasible setup?<br>
    </blockquote></div>
    See previous comment.<div class="im"><br>
    <blockquote type="cite"><br>
      To make it even more redundant, maybe I should do the following
      with Server 2)<br>
      <br>
      Install Fedora 17 with KVM/Virt-Manager, and VDSM... in the event
      that Server 1) fails... I can run my VMs on Server 2) through
      virt-manager?<br>
      <br>
      Should I just drop oVirt for now and run virt-manager on my 2
      hosts, moving VMs manually (as they are running off iSCSI NAS) if
      a host fails? &lt;tear&gt;<br>
    </blockquote></div>
    It depends on what you are trying to do.  oVirt and virt-manager
    solve different problems.  I would say that virt-manager is probably
    OK for a small setup, but I wouldn&#39;t deploy an enterprise solution
    around it.<br>
    <br>
    You have enough gear for a small oVirt setup.  Run with that and add
    more nodes as you can.  My 2c.<div><div class="h5"><br>
    <blockquote type="cite"> <br>
      Thank you,<br>
      <br>
      Nic<br>
      <br>
      <br>
      <br>
      <div class="gmail_quote">On Sat, Sep 22, 2012 at 4:09 PM, Keith
        Robertson <span dir="ltr">&lt;<a href="mailto:kroberts@redhat.com" target="_blank">kroberts@redhat.com</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div bgcolor="#FFFFFF" text="#000000">
            <div>
              <div>On 09/22/2012 02:28 PM, Nicolas Chenier wrote:<br>
              </div>
              <blockquote type="cite">Question - if oVirt goes down...
                do the ovirt-nodes and VMs remain up?<br>
                <br>
                <br>
                Keith, how would you set yourself up with these specs:<br>
                <br>
                2 host servers (quad-core xeons with 32gigs of ram)<br>
              </blockquote>
            </div>
            Are you saying that you only have 2 machines in total, or
            that you have 2 machines that can be dedicated hypervisors
            (ie. ovirt-node) and a third machine that can be a dedicated
            manager?<br>
            <br>
            If the former then one machine must run some version of *nix
            compatible with oVirt Manager and, the other machine in this
            scenario can simply run ovirt-node. <br>
            <br>
            If the latter, then you have 1 box dedicated as a manager
            and 2 boxes as dedicated hypervisors.  This is a fairly
            basic/good setup.  <br>
            <div>
              <blockquote type="cite">1 iSCSI NAS<br>
                <br>
                Starting to think there is no way to achieve HA with
                this setup? </blockquote>
            </div>
            Not with only 2 boxes.  No.
            <div><br>
              <blockquote type="cite">oVirt requires a dedicated
                machine?<br>
              </blockquote>
            </div>
            Generally, speaking.  Yes.<br>
            <br>
            Truly HA setups aren&#39;t cheap and people often have different
            ideas of what constitutes HA.  Offhand I would think that
            you would need...<br>
            <br>
            - 2 boxes for the oVirt manager<br>
            - Clustering software for the manager to facilitate an
            active/passive setup.<br>
            - UPSs (at *least* 2) which can be controlled by clustering
            software.  Why?  Most clustering SW require a fence device. 
            These will be your fence devices.<br>
            - 2 boxes for your hypervisors (ie. ovirt-nodes).  This will
            facilitate fail-over from one node to the other.<br>
            <br>
            HA isn&#39;t cheap and can&#39;t usually be done on 2 boxes, IMO
            unless you&#39;re failing over a single app.
            <div>
              <div><br>
                <br>
                <br>
                <blockquote type="cite"> <br>
                  Thank you!<br>
                  <br>
                  Nic<br>
                  <br>
                  PS. Could oVirt be integrated into ovirt-node on every
                  server?<br>
                  <br>
                  <br>
                  <br>
                  <div class="gmail_quote">On Sat, Sep 22, 2012 at 2:16
                    PM, Keith Robertson <span dir="ltr">&lt;<a href="mailto:kroberts@redhat.com" target="_blank">kroberts@redhat.com</a>&gt;</span>
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      <div bgcolor="#FFFFFF" text="#000000">
                        <div>
                          <div>On 09/22/2012 01:09 PM, Nicolas Chenier
                            wrote:<br>
                          </div>
                          <blockquote type="cite">Hi Alan,<br>
                            <br>
                            I have oVirt running in a VM off my Desktop
                            (Fedora 17 w/ KVM &amp; Virt-Manager) off my
                            iSCSI NAS. <br>
                            <br>
                            I&#39;ve attached Server #1 as my first host
                            (it&#39;s running ovirt-node).<br>
                            <br>
                            In the process of setting up my storage
                            domains. I have a few questions to the
                            experts out there:<br>
                            <br>
                            1) How do I add my CD .ISOs to setup new
                            VMs? Create iSCSI storage domain? But then
                            how do I copy my ISOs to it?<br>
                          </blockquote>
                        </div>
                        Create an ISO storage domain and use the
                        ovirt-iso-uploader to add your ISOs and .vfd
                        files into that domain.
                        <div><br>
                          <blockquote type="cite"><br>
                            2) Can I run my oVirt VM from ovirt-node
                            machine, without running it in oVirt (ie.
                            setup iSCSI in virt-manager (as it is now)
                            and run oVirt from virt-manager... then I
                            can manage my hosts through that ovirt VM?<br>
                          </blockquote>
                        </div>
                        Huh?  You could run the oVirt Manager from a VM
                        managed by virt-manager... yes.  Running the
                        oVirt manager inside a VM on a hypervisor (ie.
                        ovirt-node) controlled by that same manager
                        isn&#39;t supported AFAIK because the mgr. could get
                        fenced.  <br>
                        <br>
                        To summarize, you can pretty much run the oVirt
                        manager on any supported OS as long as that OS
                        instance isn&#39;t running on a hypervisor (ie.
                        ovirt-node) controlled by *that* manager.<br>
                        <br>
                        If you haven&#39;t noticed the vocabulary to
                        describe the various components can get a little
                        confusing. ;)  <br>
                        <br>
                        <br>
                        <blockquote type="cite">
                          <div> <br>
                            Not sure if I&#39;m making myself clear... but
                            I&#39;m making progress. I think as long as you
                            are not managing your oVirt vm through oVirt
                            itself, the solution should work fine! Just
                            trying to see if I can get that done on an
                            ovirt-node machine...<br>
                            <br>
                            Thank you,<br>
                            <br>
                            Nic<br>
                            <br>
                            <br>
                            <div class="gmail_quote">On Fri, Sep 21,
                              2012 at 3:31 PM, Alan Johnson <span dir="ltr">&lt;<a href="mailto:alan@datdec.com" target="_blank">alan@datdec.com</a>&gt;</span>
                              wrote:<br>
                              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                                <div class="gmail_quote">
                                  <div>On Wed, Sep 12, 2012 at 9:22 PM,
                                    Nicolas Chenier <span dir="ltr">&lt;<a href="mailto:dascope@gmail.com" target="_blank">dascope@gmail.com</a>&gt;</span>
                                    wrote:<br>
                                    <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                                      <div>I was under the impression
                                        that my oVirt VM would show up
                                        in oVirt and that I could manage
                                        it through there...</div>
                                      <div> </div>
                                      <div>What you&#39;re saying is that I
                                        should just run it seperatly and
                                        not manage it with itself
                                        (oVirt)? keep it on my shared
                                        storage so that I can run it off
                                        any of the 2 servers? But not
                                        manage it with oVirt (itself). I
                                        think I&#39;m starting to get it
                                        now...</div>
                                      <div> </div>
                                      <div>I really appreciate your
                                        help!</div>
                                      <div> </div>
                                      <div>Nic</div>
                                    </blockquote>
                                    <div><br>
                                    </div>
                                  </div>
                                  <div>Nic, how did you make out with
                                    this?  I&#39;m looking to do the same
                                    thing and am wondering if there is
                                    any risk in running the engine on a
                                    VM managed by the same engine, as
                                    you were suggesting before.  Did you
                                    give this a shot?</div>
                                  <div><br>
                                  </div>
                                  <div>Itamar, why did you steer Nic
                                    away from this?</div>
                                  <font color="#663366"><font face="verdana,sans-serif"><br clear="all">
                                    </font></font>_______________<span><font color="#888888"><br>
                                      Alan Johnson<br>
                                      <a href="mailto:alan@datdec.com" target="_blank">alan@datdec.com</a><br>
                                      <div> </div>
                                    </font></span></div>
                              </blockquote>
                            </div>
                            <br>
                            <br>
                            <fieldset></fieldset>
                            <br>
                          </div>
                          <div>
                            <pre>_______________________________________________
Users mailing list
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
                          </div>
                        </blockquote>
                        <br>
                        <br>
                      </div>
                    </blockquote>
                  </div>
                  <br>
                </blockquote>
                <br>
              </div>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
    <br>
    <br>
  </div></div></div>

</blockquote></div><br>