Re: [openstack-dev] [telemetry] [ceilometer] [kilo] trouble reloading ceilometer pipeline

changing pipeline only requires restart ceilometer-agent-compute or ceilometer-agent-central service, no need to restart nova-compute or ceilometer-collector the question is not suitable for dev mailing list, and you have provided too less info: * what change do you made? paste the diff * what do

Re: [openstack-dev] [aodhclient] does the aodh have the feature for import/export batch alarms?

batch alarm is not supported, and I think it is a burden instead of good feature to implement it in aodh import/export alarm is not supported, considering dump db and restore it in new env? or you can get alarm list from old env and create new alarm in new env via REST API if data set is not too l

Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

Alarm name unique constraint is only applied to each project, I don't remember the original cause, but in our customer's environment, alarm will be showed in the portal, with their name, no uuid, because user will be confused about such a random like string, then if alarm name can be duplicated, it

Re: [openstack-dev] [Nova] Libvirt version requirement

Glad to hear the news. Thanks, Daniel and Michael. On Tue, May 3, 2016 at 5:19 PM, Daniel P. Berrange wrote: > On Mon, May 02, 2016 at 11:27:01AM +0800, ZhiQiang Fan wrote: > > Hi Nova cores, > > > > There is a spec[1] submitted to Telemetry project for Newton release, >

[openstack-dev] [Nova] Libvirt version requirement

c/311655/ Thanks! ZhiQiang Fan __ 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] [Ceph][ceilometer][libvirt] Libvirt error during instance disk allocation metering

Hi Ceph devs, I raise this bug again because as Ceph becomes more popular, our customer suffers from it and I have no solution for it. *Is there anyway to get the usage of a disk which is a Ceph volume? (Not sure if the term is right or not)* Ceilometer use libvirt.domain.blockInfo(device) to ge

Re: [openstack-dev] Devstack liberty with keystone v3

enstack catalog list`` ? On Wed, Apr 27, 2016 at 1:34 AM, kiran vemuri UH wrote: > Hello Sean, > > I tried doing what you suggested and what ZhiQiang Fan suggested as > well. > > But both of them give me similar error when I try to fetch keystone > catalog. > > DE

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

ble. Yes, the config changes should be picked up automatically. You > can't edit those files in the book directly, as a script writes them. > That's why your change would have been declined. > > Thanks for asking the question, though :) > > L > > On 24/04

Re: [openstack-dev] Devstack liberty with keystone v3

what you need is this patch: https://review.openstack.org/#/c/307574/ after install finished, to use admin:demo account and v3 API, run ``source openrc -k3 admin``, then it is done. Cheers! On Tue, Apr 26, 2016 at 7:10 AM, kiran vemuri UH wrote: > Hello All, > > I recently got started with Ope

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

Thank you, Sir! On Mon, Apr 25, 2016 at 2:25 AM, Andreas Jaeger wrote: > On 04/24/2016 11:12 AM, ZhiQiang Fan wrote: > >> Hi Lana, >> >> Thank you for explaining it! >> >> Yes, I noticed that the DocImpact bug track now has shifted to project >> its ow

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

> Does that answer your question? > > Thanks, > Lana > > On 23/04/16 19:00, ZhiQiang Fan wrote: > > Hi Doc Team, > > > > I want to know the recent status of DocImpact tag, is it deprecated for > config option changes now? If it's true, then what the workflow fo

Re: [openstack-dev] [openstack-manuals] What the status of DocImpact

est merged patch in > openstack-manuals > > and found what he said is true, but still don't know why and what action > I > > should follow in Ceilometer/Aodh projects > > > > Thank you very much! > > > > ZhiQiang Fan > > I recom

[openstack-dev] [openstack-manuals] What the status of DocImpact

hange is not needed any more, I searched latest merged patch in openstack-manuals and found what he said is true, but still don't know why and what action I should follow in Ceilometer/Aodh projects Thank you very much! Zh

[openstack-dev] [Telemetry][Ceilometer][Aodh] Clean crazy old bugs and patches

Hi devs, Recently I'm cleaning bugs and reviews of Ceilometer+Aodh, some out dated bugs, long time (two months) no active reviews, assignments will be removed. If you are the owner or just interest in it, please provide new information or follow ups, to let them alive again. Thanks, ZhiQian

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Thanks for the confirm. On Thu, Apr 21, 2016 at 7:44 PM, Andreas Jaeger wrote: > On 2016-04-21 13:22, ZhiQiang Fan wrote: > > Hi Andreas, > > > > so if some projects, such as ceilometer, need babel even if they don't > > directly depend on it, just bec

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

