Re: [openstack-dev] [nova][searchlight] When do instances get removed from Searchlight?

2017-03-06 Thread Lei Zhang 
On Mon, Mar 6, 2017 at 1:21 AM, Matt Riedemann  wrote:

>
> So I'm wondering at what point instances stored in searchlight will be
> removed. Maybe there is already an answer to this and the searchlight team
> can just inform me. Otherwise we might need to think about data retention
> policies and how long a deleted instances will be stored in searchlight
> before it's removed. Again, I'm not sure if nova would control this or if
> it's something searchlight supports already.
>
>
Hi,

Currently Searchlight doesn't capture soft delete notifications and simply
remove instance from ES if real delete notification comes. If these two
kind of notifications can be distinguished we could fix this issue by
marking the document in the ES instead of removing it. And we also need to
capture some extra notifications like restore(suppose it exists) .

About data retention policies, I'm not sure if something like ttl to define
how long a deleted instance should be stored in searchlight is enough. I
know Nova has cli to purge the database about deleted instances, if there
are no notification emitted for these operations, it's impossible for
searchlight to know when these delete instances are removed.
__
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] [searchlight] Propose Zhenyu Zheng for Searchlight core

2016-11-01 Thread Lei Zhang 
+1 for me

On Thu, Oct 20, 2016 at 5:13 PM, Brian Rosmaita <
brian.rosma...@rackspace.com> wrote:

> +1 from me, I'll be happy to see Kevin on the core list.
>
> On 10/19/16, 10:10 AM, "McLellan, Steven"  wrote:
>
> Hi,
>
> I'd like to propose Zhenyu Zheng (Kevin_Zheng on IRC) for Searchlight
> core. While he's most active on Nova, he's also been very active on
> Searchlight both in commits and reviews during the Newton release and into
> Ocata on Searchlight. Kevin's participated during the weekly meetings and
> during the week, and his reviews have been very high quality as well as
> numerous. This would also help move towards have greater cross-project
> participation, especially with Nova.
>
> If anyone has any objections, let me know, otherwise I will add Kevin to
> the core list at the weekend.
>
> Thanks!
>
> Steve
>
>
> __
> 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
>
>
__
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] [kolla] Can Heka solve all the deficiencies in the current rsyslog implementation: was Re: [kolla] Introduction of Heka in Kolla

2016-01-24 Thread Lei Zhang 
Just FYI.

Docker support multi log driver now[0].

Version New Logging Drivers
1.6.0 json-file, syslog, none
1.7.0 journald
1.8.0 fluentd, gelf
1.9.0 awslogs

For the stdout from container, we can use gelf/syslog driver to forward.

[0] https://docs.docker.com/engine/reference/logging/overview/

On Fri, Jan 15, 2016 at 8:28 AM, Steven Dake (stdake) 
wrote:

> Eric,
>
> Comments inline.
>
> On 1/14/16, 3:31 AM, "Eric LEMOINE"  wrote:
>
> >On Wed, Jan 13, 2016 at 1:27 PM, Steven Dake (stdake) 
> >wrote:
> >> Eric,
> >
> >
> >Hi Steven
>
>
> Feel free to call me Steve
>
> >
> >
> >>
> >> Apologies for top post, not really sure where in this thread to post
> >>this
> >> list of questions as its sort of a change in topic so I changed the
> >> subject line :)
> >>
> >> 1.
> >> Somewhere I read when researching this Heka topic, that Heka cannot log
> >> all details from /dev/log.  Some services like mariadb for example don't
> >> log to stdout as I think Heka requires to operate correctly.  Would you
> >> mind responding on the question "Would Heka be able to effectively log
> >> every piece of information coming off the system related to OpenStack
> >>(our
> >> infrastructure services like ceph/mariadb/etc as well as the OpenStack
> >> services)?
> >
> >
> >My first reaction to this is: if we have services, such as mariadb,
> >that can only send their logs to syslog then let's continue using
> >Rsyslog.  And with Rsyslog we can easily store logs on the local
> >filesystem as well (your requirement #3 below).
>
> Rsyslog may be the best tool for this job.  I'll be looking to your POC to
> get a feel for the validity of that claim :)
>
> >
> >That being said, it appears that Heka supports reading logs from
> >/dev/log.  This can be done using the UdpInput plugin with "net" set
> >to "unixgram".  See
> > for the original
> >issue.  Heka also supports writing logs to files on the local
> >filesystem, through the FileOutput plugin.  We do not currently use
> >the UdpInput plugin, so we need to test it and see if it can work for
> >Kolla.  We will work on these tests, and report back to the list.
> >
> >
> >
> >> 2.
> >> Also, I want to make sure we can fix up the backtrace defeciency.
> >> Currently rsyslog doesn't log backtraces in python code.  Perhaps Sam or
> >> inc0 know the reason behind it, but I want to make sure we can fix up
> >>this
> >> annoyance, because backtraces are mightily important.
> >
> >
> >I've had a look on my AIO Kolla.  And I do see Python tracebacks in
> >OpenStack log files created by Rsyslog (in
> >/var/lib/docker/volumes/rsyslog/_data/nova/nova-api.log for example).
> >They're just on a single line, with "#012" used as the separator [*].
> >So they are hard to read, but they are there.  I think that is
> >consistent with what SamYaple and inc0 said yesterday on IRC.
> >
> >[*] This is related to Rsyslog's $EscapeControlCharactersOnReceive
> >setting. See
> ><
> http://www.rsyslog.com/doc/master/configuration/input_directives/rsconf1_
> >escapecontrolcharactersonreceive.html>.
> >
>
> Apparently the one-lining of the tracebacks is a new feature because of a
> bug fix in oslo.log that dims fixed for us.  So my original comments about
> missing backtraces was dated information from December.
>
> >
> >> 3.
> >> Also I want to make sure each node ends up with log files in a data
> >> container (or data volume or whatever we just recently replaced the data
> >> containers with) for all the services for individual node diagnostics.
> >> This helps fill the gap of the Kibana visualization and Elasticsearch
> >> where we may not have a perfect diagnostic solution at the conclusion of
> >> Mitaka and in need of individual node inspection of the logs.  Can Heka
> >>be
> >> made to do this?  Our rsyslog implementation does today, and its a hard
> >> requirement for the moment.  If we need some special software to run in
> >> addition to Heka, I could live with that.
> >
> >
> >That "special software" could be Rsyslog :)  Seriously, Rsyslog
> >provides a solution for getting logs from services that only log to
> >syslog.  We can also easily configure Rsyslog to write logs on the
> >local filesystem, as done in Kolla already today.  And using Heka we
> >can easily make Python tracebacks look good in Kibana.
> >
> >I would like to point out that our initial intent was not to remove
> >Rsyslog.  Our intent was to propose a scalable/decentralized log
> >processing architecture based on Heka running on each node, instead of
> >relying on a centralized Logstash instance.  Using Heka we eliminate
> >the need to deploy and manage a resilient Logstash/Redis cluster.  And
> >it is to be noted that Heka gives us a lot of flexibility.  In
> >particular, Heka makes it possible to collect logs from services that
> >don't speak syslog (RabbitMQ for example, whose logs are not currently
> >collected!).
>

