|
|
| (471 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | [[Category:Virtualization]] <!-- do not copy into FWN issue --> |
| | |
| {{Anchor|Virtualization}} | | {{Anchor|Virtualization}} |
| | |
|
| |
|
| == Virtualization == | | == Virtualization == |
| In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies. | | In this section, we cover discussion of Fedora virtualization technologies on the |
| | | @fedora-virt list. |
| Contributing Writer: [[DaleBewley | Dale Bewley]]
| |
| | |
| === Enterprise Management Tools List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
| |
| | |
| === Fedora Xen List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
| |
| | |
| === Libvirt List ===
| |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
| |
| | |
| ==== Libvirt vs XenAPI ====
| |
| Atif Bajwa asked[1] about the advantages of using libvirt over [http://wiki.xensource.com/xenwiki/XenApi XenAPI] and what platforms libvirt supports. [[AtsushiSakai|Atsushi Sakai]] pointed to a list[2] of which libvirt calls work on which drivers / hypervisors. [[DanielBerrange|Daniel P. Berrange]] replied[3] that libvirt is available for every major Linux distro, and listed several benefits such as:
| |
| | |
| * avoids locking applications to a particular hypervisor
| |
| * provides a guaranteed stable API that can be used both locally and remotely
| |
| * remote security options include SSL + x509 certificates, SSH tunnel, Kerberos GSSAPI single sign on, and username + password
| |
| * works with every version of Xen 3.0.x or later while XenAPI is only usable in Xen 3.1.0 and later
| |
| | |
| [[RichardJones|Richard W.M. Jones]] mentioned[4] that although there are no binaries [[SIGs/MinGW|yet]], libvirt client code can be compiled on windows.
| |
| | |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00002.html
| |
| | |
| [2] http://libvirt.org/hvsupport.html
| |
| | |
| [3] https://www.redhat.com/archives/libvir-list/2008-September/msg00008.html
| |
| | |
| [4] https://www.redhat.com/archives/libvir-list/2008-September/msg00016.html
| |
| | |
| ==== Latest MinGW Patches ====
| |
| [[DanielBerrange|Daniel P. Berrange]] posted[1] patches to allow building on F10 of libvirt-0.dll and virsh.exe which run successfully under Wine, provided only 'test' and 'remote' drivers are turned on.
| |
| | |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00065.html
| |
| | |
| ==== Does Libvirtd Needs to Always be Running ====
| |
| [[YushuYao|Yushu Yao]] asked[1] a basic question which may be helpful to point
| |
| out. Does libvirtd need to always be running? [[RichardJones|Richard W.M. Jones]] answered[2] "yes and no". The local Xen hypervisor can be managed by direct hypervisor calls and/or a connection to xend. Warnings that libvirtd isn't running may be ignored.
| |
| | |
| Libvirtd must be running to support the following, however.
| |
| * remote access
| |
| * non-root access
| |
| * if you use the network or storage features
| |
| * managing QEMU and KVM instances
| |
| | |
| [1] https://www.redhat.com/archives/libvir-list/2008-September/msg00085.html
| |
| | |
| [2] https://www.redhat.com/archives/libvir-list/2008-September/msg00103.html
| |
|
| |
|
| === oVirt Devel List ===
| | Contributing Writer: [[User:Dale | Dale Bewley]] |
| This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
| |
|
| |
|
| ==== Renaming oVirt RPMs ==== | | === Fedora Virtualization List === |
| [[AlanPevec|Alan Pevec]] proposed[1] renaming the oVirt packages which turned into a discussion with [[DanielBerrange|Daniel P. Berrange]] about how to organize the git repos and how to continue support build-all after such a change.
| | This section contains the discussion happening on the |
| | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
|
| [1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00029.html | | ==== Virt Status Report ==== |
| | [[JustinForbes|Justin Forbes]] |
| | posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report. |
| | Justin pointed out F13 bugs<ref>http://fedoraproject.org/wiki/Virtualization_bugs</ref> now include Important and Pony classifications in addition to Blocker and Target. |
|
| |
|
| ==== WUI Management of Underlying Hardware ====
| | <references /> |
| [[ChrisLalancette|Chris Lalancette]] posted[1] a series of patches to allow the Web User Interface to manage the underlying hardware it is running on.
| |
|
| |
|
| [1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00081.html
| | ==== RHEL and Fedora Virtualization Feature Parity ==== |
| | Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4 |
| | compared to Fedora 12. |
|
| |
|
| ==== Network Interface Bonding and Failover ====
| | [[DanielBerrange|Daniel Berrange]] |
| [[DarrylPierce|Darryl L. Pierce]] began[1] a discussion on implementing support for ethernet bonding multiple interfaces for load balancing and failover. Special consideration for different hardware scenarios such as blade servers lead [[KonradRzeszutek|Konrad Rzeszutek]] to ask how these extra parameters would be passed in to the bonding setup. Darryl explained[2] that on boot the node identifies itself to the oVirt server, and downloads a configuration file to be processed by augtool[3]. The managed node then restarts the network service to apply the network configuration that it just retrieved. | | explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref> |
| | "The KVM based virtualization in RHEL-5.4 is not nearly so far behind |
| | Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was |
| | rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is |
| | also pretty close to that using what's best described as a hybrid of |
| | kvm-83 and kvm-84." |
|
| |
|
| | <references /> |
|
| |
|
| [1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00064.html
| |
|
| |
|
| [2] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00075.html
| | ==== ==== |
| | <references /> |
|
| |
|
| [3] http://augeas.net/
| | ==== ==== |
| | <references /> |
libvirt