+1 more example and documentation are welcomed On Tue, Apr 19, 2016 at 3:10 AM, John Griffith wrote: > > > On Thu, Apr 14, 2016 at 1:31 AM, Markus Zoeller > wrote: > >> Sometimes (especially when I try to reproduce bugs) I have the need >> to set up a local environment with devstack. Everytime

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Hi Andreas, so if some projects, such as ceilometer, need babel even if they don't directly depend on it, just because they are setup in infra for translations? can you explain a bit more to me, or just provide some links, or keywords for search ? Thanks ZhiQiang On Tue, Apr 19, 2016 at 2:34 PM

Re: [openstack-dev] [keystone][barbican][designate][murano][fuel][ironic][cue][ceilometer][astara][gce-api][kiloeyes] keystoneclient 3.0.0 release - no more CLI!

barbican fix: https://review.openstack.org/#/c/247810/ but no patch update since Nov 20 On Tue, Apr 19, 2016 at 7:59 AM, ZhiQiang Fan wrote: > ironic fix: https://review.openstack.org/307523 > > On Tue, Apr 19, 2016 at 7:50 AM, ZhiQiang Fan wrote: > >> cei

Re: [openstack-dev] [keystone][barbican][designate][murano][fuel][ironic][cue][ceilometer][astara][gce-api][kiloeyes] keystoneclient 3.0.0 release - no more CLI!

ironic fix: https://review.openstack.org/307523 On Tue, Apr 19, 2016 at 7:50 AM, ZhiQiang Fan wrote: > ceilometer fix: https://review.openstack.org/307521 > > On Tue, Apr 19, 2016 at 4:05 AM, Steve Martinelli > wrote: > >> Everyone, >> >> I sent out a note a

Re: [openstack-dev] [keystone][barbican][designate][murano][fuel][ironic][cue][ceilometer][astara][gce-api][kiloeyes] keystoneclient 3.0.0 release - no more CLI!

ceilometer fix: https://review.openstack.org/307521 On Tue, Apr 19, 2016 at 4:05 AM, Steve Martinelli wrote: > Everyone, > > I sent out a note about this on Friday [1], but I'll repeat it here and > tag individual projects. The keystone team *will* be releasing a new > version of keystoneclient

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Agree. Install guide is just a start/example, concentrate is better than cover all, for more services we can just provide a good place to let them discoverable, and lfor arger scale, we should use advanced tools such as puppet and ansible On Mon, Apr 4, 2016 at 6:12 PM, Thierry Carrez wrote: >

Re: [openstack-dev] Adding Custom Meters in Kilo Ceilometer

basically, you need to inherit the base class and impl the get_samples interface, then registry it in setup.cfg. see an example in kilo: https://review.openstack.org/#/c/145819/ this patch adds some new meters polling by compute agent On Tue, Mar 29, 2016 at 3:29 PM, Murali Krishna wrote: > >

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

+1 to demand meetings and asynchronous way On Thu, Mar 31, 2016 at 9:33 PM, Ildikó Váncsa wrote: > Hi Gordon, > > > > > ie. the new PTL should checkpoint with subteam leads regularly to review > spec status or identify missing resources on high-priority > > items? > > I would say anything that w

Re: [openstack-dev] [vitrage] Gerrit Upgrade 12/16

thanks for the effort, new feature is welcomed but the new UI is really worse than the old one, it is not only related to habit, it is just ugly, for the first view I thought it has css bug. And it is not easy to find out current review status, old UI has a clear and nice table for review list O

Re: [openstack-dev] [aodh] HBase gate job

I prefer to deprecate all drivers except sql, but the upgrade issue requires us providing some tools to migrate those existent data On Tue, Nov 17, 2015 at 6:10 PM, Julien Danjou wrote: > Hi, > > So we recently decided to run the functional tests for the HBase driver > and enabled the gate job.

Re: [openstack-dev] [ceilometer] proposal to add Rohit Jaiswal to Ceilometer core

+1 On Thu, Nov 5, 2015 at 9:45 PM, gord chung wrote: > hi folks, > > i'd like to nominate Rohit Jaiswal as core for Ceilometer. he's done a lot > of good work recently like discovering and fixing many issues with Events > and implemented the configuration reloading functionality. he's also been

