With the taskflow update, the only thing between upping our sqla
requirement to < 0.8.99 is pbr's requirements integration test getting a
work around for pip's behavior change (which will currently not install
netifaces because it's not on pypi... also it's largely abandoned).
Monty said he'd r
Hi,
I was looking into SSH failures and stumbled upon the following tempest issue.
The validations would not take into account the neutron agent heartbeat
timeout. This would cause tests to occasionally fail. In short there was a
window of at most 4 second for the test test_list_agent to run in
Ken'ichi,
I've been going through a bunch of the API validation reviews, and while
the specifics are fine, there are some overarching style patterns that I
think we might want to change.
First, the decorator -
@validation.schema(request_body_schema=
remote_consoles_schema
On 01/12/2014 08:00 AM, Gary Kotton wrote:
Hi,
I was looking into SSH failures and stumbled upon the following tempest
issue. The validations would not take into account the neutron agent
heartbeat timeout. This would cause tests to occasionally fail. In short
there was a window of at most 4 seco
Hi,
Just want to know do we have some policy to sync up from Oslo to other
projects?
I often noticed that there are some important changes to Oslo but the code
did not sync up to other projects on time.
Do we want to sync up from Oslo to other projects one by one or sync up
batch patches at one
Oslo Team,
We're coming up on the icehouse-2 milestone, and have several blueprints
for the milestone that need to have code reviewed. When you review this
week, please prioritize the changes associated with those blueprints.
https://launchpad.net/oslo/+milestone/icehouse-2
Thanks,
Doug
On Sun, Jan 12, 2014 at 8:59 AM, Jay Lau wrote:
> Hi,
>
> Just want to know do we have some policy to sync up from Oslo to other
> projects?
>
> I often noticed that there are some important changes to Oslo but the code
> did not sync up to other projects on time.
>
> Do we want to sync up from O
On Fri, 2014-01-10 at 10:28 -0500, Jay Dobies wrote:
> >> So, it's not as simple as it may initially seem :)
> >
> > Ah, I should have been clearer in my statement - my understanding is that
> > we're scrapping concepts like Rack entirely.
>
> That was my understanding as well. The existing Tuskar
On 01/11/2014 05:06 PM, Russell Bryant wrote:
On 01/11/2014 11:38 AM, Sean Dague wrote:
3) (still testing) https://review.openstack.org/#/c/65805/
Right now when tempest runs in the devstack-gate jobs, it runs with
concurrency=4 (run 4 tests at once). Unfortunately, it appears that
this maxes
On Fri, 2014-01-10 at 03:31 +, Gao, Fengqian wrote:
> Since we still have no new conclusion for pagination for now, shall we
> still go on with the current pagination solution?
>
> Please help to review patches:
>
> https://review.openstack.org/#/c/41869/
> https://review.openstack.org/#/c/35
Hi John,
Thank you for taking an initiative and summing up the work that need to be done
to provide PCI pass-through network support.
The only item I think is missing is the neutron support for PCI pass-through.
Currently we have Mellanox Plugin that supports PCI pass-through assuming
Mellanox A
On Fri, 2014-01-10 at 17:10 +0400, Nadya Privalova wrote:
> Idea:
> The goal is to improve performance when user gets statistics for
> meter. Now we have fixed list of statistics (min, max and so on).
> During request a user may specify the following params:
> 1. query
> 2. group_by
> 3. period
>
So I have 25 patches that I need to push to backport changes that have been
made to the nova tree that apply to the gantt tree. The problem is how do we
want to approve these patches? Given that they have already been reviewed and
approved in the nova tree do we have to go through the overhead
On Sun, Jan 12, 2014 at 5:30 PM, Dugger, Donald D wrote:
> So I have 25 patches that I need to push to backport changes that have
> been made to the nova tree that apply to the gantt tree. The problem is
> how do we want to approve these patches? Given that they have already been
> reviewed an
Thanks Doug, clear now.
Regards,
Jay
2014/1/13 Doug Hellmann
>
>
>
> On Sun, Jan 12, 2014 at 8:59 AM, Jay Lau wrote:
>
>> Hi,
>>
>> Just want to know do we have some policy to sync up from Oslo to other
>> projects?
>>
>> I often noticed that there are some important changes to Oslo but the
Excerpts from Doug Hellmann's message of 2014-01-12 14:45:11 -0800:
> On Sun, Jan 12, 2014 at 5:30 PM, Dugger, Donald D > wrote:
>
> > So I have 25 patches that I need to push to backport changes that have
> > been made to the nova tree that apply to the gantt tree. The problem is
> > how do we
On Fri, 2014-01-10 at 10:23 -0500, Doug Hellmann wrote:
>
>
>
>
> On Thu, Jan 9, 2014 at 12:02 AM, Jamie Lennox
> wrote:
> Is there any way to have WSME pass through arbitrary
> attributes to the created object? There is nothing that i can
> see in the documentation or
According to
https://www.mail-archive.com/[email protected]/msg12973.html,
it is said that we should not stop nova scheduler working for now.
BTW: I think that we may need to consider the following patches to enable
Nova use scheduler from Oslo first to reduce future work before sy
Hi,
This is a reminder that we’ll have a community meeting at #openstack-meeting at
16.00 UTC tomorrow on Jan 13.
The agenda is:
Review action items
Discuss new requirements (conditionals, direct transitions, data flow)
Open discussion
It can also be found at https://wiki.openstack.org/wiki/Mee
Jay-
Those patches are not a problem. Once they are approved and pushed into the
nova tree I will backport them over to gantt. To re-iterate, the idea is to
keep the current development going in nova and only when the gantt tree is
functional and provides the same functionality as the schedul
On 01/11/2014 09:56 AM, Sean Dague wrote:
As someone that's done a decent amount of hacking on
status.html/status.js, I think we're getting to a level of complexity on
our JS status pages that we should probably stop doing this all inline
(probably should have stopped a while ago).
I'd like to p
Hi Sean,
Thank you for reviewing patches,
2014/1/12 Sean Dague :
> Ken'ichi,
>
> I've been going through a bunch of the API validation reviews, and while the
> specifics are fine, there are some overarching style patterns that I think
> we might want to change.
>
> First, the decorator -
>
> @val
Cool! Thanks Don.
Regards,
Jay
2014/1/13 Dugger, Donald D
> Jay-
>
>
>
> Those patches are not a problem. Once they are approved and pushed into
> the nova tree I will backport them over to gantt. To re-iterate, the idea
> is to keep the current development going in nova and only when the
If all you're looking for is a javascript-based in-browser templating
system, then handlebars is a fine choice. I'm not certain on how complex
status.html/status.js is, however if you expect it to grow to something
more like an application then perhaps looking at angular as a full
application frame
> > Last, is a question, is it possible to currently run the full API an build a
> > json schema for it all? Or to query these validating schemas? We *really*
> > want that over in tempest, so we can completely drop the manual creation of
> > negative testing, and just fuzz known bad against the s
I'm facing this issue when listing tests using testr. Anyone else facing
this issue?
[bhuvan@build tempest]$ tools/with_venv.sh testr list-tests
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
${PYTHON:-pytho
On Mon, Jan 13, 2014 at 08:49:35AM +0530, Bhuvan Arumugam wrote:
> I'm facing this issue when listing tests using testr. Anyone else facing
> this issue?
>
> [bhuvan@build tempest]$ tools/with_venv.sh testr list-tests
> running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
> OS_STDERR_CAPTURE=${OS_S
On my phone so will be very brief but perhaps the extensions extension could
publish the jsonschema(s) for the extension. I think the only complicating
factor would be where extensions extend extensions but I think it's all doable.
Chris
—
Sent from Mailbox for iPhone
On Mon, Jan 13, 2014
On 01/12/2014 10:14 PM, Matthew Treinish wrote:
Last, is a question, is it possible to currently run the full API an build a
json schema for it all? Or to query these validating schemas? We *really*
want that over in tempest, so we can completely drop the manual creation of
negative testing, an
Thank you, Matt. Originally I had set it as:
OS_TEST_PATH=./tempest
When I set it as,
OS_TEST_PATH=./tempest/tests
the unit tests are listed.
bhuvan@build tempest]$ OS_TEST_PATH=./tempest/tests tools/with_venv.sh
testr list-tests
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_C
Hi,
I added two comments about enhancement of sorting and location based query
at the discussion wiki page.
https://wiki.openstack.org/wiki/Talk:MetadataSearchAPI#Metadata_Search_API_Discussion_page
On 13 Jan 2014 12:15, "Bhuvan Arumugam" wrote:
> It behave differently when I list tempest tests. All tests are listed in
single line with unicode characters. The command exit with non-zero exit
code, with import errors. Any idea on whats going on?
The import errors are due to modules not import
I think we should still review the patches in case of any merging issues
with Gantt code. If the volume of reviews is high, then we have to increase
the number of reviewers.
I was part of the discussions for an external scheduler, I will dedicate
some time for +1...
Afaik, the current weekly meet
On 13 January 2014 11:45, Doug Hellmann wrote:
>
>
>
> On Sun, Jan 12, 2014 at 5:30 PM, Dugger, Donald D
> wrote:
>>
>> So I have 25 patches that I need to push to backport changes that have
>> been made to the nova tree that apply to the gantt tree. The problem is how
>> do we want to approve t
34 matches
Mail list logo
