Re: [openstack-dev] [horizon] how to get horizon related logs to syslog?

Hi, Horizon logging depends on Django configuration which supports full python logging [1]. [1] does not provide enough examples. Perhaps [2] will help you (though I haven't tested it). [1] https://docs.djangoproject.com/en/2.0/topics/logging/ [2]

Re: [openstack-dev] [neutron] heads up to long time ovs users...

ofctl", they will hit some packet losses when upgrading neutron to Stein. We have no actual data on large deployments so far and don't know how this change impacts real deployments. Your feedback would be really appreciated. Best regards, Akihiro Motoki (irc: amotoki) 2018年9月21日(金) 10:37 IWAMOTO

Re: [openstack-dev] [neutron] Core status

Thanks Gary for long years on Neutron. You are the only core before I became quantum-core. I lose you now Anyway good luck for your new role. Thanks, Akihiro 2018年9月20日(木) 3:20 Gary Kotton : > Hi, > > I have recently transitioned to a new role where I will be working on > other parts of

Re: [openstack-dev] [Neutron] Removing external_bridge_name config option

-deprecated-what-is-modern-way Neutron: br-ex is now deprecated! what is modern way? I hope these help you to push away the usage of external_network_bridge. Thanks, Akihiro Motoki (IRC: amotoki) 2018年9月19日(水) 23:02 Slawomir Kaplonski : > > Hi, > > Some time ago I proposed patch [

[openstack-dev] [neutron] bug deputy report week Sep 10 - 12

this Monday. It continues to occur since at least Sep 10. Best Regards, Akihiro Motoki (irc: amotoki) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [release] Release countdown for week R-0, August 27 - 31

ripleo-common-tempest-plugin > trove-tempest-plugin > watcher-tempest-plugin > zaqar-tempest-plugin tempest-horizon is missing from the list. horizon team needs to release tempest-horizon. It does not follow the naming convention so it seems to be missed from the list. Thanks, Aki

Re: [openstack-dev] [requirements][release][osc] FFE osc-lib 1.11.1 release

2018年8月14日(火) 13:38 Matthew Thode : > > On 18-08-14 13:19:27, Akihiro Motoki wrote: > > Hi, > > > > I would like to request FFE for osc-lib 1.11.1 release. > > > > https://review.openstack.org/591556 > > > > osc-iib commit e3d772050f3f4de6

[openstack-dev] [requirements][release][osc] FFE osc-lib 1.11.1 release

plugin gate is now broken. To fix the gate, osc-lib 1.11.1 release would be appreciated. upper-constraints is bumped to osc-lib 1.11.1. It is better to block osc-lib 1.11.0 but I am familiar whether we need to block it or not. Thanks, Akihiro Motoki (amotoki

[openstack-dev] [cinder][api] strict schema validation and microversioning

Hi Cinder and API-SIG folks, During reviewing a horizon bug [0], I noticed the behavior of Cinder API 3.0 was changed. Cinder introduced more strict schema validation for creating/updating volume encryption type during Rocky and a new micro version 3.53 was introduced[1]. Previously, Cinder API

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

Jimmy, Does it mean translation **publishing** is ready now? In the first translation of the edge computing whitepaper, translation publishing was completely a manual process and it takes too long. If translation publishing support is not ready, it is a bit discouraging from translator

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

First of all, thanks for the release team and Radomir. Apart from the fix, is there any good way to detect this kind of errors in individual project reviews? xstatic-cores have new members and all of them are not necessarily super familiar with the xstatic process. In addition, updates in xstatic

Re: [openstack-dev] [stable][horizon] Adding Ivan Kolodyazhny to horizon-stable-maint

+1 to add Ivan to the horizon stable maint team. 2018年6月18日(月) 11:04 Tony Breeds : > Hello folks, > Recently Ivan became the Horizon PTL and as with past PTLs (Hi Rob) > isn't a member of the horizon-stable-maint team. Ivan is a member of > the Cinder stable team and as such has

[openstack-dev] [release] openstack-tox-validate: python setup.py check --restructuredtext --strict

Hi the release team, When I prepared neutron Rocky-2 deliverables, I noticed a new metadata syntax check which checks README.rst was introduced. As of now, README.rst in networking-bagpipe and networking-ovn hit this [1]. Although they can be fixed in individual projects, what is the current

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

rizon/latest/contributor/topics/packaging.html#minified-javascript-policy > > > Ge Xinni > Email: xinni.ge1...@gmail.com > > > On Tue, Jun 5, 2018 at 8:59 PM, Akihiro Motoki wrote: > >> Hi, >> >> Sorry for re-using the

Re: [openstack-dev] [horizon][plugins][heat][searchlight][murano][sahara][watcher] Use default Django test runner instead of nose

This is an important step to drop nose and nosehtmloutput :) We plan to switch the test runner and then re-enable integration tests (with selenium) for cross project testing. In addition, we horizon team are trying to minimize gate breakage in horizon plugins for recent changes (this and django

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

t; >> >> >> 2018-03-21 22:29 GMT+09:00 Kaz Shinohara : >> >> > Hi Ivan, Akihiro, >> >> > >> >> > >> >> > Thanks for your kind arrangement. >> >> > Looking forward to hearing your decision soon. >> >&

Re: [openstack-dev] [neutron][api][graphql] Feature branch creation please (PTL/Core)

Hi Gilles, 2018年6月5日(火) 10:46 Gilles Dubreuil : > > > On 04/06/18 22:20, Doug Hellmann wrote: > >> On Jun 4, 2018, at 7:57 AM, Gilles Dubreuil > wrote: > >> > >> Hi, > >> > >> Can someone from the core team request infra to create a feature branch > for the Proof of Concept we agreed to do

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

2018年6月3日(日) 10:56 Chuck Short : > Hi > > On Sat, Jun 2, 2018 at 9:50 PM, Akihiro Motoki wrote: > >> Updates on Django 2.0 support. >> >> * 18 of 29 affected repositories now support Django 2.0 >> * 4 repositories have pending patches. >> * 3 repositori

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

es at least. I'll > do my best on this effort and will work with plugins teams to do as > much as we can in Rocky timeframe. > > [2] https://www.djangoproject.com/download/ > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Mon, May 14, 2018 at 4

Re: [openstack-dev] Vancouver Forum Etherpad List

I would like to re-post this Sean's post on the YVR forum etherpad list as I believe this is worth shared now again. 2018年5月9日(水) 7:48 Sean McGinnis : > We are now less than two weeks away from the next Summit/Forum in > Vancouver. > Hopefully teams are able to spend some

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

2018年5月14日(月) 21:42 Doug Hellmann : > Excerpts from Akihiro Motoki's message of 2018-05-14 18:52:55 +0900: > > 2018年5月12日(土) 3:04 Doug Hellmann : > > > > > Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900: > > > > Hi zigo and

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

2018年5月12日(土) 3:04 Doug Hellmann : > Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900: > > Hi zigo and horizon plugin maintainers, > > > > Horizon itself already supports Django 2.0 and horizon unit test covers > > Django 2.0 with Python 3.5. > > > > A

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

Hi zigo and horizon plugin maintainers, Horizon itself already supports Django 2.0 and horizon unit test covers Django 2.0 with Python 3.5. A question to all is whether we change the upper bound of Django from <2.0 to <2.1. My proposal is to bump the upper bound of Django to <2.1 in Rocky-2.

Re: [openstack-dev] [neutron][api][grapql] Proof of Concept

Hi, I am happy to see the effort to explore a new API mechanism. I would like to see good progress and help effort as API liaison from the neutron team. > Neutron has been selected for the PoC because of its specific data model On the other hand, I am not sure this is the right reason to choose

Re: [openstack-dev] [horizon][plugins] mox -> mock migration

reak your gate. [1] https://review.openstack.org/558048 Thanks, Akihiro Motoki (amotoki) 2018-03-18 17:54 GMT+09:00 Akihiro Motoki <amot...@gmail.com>: > Hi horizon plugin developers, > > As you know, mox-removal is one of the community goal in Rocky and > horizon team is worki

Re: [openstack-dev] [neutron][dynamic routing] RYU Breaks lower constraints

Gary, I think this is caused by the recent pip change and pip no longer cannot import pip from code. The right solution seems to bump the minimum version of ryu. Thought? http://lists.openstack.org/pipermail/openstack-dev/2018-March/128939.html Akihiro 2018/04/15 午後6:06 "Gary Kotton"

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

Hi Slawek, 2018-04-06 17:38 GMT+09:00 Sławek Kapłoński : > Hi, > > One more question about implementation of this goal. Should we take care > (and add to story board [1]) projects like: > In my understanding, tasks in the storyboard story are prepared per project team

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

-21 22:29 GMT+09:00 Kaz Shinohara <ksnhr.t...@gmail.com>: >> >> > Hi Ivan, Akihiro, >> >> > >> >> > >> >> > Thanks for your kind arrangement. >> >> > Looking forward to hearing your decision soon. >> >> >

Re: [openstack-dev] [sdk] git repo rename and storyboard migration

lso...@gmail.com>: > I can run test migrations today for the rest of the OSC launchpad projects > just to make sure it all goes smoothly and report back. > > -Kendall (diablo_rojo) > > > On Thu, 22 Mar 2018, 5:54 am Dean Troyer, <dtro...@gmail.com> wrote: > >>

Re: [openstack-dev] [sdk] git repo rename and storyboard migration

2018-03-22 21:29 GMT+09:00 Monty Taylor : > On 03/22/2018 02:51 AM, Jens Harbott wrote: > >> 2018-03-21 21:44 GMT+01:00 Monty Taylor : >> >>> Hey everybody! >>> >>> This upcoming Friday we're scheduled to complete the transition from >>>

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

onsistent. > Also having exception might make unexpected confusion in near future. > > Eventually we will follow your opinion, let me hear Horizon team's > conclusion. > > Regards, > Kaz > > > 2018-03-20 12:58 GMT+09:00 Akihiro Motoki <amot...@gmail.com>

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

ge1...@gmail.com> > >>> > wrote: > >>> >> > >>> >> Hi, Akihiro > >>> >> > >>> >> Thanks for the quick reply. > >>> >> > >>> >> I agree with your opinion that BASE_XSTATIC_MOD

[openstack-dev] [horizon][plugins] mox -> mock migration

s stage, your plugin test needs to set up mox explicitly. Thanks, Akihiro Motoki (amotoki) [1] https://blueprints.launchpad.net/horizon/+spec/mock-framework-in-unit-tests [2] https://github.com/openstack/horizon/blob/6e29fdde1edc67a6797eba2c3f9c557f840d4ea7/horizon/test/helpers.py#L138 [3] https://

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

The current version of proposed patches which drops tox_install.sh works in our CI. Even if we have neutron>=12.0.0 (queens) or horizon>=13.0.0 (queens), if we have "required-projects" in zuul v3 config, tox-sibling role ensures to install the latest master of neutron/horizon. It is okay in our

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

The detail of this issue is tracked in https://bugs.launchpad.net/bugs/1755140 and it turned out that it is caused by the older version of the enabled file of the template generator. I strongly recommend to cover this in the release notes. Akihiro 2018/03/13 午前9:45 "Xinni Ge"

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

Hi Xinni, 2018-03-09 12:05 GMT+09:00 Xinni Ge : > Hello Horizon Team, > > I would like to hear about your opinions about how to add new xstatic > modules to horizon settings. > > As for Heat-dashboard project embedded 3rd-party files issue, thanks for > your advices in

Re: [openstack-dev] [heat] heat-dashboard is non-free, with broken unit test env

o hear from your all about the js and static > files issue. > > Best regards, > > Xinni > > On Fri, Mar 2, 2018 at 1:29 PM, Akihiro Motoki <amot...@gmail.com> wrote: >> >> Hi Xinni, >> >> I looked at your patch which drops the vendors stuffs, but I stil

Re: [openstack-dev] [heat] heat-dashboard is non-free, with broken unit test env

Hi Xinni, I looked at your patch which drops the vendors stuffs, but I still have a question. The patch introduces some SCSS like: - bootstrap.scss - angular-notify.scss - angular-material.scss Aren't they another type of "vendors" stuffs? I don't understand why switching to SCSS solves the

Re: [openstack-dev] [neutron][sdk] Proposal to migrate neutronclient python bindings to OpenStack SDK

10:55 AM, Rabi Mishra wrote: > > On Mon, Feb 26, 2018 at 3:44 PM, Monty Taylor <mord...@inaugust.com > > <mailto:mord...@inaugust.com>> wrote: > > > > On 02/26/2018 09:57 AM, Akihiro Motoki wrote: > > > > Hi neutron

[openstack-dev] [neutron][sdk] Proposal to migrate neutronclient python bindings to OpenStack SDK

Hi neutron and openstacksdk team, This mail proposes to change the first priority of neutron-related python binding to OpenStack SDK rather than neutronclient python bindings. I think it is time to start this as OpenStack SDK became a official project in Queens. [Current situations and problems]

Re: [openstack-dev] [heat] heat-dashboard is non-free, with broken unit test env

2018-02-21 23:35 GMT+09:00 Thomas Goirand : > Hi there! > > I'm having big trouble package heat-dashboard for Debian. I hope I can > get help through this list. > > In here: > > heat_dashboard/static/dashboard/project/heat_dashboard/template_generator/js/ > > we have minified

Re: [openstack-dev] [neutron][lbaas][neutron-lbaas][octavia] Announcing the deprecation of neutron-lbaas and neutron-lbaas-dashboard

I don't think we need to drop translation support NOW (at least for neutron-lbaas-dashboard). There might be fixes which affects translation and/or there might be translation improvements. I don't think a deprecation means no translation fix any more. It sounds too aggressive. Is there any problem

Re: [openstack-dev] [neutron][lbaas][neutron-lbaas][octavia] Announcing the deprecation of neutron-lbaas and neutron-lbaas-dashboard

Good to hear that! Thanks for your leadership. Thanks, Akihiro Motoki 2018-02-01 2:50 GMT+09:00 Michael Johnson <johnso...@gmail.com>: > Today we are announcing the start of the deprecation cycle for > neutron-lbaas and neutron-lbaas-dashboard. As part of the neutron > stadi

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

2018-01-31 17:51 GMT+09:00 Saverio Proto : > Hello all, > > I am again proposing a change due to operations experience. I am > proposing a clean and simple cherry-pick to Ocata. > > "it depends" works pretty bad as policy for accepting patches. > > Now I really dont

Re: [openstack-dev] [horizon] FFE Request for Queens

+1 for FFE. I can support it. We need a final ack from our PTL. Akihiro 2018-01-30 5:13 GMT+09:00 Lajos Katona : > Hi, > > I would like to ask for FFE on the neutron-trunk-ui blueprint to let the > admin panel for trunks be accepted for Queens. > > Based on discussion

[openstack-dev] bug deputy report (week of Jan 22)

Hi neutrinos, Sorry for a bit late report of the bug deputy of last week. I think there are several number of interesting bugs reported. [Needs attention] https://bugs.launchpad.net/neutron/+bug/1745642 SG hybrid iptables driver and FWaaS OVS driver create overlapping conntrack zones MTU

[openstack-dev] [release][requirements][horizon] django-openstack-auth retirement

Hi the release team and the requirements team, I would like to have on django-openstack-auth (DOA) retirement. In the thread of the announce of DOA retirement last week, I was advised to release a transition package which provides no python module and make horizon depend on it so that the

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

er horizon dependency is django-openstack-auth>=3.5.0. Luckily enough, the requirement freeze is extended one week. -- Akihiro Motoki __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@li

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

2018-01-22 20:30 GMT+09:00 Jeremy Stanley <fu...@yuggoth.org>: > On 2018-01-22 14:40:49 +0900 (+0900), Akihiro Motoki wrote: > [...] >> If you install horizon and django-openstack-auth by using pip (instead >> of distribution packages), please uninstall django-openstac

[openstack-dev] [horizon][packaging] django-openstack-auth retirement

Hi, packaging teams and operators This mail is the announcement of retirement of django-openstack-auth python package in the Queens release. Horizon team merged the code of django-openstack-auth into the horizon repo mainly from the maintenance reason. For more detail, see the blueprint

Re: [openstack-dev] [Neutron] Bug deputy report

Gary, > I need to drop off bug duty on Thursday night so if someone can please swap > me for Friday. I am a bug deputy of the next week. I can start my coverage from this Friday. Thanks, Akihiro 2018-01-16 21:51 GMT+09:00 Gary Kotton : > Hi, > > Things have been relatively

Re: [openstack-dev] Help with fixing python-pint fixing failed tests with last python-numpy

btw, python-pint is used in horizon.utils.units but the module is actually not used anywhere. It was used in the metering panel (ceilometer support) but the panel was dropped long ago. In addition, there seems no horizon plugins that consume the module [1] (daisycloud-core import the module but it

Re: [openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Welcome Ivan to the team! Akihiro 2017-12-16 1:52 GMT+09:00 Ying Zuo (yinzuo) : > Hi everyone, > > > > After some discussion with the Horizon Core team, I am pleased to announce > that we are adding Ivan Kolodyazhny to the team. Ivan has been actively > contributing to Horizon

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

I have another announcement on heat-dashboard split out. I moved the horizon bugs related to heat to heat-dashboard launchpad project last week. IIRC about 25 bugs were forwarded. I hope heat-dashboard team can investigate them. Akihiro 2017-12-06 15:46 GMT+09:00 Akihiro Motoki <a

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

support from Horizon repo. >> https://review.openstack.org/#/c/523402/ >> >> Also replied for your comment in our etherpad, please kindly check. >> https://etherpad.openstack.org/p/heat-dashboard-review-point >> >> Regards, >> Kaz >> >> 2017-11-

Re: [openstack-dev] [Neutron] Propose Slawek Kaplonski for Neutron core

+1 from me! 2017-11-30 4:21 GMT+09:00 Miguel Lavalle : > Hi Neutron Team, > > I want to nominate Slawek Kaplonski (irc: slaweq) to Neutron core. Slawek > has been an active contributor to the project since the Mitaka cycle. He has > been instrumental in the development of the

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi Kaz, Good hear the good progress of heat-dashboard. Thanks. I created a blueprint in horizon to track the effort (mainly in horizon side) and assign it to you: https://blueprints.launchpad.net/horizon/+spec/heat-dashboard-split-out I also left comments in your etherpad. I think it is time to

Re: [openstack-dev] [Neutron] Debug tool

Forwarding the mail to openstack-operator ML. I believe the operator list is a better to place to discuss this topic. This is about 'neutron-debug' command. https://github.com/openstack/neutron/blob/master/setup.cfg#L48 Thanks, Akihiro 2017-11-19 21:24 GMT+09:00 Gary Kotton

Re: [openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed

2017-11-16 19:33 GMT+09:00 Andreas Jaeger <a...@suse.com>: > On 2017-11-16 11:27, Akihiro Motoki wrote: >> 2017-11-16 18:59 GMT+09:00 Andreas Jaeger <a...@suse.com>: >>> On 2017-11-15 19:07, Doug Hellmann wrote: >>>> [...] >>>> Someone

Re: [openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed

2017-11-16 18:59 GMT+09:00 Andreas Jaeger : > On 2017-11-15 19:07, Doug Hellmann wrote: >> Excerpts from Akihiro Motoki's message of 2017-11-16 01:32:00 +0900: >>> 2017-11-15 1:06 GMT+09:00 Andreas Jaeger : On 2017-11-14 17:03, Doug Hellmann wrote: > Excerpts

Re: [openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed

2017-11-15 1:06 GMT+09:00 Andreas Jaeger : > On 2017-11-14 17:03, Doug Hellmann wrote: >> Excerpts from Andreas Jaeger's message of 2017-11-14 09:31:48 +0100: >>> On 2017-11-13 22:09, Doug Hellmann wrote: Excerpts from zuul's message of 2017-11-13 20:37:18 +: > Unable

Re: [openstack-dev] [heat][horizon] Migration to heat-dashboard: how can we move this forward?

ent > Yes we can take over those bugs, but now we are focusing to stabilize > heat-dashboard-self. > We would like to fix them after we will safely land heat-dashboard in > queens-2. > > Regards, > Kaz Shinohara > > 2017-10-25 11:47 GMT+09:00 Akihiro Motoki <amot...@gmail.

[openstack-dev] [heat][horizon] Migration to heat-dashboard: how can we move this forward?

Hi Heat dashboard team, I noticed heat-dashboard repository was created. I have several questions from horizon side. A big question is "When does the switch happen?" This mainly affects two things: (1) Patch reviews and approvals in horizon Should the horizon team stop to accept

Re: [openstack-dev] Regarding Horizon panel of Gnoochi/Adoh Services

2017-10-12 18:09 GMT+09:00 Sudheer Kalla : > Hello All, > > I have some queries regarding horizon support for gnoochi/adoh services, As > you may all already aware that Resource Usage panel which displays > ceilometer service is no longer available from ocata cycle. So i

Re: [openstack-dev] [Neutron] Denver Team Dinner

+1 thanks for organizing this 2017-09-12 17:23 GMT-06:00 Miguel Lavalle : > Dear Neutrinos, > > Our social event will take place on Thursday September 12th at 7:30pm. The > venue is going to be https://www.famousdaves.com/Denver-Stapleton. It is > located 0.4 miles from the

[openstack-dev] [doc] help for new URL after doc-migration

Hi docs team, I am checking URLs in the horizon documentation after doc-migration and am struggling to find new URLs corresponding to the below. If we fail to find corresponding URLs, it seems to mean we need to drop the URLs. - https://docs.openstack.org/admin-guide/cli-admin-manage-stacks.html

Re: [openstack-dev] [neutron-fwaas]Why fwaas v1 plugin automatically inserts a rule to the head of a policy if people haven't set its position manually?

See the Networking API definition https://developer.openstack.org/api-ref/networking/v2/index.html?expanded=insert-rule-into-a-firewall-policy-detail#insert-rule-into-a-firewall-policy It says "If both insert_before and insert_after are not set, the new firewall_rule_id is inserted at the top of

Re: [openstack-dev] [all] Secrets of edit-constraints

Thanks Tony for the confirmation. We have various variants of tox_install.sh. I just wondered we need to fix it globally or it depends on someone's development environment. Anyway we can improve tox_install.sh for more general way :) Thanks, Akihiro 2017-08-16 18:14 GMT+09:00 Tony Breeds

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron] supporting resource extensions with our CLI

com>: > > On 8/8/17 10:29 AM, Akihiro Motoki wrote: >> My reply applies to 'resource' extension but does not apply to >> 'attribute extension' > > My apologies for using confusing terminology; as you pointed out we > don't currently have a good solution for attribute ext

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

Tony, Thanks for taking care. > The following repos don't seem to use the openstack/releases repo so I > have less information there. Most of them are projects not under the governance (so-called "hosted" or "unofficial" projects), so I am not sure there is a good way to handle them. I can

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron][nova] supporting resource extensions with our CLI

2017-08-08 23:12 GMT+09:00 Akihiro Motoki <amot...@gmail.com>: > 2017-08-08 22:41 GMT+09:00 Boden Russell <boden...@gmail.com>: >> On 8/7/17 10:39 PM, Clint Byrum wrote: >>> If the thing you're doing doesn't fit in the mainline API, then what >>> you're doi

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron][nova] supporting resource extensions with our CLI

2017-08-08 22:41 GMT+09:00 Boden Russell : > On 8/7/17 10:39 PM, Clint Byrum wrote: >> If the thing you're doing doesn't fit in the mainline API, then what >> you're doing is making a new API. Extensions just bypass the important >> part where that API gets designed and thought

Re: [openstack-dev] [neutron][vpnaas] pike rc

I proposed a project-config patch to allow us to release neutron-vpnaas. https://review.openstack.org/#/c/491670/ There is a missing configuration when neutron-vpnaas was pushed out from the neutron stadium. Once the patch is merged and -release group are setup, we can release neutron-vpnaas by

Re: [openstack-dev] [requirements][ptls] HELP! Thawing the requirements repo

2017-08-07 11:59 GMT+09:00 Tony Breeds : > Hi All, > So as you all know we've frozen the requirements repo and it will > stay frozen until after all the cycle-with-milestones projects have > stable/pike branches. That's pretty normal. > > The last couple of cycles

Re: [openstack-dev] [neutron] - FFE for neutron-fwaas v2 requested

2017-08-04 12:05 GMT+09:00 Furukawa, Yushiro : > Hi PTL/all, > > So sorry for late request. As I discussed in driver's meeting, I would like > to > request an exception for 'Firewall as a Service v2' (neutron-fwaas) and > 'FWaaS v2 dashboard'

Re: [openstack-dev] string freeze exception for VMAX driver

I am not sure who is responsible to respond to string freeze exception, but I will comment it as my hat of the i18n team. Looking at "cinder" translation status [1], the best progress is ~73% and 718 of 2932 message are remaining. In other languages the progress is lower. Adding two new messages

Re: [openstack-dev] [nova][docs] Concerns with docs migration

2017-08-03 0:52 GMT+09:00 Doug Hellmann : > Excerpts from Stephen Finucane's message of 2017-08-02 16:35:23 +0100: >> On Wed, 2017-08-02 at 09:28 -0600, Chris Friesen wrote: >> > On 08/02/2017 09:22 AM, Stephen Finucane wrote: >> > > On Wed, 2017-08-02 at 09:55 -0500, Matt

Re: [openstack-dev] [nova][docs] Concerns with docs migration

Thanks for summarizing the concerns. It is really helpful for all projects! 2017-08-02 23:55 GMT+09:00 Matt Riedemann : > Now that Stephen Finucane is back from enjoying his youth and gallivanting > all over Europe, and we talked about a few things in IRC this morning on the

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-24 23:44 GMT+09:00 Doug Hellmann : > Excerpts from Kevin Benton's message of 2017-07-23 14:19:51 -0700: >> Yeah, the networking guide does include configuration for some of the >> sub-projects (e.g. BGP is at [1]). For the remaining ones there is work >> that needs

Re: [openstack-dev] [docs][neutron] doc-migration status

Hi, I have a question on admin/ document related to the networking guide and would like to have advices from the documentation experts. It seems the check site by Doug expect all project have admin/ page. In the case of neutron the situation is a bit special. We have the networking guide as

Re: [openstack-dev] Idea of adding the language index to individual release notes

and then enhance it gradually. 2017-07-11 23:35 GMT+09:00 Doug Hellmann <d...@doughellmann.com>: > > On Jul 11, 2017, at 9:18 AM, Andreas Jaeger <a...@suse.com> wrote: > > On 2017-07-11 14:43, Akihiro Motoki wrote: > > Hi Doug, Ian, Andreas, > > I proposed a patch to a

Re: [openstack-dev] [keystone] office hours report 2017-7-7

2017-07-12 10:35 GMT+09:00 Lance Bragstad : > Hey all, > > This is a summary of what was worked on today during office hours. Full logs > of the meeting can be found below: > > http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-07-11-19.00.log.html It

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

Thanks for update the status! > openstack/networking-midonet The doc-migration work networking-midonet has almost completed. Unfortunately they do not use 'doc-migration' topic as it seems they already started the document overhaul before the doc-migration starts.

Re: [openstack-dev] [OpenStack-Dev][OpenStackClient] - Running functional tests

As Steve mentioned, you need to import OS_* envvars. A user with admin role is required to pass all functional tests. What I usually do is "export OS_CLOUD=devstack-admin" (if you use DevStack). 2017-07-04 22:01 GMT+09:00 Steve Martinelli : > Looks like running tox will

Re: [openstack-dev] [neutron][horizon][fwaas][vpnaas] fwaas/vpnaas dashboard split out

t in the main repo of these projects ? >> >> (networking-bgpvpn has had a dashboard for some time already, it is hosted >> under networking-bgpvpn/bgpvpn_dashboard and we haven't heard about any >> drawback) >> >> Thanks, >> >> -Thomas >> >>

[openstack-dev] [neutron][horizon][fwaas][vpnaas] fwaas/vpnaas dashboard split out

Hi neutron and horizon teams (especially fwaas and vpnaas folks), As we discussed so far, I prepared separate git repositories for FWaaS and VPNaaS dashboards. http://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/ http://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/ All

[openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

disable new rules in pylint 1.7.1 temporarily and clean up your code later as neutron does [3]. As far as I checked, most rules are reasonable and worth enabled. Thanks, Akihiro Motoki [1] https://review.openstack.org/#/c/470800/ [2] https://review.openstack.org/#/c/471756/ [3] https

Re: [openstack-dev] [neutron] pep8 breakage

Six 1.10.0 is not the root cause. The root cause is the version bump of pylint (and astroid). Regarding pylint and astroid, I think the issue will go once https://review.openstack.org/#/c/469491/ is merged. However, even after the global requirement is merged, neutron pylint will fail because

[openstack-dev] [neutron][horizon] FWaaS/VPNaaS dashboard split out from horizon

Hi all, As discussed last month [1], we agree that each neutron-related dashboard has its own repository. I would like to move this forward on FWaaS and VPNaaS as the horizon team plans to split them out as horizon plugins. A couple of questions hit me. (1) launchpad project Do we create a new

Re: [openstack-dev] [Openstack][Neutron]Why we use secuirity group which only support dispatching whiltelist rules?

2017-04-28 7:03 GMT+09:00 Monty Taylor : > On 04/25/2017 10:32 AM, Gary Kotton wrote: >> >> Hi, >> I would like us to think of considering enabling an API that would allow >> ‘deny’, for example an admin could overwrite a tenant’s security groups. For >> example, and admin

Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

Thanks for your feedback, all! It seems we have a consensus and the route is "(a) dashboard repository per project". I would suggest -dashboard as a repository name where is your main repo name. 2017-04-11 0:09 GMT+09:00 Akihiro Motoki <amot...@gmail.com>: > Hi neutri

Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

re > would we like to have horizon dashboard for neutron stadium projects? > > > > I think 'a' is probably the way to go since we can mainly rely on existing > horizon guides for creating new dashboard repos. > > > > On Apr 10, 2017 08:11, "Akihiro Motoki" &

Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-15 12:44 GMT+09:00 Trinath Somanchi : > Hi Jay- > > Thanks for the suggestions, we have improved this to an extent [1]. > > For 'openstack vnf service function chain create' we agreed to go with, > 'openstack nfv chain create' or 'openstack vnf chain create' I

Re: [openstack-dev] [Tacker][OSC] Command naming specs

networking-sfc has many overlapping areas with tacker and the command names can conflict, so I believe it is worth shared in this thread. networking-sfc team is now implementing OSC commands (as neutronclient OSC plugin). Their command name proposal can be found at

Re: [openstack-dev] [horizon][nova][tc] nova-network deprecation in horizon

2017-04-10 23:19 GMT+09:00 Dean Troyer <dtro...@gmail.com>: > On Mon, Apr 10, 2017 at 8:58 AM, Akihiro Motoki <amot...@gmail.com> wrote: >> (question not directly related to this topic) >> I am not sure there is a case where users still use API 2.36 for >> ne

[openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

Hi neutrinos (and horizoners), As the title says, where would we like to have horizon dashboard for neutron stadium projects? There are several projects under neutron stadium and they are trying to add dashboard support. I would like to raise this topic again. No dashboard support lands since

Re: [openstack-dev] [horizon][nova][tc] nova-network deprecation in horizon

h that, from a Horizon point of view. > > Rob > > On 28 March 2017 at 21:06, Matt Riedemann <mriede...@gmail.com> wrote: >> >> On 3/28/2017 9:04 AM, Akihiro Motoki wrote: >> > Hi, >> > >> > I would like to raise a topic when horizon nova-networ

Re: [openstack-dev] [horizon][nova][tc] nova-network deprecation in horizon

2017-03-29 5:06 GMT+09:00 Matt Riedemann <mriede...@gmail.com>: > On 3/28/2017 9:04 AM, Akihiro Motoki wrote: >> >> Hi, >> >> I would like to raise a topic when horizon nova-network support can be >> dropped. >> I added [tc] tag as it is related to

Re: [openstack-dev] How to get all detail RPC message and detail context in neutron docs?

Hi Sam, 'context' is an object of neutron.context.Context which inherits oslo_context.RequestContext. When you see 'context' as a method signature like router_added_to_agent(self, context, payload), 'context' is Context object. oslo_messaging serializes the context object and sends to RPC

Re: [openstack-dev] [all][TripleO][release][deployment] Packaging problems due to branch/release ordering

I see Emilien proposed a number of patches to individual projects with "Sem-Ver: api-break" in the commit message. As far as I understand the pbr documentation [1] correctly (see the forth paragraph in the section) which is pointed by Emilien, the change looks reasonable. Honestly it would be

  1   2   3   4   >