Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi Kaz, These repositories are under horizon project. It looks better to keep the current core team. It potentially brings some confusion if we treat some horizon plugin team specially. Reviewing xstatic repos would be a small burden, wo I think it would work without problem even if only

[openstack-dev] [cinder] Support share backup to different projects?

Now Cinder can transfer volume (with or without snapshots) to different projects, and this make it possbile to transfer data across tenant via volume or image. Recently we had a conversation with our customer from Germany, they mentioned they are more pleased if we can support transfer data

Re: [openstack-dev] [kolla][vote] core nomination for caoyuan

Time is up. Welcome caoyuan join core team :D On Fri, Mar 16, 2018 at 2:57 PM, duon...@vn.fujitsu.com < duon...@vn.fujitsu.com> wrote: > +1 > > > > *From:* Jeffrey Zhang [mailto:zhang.lei@gmail.com] > *Sent:* Monday, March 12, 2018 9:07 AM > *To:* OpenStack Development Mailing List

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

2018-03-19 0:34 GMT+08:00 Nadathur, Sundar : > Sorry for the delayed response. I broadly agree with previous replies. > For the concerns about the impact of Cyborg weigher on scheduling > performance , there are some options (apart from filtering candidates as > much as

[openstack-dev] [openstack-helm] need an ideation on multiline logging support

Docker generate container logs in json format, and Fluent-bit deliver the logs. Fluent-bit provides some mechanism for various logs, but it cannot apply them to the logs, because the logs already converted in json-format. There are some debates on this issue.

[openstack-dev] [ceilometer] [gnocchi] keystone verification failed.

hi?? I have a question about the validation of gnocchi keystone. I run the following command, but it is not successful.(api.auth_mode :basic, basic mode can be # gnocchi status --debug REQ: curl -g -i -X GET http://localhost:8041/v1/status?details=False -H "Authorization:

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi Ivan, Horizon folks, Now totally 8 xstatic-** repos for heat-dashboard have been landed. In project-config for them, I've set same acl-config as the existing xstatic repos. It means only "xstatic-core" can manage the newly created repos on gerrit. Could you kindly add "heat-dashboard-core"

Re: [openstack-dev] Adding "not docs" banner to specs website?

Excerpts from Jeremy Stanley's message of 2018-03-19 20:17:37 +: > On 2018-03-19 16:09:14 -0400 (-0400), Doug Hellmann wrote: > [...] > > We want them all to use the openstackdocstheme so you could look > > into creating a "subclass" of that one with the extra content in > > the header, then

Re: [openstack-dev] [Openstack-sigs] [all][api] POST /api-sig/news

On Fri, Mar 16, 2018 at 4:55 AM, Chris Dent wrote: > > >> So summarize and clarify, we are talking about SDK being able to build >> their interface to Openstack APIs in an automated way but statically from >> API Schema generated by every project. Such API Schema is

[openstack-dev] [ironic] Moving Ironic meeting time

Greetings everyone! In an effort to have our meeting be a little friendlier to contributors in Japan and India, we agreed today [0] to move our meeting time up two hours to 1500 UTC. The appropriate change [1] has been submitted to the irc-meetings repository. Please let me know if you have any

[openstack-dev] [all] Job failures on stable/pike and stable/ocata

I've seen this pop up in various channels now, so I figure I better get more visibility on what is going on to avoid wasted troubleshooting. We have a couple of issues causing failures with stable/pike and stable/ocata. Actually, it also affects stable/queens as well due to grenade jobs needing

Re: [openstack-dev] [nova] New image backend: StorPool

On Fri, 16 Mar 2018 19:24:01 +0200, Peter Penchev wrote: On Fri, Mar 16, 2018 at 09:23:11AM -0700, melanie witt wrote: On Fri, 16 Mar 2018 17:33:30 +0200, Peter Penchev wrote: Would there be any major opposition to adding a StorPool shared storage image backend, so that our customers are not

[openstack-dev] [nova][ironic] Rocky PTG summary - nova/ironic

Hello everyone, Here's the summary etherpad [0] for the nova/ironic session from the PTG in the Croke Park Hotel breakfast area, also included as a plain text export on this email. Please feel freed to edit or reply to this thread to add/correct anything I've missed. Cheers, -melanie [0]

Re: [openstack-dev] Adding "not docs" banner to specs website?

On 2018-03-19 16:09:14 -0400 (-0400), Doug Hellmann wrote: [...] > We want them all to use the openstackdocstheme so you could look > into creating a "subclass" of that one with the extra content in > the header, then ensure all of the specs repos use it. We would > have to land a small patch to

Re: [openstack-dev] Adding "not docs" banner to specs website?

Excerpts from Jim Rollenhagen's message of 2018-03-19 19:06:38 +: > On Mon, Mar 19, 2018 at 3:46 PM, Jeremy Stanley wrote: > > > On 2018-03-19 14:57:58 + (+), Jim Rollenhagen wrote: > > [...] > > > What do folks think about a banner at the top of the specs website

Re: [openstack-dev] Adding "not docs" banner to specs website?

Agree this is a good idea. Let me know what we can do to help. Jay On Mon, Mar 19, 2018, 9:58 AM Jim Rollenhagen wrote: > Ironic (and surely other projects) have had to point out many times that > specs are a point in time design discussion, and not completed >

Re: [openstack-dev] Adding "not docs" banner to specs website?

On 2018-03-19 19:06:38 + (+), Jim Rollenhagen wrote: [...] > Huh, I had totally thought there was a theme for the specs site > that most/all projects use. I may try to accomplish this anyway, > but will likely be more work that I thought. I'll poke around at > options (small sphinx plugin,

Re: [openstack-dev] Adding "not docs" banner to specs website?

On Mon, Mar 19, 2018 at 3:46 PM, Jeremy Stanley wrote: > On 2018-03-19 14:57:58 + (+), Jim Rollenhagen wrote: > [...] > > What do folks think about a banner at the top of the specs website > > (or each individual spec) that points this out? I'm happy to do > > the work

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

Hi, We are glad 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) Weekly priorities

[openstack-dev] [tacker] tacker meeting on Mar. 20th 2018 is cancelled

hi Because I am on a trip, the Tacker project meeting on Mar. 20th is cancelled. If you guys need to talk, please go to #tacker channel or send me an email. please go ahead according to our PTG meeting. Regards, yong sheng gong

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

Hello We are going to have a TripleO CI Community meeting tomorrow 03/20/2018 at 3 pm UTC time. The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo channel. After that, we will hold Office Hours starting at 4PM UTC in case someone from community have any questions

Re: [openstack-dev] Adding "not docs" banner to specs website?

On 2018-03-19 14:57:58 + (+), Jim Rollenhagen wrote: [...] > What do folks think about a banner at the top of the specs website > (or each individual spec) that points this out? I'm happy to do > the work if we agree it's a good thing to do. [...] Sounds good in principle, but the

Re: [openstack-dev] Adding "not docs" banner to specs website?

On Mon, 19 Mar 2018 14:57:58 + Jim Rollenhagen wrote: > Ironic (and surely other projects) have had to point out many times that > specs are a point in time design discussion, and not completed > documentation. It's obviously too much work to go back and update specs

Re: [openstack-dev] Adding "not docs" banner to specs website?

I'm all for the idea, although that may be because I've been been one of the people in the past attempting to assist people who have found specs, and who are are confused or frustrated. I believe it is because some people latch on to the highly technical design documents when they can't find

Re: [openstack-dev] Adding "not docs" banner to specs website?

On Mon, Mar 19, 2018 at 02:57:58PM +, Jim Rollenhagen wrote: > Ironic (and surely other projects) have had to point out many times that > specs are a point in time design discussion, and not completed > documentation. It's obviously too much work to go back and update specs > constantly. > >

Re: [openstack-dev] [Qos]Unable to apply qos policy with dscp marking rule to a port

Please step up to drive https://review.openstack.org/#/c/519513/ At the moment no one is working on the patch. Thanks, On Fri, Mar 16, 2018 at 07:25:58PM +, A Vamsikrishna wrote: > Hi Manjeet / Isaku, > > I am unable to apply qos policy with dscp marking

Re: [openstack-dev] Adding "not docs" banner to specs website?

I think it's a good idea especially as some times a spec is never completed or not in the same release. Thanks, Amy(spotz) On Mon, Mar 19, 2018 at 9:57 AM, Jim Rollenhagen wrote: > Ironic (and surely other projects) have had to point out many times that > specs are a

[openstack-dev] Adding "not docs" banner to specs website?

Ironic (and surely other projects) have had to point out many times that specs are a point in time design discussion, and not completed documentation. It's obviously too much work to go back and update specs constantly. What do folks think about a banner at the top of the specs website (or each

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

> On 3/19/18 7:15 AM, Andreas Jaeger wrote: > > pip install -U breaks it, please double check that this does the right > thing: > > https://review.openstack.org/554222 I'm not yet convinced the pip -U is the only factor here. When I run with 554222 in my local env I still get a back-leveled

[openstack-dev] [kolla] kolla-ansible 6.0.0.0rc2 (queens)

Hello everyone, A new release candidate for kolla-ansible for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kolla-ansible/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

Re: [openstack-dev] [neutron] Prevent ARP spoofing

If I understood correctly, you talk about rules which are generated by security_group extension as default from the fixed_ips + allowed_address_pairs list. In our openstack installation we disabled the security_group and the allowed_address_pairs extensions to simplify the configuration the HA

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

On Sat, Mar 17, 2018 at 9:49 PM, Doug Hellmann wrote: > Both of those are good ideas. > Agree. I like the socket idea a bit more as I can imagine some operators don't want config file changes automatically applied. Do we want to choose one to standardize on or allow each

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

On 2018-03-19 14:24, Gary Kotton wrote: > The change will need to be in all of the decomposed projects - > http://codesearch.openstack.org/?q=install_cmd%20-U=nope== > Good catch! Will you do those, please? (once confirmed that this is the right change), Andreas > > On 3/19/18, 3:18 PM, "Gary

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

The change will need to be in all of the decomposed projects - http://codesearch.openstack.org/?q=install_cmd%20-U=nope== Good catch! On 3/19/18, 3:18 PM, "Gary Kotton" wrote: Thanks!! Will check if it now On 3/19/18, 3:15 PM, "Andreas Jaeger"

Re: [openstack-dev] [neutron] Prevent ARP spoofing

Disabling ARP spoofing protection alone will not let the standby instance source traffic using the active instance's IP. IP filtering rules independent of ARP enforcement rules ensure the source IP is in the fixed_ips or allowed_address_pairs. Are you already using allowed address pairs to add

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

Thanks!! Will check if it now On 3/19/18, 3:15 PM, "Andreas Jaeger" wrote: On 2018-03-19 14:01, Gary Kotton wrote: > The issue is that since the change below - > https://review.openstack.org/553045 - we are not picking up the latest > neutron master code.

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

On 2018-03-19 14:01, Gary Kotton wrote: > The issue is that since the change below - > https://review.openstack.org/553045 - we are not picking up the latest > neutron master code. I see neutron installed:

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

The issue is that since the change below - https://review.openstack.org/553045 - we are not picking up the latest neutron master code. From: Thomas Morin Organization: Orange S.A. Reply-To: OpenStack List Date: Monday, March 19, 2018

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

Hi Sundar, I think the two points you raised is valid and please also reflect that in the spec you are helping drafting :) On Mon, Mar 19, 2018 at 12:34 AM, Nadathur, Sundar < sundar.nadat...@intel.com> wrote: > Sorry for the delayed response. I broadly agree with previous replies. > For the

