Re: [openstack-dev] [neutron] Rotating the weekly Neutron meeting

Huge +1 On Wed, Aug 13, 2014 at 11:05 PM, Kyle Mestery wrote: > Per this week's Neutron meeting [1], it was decided that offering a > rotating meeting slot for the weekly Neutron meeting would be a good > thing. This will allow for a much easier time for people in > Asia/Pacific timezones, as wel

Re: [openstack-dev] [neutron] [third-party] What tests are required to be run

On 2014/08/18 0:12, Kyle Mestery wrote: > On Fri, Aug 15, 2014 at 5:35 PM, Edgar Magana > wrote: >> Team, >> >> I did a quick audit on the Neutron CI. Very sad results. Only few plugins >> and drivers are running properly and testing all Neutron commits. >> I created a report here: >> https://wi

Re: [openstack-dev] [Ironic] [Horizon] Ironic Horizon API

Hi, Good to know we will have Ironic support. I can help the integration. Let me clarify the situation as Horizon core team. I wonder why it is ASAP. Horizon is released with integrated projects and it is true in Juno release too. Ironic is still incubated even if it is graduated for Kilo release

Re: [openstack-dev] [H][Neutron][IPSecVPN]Cannot tunnel two namespace Routers

It seems -dev list is not an appropriate place to discuss it. please use the general list. I replies to the general list. 2014年9月3日水曜日、Germy Lureさんは書きました: > Hi Stackers, > > Network TOPO like this: VM1(net1)--Router1---IPSec VPN > tunnel---Router2--VM2(net2) > If left and right side deplo

Re: [openstack-dev] [Ironic] [Horizon] Ironic Horizon API

t; > Thanks! > > --- > Josh Gachnang > Tech Blog: ServerCobra.com, @ServerCobra > Github.com/PCsForEducation > > > On Tue, Sep 2, 2014 at 9:37 PM, Jim Rollenhagen > wrote: >> >> >> >> On September 2, 2014 9:28:15 PM PDT, Akihiro Motoki >&

[openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

Hi Neutron team, There are many third party CI in Neutron and we sometimes/usually want to retrigger third party CI to confirm results. A comment syntax varies across third party CI, so I think it is useful to gather "recheck command" in one place. I struggled to know how to rerun a specific CI.

Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

On Tue, Sep 9, 2014 at 10:23 PM, Thierry Carrez wrote: > Mac Innes, Kiall wrote: >> While requesting a openstack/designate-dashboard project from the TC/Infra >> – The topic of why Designate panels, as an incubated project, can’t >> be merged into openstack/horizon was raised. >> >> In the opensta

Re: [openstack-dev] Feature freeze + Juno-3 milestone candidates available

ck.org/__cgi-bin/mailman/listinfo/__openstack-i18n >>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n> >>> >>> -- >>> >>> Thanks, >>> >>> Matt Riedemann >>> >>> >>> _ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.__org >>> <mailto:OpenStack-dev@lists.openstack.org> >>> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev >>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> >>> >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> <mailto:OpenStack-dev@lists.openstack.org> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > -- > Thierry Carrez (ttx) > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro Motoki ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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] https://www.simonkrueger.com/2015/05/27/logging-d

Re: [openstack-dev] [Neutron] Find the compute host on which a VM runs

Hi Stefan, HOST_ID is set by the client. In most usual case nova compute set binding:host_id. On Thu, Nov 21, 2013 at 6:20 PM, Stefan Apostoaie wrote: > Hello again, > > I studied the portbindings extension (the quantum.db.portbindings_db and > quantum.extensions.portbindings modules). However

[openstack-dev] request-id in API response

Hi, I am working on adding request-id to API response in Neutron. After I checked what header is used in other projects header name varies project by project. It seems there is no consensus what header is recommended and it is better to have some consensus. nova: x-compute-request-id cind

[openstack-dev] [oslo] middleware to ensure request-id (Re: request-id in API response)

e, when Swift makes a call to Keystone, Swift could >> log the Keystone transaction id. This wouldn't result in a single >> transaction id across all systems, but it would provide markers so an >> admin could trace the request. > > Sure, this is a perfectly fine optio

Re: [openstack-dev] request-id in API response