Re: [openstack-dev] [kolla] Nominating Lei Zhang (Jeffrey Zhang in English) - jeffrey4l on irc

2016-01-19 Thread Lei Zhang 
Thank you all for the nominating and votes. I will try and maintain my
current level activity and make the Kolla better.

On Wed, Jan 20, 2016 at 12:13 PM, Steven Dake (stdake) <std...@cisco.com>
wrote:

> Lei,
>
> Looks like its unanimous in under 24 hours :)  Welcome to the Kolla core
> reviewer team!  I made the appropriate changes in gerrit.
>
> Regards
> -steve
>
>
> From: Steven Dake <std...@cisco.com>
> Reply-To: "openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> Date: Tuesday, January 19, 2016 at 1:26 AM
> To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org
> >
> Subject: [openstack-dev] [kolla] Nominating Lei Zhang (Jeffrey Zhang in
> English) - jeffrey4l on irc
>
> Hi folks,
>
> I would like to propose Lei Zhang for our core reviewer team.  Count this
> proposal as a +1 vote from me.  Lei has done a fantastic job in his reviews
> over the last 6 weeks and has managed to produce some really nice
> implementation work along the way.  He participates in IRC regularly, and
> has a commitment from his management team at his employer to work full time
> 100% committed to Kolla for the foreseeable future (although things can
> always change in the future :)
>
> Please vote +1 if you approve of Lei for core reviewer, or –1 if wish to
> veto his nomination.  Remember just one –1 vote is a complete veto, so if
> your on the fence, another option is to abstain from voting.
>
> I would like to change from our 3 votes required, as our core team has
> grown, to requiring a simple majority of core reviewers with no veto
> votes.  As we have 9 core reviewers, this means Lei requires 4 more  +1
> votes with no veto vote in the voting window to join the core reviewer team.
>
> I will leave the voting open for 1 week as is the case with our other core
> reviewer nominations until January 26th.  If the vote is unanimous or there
> is a veto vote before January 26th I will close voting.  I'll make
> appropriate changes to gerrit permissions if Lei is voted into the core
> reviewer team.
>
> Thank you for your time in evaluating Lei for the core review team.
>
> Regards
> -steve
>
>
> __
> 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
>
>


-- 
Jeffrey Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

2015-12-29 Thread Lei Zhang 
Great. I think we can use this PPA now.

On Wed, Dec 30, 2015 at 1:29 AM, Canonical Calendar <
james.p...@canonical.com> wrote:

