On Fri, Nov 29, 2013 at 8:24 AM, Roman Bogorodskiy
wrote:
> Hello,
>
> Yes, libvirt's qemu driver works almost fine currently, except the fact that
> it
> needs a 'real' bridge driver, so all the networking configuration like
> filtering rules, NAT, etc
> could be done automatically, like for Linu
On Wed, Nov 27, 2013 at 7:32 PM, Rafał Jaworowski wrote:
> The maintenance aspect and testing coverage are valid points, on the
> other hand future changes would have to go a longer way for us: first
> upstream to libvirt, then downstream to the FreeBSD ports collection
> (+ perhaps some OpenStac
Hello,
Yes, libvirt's qemu driver works almost fine currently, except the fact
that it
needs a 'real' bridge driver, so all the networking configuration like
filtering rules, NAT, etc
could be done automatically, like for Linux now, instead of making user to
perform
all the configuration manually.
On 11/28/2013 05:13 AM, Daniel P. Berrange wrote:
> NB, technically we should have separate CI running for each hypervisor
> that libvirt is able to talk to, so there'd likely want to be dedicated
> CI infrastructure for the libvirt+bhyve combination regardless, perhaps
> it would need less overal
On Wed, Nov 27, 2013 at 05:29:35PM -0500, Sean Dague wrote:
> On 11/27/2013 01:32 PM, Rafał Jaworowski wrote:
> > On Mon, Nov 25, 2013 at 3:50 PM, Daniel P. Berrange
> > wrote:
> >> On Fri, Nov 22, 2013 at 10:46:19AM -0500, Russell Bryant wrote:
> >>> On 11/22/2013 10:43 AM, Rafał Jaworowski wrot
On 28 November 2013 11:29, Sean Dague wrote:
> I think you also need to weigh that against the CI requirements for
> landing a driver in tree for nova, which is probably a dedicated rack of
> hardware running the zuul infrastructure reporting back success / fail
> results on every proposed nova pa
On 11/27/2013 01:32 PM, Rafał Jaworowski wrote:
> On Mon, Nov 25, 2013 at 3:50 PM, Daniel P. Berrange
> wrote:
>> On Fri, Nov 22, 2013 at 10:46:19AM -0500, Russell Bryant wrote:
>>> On 11/22/2013 10:43 AM, Rafał Jaworowski wrote:
Russell,
First, thank you for the whiteboard input regard
On Wed, Nov 27, 2013 at 07:32:13PM +0100, Rafał Jaworowski wrote:
> On Mon, Nov 25, 2013 at 3:50 PM, Daniel P. Berrange
> wrote:
> > I am of course biased, as libvirt project maintainer, but I do agree
> > that supporting bhyve via libvirt would make sense, since it opens up
> > opportunities bey
On Mon, Nov 25, 2013 at 3:50 PM, Daniel P. Berrange wrote:
> On Fri, Nov 22, 2013 at 10:46:19AM -0500, Russell Bryant wrote:
>> On 11/22/2013 10:43 AM, Rafał Jaworowski wrote:
>> > Russell,
>> > First, thank you for the whiteboard input regarding the blueprint for
>> > FreeBSD hypervisor nova driv
On Fri, Nov 22, 2013 at 10:46:19AM -0500, Russell Bryant wrote:
> On 11/22/2013 10:43 AM, Rafał Jaworowski wrote:
> > Russell,
> > First, thank you for the whiteboard input regarding the blueprint for
> > FreeBSD hypervisor nova driver:
> > https://blueprints.launchpad.net/nova/+spec/freebsd-comput
> So just to clarify: the native driver for another hypervisor (bhyve)
> would not be accepted into Nova even if it met testing coverage
> criteria? As I said the libvirt route is an option we consider, but we
> would like to have the possibility of a native FreeBSD api integration
> as well, simil
On Fri, Nov 22, 2013 at 4:46 PM, Russell Bryant wrote:
> On 11/22/2013 10:43 AM, Rafał Jaworowski wrote:
>> Russell,
>> First, thank you for the whiteboard input regarding the blueprint for
>> FreeBSD hypervisor nova driver:
>> https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node
>>
>>
On 11/22/2013 10:43 AM, Rafał Jaworowski wrote:
> Russell,
> First, thank you for the whiteboard input regarding the blueprint for
> FreeBSD hypervisor nova driver:
> https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node
>
> We were considering libvirt support for bhyve hypervisor as we
Russell,
First, thank you for the whiteboard input regarding the blueprint for
FreeBSD hypervisor nova driver:
https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node
We were considering libvirt support for bhyve hypervisor as well, only
wouldn't want to do this as the first approach for
14 matches
Mail list logo