(2013/12/06 17:57), Joe Gordon wrote: > > On Dec 6, 2013 9:57 AM, "Maru Newby" > wrote: > > > > > > On Dec 6, 2013, at 1:09 AM, John Dickinson > wrote: > > > > > > > > On Dec 5, 2013, at 1:36 AM, Maru Newby > wrote: >

[openstack-dev] [qa][Neutron] grenade fails due to iso8601 version mismatch

Hi, A patch in neutronclient [1] which updates iso8601 requirement to 0.1.8 fails with grenade due to iso8601 version mismatch [2]. (It blocks the patch for a month.) The error occurs in old devstack (i.e., grizzly devstack). I I see both iso8601 requirements of 0.1.4 and 0.1.8 in devstack log. I

Re: [openstack-dev] [qa][Neutron] grenade fails due to iso8601 version mismatch

Dague wrote: > On 12/09/2013 05:16 AM, Akihiro Motoki wrote: >> Hi, >> >> A patch in neutronclient [1] which updates iso8601 requirement to 0.1.8 >> fails with grenade due to iso8601 version mismatch [2]. >> (It blocks the patch for a month.) >> >> Th

Re: [openstack-dev] Neutron Distributed Virtual Router

Neutron defines "provider" attribute and it is/will be used in advanced services (LB, FW, VPN). Doesn't it fit for a distributed router case? If we can cover all services with one concept, it would be nice. According to this thread, we assumes at least two types "edge" and "distributed". Though

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

Thanks Kyle for coordinating the meeting. The time is midnight to me, but it fits everyone except me. I'll try the time but not sure. Anyway I will follow the log. 2013年12月11日水曜日 Shiv Haris sha...@brocade.com: > +1 > > > > Will join via IRC or voice call > > > > > > > > *From:* Gary Duan [mailto

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

>> about setting the followup meeting up. >> >> Thanks, >> Kyle >> >> On Dec 10, 2013, at 8:14 PM, Yongsheng Gong >> wrote: >> >> > It is 1am beijing time, so I am afraid I will not join. >> > >> > >> > On Wed, Dec 11

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

+1 for both Tatiana and cleaning up the core list. On Wed, Dec 11, 2013 at 5:24 AM, Lyle, David wrote: > I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a > significant code contributor in the last two releases, understands the code > base well and has been doing a si

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

Is the meeting time today 1700UTC? I think this week meeting should be held at the original time to avoid confusion. 2013年12月12日木曜日 Sukhdev Kapur sukhdevka...@gmail.com: > +1 > I'll be there.. > > Sukhdev > On Dec 10, 2013 12:43 PM, "Kyle Mestery" wrote: > > OK, looks like we've reached consensu

Re: [openstack-dev] [Neutron][3rd Party Testing] Jenkins setup

(2014/01/22 2:56), Lucas Eznarriaga wrote: > Hi, > > > For step 3/5, is the right procedure. Or is there a way to use a cmd to > run all the tests and use a different mechanism to specify a filter for the > tests to be run. > > > I don't know if Tempest allows you to filter for the tests to

Re: [openstack-dev] [Neutron][3rd Party Testing] Jenkins setup

tempest defines some sets of tests like "smoke-serial" in tox.ini [1]. We can use "tox -e smoke-serial" or corresponding testr command like testr run '(?!.*\[.*\bslow\b.*\])((smoke)|(^tempest\.scenario))' to run a specific set of tests. The command runs tests with "smoke" tag and all tests fr

Re: [openstack-dev] [Neutron]Contributing code to Neutron (ML2)

Hi Trinath, Jenkins is not directly related to proposing a new code. The process to contribute the code is described in the links Andreas pointed. There is no difference even if you are writing a new ML2 mech driver. In addition to the above, Neutron now requires a third party testing for all new

Re: [openstack-dev] [QA][Neutron][3rd Party Testing] Methodology for 3rd party

Hi, I think it is better to use a fresh VM to run tests. When running tempest scenario tests, there is a case where some resources can not be cleanup properly. It happens when some test fails of course. I think 10 minutes is not too long. It requires more than 30 minutes until gate jobs on openst

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

