[openstack-dev] OpenStack Dev Digest 10- 16

HTML Version: http://wp.me/p1eUil-255 Updates - Release schedule clarification after Ocata [5] - Nova placement/resource providers [6][12] - Stuart McLaren stepping down from glance core [8] Allowing Teams Based on Vendor-specific Drivers (cont) [1] - Narrowed down

[openstack-dev] Which service is using port 8778?

Hi, all, Starting yesterday, Senlin's gate jobs kept failing due to two reasons: 1. Recent changes to tempest is breaking our plugin. This is being fixed. 2. Senlin API cannot bind it to port 8778 now. So, we are wondering which service else is using port 8778? Thanks in advance for any

Re: [openstack-dev] Which service is using port 8778?

Yes, it seems placement API using it [1] > 1. Recent changes to tempest is breaking our plugin. This is being >fixed. Tempest patch should fix issue but port issue blocking that[2] For port think, I think we can change the placement API port to something else. I will propose and we can get

Re: [openstack-dev] [neutron][nova][oslo][osprofiler] Next step of OSprofiler

Hi Rui Wang, We also recognize the benefit of OSProfiler and are on the way to improve it. > 1. The integration with neutronclient, > nova and novaclient has not been done yet. Yes, the works in Nova are in reviewing but Nova team seems very busy in this cycle and they want to have more tests

[openstack-dev] [Cinder] Does cinder use novaclient?

Hi Cinder community, Does cinder use novaclient? What's the use of cinder/compute/nova.py? I find that there seems to have some problems when construct novaclient in the file cinder/compute/nova.py, but I think the file is not being used. Would you explain the use of this file or how does

[openstack-dev] [Congress] [infra] tempest job timeout appears shorter than configured

The congress {pipeline}-congress-dsvm-api-{node}{suffix} check/gate job seems to timeout around the 60 minute mark even though the project config appears to set it for 70min. Any hints as to why? Are there two different measures of time? Thanks so much!

Re: [openstack-dev] [api][zun] Effective URL for resource actions

Yea, looks like no consensus at here. Look at the discussion Chris pointed to, the "/containers//action" sounds a good API for tasks. But we also see the disadvantage for it. When we want to use URL to identifying an action, we found all the actions into a single API. We faced this problem

Re: [openstack-dev] [Zun][Glare][Glance] Building Docker images

I believe we can add Glare driver to Zun [1] and allow it to pull container images from Glare directly. Then, as Kairat mentioned, we should prepare 'container-images' artifact type for Glare [2]. For sure, we can use 'images' (which are actually vm images) to store containers, but it's ugly,

Re: [openstack-dev] [Congress] [infra] tempest job timeout appears shorter than configured

On 2016-12-19 17:33:10 -0800 (-0800), Eric K wrote: > The congress {pipeline}-congress-dsvm-api-{node}{suffix} check/gate job > seems to timeout around the 60 minute mark even though the project config > appears to set it for 70min. Any hints as to why? Are there two different > measures of time?

Re: [openstack-dev] multi-attach-volume for rbd

On 12/19/2016 2:24 AM, Avishay Traeger wrote: Multi-attach also happens during VM migration: (attach volume to destination host, move VM to destination host, detach volume from source host). It's not clear if rbd's limitation affects this as well - it's not clear from the bug report or the

Re: [openstack-dev] Which service is using port 8778?

On Tue, Dec 20, 2016 at 06:16:59AM +, Ghanshyam Mann wrote: > Yes, it seems placement API using it [1] > > > 1. Recent changes to tempest is breaking our plugin. This is being > >fixed. > Tempest patch should fix issue but port issue blocking that[2] > > For port think, I think we can

Re: [openstack-dev] Which service is using port 8778?

Changing placement API port to 8780 [1], hope this is not being used by any services. But I am not sure how to check all used port currently as wiki does not seems to have all. .. [1] https://review.openstack.org/#/c/412770/ -gmann > -Original Message- > From: Ghanshyam Mann

Re: [openstack-dev] [infra] Any way to disable zuul status page auto-refresh?

You could try saving the status page and modifying the refresh time, or similarly you could checkout zuul and run the webapp locally[0]. You'd have to point it at [1] and modify the refresh times here [2]. (The status page in the zuul tree is different to the one on status.o.o). Cheers, Josh [0]

Re: [openstack-dev] [api][zun] Effective URL for resource actions