>
>
> > On 29 Dec 2015, at 08:51, Thomas Goirand  wrote:
> >
> >> On 12/28/2015 05:16 PM, Steven Dake (stdake) wrote:
> >> Hey folks,
> >>
> >> I have received significant feedback that the lack of Ubuntu binary
> >> support is a problem for Kolla adoption.  Still, we had nobody to do the
> >> work, so we held off approving the blueprint.  There were other reasons
> >> such as:
> >>
> >>  * There is no delorean style repository for debian meaning we would
> >>always be installing Liberty with our Mitaka tree
> >
> > While its true that Canonical isn't providing packages between releases,
> > I am doing so in Debian: I do publish each and every beta releases of
> > OpenStack backported for Jessie on non-debian-official repositories.
>
> Actually Canonical does provide packages between releases for Ubuntu 14.04
> - the cloud archive is populated from the start of the Mitaka release cycle
> - the first Mitaka milestone is currently working through QA and testing
> but you can get early visibility using the following PPA:
>
> sudo add-apt-repository ppa:ubuntu-cloud-archive/mitaka-staging
>
> Cheers
>
> James
>
>
> >
> > If we get enough people working on the Debian packaging (which means:
> > more than just me right now...), then I may at some point be able to do
> > packaging from trunk as well. I already wrote the scripts in Jenkins to
> > do so, but what's blocking me is having enough time to do the 3rd party
> > and OpenStack libraries update.
> >
> > I would very much like if the Kolla project was reusing my work on the
> > Debian packaging. I would be very supportive of that, and will do as
> > much as I can to help.
> >
> > Currently, my packages work out of the box in Debian, and can be rebuilt
> > for Ubuntu Trusty. Upstream puppet also work out of the box. The only
> > thing, if you use Ubuntu, is to install a file in
> > /etc/facter/facts.d/os_package_type.txt containing
> > "os_package_type=debian" (to tell puppet that you're using Debian type
> > of packages on top of Ubuntu, which will influence package and service
> > naming, needed to handle the packaging differences in Nova, Neutron and
> > Horizon).
> >
> > Your thoughts?
> >
> > Cheers,
> >
> > Thomas Goirand (zigo)
> >
> >
> >
> __
> > 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
>
> __
> 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
>



-- 
Jeffrey Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

2015-12-29 Thread Lei Zhang 
Why the package is still the nova 12.0.0 rather than 13.0.0 ? [0]
Most the package is updated at Nov 9, 2015. But it is almost 2016 now.

[0]
http://ppa.launchpad.net/ubuntu-cloud-archive/mitaka-staging/ubuntu/pool/main/n/nova/

On Wed, Dec 30, 2015 at 1:29 AM, Canonical Calendar <
james.p...@canonical.com> wrote:

>
>
> > On 29 Dec 2015, at 08:51, Thomas Goirand  wrote:
> >
> >> On 12/28/2015 05:16 PM, Steven Dake (stdake) wrote:
> >> Hey folks,
> >>
> >> I have received significant feedback that the lack of Ubuntu binary
> >> support is a problem for Kolla adoption.  Still, we had nobody to do the
> >> work, so we held off approving the blueprint.  There were other reasons
> >> such as:
> >>
> >>  * There is no delorean style repository for debian meaning we would
> >>always be installing Liberty with our Mitaka tree
> >
> > While its true that Canonical isn't providing packages between releases,
> > I am doing so in Debian: I do publish each and every beta releases of
> > OpenStack backported for Jessie on non-debian-official repositories.
>
> Actually Canonical does provide packages between releases for Ubuntu 14.04
> - the cloud archive is populated from the start of the Mitaka release cycle
> - the first Mitaka milestone is currently working through QA and testing
> but you can get early visibility using the following PPA:
>
> sudo add-apt-repository ppa:ubuntu-cloud-archive/mitaka-staging
>
> Cheers
>
> James
>
>
> >
> > If we get enough people working on the Debian packaging (which means:
> > more than just me right now...), then I may at some point be able to do
> > packaging from trunk as well. I already wrote the scripts in Jenkins to
> > do so, but what's blocking me is having enough time to do the 3rd party
> > and OpenStack libraries update.
> >
> > I would very much like if the Kolla project was reusing my work on the
> > Debian packaging. I would be very supportive of that, and will do as
> > much as I can to help.
> >
> > Currently, my packages work out of the box in Debian, and can be rebuilt
> > for Ubuntu Trusty. Upstream puppet also work out of the box. The only
> > thing, if you use Ubuntu, is to install a file in
> > /etc/facter/facts.d/os_package_type.txt containing
> > "os_package_type=debian" (to tell puppet that you're using Debian type
> > of packages on top of Ubuntu, which will influence package and service
> > naming, needed to handle the packaging differences in Nova, Neutron and
> > Horizon).
> >
> > Your thoughts?
> >
> > Cheers,
> >
> > Thomas Goirand (zigo)
> >
> >
> >
> __
> > 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
>
> __
> 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
>



-- 
Jeffrey Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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] [nova][oslo][policy] oslo.policy adoption in Nova.

2015-09-08 Thread Lei Zhang 
The oslo.policy has a class method `from_dict` which can be helpful.
So I replaced the `parse_rule` with `from_dict`, and it works as expect.

Is there any other feature that oslo.policy doesn't have?



On Mon, Sep 7, 2015 at 6:48 PM, Sergey Vilgelm 
wrote:

