+1
Thanks for your contribution, Felipe
2018年4月28日(土) 3:29 Ghanshyam Mann :
> Hi Tempest Team,
>
> I would like to propose Felipe Monteiro (irc: felipemonteiro) to Tempest
> core.
>
> Felipe has been an active contributor to the Tempest since the Pike
> cycle. He has
+1
2018-03-27 6:39 GMT-07:00 Dan Smith :
>> To the existing core team members, please respond with your comments,
>> +1s, or objections within one week.
>
> +1.
>
> --Dan
>
> __
> OpenStack Development
+1
2018年2月9日(金) 8:09 Stephen Finucane :
> On Fri, 2018-02-09 at 09:01 -0600, Matt Riedemann wrote:
> > I'd like to add Takashi to the python-novaclient core team.
> >
> > python-novaclient doesn't get a ton of activity or review, but Takashi
> > has been a solid reviewer
2018-01-22 15:09 GMT-08:00 Matt Riedemann :
> On 1/15/2018 11:04 AM, Kendall Nelson wrote:
>>
>> Election details: https://governance.openstack.org/election/
>>
>> Please read the stipulations and timelines for candidates and electorate
>> contained in this governance
2018-01-18 12:36 GMT-08:00 Doug Hellmann :
> Excerpts from Doug Hellmann's message of 2018-01-18 15:21:12 -0500:
>> Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +:
>> >
>> > On 18/01/18 18:52, Doug Hellmann wrote:
>> > > Excerpts from Graham Hayes's
Hi
I tried to install glance manually according to docs site[1] for Pike
release, and current doc site doesn't show how to create glance
database.
The bug has been already fixed and the backport patch[2] also has been
merged into Pike branch.
So how to affect these backport patches to actual doc
Yay (^_^)
2017-08-22 18:18 GMT-07:00 Matt Riedemann :
> I'm proposing that we add gibi to the nova core team. He's been around for
> awhile now and has shown persistence and leadership in the multi-release
> versioned notifications effort, which also included helping new
Hi Clark,
Thanks for your support, that works for me :-)
Thanks
---
2017-08-07 10:10 GMT-07:00 Clark Boylan <cboy...@sapwetik.org>:
> On Mon, Aug 7, 2017, at 10:01 AM, Ken'ichi Ohmichi wrote:
>> Hi
>>
>> My name is on the nonmembers list and I guess that could be be
Hi
My name is on the nonmembers list and I guess that could be because of
"Current Member Level: Speaker", not "Current Member Level: Foundation
Member".
Can I know how to change this member level?
Thanks
Ken'ichi Ohmichi
---
2017-08-03 8:07 GMT-07:00 Doug Hellmann &l
2017-06-08 10:51 GMT-07:00 Jeremy Stanley <fu...@yuggoth.org>:
> On 2017-06-08 09:49:03 -0700 (-0700), Ken'ichi Ohmichi wrote:
>> 2017-06-08 7:19 GMT-07:00 Jeremy Stanley <fu...@yuggoth.org>:
> [...]
>> > There is a foundation member directory API now which
2017-06-08 7:19 GMT-07:00 Jeremy Stanley <fu...@yuggoth.org>:
> On 2017-06-07 16:36:45 -0700 (-0700), Ken'ichi Ohmichi wrote:
> [...]
>> one of config files is 30KL due to much user information and that
>> makes the maintenance hard now. I am trying to separate user part
&
2017-05-17 11:55 GMT-07:00 Jeremy Stanley :
> On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote:
> [...]
>> we need help with completing the migration to infra. If interested
>> you can reach out to fungi (Infra team PTL) nor mrmartin (who
>> currently helps with the
+1, thanks Zhu for your work.
2017-05-16 4:22 GMT-04:00 Andrea Frittoli :
> 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
> and its community.
> She's done
Hi Jay,
Thanks for your reply.
2017-03-29 12:26 GMT-07:00 Jay Pipes <jaypi...@gmail.com>:
> On 03/29/2017 02:04 PM, Ken'ichi Ohmichi wrote:
>>
>> Hi
>>
>> I have some questions about plancement API design from
>> https://review.openstack.org/#/c/376200
Hi
I have some questions about plancement API design from
https://review.openstack.org/#/c/376200
Current implementation of the above patch (PS26) adds GET method for
checking trait existence, and tags.rst of api-wg guideline[1] requires
GET for checking trait existence.
On the other hand,
.py#L776
> On Thu, Mar 23, 2017 at 7:02 AM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
> wrote:
>>
>> 2017-03-22 14:32 GMT-07:00 Andrea Frittoli <andrea.fritt...@gmail.com>:
>> >
>> >
>> > On Wed, Mar 22, 2017 at 8:31 PM Sean McGinnis <sean.mcgin...@gmx.com>
>
2017-03-22 14:32 GMT-07:00 Andrea Frittoli <andrea.fritt...@gmail.com>:
>
>
> On Wed, Mar 22, 2017 at 8:31 PM Sean McGinnis <sean.mcgin...@gmx.com> wrote:
>>
>> On Wed, Mar 22, 2017 at 01:08:23PM -0700, Ken'ichi Ohmichi wrote:
>> > Hi,
>> >
>
Hi,
Now we need to update Tempest for following Cinder API status.
I have an idea for restructuring and happy to see feedback about that.
Now Cinder API status is
V1: Deprecated
V2: Deprecated
V3: Current
V1 API tests have been removed from Tempest side already, so we just
need to
2017-03-10 8:51 GMT-08:00 Sean McGinnis :
>> >
>> As far as I can tell:
>> - Cinder v1 if I'm not mistaken has been deprecated in Juno, so it's
>> deprecated in all supported releases.
>> - Glance v1 has been deprecated in Newton, so it's deprecated in all
>> supported
2017-03-14 18:52 GMT-07:00 Takashi Yamamoto <yamam...@midokura.com>:
> thank you for heads up.
>
> On Wed, Mar 15, 2017 at 2:18 AM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
> wrote:
>> Hi,
>>
>> Many projects are using data_utils library which is provided
Hi,
Many projects are using data_utils library which is provided by
Tempest for creating test resources with random resource names.
Now the library is provided as stable interface (tempest.lib) and old
unstable interface (tempest.common) will be removed after most
projects are switching to the
2017-03-13 12:23 GMT-07:00 Jim Rollenhagen :
> On Mon, Mar 13, 2017 at 12:58 PM, Chris Friesen
> wrote:
>>
>> On 03/10/2017 01:37 PM, John Griffith wrote:
>>
>>> Now that micro-versions are *the API versioning scheme to rule them all*
>>> one
2017-03-10 13:32 GMT-08:00 Matthew Treinish <mtrein...@kortar.org>:
> On Fri, Mar 10, 2017 at 12:34:31PM -0800, Ken'ichi Ohmichi wrote:
>> Hi John,
>>
>> Now Tempest is testing microversions only for Nova and contains some
>> testing framework
Hi John,
Now Tempest is testing microversions only for Nova and contains some
testing framework for re-using for another projects.
On this framework, we can implement necessary microversions tests as
we want and actually many microversions of Nova are not tested by
Tempest.
We can see the tested
Hi,
This is a kind of notification as the mail title.
Now QA-team is trying to test most recent stable APIs which are marked
as CURRENT in most components.
The investigation is written on
https://etherpad.openstack.org/p/tempest-api-versions-in-pike
On Keystone side, the V3 API is CURRENT and
I see Jordan's opinion here and I also faced this situation before.
I proposed a hacking patch [1] to notify wrong usage of Tempest
methods to projects and I saw some users of these methods didn't know
the definition of stable interfaces of Tempest.
We always face this issue on developments which
Hi,
QA team defines stable interfaces of Tempest for using them from
outside(tempest plugins).
We are removing a deprecated call_until_true() method from unstable
module(test.py of Tempest), but some projects are still using it.
We have prepared patches[1] for soft-landing on these projects,
Hi Andrea,
Thanks for organizing QA sessions for PTG.
2017-02-13 16:16 GMT-08:00 Andrea Frittoli :
> Hello team,
>
> I did some work on the etherpad [0] to organise the QA PTG schedule based on
> the proposed sessions.
> I separated discussion sessions from hands-on
2017-02-07 10:31 GMT-08:00 Ed Leafe <e...@leafe.com>:
> On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com> wrote:
>>
>>> To summarize, my point is that we shouldn't be worried that this case is
>>> going to set a precedent. It wou
2017-02-07 6:56 GMT-08:00 Brian Rosmaita <rosmaita.foss...@gmail.com>:
> On 2/6/17 4:28 PM, Ken'ichi Ohmichi wrote:
>> 2017-02-06 6:45 GMT-08:00 Brian Rosmaita <rosmaita.foss...@gmail.com>:
>>> On 2/6/17 5:51 AM, Jordan Pittier wrote:
>>> [super-enormous s
2017-02-06 6:45 GMT-08:00 Brian Rosmaita :
> On 2/6/17 5:51 AM, Jordan Pittier wrote:
> [super-enormous snip -- Chris, Ken, and Jordan make good points, I
> encourage you to read the entire thread; I just want to concentrate on
> one point]
>>
>> I would say we should
2017-02-06 2:51 GMT-08:00 Jordan Pittier :
>>
>> >> If we change the success status code (200 ->204) without any version
>> >> bumps, OpenStack clouds return different status codes on the same API
>> >> operations.
>> >> That will break OpenStack interoperability and
2017-02-03 9:56 GMT-08:00 Chris Dent <cdent...@anticdent.org>:
> On Thu, 2 Feb 2017, Ken'ichi Ohmichi wrote:
>>>
>>> In today's meeting [0] after briefly covering old business we spent
>>> nearly
>>> 50 minutes going round in circles discussing the co
2017-02-02 9:38 GMT-08:00 Chris Dent :
>
> Greetings OpenStack community,
>
> In today's meeting [0] after briefly covering old business we spent nearly
> 50 minutes going round in circles discussing the complex interactions of
> expectations of API stability, the need to
2017-01-27 19:35 GMT-08:00 Matt Riedemann :
> On 1/27/2017 5:00 PM, Matt Riedemann wrote:
>>
>> I noticed that this job is 100% failure since 1/21:
>>
>> http://tinyurl.com/zjh5bc5
>>
>>
>>
I am preparing for PTG sessions.
How much capacity is in each room ? 30 people or more?
We might want to have different discussions or coding meetups in
parallel in the same room, because each developer concentrates on
different working topics (Tempest, Devstack, Grenade, Patrole, etc
under QA
Hi,
I will step down as PTL after this Ocata cycle.
I was happy to see new ideas and folks who try making ideas true in
this 2 cycles.
Now QA project has a lot of components with many people's effort and
we help each other as a community.
This experience is very exciting for me, I am proud to
2017-01-13 9:25 GMT-08:00 Ian Cordasco :
> -Original Message-
> From: Ian Cordasco
> Reply: Ian Cordasco
> Date: January 13, 2017 at 08:12:12
> To: OpenStack Development Mailing List (not for usage questions)
>
2017-01-12 5:47 GMT-08:00 Brian Rosmaita :
> On 1/11/17 10:35 PM, GHANSHYAM MANN wrote:
>
>> But from meeting logs, it looks like impression was(if am not wrong) that
>> Tempest test[1] is not doing the right thing and should be ok to change.
>> I do not think this is
Hi QA-team,
We will have the first PTG[1] next Feb and it is nice to get session ideas now.
I am looking forward to seeing new ideas and discussing them together
as the community.
The etherpad is https://etherpad.openstack.org/p/qa-ptg-pike
Please write your ideas down on that if you have.
Thanks
2016-12-06 19:42 GMT-08:00 GHANSHYAM MANN :
> Hi All,
>
> Recently all gate heat gate jobs were switched to use heat devstack plugin
> and heat code was removed from devstack tree.
>
> During that tempest layer 4 job is missed and blocked the tempest gate[1].
> Also
2016-12-02 5:39 GMT-08:00 Masayuki Igawa <masay...@igawa.me>:
> Hi,
>
> On Fri, Dec 2, 2016 at 6:29 PM, Andreas Jaeger <a...@suse.com> wrote:
>> On 12/02/2016 10:03 AM, Thierry Carrez wrote:
>>> Ken'ichi Ohmichi wrote:
>>>> Hi QA-team,
>>&g
2016-12-02 7:22 GMT-08:00 Matt Riedemann :
> I'm proposing that we add Stephen Finucane to the nova-core team. Stephen
> has been involved with nova for at least around a year now, maybe longer, my
> ability to tell time in nova has gotten fuzzy over the years.
Hi QA-team,
In the big-tent policy, we continue creating new projects.
On the other hand, some projects became non-active.
That seems natural thing.
Now openstack-health[1] shows non-active project as 100% failure ratio
on "Project Status".
The project has became non-official since
Hi,
Today a new hacking 0.12.0 is released.
The release contains a new hacking rule:
[H904] Delay string interpolations at logging calls.
BTW, the hacking repo starts containing reno since this release but it
is not used yet.
Please check the git history (or
Hi QA-team,
Thanks for joining QA sessions on OpenStack Summit Barcelona.
They were interesting and good to get directions to move forward in
this development cycle.
This is a summary of these sessions for next steps and hope this helps
our works.
* (Tempest) Add an option for stopping cleanup
Hi QA team,
There are three gate jobs related to puppet jobs (like
gate-puppet-openstack-integration-4-scenario001-tempest-centos-7-nv)
and they are marked as non-voting now.
If finding these jobs failures during Tempest patch reviews even but
jenkins +1, please notify the failures to the
to us on the etherpad or this mail thread :)
Thanks
Ken Ohmichi.
2016-09-27 12:40 GMT-07:00 Ken'ichi Ohmichi <ken1ohmi...@gmail.com>:
> Hi,
>
> We have a Design Summit next month, and now we are trying to get ideas
> for QA sessions.
> There is an etherpad for ideas and it is
this on clear document and it is clear
to get a consensus about adding this.
Thanks
Ken Ohmichi
---
.
2016-10-07 12:43 GMT-07:00 Ken'ichi Ohmichi <ken1ohmi...@gmail.com>:
> Hi Timur,
>
> 2016-10-06 4:08 GMT-07:00 Timur Nurlygayanov <tnurlygaya...@mirantis.com>:
>
Thanks for pointing this up, Jordan
Before removing volume v1 API tests, it is nice to make the v2 API the
default of Tempest scenario tests.
Now the v1 and v2 is set as True on the default in the
configuration[1], and the v1 API is used in the scenario like [2].
So it is better to switch using
Hi QA team,
As you know, the first PTG(Project Teams Gathering) happens at Atlanta
20th-24th February the next year.
After Barcelona, OpenStack Summit will be separated into two parts
(conferences and design sessions) and PTG is a new format for design
sessions for developers(Please see the
the use in the
>> os-faults/examples directory.
>>
>> Regards,
>> Yaroslav Lobankov.
>>
>> On Tue, Oct 4, 2016 at 8:02 PM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
>> wrote:
>>>
>>> Hi Timur,
>>>
>>> Thanks for your e
Hi Timur,
Thanks for your explanation.
2016-09-29 6:22 GMT-07:00 Timur Nurlygayanov :
>
>> I am guessing the above "restart nodes" is for verifying each
>> OpenStack service restarts successfully, right?
>
> Yes, this is right. And we also will check that HA logic for
Hi Timur,
Thanks for picking this up, that is interesting for me.
2016-09-22 5:58 GMT-07:00 Timur Nurlygayanov :
>
> we have an idea to create the test suite with destructive/HA and advanced
> end-user scenarios for the OpenStack clusters. This test suite will
Hi,
We have a Design Summit next month, and now we are trying to get ideas
for QA sessions.
There is an etherpad for ideas and it is good if writing your ideas on that:
https://etherpad.openstack.org/p/ocata-qa-summit-topics
After getting ideas, we will arrange them into available slots for QA
Hi Hugh,
2016-09-25 22:50 GMT-07:00 Hugh Blemings :
> Hi Ohmichi-san,
>
> Firstly congratulations on becoming PTL for Quality Assurance!
Thanks
>> As previous mail, Marc has resigned from tempest-cores.
>> In addition, David also has done from tempest-cores to concentrate on
Hi Ofer,
The scenario test of Horizon has been removed from Tempest since
https://review.openstack.org/#/c/313713/
And now the test[1] exists in openstack/tempest-horizon.
The test is very simple like
* checks that the login page is available
* logs in as a regular user
* checks that the user
Hi,
As previous mail, Marc has resigned from tempest-cores.
In addition, David also has done from tempest-cores to concentrate on new work.
Thank you two for many contributions to the project and I wish your
continuous successes.
Thanks
Ken Ohmichi
Hi Marc,
Thanks for hosting a QA/Infra code sprint.
All attendees have been satisfied with rooms, coffee, food and weather.
And thanks for your work on QA project in long term.
You have brought a lot of value to us.
Thanks
Ken Ohmichi
2016-09-19 11:51 GMT+02:00 Koderer, Marc
5/09/2016 00:12, Ken'ichi Ohmichi wrote:
>> Hi Cue-team,
>>
>> As http://status.openstack.org/openstack-health/#/ , the cue gate jobs
>> continues failing 100%.
>> What is current status of the development?
>> Hopefully the job will become stable for smooth deve
Hi,
We have QA/Infra mid-cycle meetup next week, then it is hard to attend
the next meeting for most people.
So let's cancel the next week meeting.
The next irc meeting of QA will be Sep. 29th 2016 (1700 UTC).
Thanks
Ken Ohmichi
Hi Cue-team,
As http://status.openstack.org/openstack-health/#/ , the cue gate jobs
continues failing 100%.
What is current status of the development?
Hopefully the job will become stable for smooth development.
Thanks
Ken Ohmichi
Hi Chaoyi,
That is a nice point.
Now Tempest have tests for some volume v2 action APIs which doesn't
contain os-force_detach.
The available APIs of tempest are two: os-set_image_metadata and
os-unset_image_metadata like
Hi Infra-team,
(We told this a little bit on IRC, but it is happy to get more feedback widely)
Recently, we are triaging bugs of Tempest on the launchpad and that
work was fine to clean up old bugs and fixed bugs with different
patches.
There is bugdaystats[1] for showing a progress on bag days,
2016-08-11 14:53 GMT-07:00 Matt Riedemann :
> I wanted to bring this up for awareness since we're getting close to feature
> freeze and want consensus before it gets too late.
>
> Ken'ichi brought up a good question on my REST API change for the 2.37
> microversion:
>
>
2016-08-03 9:53 GMT-07:00 Andrew Laski :
> I think the discussion about whether or not this needs a microversion is
> missing the bigger question of whether or not this should be in the API to
> begin with. If it's safe to rollback from this error state why not just do
> that
2016-07-29 10:32 GMT-07:00 Sean Dague :
> On 07/28/2016 05:38 PM, Matt Riedemann wrote:
>> On 7/28/2016 3:55 PM, Matt Riedemann wrote:
>>> For os-attach-interfaces, we need that to attach/detach interfaces to a
>>> server, so those actions don't go away with 2.36. We can also list
Hi
Sorry for notifying this too lately.
We don't have enough attendees of QA meeting today and it is difficult
to run that.
So we cancel this week QA meeting.
Thanks
Ken Omichi
__
OpenStack Development Mailing List (not for
Hi Matt,
2016-07-14 11:55 GMT+09:00 Matt Riedemann :
> There are several changes in Tempest right now trying to add response schema
> validation for the 2.26 microversion which added server tags to the server
> GET response. This is needed for anything testing a
2016-06-16 2:26 GMT-07:00 Morgan Fainberg <morgan.fainb...@gmail.com>:
> On Wed, Jun 15, 2016 at 11:54 PM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
> wrote:
>>
>> This discussion was expected when we implemented the Tempest patch,
>> then I sent a mail to de
2016-06-14 17:00 GMT-07:00 Andrea Frittoli :
> Dear all,
>
> TL;DR: I'd like to propose to start running some of the existing dsvm
> check/gate jobs using Tempest pre-provisioned credentials.
>
> Full Text:
> Tempest provides tests with two mechanisms to acquire test
Hi Everyone,
As we've done the past 3 cycles we'll be having another QA/Infra code
sprint this cycle.
Previous code sprints were amazing, and we could concentrate on the
development with working together directly.
At this time, we have gotten an opportunity to hold a code sprint with
QA team and
This discussion was expected when we implemented the Tempest patch,
then I sent a mail to defcore comittee[1]
As the above ml, "A DefCore Guideline typically covers three OpenStack
releases".
That means the latest guideline needs to cover Mitaka, Liberty and Kilo, right?
In the Kilo development,
2016-06-10 17:01 GMT-07:00 Assaf Muller :
> On Fri, Jun 10, 2016 at 12:02 PM, Andrea Frittoli
> wrote:
>> Dear all,
>>
>> I'm working on making the client manager in Tempest a stable interface, so
>> that in future it may be used safely by plugins to
mail.com> wrote:
>> On Mon, 30 May 2016, 6:25 p.m. Ken'ichi Ohmichi, <ken1ohmi...@gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> There are many patches which are not updated in Tempest review queue
>>> even if having gotten negative feedback from re
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 such patches like [1].
I feel it would be nice to abandone such patches which are not updated
since the end of 2015.
Any thoughts?
2016-05-29 19:25 GMT-07:00 Alex Xu :
>
>
> 2016-05-20 20:05 GMT+08:00 Sean Dague :
>>
>> There are a number of changes up for spec reviews that add parameters to
>> LIST interfaces in Newton:
>>
>> * keypairs-pagination (MERGED) -
>>
>>
Hi Masayuki,
Sorry for late response.
That is nice because we had much conversation at the summit.
Next QA meeting is May 12th 1700UTC.
I put the agenda for the next meeting on
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_May_12th_2016_.281700_UTC.29
It is nice to add more
to do the devstack plugin in heat if there is no one is
> doing it now.
>
>
>
> Thanks
> dixiaoli
>
>
>
>
>
>
> At 2016-04-30 05:30:02, "Ken'ichi Ohmichi" <ken1ohmi...@gmail.com> wrote:
>>Hi Heat-team,
>>
>>Thanks for talki
Hi Heat-team,
Thanks for talking the topic of devstack plugin with us in Austin summit.
As you know, many projects have started to use devstack plugin in each
project repo.
and it is nice to use the plugin in heat also.
A good sample is ironic one:
Hi QA-team,
Thanks for joining QA sessions on OpenStack Summit Austin.
They were interesting and good to get directions to move forward in
this development cycle.
This is a summary of these sessions for next steps and hope this helps
our works.
1. Tempest: Cleanup
Hi,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, April 14th at 17:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_April_14th_2016_.281700_UTC.29
Anyone is
+1
Thanks for implementing microversion support, Andrey.
2016-04-13 10:53 GMT-07:00 Matt Riedemann :
> I'd like to propose that we make Andrey Kurilin core on python-novaclient.
>
> He's been doing a lot of the maintenance the last several months and a lot
> of times
2016/04/08 10:55、Anita Kuno :
>> On 04/08/2016 01:42 PM, Dmitry Tantsur wrote:
>> 2016-04-08 19:26 GMT+02:00 Davanum Srinivas :
>>
>>> Team,
>>>
>>> Steve pointed out to a problem in Stackalytics:
>>>
I much prefer this lib work.
Thanks, Chris
2016/04/08 4:32、Chris Dent
>> On Thu, 7 Apr 2016, michael mccune wrote:
>>
>> 1. version discover guideline for API microversions
>> https://review.openstack.org/243429
>>
>> 2. client interaction guideline for API
2016-03-30 12:54 GMT-07:00 Matt Riedemann :
>>> - Microversion Testing in Tempest (underway)
>
> How much coverage do we have today? This could be like novaclient where
> people just start hacking on adding tests for each microversion (assuming
> gmann would be working
2016-03-30 12:26 GMT-07:00 Sean Dague :
>
> One other issue that we've been blocking on for a while has been
> Capabilities discovery. Some API proposed adds like live resize have
> been conceptually blocked behind this one. Once upon a time there was a
> theory that JSON Home was
Hi
We have a Design Summit next month, and now we are trying to get ideas
for QA sessions.
There is an etherpad for ideas and it is great if writing your ideas
on the etherpad:
https://etherpad.openstack.org/p/newton-qa-summit-topics
After getting ideas, we will arrange them into available
2016-03-16 20:27 GMT-07:00 Assaf Muller <as...@redhat.com>:
> On Wed, Mar 16, 2016 at 10:41 PM, Jim Rollenhagen
> <j...@jimrollenhagen.com> wrote:
>> On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
>>> Hi
>>>
>>> I have o
2016-03-17 5:32 GMT-07:00 Adam Young <ayo...@redhat.com>:
> On 03/16/2016 11:01 PM, Ken'ichi Ohmichi wrote:
>>
>> 2016-03-16 19:29 GMT-07:00 Adam Young <ayo...@redhat.com>:
>>>
>>> On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
>>>>
>
2016-03-17 3:22 GMT-07:00 Jordan Pittier :
>>
>> If wanting to add negative tests, it is a nice option to implement
>> these tests on each component repo with Tempest plugin interface. We
>> can avoid operating negative tests on different component gates and
>> each
2016-03-17 15:05 GMT-07:00 Rochelle Grober :
> (Sorry for the top post. It was this or bottom post because of company
> choice of email systems)
(no problem :)
> Integration tests, corner cases, negative tests. Lots of names that don't
> have clear definitions in
2016-03-17 4:05 GMT-07:00 Andrea Frittoli <andrea.fritt...@gmail.com>:
> On Thu, Mar 17, 2016 at 2:57 AM Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
> wrote:
>>
>> 2016-03-16 19:41 GMT-07:00 Jim Rollenhagen <j...@jimrollenhagen.com>:
>> > On Wed, Mar 1
Mar 18, 2016 at 9:06 AM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
>> wrote:
>>> 2016-03-17 4:05 GMT-07:00 Andrea Frittoli <andrea.fritt...@gmail.com>:
>>>> On Thu, Mar 17, 2016 at 2:57 AM Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
>>>&
2016-03-16 19:29 GMT-07:00 Adam Young <ayo...@redhat.com>:
> On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
>>
>> Hi
>>
>> I have one proposal[1] related to negative tests in Tempest, and
>> hoping opinions before doing that.
>>
>> Now Te
2016-03-16 19:41 GMT-07:00 Jim Rollenhagen <j...@jimrollenhagen.com>:
> On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
>> Hi
>>
>> I have one proposal[1] related to negative tests in Tempest, and
>> hoping opinions before doing that.
>>
Hi
I have one proposal[1] related to negative tests in Tempest, and
hoping opinions before doing that.
Now Tempest contains negative tests and sometimes patches are being
posted for adding more negative tests, but I'd like to propose
removing them from Tempest instead.
Negative tests verify
Thank you so much, John.
Nova PTL is always a hard position, and you have accelerated our
collaboration with your leadership.
Thanks
2016-03-11 11:22 GMT-08:00 John Garbutt :
> Hi,
>
> It has been greatly rewarding serving you all as Nova PTL over the
> Liberty and Mitaka
2016-03-11 11:34 GMT-08:00 Matthew Treinish :
> Hi everyone,
>
> I'm writing this to announce that I am not running for QA PTL this cycle. I've
> been the QA PTL for the past 4 cycles and I think it's time for another person
> to take over the role. I think during the past 4
2016-03-06 15:41 GMT-08:00 Jay Pipes :
> On 03/06/2016 02:21 PM, Matt Riedemann wrote:
>>
>> Thanks, good point. I think 400 would be best here. And according to our
>> handy-dandy docs [1] it should be OK to do this without a microversion.
>
>
> Yup, 400 is correct and yes,
1 - 100 of 240 matches
Mail list logo