ately but we use to have several reports with just a bunch of traces, or
> just a link..
+1
How about like this?[1]
Description of problem:
How reproducible:
Steps to Reproduce:
Actual results:
Expected results:
Additional info:
[1] https://bugzilla.redha
reviewers can find "interesting" patches easily if the
dashboard shows the tags.
This is not so strong opinion because some scenario tests may have
several services tags.
--
Masayuki Igawa
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
On Tue, Dec 24, 2013 at 6:20 PM, Yair Fried wrote:
>
>
> - Original Message -
>> From: "Masayuki Igawa"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Sent: Tuesday, December 24, 2013 10:42:39 AM
; might also be having a transportation day, Sean has steered away from
> this date as an option.
>
> Thanks,
> Anita.
>> ___
>> 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
--
Masayuki Igawa
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
takes on this list, feel free to correct/update it
please.
Best Regards,
-- Masayuki Igawa
smime.p7s
Description: S/MIME cryptographic signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/ma
xt.gz manually because of some reasons.)
This information would be useful for creating Tempest tests.
Any comments/questions/suggestions are welcome.
And if you notice any mistakes on this list, feel free to correct/update it
please.
Best Regards,
-- Masayuki
Hi Oscar,
I'm sorry for my delayed reply.
I think this is a development topic. I added openstack-dev ML to CC this
time.
Actually, I'm not familiar with Swift unit tests. So I just CCed and I'm
expecting answers from Swift people.
-- Masayuki Igawa
Thank you Masayuki for eve
mpler even in the devstack environment.
>>
>> -Sean
>>
> http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-disk.img
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cg
+1!
On 2014年11月22日(土) 3:29 Matthew Treinish wrote:
>
> Hi Everyone,
>
> I'd like to propose we add Ghanshyam Mann (gmann) to the tempest core
> team. Over
> the past couple of cycles Ghanshyam has been actively engaged in the
> Tempest
> community. Ghanshyam has had one of the highest review cou
; ___
>> 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
>
--
Masayuki Igawa
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I'm interested in this. I can join except 13-21 UTC.
Thanks,
-- Masayuki IGAWA
2014/03/07 9:53 "Christopher Yeoh" :
>
> Hi,
>
> I'd like to start a weekly IRC meeting for those interested in
> discussing Nova API issues. I think it would be a useful forum for
[2] https://wiki.openstack.org/wiki/GerritWorkflow
Best Regards,
-- Masayuki Igawa
>
>
> Oscar CorreiaCTwww.lettersvitae.comSkype: oscar.correiaFacebook: Letters
> VitaeE-Mail: oscar_correiaj@hotmail.comoscarmo...@lettersvitae.com
&g
tions/suggestions are welcome.
And if you find any mistakes on this list, feel free to correct/update it
please.
Best Regards,
-- Masayuki Igawa
smime.p7s
Description: S/MIME cryptographic signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstac
one or more OpenStack's processes.
Currently, Tempest can't stop the OpenStack processes. Because Tempest
can operate OpenStack components through OpenStack APIs only for now.
Thanks,
-- Masayuki Igawa
> 3) Running this test, and checking that each resource doesn't stop.
> 4) Upda
overview.html#design-principles
Thanks,
-- Masayuki Igawa
>
> - Tomoya Goto
>
>
> >You are correct. The testing we do for this is in Grenade, which we run
> >in the gate. Grenade tests an upgrade from last stable release to
> >current master. It creates a few res
t into the
> # other sections.
>
> -- template end -
+1!
I think many of bug descriptions don't have enough information for
debugging now. So we should have enough information like this as
possible.
However, one thing I'm concerned about this template is a little heavy
process for submitting an easy bug. We might have some templates for
depending on the situation.
Thanks,
--
Masayuki Igawa
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Kilo development cycle for filling the gap. And that will
be an input to make blurprints.
[1]
http://kilodesignsummit.sched.org/event/6d91b3205804c930c2a067b23e7aab76#.VErHcH96c-U
[2]
https://etherpad.openstack.org/p/kilo-summit-gap-analysis-tempest-in-production
Thanks,
--
Masayuki
pdate
> and merge it soon.
>
> By the way, could you please add the link to etherpad [2] to the event
> description [1], it will help to
> find the correct link from mobile devices.
>
> Thank you!
>
>
> On Fri, Oct 31, 2014 at 4:23 AM, Masayuki Igawa
> wrote:
>>
+1 !
On Jul 22, 2014 7:36 AM, "Matthew Treinish" wrote:
>
>
> Hi Everyone,
>
> I would like to propose 2 changes to the Tempest core team:
>
> First, I'd like to nominate Andrea Fritolli to the Tempest core team.
Over the
> past cycle Andrea has been steadily become more actively engaged in the
T
avorites,
and implement tempest tests.
Any comments are welcome.
Additional information:
I made this API list with modification of nova's code that based on
https://review.openstack.org/#/c/25882/ (Abandoned).
Best Regards,
-- Masayuki Igawa
smime.p7s
Description: S/MIME crypt
% 0
(*1) Because they are deprecated APIs such as nova-network and volume.
(*2) not included v3 APIs
I hope this information would be helpful for creating Tempest tests.
Any comments and questions are welcome.
Best Regards,
-- Masayuki Igawa
> Hi, Tempest developers
>
> I
lcome.
Best Regards,
-- Masayuki Igawa
> Hi, Tempest developers
>
> I have made:
> Nova API List for Missing Tempest Tests.
>
> https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWc
>
> This list shows what we should test. That i
analysis tooling: http://summit.openstack.org/cfp/details/171
This information would be useful for creating Tempest tests.
Any comments/questions/suggestions are welcome.
Best Regards,
-- Masayuki Igawa
> Hi,
>
> # I'm sorry for this resending because my last mail has unnecessa
nder.. and so on now. But I think this flow is one of the missing
Tempest test reasons.
I think we can increase the test coverage of Tempest if we write a Tempest code
first.
Best Regards,
-- Masayuki Igawa
On 2013/10/15 23:24:56 +0900, Matthew Treinish wrote:
> On Tue, Oct 15, 2013 at 06:
ion
> one by one, list the status file by file.
I have a question. Is there any way to list the nova v3 apis?
If so, I think the checking process of the test implementation can be
automatically.
Best Regards,
-- Masayuki Igawa
>
> Due to these patch https://review.openstack.org/#/c
pest tests.
Any comments/questions/suggestions are welcome.
And if you notice any mistakes on this list, feel free to correct/update it
please.
Best Regards,
-- Masayuki Igawa
> Hi,
>
> First, thank you to an anonymous for updating this list!
> -> GET /{project_id}/servers/:ser
Hi, Christopher
2013/10/23 12:40:38 Christopher Yeoh wrote:
> On Tue, Oct 22, 2013 at 9:22 PM, Masayuki Igawa
> wrote:
>
>
> Hi, Ivan
>
> Thank you for your information. And I'm sorry for delay reply.
>
>
> > Hi,
>
ve anything else setup at the moment, so as a
> temporary measure I've created an etherpad here:
>
> https://etherpad.openstack.org/p/TempestTestDevelopment
Thank you for creating this page!
I think this is really good for avoiding the conflict.
Best Regards,
-- Masayuki Igawa
>
t was worth a try.
I think etherpads is useful for the first step.
Of course, more systematic/automatic approach as David said is better. I have
no idea for now, though..
Best Regards,
-- Masayuki Igawa
smime.p7s
Description: S/MIME cryptographic signature
013-11-14-17.02.log.html
[2]
https://blueprints.launchpad.net/tempest/+spec/add-scenario-tests-in-icehouse
Any comments and suggestions are welcome.
Best Regards,
-- Masayuki Igawa
On Mon, Nov 18, 2013 at 10:07 PM, Salvatore Orlando wrote:
>
> I've pushed https://review.openstack.org/#
Hi, David
Thanks for your reply.
On Tue, Nov 19, 2013 at 12:37 AM, David Kranz wrote:
> On 11/18/2013 09:34 AM, Masayuki Igawa wrote:
>>
>> Hi,
>> I read the qa-meeting log[1]. And I registered a blueprint[2] for
>> tracking and avoiding duplication.
>>
e question and/or opinion, please let me know.
[1] https://etherpad.openstack.org/p/tempest-cli-improvements
[2] https://review.openstack.org/#/c/240399/
Best Regards,
-- Masayuki Igawa
__
OpenStack Development Mailing List
2015年11月18日(水) 5:37 Matthew Treinish :
> On Tue, Nov 17, 2015 at 01:39:34AM +0000, Masayuki Igawa wrote:
> > Hi tempest CLI users and developers,
> >
> > Now, we are improving Tempest CLI as we discussed at the summit[1] and
> > migrating legacy commands to temp
api-ref-identity-v3-ext.html#identity_v3_OS-INHERIT-ext
I've found a client for OS-TRUST extension api
in tempest/services/identity/v3/json/identity_client.py but not about
OS-INHERIT.
So I think you can add OS-INHERIT api client and test then post it :)
Best regards,
-- Masayuki Igawa
wizard" for
tempest configuration?
This is a just idea, though..
Anyway, if you have the motivation to introduce tempest-config, how about
writing a spec for the feature for a concrete discussion?
(I think we should have agreements about the target issues, users,
solutions, etc.)
Best Rega
On Wed, Jun 1, 2016 at 3:05 AM, Andrea Frittoli
wrote:
> On Mon, 30 May 2016, 6:25 p.m. Ken'ichi Ohmichi,
> wrote:
>>
>> Hi,
>>
>> There are many patches which are not updated in Tempest review queue
>> even if having gotten negative feedback from reviewers or jenkins.
>> Nova team is abandoning
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Best Regards,
-- Masayuki Igawa
Congrats! I'm looking forward to seeing an integration/collaboration
with openstack-heath :)
On Tue, Jun 7, 2016 at 8:32 AM, Buckley, Tim Jason
wrote:
> Hello all,
>
> I'd like to announce that StackViz will now be running at the end all
> tempest-dsvm jobs and saving visualization output to the
Hi Jianghua and QA team,
Thank you for bringing this up.
IMO, it's good to make it voting in openstack/tempest. Because it's
already a voting job in Nova and seems having enough stability.
And we should keep test stability for projects.
My concern is that the resource of "Citrix XenServer CI". D
2016-04-11 9:46 GMT+09:00 Matt Riedemann :
>
>
> On 4/10/2016 6:37 PM, Clint Byrum wrote:
>>
>> Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700:
>>>
>>> There is also disincentive in +1ing a change that you don't understand
>>> and is wrong and then a core comes along and -1s it
int. Yeah, I suppose that not everyone read all docs. But some
reviewers can
know our custom/culture through the docs. And we can indicate the
pointer if reviewers
don't know it.
Best Regards,
-- Masayuki Igawa
>
> But atleast we should document it somewhere.
>
> Regards,
> Sheel
https://bugs.launchpad.net/openstack-health
[3] http://git.openstack.org/cgit/openstack/openstack-health
Best Regards,
-- Masayuki Igawa
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
Hi QA guys,
We have very few topic this week to discuss. So I think we should skip
this week meeting.
Any thoughts?
Best Regards,
-- Masayuki Igawa
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
.youtube.com/watch?v=D9vwge557hY
I think this is a casual version and Japanese people are familiar with this.
Thanks,
-- Masayuki Igawa
> -amrith
>
> P.S. the yahoo answer suggests that you pronounce it as "Meh - gee" with
> the emphasis on the "meh" ;)
>
> ---
2015年7月7日(火) 21:14 Matthias Runge :
> On 07/07/15 13:55, Masayuki Igawa wrote:
>
> >
> > https://www.youtube.com/watch?v=D9vwge557hY
> > I think this is a casual version and Japanese people are familiar with
> this.
> Thank you! I have an idea now.
>
>
me to add an item to the agenda.
To help people figure out what time 22:00 UTC is in other timezones
tomorrow's
meeting will be at:
18:00 EDT
07:00 JST
07:30 ACST
00:00 CEST
17:00 CDT
15:00 PDT
-- Masayuki Igawa
__
+1 :)
On 2015年6月23日(火) at 5:30 Matthew Treinish wrote:
>
>
> Hi Everyone,
>
> I'd like to propose we add Jordan Pittier (jordanP) to the tempest core
> team.
> Jordan has been a steady contributor and reviewer on tempest over the past
> few
> cycles and he's been actively engaged in the Tempest c
reat work! And I hope you still
continue to deeply involved with the QA program for the better OpenStack
quality,
too :)
Best Regards,
-- Masayuki Igawa(IRC: masayukig)
__
OpenStack Development Mailing List (not for usage que
y to implement all then it will be huge tests number.
> I think its project which should be verifying those.
>
> In Summary -
>
> 1. If we choose to have only valid negative tests (other than surface
> level negative testing) which can verify stability/integration of API
> and
_
> 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
>
--
Masayuki Igawa
_
+1!
--
Masayuki Igawa
masay...@igawa.me
On Tue, May 16, 2017, at 05:22 PM, Andrea Frittoli wrote:
> Hello team,
>
> I'm very pleased to propose Fanglei Zhu (zhufl) for Tempest core.
>
> Over the past two cycle Fanglei has been steadily contributing to
> Tempest an
+1!
--
Masayuki Igawa
masay...@igawa.me
On Tue, May 16, 2017, at 05:22 PM, Andrea Frittoli wrote:
> Hello team,
>
> I'm very pleased to propose Fanglei Zhu (zhufl) for Tempest core.
>
> Over the past two cycle Fanglei has been steadily contributing to
> Tempest an
Thanks Andrea,
+1
But my only one concern is this change is not good for you, right? Of
course, you don't need to attend both meetings, though :)
--
Masayuki Igawa
On Fri, May 26, 2017, at 10:41 AM, zhu.fang...@zte.com.cn wrote:
>
> +1, thanks!
>
> zhufl
>
&
n them doesn't change the scaling problem. It just shifts
> that from the tempest repo to another repo. (or multiples)
Yeah, we should define and clear the problems before discussing the
solution. I
think Thierry already mentioned about that like below.
---
> &
On 11/28, Ghanshyam Mann wrote:
> Mon-Tue/Wed-Fri works as most suitable format. There are always
> conflict for many of us but that can be adjusted by working with team
> planning.
>
> Another thing can help is to give flexibility to team to have team
> topic even on Mon-Tue, which mean team need
Hi Emilien,
I'd love to take this role!
I have some tempest experience but not QA work which you mentioned
(devstack, grenade, zuul layout) that much. However, I think it will
be a very good opportunity to step-up.
So, for me, the next step might be to know grenade / upgrade jobs /
plugin mechani
ple with https://review.openstack.org/#/c/532361/ (from Sean).
>
> Thanks,
>
> On Thu, Jan 11, 2018 at 9:29 PM, Emilien Macchi wrote:
> > On Thu, Jan 11, 2018 at 7:13 PM, Masayuki Igawa
> > wrote:
> >> Hi Emilien,
> >>
> >> I'd love to take
;t know of anyone working on that, but I suspect it could be done
> using the pygments library.
Oh, it's an interesting feature to me :) I'll try to investigate and
implement in next couple of days :)
Thanks,
-- Masayuki Igawa
>
> -Jim
>
> _
On 02/14, Andrea Frittoli wrote:
> On Wed, Feb 14, 2018 at 10:42 AM Thierry Carrez
> wrote:
>
> > Clark Boylan wrote:
> > > Last PTG the infra helproom seemed to work out for projects that knew
> > about it. The biggest problem seemed to be that other projects either just
> > weren't aware that t
Hi All,
Today, QA Office Hours @9:00 UTC is canceled due to unavailability of
members.
Happy Hacking!!
--
Masayuki Igawa
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage
+1
-- Masayuki Igawa
Key fingerprint = C27C 2F00 3A2A 999A 903A 753D 290F 53ED C899 BF89
On Sat, Apr 28, 2018, at 19:27, Ghanshyam Mann wrote:
> Hi Tempest Team,
>
> I would like to propose Felipe Monteiro (irc: felipemonteiro) to Tempest
> core.
>
> Felipe
bscribe: 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 quest
re the cue is dead or not. But I think we should fix the
failure of the job or remove the periodic jobs. Otherwise, the job
just waste the resource of the OpenStack infra..
But we should have the filter feature like a 'Project Type' of
stackalitics, probably. I think it's useful
Thank you for your great effort! I'm very proud of you as a colleague :)
-- Masayuki Igawa
On Fri, Jan 20, 2017 at 6:16 AM, Ken'ichi Ohmichi wrote:
> Hi,
>
> I will step down as PTL after this Ocata cycle.
> I was happy to see new ideas and folks who try making ideas t
enStack QA
works and review and make patches for better QA, of course. And any
contribution like reporting bugs, suggesting a lack of documentations, are
appreciated, too.
Join us and happy hacking!
[1] http://stackalytics.com/?user_id=igawa
Thanks for your consideration!
Masa
your tempest.conf and accounts.yaml file.
If you want to know more details, some documents[1] might be helpful.
[1]
http://docs.openstack.org/developer/tempest/configuration.html#tempest-configuration
.
Best Regards,
-- Masayuki Igawa
On Thu, Sep 22, 2016 at 7:27 AM, Andrea Frittoli
wrote:
>
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Best Regards,
-- Masayuki Igawa
with you. (I'm not sure I'll be there, though.)
Do we(QA team) need to register or something for the PTG?
Best Regards,
-- Masayuki Igawa
>
> Thanks
> Ken Omichi
>
> ---
> [1]: http://www.openstack.org/ptg
>
> ___
Thank you for clarifying Thierry! I got it!
I'm looking forward to see the registration:)
Best Regards,
-- Masayuki Igawa
On Wed, 12 Oct 2016 at 18:46 Thierry Carrez wrote:
> Masayuki Igawa wrote:
> > Hi Ken'ichi,
> >
> > Thanks for bring this up.
> >
Hi,
My first impression is "It's interesting" :)
I actually don't read whole of this threads, but, I re-read the QA
mission statement[1].
I feel os-faults is a little bit far from the mission statement.
Because os-faults seems like focusing on operator testing.
But I think this can be under the
Hi!
We cancel this week QA meeting because of too few attendees this timing.
See you next time :)
Best Regards,
-- Masayuki Igawa
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
71 matches
Mail list logo
