Hi all,
I’m stepping down from the core team because my role changed and I cannot
have responsibilities of neutron core.
My start of neutron was 5 years ago. I had many good experiences from
neutron team.
Today neutron is great project. Neutron gets new reviewers, contributors
and, users.
Hi,
I was the bug deputy for the week of August 27 - September 2.
There is no Ctirical bug.
High:
https://bugs.launchpad.net/neutron/+bug/1789878
https://bugs.launchpad.net/neutron/+bug/1789846
https://bugs.launchpad.net/neutron/+bug/1789579
https://bugs.launchpad.net/neutron/+bug/1789434
Hi all,
There is no critical bug but I'd like to report some bugs last week.
Three high priority bugs.
- https://bugs.launchpad.net/neutron/+bug/1741954 :
create_and_list_trunk_subports rally scenario failed with timeouts
- https://bugs.launchpad.net/neutron/+bug/1742401 : Fullstack tests
Hi Armando,
It's been a great pleasure working with you. We appreciate your hard work
and dedication.
Best wishes and good luck at your new commitments.
Thanks,
Hirofumi
2017-12-16 4:01 GMT+09:00 Armando M. :
> Hi neutrinos,
>
> To some of you this email may not come as a
+1
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 QoS
2017-08-30 16:37 GMT+09:00 Jens Harbott <j.harb...@x-ion.de>:
> 2017-08-30 9:04 GMT+02:00 Hirofumi Ichihara <ichihara.hirof...@gmail.com>:
> > Hi team,
> >
> > Currently neutron-dynamic-routing supports 2 byte AS numbers only[1].
> > Does team have a plan s
Hi team,
Currently neutron-dynamic-routing supports 2 byte AS numbers only[1].
Does team have a plan supporting 4 byte AS numbers?
[1]:
https://github.com/openstack/neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/common/constants.py#L27
Thanks,
Hirofumi
Hi Miguel,
Unfortunately I already have a plan to attend another party. Please give
another attendee my seat.
Thanks,
Hirofumi
2017-05-08 18:18 GMT-04:00 Miguel Lavalle :
> Dear Neutrinos,
>
> I am working with Legal Sea Foods on a reservation for 30 people,
> Wednesday at
On 2017/03/09 2:33, Armando M. wrote:
On 8 March 2017 at 07:39, Hirofumi Ichihara
<ichihara.hirof...@lab.ntt.co.jp
<mailto:ichihara.hirof...@lab.ntt.co.jp>> wrote:
On 2017/03/08 23:59, Andreas Jaeger wrote:
On 2017-03-08 15:40, ZZelle wrote:
from source,
Andreas
On Wed, Mar 8, 2017 at 3:16 PM, Hirofumi Ichihara
<ichihara.hirof...@lab.ntt.co.jp
<mailto:ichihara.hirof...@lab.ntt.co.jp>> wrote:
Hi,
I thought that we can post neutron patch depending on neutron-lib
patch under review.
However, I saw it do
Hi,
I thought that we can post neutron patch depending on neutron-lib patch
under review.
However, I saw it doesn't work[1, 2]. In the patches, neutron patch[1]
has Depends-on tag with neutron-lib patch[2] but the pep8 and unit test
fails because the test doesn't use the neutron-lib patch.
+1
On 2016/12/16 8:58, Armando M. wrote:
Hi neutrinos,
I would like to propose Ryan and Nate as the go-to fellows for
service-related patches.
Both are core in their repos of focus, namely neutron-dynamic-routing
and neutron-fwaas, and have a good understanding of the service
framework,
+1
On 2016/12/16 8:14, Armando M. wrote:
Hi neutrinos,
Miguel Lavalle has been driving the project forward consistently and
reliably. I would like to propose him to be entrusted with +2/+A
rights in the areas he's been most prolific, which are L3 and DHCP.
At the same time, I'd like to
+1
On 2016/12/14 11:56, Kevin Benton wrote:
+1
On Dec 13, 2016 17:27, "Armando M." > wrote:
Hi folks,
Abhishek Raut's recent involvement in OSC and python-neutronclient
has helped moving a few efforts along in the right direction. I
Hi Carl,
Your great work always helped Neutron community.
Thank you so much for all your help.
Hirofumi
On 2016/11/18 3:42, Carl Baldwin wrote:
Neutron (and Openstack),
It is with regret that I report that my work situation has changed
such that I'm not able to keep up with my duties as a
On 2016/09/28 10:18, Armando M. wrote:
Hi Neutrinos,
I wanted to double check with you the state of these following projects:
- networking-ofagent
I think that ofagent is ready for retirement. I have seen the
declaration as "OFAgent is decomposed and deprecated in the Mitaka
cycle." in
The use-case is similar to the spec[1].
[1]: https://review.openstack.org/#/c/351675/
On 2016/08/22 15:48, Edan David wrote:
Hi all,
It seems today that the ml2 rpc API only supports reporting that a
port is up\down,
There may be situations when the l2 agent can fail,
For example SR-IOV
(timestamp). I think that it's next step after implementing tag
notification.
Thanks,
Hirofumi
Thanks,
Steve
On 8/1/16, 3:33 AM, "Hirofumi Ichihara" <ichihara.hirof...@lab.ntt.co.jp>
wrote:
Hi,
I'm trying to solve a issue[1, 2] which doesn't send a notification when
Tag is upda
Hi,
I'm trying to solve a issue[1, 2] which doesn't send a notification when
Tag is updated. I'm worried about the payload. My solution just outputs
added tag, resource type, and resource id as payload. However, there was
a comment which mentioned the payload should have more information.
port (physical bridge, tunnel) will be shaped. Of course,
this implementation is a bit tangled, so please be gentle in the
code-review.
Regards.
*From:*Hirofumi Ichihara [mailto:ichihara.hirof...@lab.ntt.co.jp]
*Sent:* Tuesday, June 21, 2016 10:27 AM
*To:* OpenStack Development Mailing List
On 2016/06/15 18:54, Alonso Hernandez, Rodolfo wrote:
Hello:
Context: try to develop a driver for this feature in OVS.
During the last week I’ve been testing several scenarios to make a POC
of this feature.
Scenario 1:
3 VM connected to br-int, sending traffic through br-physical to
Motoki <amot...@gmail.com>:
Hi Neutrinos,
As the API Lieutenant of Neutron team,
I would like to propose Hirofumi Ichihara (irc: hichihara) as a member of
Neutron core reviewer team mainly focuing on the API/DB area.
Hirofumi has been contributing neutron actively in the recent two
re
t change the option in the
neutron.conf and restart.
>
> On Mon, Apr 11, 2016 at 12:42 PM, Hirofumi Ichihara
> <ichihara.hirof...@lab.ntt.co.jp
<mailto:ichihara.hirof...@lab.ntt.co.jp>> wrote:
> I agree. Throughout I was reviewing Devstack ov
I agree. Throughout I was reviewing Devstack over 3 cycles,
I thought the same thing. Devstack often accepted patches just
adding option although we're not sure who really needs the options.
There are many useless stuff in the options.
For example, default value of devstack option is the same
On 2016/04/08 12:10, Kevin Benton wrote:
Try depending on I2a10a8f15cdd5a144b172ee44fc3efd9b95d5b7e
I tried. Let's wait for the result.
On Thu, Apr 7, 2016 at 8:02 PM, Hongbin Lu > wrote:
> -Original Message-
>
On 2016/04/05 22:23, Ihar Hrachyshka wrote:
Hirofumi Ichihara <ichihara.hirof...@lab.ntt.co.jp> wrote:
Hi Ihar,
On 2016/04/05 7:57, Ihar Hrachyshka wrote:
Hi all,
in neutron, we have a bunch of configuration options to control
advanced filtering features for API, f.e. allow_s
Hi Ihar,
On 2016/04/05 7:57, Ihar Hrachyshka wrote:
Hi all,
in neutron, we have a bunch of configuration options to control
advanced filtering features for API, f.e. allow_sorting,
allow_pagination, allow_bulk, etc. Those options have default False
values.
I saw allow_bulk option is set
We should go back to our roots so it's better to rename "Neutron" to
"Nova Network".
Thanks,
Hirofumi
On 2016/04/01 15:24, Akihiro Motoki wrote:
IIRC 'Quantum' was renamed to 'Neutron' due to the trademark issue.
I don't think reverting it to 'Quantum' resolves the issue.
When we chose a new
Hi Gary,
You can look at the discussion in here[1, 2]
[1]: https://bugs.launchpad.net/neutron/+bug/1560003
[2]: https://review.openstack.org/#/c/268726
Thanks,
Hirofumi
On 2016/03/28 15:36, Gary Kotton wrote:
Hi,
In the M cycle BGP support was added in tree. I have seen specs in the
L2 GW
Hi reedip,
On 2016/03/18 12:06, reedip banerjee wrote:
Dear All Neutron Developers and Reviewers,
I have a query/concern related to the parsing of options in
python-neutronclient.
I would like to bring this up, as it "may" also impact the transition
of the CLIs to the openstack client as
Which version did you use? Neutron had the issue once.
On 2016/03/13 10:54, Zhi Chang wrote:
hi, guys.
I deployed DVR in my local environment by following this
document(https://wiki.openstack.org/wiki/Neutron/DVR). And I have
three compute nodes which running DVR l3-agent and two
On 2016/03/01 9:00, Armando M. wrote:
On 29 February 2016 at 15:34, Hirofumi Ichihara
<ichihara.hirof...@lab.ntt.co.jp
<mailto:ichihara.hirof...@lab.ntt.co.jp>> wrote:
Hi Armando,
I didn't know and I have such patch now.
Thank you for your message.
Hi Armando,
I didn't know and I have such patch now.
Thank you for your message.
I have seen that neutron spec has the flag in the Commit Message.
In such case, we don't need to add the flag into the implementation
patch, do we?
Thanks,
Hirofumi
On 2016/03/01 7:18, Armando M. wrote:
Hi
I'm considering the tag implementation in neutron.
Although I proposed server returns 409 in tag existing case, on the
basis of the above discussion, server should return the same response code.
I will change current implementation to returning 201.
Thanks,
Hirofumi
On 2016/02/27 2:24,
On 2016/02/08 18:17, Ihar Hrachyshka wrote:
Kevin Benton wrote:
Propose it as a devref patch!
+1. Has it happened already?
Here https://review.openstack.org/#/c/275381/
On Wed, Jan 27, 2016 at 12:30 PM, Dustin Lundquist
wrote:
We should
On 2016/01/12 5:14, Armando M. wrote:
On 11 January 2016 at 12:04, Carl Baldwin > wrote:
What do we do? My calendar was set up with the sane bi-weekly thing
and it shows the meeting for tomorrow. The last word from our
fearless
cases that are needed by operators and users.
On Sun, Dec 13, 2015 at 11:25 PM, Hirofumi Ichihara
<ichihara.hirof...@lab.ntt.co.jp
<mailto:ichihara.hirof...@lab.ntt.co.jp>> wrote:
On 2015/12/14 15:58, Kevin Benton wrote:
What decision would lead the user to request
Hi Kevin,
On 2015/12/14 11:10, Kevin Benton wrote:
Hi all,
The availability zone code added a new field to the network API that
shows the availability zones of a network. This caused a pretty big
performance impact to get_networks calls because it resulted in a
database lookup for every
first. There is a gap between the time user threw and the time
his resource is scheduled. After user threw API request with AZ1 and
AZ2, if all agents of AZ2 are dead before scheduling, the resource is
scheduled in AZ1 only.
On Sun, Dec 13, 2015 at 10:31 PM, Hirofumi Ichihara
<ichihara.hi
recreates his resource with
availability_zone_hints [AZ1, AZ3]
On Sun, Dec 13, 2015 at 8:57 PM, Hirofumi Ichihara
<ichihara.hirof...@lab.ntt.co.jp
<mailto:ichihara.hirof...@lab.ntt.co.jp>> wrote:
Hi Kevin,
On 2015/12/14 11:10, Kevin Benton wrote:
Hi all,
The avail
Although the restaurant is announced, the place is hard to go for us.
I and Akihiro will take you to the place.
Please gather in registration hall at 6:30.
Don’t mind about RSVP. You can come freely.
IMPORTANT THING: Don’t leave your wallet. We don’t have sponsor ;)
> On 2015/10/27, at 15:07,
> On 2015/10/14, at 4:07, Armando M. wrote:
>
> Hi folks,
>
> We are in the last hours of Liberty, let's pause for a second and consider
> merging patches only if absolutely necessary. The gate is getting clogged and
> we need to give priority to potential RC3 fixes or
Hi Gary,
Thank you for your suggestion.
In Liberty cycle[1], I have discussed about these points with neutron folks and
network operators.
> On 2015/10/05, at 15:54, Gary Kotton wrote:
>
> Hi,
> Yes, you are correct. That patch is the culprit (my bad and once again humble
Hi,
I have some plans in Mitaka cycle.
1. AZ support[1]
- I proposed AZ support in Liberty but the millstone is Mitaka now. The spec
has been merged in Mitaka.
I keep to propose the patches on Gerrit.
2. LinuxbrideDVR
- I'm trying to create concrete implementation and then I achieve it
Good work and thank you for your help with my patch.
Anyway, I don’t know when does bp owner have to merge the code by.
I can see the following sentence in bp rule[1]
“The PTL will create a -backlog directory during the RC window and
move all specs which didn’t make the there.”
Did we have to
-
Hirofumi Ichihara
__
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
On 2015/06/11, at 11:05, Kyle Mestery mest...@mestery.com wrote:
On Wed, Jun 10, 2015 at 8:56 PM, Hirofumi Ichihara
ichihara.hirof...@lab.ntt.co.jp mailto:ichihara.hirof...@lab.ntt.co.jp
wrote:
Hi folks,
I have maintained metaplugin in Neutron.
The plugin enables users to use
unify the two parameters.
I would leave the following for backward compatibility.
PUBLIC_PHYSICAL_NETWORK=${PUBLIC_PHYSICAL_NETWORK:-$PHYSICAL_NETWORK}
and
change PHYSICAL_NETWORK into PUBLIC_PHYSICAL_NETWORK in all the code.
-
Hirofumi Ichihara
Hi Sean,
We have a *lot* of configuration knobs in DevStack for Neutron. I am not
a smart man, so I think we may need to wrap our arms around this and
simplify.
I agree with you. I want to fix the confused configure too.
PHYSICAL_NETWORK is a option in order to setup L2 public network only
Sure, though on the other hand, doesn't current discussion seem to indicate
that OVS with DVR is not a viable replacement for nova-network multi-host HA
(eg due to complexity), and this is why folks were working towards linux
bridge?
Some openstacker doesn’t believe ovs performance is
Hi Dean,
Thank you for your response.
I’ve forgotten the sprint. I looked etherpad log and got it clearly.
thanks,
Hirofumi
2015/03/27 12:46、Dean Troyer dtro...@gmail.com のメール:
On Thu, Mar 26, 2015 at 8:00 PM, Hirofumi Ichihara
ichihara.hirof...@lab.ntt.co.jp wrote:
I found lib/neutron
Hi Devstack folks,
I found lib/neutron-legacy in master branch today.
I didn’t know this important change because I couldn’t watch for the last few
days.
Could someone tell me what is neutron-legacy?
How do we manage and develop it?
I would also like to know where is the change decided, IRC or
it. It may be worth fixing.
Thanks,
Hirofumi
2015/02/24 2:00、Ihar Hrachyshka ihrac...@redhat.com :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/2015 11:45 AM, Hirofumi Ichihara wrote:
Neutron experts,
I caught a bug report[1].
Currently, Neutron enable admin to delete default
Neutron experts,
I caught a bug report[1].
Currently, Neutron enable admin to delete default security group. But Neutron
doesn’t allow default security group to keep deleted. Neutron regenerates
default security group as security group api is called next. I have two
questions about the
of reasons.
It seems everything is fixed now and all the jobs have been reinstated.
Salvatore
On 25 December 2014 at 08:32, Hirofumi Ichihara
ichihara.hirof...@lab.ntt.co.jp wrote:
Hi Gary,
Thank you for your response.
I understand. I’m expecting good news.
Thanks,
Hirofumi
2014
Hi,
My patch(https://review.openstack.org/#/c/124011/) received verified-1 from
VMware NSX CI.
But my patch isn’t related to VMware so I added comment “vmware-recheck-patch”
according to VMware NSX CI comment.
However, VMware NSX CI don’t recheck.
I don’t know recheck word was wrong or CI
: Hirofumi Ichihara ichihara.hirof...@lab.ntt.co.jp
Reply-To: OpenStack List openstack-dev@lists.openstack.org
Date: Thursday, December 25, 2014 at 5:41 AM
To: OpenStack List openstack-dev@lists.openstack.org
Subject: [openstack-dev] [devstack][VMware NSX CI] VMware NSX CI fails and
don't recheck
Hi, all
I’m trying to connect ofagent to switches other than OVS.
But, it’s not going. I think that the ofagent cannot connect their switches.
Is there anyone tried?
Hirofumi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Yamamoto,
ofagent is still OVS-only.
to support non-OVS switches, there are some todo items including
nova/neutron interface drivers.
https://wiki.openstack.org/wiki/Neutron/OFAgent/Todo
I understand.
Thank you.
Hirofumi Ichihara
___
OpenStack-dev
are just options at the moment; I tend to lean toward the latter,
but it would be great to have your feedback.
Salvatore
On 28 May 2014 11:20, Hirofumi Ichihara ichihara.hirof...@lab.ntt.co.jp
wrote:
Hi, Salvatore
I think neutron needs the task management too.
IMO, the problem
://wiki.openstack.org/wiki/Neutron/LBaaS/API_1.0#Synchronous_versus_Asynchronous_Plugin_Behavior
thanks,
Hirofumi
-
Hirofumi Ichihara
NTT Software Innovation Center
Tel:+81-422-59-2843 Fax:+81-422-59-2699
Email:ichihara.hirof...@lab.ntt.co.jp
61 matches
Mail list logo