On Tue, Dec 20, 2016 at 10:14:49AM +0800, Alex Xu wrote: > Yea, looks like no consensus at here. Look at the discussion Chris pointed > to, the "/containers//action" sounds a good API for tasks. Did you mean "/containers//actions" ? > But we also see the disadvantage for it. When we want to use

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

> > On Dec 19, 2016, at 14:31, Tony Breeds wrote: > > On Mon, Dec 19, 2016 at 09:18:20AM -0800, Samuel Cassiba wrote: > >> The Chef OpenStack cookbooks team is way late to the party. The cookbooks >> (openstack/cookbook-openstack-*, openstack/openstack-chef-repo )

Re: [openstack-dev] Upgrade skip release

On 12/19/2016 4:26 PM, Chris Friesen wrote: On 12/19/2016 03:17 PM, Ajay Kalambur (akalambu) wrote: Hi Chris Thanks for the response. What were the specific problem areas you saw when upgrading from Kilo to Mitaka which were introduced by skipping Liberty? There were issues with RPC

Re: [openstack-dev] OpenStack Dev Digest 10- 16

Use this link for HTML Version: http://www.openstack.org/blog/2016/12/openstack-developer-mailing-list-digest-december-10-16/ On Mon, Dec 19, 2016 at 10:54 PM Kendall Nelson wrote: > HTML Version: http://wp.me/p1eUil-255 > > Updates > >- > >Release schedule

Re: [openstack-dev] [api][zun] Effective URL for resource actions

On Mon, Dec 19, 2016 at 11:57:26AM +, Chris Dent wrote: > On Fri, 16 Dec 2016, Hongbin Lu wrote: > > >I am from the Zun team and I wanted to consult with you about the API > >design. Our team was discussing what is the best API design for > >exposing different container operations [1]. There

[openstack-dev] [nova] Help: How to make Nova official support AArch64?

Hello Nova, Greetings from ARM and Linaro :D This is Kevin Zhao from ARM. Nowadays Linaro and other contributors have submitted some patches to Nova community , fixing bugs for Nova running on AArch64. Now we can successfully running a OpenStack cluster on AArch64 and pass much of the

Re: [openstack-dev] [api][zun] Effective URL for resource actions

2016-12-20 11:34 GMT+08:00 Qiming Teng : > On Tue, Dec 20, 2016 at 10:14:49AM +0800, Alex Xu wrote: > > Yea, looks like no consensus at here. Look at the discussion Chris > pointed > > to, the "/containers//action" sounds a good API for tasks. > > Did you mean

Re: [openstack-dev] [neutron] Where will Neutron go in future?

Hi, Srider. Thanks for your reply. I still have a question about SG and FWaaS. VM's east-west traffic belongs to FWaaS or SG? What about VM's north-south traffic? I think that VM's east-west traffic belongs to SG and the north-south traffic belongs to FWaaS, isn't it? :) Thanks Zhi Chang

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 On 12/16/16, 12:35 PM, "Brandon Logan" wrote: +1! On Fri, 2016-12-16 at 00:58 +0100, Armando M. wrote: > Hi neutrinos, > > I would like to propose Ryan and Nate as the go-to fellows for > service-related patches. > > Both

Re: [openstack-dev] [neutron][upgrades] no meetings till Jan 9th

Ihar Hrachyshka wrote: Hi, we skip two next meeting slots and will meet again Jan 9th usual time. Happy holidays y’all! Ihar OK just to clarify, I am talking about *UPGRADES* neutron meeting, not general neutron team meeting. Sorry for any misunderstanding. Ihar

