Hi, all.
Recently, I do some research about RPC by using oslo-messaging. I write
some demo code about RPC server and RPC client by following here [1]. And
the demo codes locate here[2].
I think there is something wrong about these codes. The server code
doesn't print response message when
On 2017-06-23 08:05, Rikimaru Honjo wrote:
> Hi,
>
> I run "tox -epy27" in nova repository just now.
> As a result, following error message was printed.
>
>> HTTPError: 404 Client Error: Not found for url:
>> https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt
>>
>
On 2017/06/23 16:17, Andreas Jaeger wrote:
On 2017-06-23 08:05, Rikimaru Honjo wrote:
Hi,
I run "tox -epy27" in nova repository just now.
As a result, following error message was printed.
HTTPError: 404 Client Error: Not found for url:
https://git.openstack.org/cgit/openstack/requirements/pla
Hello,
In Queen OpenStack release, We have a community goal to split In-Tree
tempest plugin to a separate repo[1.].
I have a couple question regarding the tempest tests movement within
tempest plugins.
[1.] Since some of the core OpenStack projects like Nova, Glance and
Swift does have tempest p
Just a heads up: The recent failure of git.openstack.org - seen by many
jobs with a download failure of the upper-constraints.txt file - has
been fixed. Feel free to recheck failed changes where jobs failed to
download from git.openstack.org.
thanks to Clark, Monty, and Ian from the Infra team!
An
On Fri, Jun 23 2017, Deepthi V V wrote:
> Current gnocchi code supports RBAC at operation level
> [gnocchi/gnocchi/rest/policy.json].
> Is it possible to add RBAC for attributes in a resource?
> For eg: Restrict resource search/show should display specific attributes only
> when query is performe
Can you provide your ml2_conf.ini values you are using?
On Thu, Jun 22, 2017 at 7:06 AM, Margin Hu wrote:
> thanks.
>
> I met an issue , I configured three ovs bridge ( br-ex, provision,
> provider) in ml2_conf.ini but after I reboot the node , found only 2
> bridges flow table is normal , the
Hi Saverio,
Comments and questions inline:
First of all, which backend are you using? the l2gateway agent? or
something like OpenDaylight?? I'm currently testing an L2GW scenario with
ODL.
On Mon, May 29, 2017 at 4:54 PM, Saverio Proto
wrote:
> Hello,
>
> I have a question about the l2gw. I d
Hi!
Here is our regular update on the status of a number of TC-proposed
governance changes, in an attempt to rely less on a weekly meeting to
convey that information.
You can find a regularly-updated status list of all open topics at:
https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
On Wed, Jun 21, 2017 at 12:47:27PM +0200, Henning Schild wrote:
> Am Tue, 20 Jun 2017 10:04:30 -0400
> schrieb Luiz Capitulino :
>
> > On Tue, 20 Jun 2017 09:48:23 +0200
> > Henning Schild wrote:
> >
> > > Hi,
> > >
> > > We are using OpenStack for managing realtime guests. We modified
> > > it
Hey Blair,
Thanks ( I appreciate your offer of assistance. We are in full swing at the
moment. The spec is very close to being merged. You can view that here:
https://review.openstack.org/#/c/472275/
I am still looking for someone who can help us out with the pandoc conversion.
I am happy to
Zane Bitter wrote:
> But back in the day we had a process (incubation) for adding stuff to
> OpenStack that it made sense to depend on being there. It was a highly
> imperfect process. We got rid of that process with the big tent reform,
> but didn't really replace it with anything at all. Tags nev
Lance Bragstad wrote:
> Is the role of a goal "champion" limited to a single person? Can it be
> distributed across multiple people pending actions are well communicated?
I'm a bit torn on that. On one hand work can definitely (and probably
should) be covered by multiple people. But I like the ide
On Wed, 21 Jun 2017 at 20:08 Jason Dillaman wrote:
> On Wed, Jun 21, 2017 at 12:32 PM, Jon Bernard wrote:
> > I suspect you'd want to enable layering at minimum.
>
> I'd agree that layering is probably the most you'd want to enable for
> krbd-use cases as of today. The v4.9 kernel added support
On 06/23/2017 05:44 AM, Thierry Carrez wrote:
> Lance Bragstad wrote:
>> Is the role of a goal "champion" limited to a single person? Can it be
>> distributed across multiple people pending actions are well communicated?
>
> I'm a bit torn on that. On one hand work can definitely (and probably
> s
On 22 June 2017 at 14:01, Dougal Matthews wrote:
>
>
> On 22 June 2017 at 11:01, Thierry Carrez wrote:
>
>> Thierry Carrez wrote:
>> > Renat Akhmerov wrote:
>> >> We have a weekly meeting next Monday, will it be too late?
>> >
>> > Before Thursday EOD (when the Pike-2 deadline hits) should be OK
Dougal Matthews wrote:
>> We have been trying to break the requirement on mistral (from
>> tripleo-common) but it is proving to be harder than expected. We are
>> really doing some nasty things, but I wont go into details here :-)
>> If anyone is interested, feel free to reach out.
Hi kevin,
[ovs]
bridge_mappings = physnet1:br-ex,physnet2:provision,physnet3:provider
ovsdb_connection = tcp:10.53.16.12:6640
local_ip = 10.53.32.12
you can check the attachement, and more logs can be found at
https://bugs.launchpad.net/neutron/+bug/1697243
On 6/23 16:43, Kevin Benton wrote:
On Thu, 22 Jun 2017, Shewale, Bhagyashri wrote:
* who or what needs to consume these JSON samples?
The users of placement API can rely on the request/response for different
supported placement versions based on some tests running on the OpenStack CI
infrastructure.
Right now, most of the plac
Hi everyone,
This morning (afternoon) the specification for the documentation migration was
merged. Thanks to all that took time to review :)
You can now view here in all its glory:
https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
If you have any questions,
Yes, let's move discussion to bug report.
On Fri, Jun 23, 2017 at 5:01 AM, Margin Hu wrote:
> Hi kevin,
>
> [ovs]
> bridge_mappings = physnet1:br-ex,physnet2:provision,physnet3:provider
> ovsdb_connection = tcp:10.53.16.12:6640
> local_ip = 10.53.32.12
> you can check the attachement, and more
We'll do that.
Thanks
Renat Akhmerov
@Nokia
23 июня 2017 г., 18:54 +0700, Thierry Carrez , писал:
> Dougal Matthews wrote:
> > > We have been trying to break the requirement on mistral (from
> > > tripleo-common) but it is proving to be harder than expected. We are
> > > really doing some nasty
As no objections were recorded, I'm proceeding with the plan.
Governance change for ironic-python-agent-builder:
https://review.openstack.org/476900.
On 05/22/2017 04:59 PM, Dmitry Tantsur wrote:
On 05/22/2017 03:10 PM, Sam Betts (sambetts) wrote:
I would like to suggest that we create a new
I can say for Mistral . We only planned to add Mistral docs to the central repo
but didn’t do it yet. So, as far as I understand, we don’t need to move
anything. We’ll review the spec and adjust the folder structure according to
the proposed.
Thanks
Renat Akhmerov
@Nokia
23 июня 2017 г., 3:32
On Fri, Jun 23, 2017 at 6:14 AM, Sean Dague wrote:
> On 06/23/2017 05:44 AM, Thierry Carrez wrote:
>> Lance Bragstad wrote:
>>> Is the role of a goal "champion" limited to a single person? Can it be
>>> distributed across multiple people pending actions are well communicated?
>>
>> I'm a bit torn
You're using the eventlet executor and time.sleep(1) but not
monkey-patching your server for eventlet.
Try adding:
import eventlet
eventlet.monkey_patch()
Above your other imports in the server file.
Best,
-jay
On 06/23/2017 02:58 AM, zhi wrote:
Hi, all.
Recently, I do some research a
On 23/06/17 05:31, Thierry Carrez wrote:
Zane Bitter wrote:
But back in the day we had a process (incubation) for adding stuff to
OpenStack that it made sense to depend on being there. It was a highly
imperfect process. We got rid of that process with the big tent reform,
but didn't really repla
> On Jun 23, 2017, at 8:57 AM, Renat Akhmerov wrote:
>
> I can say for Mistral . We only planned to add Mistral docs to the central
> repo but didn’t do it yet. So, as far as I understand, we don’t need to move
> anything. We’ll review the spec and adjust the folder structure according to
> t
On 06/22/2017 11:59 AM, Fox, Kevin M wrote:
My $0.02.
That view of dependencies is why Kubernetes development is outpacing OpenStacks
and some users are leaving IMO. Not trying to be mean here but trying to shine
some light on this issue.
Kubernetes at its core has essentially something kin
Am Fri, 23 Jun 2017 11:11:10 +0200
schrieb Sahid Orentino Ferdjaoui :
> On Wed, Jun 21, 2017 at 12:47:27PM +0200, Henning Schild wrote:
> > Am Tue, 20 Jun 2017 10:04:30 -0400
> > schrieb Luiz Capitulino :
> >
> > > On Tue, 20 Jun 2017 09:48:23 +0200
> > > Henning Schild wrote:
> > >
> > > >
Hi Doug,
first of all sorry for the late response. I am the current PTL of the
openstack-chef project and read the spec a while ago, but did not really
connect it to our project. To be honest, i am not really sure what we would
move and how to do it. Currently we have some wiki pages, but most
The Barbican team is currently lacking a UWSGI expert.
We need help identifying what work items we have to meet the UWSGI community
goal.[1]
Could someone with expertise in this area review our code and docs [2] and help
me put together a to-do list?
Thanks!
Dave (dave-mccowan)
[1] https://gove
The spec [1] with the plan to migrate project-specific docs from
docs.openstack.org to each project has merged.
There are a number of steps outlined in there which need people from the
project teams, e.g. nova, to do for their project. Some of it we're
already doing, like building a config ref
> On Jun 23, 2017, at 12:10 PM, j.kl...@cloudbau.de wrote:
>
> Hi Doug,
>
> first of all sorry for the late response. I am the current PTL of the
> openstack-chef project and read the spec a while ago, but did not really
> connect it to our project. To be honest, i am not really sure what we w
On 06/23/2017 09:35 AM, Henning Schild wrote:
Am Fri, 23 Jun 2017 11:11:10 +0200
schrieb Sahid Orentino Ferdjaoui :
In Linux RT context, and as you mentioned, the non-RT vCPU can acquire
some guest kernel lock, then be pre-empted by emulator thread while
holding this lock. This situation block
The Nova bug backlog is just over 800 open bugs, which while
historically not terrible, remains too large to be collectively usable
to figure out where things stand. We've had a few recent issues where we
just happened to discover upgrade bugs filed 4 months ago that needed
fixes and backports.
Hi
On 22/06/17 01:57 PM, Mike Perez wrote:
> An idea that came from the meeting was creating a role of "Champions",
> who are the drum beaters to get a goal done by helping projects with
> tracking status and sometimes doing code patches. These would be
> interested volunteers who have a good unders
Sean,
This sounds amazing and Swift could definitely use some [automated]
assistance here. It would help if you could throw out a WIP somewhere.
First thought that comes to mind tho storyboard.o.o :\
-Clay
On Fri, Jun 23, 2017 at 9:52 AM, Sean Dague wrote:
> The Nova bug backlog is just
I think more than one champion is helpful in some cases, but its dangerous
when you get more than two that each person thinks the other two will
handle things unless they are very communicative with one another :)
Somewhere else in this thread the idea of a committee and a chair was
mentioned whic
Kevin, just one comment inline below.
On Thu, Jun 22, 2017 at 3:33 PM, Fox, Kevin M wrote:
> No, I'm not necessarily advocating a monolithic approach.
>
> I'm saying that they have decided to start with functionality and accept
> whats needed to get the task done. Theres not really such stro
On Thu, Jun 22, 2017 at 4:38 PM, Zane Bitter wrote:
> (Top posting. Deal with it ;)
>
>
Yes, please keep the conversation going; top posting is fine, the k8s
issue isn't 'off topic'.
> You're both right!
>
> Making OpenStack monolithic is not the answer. In fact, rearranging Git
> repos has
On Fri, Jun 23, 2017 at 04:11:50PM +, Dave McCowan (dmccowan) wrote:
> The Barbican team is currently lacking a UWSGI expert.
> We need help identifying what work items we have to meet the UWSGI community
> goal.[1]
> Could someone with expertise in this area review our code and docs [2] and
On Thu, 2017-06-22 at 22:57 +, gordon chung wrote:
>
> On 22/06/17 04:23 PM, mate...@mailbox.org wrote:
> > Hello everyone !
> >
> > I'm sorry that I'm disturbing you, but I was sent here from
> > openstack-operators ML.
> > On my Mitaka test stack I installed Gnocchi as database for measu
On 23/06/17 03:08 PM, mate...@mailbox.org wrote:
> The quantity of metrics is very low. I'm not sure that batch_size works.
> Regarding the batch_timeout. What will be when the timeout reached ? Will
> ceilometer throw error to the log file and
> discard the whole batch ? I've got this timeout s
Hello all,
Every month we have people asking on IRC or the dev mailing list having
interest in working on OpenStack, and sometimes they're given different
answers from people, or worse, no answer at all.
Suggestion: lets work our efforts together to create some common
documentation so that all te
On Wed, Jun 21, 2017 at 10:13 AM, Ilya Shakhat wrote:
> Hi Ken,
>
> Please check scenarios and reports that exist in Performance Docs. In
> particular you may be interested in:
> * O.M.Simulator - https://github.com/openstack/o
> slo.messaging/blob/master/tools/simulator.py
> * MQ performance
Great idea!
I would also throw another issue new people often have (I had it too).
Namely what to contribute. Lot's of people wants to do something but
not quite know where to start.
So few ideas for start:
* List of triaged bugs
* List of work items of large blueprits
Thoughts,
Michal
On 23 Jun
On 6/23/17, 2:24 PM, "Matthew Treinish" wrote:
>On Fri, Jun 23, 2017 at 04:11:50PM +, Dave McCowan (dmccowan) wrote:
>> The Barbican team is currently lacking a UWSGI expert.
>> We need help identifying what work items we have to meet the UWSGI
>>community goal.[1]
>> Could someone with exp
I will help
On Sat, Jun 24, 2017 at 12:23 AM, Matt Riedemann
wrote:
> The spec [1] with the plan to migrate project-specific docs from
> docs.openstack.org to each project has merged.
>
> There are a number of steps outlined in there which need people from the
> project teams, e.g. nova, to do f
49 matches
Mail list logo