> Hi nova-team,
>
> Jeffrey Zhang has updated his patch[1].
> Dan Smith, Could you remove -2?
>
> [1] https://review.openstack.org/#/c/198065
>
>
> On Aug 20, 2015, at 17:26, Sergey Vilgelm  wrote:
>
> Nova-cores,
> Do you have any decision about the patch:
> https://review.openstack.org/#/c/198065/ ?
> Dan Smith, Could you remove -2?
> Jeffrey Zhang, What is your opinion?
>
> On Tue, Aug 4, 2015 at 12:26 AM, Doug Hellmann  > wrote:
> Excerpts from Doug Hellmann's message of 2015-08-03 16:19:31 -0400:
> > Excerpts from Morgan Fainberg's message of 2015-08-04 06:05:56 +1000:
> > >
> > > > On Aug 4, 2015, at 05:49, Doug Hellmann 
> wrote:
> > > >
> > > > Excerpts from Sergey Vilgelm's message of 2015-08-03 22:11:50 +0300:
> > > >>> On Mon, Aug 3, 2015 at 9:37 PM, Doug Hellmann <
> d...@doughellmann.com> wrote:
> > > >>>
> > > >>> Making that function public may be the most expedient fix, but the
> > > >>> parser was made private for a reason, so before we expose it we
> > > >>> should understand why, and if there are alternatives (such as
> > > >>> creating a fixture in oslo.policy to do what the nova tests need).
> > > >>
> > > >> Probably we may extend the Rules class and add the similar
> functions as a
> > > >> classmethod?
> > > >> I've created a patch for slo.policy as example[1]
> > > >
> > > > Well, my point was that the folks working on that library considered
> the
> > > > entire parser to be private. That could just be overly ambitious API
> > > > pruning, or there could be some underlying reason (like, the syntax
> may
> > > > be changing or we want apps to interact with APIs and not generate
> DSL
> > > > and feed it to the library). So we should find out about the reason
> > > > before looking for alternative places to expose the parser.
> > > >
> > >
> > > The idea is to have apis vs dsl generation. But we did a "everything
> private that isnt clearly used" as a starting point. I would prefer to not
> make this public and have a fixture instead. That said, i am not hard-set
> against a change to make it public.
> >
> > It would be easy enough to provide a fixture, which would make it clear
> > that the API is meant for testing and not for general use. I see a
> > couple of options:
> >
> > 1. a fixture that takes some DSL text and creates a new Enforcer
> >instance populated with the rules based on parsing the text
> >
> > 2. a fixture that takes some DSL text *and* an existing Enforcer
> >instance and replaces the rules inside that Enforcer instance with the
> >rules represented by the DSL text
> >
> > Option 1 feels a little cleaner but option 2 is more like how Nova
> > is using parse_rule() now and may be easier to drop in.
>
> Brant also pointed out on IRC that the Rules class already has a
> load_json() class method that invokes the parser, so maybe the thing to
> do is update nova's tests to use that method. A fixture would still be
> an improvement, but using the existing code will let us move ahead
> faster (assuming we've decided not to wait for the new features to be
> implemented).
>
> Doug
>
> >
> > Doug
> >
> > >
> > > > Doug
> > > >
> > > >>
> > > >> [1] https://review.openstack.org/#/c/208617/
> > > >
> > > >
> __
> > > > 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
> > >
> >
>
> __
> 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
>
>
>
> --
> Thanks,
> Sergey Vilgelm
> OpenStack Software Engineer
> Mirantis Inc.
> Skype: sergey.vilgelm
> Phone: +36 70 512 3836
>
>
>
> —
> Sergey Vilgelm
> OpenStack Software Engineer
> Mirantis Inc.
>
>
> __
> 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
>
>


-- 
​Jeffrey
 Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] Why the the id can set when creating flavor.

2015-07-15 Thread Lei Zhang 
It is uncommon that the id can be set when creating resource.

Other resource can not, e.g. instance.

I want to know why this is happend only in flavor.  history logical or
something else?



-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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] [Nova] The security group is confused in the create server api

2015-05-13 Thread Lei Zhang 
Thank for your reply.

I read that thread, but it just throw a exception when using confused
params.

To solve this issue, is it worth to create a now micro version of api to
implement above cli?

On Wed, May 13, 2015 at 3:35 PM, Feodor Tersin fter...@cloudscaling.com
wrote:


 nova boot test --flavor m1.tiny --security_group ssh
 --security_group http --nic net-id=xxx --nic port-id=yyy

 Which port/nic the security group should bind to?  the first one? both?


 Both groups will be set to a new port of xxx network. A set of port yyy SG
 will not be changed.

 This question was discussed here recently:
 http://lists.openstack.org/pipermail/openstack-dev/2015-February/056339.html.
 See also https://review.openstack.org/#/c/154068/ with its comments.




 The legacy network will be removed and I think it is the time to change
 the API to satisfied the new situation. May be the new cli like below:

 nova boot test --flavor m1.tiny --nic
 net-id=xx,security_group=ssh  --nic port-id=y --nic
 net-id=,security_group=http,security_group=mysql


 I agree, API have to be more straightforward.


 __
 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




-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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

[openstack-dev] [Nova] The security group is confused in the create server api

2015-05-13 Thread Lei Zhang 
In the legency network, there only one nic. So it is OK and understandable
by using following cli.

nova boot test --flavor m1.tiny --security_group ssh --security_group
http --image cirros

The instance only have one network associate with several security groups.

But in Neutron Network, we can attach more than one network to the
instance. It will be confused using the following cli.

nova boot test --flavor m1.tiny --security_group ssh --security_group
http --nic net-id=xxx --nic port-id=yyy

Which port/nic the security group should bind to?  the first one? both?


