[et-mgmt-tools] Features request

[bodhi zazen]

Thank you all for listening to my request.

I think there are 3 "basic" types of virtualization users, each with
slightly different needs.

1. Testing development. VM used as a sand box.

2. Testing an iso, taking rawhide for a spin.

3. Running servers in an isolated VM for any variety of reasons.

In the first two NAT is sufficient.

With the last, however, NAT is not the easiest of options.

In terms of networking, there are 3 types.

1. (most common) virtual machines have assess to external network.

2. (not unusaual) Host only. The virtual machines can talk with host only.

3. Isolated virtual network. The VM talk to each other and to host.
Some maytake to external networks and some
may not .

These are broad categories I know, my point is IMO it would be nice if one
could have such options in virt-manager. If you want a more detailed user
case I for these options I can provide one =)

How about running a DMZ on virtual machines, with a proxy server to public
net and isolated web / mysql servers, in the DMZ, isolated from both LAN and
public access, but accessible by host and public proxy server.

FYI wireless cards can be bridged with parprouted . I am not an expert on
this mind you. Virtualbox is able to bridge wireless cards and (I do not use
VBox) I believe they use parprouted.

At any rate here is an example :

http://www.linux-kvm.org/page/Simple_shell_script_to_manage_your_virtual_machine_with_bridged_networking

sorry for the long url , lol

Scroll down to the "kvm-manager.sh for wireless interface " section.

I would also like to say I am not implying you should "break" or change the
way virt-manager works or the xml file structure.

I would hope one could add in some "advanced" features of KVM as suggested
by "Emre Erenoglu" <erenoglu at gmail.com> .

One such feature would be snapshot ;)

Again thank you.

----- Original Message -----
From: "Cole Robinson" <crobinso at redhat.com>
To: "Fedora/Linux Management Tools" <et-mgmt-tools at redhat.com>
Sent: Wednesday, June 17, 2009 6:28:43 AM GMT -07:00 US/Canada Mountain
Subject: Re: [et-mgmt-tools] Features request

On 06/17/2009 02:28 AM, Michal Novotny wrote:
> Well, in my opinion you have to consider that virt-manager supports both
> KVM and Xen so you can't simply give KVM only stuff there. It's like the
> ac97 card request - Xen doesn't support this card so virt-manager
> doesn't have a choice to select it at all.

This isn't very clear. Because xen doesn't support ac97 (and neither does
old
QEMU), we can't _unconditionally_ add an ac97 card. That doesn't mean we
can't
support it, such as giving the user an option to install ac97 via the Add
Hardware wizard if they are using qemu or kvm.

Just because virt-manager supports N platforms doesn't mean we can't support
features that only work on M < N platforms, we just need to expose them in a
hypervisor independent way (but libvirt largely sets the stage for this).

Thanks,
Cole

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools at redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/et-mgmt-tools/attachments/20090617/c70e82e7/attachment.htm>