[openstack-dev] [oslo.config] MultiStrOpt VS. ListOpt

Hi, devs I come across a problem that crudini cannot handle MultiStrOpt[1], I don't know why such type configuration option is needed. It seems ListOpt is a better choice. Currently I find lots of MultiStrOpt options in both Nova and Ceilometer, and I think other projects have too. Here are my qu

[openstack-dev] [ceilometer] time based auto scaling

Hi devs, I'm thinking to add new type of alarm for time based auto scaling, but not sure if there is a better way to achieve it outside ceilometer scope Currently we can auto scaling based on vm load, but it will take several minutes to do it. For the worst case, when the vm load is heavy, ceilom

Re: [openstack-dev] [ceilometer] Stepping down as PTL

Thanks for your great work! On Fri, Apr 3, 2015 at 10:18 PM, Doug Hellmann wrote: > Excerpts from Eoghan Glynn's message of 2015-04-02 10:18:22 -0400: > > > > Hi Folks, > > > > Just a quick note to say that I won't be running again for > > ceilometer PTL over the liberty cycle. > > > > I've take

Re: [openstack-dev] [all] "All rights reserved" V.S. "Apache license"

@Stefano Maffulli Yes, the main point is the conflict of reserved all, and abandon some (actually most). According to the order the last will take effect IIUC Monty Taylor's explaination. I'm thinking that we should remove the "all rights reserved" words if we're using Apache license. Misleading

Re: [openstack-dev] [all] "All rights reserved" V.S. "Apache license"

Thanks for the clarification On Sun, Jan 18, 2015 at 5:07 AM, Monty Taylor wrote: > On 01/17/2015 03:27 AM, ZhiQiang Fan wrote: > > Hi, developers > > > > I have observed that some source code files in our projects have been > > announced as "Copyright xxx

[openstack-dev] [all] "All rights reserved" V.S. "Apache license"

Hi, developers I have observed that some source code files in our projects have been announced as "Copyright xxx, All rights reserved", and then followed by a "Apache License" Is this right? any conflict? And if one company claims that it reserves all rights for some source files, those source

Re: [openstack-dev] [nova][gate][stable] How eventlet 0.16.1 broke the gate

+1 how about the deep dependency? for example, we depends package A, and pin it, but A->B->C, then B and C are not pined since they are not directly depended, then what should we do? pin everything? On Thu, Jan 15, 2015 at 5:35 PM, Joe Gordon wrote: > Eventlet released 0.16.1 on 2015-01-14 [0],

[openstack-dev] [CI][TripleO][Ironic] check-tripleo-ironic-xxx fails

