[openstack-dev] [nova] Removes the extra URL routes in Nova API

Currently I'm working on removing the stevedore [0], and move the URL routes mapping into a plain list [1]. But actually, the original URL mappings which Nova created [2] are more than that list. Due to the interface 'routes.Mapper.resources' create a set routes conforming to the Atom publish

[openstack-dev] [ironic] New contributor

Hi all I'm looking to start contributing to Ironic, and in fact I did a couple of small patches already which are still waiting to be landed/reviewed. [1] I'm finding it a little hard to find some more reasonable bugs to get started with fixing, so if any of you guys can point me at a few I

Re: [openstack-dev] [keystone] broken python35 job due to webob compatibility issues

The patch merged and the gate is now unblocked. > On Mar 29, 2017, at 5:54 PM, Lance Bragstad wrote: > > The keystone gate is currently broken [0]. This seems related to a previous > change we made to be compatible with webob 1.7 [1]. Looks like we missed a > couple spots

Re: [openstack-dev] Project Navigator Updates - Feedback Request

On 3/29/17 12:55 AM, Jimmy McArthur wrote: [snip] > What we really need is the following: > > * A project history, including the date of project inception that's > included in the TC tags. > * An API history in an easily digestible format that all projects share. > So whether you're doing micro

Re: [openstack-dev] [tripleo] container jobs are unstable

On Wed, Mar 29, 2017 at 10:07:24PM -0400, Paul Belanger wrote: > On Thu, Mar 30, 2017 at 09:56:59AM +1300, Steve Baker wrote: > > On Thu, Mar 30, 2017 at 9:39 AM, Emilien Macchi wrote: > > > > > On Mon, Mar 27, 2017 at 8:00 AM, Flavio Percoco wrote: > > >

Re: [openstack-dev] [tripleo] container jobs are unstable

On Thu, Mar 30, 2017 at 09:56:59AM +1300, Steve Baker wrote: > On Thu, Mar 30, 2017 at 9:39 AM, Emilien Macchi wrote: > > > On Mon, Mar 27, 2017 at 8:00 AM, Flavio Percoco wrote: > > > On 23/03/17 16:24 +0100, Martin André wrote: > > >> > > >> On Wed, Mar

[openstack-dev] [neutron][qos] qos service enabling in test env

Hi neutrinos, I reported a bug in plugin been sending stale data to mechanism driver [1]. Which was fixed by [2]. I am trying to write a test case as well, but seems like I am unable to see success for enabling qos service properly in test environment In

Re: [openstack-dev] [neutron]: floating IP not being set for L2 GRE packets

Strangely enough, there is no problem when I make use of a VxLAN tunnel to communicate between the VM (inside the cloud) and an external machine. In this case, the network node is performing the correct translation between the VM's local IP and the floating IP currently assigned to it. So far I

[openstack-dev] [neutron] drivers meeting back to old time for tomorrow

The drivers meeting will be back to the old time tomorrow while we find a new meeting time that works for everyone[1]. 1. https://review.openstack.org/#/c/448886/ __ OpenStack Development Mailing List (not for usage

[openstack-dev] [neutron]: floating IP not being set for L2 GRE packets

Hi, I am seeing a strange behavior when it comes to floating IPs and L2 GRE tunnels that I was hoping someone could shed light on. Inside a tenant (project) I have a VM that wants to communicate with a machine residing outside the cloud. For this purpose, a floating IP has been assigned to the

[openstack-dev] [keystone] broken python35 job due to webob compatibility issues

The keystone gate is currently broken [0]. This seems related to a previous change we made to be compatible with webob 1.7 [1]. Looks like we missed a couple spots in the original patch that are failing now that we're using a newer version of webob. There is a solution up for review [2] that

Re: [openstack-dev] All patches failing CI for validations stable/ocata branch - help needed

