On 09/09/13 14:17, Boris Pavlovic wrote:
> Nikola,
>
> The main problem in this case that we use DB in wrong way.
> If you need in online request to return 100k rows then you are doing
> something wrong IMHO.
Agreed!
> And this fix is better then nothing (and it is the
> best thing that we co
Nikola,
The main problem in this case that we use DB in wrong way.
If you need in online request to return 100k rows then you are doing
something wrong IMHO. And this fix is better then nothing (and it is the
best thing that we could do).
Best regards,
Boris Pavlovic
On Mon, Sep 9, 2013 at 4
On 09/09/13 13:12, Roman Podolyaka wrote:
> Hi,
>
> I'm ok with both accepting this patch and reverting the commit, which
> introduced the regression, but it would be really nice to have these DB
> optimizations in Nova.
>
> As for your concern of accepting such optimizations. I don't think, it's
Robert,
Cool! That would be really nice! nova-bm functional tests are the bare
minimum we need.
Thanks,
Roman
On Mon, Sep 9, 2013 at 2:27 PM, Robert Collins wrote:
> We deseperately want TripleO in the gate and are working towards it.
> However, doing that acceptably fast makes it non-trivial
We deseperately want TripleO in the gate and are working towards it.
However, doing that acceptably fast makes it non-trivial [nested VM's
are kindof slow...]. If there was BYOI in RackSpace and in HP's
non-Beta regions, and custom networking in both clouds, then we could
avoid a layer of nesting a
Hi,
I'm ok with both accepting this patch and reverting the commit, which
introduced the regression, but it would be really nice to have these DB
optimizations in Nova.
As for your concern of accepting such optimizations. I don't think, it's a
problem of such patches themselves, but rather with t
On 09/09/13 11:25, Roman Podolyaka wrote:
> Hi,
>
> There is a patch on review (https://review.openstack.org/#/c/45422/)
> fixing https://bugs.launchpad.net/tripleo/+bug/1221620 which has
> importance 'Critical' in Nova and TripleO (long story short: currently
> Nova Baremetal deployments with mor
Hi,
There is a patch on review (https://review.openstack.org/#/c/45422/) fixing
https://bugs.launchpad.net/tripleo/+bug/1221620 which has importance
'Critical' in Nova and TripleO (long story short: currently Nova Baremetal
deployments with more than one baremetal node won't work).
It would be re
