On Jan 30, 2014, at 6:26 AM, CARVER, PAUL wrote:
> Vishvananda Ishaya wrote:
>
> >In testing I have been unable to saturate a 10g link using a single VM. Even
> >with multiple streams,
> >the best I have been able to do (using virtio and vhost_net is about 7.8g.
>
> Can you share details ab
Vishvananda Ishaya wrote:
>In testing I have been unable to saturate a 10g link using a single VM. Even
>with multiple streams,
>the best I have been able to do (using virtio and vhost_net is about 7.8g.
Can you share details about your hardware and vSwitch config (possibly off list
if that isn
On 25 January 2014 03:33, CARVER, PAUL wrote:
> I agree that I'd like to see a set of use cases for this. This is the second
> time in as many days that I've heard about a desire to have such a thing but
> I still don't think I understand any use cases adequately.
>
>
>
> In the physical world it
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova]Why not allow to create a vm directly with
> two VIF in the same network
>
> I agree its oddly inconsistent (you’ll get used to that over time ;-) - but
> to me it feels mo
nstack-dev] [nova]Why not allow to create a vm directly with
two VIF in the same network
Hi Paul:
I am very glad to do the thing that puts together the practical use cases in
which the same VM would benefit from multiple virtual connections to the same
network, whatever it takes, I think we
nt: Friday, January 24, 2014 09:11
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova]Why not allow to create a vm directly with
two VIF in the same network
I agree its oddly inconsistent (you’ll get used to that over time ;-) - but to
me it feels mor
Lingxian Kong wrote:
>Actually, in the scenario of NFV, all the rules or behaviors of the physical
>world will apply to that in the virtual world, right?
>IMHO, despite of the scenarios, we should at least guarantee the consistency
>of creating vms with nics and attaching nics .
I'll need to t
nstant Message
>
>
>
> *From:* Day, Phil [mailto:philip@hp.com]
> *Sent:* Friday, January 24, 2014 09:11
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [nova]Why not allow to create a vm
> directly with two VIF in t
On Fri, Jan 24, 2014 at 02:11:02PM +, Day, Phil wrote:
> I agree its oddly inconsistent (you'll get used to that over time ;-)
> - but to me it feels more like the validation is missing on the attach
> that that the create should allow two VIFs on the same network. Since
> these are both vir
On 01/24/2014 08:33 AM, CARVER, PAUL wrote:
I agree that I’d like to see a set of use cases for this. This is the
second time in as many days that I’ve heard about a desire to have such
a thing but I still don’t think I understand any use cases adequately.
In the physical world it makes perfect
, 2014 09:11
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova]Why not allow to create a vm directly with
two VIF in the same network
I agree its oddly inconsistent (you'll get used to that over time ;-) - but to
me it feels more like the validatio
rovide any additional
resilience, etc) I'm curious about why you'd want two VIFs in this
configuration ?
From: shihanzhang [mailto:ayshihanzh...@126.com]
Sent: 24 January 2014 03:22
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova]Why not allow to create a vm directly
I am a beginer of nova, there is a problem which has confused me, in the latest
version, it not allowed to create a vm directly with two VIF in the same
network, but allowed to add a VIF that it network is same with a existed
VIF'network, there is the use case that a vm with two VIF in the same
13 matches
Mail list logo