I think testing with sandbox repo is really useful during setting up third party CI. Not so many people know sandbox repo. When neutron folks were setting up third party CI, we created test reviews in openstack/neutron, but if we knew it it would be great. It is worth documented in "Third Party Te

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

+1 (2014/02/11 8:28), Mark McClain wrote: > All- > > I’d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg > has been valuable contributor to Neutron by actively reviewing, working on > bugs, and contributing code. > > Neutron cores please reply back with +1/0/-1 votes. > >

Re: [openstack-dev] [OpenStack-Infra] [cinder][neutron][nova][3rd party testing] Gerrit Jenkins plugin will not fulfill requirements of 3rd party testing

Hi, I wrote a blog post about how to setup Zuul manually. http://ritchey98.blogspot.jp/2014/02/openstack-third-party-testing-how-to.html It covers how to migrate from Gerrit Trigger plugin to Zuul and some tips including a way to define vendor-specific recheck trigger in addition to the setup pro

Re: [openstack-dev] [infra] reverify/recheck

Hi Gary, According to zuul layout.yaml [1], "reverify bug #" should still work but it seems to work only when verified score from jenkins is -2. https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/zuul/layout.yaml#L25 Note that core team can trigger gate jobs by

Re: [openstack-dev] [Openstack-dev] [neutron] [ml2] Neutron and ML2 - adding new network type

Hi, I think you are trying to use different IP allocation algorithm for a network based on some attribute of the network. network_type of the provider network specifies how layer2 network is segmented and ML2 type drivers are defined per network_type. I think it is different from your need. IMO i

Re: [openstack-dev] False Positive testing for 3rd party CI

Thanks Aaron, it is really interesting. > The Hyper-V CI is non-voting (as required for new third-party CIs) and this > is the reason why any post from it will show “build succeeded”. As published > in other threads, AFAIK the only way to get rid > of this issue is to have the CI as voting.

Re: [openstack-dev] [neutron] Changes to the core team

of Henry > and Kevin to the core team. > > Thanks! > Kyle > > [1] http://stackalytics.com/report/contribution/neutron-group/180 > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstac

Re: [openstack-dev] [neutron] Changes to the core team

>> > OpenStack Development Mailing List (not for usage questions) >> > Unsubscribe: >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>

Re: [openstack-dev] [neutron] status of VPNaaS and FWaaS APIs in Icehouse

we need to correct the previous reply. Both should still be considered experimental because of the multivendor work was NOT completed in Icehouse. We can use only one service backend for each service and there are no way to choose a backend when creating a service instance. In addition,

Re: [openstack-dev] [Neutron] Flavor(?) Framework

Hi, I have a same question from Mark. Why is "flavor" not desired? My first vote is "flavor" first, and then "type". There is similar cases in other OpenStack projects. Nova uses "flavor" and Cinder uses "(volume) type" for similar cases. Both cases are similar to our use cases and I think it is

Re: [openstack-dev] [DriverLog][nova][neutron][cinder] Call for vendor participation please

Hi, Thanks for the effort. While I am looking the website and the driver database, I have a couple of questions and suggestions. - Is it better to include "trunk" (= Juno) in "releases" in each driver if it is a part of the trunk or to wait it until Juno is released? We need some guidelines

Re: [openstack-dev] [Ironic][Neutron] - Integration with neutron using external attachment point

# Added [Neutron] tag as well. Hi Igor, Thanks for the comment. We already know them as I commented in the Summit session and ML2 weekly meeting. Kevin's blueprint now covers Ironic integration and layer2 network gateway and I believe "campus-network" blueprint will be covered. We think the work

Re: [openstack-dev] [neutron] Proposed changes to core team

+1 from me too. Akihiro On Thu, May 22, 2014 at 5:59 AM, Kyle Mestery wrote: > I would like to propose a few changes to the Neutron core team. > Looking at how current cores are contributing, both in terms of review > [1] as well as project participation and attendance at the summit > sessions

Re: [openstack-dev] [devstack] [neutron] How to tell a compute host the control host is running Neutron

Hi Kyle, I am happy to hear OpenDaylight installation and startup are restored to devstack. It really helps openstack integration with other open source based software. I have a question on a file location for non-OpenStack open source software. when I refactored neutron related devstack code, we