Re: [openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list

On 12/19/2016 07:21 AM, Steven Dake (stdake) wrote: > Folks, > > I am in favor of using a new tag called [rdo] such that RDO (or its > transitive dependencies) can be discussed and filtered by email clients as it > relates to development topics that affect the broader OpenStack ecosystem. > As

Re: [openstack-dev] [TripleO] DB cleanup cron jobs added to rh1

On 16 December 2016 at 21:40, Ben Nemec wrote: > Just a heads up for everyone, I've added some DB cleanup jobs to rh1 which > will hopefully prevent the performance degradations over time that we've > been seeing in that environment. Specifically, the crontab now looks

Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

On 2016-12-19 11:29:51 +1100 (+1100), Tony Breeds wrote: [...] > Given that we can't just re-run the job and expect success what > options do we have to publish an 11.0.2 tarball? > > I'm assuming this will be a somewhat manual process, given that is > there anything preventing us from tagging

[openstack-dev] [neutron][nova][oslo][osprofiler] Next step of OSprofiler

Hi folks, I’m glad to tell that OSprofiler would help a lot for us to find problems and slowness in system. I really hope to help improve it. I noticed some problems: 1. The integration with neutronclient, nova and novaclient has not been done yet. 2. The blueprint

Re: [openstack-dev] [neutron] Where will Neutron go in future?

You are correct LBaaS development has moved to the Octavia team. However, Octavia will have a way for 3rd party load balancers to plug in instead of the Octavia load balancing solution. The Octavia team is currently deciding if it should continue to support the Haproxy namespace driver as part

[openstack-dev] [neutron][upgrades] no meetings till Jan 9th

Hi, we skip two next meeting slots and will meet again Jan 9th usual time. Happy holidays y’all! Ihar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [infra] Any way to disable zuul status page auto-refresh?

The subject pretty much covers it. When there are a lot of jobs on the zuul status page, it kind of brings my browser to its knees, which makes it hard to navigate the page. I know you can filter it, but sometimes I want to see all of the jobs in a queue so that isn't always an option. If

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

On Nov 21, 2016, at 18:35, Tony Breeds wrote: > > Hi all, >I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects

Re: [openstack-dev] [Cinder] Marking Cloudbyte driver as unsupported

Hmm, nice! Thanks! On Mon, Dec 19, 2016 at 11:48 AM, Sean McGinnis wrote: > On Mon, Dec 19, 2016 at 08:27:52AM -0200, Erlon Cruz wrote: > > Hi Sean, what is the command to generate this output? > > > > On Fri, Dec 16, 2016 at 6:27 PM, Sean McGinnis

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500: > 3) Choose Goals for Pike. > Some of us already did, but we might want to start looking at what > Goals we would like to achieve during Pike cycle. > I was thinking at giving a score to the Goals, that could be > calculated by

[openstack-dev] [heat] A question on the endpoint of Heat

Hi, Heat stackers: May I ask a question about the endpoint of Heat. I see the endpoints of Heat registered to Keystone look like this. 'http://10.229.45.150:8004/v1/$(project_id)s' . My question is that why use '$' instead of '%' as the replacement symbol. Is there some kind of rule?

[openstack-dev] [OSSN-0074] Nova metadata service should not be used for sensitive information

OpenStack Security Note: 0074 Nova metadata service should not be used for sensitive information --- ### Summary ### A recent security report has highlighted how users may be using the metadata service to store security sensitive information. The Nova metadata service should not be considered

Re: [openstack-dev] [Cinder] Marking Cloudbyte driver as unsupported

Hi Sean, what is the command to generate this output? On Fri, Dec 16, 2016 at 6:27 PM, Sean McGinnis wrote: > Checking name: CloudByte CI > last seen: 2016-09-27 11:49:45 (80 days, 5:38:50 old) > last success: 2016-09-27 11:49:45 (80 days, 5:38:30 old) > success rate: 72%

Re: [openstack-dev] [neutron] Is it possible that creating a port and binding it with 2 IPs

Thank you very much for the reply, and the reply are work! Vincent Chao 2016-12-06 18:45 GMT+09:00 Kevin Benton : > +1. Also, if you just need an additional IP for the instance that isn't > used by other instances, you can do a port update and add additional IPs to > the

[openstack-dev] Upgrade skip release

Hi Does openstack support skipping releases if one is performing a maintanance upgrade. Would alembic migrations work for instance from Liberty to Newton I think we would have to stop all existing services since API backward compatiblity is only 1 release front and back right? Ajay

Re: [openstack-dev] Upgrade skip release

Hi Chris Thanks for the response. What were the specific problem areas you saw when upgrading from Kilo to Mitaka which were introduced by skipping Liberty? Ajay On 12/19/16, 12:36 PM, "Chris Friesen" wrote: >On 12/19/2016 01:56 PM, Ajay Kalambur (akalambu)

Re: [openstack-dev] Upgrade skip release

On 12/19/2016 01:56 PM, Ajay Kalambur (akalambu) wrote: Hi Does openstack support skipping releases if one is performing a maintanance upgrade. Would alembic migrations work for instance from Liberty to Newton OpenStack as a whole only supports N to N+1 upgrades, though it's possible some

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are delighted to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1.

[openstack-dev] [Ironic] Retiring ironic-webclient

As discussed at the last summit during the contributor meet-up, as well as during today’s Ironic team meeting[0], we will be retiring the ironic-webclient. This is due to a number of factors, the largest being that the primary contributor has changed positions and is no longer contributing,