Re: [openstack-dev] [openstack][charms] Openstack + OVN

Hi James, Thank you for the previous code review. I have pushed another patch. Also, I do not know how to reply to your review comments on gerrit, so I will reply to them here. About the signed-off-message, I did not know that it wasn't a requirement for OpenStack, I assumed it was. I have

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

Hi Gary, Seehttp://lists.openstack.org/pipermail/openstack-dev/2018-March/128311 .html > Note that thanks to the tox-siblings feature, we really continue to> install neutron and horizon from git - and not use the versions in> the global-requirements constraints file, Gary Kotton, 2018-03-19 11:25:

Re: [openstack-dev] [requirements][neutron] Depending on pypi versions

On 2018-03-19 12:25, Gary Kotton wrote: > Hi, > > The change > https://github.com/openstack/requirements/commit/35653e8c5044bff1059f50a82b6065176eea > has created some issues with decomposed neutron plugins. Let me try and > give an example to explain. > > Say for example a patch landed in

[openstack-dev] [requirements][neutron] Depending on pypi versions

Hi, The change https://github.com/openstack/requirements/commit/35653e8c5044bff1059f50a82b6065176eea has created some issues with decomposed neutron plugins. Let me try and give an example to explain. Say for example a patch landed in neutron master that exposed feature X. Now if a