Re: [openstack-dev] [Neutron][IPv6][Security Group] BP: Support ICMP type filter by security group

I wonder why RA needs to be exposed by security group API. Does a user need to configure security group to allow IPv6 RA? or should it be allowed in infra side? In the current implementation DHCP packets are allowed by provider rule (which is hardcoded in neutron code now). I think the role of IPv

Re: [openstack-dev] [Neutron][ML2]

Hi, I think it is better to continue the discussion here. It is a good log :-) Eugine and I talked the related topic to allow drivers to load extensions) in Icehouse Summit but I could not have enough time to work on it during Icehouse. I am still interested in implementing it and will register

Re: [openstack-dev] [Horizon] Nominating Radomir Dopieralski to Horizon Core

+1 from me too. Having a core member who is familiar with horizon and tuskar-ui code base encourages the integration more! Akihiro On Fri, Mar 7, 2014 at 4:56 PM, Matthias Runge wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, Mar 05, 2014 at 10:36:22PM +, Lyle, David wro

Re: [openstack-dev] [Neutron] Developer documentation

Hi Carl, I really appreciate you for writing this up! I have no hurdle to remove my -1 for the review. I just thought it is an item easy to fix. It is a great start line towards useufl developer documentation. Thanks, Akihiro On Sat, Mar 8, 2014 at 3:12 AM, Collins, Sean wrote: > Hi, > > I kn

Re: [openstack-dev] [Neutron][IPv6][Security Group] BP: Support ICMP type filter by security group

server, how is it done now? > > thanks, > Robert > > On 3/7/14 12:00 AM, "Akihiro Motoki" wrote: > >>I wonder why RA needs to be exposed by security group API. >>Does a user need to configure security group to allow IPv6 RA? or >>should it be allow

Re: [openstack-dev] [I18n][Horizon] I18n compliance test & string freeze exception

+1 In my understanding "String Freeze" is a SOFT freeze as Daisy describes. Applying string freeze to incorrect or incomprehensible messages is not good from UX point of view and shipping the release with such strings will make the situation worse and people feel OpenStack is not mature and can mi

Re: [openstack-dev] [I18n][Horizon] I18n compliance test & string freeze exception

WORDS can be accepted. My proposal is that we have a deadline for merges of mini features with string updates. The deadline in my mind is the first two weeks after feature freeze Tuesday. Thought? Akihiro On Thu, Mar 13, 2014 at 9:05 PM, Julie Pichon wrote: > On 13/03/14 09:28, Akihiro Motoki wr

Re: [openstack-dev] [horizon] horizon PyPi distribution missing

Does muranodashboard depend on only horizon or require openstack_dashboard too? I think we can publish openstack_dashboard (including horizon) even if horizon and openstack_dashboard are not separeted. Once we separate them successfully, we can publish horizon module and add dependency on horizon

Re: [openstack-dev] [Horizon] Edit subnet in workflows - ip_version hidden?

