On Mon, 2009-02-02 at 10:59 +0100, Marius Tomaschewski wrote:
For now, I want to stay out of setting up static routes, but I think
that has to come sooner or later.
It is OK to limit routes to the default route for now, but IMO
it is better to use separate xml nodes, e.g.:
static
On Thu, 2009-01-29 at 13:34 -0800, Kaitlin Rupert wrote:
Mark McLoughlin wrote:
I don't think we want to define a bridge here, but more that an
interface is shared - i.e. this is a property of eth2.
Note this line.
The main concern is that this is the way I'd expect NetworkManager
David Lutterkort wrote:
On Thu, 2009-01-29 at 13:34 -0800, Kaitlin Rupert wrote:
Mark McLoughlin wrote:
I don't think we want to define a bridge here, but more that an
interface is shared - i.e. this is a property of eth2.
Note this line.
The main concern is that this is the way I'd expect
Mark McLoughlin wrote:
Hi David,
On Fri, 2009-01-16 at 22:23 +, David Lutterkort wrote:
bridge name=br0 stp=off onboot=yes
member device=eth2/
dhcp peerdns=yes/
/bridge
I don't think we want to define a bridge here, but more that an
interface is shared - i.e. this is a property of
Adding Marius (SuSE sysconfig maintainer) in case I'm misspeaking :-)
David Lutterkort wrote:
On Tue, 2009-01-20 at 11:35 -0700, Jim Fehlig wrote:
David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways;
David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways; currently, we are most
interested in teaching libvirt how to set up ordinary ethernet
interfaces, bridges, bonding and vlan's.
Below is a high-level
On Tue, 2009-01-20 at 11:35 -0700, Jim Fehlig wrote:
David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways; currently, we are most
interested in teaching libvirt how to set up ordinary ethernet
interfaces,
Hi David,
On Fri, 2009-01-16 at 01:13 +, David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways; currently, we are most
interested in teaching libvirt how to set up ordinary ethernet
interfaces, bridges,
On Fri, 2009-01-16 at 03:29 +, John Levon wrote:
On Fri, Jan 16, 2009 at 02:59:17AM +, David Lutterkort wrote:
I am not disagreeing with you, but either way, libvirt needs _some_ way
to control host interfaces.
This is far from obvious to me. Could you explain more?
You're right
On Fri, Jan 16, 2009 at 09:06:05AM +, Mark McLoughlin wrote:
On Fri, 2009-01-16 at 03:29 +, John Levon wrote:
On Fri, Jan 16, 2009 at 02:59:17AM +, David Lutterkort wrote:
I am not disagreeing with you, but either way, libvirt needs _some_ way
to control host interfaces.
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways; currently, we are most
interested in teaching libvirt how to set up ordinary ethernet
interfaces, bridges, bonding
On Fri, Jan 16, 2009 at 12:35:55PM +, Richard W.M. Jones wrote:
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways; currently, we are most
interested in teaching
On Fri, Jan 16, 2009 at 12:41:42PM +, Daniel P. Berrange wrote:
On Fri, Jan 16, 2009 at 12:35:55PM +, Richard W.M. Jones wrote:
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network
On Fri, Jan 16, 2009 at 12:44:21PM +, Richard W.M. Jones wrote:
On Fri, Jan 16, 2009 at 12:41:42PM +, Daniel P. Berrange wrote:
On Fri, Jan 16, 2009 at 12:35:55PM +, Richard W.M. Jones wrote:
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
For certain
On Fri, Jan 16, 2009 at 09:00:16AM +, Mark McLoughlin wrote:
What I don't like about any of these is that I've always imagined we
might add further APIs to libvirt for changing a domain's configuration
without munging XML e.g.
I'm glad to hear this is being considered: you're most
On Fri, Jan 16, 2009 at 01:24:53PM +, John Levon wrote:
On Fri, Jan 16, 2009 at 10:11:02AM +, Daniel P. Berrange wrote:
Integrating with host networking meanwhile is a fundamental requirement
for virtualization for all apps using libvirt, since guests need network
connectivity,
On Fri, Jan 16, 2009 at 09:00:16AM +, Mark McLoughlin wrote:
Hi David,
On Fri, 2009-01-16 at 01:13 +, David Lutterkort wrote:
3. Implementation
=
Configuring network interfaces is highly OS and OS-variant/distro
dependant. There are at least two different
On Fri, Jan 16, 2009 at 01:41:19PM +, Daniel P. Berrange wrote:
I don't think that's much of an argument. Plenty of things can be
considered fundamental. My kernel version certainly is, so why isn't
libvirt letting me upgrade that? What about my firewall? Why isn't
libvirt configuring
Just to be clear - I am very sympathetic to the need for this stuff and
the conclusion that it belongs in libvirt. I just think we need to be
fairly clear on where the line is.
On Fri, 2009-01-16 at 13:41 +, Daniel P. Berrange wrote:
On Fri, Jan 16, 2009 at 01:24:53PM +, John Levon
On Fri, Jan 16, 2009 at 02:20:27PM +, Mark McLoughlin wrote:
Just to be clear - I am very sympathetic to the need for this stuff and
the conclusion that it belongs in libvirt. I just think we need to be
fairly clear on where the line is.
On Fri, 2009-01-16 at 13:41 +, Daniel P.
On Fri, Jan 16, 2009 at 01:24:53PM +, John Levon wrote:
We should be considering why libvirt is /well-placed/ to configure the
host. I think it should be pretty clear that it's actually not: the
problems around distro differences alone is a good indication. The
proposed API is anaemic
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
1. XML Format
=
The first question is how the user would describe the host interfaces they
want. Below are some sketches of what an XML representation of the various
kinds of interfaces would look like. This
On Fri, 2009-01-16 at 03:29 +, John Levon wrote:
On Fri, Jan 16, 2009 at 02:59:17AM +, David Lutterkort wrote:
I am not disagreeing with you, but either way, libvirt needs _some_ way
to control host interfaces.
This is far from obvious to me. Could you explain more?
The
On Fri, 2009-01-16 at 15:06 +, Daniel P. Berrange wrote:
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
From a style point of view I'd prefer these to all have the same
top level XML element name, and use type='phys|bond|vlan|bridge'
attribute for distinction, since
Hi Mark,
On Fri, 2009-01-16 at 09:00 +, Mark McLoughlin wrote:
Hi David,
On Fri, 2009-01-16 at 01:13 +, David Lutterkort wrote:
bond name=bond00 onboot=yes mode=active-backup
slave device=eth0 primary=yes/
slave device=eth1/
/bond
bridge name=br0 stp=off onboot=yes
On Fri, 2009-01-16 at 13:49 +, Daniel P. Berrange wrote:
On Fri, Jan 16, 2009 at 09:00:16AM +, Mark McLoughlin wrote:
The thing is, this has to integrate with existing configuration -
there's no point in futzing about with ip link set eth0 ... if the
user has configured eth0 with
David Lutterkort wrote:
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways; currently, we are most
interested in teaching libvirt how to set up ordinary ethernet
interfaces, bridges, bonding and vlan's.
I agree that carving up
For certain applications, we want libvirt to be able to configure host
network interfaces in a variety of ways; currently, we are most
interested in teaching libvirt how to set up ordinary ethernet
interfaces, bridges, bonding and vlan's.
Below is a high-level proposal of how that could be done.
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
* Should this even be done as part of libvirt ? It seems like a very
generic network config tool, and libvirt merely the conduit to exposing
this through an API, most importantly, a remotable API.
My humble opinion
On Fri, 2009-01-16 at 01:26 +, John Levon wrote:
On Fri, Jan 16, 2009 at 01:13:18AM +, David Lutterkort wrote:
* Should this even be done as part of libvirt ? It seems like a very
generic network config tool, and libvirt merely the conduit to exposing
this through an
On Fri, Jan 16, 2009 at 02:59:17AM +, David Lutterkort wrote:
I am not disagreeing with you, but either way, libvirt needs _some_ way
to control host interfaces.
This is far from obvious to me. Could you explain more?
regards
john
--
Libvir-list mailing list
Libvir-list@redhat.com
] RFC: configuring host interfaces with libvirt
On Fri, Jan 16, 2009 at 02:59:17AM +, David Lutterkort wrote:
I am not disagreeing with you, but either way, libvirt needs _some_ way
to control host interfaces.
This is far from obvious to me. Could you explain more?
regards
john
--
Libvir
32 matches
Mail list logo
