https://wiki.openstack.org/wiki/Meetings/ServiceVM
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
e.
thanks,
>
> Thanks,
>
> Edgar
>
> On 11/19/13 3:57 AM, "Isaku Yamahata" wrote:
>
> >On Mon, Nov 18, 2013 at 03:55:49PM -0500,
> >Robert Kukura wrote:
> >
> >> On 11/18/2013 03:25 PM, Edgar Magana wrote:
> >> > Develope
reliable set of abstractions for
> ensuring operations are properly ordered thus avoiding those races (I agree
> on the observation on the pre/post commit solution).
This discussion has been started with core plugin, another resources like
service (lbaas, fw, vpn...) have similar race conditi
arn from other projects, nova, cinder...
thanks,
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
river?
> How to
> make sure database and back-end implementation in sync need more thought.
> As configuring backend device can be an a-sync process, rollback database
> tables can be cumbersome.
--
Isaku Yamahata
___
OpenStack-dev mailing li
nges to DB before sending
notifications. In such cases, notification will be lost.
Polling to resync would be necessary somewhere.
- notification loss isn't considered.
self.resync is not always run.
some optimization is possible, for example
- detect loss by sequence number
- polling can be postponed when notifications come without loss.
- periodic resync spawns threads, but doesn't wait their completion.
So if resync takes long time, next resync can start even while
resync is going on.
- processing notification can be batched.
- reducing live report.
piggyback on other RPC call.
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
Regarding to out-of-order notification, making agent to be able to accept
out-of-order notifications somehow (by polling, sequence number or however) will
open up the possibility for active-active Neutron server which is being
discussed
in this thread.
> > - periodic resync spaw
f we expose that functionality via oslo.messaging, but
> it's certainly something AMQP can do.
What happens if intermittent network instability occur?
When the connection between agent <-> AMQP is unintentionally closed,
will agent die or reconnect to it?
--
Isaku Yamahata
_
On Mon, Dec 09, 2013 at 08:07:12PM +0900,
Isaku Yamahata wrote:
> On Mon, Dec 09, 2013 at 08:43:59AM +1300,
> Robert Collins wrote:
>
> > On 9 December 2013 01:43, Maru Newby wrote:
> > >
> >
> > >>> If AMQP service is set up not to lose notifica
On Tue, Dec 10, 2013 at 07:28:10PM +1300,
Robert Collins wrote:
> On 10 December 2013 19:16, Isaku Yamahata wrote:
>
> > Answering myself. If connection is closed, it will reconnects automatically
> > at rpc layer. See neutron.openstack.common.rpc.impl_{kombu, qpid}.py.
&g
> > synchronization are able to cooperate safely? Or hoping that it will be so
> > in the future?
>
> I'm saying that you can avoid race conditions by a combination of
> 'subscribe to changes' + 'give me the full state'.
Like this?
https://revie
On Tue, Dec 10, 2013 at 06:35:38PM +0900,
Maru Newby wrote:
>
> On Dec 10, 2013, at 4:47 PM, Isaku Yamahata wrote:
>
> > On Tue, Dec 10, 2013 at 07:28:10PM +1300,
> > Robert Collins wrote:
> >
> >> On 10 December 2013 19:16, Isaku Yamahata wrote:
> &g
On Wed, Dec 11, 2013 at 01:23:36AM +0900,
Maru Newby wrote:
>
> On Dec 10, 2013, at 6:36 PM, Isaku Yamahata wrote:
>
> > On Mon, Dec 09, 2013 at 08:43:59AM +1300,
> > Robert Collins wrote:
> >
> >>>> listening: when an agent connects after an outa
On Fri, Dec 06, 2013 at 04:30:17PM +0900,
Maru Newby wrote:
>
> On Dec 5, 2013, at 5:21 PM, Isaku Yamahata wrote:
>
> > On Wed, Dec 04, 2013 at 12:37:19PM +0900,
> > Maru Newby wrote:
> >
> >> In the current architecture, the Neutron service handles RPC
me to l2-gateway one?
https://blueprints.launchpad.net/neutron/+spec/l2-gateway
- Figure 5
What's the purpose of br-int local VID?
VID can be directly converted from br-eth1 VID to VM VID untagged.
--
Isaku Yamahata
___
OpenStack-dev mailing list
we have to
> accommodate the fact that VLANs are a special case, but this is very much
> an artifact of the plugin implementation - Linux bridge based network
> infrastructure simply doesn't have this problem, for instance.
>
> On 17 December 2013 06:17, Isaku Yamahata wrote:
operations?
Instead of issueing many ovs-vsctl command,
ovs-vsctl -- command0 [args] -- command1 [args] -- ...
Then, the number of ovs-vsctl will be reduced and ovs-vsctl issues
only single ovsdb transaction.
--
Isaku Yamahata
___
OpenStack-dev ma
nd wait for its reply to confirm the result.
Single barrier synchronization of add/mod-flows vs each barrier
synchronizations of add/mod-flow.
The current implementation doesn't have defer_apply_on/off in
process_network_ports(). Is there any reason for it?
Thanks,
Isaku Yamahata
> Summa
difications,
> such as the drop all rule, will be applied.
> This will probably create a short interval of time in which we might have
> unexpected behaviours (such as VMs on DEAD VLAN able to communicate each
> other for instance).
Agree that more careful ordered update is necessary with
eBAiIZoMJP0NPAO4-60XFY/edit
[3] https://review.openstack.org/#/c/56892/
[4] https://etherpad.openstack.org/p/NeutronServiceVM
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
nks,
On Fri, Jan 10, 2014 at 01:36:23PM +0900,
Isaku Yamahata wrote:
> Hello Neutron developers.
>
> Framework for advanced service[1][2] was discussed at the last summit.
> Since it's been a while and there has been a progress as the code[3],
> I think it's good time
ia 192.168.1.1 dev wlan0 src 192.168.1.17
> cache
6: run a command which is specified in the config file.
use its output.
Then arbitrary logic can be used by writing shell script or whatever
without modifying neutron.
Some samples which implement option 1-5 can be put in the repo.
thanks,
C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
tings/AdvancedServices
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
e are any other better way, I'd also like to know.
thanks,
> I'm very eager to be able to get your help and sincerely thank you in advance.
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://l
What's your timezone?
18.00UTC doesn't work for me because my timezone is UTC+9 and it's 3:00AM.
thanks,
On Mon, Feb 10, 2014 at 06:43:05AM +,
"balaj...@freescale.com" wrote:
> Hi Isaku Yamahata,
>
> Is it possible to move the below time slot a little e
balaj...@freescale.com [mailto:balaj...@freescale.com]
> ??送?奔?: 2014年2月10日 15:11
> 收件人: Isaku Yamahata; OpenStack Development Mailing List (not for usage
> questions)
> 主??: Re: [openstack-dev] [Neutron] Service VM: irc discussion?
>
> Hi Isaku Yamahata,
>
> We are at UTC+5.30
gt;>
> >>
> >>
> >> ___
> >> OpenStack-dev mailing list
> >> OpenStack-dev@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
>
23, 2014 7:17 PM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Cc: isaku yamahata
> > Subject: Re: [openstack-dev] [neutron] Service VMs
> >
> > On Tue, Apr 22, 2014 at 5:49 PM, Isaku Yamahata
> > wrote:
> > > Hi. Keyle, tha
, jeeve,...
topic name: servicevm, hosting device,...
- design API/model
- way to review: gerrit or google-doc?
- design strategy
* open discussion
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
https://wiki.openstack.org/wiki/ServiceVM/terminology
LINK: https://wiki.openstack.org/wiki/ServiceVM
lots of short-term gap-filler discussion
thanks,
Isaku Yamahata
On Fri, May 02, 2014 at 02:01:31PM +0900,
Isaku Yamahata wrote:
> Hi. This is a reminder mail for the servicevm IRC meeting
> May 6, 2014
visit docs.google.com in China.
>
>url:
> https://docs.google.com/presentation/d/14dvV3S9Eph2z-auk34I_Ftld-lHA3VMoyNWAPRTeWgE/edit?usp=sharing
>
>
> many thanks!
>
>
>
>
>
>
>
>
>
> At 2014-05-06 14:54:09,&quo
Hi. This is a follow up mail of the design summit.
The next IRC meeting will be held on
June 2nd, 2014 Tuesdays 5:00(AM)UTC-
on #openstack-meeting
(May 20, 27 will be skipped).
https://etherpad.openstack.org/p/servicevm
https://wiki.openstack.org/wiki/Meetings/ServiceVM
thanks,
--
Isaku Yamahata
Hi, I will also attend the NFV IRC meeting.
thanks,
Isaku Yamahata
On Tue, May 20, 2014 at 01:23:22PM -0700,
Stephen Wong wrote:
> Hi,
>
> I am part of the ServiceVM team and I will attend the NFV IRC meetings.
>
> Thanks,
> - Stephen
>
>
> On Tue, May 20, 20
estrator and VNF manager.
Especially life cycle management of VMs/services. configuration of services.
I think the above document and the NFV documents only give high level
statement of components, right?
thanks,
>
> Thanks,
> Dmitry
>
>
> On Wed, May 21, 2014 at 9:01 AM, Isaku Yam
ice is composed of hierarchical multiple VMs.
I suspect no one knows. This is why we unite to make efforts for NFV.
thanks,
Isaku Yamahata
> All the best,
> Kenichi
>
>
>
> > From: Dmitry [mailto:mey...@gmail.com]
> > Sent: Thursday, May 22, 2014 5:40 PM
> >
he implementation for more complex case like forwarding graph
(VNF and VNF-FG in NFV terminology?).
> In addition, I would happy to know if Service VM will be incubated for Juno
> release.
Yea, I'm going to create the first repo in stackforge in one or two weeks.
thanks,
Isaku Yamahata
&g
nstack.org/p/topology-as-a-service
[4] https://blueprints.launchpad.net/neutron/+spec/physical-network-topology
[5] https://review.openstack.org/#/c/91275/
thanks,
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http:
surely useful.
The information which is got by your work can be used for many purpose.
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
https://wiki.openstack.org/wiki/Topology-as-a-service
[2] https://etherpad.openstack.org/p/hierarchical_network_topology
[3] http://lists.openstack.org/pipermail/openstack-dev/2014-May/035868.html
[4] https://review.openstack.org/#/c/91275/
thanks,
Isaku Yamahata
On Fri, May 30, 2014 at 11:11:46AM
tps://etherpad.openstack.org/p/servicevm
https://wiki.openstack.org/wiki/Meetings/ServiceVM
Sorry for confusion.
thanks,
On Mon, May 19, 2014 at 10:59:26PM +0900,
Isaku Yamahata wrote:
> Hi. This is a follow up mail of the design summit.
> The next IRC meeting will be held on
> June 2nd, 201
-03-05.04.html
http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-06-03-05.04.log.html
thanks,
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.
ed: more than 1h when VXLAN range is [1,
> >>> 1M].
> >>> >> >
> >>> >> > So, any good solution about this performance issue?
> >>> >> >
> >>> >> > Thanks,
> >>> >> > Xurong Yang
> >
mitry
>
>
> On Tue, Jun 3, 2014 at 10:00 AM, Isaku Yamahata
> wrote:
>
> > Here is the meeting minutes of the meeting.
> >
> > ServiceVM/device manager
> > meeting minutes on June 3, 2014:
> > https://wiki.openstack.org/wiki/Meetings/Servic
Hi. This is a reminder mail for the servicevm IRC meeting
June 10, 2014 Tuesdays 5:00(AM)UTC-
#openstack-meeting on freenode
https://wiki.openstack.org/wiki/Meetings/ServiceVM
agenda: (feel free to add your items)
* project incubation
* NFV meeting follow up
* open discussion
--
Isaku Yamahata
Mon, Jun 09, 2014 at 03:16:27PM +0900,
Isaku Yamahata wrote:
> Hi. This is a reminder mail for the servicevm IRC meeting
> June 10, 2014 Tuesdays 5:00(AM)UTC-
> #openstack-meeting on freenode
> https://wiki.openstack.org/wiki/Meetings/ServiceVM
>
> agenda: (feel free to add yo
ement
* action items from the last week
* project incubation
* NFV meeting follow up
* blueprint follow up
* open discussion
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/lis
L2 agents. I have also posted some code fragments at [2]
> >> >> > sketching the implementation of the proposed architecture. Please
> >> >> > have a
> >> >> > look when you get a chance and let us know if you have any comments.
> >> >> >
> >> &
ar library written in python.
thanks,
Isaku Yamahata
On Tue, Jun 17, 2014 at 11:38:36AM -0500,
Kyle Mestery wrote:
> Another area of improvement for the agent would be to move away from
> executing CLIs for port commands and instead use OVSDB. Terry Wilson
> and I talked about this, and re
me is inconvenient for you. The schedule will also be
discussed, and the meeting time would be changed from the 2nd one.
Thanks,
On Mon, Feb 10, 2014 at 03:11:43PM +0900,
Isaku Yamahata wrote:
> As the first patch for service vm framework is ready for review[1][2],
> it would be a good idea
tp://wiki.debian.org/MeetBot . (v 0.1.4)
>
> To clarify, are you looking at Tuesdays at 22:00 UTC or 23:00 UTC?
>
> Thanks,
> - Stephen
>
>
>
> On Wed, Mar 5, 2014 at 9:57 AM, Isaku Yamahata
> wrote:
>
> > Since I received some mails privately, I'd
Thanks,
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi Balaji.
Let's discuss/determine on the time at the meeting as it is listed as agenda.
Sorry for inconvenience for the first time.
Do you have any feedback other than the meeting time?
thanks,
On Tue, Mar 18, 2014 at 06:18:01AM +,
"balaj...@freescale.com" wrote:
>
nstack.org/wiki/Meetings/ServiceVM
Thanks,
On Tue, Mar 18, 2014 at 03:04:53PM +0900,
Isaku Yamahata wrote:
> Hello. This is a reminder for servicevm framework IRC meeting.
> date: March 18 (Tuesday) 23:00 UTC
> channel: #openstack-meeting
>
> the followings are proposed as agen
Hi. This is a reminder mail for the servicevm IRC meeting
April 1, 2014 Tuesdays 5:00(AM)UTC-
- status update
- dividing the blueprints into smaller elemental ones
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hi. This is a reminder mail for the servicevm IRC meeting
April 8, 2014 Tuesdays 5:00(AM)UTC-
#openstack-meeting on freenode
- status update
- details of dividing the blueprints
(Sorry I'm going to write it up from now on.)
- design summit plan
--
Isaku Yam
sage-proxy-server
[6] https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
of network-based agent as a huge
> advantage. Could you please clarify why you've picked design depending
> on hypervisor?
I agree those arguments.
But I don't see how network-based agent approach works with Neutron
network for now. Can you please elaborate on it?
thanks,
tion in case that the
agent local configuration is out of sync with what neutron server
thinks.
thanks,
Isaku Yamahata
On Thu, Apr 10, 2014 at 2:11 AM, Daniel P. Berrange wrote:
> On Wed, Apr 09, 2014 at 05:33:49PM +0900, Isaku Yamahata wrote:
>> Hello developers.
>>
>>
; >>
> >> ___
> >> OpenStack-dev mailing list
> >> OpenStack-dev@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> > ___
https://blueprints.launchpad.net/neutron/+spec/l3-plugin-brocade-vyatta-vrouter
https://blueprints.launchpad.net/neutron/+spec/firewall-plugin-for-brocade-vyatta-vrouter
[3]
https://blueprints.launchpad.net/neutron/+spec/tcs-fwaas-netconf-host-plugin
--
Isaku Yam
_
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
thanks,
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Thu, Nov 13, 2014 at 12:09:18PM +0900,
Isaku Yamahata wrote:
> 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
Oops.
- Weekly 17:00 UTC(Wednesday) 30min
(time is co
; >>
> >>>> >>
> >>>> >> ___
> >>>> >> 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@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
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Igor Duarte Cardoso.
> >>> http://igordcard.com
> >>> @igordcard
> >>>
> >>> ___
> >>> 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@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
> >
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi. This is a reminder mail for the weekly servicevm IRC meeting.
>From Nov 19 2014, the timeslot/channel has been changed.
Please be prepared.
Nov 19, 2014 Wednesday 17:00 UTC-
#openstack-meeting-4 on freenode
https://wiki.openstack.org/wiki/Meetings/ServiceVM
--
Isaku Yamah
What's the progress by Terry Wilson?
If not much, I'm willing to file blueprint/spec and drive it.
thanks,
On Wed, Jun 18, 2014 at 07:00:59PM +0900,
Isaku Yamahata wrote:
> Hi. Ryu provides ovs_vsctl.py library which is python equivalent to
> ovs-vsctl command. It speaks OVSDB
reason? Maru? I'm curious.
At least I fixed the issues I hit when I wrote ovs_vsctl.py.
Thanks,
> Terry
>
> > On Wed, Jun 18, 2014 at 07:00:59PM +0900,
> > Isaku Yamahata wrote:
> >
> > > Hi. Ryu provides ovs_vsctl.py library which is python equiva
print follow up
* open discussion
* add your items
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
As action items, I've moved API spec to google-doc
until stackforge repo is created.
Here is the link
https://docs.google.com/document/d/10v818QsHWw5lSpiCMfh908PAvVzkw7_ZUL0cgDiH3Vk/edit?usp=sharing
thanks,
On Mon, Jun 23, 2014 at 11:25:03PM +0900,
Isaku Yamahata wrote:
> Hi. T
> > Kyle
> >
> > [1]
> > https://wiki.openstack.org/wiki/Network/Meetings#Team_Discussion_Topics
> >
> >
> >> Cheers,
> >>
> >> Brent
> >>
> >> ___
> >> 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@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
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
hem to send an email to the
> openstack-dev ML though, so we can have the discussion here.
As I commented at the gerrit, we, two authors of port security
(Shweta and me), have agreed that the blueprints/specs will be unified.
I'll send a mail for a spec freeze exception soon.
thanks,
--
Isaku
https://review.openstack.org/#/c/106222/
Add Port Security Implementation in ML2 Plugin
The author, Shweta, and I have agreed to consolidate those specs/blueprints
and unite for the same goal.
Thanks,
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStac
but it defines only rest API.
If it touches iptables_firewall driver, both BPs need mostly same
code change on the driver.
thanks,
>
>
>
> On Tue, Jul 22, 2014 at 11:17 AM, Isaku Yamahata
> wrote:
>
> >
> > I'd like to request Juno spec freeze exception for ML
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
from a user request passed down
> >>> >to the context so it can potentially be used by the plugin or driver?
> >>> >
> >>> >Thank you
> >>> >
> >>> >
> >>> >___
> >>> >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@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
> >>>
> >>
> >>
> >>
> >> --
> >> Kevin Benton
> >>
> >> ___
> >> OpenStack-dev mailing list
> >> OpenStack-dev@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >
> >
> > --
> > Kevin Benton
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
>
>
> --
> Kevin Benton
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Thu, Oct 03, 2013 at 11:33:35PM +,
"Regnier, Greg J" wrote:
> RE: vlan trunking support for network tunnels
> Copying to dev mailing list.
> - Greg
>
> -Original Message-
> From: Kyle Mestery (kmestery) [mailto:kmest...@cisco.com]
> Sent: Thursday, October 03, 2013 6:33 AM
like to discuss this.
>
> Regards,
> Erik
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
some compute nodes use OVS plugin, another nodes LB plugin.
(Right now it may not possible easily, but it will be with ML2 plugin and
mechanism driver). User wants their VMs to run on nodes with OVS plugin for
some reason(e.g. performance difference).
Such usage would be handled similarly.
Thanks
eduling , so possibly
> that's the right direction? Let's wait for the summit discussion.
Interesting. Yeah, I look forward for the summit discussion.
Let's try to involve not only Nova developers, but also other Neutron
developers.
thanks,
--
Isaku Yamahata
___
Port profile is generic way of Neutron to pass plugin-specific data
as dictionary. Cisco plugin uses it to pass VMEFX specific data.
Robert, correct me if I'm wrong.
thanks,
---
Isaku Yamahata
On Thu, Oct 31, 2013 at 10:21:20PM +,
"Jiang, Yunhong" wrote:
> Robert, I
Thursday?
> >
> > On Nov 4, 2013, at 10:20 PM, Yi Sun
> > wrote:
> >
> > > Guys,
> > > I just checked the schedule of unconference sessions. There are no free
> > slots anymore.
> > >
> > > Yi
> > >
> > > On Tuesday,
t; >> migration.save()
> >>
> >>___
> >>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@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
--
Isaku Yamahata
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
e.
changing port during subnet/network update/deletion.)
I think it would be useful to establish reference locking policy
for ML2 plugin for SDN controllers.
Thoughts or comments? If this is considered useful and acceptable,
I'm willing to help.
thanks,
Isaku Yamahata
> -Bob
>
> &
ts.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
versions...
Or are you referring to recirculation?
> >> 2) Using OVS+OF to do QoS
> >>
> >> other interesting stuff to look at:
What exactly do you mean? marking packet or tc queuing?
thanks,
--
Isaku Yamahata
___
; > originated this I'd be grateful.
> > >
> > > dt
> > >
> > > [0] https://github.com/dtroyer/openwrt-packages/tree/master/rc.cloud
> > > --
> > >
> > > Dean Troyer
> > > dtro...@gmail.com
> >
> > >
> > __
Hello Cathy. Thank you for arranging the meeting.
Will we have goto meeting/irc meeting this week(May 12) on this topic?
I haven't seen any announcement yet.
thanks in advance
Isaku Yamahata
On Tue, May 05, 2015 at 08:55:25PM +,
Cathy Zhang wrote:
> Attendees (Sorry we did not c
me.
>
> Thanks,
> Deepthi
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi
gt; 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
--
Isaku Yamahata
_
ch.
> >> given these issues, now i tend to think it's cleaner to introduce
> >> ml2-like precommit/postcommit driver api (or its equivalent via
> >> callbacks) rather than using these existing notifications.
> >>
> >> how do you think?
> >
> >
>
>
On Fri, Sep 08, 2017 at 12:26:56PM +0900,
Takashi Yamamoto wrote:
> hi,
>
> On Fri, Sep 8, 2017 at 5:52 AM, Isaku Yamahata
> wrote:
> > Hi.
> >
> > Any update on this? Now L3 service provider got the time slot at the PTG.
> >
> > Yamamoto, do you ha
; > > > > > _
> > > > > > OpenStack Development Mailing List (not for usage questions)
> > > > > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subjec
> > > > > > t:unsubscribe
> > > > > > http://lis
y: policy
>
>
> Thanks,
> Vamsi
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.
ailing list
> > neutron-...@lists.opendaylight.org
> > https://lists.opendaylight.org/mailman/listinfo/neutron-dev
> >
> >
>
>
> --
> Regards,
> Mike
> __
> OpenStack Development
ODL mech driver, then you don't need to run the test
> for networking-odl changes. I'd be hesitant to remove all tests
> though, it's a good investment of time to figure out which tests are
> valuable to you.
Mike and Michel should raise it at the PTG for di
k this issue:
>
> https://bugs.launchpad.net/networking-odl/+bug/1756132
>
>
>
> Thanks,
> Vamsi
--
Isaku Yamahata
__
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
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
--
Isaku Yamahata
__
arify your plans for cutting an
> Ocata release?
>
> Thanks,
> Armando
>
>
> > [1] https://releases.openstack.org/ocata/schedule.html
> > [2] https://review.openstack.org/#/c/428474/
> >
> ______
>
subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Isaku Yamahata
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack
1 - 100 of 103 matches
Mail list logo