The legacy network will be removed and I think it is the time to change the
API to satisfied the new situation. May be the new cli like below:

nova boot test --flavor m1.tiny --nic net-id=xx,security_group=ssh
 --nic port-id=y --nic
net-id=,security_group=http,security_group=mysql

Related Bug: https://bugs.launchpad.net/nova/+bug/1195720


-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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] [Openstack] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Lei Zhang 
I created project for the user admin(6433222efd78459bb70ad9adbcfac418).

The token horizon is past is a project scope token. So it can not passed
the cloud_admin rule.
I changed the rule to the admin_id is a little trick, and it works.

On Thu, Mar 12, 2015 at 5:16 PM, Trelohan Christophe 
ctrelo...@voyages-sncf.com wrote:

 Hello,

 Does user_id replaced in cloud_admin rule is id of cloud_admin user ?
 I don't think you can log in with cloud_admin user in horizon, it seems
 that without project created for an user, you can't log in
 in horizon.

 I'm also interested in this, I also followed the mentioned article, but
 when I try to login with admin user in default domain,
 I have the same error (not authorized to list_projects). Both with horizon
 and Rest API.




 De : Lei Zhang [mailto:zhang.lei@gmail.com]
 Envoyé : jeudi 12 mars 2015 03:33
 À : openstack; OpenStack Development Mailing List
 Objet : [Openstack] [Horizon][Keystone] Failed to set up keystone v3 api
 for horizon

 is there anyone tryed this and successfully?

 On Mon, Mar 9, 2015 at 4:25 PM, Lei Zhang zhang.lei@gmail.com wrote:
 Hi guys,

 I am setting up the keytone v3 api. Now I meet a issue about the
 `cloud_admin` policy.

 Base on the
 http://www.florentflament.com/blog/setting-keystone-v3-domains.html
 article, I modify the cloud_admin policy to

 ```
 cloud_admin: rule:admin_required and
 domain_id:ef0d30167f744401a0cbfcc938ea7d63,
 ```

 But the cloud_admin don't work as expected. I failed to open all the
 identity panel ( like http://host/horizon/identity/domains/)
 Horizon tell me Error: Unable to retrieve project list.
 And keystone log warning:

 ```
 2015-03-09 16:00:06.423 9415 DEBUG keystone.policy.backends.rules [-]
 enforce identity:list_user_projects: {'is_delegated_auth': False,
 'access_token_id': None, 'user_id': u'6433222efd78459bb70ad9adbcfac418',
 'roles': [u'_member_', u'admin'], 'trustee_id': None, 'trustor_id': None,
 'consumer_id': None, 'token': KeystoneToken
 (audit_id=DWsSa6yYSWi0ht9E7q4uhw, audit_chain_id=w_zLBBeFQ82KevtJrdKIJw) at
 0x7f4503fab3c8, 'project_id': u'4d170baaa89b4e46b239249eb5ec6b00',
 'trust_id': None}, enforce
 /usr/lib/python2.7/dist-packages/keystone/policy/backends/rules.py:100
 2015-03-09 16:00:06.061 9410 WARNING keystone.common.wsgi [-] You are not
 authorized to perform the requested action: identity:list_projects (Disable
 debug mode to suppress these details.)
 ```

 ​I make some debug and found that, the root cause is that the `context`
 variable in keystone has no `domain_id` field( like the above keystone
 log). So the `cloud_admin` rule failed.​ if i change the `cloud_admin` to
 following. It works as expected.

 ```
 cloud_admin: rule:admin_required and
 user_id:6433222efd78459bb70ad9adbcfac418,
 ```

 I found that in the keystone code[0], the domain_id only exist when it is
 a domain scope. But i believe that the horizon login token is a project
 one( I am not very sure this)

 ```
 if token.project_scoped:
 auth_context['project_id'] = token.project_id
 elif token.domain_scoped:
 auth_context['domain_id'] = token.domain_id
 else:
 LOG.debug('RBAC: Proceeding without project or domain scope')

 ```

 Is it a bug? or some wrong configuration?


 Following is my configuration.


 ```
 # /etc/keystone/keystone.conf
 [DEFAULT]
 debug=true
 verbose=true
 log_dir=/var/log/keystone
 [assignment]
 driver = keystone.assignment.backends.sql.Assignment
 [database]
 connection=mysql://:@controller/keystone
 [identity]
 driver=keystone.identity.backends.sql.Identity
 [memcache]
 servers=controller1:11211,controller2:11211,controller3:1121
 [token]
 provider=keystone.token.providers.uuid.Provider
 ```

 ```
 # /etc/openstack-dashboard/local_settings.py ( partly )
 POLICY_FILES_PATH = /etc/openstack-dashboard/
 POLICY_FILES = {
 'identity': 'keystone_policy.json',
 }
 OPENSTACK_HOST = 127.0.0.1
 OPENSTACK_KEYSTONE_URL = http://%s:5000/v3; % OPENSTACK_HOST
 OPENSTACK_KEYSTONE_DEFAULT_ROLE = _member_
 OPENSTACK_API_VERSIONS = {
  data_processing: 1.1,
  identity: 3,
  volume: 2
 }
 OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = True
 OPENSTACK_KEYSTONE_DEFAULT_DOMAIN = 'admin'
 ```

 ​[0]
 https://github.com/openstack/keystone/blob/master/keystone/common/authorization.py#L58
 ​

 --
 Lei Zhang
 Blog: http://xcodest.me
 twitter/weibo: @jeffrey4l




 --
 Lei Zhang
 Blog: http://xcodest.me
 twitter/weibo: @jeffrey4l




-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Lei Zhang 
Hi Lin,

This two PS is what I wanted. Thx a lot.

btw, is it possible that these PS finished in Kilo?

On Thu, Mar 12, 2015 at 5:41 PM, Lin Hua Cheng os.lch...@gmail.com wrote:

 Hi,

 The 'cloud_admin' policy file requires domain-scoped to work to work.

 Horizon does not currently support domain scope token yet. So yes, it is a
 gap in horizon at the moment.

 There are on-going patches to address this in horizon:
 - https://review.openstack.org/#/c/141153/
 - https://review.openstack.org/#/c/148082/

 Dan (esp) prepared a nicely written document on this should eventually
 work.

 -Lin

 On Wed, Mar 11, 2015 at 7:33 PM, Lei Zhang zhang.lei@gmail.com
 wrote:

 is there anyone tryed this and successfully?

 On Mon, Mar 9, 2015 at 4:25 PM, Lei Zhang zhang.lei@gmail.com
 wrote:

 Hi guys,

 I am setting up the keytone v3 api. Now I meet a issue about the
 `cloud_admin` policy.

 Base on the
 http://www.florentflament.com/blog/setting-keystone-v3-domains.html
 article, I modify the cloud_admin policy to

 ```
 cloud_admin: rule:admin_required and
 domain_id:ef0d30167f744401a0cbfcc938ea7d63,
 ```

 But the cloud_admin don't work as expected. I failed to open all the
 identity panel ( like http://host/horizon/identity/domains/)
 Horizon tell me Error: Unable to retrieve project list.
 And keystone log warning:

 ```
 2015-03-09 16:00:06.423 9415 DEBUG keystone.policy.backends.rules [-]
 enforce identity:list_user_projects: {'is_delegated_auth': False,
 'access_token_id': None, 'user_id': u'6433222efd78459bb70ad9adbcfac418',
 'roles': [u'_member_', u'admin'], 'trustee_id': None, 'trustor_id': None,
 'consumer_id': None, 'token': KeystoneToken
 (audit_id=DWsSa6yYSWi0ht9E7q4uhw, audit_chain_id=w_zLBBeFQ82KevtJrdKIJw) at
 0x7f4503fab3c8, 'project_id': u'4d170baaa89b4e46b239249eb5ec6b00',
 'trust_id': None}, enforce
 /usr/lib/python2.7/dist-packages/keystone/policy/backends/rules.py:100
 2015-03-09 16:00:06.061 9410 WARNING keystone.common.wsgi [-] You are
 not authorized to perform the requested action: identity:list_projects
 (Disable debug mode to suppress these details.)
 ```

 ​I make some debug and found that, the root cause is that the `context`
 variable in keystone has no `domain_id` field( like the above keystone
 log). So the `cloud_admin` rule failed.​ if i change the `cloud_admin` to
 following. It works as expected.

 ```
 cloud_admin: rule:admin_required and user_id:
 6433222efd78459bb70ad9adbcfac418,
 ```

 I found that in the keystone code[0], the domain_id only exist when it
 is a domain scope. But i believe that the horizon login token is a project
 one( I am not very sure this)

 ```
 if token.project_scoped:
 auth_context['project_id'] = token.project_id
 elif token.domain_scoped:
 auth_context['domain_id'] = token.domain_id
 else:
 LOG.debug('RBAC: Proceeding without project or domain scope')

 ```

 Is it a bug? or some wrong configuration?


 Following is my configuration.


 ```
 # /etc/keystone/keystone.conf
 [DEFAULT]
 debug=true
 verbose=true
 log_dir=/var/log/keystone
 [assignment]
 driver = keystone.assignment.backends.sql.Assignment
 [database]
 connection=mysql://:@controller/keystone
 [identity]
 driver=keystone.identity.backends.sql.Identity
 [memcache]
 servers=controller1:11211,controller2:11211,controller3:1121
 [token]
 provider=keystone.token.providers.uuid.Provider
 ```

 ```
 # /etc/openstack-dashboard/local_settings.py ( partly )
 POLICY_FILES_PATH = /etc/openstack-dashboard/
 POLICY_FILES = {
 'identity': 'keystone_policy.json',
 }
 OPENSTACK_HOST = 127.0.0.1
 OPENSTACK_KEYSTONE_URL = http://%s:5000/v3; % OPENSTACK_HOST
 OPENSTACK_KEYSTONE_DEFAULT_ROLE = _member_
 OPENSTACK_API_VERSIONS = {
  data_processing: 1.1,
  identity: 3,
  volume: 2
 }
 OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = True
 OPENSTACK_KEYSTONE_DEFAULT_DOMAIN = 'admin'
 ```

 ​[0]
 https://github.com/openstack/keystone/blob/master/keystone/common/authorization.py#L58
 ​

 --
 Lei Zhang
 Blog: http://xcodest.me
 twitter/weibo: @jeffrey4l




 --
 Lei Zhang
 Blog: http://xcodest.me
 twitter/weibo: @jeffrey4l

 __
 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



 __
 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




-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http

[openstack-dev] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-11 Thread Lei Zhang 
is there anyone tryed this and successfully?

On Mon, Mar 9, 2015 at 4:25 PM, Lei Zhang zhang.lei@gmail.com wrote:

 Hi guys,

 I am setting up the keytone v3 api. Now I meet a issue about the
 `cloud_admin` policy.

 Base on the
 http://www.florentflament.com/blog/setting-keystone-v3-domains.html
 article, I modify the cloud_admin policy to

 ```
 cloud_admin: rule:admin_required and
 domain_id:ef0d30167f744401a0cbfcc938ea7d63,
 ```

 But the cloud_admin don't work as expected. I failed to open all the
 identity panel ( like http://host/horizon/identity/domains/)
 Horizon tell me Error: Unable to retrieve project list.
 And keystone log warning:

 ```
 2015-03-09 16:00:06.423 9415 DEBUG keystone.policy.backends.rules [-]
 enforce identity:list_user_projects: {'is_delegated_auth': False,
 'access_token_id': None, 'user_id': u'6433222efd78459bb70ad9adbcfac418',
 'roles': [u'_member_', u'admin'], 'trustee_id': None, 'trustor_id': None,
 'consumer_id': None, 'token': KeystoneToken
 (audit_id=DWsSa6yYSWi0ht9E7q4uhw, audit_chain_id=w_zLBBeFQ82KevtJrdKIJw) at
 0x7f4503fab3c8, 'project_id': u'4d170baaa89b4e46b239249eb5ec6b00',
 'trust_id': None}, enforce
 /usr/lib/python2.7/dist-packages/keystone/policy/backends/rules.py:100
 2015-03-09 16:00:06.061 9410 WARNING keystone.common.wsgi [-] You are not
 authorized to perform the requested action: identity:list_projects (Disable
 debug mode to suppress these details.)
 ```

 ​I make some debug and found that, the root cause is that the `context`
 variable in keystone has no `domain_id` field( like the above keystone
 log). So the `cloud_admin` rule failed.​ if i change the `cloud_admin` to
 following. It works as expected.

 ```
 cloud_admin: rule:admin_required and user_id:
 6433222efd78459bb70ad9adbcfac418,
 ```

 I found that in the keystone code[0], the domain_id only exist when it is
 a domain scope. But i believe that the horizon login token is a project
 one( I am not very sure this)

 ```
 if token.project_scoped:
 auth_context['project_id'] = token.project_id
 elif token.domain_scoped:
 auth_context['domain_id'] = token.domain_id
 else:
 LOG.debug('RBAC: Proceeding without project or domain scope')

 ```

 Is it a bug? or some wrong configuration?


 Following is my configuration.


 ```
 # /etc/keystone/keystone.conf
 [DEFAULT]
 debug=true
 verbose=true
 log_dir=/var/log/keystone
 [assignment]
 driver = keystone.assignment.backends.sql.Assignment
 [database]
 connection=mysql://:@controller/keystone
 [identity]
 driver=keystone.identity.backends.sql.Identity
 [memcache]
 servers=controller1:11211,controller2:11211,controller3:1121
 [token]
 provider=keystone.token.providers.uuid.Provider
 ```

 ```
 # /etc/openstack-dashboard/local_settings.py ( partly )
 POLICY_FILES_PATH = /etc/openstack-dashboard/
 POLICY_FILES = {
 'identity': 'keystone_policy.json',
 }
 OPENSTACK_HOST = 127.0.0.1
 OPENSTACK_KEYSTONE_URL = http://%s:5000/v3; % OPENSTACK_HOST
 OPENSTACK_KEYSTONE_DEFAULT_ROLE = _member_
 OPENSTACK_API_VERSIONS = {
  data_processing: 1.1,
  identity: 3,
  volume: 2
 }
 OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = True
 OPENSTACK_KEYSTONE_DEFAULT_DOMAIN = 'admin'
 ```

 ​[0]
 https://github.com/openstack/keystone/blob/master/keystone/common/authorization.py#L58
 ​

 --
 Lei Zhang
 Blog: http://xcodest.me
 twitter/weibo: @jeffrey4l




-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
__
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] [keystone] Using 'admin_token' option as token to create keystone client.

2014-10-09 Thread Lei Zhang 
it should works but it is not safe to use admin_token. Because
* It is a admin token which has the full privilege for the keystone service
* The token will be always valid till the admin_token in the conf file
is changed.
  It is dangerous when the token leak.

Suggest that the admin_token is only used for the initial of admin account.

On Thu, Oct 9, 2014 at 2:29 PM, Nader Lahouti nader.laho...@gmail.com wrote:
 Hi,

 Is it acceptable to use 'admin_token' option from keystone.conf,  when
 creating a keystone client? something like this:

 kc = client.Client(token=cfg.CONF.admin_token,

endpoint='http://localhost:35357/v2.0/')




 Thanks,

 Nader.



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




-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l

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

Re: [openstack-dev] [keystone] Using 'admin_token' option as token to create keystone client.

2014-10-09 Thread Lei Zhang 
Yes. That will be more safer.

On Fri, Oct 10, 2014 at 12:00 AM, Nader Lahouti nader.laho...@gmail.com wrote:
 Thanks Lei for the reply and clarification.
 So, instead of that we can use the following:


 from keystone client.v2_0 import Client

 keystone = Client(username=user, password=password, tenant_name=tenant,
 auth_url=url)


 with user, password, tenant and url can be obtained from cfg.CONF.


 Thanks,

 Nader.


 On Wed, Oct 8, 2014 at 11:54 PM, Lei Zhang zhang.lei@gmail.com wrote:

 it should works but it is not safe to use admin_token. Because
 * It is a admin token which has the full privilege for the keystone
 service
 * The token will be always valid till the admin_token in the conf file
 is changed.
   It is dangerous when the token leak.

 Suggest that the admin_token is only used for the initial of admin
 account.

 On Thu, Oct 9, 2014 at 2:29 PM, Nader Lahouti nader.laho...@gmail.com
 wrote:
  Hi,
 
  Is it acceptable to use 'admin_token' option from keystone.conf,  when
  creating a keystone client? something like this:
 
  kc = client.Client(token=cfg.CONF.admin_token,
 
 endpoint='http://localhost:35357/v2.0/')
 
 
 
 
  Thanks,
 
  Nader.
 
 
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 



 --
 Lei Zhang
 Blog: http://xcodest.me
 twitter/weibo: @jeffrey4l

 ___
 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




-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l

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

[openstack-dev] [Zaqar] How to get the pool list in graceful way.

2014-10-08 Thread Lei Zhang 
The question comes from my patch[1]. Kgriffs point that there are two
way to get all the pools. But I don’t know which one is better, event
though I comment that limit=0 is wired. I think there are three ways.

use limit=0( current logical).
pro: 1) may easy to implement
con: 1) not clearly and wired. 2) may some storage driver doesn’t support?
call .list multiple times
pro: 1) directly and compatiblely
con: 1) multiple request must make when the list size is too large.
define a new method named list_all

