[openstack-dev] [openstack-operators][Rally][announce] What's new in Rally v0.0.4
Hi everyone, Rally team is happy to announce that we have just cut the new release 0.0.4! *Release stats:* - Commits: *87* - Bug fixes: *21* - New scenarios: *14* - New contexts: *2* - New SLA: *1* - Dev cycle: *30 days* - Release date: *14/May/2015* *New features:* - *Rally now can generate load with users that already exist. *This makes it possible to use Rally for benchmarking OpenStack clouds that are using LDAP, AD or any other read-only keystone backend where it is not possible to create any users dynamically. - *New decorator **@osclients.Clients.register. *This decorator adds new OpenStack clients at runtime. The added client will be available from *osclients.Clients* at the module level and cached. - *Improved installation script.* The installation script for Rally now can be run from an unprivileged user, supports different database types, allows to specify a custom python binary, automatically installs needed software if run as root etc. For more details, take a look at the *Release notes for 0.0.4* https://rally.readthedocs.org/en/latest/release_notes/latest.html. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings
We have decided to stay in *#openstack-meeting* but have our meetings *on Mondays at 1400 UTC*. Hope that this time there will be no conflicts. We will also have the internal release meeting in *#openstack-rally* one hour before that, on Mondays at 1300 UTC. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Thu, May 7, 2015 at 3:15 AM, Tony Breeds t...@bakeyournoodle.com wrote: On Wed, May 06, 2015 at 05:09:07PM +0300, Mikhail Dubov wrote: many thanks for noticing it, I didn't see it for some reason while looking at the iCal file / checking the wiki. No problem. Seeing conflicts is non-trivial. with 90+meetings in 4+ IRC channels. We will use another time then. As I said that time is fine as long as you switch to #openstack-meeting-4 Yours Tony. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings
Tony, many thanks for noticing it, I didn't see it for some reason while looking at the iCal file / checking the wiki. We will use another time then. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Wed, May 6, 2015 at 5:15 AM, Tony Breeds t...@bakeyournoodle.com wrote: On Tue, May 05, 2015 at 06:22:47PM +0300, Mikhail Dubov wrote: Hi Rally team, as mentioned in another message from me in this list, we have decided to use the meeting time on Wednesdays at 14:00 UTC for our *usual weekly meeting in #openstack-meeting*. This meeting time and channel will clash with the docs meeting every second week. Check May 13th (UTC) at: https://www.google.com/calendar/embed?src=bj05mroquq28jhud58esggqmh4%40group.calendar.google.comctz=Iceland/Reykjavik It looks like #openstack-meeting-4 is free at that time. As for the release meeting, we wil hold it just before the main meeting, weekly on Wednesdays at 13:30 UTC in *#openstack-rally*. Do you want this listed as a meeting on https://wiki.openstack.org/wiki/Meetings and in thr iCal above? Tony. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Rally] Improve review process
Hi Roman, a truly great job. Very impressive and useful. Thanks a lot! Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Tue, May 5, 2015 at 3:11 PM, Roman Vasilets rvasil...@mirantis.com wrote: Hi, Rally Team. I have created Rally Gerrit dashboard that organized patches in groups: Critical for next release, Waiting for final approve, Bug fixes, Proposed specs, Important patches, Ready for review, Has -1 but passed tests. Please use link http://goo.gl/iRxA5t for you comfortable. Patch is here https://review.openstack.org/#/c/179610/ It was made by gerrit-dash-creator. First group are the patches that are needed to merge to the nearest release. Content of the next three groups is obvious from the titles. Important patches - its just patches chosen(starred) by Boris Pavlovic or Mikhail Dubov. Ready for review - patches that are waiting for attention. And the last section - its patches with -1 mark but they passed CI. Roman Vasilets, Mirantis Inc. Intern Software Engineer __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings
Hi everyone, this is to inform you that we have registered a second Rally meeting devoted to Rally releases: https://wiki.openstack.org/wiki/Meetings#Rally_meeting This new meeting is going to be held on Wednesdays at 14:00 UTC and will be held for the first time tomorrow. The main Rally meeting time has not changed and is still on Tuesdays at 17:00 UTC. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Mon, Apr 20, 2015 at 12:56 PM, Sergey Skripnick sskripn...@mirantis.com wrote: - We should start making agenda for each meeting and publish it to Rally wiki +1 - We should do 2 meeting per week: We can do both things in one meeting. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally] Weekly meeting
Hi everyone, sorry for the previous disinformative message. We have decided to move our weekly meeting to Wednesdays at 14:00 UTC (IRC, *#openstack-meeting*). As said before, all the relevant information including the meeting agenda can be found on the wiki page https://wiki.openstack.org/wiki/Meetings/Rally. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Tue, May 5, 2015 at 6:10 PM, Mikhail Dubov mdu...@mirantis.com wrote: Hi everyone, let me remind you that today there is the weekly Rally meeting at 17:00 UTC (IRC, *#openstack-meeting*). Starting from today, we will be posting our meeting agenda at the corresponding wiki page https://wiki.openstack.org/wiki/Meetings/Rally. Fell free to comment on the agenda / to propose new topics. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Tue, Apr 28, 2015 at 1:05 PM, Mikhail Dubov mdu...@mirantis.com wrote: Hi everyone, let me remind you that today there is the weekly Rally meeting at 17:00 UTC (IRC, *#openstack-meeting*). Here is the agenda for today: 1. Rally QA week: tasks, assignees, progress 2. Upcoming Rally 0.0.4 release: progress on critical patches 3. Spec on refactoring scenario utils: review and discussion ( https://review.openstack.org/#/c/172831/) 4. Spec on in-tree functional tests: review and discussion ( https://review.openstack.org/#/c/166487/) 5. Free discussion The meeting is going to be chaired by Alexander Maretskiy. Fell free to comment on the agenda / to propose new topics. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally] Weekly meeting
Hi everyone, let me remind you that today there is the weekly Rally meeting at 17:00 UTC (IRC, *#openstack-meeting*). Starting from today, we will be posting our meeting agenda at the corresponding wiki page https://wiki.openstack.org/wiki/Meetings/Rally. Fell free to comment on the agenda / to propose new topics. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Tue, Apr 28, 2015 at 1:05 PM, Mikhail Dubov mdu...@mirantis.com wrote: Hi everyone, let me remind you that today there is the weekly Rally meeting at 17:00 UTC (IRC, *#openstack-meeting*). Here is the agenda for today: 1. Rally QA week: tasks, assignees, progress 2. Upcoming Rally 0.0.4 release: progress on critical patches 3. Spec on refactoring scenario utils: review and discussion ( https://review.openstack.org/#/c/172831/) 4. Spec on in-tree functional tests: review and discussion ( https://review.openstack.org/#/c/166487/) 5. Free discussion The meeting is going to be chaired by Alexander Maretskiy. Fell free to comment on the agenda / to propose new topics. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings
Hi Rally team, as mentioned in another message from me in this list, we have decided to use the meeting time on Wednesdays at 14:00 UTC for our *usual weekly meeting in #openstack-meeting*. As for the release meeting, we wil hold it just before the main meeting, weekly on Wednesdays at 13:30 UTC in *#openstack-rally*. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Tue, May 5, 2015 at 4:13 PM, Mikhail Dubov mdu...@mirantis.com wrote: Hi everyone, this is to inform you that we have registered a second Rally meeting devoted to Rally releases: https://wiki.openstack.org/wiki/Meetings#Rally_meeting This new meeting is going to be held on Wednesdays at 14:00 UTC and will be held for the first time tomorrow. The main Rally meeting time has not changed and is still on Tuesdays at 17:00 UTC. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Mon, Apr 20, 2015 at 12:56 PM, Sergey Skripnick sskripn...@mirantis.com wrote: - We should start making agenda for each meeting and publish it to Rally wiki +1 - We should do 2 meeting per week: We can do both things in one meeting. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [rally] Weekly meeting
Hi everyone, let me remind you that today there is the weekly Rally meeting at 17:00 UTC (IRC, *#openstack-meeting*). Here is the agenda for today: 1. Rally QA week: tasks, assignees, progress 2. Upcoming Rally 0.0.4 release: progress on critical patches 3. Spec on refactoring scenario utils: review and discussion ( https://review.openstack.org/#/c/172831/) 4. Spec on in-tree functional tests: review and discussion ( https://review.openstack.org/#/c/166487/) 5. Free discussion The meeting is going to be chaired by Alexander Maretskiy. Fell free to comment on the agenda / to propose new topics. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings
Hi Boris, thanks for your proposal. As for the agenda, I really think it's important to have it in advance. How are we going to prepare it? Google docs? Who is going to be responsible for that? As for the meeting time, I'm ok with 15:00 UTC, as well as with some earlier time that would satisfy Yair. As for the meeting days, I think that having two meetings on two days in a row (Monday-Tuesday) may be a bit too tough. What if we make one meeting on Tuesday and the other on Thursday? Like the first one near the beginning of the week, and the other towards the end of the week. Best wishes, Mikhail Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Sun, Apr 19, 2015 at 8:28 AM, Yair Fried yfr...@redhat.com wrote: -- *From: *Aleksandr Maretskiy amarets...@mirantis.com *To: *Andrey Kurilin akuri...@mirantis.com *Cc: *Boris Pavlovic bo...@pavlovic.me, OpenStack Development Mailing List openstack-dev@lists.openstack.org, yfr...@redhat.com, yingjun li yingjun...@kylin-cloud.com, Mikhail Dubov msdu...@gmail.com, Oleg Anufriev oanufr...@mirantis.com, Roman Vasilets rvasil...@mirantis.com, Sergey Skripnick sskripn...@mirantis.com *Sent: *Saturday, April 18, 2015 1:00:55 PM *Subject: *Re: [opentack-dev][meetings] Proposing changes in Rally meetings Agreed with everything, but I think it would be a bit better if move one meeting from Monday to another day (Andrey K. is right) On Fri, Apr 17, 2015 at 5:35 PM, Andrey Kurilin akuri...@mirantis.com wrote: - We should start making agenda for each meeting and publish it to Rally wiki +1 +1 * Second is release management meeting, where we are discussing priorities for current next release. So core team will know what to review first. It would be nice to post list of high priority patches to etherpad or google docs after each meeting - Move meetings from #openstack-meeting to #openstack-rally chat. doesn't matter for me:) As long as the records are kept. - We should adjust better time for current Rally team. yeah. Current time is not good:( +1 for 15:00 UTC I'd like even earlier, but if it works for everyone else, I'll make the effort. - Do meetings every Monday and Wednesday Monday?) Monday is very hard day... On Fri, Apr 17, 2015 at 4:26 PM, Boris Pavlovic bo...@pavlovic.me wrote: Rally team, I would like to propose next changes in Rally meetings: - We should start making agenda for each meeting and publish it to Rally wiki - We should do 2 meeting per week: * First is regular meeting (like we have now) where we are discussing everything * Second is release management meeting, where we are discussing priorities for current next release. So core team will know what to review first. Seems like the 2nd meeting is mainly for core, so maybe we can set a better(earlier) time for it among a smaller group? - Move meetings from #openstack-meeting to #openstack-rally chat. - We should adjust better time for current Rally team. Like at the moment it is too late for few of cores in Rally. it's 17:00 UTC and I would like to suggest to make at 15:00 UTC. - Do meetings every Monday and Wednesday Thoughts ? Best regards, Boris Pavlovic -- Best regards, Andrey Kurilin. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Rally] Rally release management changes and future worfklow
Hi all, as some of you probably know, Rally has recently adopted a release-based software development model. The latest release is 0.0.3 (appeared on Apr 14). We have set as our goal to have a new release every 2-3 weeks. Since this is quite ambitious and not so easy to achieve, we are also going to set up a certain release management process: - We are going to have a special IRC meeting at *#openstack-rally* for release discussions. At this weekly meeting, we will discuss the goals for the next release, as well as the progress on them. - The features that are to be implemented in the next release will be posted in a special Google doc https://docs.google.com/document/d/1TX5zpYcTX8AXm-K_h1lzUNVCMvbRgsjUKU-dEYNWLY8/edit?usp=sharing. This doc is open for anyone to view comment. For code reviewers, this document should serve as a link to the patches with the highest priority. - Bugs on Launchpad https://bugs.launchpad.net/rally will be used as well to indicate issues that are to be fixed in the next release. - The release process will be managed by Mikhail Dubov, a Rally core reviewer from Mirantis. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings
Sorry, I have incorrectly read the proposed meeting days. Meetings of Monday and Wednesday are okay, but I agree with Roman that Monday/Thursday would be a bit better. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Mon, Apr 20, 2015 at 12:39 PM, Roman Vasilets rvasil...@mirantis.com wrote: Hi, Agree with all proposes. But maybe it's make sense to do a bigger interval between mitings to make as much as possible work for the next meting. For example Monday/Thursday. Its not principal for me. -Thanks, Roman Vasilets. On Fri, Apr 17, 2015 at 4:26 PM, Boris Pavlovic bo...@pavlovic.me wrote: Rally team, I would like to propose next changes in Rally meetings: - We should start making agenda for each meeting and publish it to Rally wiki - We should do 2 meeting per week: * First is regular meeting (like we have now) where we are discussing everything * Second is release management meeting, where we are discussing priorities for current next release. So core team will know what to review first. - Move meetings from #openstack-meeting to #openstack-rally chat. - We should adjust better time for current Rally team. Like at the moment it is too late for few of cores in Rally. it's 17:00 UTC and I would like to suggest to make at 15:00 UTC. - Do meetings every Monday and Wednesday Thoughts ? Best regards, Boris Pavlovic __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [docs][rally] Rally template tasks in a nutshell
Hi stackers, as you might remember, we have recently added a nice feature to Rally which is the support of *task templates*. Rally uses the template syntax based on *Jinja2*, and thus makes it simple to parameterize your benchmark task files. Our step-by-step tutorial has just been updated with a new lesson devoted to task templates in Rally: http://rally.readthedocs.org/en/latest/tutorial/step_8_task_templates.html You are welcome to read it through (it is fairly short) and ask any questions. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack-operators][Rally][HA-testing][multi-scenarios-load-gen] Proposal to change Rally input task format
Hi Boris, nice job! I like how this new task format looks like. I have commented your patch with a couple of suggestions to make it even easier to understand. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Thu, Feb 26, 2015 at 12:24 AM, Boris Pavlovic bo...@pavlovic.me wrote: Hi stackers, When we started Rally we have a just small idea to make some tool that generates load and measures performance. During almost 2 years a lot of changed in Rally, so now it's quite common testing framework that allows to cover various topics like: stress, load, volume, performance, negative, functional testing. Since the begging we have idea of scenario centric approach, where scenario method that is called multiple times simultaneously to generate load and duration of it is collected. This is huge limitation that doesn't allow us to easily generate real life load. (e.g. loading simultaneously few components) or HA testing (where we need during the load generation to disable/kill process, reboot or power off physical nodes). To make this possible we should just run multiple scenarios in parallel, but this change will require change in input task format. I made proposal of new Rally task input format in this patch: https://review.openstack.org/#/c/159065/3/specs/new_rally_input_task_format.yaml Please review it. Let's try to resolve all UX issues before starting working on it. P.S. I hope this will be the last big change in Rally input task format.. Best regards, Boris Pavlovic __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Rally] New awesome Rally Docs available on ReadTheDocs now!
Hi stackers, on behalf of the Rally team, I am happy to announce that we have completely redesigned our Rally documentation in ReadTheDocs http://rally.readthedocs.org/en/latest/. The docs have now received a simpler structure and have become much easier to get through! One of the nicest new things is the Rally step-by-step tutorial http://rally.readthedocs.org/en/latest/tutorial.html that explains, in a series of lessons, how to explore the power of Rally in benchmarking your OpenStack clouds. You are also welcome to take a look at the updated tutorial on how to set up a Rally gate job http://rally.readthedocs.org/en/latest/gates.html in your project. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack-operators][qa][Rally] Thoughts on removing half of Rally benchmark scenarios
Hi Boris,
I understand your concern about keeping the number of different benchmark
scenarios in Rally not too big so that users don't get confused. But what I
really like now about benchmark scenario names in Rally is that they are
highly declarative, i.e. you read them and you have a clear idea of what's
going on inside those scenarios. You see boot_and_delete_server = you
know that Rally will boot and then delete a server, boot_server = only
boot a server.
That's very convenient e.g. when you navigate through Rally report pages:
you see the scenario names in the left panel and you know what to expect
from their results. It seems to me that, if we merge scenarios like
boot_server
and boot_and_delete_server together, we will lose a bit in clarity.
Besides, as you pointed out, Nova.boot_server and
Nova.boot_and_delete_server
are used for two different purposes - seems to be indeed a strong reason
for keeping them separated.
Best regards,
Mikhail Dubov
Engineering OPS
Mirantis, Inc.
E-Mail: mdu...@mirantis.com
Skype: msdubov
On Sat, Jan 17, 2015 at 8:47 PM, Boris Pavlovic bo...@pavlovic.me wrote:
Hi stackers,
I have an idea about removing almost half of rally scenarios and keep all
functionality.
Currently you can see a lot of similar benchmarks like:
NovaServers.boot_server # boot server with passed
arguments
NovaServers.boot_and_delete_server # boot server with passed arguments
and delete
The reason of having this 2 benchmarks are various purpose of them:
1) Nova.boot_server is used for *volume/scale testing*.
Where we would like to see how N active VM works and affects OpenStack API
and booting next VMs.
2) Nova.boot_and_delete_server is used for *performance/load* testing.
We are interested how booting and deleting VM perform in case on various
load (what is different in duration of booting 1 VM when we have 1, 2, M
simultaneously VM boot actions)
*The idea is to keep only 1 boot_server and add arguments do_delete with
by default False. *
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?
Best regards,
Boris Pavlovic
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally] KeyError: 'admin'
Hi Daisuke,
seems like your issue is connected to the change in the deployment
configuration file format for existing clouds we've merged
https://review.openstack.org/#/c/116766/ recently.
Please see the updated Wiki How to page
https://wiki.openstack.org/wiki/Rally/HowTo#Step_1._Deployment_initialization_.28use_existing_cloud.29
that
describes the new format. In your case, you can just update the deployment
configuration file and run again *rally deployment create*. Everything
should work then.
Best regards,
Mikhail Dubov
Mirantis, Inc.
E-Mail: mdu...@mirantis.com
Skype: msdubov
On Mon, Sep 8, 2014 at 3:16 PM, Daisuke Morita morita.dais...@lab.ntt.co.jp
wrote:
Hi, rally developers!
Now, I am trying to use Rally to devstack cluster on AWS VM
(all-in-one). I'm following a blog post
https://www.mirantis.com/blog/rally-openstack-tempest-testing-made-simpler/
. I successfully installed Devstack, Rally and Tempest. Now, I just ran
Tempest by 'rally verify start' command, but the command failed with the
following stacktrace.
2014-09-08 10:57:57.803 17176 CRITICAL rally [-] KeyError: 'admin'
2014-09-08 10:57:57.803 17176 TRACE rally Traceback (most recent call
last):
2014-09-08 10:57:57.803 17176 TRACE rally File /usr/local/bin/rally,
line 10, in module
2014-09-08 10:57:57.803 17176 TRACE rally sys.exit(main())
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/main.py, line 40, in
main
2014-09-08 10:57:57.803 17176 TRACE rally return
cliutils.run(sys.argv, categories)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/cliutils.py, line
184, in run
2014-09-08 10:57:57.803 17176 TRACE rally ret = fn(*fn_args,
**fn_kwargs)
2014-09-08 10:57:57.803 17176 TRACE rally File string, line 2, in
start
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/envutils.py, line 64,
in default_from_global
2014-09-08 10:57:57.803 17176 TRACE rally return f(*args, **kwargs)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/commands/verify.py,
line 59, in start
2014-09-08 10:57:57.803 17176 TRACE rally api.verify(deploy_id,
set_name, regex)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/orchestrator/api.py, line
153, in verify
2014-09-08 10:57:57.803 17176 TRACE rally
verifier.verify(set_name=set_name, regex=regex)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/tempest/tempest.py,
line 247, in verify
2014-09-08 10:57:57.803 17176 TRACE rally
self._prepare_and_run(set_name, regex)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/utils.py, line 165, in
wrapper
2014-09-08 10:57:57.803 17176 TRACE rally result = f(self, *args,
**kwargs)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/tempest/tempest.py,
line 146, in _prepare_and_run
2014-09-08 10:57:57.803 17176 TRACE rally self.generate_config_file()
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/tempest/tempest.py,
line 89, in generate_config_file
2014-09-08 10:57:57.803 17176 TRACE rally
config.TempestConf(self.deploy_id).generate(self.config_file)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/tempest/config.py,
line 242, in generate
2014-09-08 10:57:57.803 17176 TRACE rally func()
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/tempest/config.py,
line 115, in _set_boto
2014-09-08 10:57:57.803 17176 TRACE rally
self.conf.set(section_name, 'ec2_url', self._get_url('ec2'))
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/tempest/config.py,
line 105, in _get_url
2014-09-08 10:57:57.803 17176 TRACE rally return
service['admin']['publicURL']
2014-09-08 10:57:57.803 17176 TRACE rally KeyError: 'admin'
2014-09-08 10:57:57.803 17176 TRACE rally
I tried to dig into the root cause of above error, but I did not have
any idea where to look into. The most doubtful may be automatically
generated configuration file, but I did not find anything odd.
If possible, could you give me some hints on what to do?
Sorry for bothering you. Thanks in advance.
Best Regards,
Daisuke
--
Daisuke Morita morita.dais...@lab.ntt.co.jp
NTT Software Innovation Center, NTT Corporation
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally] KeyError: 'admin'
Hi Daisuke,
have you executed as well
* $ rally-manage db recreate*
as Boris pointed out in the previous letter?
Best regards,
Mikhail Dubov
Community
Mirantis, Inc.
E-Mail: mdu...@mirantis.com
Skype: msdubov
On Mon, Sep 8, 2014 at 3:46 PM, Daisuke Morita morita.dais...@lab.ntt.co.jp
wrote:
Hi Mikhail,
Thanks for your quick reply. I have already added cloud by using json
format. Just to be safe, I retried to create deployment by following How
to, but the same error is shown now.
My existing.json is as follows. Is there anything wrong?
{
type: ExistingCloud,
auth_url: http://127.0.0.1:5000/v2.0/;,
admin: {
username: admin,
password: pass,
tenant_name: admin
}
}
Best regards,
Daisuke
On 2014/09/08 20:24, Mikhail Dubov wrote:
Hi Daisuke,
seems like your issue is connected to the change in the deployment
configuration file format for existing clouds we've merged
https://review.openstack.org/#/c/116766/ recently.
Please see the updated Wiki How to page
https://wiki.openstack.org/wiki/Rally/HowTo#Step_1._
Deployment_initialization_.28use_existing_cloud.29 that
describes the new format. In your case, you can just update the
deployment configuration file and run again /rally deployment create/.
Everything should work then.
Best regards,
Mikhail Dubov
Mirantis, Inc.
E-Mail: mdu...@mirantis.com mailto:mdu...@mirantis.com
Skype: msdubov
On Mon, Sep 8, 2014 at 3:16 PM, Daisuke Morita
morita.dais...@lab.ntt.co.jp mailto:morita.dais...@lab.ntt.co.jp
wrote:
Hi, rally developers!
Now, I am trying to use Rally to devstack cluster on AWS VM
(all-in-one). I'm following a blog post
https://www.mirantis.com/blog/rally-openstack-tempest-
testing-made-simpler/
. I successfully installed Devstack, Rally and Tempest. Now, I just
ran
Tempest by 'rally verify start' command, but the command failed with
the
following stacktrace.
2014-09-08 10:57:57.803 17176 CRITICAL rally [-] KeyError: 'admin'
2014-09-08 10:57:57.803 17176 TRACE rally Traceback (most recent
call last):
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/bin/rally,
line 10, in module
2014-09-08 10:57:57.803 17176 TRACE rally sys.exit(main())
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/main.py, line 40,
in main
2014-09-08 10:57:57.803 17176 TRACE rally return
cliutils.run(sys.argv, categories)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/cliutils.py, line
184, in run
2014-09-08 10:57:57.803 17176 TRACE rally ret = fn(*fn_args,
**fn_kwargs)
2014-09-08 10:57:57.803 17176 TRACE rally File string, line 2,
in
start
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/envutils.py, line
64,
in default_from_global
2014-09-08 10:57:57.803 17176 TRACE rally return f(*args,
**kwargs)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/cmd/
commands/verify.py,
line 59, in start
2014-09-08 10:57:57.803 17176 TRACE rally api.verify(deploy_id,
set_name, regex)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/orchestrator/api.py,
line
153, in verify
2014-09-08 10:57:57.803 17176 TRACE rally
verifier.verify(set_name=set_name, regex=regex)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/
tempest/tempest.py,
line 247, in verify
2014-09-08 10:57:57.803 17176 TRACE rally
self._prepare_and_run(set_name, regex)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/utils.py, line 165, in
wrapper
2014-09-08 10:57:57.803 17176 TRACE rally result = f(self, *args,
**kwargs)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/
tempest/tempest.py,
line 146, in _prepare_and_run
2014-09-08 10:57:57.803 17176 TRACE rally
self.generate_config_file()
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/
tempest/tempest.py,
line 89, in generate_config_file
2014-09-08 10:57:57.803 17176 TRACE rally
config.TempestConf(self.deploy_id).generate(self.config_file)
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally/verification/verifiers/
tempest/config.py,
line 242, in generate
2014-09-08 10:57:57.803 17176 TRACE rally func()
2014-09-08 10:57:57.803 17176 TRACE rally File
/usr/local/lib/python2.7/dist-packages/rally
Re: [openstack-dev] [rally] Parallel scenarios
Ajay, to be more precise, we also already had a feature request https://github.com/stackforge/rally/blob/master/doc/feature_request/multi_scenarios_load_gen.rst for implementing load generation from multiple scenarios, which seems to be exactly what you proposed. So we are working on this. Best regards, Mikhail Dubov Community Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Sat, Sep 6, 2014 at 2:35 AM, Mikhail Dubov mdu...@mirantis.com wrote: Hi Ajay, Rally as of now does not support launching different scenarios in parallel; implementing this functionality is, however, one of the major points in our roadmap (see this blueprint https://blueprints.launchpad.net/rally/+spec/benchmark-runners-at-large-scale), since being able to produce e.g. parallel load from different servers is really important for benchmarking at scale. Best regards, Mikhail Dubov Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Fri, Sep 5, 2014 at 10:09 PM, Ajay Kalambur (akalambu) akala...@cisco.com wrote: Hi In Rally is there a way to run parallel scenarios? I know the scenario can support concurrency but I am talking about running multiple such scenarios themselves in parallel Ajay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally] Parallel scenarios
Hi Ajay, Rally as of now does not support launching different scenarios in parallel; implementing this functionality is, however, one of the major points in our roadmap (see this blueprint https://blueprints.launchpad.net/rally/+spec/benchmark-runners-at-large-scale), since being able to produce e.g. parallel load from different servers is really important for benchmarking at scale. Best regards, Mikhail Dubov Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Fri, Sep 5, 2014 at 10:09 PM, Ajay Kalambur (akalambu) akala...@cisco.com wrote: Hi In Rally is there a way to run parallel scenarios? I know the scenario can support concurrency but I am talking about running multiple such scenarios themselves in parallel Ajay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [rally] Weekly Rally meeting
Hi all, we would like to inform you that there will be a weekly Rally team meeting today at 17:00 UTC. The meeting will be held in the *#openstack-meeting*channel. We also encourage you to check out our weekly update post: https://wiki.openstack.org/wiki/Rally/Updates. Best regards, Mikhail Dubov Community Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
