-project with just adding
--profile to any python client call.
And get such results: http://boris-42.github.io/profiler/
[1] https://github.com/stackforge/osprofiler
Best regards,
Boris Pavlovic
On Fri, Aug 8, 2014 at 8:03 PM, Chris Friesen
wrote:
> Is there a straightforward way to determ
on in these jobs, so we can be first adopters and switch to mongodb.
This will ensure that everything works stable even under load, and i hope
convince people to switch integrate gate to mongo.
Best regards,
Boris Pavlovic
On Sat, Aug 9, 2014 at 3:19 PM, Eoghan Glynn wrote:
>
> Hi Folk
7;t see actually any benefits.
What I heard for now is something like "this decision will make tempest
better"..
But do you care more about Tempest than OpenStack?
Best regards,
Boris Pavlovic
On Tue, Aug 12, 2014 at 12:37 AM, David Kranz wrote:
> On 08/11/2014 04:21 PM, Matthe
t believe or feel, you should just ask users and
community of the project: "what they think?".
In my case I asked Rally community and about 20 different Operators from
various companies and they like and support
this idea. So I would prefer to keep this section in code of Rally and help
with i
processes you are
going to create from scratch similar solution?
I really don't see any reasons why we need to duplicate existing and
working solution and can't just work together on Rally?
Best regards,
Boris Pavlovic
On Fri, Aug 15, 2014 at 1:15 AM, Matthew Treinish
wrote:
> O
+1
On Fri, Aug 15, 2014 at 12:21 PM, Roman Podoliaka
wrote:
> Hi Oslo team,
>
> I propose that we add Mike Bayer (zzzeek) to the oslo.db core reviewers
> team.
>
> Mike is an author of SQLAlchemy, Alembic, Mako Templates and some
> other stuff we use in OpenStack. Mike has been working on OpenS
Hi Lesile,
Woot! Somebody started using OSprofiler!
I create OSprofiler launchpad page: https://bugs.launchpad.net/osprofiler
Feel free to report bug there.
Best regards,
Boris Pavlovic
On Mon, Aug 25, 2014 at 1:54 PM, LeslieWang wrote:
> Dear all,
>
> I found a bug of osprofiler
:
https://github.com/stackforge/rally/tree/master/doc/feature_request
It's very similar to specs, but much simpler for end users, because only
thing that they should fill is description of "what" and "why" is needed in
rally.
Thoughts?
Best regards,
Boris Pavlovic
ies to keep Rally team concentrated on real use cases and move
in right direction
Best regards,
Boris Pavlovic
On Tue, Aug 26, 2014 at 10:05 PM, Joe Gordon wrote:
>
>
>
> On Tue, Aug 26, 2014 at 5:31 AM, Boris Pavlovic wrote:
>
>> Hi stackers,
>>
>>
>>
Joe,
This is a resource problem, the nova team simply does not have enough
> people doing enough reviews to make this possible.
Adding in such case more bureaucracy (specs) is not the best way to resolve
team throughput issues...
my 2cents
Best regards,
Boris Pavlovic
On Fri, Aug 29, 2
all iterations (including exceptions)
Second when most of the steps in the scenario failed like attaching to
> network, ssh and run command why bother reporting the results
Because, bad results are better then nothing...
Best regards,
Boris Pavlovic
On Sat, Aug 30, 2014 at 12:54 AM, Ti
elf, body=None, resp=None):
body = body or {}
self.update(body)
self.resp = resp
In your case you have side effect. Take a look at:
http://stackoverflow.com/questions/1132941/least-astonishment-in-python-the-mutable-default-argument
Best regards,
Boris Pavlovic
On Sat, Aug
volve without straight direction ..
So probably it's time to think how to make Nova simpler? (refactoring and
so on?)
Best regards,
Boris Pavlovic
On Thu, Sep 4, 2014 at 4:16 AM, Joe Gordon wrote:
>
>
>
> On Wed, Sep 3, 2014 at 8:57 AM, Solly Ross wrote:
>
>> > I
Hi Ajay,
Thank you for your work on this. Could you please send on review your code?
Here is the instruction:
https://wiki.openstack.org/wiki/Rally/Develop#How_to_contribute
Thanks
Best regards,
Boris Pavlovic
On Wed, Sep 3, 2014 at 10:47 PM, Ajay Kalambur (akalambu) <
akala...@cisco.
Massoom,
Seems like you are using old rally code.
On Sun, Sep 7, 2014 at 10:33 PM, Ajay Kalambur (akalambu) <
akala...@cisco.com> wrote:
> The following context worked for me.
>
>
> "context": {
> "neutron_network": {
> "network_cidr": "10.%s.0.
Pavlovic
On Sun, Sep 7, 2014 at 10:57 PM, Boris Pavlovic wrote:
> Massoom,
>
> Seems like you are using old rally code.
>
>
> On Sun, Sep 7, 2014 at 10:33 PM, Ajay Kalambur (akalambu) <
> akala...@cisco.com> wrote:
>
>> The following context worked fo
Daisuke,
We have as well changes in our DB models.
So running:
$ rally-manage db recreate
Will be as well required..
Best regards,
Boris Pavlovic
On Mon, Sep 8, 2014 at 3:24 PM, Mikhail Dubov wrote:
> Hi Daisuke,
>
> seems like your issue is connected to the change in the d
> Best regards,
> Daisuke
>
> On 2014/09/08 20:38, Boris Pavlovic wrote:
>
>> Daisuke,
>>
>> We have as well changes in our DB models.
>>
>> So running:
>>
>> $ rally-manage db recreate
>>
>> Will be as well required..
>&g
ition. In other words, monopoly sux in any moment of
time (even after community decided to chose project A and not project B)
Best regards,
Boris Pavlovic
On Wed, Sep 10, 2014 at 4:18 AM, Adam Lawson wrote:
> *"should OpenStack include, in the integrated release,
> a messaging-as-a
,
but there is still a lot of to do.
So you'll be able to use the same tool for gates, local usage and
large-scale tests.
Best regards,
Boris Pavlovic
On Fri, Sep 12, 2014 at 3:17 AM, Kurt Griffiths <
kurt.griffi...@rackspace.com> wrote:
> On 9/11/14, 2:11 PM, "Devananda van de
" and "how" we are
doing.
That will allows us to find simpler solutions for current functionality.
Best regards,
Boris Pavlovic
On Sun, Sep 14, 2014 at 1:07 AM, Michael Still wrote:
> Just an observation from the last week or so...
>
> The biggest problem nova faces at
Ilya,
It sounds good, moreover few other devs asked about similar feature=)
So I am working on proposal how to implement this=)
Best regards,
On Thu, Sep 18, 2014 at 4:35 PM, Ilya Shakhat wrote:
> Ralliers,
>
> I'd like to share with you an idea on how to test dependent resources.
>
> Let's
on (or few
persons) that will track all changes in project and prepare such updates
each week.
Best regards,
Boris Pavlovic
--
Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
uld you explain please?
Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
..
Best regards,
Boris Pavlovic
On Thu, Nov 21, 2013 at 11:09 AM, Clint Byrum wrote:
> Excerpts from Boris Pavlovic's message of 2013-11-19 21:33:08 -0800:
> > Hi stackers,
> >
> >
> > Currently what I see is growing amount of interesting projects, that at
>
) method
4) Move malina scheduler rpc method to scheduler service
5) Remove Malina Scheduler
I don't think that it is step backward as it was mentioned in etherpad..
Best regards,
Boris Pavlovic
On Fri, Nov 22, 2013 at 12:58 AM, Robert Collins
wrote:
> https://etherpad.opens
Robert,
Btw, I would like to be a volunteer too=)
Best regards,
Boris Pavlovic
On Sun, Nov 24, 2013 at 10:43 PM, Robert Collins
wrote:
> On 22 November 2013 23:55, Gary Kotton wrote:
> >
> >
>
> >>> I'm looking for 4-5 folk who have:
> >>>
Mark,
Why we are not able to combine this and Nova meetup in the same place in
the same time?
Best regards,
Boris Pavlovic
On Wed, Nov 20, 2013 at 11:23 PM, Mark Washenberger <
mark.washenber...@markwash.net> wrote:
>
>
>
> On Thu, Nov 14, 2013 at 1:35 PM,
, that could be ported from
zipkin.
So, it will be nice if you will be able to join our efforts. And help with
testing ceilometer & build OpenStack profiling system.
Best regards,
Boris Pavlovic
On Fri, Nov 29, 2013 at 9:05 PM, Sandy Walsh wrote:
>
>
> On 11/29/2013 11:32 AM, Na
After all
integrated projects that use the code are using the library instead of the
incubator, we can delete the module(s) from the incubator.
Sounds good and right.
Best regards,
Boris Pavlovic
On Fri, Nov 29, 2013 at 10:47 PM, Eric Windisch wrote:
> > Based on that, I would like t
Make scheduler as a big lib, then implement RPC methods + bit of
business logic in each project
2) Move all RPC calls from nova,cinder,ironic,... and business logic in 1
scheduler as a service
Best regards,
Boris Pavlovic
On Tue, Dec 3, 2013 at 1:11 PM, Khanh-Toan Tran <
khanh-toan.t...@cloud
thank you for understanding.
Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Russell,
Actually what I said is not only related to Solumn or any other project.
Main "idea" of it was that, well structured etherpads are much better
instrument for such discussions.
Do you disagree with this also?
Best regards,
Boris Pavlovic
On Thu, Dec 5, 2013 at 2:12 A
All,
Thank you guys for your opinion.
As a conclusion of this thread, I think that I shouldn't hesitate to raise
all discussion about Rally in mailing list also.. Right?
Best regards,
Boris Pavlovic
On Thu, Dec 5, 2013 at 2:42 AM, Robert Collins wrote:
> On 5 December 2013 11:3
nd find something more suitable...
I hope that this email will help everybody to be more involved in Rally.
Btw any ideas about how to improve current project organization will be
really super useful. Thanks.
Best regards,
Boris Pavlovic
___
Ope
Hi all,
We made a etherpad about memcached based scheduler:
https://etherpad.openstack.org/p/scheduler-design-proposal
Best regards,
Boris Pavlovic
On Tue, Dec 10, 2013 at 8:16 AM, Dugger, Donald D wrote:
> 1) Scheduler as a Service (review BP
> https://blueprints.launchpad.net/nova
log collector.
And we already made patch for this in Ceilometer:
https://review.openstack.org/#/c/60262/
So it will be nice to get it reviewed/merged.
Thanks.
Best regards,
Boris Pavlovic
On Tue, Dec 10, 2013 at 3:19 PM, Julien Danjou wrote:
> On Tue, Dec 10 2013, Nadya Privalova wr
nd we should mention that declarative_base won't make this work for us
transparent. (Even if we make all in one transactions there will be N
Inserts).
Best regards,
Boris Pavlovic
On Sat, Dec 21, 2013 at 10:57 AM, Jay Pipes wrote:
> On 12/20/2013 04:43 PM, Julien Danjou wrote:
>
&
ure that existing installation pass SLA
4) Ensure that OpenStack VMs have their resources and work as expected
(already started discussion)
Best regards,
Boris Pavlovic
On Sat, Dec 28, 2013 at 11:40 PM, Tim Bell wrote:
>
>
> I think there also needs to be a scalability best pract
team
will get it..
Best regards,
Boris Pavlovic
On Sun, Dec 29, 2013 at 12:08 AM, Tim Bell wrote:
>
>
> Thanks.. can you advise where the accumulated experience from Rally will
> be assembled ?
>
>
>
> Rally gives me the method to test my cloud but we also need to have
, that is actually just Nova copy paste is under
"openstack"?
Best regards,
Boris Pavlovic
On Sun, Jan 5, 2014 at 6:13 PM, Jay Lau wrote:
> Greetings,
>
> Here come a question related to AvailabilityZoneFilter.
>
> A new project Gantt which is a common scheduler f
models, that it is
useless for every other project.
So I don't think that forkit in such state of Nova Scheduler is useful for
any other project.
Best regards,
Boris Pavlovic
On Mon, Jan 6, 2014 at 11:30 PM, Vishvananda Ishaya
wrote:
>
> On Jan 6, 2014, at 11:02 AM, Jay P
That seems pretty ideal to me.
Not sure that nova history is right history for scheduler (Why not Cinder
for example? why exactly Nova?).
Imho Scheduler aaS for all projects and Nova Scheduler
are different things.
Best regards,
Boris Pavlovic
On Mon, Jan 6, 2014 at 11:59 PM, Russell Bryant
implement retry logic in python clients?
Best regards,
Boris Pavlovic
On Wed, Jan 15, 2014 at 10:00 PM, Joe Gordon wrote:
>
>
>
> On Wed, Jan 15, 2014 at 5:28 AM, Frittoli, Andrea (Cloud Services) <
> fritt...@hp.com> wrote:
>
>> Hi all,
>>
>>
>>
Hi,
Nice work Oleg!
Soon we should also have tempest verification of cloud.
So we should add to API it as well.
Something like deployements/{id}/verify?{type}
Best regards,
Boris Pavlovic
On Mon, Jan 20, 2014 at 6:39 PM, Oleg Gelbukh wrote:
> I've finished the v0.1 spec of R
around Web UI)
Best regards,
Boris Pavlovic
On Mon, Jan 20, 2014 at 8:32 PM, LELOUP Julien wrote:
> Hi everyone,
>
>
>
> I’m forwarding my own email previously posted on the QA list.
>
>
>
> I would like to discuss about the cleanup() process used right after a
&
based created schema we should add tests that will check that model &
migrations are synced.
(we are working on this)
Best regards,
Boris Pavlovic
On Fri, Jan 31, 2014 at 7:31 PM, Andrew Lazarev wrote:
> Trevor,
>
> Such check could be useful on alembic side too. Good oppo
Monty,
One of the bugs that can produce random issues=)
https://github.com/openstack/oslo.messaging/blob/master/oslo/messaging/_drivers/impl_rabbit.py#L548
Best regards,
Boris Pavlovic
On Tue, Feb 4, 2014 at 11:05 PM, Andrew Laski wrote:
> On 02/04/14 at 10:39am, Dan Smith wrote:
>
you Alexei for all work that you have
done.
Thoughts?
Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hugh,
welcome to Rally core team!
Best regards,
Boris Pavlovic
On Wed, Feb 5, 2014 at 3:17 PM, Ilya Kharin wrote:
> +1 for Hugh
>
>
> On Wed, Feb 5, 2014 at 2:22 PM, Sergey Skripnick
> wrote:
>
>>
>> +1 for Hugh, but IMO no need to rush with Alexei's
+1 absolutely agree with all words, thank you Sergey for help!
Best regards,
Boris Pavlovic
On Mon, Feb 10, 2014 at 9:48 PM, James E. Blair wrote:
> Hi,
>
> I'm very pleased to propose that we add Sergey Lukjanov to the
> infra-core team.
>
> He is among the top r
oslo-incubator/tree/master/openstack/common/apiclient
Best regards,
Boris Pavlovic
On Wed, Feb 12, 2014 at 12:40 AM, Jesse Noller
wrote:
> As I said last week; we're ready to kickoff and have regular meetings for
> the "unified python SDK" project. The initial meeting i
fig-generator
Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
cong params)
[1] https://wiki.openstack.org/wiki/Rally
[2]
https://review.openstack.org/#/c/57240/27/doc/samples/deployments/multihost.rst
[3] https://github.com/pboris/osprofiler
Best regards,
Boris Pavlovic
On Thu, Feb 13, 2014 at 6:38 PM, David Kranz wrote:
> I was recently bitten b
Hi,
I will be glad to help with this part! It shouldn't be too much work to
handle this.
Who will lead this thing?)
Best regards,
Boris Pavlovic
On Tue, Feb 18, 2014 at 7:51 PM, Matthew Treinish wrote:
> On Tue, Feb 18, 2014 at 09:42:43AM -0500, Sean Dague wrote:
> >
Mike,
What version of tox do you use?
Best regards,
Boris Pavlovic
On Tue, Feb 18, 2014 at 9:46 PM, Mike Spreitzer wrote:
> I am trying to figure out how I should be doing unit testing, and
> documenting it in https://wiki.openstack.org/wiki/Gerrit_Workflow
>
> Oddly, the situat
f they don't pass your gates like here:
https://review.openstack.org/#/c/76718/
So Doug could you please merge our revert to revert:
https://review.openstack.org/#/c/76836/
And we will sync it to nova:
https://review.openstack.org/#/c/76880/
Best regards,
Boris Pavlovic
___
f they don't pass your gates like here:
https://review.openstack.org/#/c/76718/
So Doug could you please merge our revert to revert:
https://review.openstack.org/#/c/76836/
And we will sync it to nova:
https://review.openstack.org/#/c/76880/
Best regards,
Boris Pavlovic
___
Matthew,
LOL ORM on top of another ORM
https://img.neoseeker.com/screenshots/TW92aWVzL0RyYW1h/inception_image33.png
Best regards,
Boris Pavlovic
On Wed, Nov 19, 2014 at 8:46 PM, Matthew Booth wrote:
> We currently have a pattern in Nova where all database code lives in
> d
/nova/boot.json
That boots VMs but doesn't delete them. So they will be deleted only in
generic cleanup context.
Best regards,
Boris Pavlovic
On Thu, Nov 20, 2014 at 4:28 AM, Ajay Kalambur (akalambu) <
akala...@cisco.com> wrote:
> Hi
> In rally I have 2 questions. When you use
here:
https://github.com/stackforge/rally/tree/master/rally/benchmark
So I really don't the case when you need to pass something to periodic
task.. It's not that "task"
Best regards,
Boris Pavlovic
On Fri, Nov 21, 2014 at 3:36 AM, Ajay Kalambur (akalambu) <
akala...@
periodic task would be useful for that. I guess I need to look
> at some other way of performing this
> Ajay
>
>
> From: Boris Pavlovic
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
>
27;ll get ability to compare results of 2 runs (if you need
that)
Best regards,
Boris Pavlovic
On Mon, Nov 24, 2014 at 6:05 PM, Vineet Menon
wrote:
> Hi,
>
> I cannot comment on the best practice.
>
> But I can point to you a few more methods and links.
>
> 1. https://dague.
we can repeat race condition in gates with close to 100% likelihood
in other words we are able to test that fix really fix this issue.
Happy bug fixing!=)
Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Michael,
Rally project (https://github.com/stackforge/rally) needs hands!
We have a billions of interesting, simple and complex tasks.
Please join us at #openstack-rally IRC chat
Thanks!
Best regards,
Boris Pavlovic
On Thu, Dec 18, 2014 at 6:49 PM, Michael wrote:
>
> Hi all,
&g
basically you can use it and extend current benchmark scenarios in
rally/benchmark/scenarios/nova/ or add new one that will attach N networks
to created VM (which is just few lines of code). So task is quite easy
resolvable now.
Best regards,
Boris Pavlovic
On Wed, Nov 26, 2014 at 9:54 PM, Ajay Kalambur
self.admin_clients("neutron") (it's similar to self.clients but with
admin access)
That's how live_migrate benchmark is implemented:
https://github.com/stackforge/rally/blob/master/rally/benchmark/scenarios/nova/servers.py#L253
Does this make sense?
4. Iperf scenario we di
h data
for statistical analyze.
As well use "rps" runner that generates more real life load.
Plus it will be nice to share as well output of "rally task report" command.
By the way what do you think about using Rally scenarios (that you already
wrote) for integration testing
Guys,
I added patch to infra:
https://review.openstack.org/#/c/143879/
That allows to run Rally against Mistral in gates.
Best regards,
Boris Pavlovic
On Mon, Dec 22, 2014 at 4:25 PM, Anastasia Kuznetsova <
akuznets...@mirantis.com> wrote:
> Dmitry,
>
> Now I see that my comm
eate_async()
> .
> vm = create_future.result()
As well this pattern doesn't look great.
I would prefer to see something like:
vm = novaclient.servers.create(, sync=True)
Best regards,
Boris Pavlovic
On Mon, Jan 12, 2015 at 2:30 PM, Konstantin Danilov
wrote:
> Hi
led information about execution of
test. Like for benchmarking it will be quite interesting to collect
durations of every API call.
Best regards,
Boris Pavlovic
On Mon, Jan 12, 2015 at 10:54 PM, Eoghan Glynn wrote:
>
>
> > After some discussion with Sean Dague and a few others it be
s and let them
> start working with it.
+1 more testing better code.
Best regards,
Boris Pavlovic
On Mon, Jan 12, 2015 at 11:20 PM, Sean Dague wrote:
> On 01/12/2015 03:11 PM, Dean Troyer wrote:
> > Thanks for this Chris, I'm hoping to get my fingers dirty with it Real
>
ren't even
on stackforge.
Having few more or less doesn't make any sense...
Best regards,
Boris Pavlovic
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
et
-> run first Rest call
-> run second Rest call
...
-> fixtures.clean
Something like that?
And where are you doing cleanup? (like if you would like to test only
creation of resource?)
Best regards,
Boris Pavlovic
On Tue, Jan 13, 2015 at 12:37 AM, Chris Dent wrote:
>
cient for having quality
> components in OpenStack.
Please be more specific about what tools were tested?
It will be nice to see overview. At least what tool were tested
and why they can't be used for testing-in-tree.
Best regards,
Boris Pavlovic
On Tue, Jan 13, 2015 at 1:37 AM, Anne Gent
friendly.
Best regards,
Boris Pavlovic
On Tue, Jan 13, 2015 at 1:46 PM, Flavio Percoco wrote:
> On 13/01/15 01:14 +0400, Boris Pavlovic wrote:
>
>> Hello TC,
>>
>> I would like to propose to allow adding all python-clients from stackforge
>> (that are regarding global-
on clients from
projects
that are not Core and suggesting another making incompatible with
OpenStack.
Best regards,
Boris Pavlovic
On Tue, Jan 13, 2015 at 6:01 PM, Jeremy Stanley wrote:
> On 2015-01-13 07:46:38 -0500 (-0500), Sean Dague wrote:
> > Why doesn't rally just remove itself
lse. *
It means that:
# this is equal to old Nova.boot_server
NovaServers.boot_server: [{"args": {...} }]
# this is equal to old Nova.boot_and_delete_server
NovaServers.boot_server: [{"args": {..., do_delete: True}]
Thoughts?
case this reduce huge duplication of code with should be nice IMHO.
Best regards,
Boris Pavlovic
On Sun, Jan 18, 2015 at 7:18 PM, Mikhail Dubov wrote:
> Hi Boris,
>
> I understand your concern about keeping the number of different benchmark
> scenarios in Rally not too big so that
.
4) WTF???
Adding extra steps/conditions that are required for using product are
adding exponential complexity to it. So having 5 such steps/conditions will
make product inconsumable.
So the only thing that I would like is to remove one "extra step" by adding
good python clients to g-
Hi Nachi,
Sorry for question, but did you try stackalytics?
E.g. this page http://stackalytics.com/report/contribution/neutron/30
Best regards,
Boris Pavlovic
On Tue, May 20, 2014 at 5:20 AM, Nachi Ueno wrote:
> Hi folks
>
> As per neutron discussion, we agreed there is really
+1 =)
On Thu, May 22, 2014 at 2:03 AM, Clark Boylan wrote:
> On Wed, May 21, 2014 at 2:57 PM, James E. Blair
> wrote:
> > The Infrastructure program has a unique three-tier team structure:
> > contributors (that's all of us!), core members (people with +2 ability
> > on infra projects in Gerrit
will
automatically adjust it before running benchmark.
Thoughts?
Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Joe,
Fully agree. We should just make a blueprint "Get rid of soft deletion". So
we will get much better performance of DB + cleaner code, and avoid such
things like shadow tables and DB purge scripts.
Probably we should some other thread to cover this topic?
Best regards,
Boris Pav
record to this table
2.3-5) similar to 1.1, 1.2, 13
3) We use soft deleted records in API
3.1) Deprecated API call if it is possible
3.2) Make proxy call to ceilometer from API
3.3) On .delete() store info about records in (ceilometer, or somewhere
else)
3.4-6) similar to 1.1, 1.2, 1.3
This is not r
framework
c) replace API stuff using ceilometer (for logs) or this framework (for
restorable stuff)
To put in a nutshell: Restoring Delete resources / Delayed Deletion != Soft
deletion.
Best regards,
Boris Pavlovic
On Thu, Mar 13, 2014 at 9:21 PM, Mike Wilson wrote:
> For some guests we use the
tion of OpenStack Resource in common way
& without these hacks with soft deletion in DB. It is actually very
simple, take a look at this document:
https://docs.google.com/document/d/1WGrIgMtWJqPDyT6PkPeZhNpej2Q9Mwimula8S8lYGV4/edit?usp=sharing
Best regards,
Boris
Joshua,
Fully agree, seems like Mistral duplicates a lot of efforts of TaskFlow.
I just don't see any reason why Mistral is reimplementing TaskFlow and not
just adding new features to...
Best regards,
Boris Pavlovic
On Fri, Mar 14, 2014 at 3:02 AM, Joshua Harlow wrote:
> Separat
A, case B, case C. And these cases couldn't be
implemented in TaskFlow (or Joshua will be totally disagree).
Otherwise seems like Mistral team didn't spend time to investigate already
existing OpenStack solutions..
Best regards,
Boris Pavlovic
On Fri, Mar 14, 2014 at 4:19 AM, Stan Lagu
quot;Soft deletion"
[1] you'll see that restoring "deleted" stuff is popular thing. So the goal
of this proposal is to make standard approach for restoring that won't use
"soft deletion".
[1] http://osdir.com/ml/openstack-dev/2014-03/msg00947.html
Best rega
ms that we are using are bad
2) Architecture solutions that we are using are bad
And start thinking about how to improve them.
[1] https://review.openstack.org/#/c/43151/
[2] http://en.wikipedia.org/wiki/Buran_(spacecraft)
Best regards,
Boris Pavlovic
On Fri, Mar 21, 2014 at 3:04 PM, Sean Da
/30
Thoughts?
Best regards,
Boris Pavlovic
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Kun,
Welcome to Rally core team! =)
Best regards,
Boris Pavlovic
On Mon, Mar 24, 2014 at 2:12 PM, Gareth wrote:
> nice to join you guys ; )
>
>
> On Monday, March 24, 2014, Hugh Saunders wrote:
>
>> +1
>> Kun has been very active on gerrit, and contributed go
+2 =)
On Fri, Mar 28, 2014 at 11:21 PM, Michael Still wrote:
> Hi.
>
> I would like to run for the OpenStack Compute PTL position as well.
>
> I have been an active nova developer since late 2011, and have been a
> core reviewer for quite a while. I am currently serving on the
> Technical Commi
Oleg,
Seems like very interesting topic.
Especially I am interested in how could be this integrated with production
clouds (could it be run on controllers?). What API it present and is there
integration with horizon?
Best regards,
Boris Pavlovic
On Wed, Apr 2, 2014 at 11:20 PM, Oleg Gelbukh
Bruno,
Well done. Finally we have this feature in Rally!
Best regards,
Boris Pavlovic
On Thu, Apr 3, 2014 at 11:37 PM, Bruno Semperlotti <
bruno.semperlo...@gmail.com> wrote:
> Hi Rally users,
>
> I would like to inform you that the feature allowing to update tenant'
Bruno,
Btw great idea add benchmark scenarios for quotas as well!
Best regards,
Boris Pavlovic
On Fri, Apr 4, 2014 at 7:28 PM, Bruno Semperlotti <
bruno.semperlo...@gmail.com> wrote:
> Hi Joshua,
>
> Quotas will not be expanded during the scenario, they will be updated
> *p
Ajay,
I am working that feature. It's almost ready.
I'll let you know when I finish.
Best regards,
Boris Pavlovic
On Thu, Sep 25, 2014 at 5:02 AM, Ajay Kalambur (akalambu) <
akala...@cisco.com> wrote:
> Hi
> Our default mode of execution of rally is allowing Rally to c
/stackforge/rally/tree/master/doc/feature_request
With the list of features that we are working now.
Best regards,
Boris Pavlovic
On Thu, Sep 25, 2014 at 5:30 AM, Ajay Kalambur (akalambu) <
akala...@cisco.com> wrote:
> Hi Boris
> Existing users is one thing but according to Rally page i
+1
On Sat, Sep 27, 2014 at 9:51 AM, Nikhil Manchanda
wrote:
> Big +1 from me.
> Anita has been super helpful, both with reviews and with discussions on
> IRC.
>
>
> On Fri, Sep 26, 2014 at 8:34 AM, James E. Blair
> wrote:
>
>> I'm pleased to nominate Anito Kuno to the project-config core team.
1 - 100 of 345 matches
Mail list logo