[1] https://review.openstack.org/#/c/123462/5/zaqar/queues/storage/pooling.py

-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l

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

Re: [openstack-dev] [Cinder] Does cinder support HDS AMS 2300 storage now?

2013-11-21 Thread Lei Zhang 
Did you test on it?
That's meaning the CLI on both AMS and HUS are the same? Right?


On Fri, Nov 22, 2013 at 4:14 AM, Steven Sonnenberg 
steven.sonnenb...@hds.com wrote:

   On *Thu Nov 21 03:32:10 UTC 2013, Lei asked:*

 I just found the HUS is supported. But I have a old AMS storage machine
 and want to use it.

 So I want to make sure is it possible?

 The answer is that both AMS and HUS arrays are supported.



 Steve Sonnenberg

 Master Solutions Consultant

 Hitachi Data Systems

 Cell: 443-929-6543



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




-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Cinder] Does cinder support HDS AMS 2300 storage now?

2013-11-20 Thread Lei Zhang 
I just found the HUS is supported. But I have a old AMS storage machine and
want to use it.
So I want to make sure is it possible?

-- 
Lei Zhang
Blog: http://xcodest.me
twitter/weibo: @jeffrey4l
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] what's the filter_properties looks like in nova scheduler?

2013-11-11 Thread Lei Zhang 
hi guys, where can I find more info about filter_properties variable
definition? How the dict looks like?

