On Fri, Jul 12, 2013 at 1:57 AM, Robert Collins
wrote:
> On 11 July 2013 02:39, Russell Bryant wrote:
>
> >> We'll probably need something like this for Ironic with persistent
> >> volumes on machines - yes its a rare case, but when it matters, it
> >> matters a great deal.
> >
> > I believe you,
On 11 July 2013 02:39, Russell Bryant wrote:
>> We'll probably need something like this for Ironic with persistent
>> volumes on machines - yes its a rare case, but when it matters, it
>> matters a great deal.
>
> I believe you, but I guess I'd like to better understand how this works
> to make s
On Thu, Jul 11, 2013 at 9:12 AM, Álvaro López García
wrote:
> On Wed 10 Jul 2013 (13:10), Joe Gordon wrote:
>> On Mon, Jul 8, 2013 at 8:53 AM, Ilya Kharin wrote:
>>
>> > Hi all.
>> >
>> > In my opinion it is about things that can live in one form or another,
>> > because
>> > in some cases there
On Wed 10 Jul 2013 (13:10), Joe Gordon wrote:
> On Mon, Jul 8, 2013 at 8:53 AM, Ilya Kharin wrote:
>
> > Hi all.
> >
> > In my opinion it is about things that can live in one form or another,
> > because
> > in some cases there is a need to place an instance in the same place where
> > its
> > bl
On 07/10/2013 08:34 AM, Robert Collins wrote:
> On 4 July 2013 03:54, Russell Bryant wrote:
>
>> Thanks for starting this thread.
>>
>> I was pushing for the weight function. It seems much more appropriate
>> for a cloud environment than the filter. It's an optimization that is
>> always a good
On 4 July 2013 03:54, Russell Bryant wrote:
> Thanks for starting this thread.
>
> I was pushing for the weight function. It seems much more appropriate
> for a cloud environment than the filter. It's an optimization that is
> always a good idea, so the weight function that works automatically
On Mon, Jul 8, 2013 at 8:53 AM, Ilya Kharin wrote:
> Hi all.
>
> In my opinion it is about things that can live in one form or another,
> because
> in some cases there is a need to place an instance in the same place where
> its
> block device is located or will be attached. Both solutions that l
Hi all.
In my opinion it is about things that can live in one form or another, because
in some cases there is a need to place an instance in the same place where its
block device is located or will be attached. Both solutions that let you do it,
I mean filter and weigher, have a right to life. A l
On Wed 03 Jul 2013 (18:24), Alexey Ovchinnikov wrote:
> Hi everyone,
Hi Alexey.
> for some time I have been working on an implementation of a filter that
> would allow to force instances to hosts which contain specific volumes.
> A blueprint can be found here:
> https://blueprints.launchpad.net/n
Hi all,
Russell, I agree with all of your remarks, and especially with the
fact that placement details "have to be avoided" to be exposed to
users.
However I see a possible use case for the filter. For instance, if we
consider the BP "Support for multiple active scheduler drivers" (
https://bluep
On 07/03/2013 10:24 AM, Alexey Ovchinnikov wrote:
> Hi everyone,
>
> for some time I have been working on an implementation of a filter that
> would allow to force instances to hosts which contain specific volumes.
> A blueprint can be found here:
> https://blueprints.launchpad.net/nova/+spec/volu
Hi everyone,
for some time I have been working on an implementation of a filter that
would allow to force instances to hosts which contain specific volumes.
A blueprint can be found here:
https://blueprints.launchpad.net/nova/+spec/volume-affinity-filter
and an implementation here:
https://review.
12 matches
Mail list logo