Le 22/04/2016 16:14, Matt Riedemann a écrit :
On 4/22/2016 2:48 AM, Sylvain Bauza wrote:
Le 22/04/2016 02:49, Jay Pipes a écrit :
On 04/20/2016 06:40 PM, Matt Riedemann wrote:
Note that I think the only time Nova gets details about ports in
the API
during a server create request is when
On 4/22/2016 2:48 AM, Sylvain Bauza wrote:
Le 22/04/2016 02:49, Jay Pipes a écrit :
On 04/20/2016 06:40 PM, Matt Riedemann wrote:
Note that I think the only time Nova gets details about ports in the API
during a server create request is when doing the network request
validation, and that's
Le 22/04/2016 02:49, Jay Pipes a écrit :
On 04/20/2016 06:40 PM, Matt Riedemann wrote:
Note that I think the only time Nova gets details about ports in the API
during a server create request is when doing the network request
validation, and that's only if there is a fixed IP address or
On 04/20/2016 06:40 PM, Matt Riedemann wrote:
Note that I think the only time Nova gets details about ports in the API
during a server create request is when doing the network request
validation, and that's only if there is a fixed IP address or specific
port(s) in the request, otherwise Nova
On 4/20/2016 8:25 AM, Miguel Angel Ajo Pelayo wrote:
Inline update.
On Mon, Apr 11, 2016 at 4:22 PM, Miguel Angel Ajo Pelayo
wrote:
On Mon, Apr 11, 2016 at 1:46 PM, Jay Pipes wrote:
On 04/08/2016 09:17 AM, Miguel Angel Ajo Pelayo wrote:
[...]
Yes,
On Wed, Apr 20, 2016 at 4:25 PM, Miguel Angel Ajo Pelayo <
majop...@redhat.com> wrote:
> Inline update.
>
> On Mon, Apr 11, 2016 at 4:22 PM, Miguel Angel Ajo Pelayo
> wrote:
> > On Mon, Apr 11, 2016 at 1:46 PM, Jay Pipes wrote:
> >> On 04/08/2016 09:17
Inline update.
On Mon, Apr 11, 2016 at 4:22 PM, Miguel Angel Ajo Pelayo
wrote:
> On Mon, Apr 11, 2016 at 1:46 PM, Jay Pipes wrote:
>> On 04/08/2016 09:17 AM, Miguel Angel Ajo Pelayo wrote:
[...]
>> Yes, Nova's conductor gathers information about the
On Mon, Apr 11, 2016 at 1:46 PM, Jay Pipes wrote:
> Hi Miguel Angel, comments/answers inline :)
>
> On 04/08/2016 09:17 AM, Miguel Angel Ajo Pelayo wrote:
>>
>> Hi!,
>>
>> In the context of [1] (generic resource pools / scheduling in nova)
>> and [2] (minimum bandwidth
Hi Miguel Angel, comments/answers inline :)
On 04/08/2016 09:17 AM, Miguel Angel Ajo Pelayo wrote:
Hi!,
In the context of [1] (generic resource pools / scheduling in nova)
and [2] (minimum bandwidth guarantees -egress- in neutron), I had a talk
a few weeks ago with Jay Pipes,
The idea
openstack-dev@lists.openstack.org>
> *Subject:* [openstack-dev] [neutron] [nova] scheduling bandwidth
> resources / NIC_BW_KB resource class
>
>
>
>
>
> Hi!,
>
>
>
>In the context of [1] (generic resource pools / scheduling in nova) and
> [2] (minimu
From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com]
Sent: Friday, April 08, 2016 4:17 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [neutron] [nova] scheduling bandwidth resources /
NIC_BW_KB re
Hi!,
In the context of [1] (generic resource pools / scheduling in nova) and
[2] (minimum bandwidth guarantees -egress- in neutron), I had a talk a few
weeks ago with Jay Pipes,
The idea was leveraging the generic resource pools and scheduling
mechanisms defined in [1] to find the right
12 matches
Mail list logo