On 2017-03-29 18:32:09 +0200 (+0200), Florian Fuchs wrote: [...] > The error in the logs however is always the same [2] and appears > to be related to an issue with setuptools 34[3], which apparently > hit other openstack projects as well. I tried to create a patch > with a fix (excluding

Re: [openstack-dev] [TripleO] spec-lite process for tripleo

On Tue, Mar 28, 2017 at 12:09:43PM -0400, Emilien Macchi wrote: > Bringing an old topic on the table. > > We might have noticed: > > 1. Some tripleo-specs take huge amount of time before getting merged > (or even reviewed). We have been asking folks to review them every > week but unfortunately

Re: [openstack-dev] [nova][vmware] CI results show up about a week late, if at all

On 3/29/2017 2:27 PM, Tracy Jones wrote: Just FYI the VMware NSX CI job is back up and running! We have added more resources and doing more updates so we can remain stable and timely. Thanks for your patience Tracy Thanks for the update Tracy. -- Thanks, Matt

Re: [openstack-dev] [nova][vmware] CI results show up about a week late, if at all

Just FYI the VMware NSX CI job is back up and running! We have added more resources and doing more updates so we can remain stable and timely. Thanks for your patience Tracy From: Tracy Jones Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [tripleo] container jobs are unstable

On Thu, Mar 30, 2017 at 9:39 AM, Emilien Macchi wrote: > On Mon, Mar 27, 2017 at 8:00 AM, Flavio Percoco wrote: > > On 23/03/17 16:24 +0100, Martin André wrote: > >> > >> On Wed, Mar 22, 2017 at 2:20 PM, Dan Prince wrote: > >>> > >>>

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

- Original Message - > From: "Davanum Srinivas" > To: "Chris Hoge" > Cc: "OpenStack Development Mailing List (not for usage questions)" > , > "kubernetes-sig-openstack"

Re: [openstack-dev] [tripleo] container jobs are unstable

On Mon, Mar 27, 2017 at 8:00 AM, Flavio Percoco wrote: > On 23/03/17 16:24 +0100, Martin André wrote: >> >> On Wed, Mar 22, 2017 at 2:20 PM, Dan Prince wrote: >>> >>> On Wed, 2017-03-22 at 13:35 +0100, Flavio Percoco wrote: On 22/03/17 13:32

Re: [openstack-dev] [nova][api] GET or HEAD for checking trait existence

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 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

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

Team, Repo is ready: http://git.openstack.org/cgit/openstack/k8s-cloud-provider I've taken the liberty of updating it with the latest changes in the kubernetes/kubernetes repo: https://review.openstack.org/#/q/project:openstack/k8s-cloud-provider is ready So logical next step would be to add CI

[openstack-dev] [nova][api] GET or HEAD for checking trait existence

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,

Re: [openstack-dev] [acceleration]Cyborg Weekly Team Meeting 2017.03.29

Hi Team, Thanks for the great discussion, please find the meeting minutes here: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-03-29-15.00.log.html On Wed, Mar 29, 2017 at 10:33 AM, Zhipeng Huang wrote: > Hi Team, > > Just a kind

Re: [openstack-dev] All patches failing CI for validations stable/ocata branch - help needed

On Wed, Mar 29, 2017 at 12:32 PM, Florian Fuchs wrote: > Hi all, > > currently all branches proposed for the newly created stable/ocata > branch on tripleo-validations are failing CI, and the failures seem to > be unrelated to the content of the patches.[1] > > Interestingly,

[openstack-dev] All patches failing CI for validations stable/ocata branch - help needed

Hi all, currently all branches proposed for the newly created stable/ocata branch on tripleo-validations are failing CI, and the failures seem to be unrelated to the content of the patches.[1] Interestingly, the 3 gates seem to succeed/fail randomly (after a few rechecks, some gates failed that

[openstack-dev] [DLRN][tripleo][kolla][puppet] trunk.rdoproject.org maintenance on Thu 30 Mar, 9:00 UTC

FYI, trunk.rdo maintenance will affect CI jobs tomorrow. - Forwarded Message - Hi, We need to do some maintenance patching in trunk.rdoproject.org. The expected downtime is 1 hour, and during the reboot you will see errors in CI jobs that fetch packages from it. I will send a

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

Actually - in lieu of writing specs for this work, we already have a keystonemiddleware bug open for moving to oslo.cache [0]. I've opened another bug for moving to supported crypto library [1]. [0] https://bugs.launchpad.net/keystonemiddleware/+bug/1523375 [1]

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

With pycrypto removed from keystoneauth [0] (thanks Brant, Monty, and Morgan!), I did some poking at the usage in keystonemiddleware [1]. The usage is built into auth_token middleware for encrypting and decrypting things stored in cache [2], but it is conditional based on configuration [3] and

Re: [openstack-dev] [puppet] Stepping down from puppet core

On Wed, Mar 29, 2017 at 8:57 AM, Ivan Berezovskiy wrote: > Hello Puppeteers! > > I'd like to step down as a core review for the OpenStack Puppet. > Unfortunately, as you could see I didn't participate in Puppet > activities last few months. My career objective has

Re: [openstack-dev] [puppet] Stepping down from puppet core

On Wed, Mar 29, 2017 at 10:57 AM, Ivan Berezovskiy wrote: > Hello Puppeteers! > > I'd like to step down as a core review for the OpenStack Puppet. > Unfortunately, as you could see I didn't participate in Puppet > activities last few months. My career objective has

[openstack-dev] [puppet] Stepping down from puppet core

Hello Puppeteers! I'd like to step down as a core review for the OpenStack Puppet. Unfortunately, as you could see I didn't participate in Puppet activities last few months. My career objective has changed and now I won't be able even to take a look on OpenStack Puppet. This was an exciting

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

On 3/8/17 2:03 PM, Matthew Thode wrote: > So, pycrypto upstream is dead and has been for a while, we should look > at moving off of it for both bugfix and security reasons. > > Currently it's used by the following. > > barbican, cinder, trove, glance, heat, keystoneauth, keystonemiddleware, >

[openstack-dev] [keystone] No policy meeting today

Hey folks, The schedule for today's meeting is pretty empty [0] so we will go ahead and cancel. There are several policy patches in keystone and nova that are working their way through review. Instead of meeting, a better use of that time might be reviewing what we have in the pipeline (detailed

[openstack-dev] [neutron] No DVR meeting today

Both chairs have conflicts today, will resume the DVR meeting next week. Current work items and bugs can be found on the meeting page as usual, https://wiki.openstack.org/wiki/Meetings/Neutron-DVR -Brian __ OpenStack

[openstack-dev] Forum Details Summary- Hacking & Onboarding Rooms, Session Proposals & More!

Hello All! I know you have been getting bombarded with information about the upcoming Summit & Forum so I just wanted to take a moment to summarize everything into one place. Hacking Rooms: There are no specific plans for these rooms. They will be filled with roundtables for ad-hoc discussions

Re: [openstack-dev] [tripleo] Log collection of overcloud nodes

On 29/03/17 12:10 +0200, Bogdan Dobrelya wrote: On 29.03.2017 00:57, Alex Schultz wrote: Hey folks, So as part of the capture-environment-status-and-logs blueprint[0], I'm working on adding a single command to perform status and log collection of the overcloud nodes via the tripleoclient that

Re: [openstack-dev] [tripleo] Log collection of overcloud nodes

On 03/28/2017 06:57 PM, Alex Schultz wrote: > Hey folks, > > So as part of the capture-environment-status-and-logs blueprint[0], > I'm working on adding a single command to perform status and log > collection of the overcloud nodes via the tripleoclient that can be > used on the undercloud. I

Re: [openstack-dev] [tripleo] Log collection of overcloud nodes

On 29.03.2017 00:57, Alex Schultz wrote: > Hey folks, > > So as part of the capture-environment-status-and-logs blueprint[0], > I'm working on adding a single command to perform status and log > collection of the overcloud nodes via the tripleoclient that can be > used on the undercloud. I would

Re: [openstack-dev] [nova] How can i check if an instance belongs to host-aggregate

Not sure what your use case is. But basically, you can get the list of compute nodes belonging to one host aggregate and then, get the virtual instances on each compute nodes in the list. Regards, Ligong Duan From: Pradeep Singh [mailto:ps4openst...@gmail.com] Sent: Wednesday, March 29, 2017

Re: [openstack-dev] [nova] How can i check if an instance belongs to host-aggregate

Le 29/03/2017 10:23, Pradeep Singh a écrit : > Hello, > > I want to filter out some instances(to avoid some operation on them) > which are scheduled on host-aggregates. > > How can i filter out these instances from all instances list in my cloud. > Aggregates are host-based. So, if you want

Re: [openstack-dev] OpenStack Bug Smash for Pike Release

I attended the bug smash two times before. it's really like we did at PTG, but just fix bugs in same room in 3 days, It's appricated core reviewers can help review online. 2017-03-28 21:35 GMT+08:00 Sean McGinnis : > I can say from my experience being involved in the last

[openstack-dev] [acceleration]Cyborg Weekly Team Meeting 2017.03.29

Hi Team, Just a kind reminder for our team meeting today EST 11:00am on #openstack-cyborg, please find the agenda here: https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda_for_next_meeting and past logs here https://wiki.openstack.org/wiki/Cyborg/MeetingLogs . I'm now at

[openstack-dev] [tricircle]weekly meeting of Mar. 29

Hello, team, Agenda of Mar.29 weekly meeting: 1. Pike-1 prioritized patches 2. Requirements from VNF high availability across OpenStack (which will be a demo in OPNFV Beijing Summit) 3. Open Discussion How to join: # IRC meeting:

[openstack-dev] [nova] How can i check if an instance belongs to host-aggregate

Hello, I want to filter out some instances(to avoid some operation on them) which are scheduled on host-aggregates. How can i filter out these instances from all instances list in my cloud. Thanks in advance!! Thanks, Pradeep Singh

Re: [openstack-dev] Your next semi weekly gate status report

On 03/28/2017 08:57 AM, Clark Boylan wrote: 1. Libvirt crashes: http://status.openstack.org/elastic-recheck/#1643911 and http://status.openstack.org/elastic-recheck/#1646779 Libvirt is randomly crashing during the job which causes things to fail (for obvious reasons). To address this will

[openstack-dev] [openstack][neutron][fwaas] Migration of the Public attribute to Shared in FWaaS v2

Dear All, In the meeting for FWaaS held on 21st of March 2017 [1], it was decided that the "Public" attribute of FWaaS would be changed to "Shared" , keeping in line with the meaning of the "Shared" attribute in Openstack. [2] has been logged for the same.Note that this is targetted only for