Re: [openstack-dev] Upgrade skip release

On 12/19/2016 03:17 PM, Ajay Kalambur (akalambu) wrote: Hi Chris Thanks for the response. What were the specific problem areas you saw when upgrading from Kilo to Mitaka which were introduced by skipping Liberty? There were issues with RPC incompatibility, object versioning, DB upgrades, etc.

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

On Mon, Dec 19, 2016 at 09:18:20AM -0800, Samuel Cassiba wrote: > The Chef OpenStack cookbooks team is way late to the party. The cookbooks > (openstack/cookbook-openstack-*, openstack/openstack-chef-repo ) should have > had their liberty branches EOL’d. I have checked and no open reviews exist >

Re: [openstack-dev] [api][zun] Effective URL for resource actions

On Fri, 16 Dec 2016, Hongbin Lu wrote: I am from the Zun team and I wanted to consult with you about the API design. Our team was discussing what is the best API design for exposing different container operations [1]. There are two proposed options: 1. Expose multiple URLs for individual

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

On Fri, Dec 16, 2016 at 4:16 PM Neil Jerram wrote: > On Fri, Dec 16, 2016 at 4:08 PM Steve Gordon wrote: > > > If you haven't already I would suggest grabbing qemu-kvm-ev from the > CentOS > > > Virt SIG repos: > > > > > >

[openstack-dev] [MassivelyDistributed] Next IRC meeting - Jan 4 2017

Dear all, Due to the vacation period, I propose to cancel our meeting this week. The next meeting will be held on Jan, the 4th. Season's greetings, ad_rien_ __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] multi-attach-volume for rbd

Multi-attach also happens during VM migration: (attach volume to destination host, move VM to destination host, detach volume from source host). It's not clear if rbd's limitation affects this as well - it's not clear from the bug report or the patch. On Thu, Dec 15, 2016 at 1:30 AM, Matt

[openstack-dev] [monasca] Team meeting on 28 Dec

Hello everyone, should we cancel the team meeting on 28 Dec? Most of us will be in vacation I assume. Greetings Witek __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Cinder] Marking Cloudbyte driver as unsupported

On Mon, Dec 19, 2016 at 08:27:52AM -0200, Erlon Cruz wrote: > Hi Sean, what is the command to generate this output? > > On Fri, Dec 16, 2016 at 6:27 PM, Sean McGinnis > wrote: I'm using a modified version of the lastcomment script:

Re: [openstack-dev] [neutron] Where will Neutron go in future?

Hi Zhi: FWaaS has been seen more as an edge (on L3 ports) use case as opposed to SG which is on a VM port. Also, as u can see there are differences in the attributes on the Rule specification at the most basic level. At this point, we are working thru the implementation of FWaaS on L2 ports so

Re: [openstack-dev] [Release-job-failures] Tag of openstack/openstack-ansible-security failed

On Tue, Dec 20, 2016 at 12:29:59AM +, jenk...@openstack.org wrote: > Build failed. > > - openstack-ansible-security-releasenotes > http://logs.openstack.org/6c/6cf9e9174441a071b3071e468235fc18a4c08478/tag/openstack-ansible-security-releasenotes/f814d7f/ > : FAILURE in 51s This should be

[openstack-dev] [tripleo] newton-2 release

I'm proposing a new Newton release for TripleO, as we scheduled it a few weeks ago: https://review.openstack.org/#/c/412643/ Please let me know any blocker or any backport you want to see in this release. Thanks, -- Emilien Macchi

Re: [openstack-dev] [tripleo] [puppet] A week in CI

On Sat, Dec 17, 2016 at 4:30 PM, Emilien Macchi wrote: > This week was outstanding for CI and I found useful to share what > happened in TripleO and Puppet CIs, and where we are now. > TL;DR: > - Puppet OpenStack: full green on ocata/newton/mitaka > - TripleO CI: full green

[openstack-dev] [neutron] [classifier] No Common Classifier / Classification Framework meeting

Hi all, Tomorrow, Tuesday 20th December 2016, there will be no Common Classification Framework meeting, as there are no major topics to discuss. Meanwhile we are working on an initial PoC for the framework. As a reminder, please take a look at the respective spec:

[openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list

Folks, I am in favor of using a new tag called [rdo] such that RDO (or its transitive dependencies) can be discussed and filtered by email clients as it relates to development topics that affect the broader OpenStack ecosystem. As RDO is a community driven project which is very much related