Re: [openstack-dev] [neutron] Prevent ARP spoofing

Yes, there's really a need for mechanisms of high availability like corosync, vrrp etc. Another simple example: we have two servers with the active/standby HA configuration (for example keepalived + haproxy) and we have third-party monitoring system for these servers. The monitoring system gets

Re: [openstack-dev] [neutron] Prevent ARP spoofing

Do you need to spoof arbitrary addresses? If not (i.e. a set you know ahead of time), you can put entries in the allowed_address_pairs field of the port that will allow you to send traffic using other MAC/IPs. On Mar 19, 2018 8:42 PM, "Vadim Ponomarev" wrote: Hi, I

Re: [openstack-dev] [neutron] Prevent ARP spoofing

Hi, I support, that is a problem. It's unclear, how after removing the option prevent_arp_spoofing, I can manage the prevent ARP spoofing mechanism. Example: I use security groups but I don't want to use ARP spoofing protection. How do I can disable the protection? 2018-03-14 10:26 GMT+03:00

[openstack-dev] [neutron] Bug deputy report

Hi all, I'm zhaobo, I was the bug deputy for the last week and I'm afraid that cannot attending the comming upstream meeting so I'm sending out this report: Last week there are some high priority bugs for neutron . Also some bugs need to attention, I list them here: High priority