http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-08-11-21.00.html
YAMAMOTO Takashi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
i asked him to trigger
recheck and it worked.
YAMAMOTO Takashi
>
> Can we remove the voting rights for the ODL CI until there is a documented
> way to trigger rechecks and a public contact on the drivers page for when
> things go wrong? Getting reviews is already hard enough, le
hi,
we (Ryu project) are currently working on a new version of
Ryu neutron plugin/agent. we have a blueprint for it
waiting for review/approval. can you please take a look? thanks.
https://blueprints.launchpad.net/neutron/+spec/ryu-ml2-driver
YAMAMOTO Takashi
-to-review code to gerrit.
mark, can you please consider moving it back into icehouse?
YAMAMOTO Takashi
>
> YAMAMOTO Takashi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
it if you have any opinions. thank you.
YAMAMOTO Takashi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
https://review.openstack.org/#/c/138980/)
thank you.
YAMAMOTO Takashi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
hi,
good to hear.
do you have any estimate when it will be available?
will it cover dom0 side of the code found in
neutron/plugins/openvswitch/agent/xenapi?
YAMAMOTO Takashi
> Hi Yamamoto,
>
> XenAPI and Neutron do work well together, and we have an private CI that is
> running
> Today's ML2 sub-team meeting is cancelled.
>
> -Bob
will the next one be held normally?
i want to hear details of modular l2 agent idea before the summit.
sooner is better because it's blocking ofagent works
totype
a modular agent to demonstrate how much of the code can be shared
by this effort?
YAMAMOTO Takashi
>
> Thanks,
>
> -Mohammad
>
> [1] https://etherpad.openstack.org/p/juno-neutron-modular-l2-agent
> [2]
> http://junodesignsummit.
n in OVS plugin
> and would be submitting a neutron spec related to the blueprint soon.
does your implementation use OVS' mirroring functionality?
or is it flow-based?
YAMAMOTO Takashi
>
> I would like to know other who are also interested in introducing Port
> Mirroring extens
te if someone provides more info for other bgp speakers.
YAMAMOTO Takashi
> Good afternoon Neutron developers!
>
> There has been a discussion about dynamic routing in Neutron for the past few
> weeks in the L3 subteam weekly meetings. I've submitted a review request of
> the
> Hi folks
>
> ExaBGP won't suit for BGPVPN implementation because it isn't support vpnv4.
> Ryu is supporting it, however they have no internal api to binding
> neutron network & route target.
can you explain a little more?
do you have api suggestions?
YAMAMOTO T
can anyone please review this small fix for ofagent?
https://review.openstack.org/#/c/88224/
it's unfortunate a simple fix like this taking months to be merged.
YAMAMOTO Takashi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
gestions and/or requests.
we are currently working on our bgp api refinement and documentation.
hopefully they will be available early next week.
for both of bgp blueprints, it would be possible, and might be desirable,
to create reference implementations in python using ryu or exabgp.
(i p
an update after today's l3 meeting:
here's a new version of ryu bgp api patch.
http://sourceforge.net/p/ryu/mailman/message/32453021/
YAMAMOTO Takashi
> I have seen the Ryu team is involved and responsive to the community.
> That goes a long way to support it as the reference im
eadthedocs.org/en/latest/library_bgp_speaker.html
http://ryu.readthedocs.org/en/latest/library_bgp_speaker_ref.html
YAMAMOTO Takashi
>
> YAMAMOTO Takashi
>
>> I have seen the Ryu team is involved and responsive to the community.
>> That goes a long way to support it as the re
ects
> using spec repositories had similar thoughts, and I also wanted to
> share this info for BP submitters and reviewers.
it would be better if there's an easy way for reviewers to
see formatted versions of specs rather than raw *.rst, especially
for diagrams. does other project have
is it ok?
YAMAMOTO Takashi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
addresses should be used for non-trunk VLANs)
YAMAMOTO Takashi
> Aaron: untrue. It does, but OVS doesn't, and so networks implemented with
> the OVS driver will drop packets. Use Linuxbridge instead.
> --
> Ian.
>
> On 19 September 2014 22:27, Aaron Rosen wrote:
>
hi,
> Hi, all
>
> I’m trying to connect ofagent to switches other than OVS.
thank you for trying ofagent.
> But, it’s not going. I think that the ofagent cannot connect their switches.
> Is there anyone tried?
ofagent is still OVS-only.
to support non-OVS switches, there are some todo items in
> Hello. As we discussed at the summit and following irc meeting,
> the time slot/channel is changed from Nov 19, 2014.
>
> - Weekly 17:00AM UTC(Wednesday) 30min
17:00AM ???
> - IRC channel: #openstack-meeting-4
> - Next: Nov 19, 2014
>
> see https://wiki.openstack.org/wiki/Meetings/ServiceVM f
CI clean $DEST for each runs?
i guess you are somehow mixing different versions of code.
YAMAMOTO Takashi
>
> I found some CIs have same problem.
>
> Does anyone give me a hint to solve this problem ?
>
> Thanks.
> --
> Itsuro ODA
>
>
> __
CI started detecting the breakage correctly. the breakage
will be fixed if the following changes are merged.
https://review.openstack.org/#/c/103764/
https://review.openstack.org/#/c/106701/
YAMAMOTO Takashi
___
OpenStack-dev mailing list
Ope
> On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi
> wrote:
>> if you are wondering why ofagent CI ("Neutron Ryu") reported a failure
>> (non-voting) for your review recently, you can probably safely ignore it.
>> sorry for inconvenience.
>>
>> th
>> On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi
>> wrote:
>>> if you are wondering why ofagent CI ("Neutron Ryu") reported a failure
>>> (non-voting) for your review recently, you can probably safely ignore it.
>>> sorry for inco
can you consider increasing the number of them?
postponing vendor stuffs (like mine) for the reason would make
the situation worse as many of developers/reviewers are paid for
vendor stuffs.
YAMAMOTO Takashi
>
> I don't plan to open a Kilo directory in the specs repository quite
> yet. I
hi,
what's the right procedure to deprecate a plugin? we (ryu team) are
considering deprecating ryu plugin, in favor of ofagent. probably in
K-timeframe, if it's acceptable.
YAMAMOTO Takashi
___
OpenStack-dev mailing list
Ope
> On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi
> wrote:
>> hi,
>>
>> what's the right procedure to deprecate a plugin? we (ryu team) are
>> considering deprecating ryu plugin, in favor of ofagent. probably in
>> K-timeframe, if it's accep
migration scheme -
> from plugin A to plugin B.
i afraid it's impossible in general.
YAMAMOTO Takashi
> Thanks
> Gary
>
> On 7/30/14, 8:17 PM, "YAMAMOTO Takashi" wrote:
>
>>hi,
>>
>>what's the right procedure to deprecate a plugin? we (ryu
just an update: the "Neutron Ryu" CI is getting stable now.
please let me know if you noticed any problems. thank you.
YAMAMOTO Takashi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-b
> On Thu, Jul 31, 2014 at 1:43 AM, YAMAMOTO Takashi
> wrote:
>>> On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi
>>> wrote:
>>>> hi,
>>>>
>>>> what's the right procedure to deprecate a plugin? we (ryu team) are
>>>>
hi,
can you explain why you want to use pbr 1.0.1 in the first place?
what's wrong with requiring pbr<1.0 ?
YAMAMOTO Takashi
> Hi openstack-dev team,
>
> Can you also release latest oslo.config to allow pbr 1.0.1?
> In my convenience I want to use it.
>
>
> Tha
decision that led to the existing architecture is
>> due to the way OVS handles packets and interact with netfilter.
>
> I think you're talking about the bridge between a tap device and br-int and
> not about br-tun.
sure, these are separate topics.
FYI, ofagent uses a sing
ecked wiki and previous meeting logs but it wasn't clear to me)
YAMAMOTO Takashi
> hi,
>
> good to hear.
> do you have any estimate when it will be available?
> will it cover dom0 side of the code found in
> neutron/plugins/openvswitch/agent/xenapi?
>
> YAMAMOTO Takash
hi,
i added an item to the agenda.
https://wiki.openstack.org/wiki/Meetings/XenAPI#Next_meeting
YAMAMOTO Takashi
> Hi,
>
> The next meeting will be tomorrow @ 15:00 UTC - We'd love to see you there
> and we can talk about the CI and Terry's work.
>
> We're
Ryu/ofagent CI will be offline during this weekend.
sorry for inconvenience.
YAMAMOTO Takashi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
term.
any comments/thoughts?
YAMAMOTO Takashi
[1] https://blueprints.launchpad.net/neutron/+spec/ovs-ofctl-to-python
[2] https://review.openstack.org/#/c/153946/
__
OpenStack Development Mailing List (not for usage qu
lugins. and use requirements.txt there.
>> for longer term, this might be a way to go. but i don't want to
>> block my work until it happens.
>>
>>
>
> We’re not ready for that yet, as co-gating has proven as a bad strategy
> and we need to keep the reference i
> On 17 February 2015 at 22:00, YAMAMOTO Takashi
> wrote:
>
>> hi,
>>
>> i want to add an extra requirement specific to OVS-agent.
>> (namely, I want to add ryu for ovs-ofctl-to-python blueprint. [1]
>> but the question is not specific to the blueprint.)
hi,
Ryu/ofagent CI will be offline during the next weekend
for a scheduled maintenance. sorry for inconvenience.
YAMAMOTO Takashi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
hi,
sorry for keep forgetting and thank you for reminder.
YAMAMOTO Takashi
> Hi-
>
> Regarding the CI offline mails, I previously received an email from Anita.
> Please find the summary below.
>
> Please set your account listing to down on this page:
> https://wi
> However, I briefly looked through the L2 agent code and didn't see a
> periodic task to resync the port information to protect from a neutron
> server that failed to send a notification because it crashed or lost its
> amqp connection. The L3 agent has a period sync routers task that helps in
> t
> Hello everyone,
>
> Due to release-critical issues spotted in Nova, Sahara and Heat during
> RC1 testing, new release candidates were created for Kilo. The list of
> RC2 fixes, as well as RC2 tarballs are available at:
>
> https://launchpad.net/nova/kilo/kilo-rc2
> https://launchpad.net/nova/sa
eed nicer, it's difficult as port_update is
an async call (cast) and does not wait for errors
including UnsupportedVersion.
YAMAMOTO Takashi
>
> Cheers,
> Armando
>
>
>>
>> I am writing this email as heads up and also to ask a question. The
>> port_update sig
44 matches
Mail list logo