-- 
Lei Zhang

Blog: http://jeffrey4l.github.io
twitter/weibo: @jeffrey4l
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Propose Liang Chen for heat-core

2013-08-25 Thread Lei Zhang 
+1 from me


On Sat, Aug 24, 2013 at 4:07 AM, Steven Dake sd...@redhat.com wrote:

 On 08/22/2013 08:57 AM, Steven Hardy wrote:

 Hi,

 I'd like to propose that we add Liang Chen to the heat-core team[1]

 Liang has been doing some great work recently, consistently providing good
 review feedback[2][3], and also sending us some nice patches[4][5],
 implementing
 several features and fixes for Havana.

 Please respond with +1/-1.

 Thanks!

 [1] 
 https://wiki.openstack.org/**wiki/Heat/CoreTeamhttps://wiki.openstack.org/wiki/Heat/CoreTeam
 [2] 
 http://russellbryant.net/**openstack-stats/heat-**reviewers-90.txthttp://russellbryant.net/openstack-stats/heat-reviewers-90.txt
 [3] https://review.openstack.org/#**/q/reviewer:cbjchen@linux.**
 vnet.ibm.com,n,zhttps://review.openstack.org/#/q/reviewer:cbjc...@linux.vnet.ibm.com,n,z
 [4] https://github.com/openstack/**heat/graphs/contributors?from=**
 2013-04-18to=2013-08-18type=**chttps://github.com/openstack/heat/graphs/contributors?from=2013-04-18to=2013-08-18type=c
 [5] https://review.openstack.org/#**/q/owner:cbjc...@linux.vnet.**
 ibm.com,n,zhttps://review.openstack.org/#/q/owner:cbjc...@linux.vnet.ibm.com,n,z

 +1 from me.

  __**_
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.**org OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-devhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __**_
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.**org OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-devhttp://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