check-tripleo-ironic-xxx failed because: rm -rf /home/jenkins/.cache/image-create/pypi/mirror/ rm: cannot remove `/home/jenkins/.cache/image-create/pypi/mirror/': Permission denie see http://logs.openstack.org/37/143937/1/check-tripleo/check-tripleo-ironic-overcloud-precise-nonha/9be729b/console.

Re: [openstack-dev] 答复: Ceilometer memory.usage can not get info from libvirt

libvirt cannot inspect memory usage because some condition is not satisfied. But the AttributeError exception is ugly, Ceilometer should add basic check for return value, otherwise the unnecessary exception will bother cloud operator. I have reported a bug in Ceilometer for this issue, see https:

Re: [openstack-dev] [ceilometer] unable to collect compute.node.cpu.* data

If you don't know what IndentationError is, I think there is a long way to go before you familiar with Python. I suggest you discus something about developer issue in this Development Mailing List Your problem is that you have modify the file /opt/stack/ceilometer/ceilometer/compute/notifications

[openstack-dev] [Ceilometer] Timeout should be added when call http request

Hi, devs, I noticed that Ceilometer project uses lots of other OpenStack services, and other thirdparty services APIs, but rare of them set timeout when call http request, this is not a good behavior because many pollsters run in one of threads, if one is every slow or stuckd, then others will not

Re: [openstack-dev] [Ceilometer][MongoDB] Using native time to live feature in MongoDB

+1 On Thu, Nov 6, 2014 at 6:27 PM, Igor Degtiarov wrote: > Hi stackers, > > I'm working on solving bug [1]. Time to live feature has native > implementation in MongoDB thru index. > > Now we remove docs from resource table if they have no relations with > existing samples in meter table while sa

Re: [openstack-dev] [OpenStack-Dev] [BarbicanClient] [Cinder] Cinder unit tests failing

Actually, Alan Pevec on 2014-11-01 reported a bug https://bugs.launchpad.net/cinder/+bug/1388461 and it is assigned to original spec developer Brianna Poulos On Wed, Nov 5, 2014 at 6:33 AM, John Griffith wrote: > Hey Everyone, > > So there's been a bit

Re: [openstack-dev] [ceilometer] unable to collect compute.node.cpu.* data

is there any error or warning information related to that meter-list request in ceilometer-api.log? On Wed, Nov 5, 2014 at 10:43 AM, Du Jun wrote: > Hi all, > > I attempt to collect compute.node.cpu as the following link mentions: > > > http://docs.openstack.org/developer/ceilometer/measurements

[openstack-dev] [Ceilometer][HBase] Failed to run tox with master code on local environment

Hi, devs, When I run tox -epy27 -- alarms (fresh install with tox -r), it shows that may test case for hbase failed, I notice that jenkins runs well. I'm wondering are there any further steps needed to be taken before run tox locally? If so, which recent changes causes it? part of screen output:

Re: [openstack-dev] [heat][ceilometer]: scale up/ down based on number of instances in a group

Ceilometer mixes notifications and pollsters, so instance sample cannot represents how many instances (sample-list nor statistics), when we specify a time range in API query, the count of samples is not precise to real situation, it is ether less (due to potential lag when time range is precise) or

Re: [openstack-dev] [Ceilometer] Why alarm name is unique per project?

@Nejc Saje you're talking about group alarm, I'm going to try it on Kilo On Wed, Sep 24, 2014 at 7:34 PM, Nejc Saje wrote: > > On 09/24/2014 12:23 PM, Long Suo wrote: > >> Hi, all >> >> I am just a little confused why alarm name should be unique per project, >> anyone knows this? >> > > Good po

[openstack-dev] [ceilometer-client] query option discard special characters

Hi, developers, I find that ceilometer-client applies strict rule on query option, particularly, some special characters are not supported in key:value pairs, such as ~, !, and etc the regular expression used in ceilometerclient/v2/options.py is: r'([[a-zA-Z0-9_.]+)([>https://bugs.launchpad.net/p

[openstack-dev] [ceilometer] should we limit threshold value to be postive

Hi, developers, When I test the ceilometer threshold alarm, I find that there is no limitation for the threshold value, which means we can set it to negative value, but I didn't find any volume of meters will be negative, (if I'm wrong, please let me know, thanks) So, my question is: should we ad

[openstack-dev] [ceilometer] review request 66006

Hi, Ceilometer dev cores, There is a patch https://review.openstack.org/#/c/66006/, which is backported from 59669, aims at fixing bug : https://bugs.launchpad.net/ceilometer/+bug/1257232 in havana branch, but it is blocked by """ Alan Pevec Feb 11 Patch Set 4: Do not merge 2013.2.2 freeze """

Re: [openstack-dev] [ceilometer] raise clientSideError or do for user

thanks for the quick reply :) On Mon, Apr 14, 2014 at 9:23 PM, Julien Danjou wrote: > On Mon, Apr 14 2014, ZhiQiang Fan wrote: > > > Hi, developers, > > > > For fixing bug https://launchpad.net/bugs/1304886, I uploaded a patch > > https://review.openstack.org/#/c/

[openstack-dev] [ceilometer] raise clientSideError or do for user

Hi, developers, For fixing bug https://launchpad.net/bugs/1304886, I uploaded a patch https://review.openstack.org/#/c/86501/, when review this patch, there are two different kinds of opinions, I don't know which is the better choice, so I ask for help here. The patch aims at disallow user specif

Re: [openstack-dev] [openstack][SUSE][Ceilometer] ceilometer service init script can be improved

quit and ceilometer-collector fail I will continue follow these problem just in case, but for now, they are good thanks for your great work! On Wed, Mar 5, 2014 at 12:30 PM, ZhiQiang Fan wrote: > Hi, SUSE developers > > Thanks for your great work on OpenStack packaging for SUSE dis

Re: [openstack-dev] [Ceilometer][wsme][pecan] Need help for ceilometer havana alarm issue

thank you very much seems I should search the launchpad more carefully On Thu, Mar 6, 2014 at 3:37 PM, Mehdi Abaakouk wrote: > Hi, > > On Thu, Mar 06, 2014 at 10:44:25AM +0800, ZhiQiang Fan wrote: > > I already check the stable/havana and master branch via devstack, the >

Re: [openstack-dev] [Ceilometer][wsme][pecan] Need help for ceilometer havana alarm issue

h fix it in pecan or wsme module, or in ceilometer itself Is there anyone can help with this problem? thanks On Tue, Feb 18, 2014 at 9:09 AM, ZhiQiang Fan wrote: > Hi, > > When I try to figure out the root cause of bug[1], I found that once > wsme.exc.ClientSideError is trigge

[openstack-dev] [openstack][SUSE][Ceilometer] ceilometer service init script can be improved

Hi, SUSE developers Thanks for your great work on OpenStack packaging for SUSE distribution. I have tested some functionality of ceilometer on sles 11 sp3, and have two minor problem, which can create critical availability problem, but can be easily fixed . They all locate in the service init scr

Re: [openstack-dev] [Ceilometer][SUSE] SUSE OpenStack Havana distribution is different with upstream

26 février 2014, à 17:20 +0800, ZhiQiang Fan a écrit : > > Hi, SUSE OpenStack developers, > > > > After install OpenStack Havana on SLES 11 SP3 following the > > openstack-manuals' guide, I find that the > > ceilometer/storage/impl_sqlalchemy.py has implemented the

[openstack-dev] [Ceilometer][SUSE] SUSE OpenStack Havana distribution is different with upstream

Hi, SUSE OpenStack developers, After install OpenStack Havana on SLES 11 SP3 following the openstack-manuals' guide, I find that the ceilometer/storage/impl_sqlalchemy.py has implemented the metaquey functionality. However, the upstream, which means github.com/openstack/ceilometer stable/havana br

[openstack-dev] [OpenStack][Ceilometer] http header with large token problem

Hi, developers There is weired problem that when I try to verify the 8k http head problem for ceilometer, I construct a very long (30k) token (use a real valid PKI token as front part and copy several times), and use curl to request to ceilometer api v2 statistic interface, but ** it returns 200 O

[openstack-dev] [Ceilometer][wsme][pecan] Need help for ceilometer havana alarm issue

Hi, When I try to figure out the root cause of bug[1], I found that once wsme.exc.ClientSideError is triggerd when create an alarm, assume the faultstring is x, then if next http trigger a EntityNotFound(Exception) will get http response with faultstring equal to x. I trace the calling stack with

[openstack-dev] [Ceilometer] Policy Issue

Hi, I noticed that the Ceilometer project has no strict policy control, the /etc/ceilometer/policy.json only has one single rule 'context_is_admin', and for each specific resource operation, it will invoke acl.get_limit_to and v2._verify_query_segregation to forbid non-admin role operate other ten

[openstack-dev] [api-site] how to switch the project version for api document

Hi, I noticed that API reference in http://api.openstack.org/api-ref.htmldoesn't mention anything about the version issue. For example, Ceilometer has /v1 /v2 API, and /v2 is cross Havana and Icehouse, so if Icehouse adds some new features which add new arguments to the v2 API, then how does the r

Re: [openstack-dev] [Hacking] unit test code is too less

Hi, Dirk If a line just with single print (which means a function name) does nothing, I think it should be removed, print$ cannot be detected by "\bprint\s+[^\(]" >>> import re >>> print re.search(r"\bprint\s+[^\(]", "print") None >>> print re.search(r"\bprint(?:$|\s+[^\(])", "print") <_sre.SRE

Re: [openstack-dev] [Hacking] unit test code is too less

understand, thank you very much On Thu, Jan 23, 2014 at 3:45 PM, Yuriy Taraday wrote: > Hello. > > > On Thu, Jan 23, 2014 at 6:47 AM, ZhiQiang Fan wrote: >> >> I noticed that in openstack-dev/hacking project, there is very little >> test code, is there any parti

Re: [openstack-dev] [Heat] Reducing pep8 ignores

you can split H306 to several patches since it contains so much files. optional: It would be really nice if you can fix the unused import problem (if exist) in the same time, this seems can be checked via IDE On Wed, Jan 22, 2014 at 7:23 PM, Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com>

[openstack-dev] [Hacking] unit test code is too less

Hi, I noticed that in openstack-dev/hacking project, there is very little test code, is there any particular reason why it is in such situation? since hacking module is depended by almost all openstack projects, I think hacking code should be tested well at least for i.e. the hacking rule h233 i

[openstack-dev] [requirements][oslo] Upgrade six to 1.5.2?

six 1.5.2 has been released on 2014-01-06, it provides urllib/urlparse compatibility. Is there any plan to upgrade six to 1.5.2? (since it is fresh new, may need some time to test) six 1.4.1 is lack of urllib/urlparse support, so oslo-incubator/py3kcompat is needed, and it is used in some projects

Re: [openstack-dev] [Ceilometer][Nova] basic setting for notification_driver

, 2014 at 1:32 PM, ZhiQiang Fan wrote: > >> Hi, >> >> When read Ceilometer install guide[1], the multi valued option >> notification_driver is set to two drivers, My question is that is the first >> one, which means nova.openstack.common.notifier.rpc_notifie

[openstack-dev] [Ceilometer][Nova] basic setting for notification_driver

Hi, When read Ceilometer install guide[1], the multi valued option notification_driver is set to two drivers, My question is that is the first one, which means nova.openstack.common.notifier.rpc_notifier, necessary? what will happen if it is removed? Note, it is not configured even in Nova instal

[openstack-dev] kwargs explanation should be used when we raise webob.exc.WSGIHTTPException

Hi, stackers, In review patch: https://review.openstack.org/64099, I found that if we use kwargs detail instead of explanation when we raise that WSGIHTTPException, the http response body will generate 'message' using default explanation, instead of what we expected which is detail=msg. So I regi

[openstack-dev] [neutronclient] tox -epy27 failed because test_ssl

Sometimes, when i run tox on neutronclient, the test_ssl.TestSSL.test_client_manager_properly_creates_httpclient_instance may fail. However, gate doesn't catch this problem, and even in my env, it doesn't fail everytime, is there any other developer have meet same problem? -- blog: zqfan.github.c

Re: [openstack-dev] Requirements syncing job is live

oesn't). So there > autosync is not yet appropriate. > > > On 10/02/2013 04:40 AM, ZhiQiang Fan wrote: > >> Hi, Roman, >> >> auto sync requirements is a good job. >> >> It is so good that I'm wondering if the oslo-incubator can do such job >> too,

Re: [openstack-dev] Requirements syncing job is live

n packages. > > On the other hand, oslo.version/oslo.messaging/oslo.* are separate > libraries, having their own releases, so syncing of global requirements > will effectively make projects use newer versions of those libs. > > Thanks, > Roman > > > On Wed, Oct 2, 2013

Re: [openstack-dev] Requirements syncing job is live

great job! thanks (how about auto sync from oslo too? - projects.txt: projects want to be automatically synced from oslo - heads.txt: HEAD for each module in oslo whenever module maintainer think current module is strong enough to publish, then he/she can edit the heads.txt of that module line, t

[openstack-dev] about bug create new task

Hi, I noticed that you've done some great work about the init testr problem, thanks for your contribute. There is something can be improved if you want, which means that: you can create new task in a reported bug, just click "Also affects project" and add new project. This can help us to know wh

Re: [openstack-dev] [Neutron]All unittest passed but Jenkins failed

thanks for your help On Wed, Sep 11, 2013 at 10:38 PM, James E. Blair wrote: > ZhiQiang Fan writes: > > > currently, i don't know if it is coverage problem or something else. > > > > the direct cause is: > > > > sudo /usr/local/jenkins/slave_scripts/je

[openstack-dev] [Neutron]All unittest passed but Jenkins failed

currently, i don't know if it is coverage problem or something else. the direct cause is: sudo /usr/local/jenkins/slave_scripts/jenkins-sudo-grep.sh post Sep 9 06:57:23 precise1 sudo: jenkins : 3 incorrect password attempts ; TTY=unknown ; PWD=/home/jenkins/workspace/gate-neutron-python27 ; US

Re: [openstack-dev] [Neutron] Running unit tests (was: REST-based ML2 MechanismDriver)

why -- is important? without it still can work (maybe not work perfectly? or will miss something important?) on ubuntu12.04 py2.7.5 On Mon, Sep 2, 2013 at 1:59 AM, Akihiro Motoki wrote: > Please try: > >tox -e py27 -- neutron.tests.unit.test_l3_plugin > > "--" is important when using tox. >

Re: [openstack-dev] [Neutron] Running unit tests (was: REST-based ML2 MechanismDriver)

tox neutron.tests.unit.ml2 On Mon, Sep 2, 2013 at 1:51 AM, Luke Gorrie wrote: > Hi guys, > > Can someone tell me the best way currently to run a subset of Neutron unit > tests (e.g. ml2 ones)? > > The command I got the last time I asked has recently stopped working: > > On 6 June 2013 17:16, Lu

Re: [openstack-dev] Proposal for Raksha, a Data Protection As a Service project

+1 On Thu, Aug 29, 2013 at 6:12 AM, Murali Balcha wrote: > Hello Stackers, > > We would like to introduce a new project Raksha, a Data Protection As a > Service (DPaaS) for OpenStack Cloud. > > Raksha’s primary goal is to provide a comprehensive Data Protection for > OpenStack by leveraging N

Re: [openstack-dev] [Openstack][keystone][ldap] Bug unsupported operand type(s) for &: 'str' and 'int'

ackend/ldap/core.py,, > > > 2013/8/22 ZhiQiang Fan > >> yes, i think it is a bug, because the api doesn't convert string to >> correct type: >> >>> True & 1 >> 1 >> >>> 'True' & 1 >> Traceback (most recent c

Re: [openstack-dev] [Openstack][keystone][ldap] Bug unsupported operand type(s) for &: 'str' and 'int'

int' Feel free to report a bug and may be you can try to fix it. On Thu, Aug 22, 2013 at 3:51 PM, Qinglong.Meng wrote: > oh, yeah, > here is the keystone log: > http://paste.openstack.org/show/44857/ > > Best Regards, > > > > > > 2013/8/22 ZhiQiang Fan >

Re: [openstack-dev] [Quantum]How to contribute LBaas driver?

"""Where to post the code and where to require code review?""" the following 2 links may help - https://wiki.openstack.org/wiki/How_To_Contribute - https://wiki.openstack.org/wiki/Gerrit_Workflow good luck On Thu, Aug 22, 2013 at 3:04 PM, HuYanrui wrote: > ** > Ilya, or other guys. > As previ

Re: [openstack-dev] [Openstack][keystone][ldap] Bug unsupported operand type(s) for &: 'str' and 'int'

your first reference (the log) is incorrect. On Thu, Aug 22, 2013 at 2:55 PM, Qinglong.Meng wrote: > Hi All, > Os: Ubuntu 12.04 LTS > keystone version: stable/grizzly > > After I deploy keystone with ldap backend (openldap), I got the issue > about type in keystone.log, when I create

Re: [openstack-dev] [Openstack][keystone][ssl] Help for configure keystone with ssl.

2013.2 should be in havana? On Wed, Aug 21, 2013 at 6:13 PM, Qinglong.Meng wrote: > Hi All, > Os: ubuntu 12.04 LTS > keystone version: stable/grizzly > > Ｉ hava seen "keystone-manage ssl_setup" in keystone tag 2013.2.b1. > but I can't use it in my version. > So I want to know: >

Re: [openstack-dev] git commit message: change id will before bug/bp when first commit

thank you On Mon, Aug 19, 2013 at 12:52 AM, Jeremy Stanley wrote: > On 2013-08-18 14:25:22 +0800 (+0800), ZhiQiang Fan wrote: > > When submit code review in gerrit, i have been recommended put > > Fixes-Bug: #bug-id/Implement-Blueprint: #bp-desc before chang-id. > > Howeve

Re: [openstack-dev] [Neutron] Exceptions in neutron.extension

bm.com* > [image: IBM] > > 3605 Hwy 52 N > Rochester, MN 55901-1407 > United States > > > > > > From:ZhiQiang Fan > To:OpenStack Development Mailing List < > openstack-dev@lists.openstack.org>, > Date:08/17/2013 09:55 PM > Subject:

[openstack-dev] git commit message: change id will before bug/bp when first commit

Hi, stackers, When submit code review in gerrit, i have been recommended put Fixes-Bug: #bug-id/Implement-Blueprint: #bp-desc before chang-id. However, when first run git commit in a seperate patch branch, the change-id will generate before bug/bp, it is automatically, so i have to use git commit

[openstack-dev] [Neutron] Exceptions in neutron.extension

Hi stackers, I notice that there are some exceptions defined in neutron.extension, and many exceptions are defined in neutron.common.exception. Why they are defined seperately? In my opinion: 1) extension will define exception which is only releated to this extension and is intended to exposed t