github.com/openstack/picasso
> [3]: https://github.com/openwhisk/openwhisk
>
> Cheers,
> Lingxian Kong (Larry)
>
> ______
> Open
t (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
_
00,reg7=0x17 actions=output:19
> cookie=0x0, duration=1710.877s, table=78, n_packets=0, n_bytes=0,
> idle_age=1710, priority=100,reg7=0x15 actions=output:13
> cookie=0x0, duration=1710.876s, table=78, n_packets=0, n_bytes=0,
> idle_age=1710, priority=100,reg7=0x1a actions=output:15
>
ck/dragonflow/blob/master/dragonflow/tests/common/app_testing_objects.py
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
d you guys provide some hints on the logic about it and how to get
rid of it? I just guess it is not a bug, maybe some configuration
tuning. When I went through the codes, I couldn't find the problems.
Thanks a lot,
--
Li Ma (Nick)
Email: skywalker
tiple nodes.
Best regards,
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Hi Sean
I'm very interested in this topic, but I missed the discussion during summit.
AFAIK, when deploying OVS-dpdk, it seems transparent to DVR. The only
thing we need to do
is to switch from OVS firewall-driver to OVS-dpdk-firewall-driver.
Do you have any outputs about the integration? Is ther
Hi all,
I will have a tight schedule during design summit. I'd like to know
about the arrangement in Apr 28-29. So, I can try to re-schedule to
fit for the arrangement if needed.
Thanks,
--
Li Ma (Nick)
Email: skywalker.n...@gmai
2016年2月24日星期三,Gal Sagie > 写道:
> Hi Li Ma,
>
> Great job on this!
>
> I think Rally is the correct way to test something like that, what you
> could use to check the end to end
> solution is try to restart the DF DB server for timeouts during API
> configurations.
&
Congrats ;-)
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
here.
Any thoughts? Thanks a lot.
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Hi Gal, you reverted this patch [1] due to the broken pipeline. Could
you provide some debug information or detailed description? When I run
my devstack, I cannot reproduce the sync problem.
[1]
https://github.com/openstack/dragonflow/commit/f83dd5795d54e1a70b8bdec1e6dd9f7815eb6546
--
Li Ma
Thanks for your suggestion, Gal.
On Mon, Dec 28, 2015 at 8:04 PM, Gal Sagie wrote:
> Hi Li Ma,
>
> I think its a good idea.
> I suggest for first stage, pass the CONF as optional parameter in addition
> to the db_ip and db_port.
> This way you will have minimum code chan
!
>
>
> At 2015-12-25 19:07:10, "Li Ma" wrote:
>>Hi all, currently, we only support db_ip and db_port in the
>>configuration file. Some DB SDK supports clustering, like Zookeeper.
>>You can specify a list of nodes when client application starts to
>>conn
ip2:port', 'ip3:port'] list in the configuration file. If only one
server exists, just set it to ['ip1:port'].
Any suggestions?
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Deve
if I just bind router0:port0 to physical nic: eth0, and don't
do the uplink bridge and veth pair stuff. Can it work?
[1]
https://docs.midonet.org/docs/v2015.06/en/operations-guide/content/static_setup.html
--
Li Ma (Nick)
Email: skyw
Updated:
Lots of ARP requests from external physical router to VM are catched
on the physical NIC binded to provider router port.
It seems that external physical router doesn't get answers to these
ARP requests.
On Wed, Dec 16, 2015 at 8:08 PM, Li Ma wrote:
> Hi Midoers,
>
> I h
27;m in the business trip that cannot touch the environment.
So, I'd like to get some ideas first and then I can tell my partners
to work on it.)
Thanks a lot,
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
Open
x27;t support syncing the full Neutron DB, there has
>> been work done for this that would allow this use case, but it's still
>> not complete or released.
>>
>> @Ryu may be able to provide recommendations to do this following a
>> manual process.
>>
>> Ch
f
>
> Best Regards,
> Soichi Shigeta
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack
- Nodir
>
> [1]
> http://docs.openstack.org/cli-reference/content/neutron-debug_commands.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>
Thanks for your reply, Gus. That's awesome. I'd like to have a look at
it or test if possible.
Any source code available in the upstream?
On Fri, Sep 18, 2015 at 12:40 PM, Angus Lees wrote:
> On Fri, 18 Sep 2015 at 14:13 Li Ma wrote:
>>
>> Hi stackers,
>>
>
in the Liberty cycle. I just wonder how it is going on.
[1] https://bugs.launchpad.net/neutron/+bug/1492714
Thanks a lot,
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage
t; certain features in Neutron (For example, the OVS ARP responder).
>
> On Thu, Sep 17, 2015 at 4:17 AM, Gal Sagie wrote:
>>
>> Hello Li Ma,
>>
>> Dragonflow uses OpenFlow1.3 to communicate with OVS and thats why we need
>> OVS 2.3.1.
>> As suggested you c
A reasonable user story. Other than tag, a common description field
for Neutron resources is also usable.
I submitted a RFE bug for review:
https://bugs.launchpad.net/neutron/+bug/1496705
__
OpenStack Development Mailing List
r thoughts.
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-b
?
Thanks,
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
which bridge to use.
(2) Let Neutron decide interface name (tap-xxx) and bridge name
(brq-xxx), not Nova. As a result, when creating port, Neutron return
interface name and bridge name to Nova, so Nova has the right device
name to process. This helps Nova get rid of hard-code, but need lots
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstac
enstack.org/172062
[4] https://review.openstack.org/172063
Best regards,
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
it a/test-requirements-py3.txt b/test-requirements-py3.txt
>> > index 937c9f2..f137195 100644
>> > --- a/test-requirements-py3.txt
>> > +++ b/test-requirements-py3.txt
>> > @@ -16 +16 @@ testtools>=0.9.36,!=1.2.0
>> > -oslotest>=1.2.0 # Apache-2.0
&
https://review.openstack.org/172045
On Thu, Apr 9, 2015 at 9:21 PM, Li Ma wrote:
> Hi Doug,
>
> In the global requirements.txt, oslo.messaging version is still >=
> 1.8.0 but < 1.9.0. As a result, some bugs fixed in 1.9.0 are still
> there when I deploy with devstack
ts.txt b/test-requirements.txt
> index 0b2a583..5afaa74 100644
> --- a/test-requirements.txt
> +++ b/test-requirements.txt
> @@ -16 +16 @@ testtools>=0.9.36,!=1.2.0
> -oslotest>=1.2.0 # Apache-2.0
> +oslotest>=1.5.1,<1.6.0 # Apache-2.0
> @@ -34 +34 @@ sphinx>=1.1.2,!=
nicely matches for CALL.
> However CAST can also be implemented over REQ/REP, using
> reply as message delivery acknowledgement, but not returning it to caller.
> Listening to reply for CAST in background thread keeps it async as well.
>
> Regards,
> Oleksii Zamiatin
>
>
> On 3
in my lab, and it works well.
I know there's another blueprint for REP/REQ pattern [1], but it's not
the same, I think.
I'd like to discuss it about how to take advantage of REP/REQ of zeromq.
[1] https://review.openstack.org/#/c/154094/2/specs/kilo/zmq-req-rep-call.rst
Best regar
>> As for me, I like the idea of separate repo for zmq driver because it
>> gives more freedom for driver extension.
>> There are some ideas that we can have more than a single zmq driver
>> implementation in future.
>> At least we may have different versions one for HA a
ixed online meeting for
zmq driver.
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
htt
.
Actually I'm not sure whether it is suitable to call it a 'subgroup'.
Besides, if it is possible, we need to figure out the suitable meeting
time and irc channel. Please give advice.
Best regards,
--
Li Ma (Nick)
Email: skywalker
On Tue, Mar 10, 2015 at 8:14 PM, ozamiatin wrote:
> Hi Li Ma,
>
> Thank you very much for your reply
>
> It's good to hear you have a living deployment with zmq driver.
> Is there a big divergence between your production and upstream versions
> of the driver? Besides [
lcome to update it [4].
[1] https://review.openstack.org/#/c/152471/
[2] https://review.openstack.org/#/c/155673/
[3] https://review.openstack.org/#/c/130943/
[4] https://wiki.openstack.org/wiki/ZeroMQ
Thanks a lot,
Li Ma (Nick)
Thanks!
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Li Ma (Nick)
Email: skywalker.n...@gmail.com
equ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: opens
On 2014/12/9 22:07, Doug Hellmann wrote:
On Dec 8, 2014, at 11:25 PM, Li Ma wrote:
Hi all, I tried to deploy zeromq by devstack and it definitely failed with lots
of problems, like dependencies, topics, matchmaker setup, etc. I've already
registered a blueprint for devstack-zeromq [1
On 2014/12/9 22:07, Doug Hellmann wrote:
On Dec 8, 2014, at 11:25 PM, Li Ma wrote:
Hi all, I tried to deploy zeromq by devstack and it definitely failed with lots
of problems, like dependencies, topics, matchmaker setup, etc. I've already
registered a blueprint for devstack-zeromq [1
with ZeroMQ. The general sections may be [Why ZeroMQ],
[Current Bugs & Reviews], [Future Plan & Blueprints], [Discussions],
[Resources], etc.
Any comments?
[1] https://blueprints.launchpad.net/devstack/+spec/zeromq
cheers,
Li Ma
On 2014/11/18 21:46, James Page wrote:
-BEGIN PGP S
Hi Yatin,
Thanks for sharing your presentation. That looks great. Welcome to
contribute to ZeroMQ driver.
Cheers,
Li Ma
On 2014/11/19 12:50, yatin kumbhare wrote:
Hello Folks,
Couple of slides/diagrams, I documented it for my understanding way
back for havana release. Particularly slide
On 2014/11/19 1:49, Eric Windisch wrote:
I think for this cycle we really do need to focus on consolidating and
testing the existing driver design and fixing up the biggest
deficiency (1) before we consider moving forward with lots of new
+1
1) Outbound messaging connection r
, we'd first initialize CI for ZeroMQ. After
that, we can work together on how to improve performance, reliability
and scalability of ZeroMQ driver.
cheers,
Li Ma
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.o
On 2014/11/17 22:26, Russell Bryant wrote:
On 11/17/2014 05:44 AM, Ilya Pekelny wrote:
Hi, all!
We want to discuss opportunity of implementation of the p-2-p messaging
model in oslo.messaging for ZeroMQ driver.
On a related note, have you looked into AMQP 1.0 at all? I have been
hopeful about
L
reliable than REQ/REP. Do you have some idea or concern to improve the
reliability of the current model?
cheers,
Li Ma
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ny routing stack, like quagga or bird.
I've tested the second method. It works pretty well.
[1]
https://github.com/openstack/neutron/tree/master/neutron/services/l3_router/brocade
[2]
http://lists.openstack.org/pipermail/openstack-dev/2014-October/049150.html
cheers,
Li Ma
On 2014/11/1
deployment guide of ZeroMQ for oslo.messaging, which
is located at
https://github.com/li-ma/zmq-for-oslo
Do I need to issue a bug or propose a blueprint to trace and merge it to
oslo.messaging doc tree?
3) an analysis of what it would take to be able to run functional
tests for zeromq on our CI
could at
least invoke action by the driver team:
https://github.com/openstack/nova/blob/4ce3f55d169290015063131134f93fca236807ed/nova/tests/virt/test_ironic_api_contracts.py
Yes, it is necessary to make API consistent.
Cheers,
Li Ma
___
OpenStack-d
master_connection =
master_connection =
...
slave_connection =
slave_connection =
...
HOWEVER, I think it needs more investigation, so this is why I'd like to put it
in the mailing list in the early stage to raise some discussions in depth. I'm
not a Galera expert. I reall
Thanks for all the detailed analysis, Mike W, Mike B, and Roman.
For a production-ready database system, replication is a must I think. So, the
questions are which replication mode is suitable for OpenStack and which way is
suitable for OpenStack to improve performance and scalability of DB acc
ion method
for oslo.db that every project may happily takes advantage of it
without any code modification.
Moreover, I'd like to put it in the mailing list in advance to
make sure it is acceptable for oslo.db.
I'd appreciate any
I'd like to using iptables for port-forwarding, because it is simple and
straightforward.
I didn't notice the Tap-as-a-Service before, and it seems interesting.
Thanks,
Li Ma
- Original Message -
From: "Baohua Yang"
To: "OpenStack Development Mailing List
very important for operators
and end-users.
[1] https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding
[2] https://review.openstack.org/#/c/60512/
Thanks,
Li Ma
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
ed; try
restarting transaction') 'INSERT INTO ml2_port_bindings (port_id, host,
vnic_type, profile, vif_type, vif_details, driver, segment) VALUES (%s, %s, %s,
%s, %s, %s, %s, %s)' ('2f7996c2-7a60-4334-a71d-11e82285e272', '', 'normal',
"{'type&
(%s, %s, %s,
%s, %s, %s, %s, %s)' (...)
It seems that the transaction in the postcommit cannot be committed.
Thanks a lot,
Li Ma
- Original Message -
From: "Li Ma"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: 星期三, 2014年 6 月 25日 下午 6:21
ck wait exception is still
thrown.
Li Ma
- Original Message -
From: "Kevin Benton"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: 星期三, 2014年 6 月 25日 下午 4:59:26
Subject: Re: [openstack-dev] [Neutron ML2] Potential DB lock when developing
it
in order to make precommit and postcommit out of the db transaction? I think it
is perfect for those who develop mechanism driver and do not know well about
the functioning context of the whole ML2 plugin.
Thanks,
Li Ma
___
OpenStack-dev mailing lis
Hi xueyan,
You can do it by yourself via the following link:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Li Ma
- Original Message -
From: "l"
To: openstack-dev@lists.openstack.org
Sent: 星期一, 2014年 4 月 21日 上午 10:56:08
Subject: [openstack-dev] 退出邮件列表
您
ists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
---
cheers,
Li Ma
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Updated. I commented out the segment checking in _notify_port_updated of
ml2-plugin, and finally I can get port_update message on l2-agents.
Is there any side effect? It is working for me, but I'm not sure it is
the "real" solution.
thanks,
--
Misunderstanding. Just find out this message is sent to
notifications.info topic.
Anyway, is there any solution to get port_update_info from l2-agents?
Thanks,
Li Ma
On 3/17/2014 4:11 PM, Li Ma wrote:
> Hi stackers,
>
> I'm trying to extend the capability of port
nd segment here to prevent sending
port_update out?
In my situation, I run a devstack environment and the bound segment is
None by default. Actually, I need this message to be sent out in any
situations.
I'd appreciate any hints.
Thanks a lot,
--
---
cheers,
Li Ma
_
Hi all,
I'd like to extend port capability using ML2 binding:profile. I checked
the official docs and it seems that there's no guide for it.
Is there any CLI support for port binding:profile?
Or is there any development guide on how to set up "profile"?
-
7;s possible.
>
>
> Best regards,
> Miguel Ángel
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
cheers,
Li Ma
___
2014/1/16 NOTSU Arata :
> The question is, what criteria is appropriate for the purpose. The criteria
> being mentioned so far in the review are:
>
> 1. assigned to the interface attached to default gateway
> 2. being in the specified network (CIDR)
> 3. assigned to the specified interface
>(1
70 matches
Mail list logo