ian (absubram) wrote: > >> Althouh - how up to date is this code? > > This should be easy to check with the "git blame" command: > > $ git blame > openstack_dashboard/dashboards/project/networks/subnets/workflows.py > > [...] > 31d55e50 (Akihiro MOTOKI

Re: [openstack-dev] [horizon] horizon PyPi distribution missing

As a workaround you can use tarball in requirements.txt (or test-requirements.txt). Each versions of Horizon/openstack_dashboard is available at http://tarballs.openstack.org/horizon/. Each tarball is generated every time corresponding branch or tag is updated. If you would like to use horizon I-3

Re: [openstack-dev] [Nova][Neutron] Neutron + Nova + OVS security group fix

Hi Nachi and the teams, (2014/03/26 9:57), Salvatore Orlando wrote: > I hope we can sort this out on the mailing list IRC, without having to > schedule emergency meetings. > > Salvatore > > On 25 March 2014 22:58, Nachi Ueno mailto:na...@ntti3.com>> > wrote: > > Hi Nova, Neturon Team > >

Re: [openstack-dev] [horizon] horizon PyPi distribution missing

t; [1] > http://logs.openstack.org/25/68125/16/check/gate-murano-dashboard-python26/8ebc940/console.html.gz#_2014-03-24_11_08_50_923 > [2] https://review.openstack.org/#/c/68125/ > > On Thu, Mar 20, 2014 at 9:50 PM, Akihiro Motoki wrote: >> As a workaround you can use tarball in

Re: [openstack-dev] [horizon] horizon PyPi distribution missing

; [1] > http://logs.openstack.org/25/68125/16/check/gate-murano-dashboard-python26/8ebc940/console.html.gz#_2014-03-24_11_08_50_923 > [2] https://review.openstack.org/#/c/68125/ > > On Thu, Mar 20, 2014 at 9:50 PM, Akihiro Motoki wrote: >> As a workaround you can use tarball in

Re: [openstack-dev] [neutron] Location of 'enable_security_group' key in ml2_conf.ini

Hi Matt, Thanks for raising this. Both should be the same section. [securitygroup] section exists in Havana and previous releases and it is the right section name. When we introduced enable_security_group option, we seem to have added a new section accidentally. We don't intended to introduce a n

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

I'd like to see your use case too. I heard a similar demand recently. It is a case of migration of legacy applicaitons to virtual platform and the applications which manages redandunt NICs directly and they just want not to change the applcations itself. It is just server consolidation and not a

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

To cope with such cases, allowed-address-pairs extension was implemented. http://docs.openstack.org/api/openstack-network/2.0/content/allowed_address_pair_ext_ops.html (2014/04/17 13:39), Kevin Benton wrote: > I was under the impression that the security group rules blocked > addresses not assigne

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

Hi, (2014/04/17 21:29), CARVER, PAUL wrote: > Akihiro Motoki wrote: > >> To cope with such cases, allowed-address-pairs extension was implemented. >> http://docs.openstack.org/api/openstack-network/2.0/content/allowed_address_pair_ext_ops.html > > Question on this in

Re: [openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

(2014/04/21 18:10), Oleg Bondarev wrote: On Fri, Apr 18, 2014 at 9:10 PM, Kyle Mestery mailto:mest...@noironetworks.com>> wrote: On Fri, Apr 18, 2014 at 8:52 AM, Oleg Bondarev mailto:obonda...@mirantis.com>> wrote: > Hi all, > > While investigating possible options for Nova-network to Neutron m

Re: [openstack-dev] [Neutron] review hour?

Hi, Previously Neutron team had ReviewDays [1] and core members made themselves focus on reviews and be available on IRC channel one or more day(s) of each week (as possible as they can). The number of neutron reviews has increased compared to that time and I am afraid one or two days reviews can

Re: [openstack-dev] [Neutron][db] End of meetings for neutron-db

sts.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro Motoki ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Deprecating exceptions

deprecation > time before the remove, it's an issue about why horizon didn't respond > to the deprecation sooner. > > -Sean > > -- > Sean Dague > http://dague.net > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Akihiro Motoki ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] - what integration with Keystone is allowed?

___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro Motoki ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [requirements][horizon] Dependency freeze exceptions: django-openstack-auth

Hi, I would like to request dependency freeze exceptions for django-openstack-auth. https://review.openstack.org/#/c/123101/ django-openstack-auth is developped along with Horizon and the recent release 1.1.7 of django-openstack-auth has good fixes which affect Juno Horizon, especially from the f

Re: [openstack-dev] [requirements][horizon] Dependency freeze exceptions: django-openstack-auth

release in general. Another way is to copy the logic from a library a workaround but it is a bit ugly. Of course we need to keep compatibility for the declared version in requirement.txt. Thanks, Akihiro On Tue, Sep 23, 2014 at 6:47 PM, Thierry Carrez wrote: > Akihiro Motoki wrote: >> I wo

Re: [openstack-dev] [Nova] [All] API standards working group

ionalization working group./* >> > >> > Yes, I'd be willing to head up the working group... or at least >> > participate in it. >> >> I also would like to join the group. >> >> >> Thanks >> Ken'ichi Ohmichi >> >> >&g

[openstack-dev] [Horizon] [All?] "Status" vs "State"

Hi, # The first half is related to Horizon and the latter half is about the wording in Nova and Neutron API. During Horizon translation for Juno, I noticed the words "State" and "Status" in multiple contexts. Sometimes they are in very similar contexts and sometimes they have different contexts.

[openstack-dev] [All] [I18N] compiling translation message catalogs

Hi, To display localized strings, we need to compile translated message catalogs (PO files) into compiled one (MO files). I would like to discuss and get a consensus who and when generate compiled message catalogs. Inputs from packagers are really appreciated. [The current status] * Horizon conta

Re: [openstack-dev] [All] [I18N] compiling translation message catalogs

to change now? I would like to know opinions from distributors like RDO, Debian, Ubuntu and so on. Thanks, Akihiro On Thu, Oct 2, 2014 at 9:00 PM, Tom Fifield wrote: > On 02/10/14 14:32, Łukasz Jernaś wrote: >> On Wed, Oct 1, 2014 at 6:04 PM, Akihiro Motoki wrote: >>> Hi

Re: [openstack-dev] [All] [I18N] compiling translation message catalogs

04/10/14 18:12, Akihiro Motoki wrote: >> Thanks all for your input. This topic was also discussed in the >> I18N team meeting this week. >> >> All opinions I got so far are same and we seem to have a >> consensus. - not to have mo files (compile message catalogs) in ou

Re: [openstack-dev] [Neutron] Proposing to disallow updates of IPv6 attributes on subnets

4] https://review.openstack.org/125328 > [5] https://review.openstack.org/117799 > [6] > http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-10-07-15.01.log.html > > ___ > OpenStack-dev mailing list > OpenStack

Re: [openstack-dev] [All] [I18N] compiling translation message catalogs

x27;t need to care Build-Depends, but run_tests.sh script prompts before creating the virtualenv :-( ./run_tests.sh --compilemessages [1] https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1377923 Thanks, Akihiro > >> >> Thank you, >> >> Julie >> >&

Re: [openstack-dev] Neutron documentation to update about new vendor plugin, but without code in repository?

enstack.org. Drivers change enough >>>>>>> release-to-release >>>>>>> that it's difficult to keep up maintenance. >>>>>>> >>>>>>> Lately I've been talking to driver contributor

Re: [openstack-dev] [neutron][stable] metadata agent performance

A7Lpa3S79Rv4cT5 > CC82FlU32fbOkCVFiXqgQvadNc3wrqHMag9FD6fpbg/MZlvV/VWHMl/z55rwhNh/ > yL+CzXd9uNgZy+ng0LI1EY+u9UcLtVwF8xhLhRIu5NMRim3HeRFlFUSN41ccemRJ > TdJUxMdtlYls/nCuIUk2QpSOZt1Hk2bysrBPh0etV501vsSHCq3cYZ3vjmt+jNX9 > thTKlsOaFpSLWnTn5+ERXk3y7pvJxo1AGOli3sLXIDYYNYPK4Y8PRYPLm43U45o= >

Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard

ents.txt" would not brake > because they would pull horizon_lib with horizon. and they would still > import the proper module. Every backwards compatibility (requirements > and module) is therefore preserved. > > > -- > Yves-Gwenaël Bourhis > > ___

Re: [openstack-dev] [Neutron] "Neutron Ryu" status

Third party CI maintainers can avoid problems related to version conflicts (which do not happen in the upstream CI) by doing fresh installation of python modules. OpenStack upstream CI installs dependent python modules every time a test is run. I also suggest to use fresh installation of python mod

Re: [openstack-dev] [Neutron] Bug squashing day

Thanks Eugene for initiating Neutron bug squashing day! I would like to focus on bug triaging and checking bug status rather than fixing bugs. There seem be many bugs which are not valid anymore. Thanks, Akihiro On Thu, Aug 7, 2014 at 11:31 PM, Eugene Nikanorov wrote: > Hi neutron folks, > > Tod

Re: [openstack-dev] [Neutron] Need some clarity on security group protocol numbers vs names

he patch > is accepted upstream. I hope this e-mail gets the ball rolling on that. I > would like to hear the community's opinion on this issue and any > pros/cons/pitfalls of either approach. > > Thanks > Arvind > > ____

Re: [openstack-dev] [Neutron] Need some clarity on security group protocol numbers vs names

o me too. > tl;dr: magic constants are no good, but values should be validated in a > pluggable and explicit manner. As I said above, I agree it is important to validate values properly in general. Thanks, Akihiro > > > > On 9/11/13 10:40 AM, "Akihiro Motoki" wrote: &

Re: [openstack-dev] Gate issues - what you can do to help

he case in gate, is it? > > Cheers, > Alan > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro MOTOKI ___ OpenStack-dev mailing lis

Re: [openstack-dev] Gate issues - what you can do to help

. > Thanks > Gary > >>On Fri, Oct 4, 2013 at 2:06 AM, Akihiro Motoki wrote: >>> Hi, >>> >>> I would like to share what Gary and I investigated, while it is not >>> addressed yet. >>> >>> The cause is the failure of quantum-debug comman

Re: [openstack-dev] Gate issues - what you can do to help

branch. Gary's patch https://review.openstack.org/#/c/49943/ looks a short way to fix the gate issue since once the fix is merged the gate issue will be fixed. I am fine with the patch as a temporary solution. Thanks, Akihiro On Sun, Oct 6, 2013 at 5:51 PM, Akihiro Motoki wrote: >

Re: [openstack-dev] Gate issues - what you can do to help

, 2013 at 6:18 PM, Akihiro Motoki wrote: > Regarding https://review.openstack.org/#/c/49942/ (against > quantumclient branch), > the gate for quantumclient branch of python-neutronclient seems broken. > It seems the script expects master branch of python-neutronclient. > I am not s

[openstack-dev] [Swift] Havana Release Notes Known Issues is talking about Nova (Re: [Openstack] OpenStack 2013.2 ("Havana") is released !)

Hi Thierry, John, In Havana release notes, Swift known issues section is talking about Nova Cells issue. Could you confirm? https://wiki.openstack.org/wiki/ReleaseNotes/Havana#Known_Issues Thanks, Akihiro On Thu, Oct 17, 2013 at 11:23 PM, Thierry Carrez wrote: > Hello everyone, > > It is my gre

Re: [openstack-dev] [Swift] Havana Release Notes Known Issues is talking about Nova (Re: [Openstack] OpenStack 2013.2 ("Havana") is released !)

t that in the wrong spot. Oops. >> >>> On Oct 18, 2013, at 11:11 PM, Akihiro Motoki wrote: >>> >>> Hi Thierry, John, >>> >>> In Havana release notes, Swift known issues section is talking about >>> Nova Cells issue. Could you confirm?

[openstack-dev] Neutron - an issue regarding what API to follow

Hi, The API document is the official one, and Wiki is used during the development. We may be better to add a note to the wiki page to avoid such confusion. I am not sure what confused you. Could you give me an example? Thanks, Akihiro 2013年10月21日月曜日 GROSZ, Maty (Maty) maty.gr...@alcatel-lucent.

Re: [openstack-dev] openstack-dev][nova][neturon] NoopFirewallDriver lead nova boot/show/list failure.

Hi, Thank you for moving it to the mailing list. >> Nova operations (list/show/boot) will fail. due to Nuetron client raises >> NotFound security_group exception. I submit a patch for Nova to fix nova >> show/list failure. See https://review.openstack.org/#/c/52597/ Regarding on this point, secu

Re: [openstack-dev] extend Network topology view in horizon

Hi, In Havana release, FWaaS and VPNaaS are inserted onto routers. We don't need new blocks but it is better we have some information on firewall or vpnservice on routers. In the reference implementation LBaaS is implemented as one-arm load balancer, so we need a new block in network topology view

Re: [openstack-dev] VPNaaS questions...

Hi Paul, On Wed, Oct 23, 2013 at 9:56 PM, Paul Michali wrote: > > Hi guys, > > Some questions on VPNaaS… > > Can we get the review reopened of the service type framework changes for VPN > on the server side? > I was thinking of trying to rebase that patch, based on the latest from > master, bu

[openstack-dev] [Neutron] tempest failure: No more IP addresses available on network

Hi, I just noticed several number of neutron check (tempest-devstack-vm-neutron-isolated) fails with the same error: "No more IP addresses available on network". This errors suddenly starts to occur from yesterday. I checked there is any commit merge around the time when this failure started, but

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

Hi Eugene, In my opinion, it is better the LBaaS meeting is held on #openstack-meeting or #openstack-meeting-alt as most OpenStack projects do. In addition, information on https://wiki.openstack.org/wiki/Meetings#LBaaS_meeting is not up-to-date. The time is 1400UTC and the channel is #openstack-m

Re: [openstack-dev] [Openstack] CLI command to figure out security-group's association to particular tenant/user

quantum security-group-rule-create --protocol tcp --ethertype IPv4 > --port-range-min 1 --port-range-max 65535 --remote-ip-prefix 0.0.0.0/0 > default > > or > > nova secgroup-add-rule default tcp 1 65355 0.0.0.0/0 > > > Thanks and Regards > > -- Akihiro MOTOKI ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Service Type Framework implementation

min rest api for enable/disable service types >> Allow to create new relation if it is enabled by API >> Remove the relation if it disabled by API >> >> This is my preference. And IMO, this is same as option4. >> >> Best >> Nachi

Re: [openstack-dev] Problem with how python-neutronclient deals with Neutron exceptions

roperties. This way, when a NeutronServer exception is serialized and sent > to python-neutronclient, the specific NeutronClient exception can be raised > (and then sent to nova-api). > 3) You tell me :) ! > > Thanks a lot > Jordan > > > > > ___

Re: [openstack-dev] [Neutron] Service Type Framework implementation

xed in the patch which introduces the code >> which uses it (like the one published by Salvatore) >> >> Thanks, >> Eugene. >> >> >> >> On Wed, Jul 10, 2013 at 2:33 PM, Akihiro MOTOKI wrote: >> >>> Hi, >>> >>> Sorry f

Re: [openstack-dev] [Neutron] Proposal to add new neutron-core members

> > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ > OpenStack-dev mailing list > OpenStack-dev@list

Re: [openstack-dev] [Horizon][Neutron] Security groups call to Neutron instead of Nova

_ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Akihiro MOTOKI ___ OpenStack-dev mailing list OpenStack-dev@l

Re: [openstack-dev] [Horizon][Neutron] Security groups call to Neutron instead of Nova

med what I found! > I was wondering if I could add update that variable in devstack, I was > planning to add into lib/neutron: > > _horizon_config_set $local_settings OPENSTACK_NEUTRON_NETWORK > enable_security_group False > > What do you think? > > Edgar > > On 7/29

Re: [openstack-dev] [Nova] nova-api won't start in devstack

28:28.938 TRACE nova File >>>> "/opt/stack/nova/nova/api/openstack/__init__.py", line 251, in factory >>>> 2013-08-06 11:28:28.938 TRACE nova return cls() >>>> 2013-08-06 11:28:28.938 TRACE nova File >>>> "/opt/stack/nova/nova/api/openstack/compu

Re: [openstack-dev] [Neutron] Running unit tests (was: REST-based ML2 MechanismDriver)

_ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Akihiro MOTOKI ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Need some clarity on security group protocol numbers vs names

stants are no good, but values should be validated in a > pluggable and explicit manner. > > > > On 9/11/13 10:40 AM, "Akihiro Motoki" wrote: > >>Hi all, >> >>Arvind, thank you for initiate the discussion about the ip protocol in >>security group rule

[openstack-dev] Horizon social meetup in Tokyo

Hi Horizon team, Doug and I are planning a horizon social meetup in Tokyo. As you may know, it is planned on Monday Oct 26. 10/26 20:00 - Torikaku at Shinagawa Intercity (とりかく 品川インターシティ店) The location is: https://www.google.com/maps/place/Kineya+Shinagawa+Inter+City/@35.6269353,139.742403,15z/da

[openstack-dev] [Horizon] Horizon social meetup in Tokyo

I resent my mail as I forgot to add [Horizon] tag. 2015-10-22 23:50 GMT+09:00 Akihiro Motoki : > Hi Horizon team, > > Doug and I are planning a horizon social meetup in Tokyo. > As you may know, it is planned on Monday Oct 26. > > 10/26 20:00 - > Torikaku at Shinagawa Inter

  1   2   3   4   >