Re: [openstack-dev] Getting GERRIT error while submitting spec for liberty.
On 2015-04-04 16:39:17 +0530 (+0530), Vikram Choudhary wrote: Can anyone please help me in resolving the below errors. [...] We don't know where your gerrit is. Please manually create a remote named gerrit and try again. [...] Exception: Error running git remote add -f gerrit ssh:// vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git [...] This error error message from git-review can be misleading, because it performs a test push to attempt to determine whether your Gerrit credentials/URL are correct. However, if you're testing it on a CLA-enforced repository (such as openstack/neutron-specs) it can misinterpret a CLA-related rejection from Gerrit as implying your configuration is incorrect. If... ssh -p 29418 vikram.choudh...@review.openstack.org gerrit version ...returns a gerrit version string instead of an authentication or connection error, then this is probably the issue. Make sure your account was set up following the instructions at... http://docs.openstack.org/infra/manual/developers.html#account-setup ...including setting up your Foundation Individual Member profile at www.openstack.org, and agreeing to the ICLA and submitting contact information on review.openstack.org. If your test instead reveals that ssh is failing with something like Permission denied (publickey) then double-check that your username in Gerrit is shown as vikram.choudhary and that you've correctly added your SSH RSA public key in Gerrit as well. -- Jeremy Stanley __ 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] Getting GERRIT error while submitting spec for liberty.
Hi All, Can anyone please help me in resolving the below errors. viksdeep@ubuntu:~/work/neutron-specs$ git review -s Creating a git remote called gerrit that maps to: ssh:// vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git traceback object at 0x7fe3acbf0908 We don't know where your gerrit is. Please manually create a remote named gerrit and try again. Traceback (most recent call last): File /usr/bin/git-review, line 1196, in module main() File /usr/bin/git-review, line 1110, in main config['hostname'], config['port'], config['project']) File /usr/bin/git-review, line 489, in check_remote add_remote(hostname, port, project, remote) File /usr/bin/git-review, line 353, in add_remote raise Exception(Error running %s % cmd) Exception: Error running git remote add -f gerrit ssh:// vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git viksdeep@ubuntu:~/work/neutron-specs$ Thanks Vikram __ 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] Getting GERRIT error while submitting spec for liberty.
Hi Vikram, I had the same problem. I had first to manually add the remote: git remote add gerrit ssh://vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git then git review -s worked. Claudio Il 04-Apr-15 1:09 PM, Vikram Choudhary ha scritto: Hi All, Can anyone please help me in resolving the below errors. viksdeep@ubuntu:~/work/neutron-specs$ git review -s Creating a git remote called gerrit that maps to: ssh://vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git http://vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git traceback object at 0x7fe3acbf0908 We don't know where your gerrit is. Please manually create a remote named gerrit and try again. Traceback (most recent call last): File /usr/bin/git-review, line 1196, in module main() File /usr/bin/git-review, line 1110, in main config['hostname'], config['port'], config['project']) File /usr/bin/git-review, line 489, in check_remote add_remote(hostname, port, project, remote) File /usr/bin/git-review, line 353, in add_remote raise Exception(Error running %s % cmd) Exception: Error running git remote add -f gerrit ssh://vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git http://vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git viksdeep@ubuntu:~/work/neutron-specs$ Thanks Vikram __ 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] Getting GERRIT error while submitting spec for liberty.
Ok, I've read your answer to Vikram and I'm in the first case, where gerrit version works but git review -s doesn't. I thought by adding manually the remote I have solved the problem. I'll check the step in the documentation again, thank you Jeremy. Claudio Il 04-Apr-15 1:50 PM, Jeremy Stanley ha scritto: On 2015-04-04 13:38:07 +0200 (+0200), Claudio Pupparo wrote: I had the same problem. I had first to manually add the remote: git remote add gerrit ssh://vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git then git review -s worked. You misunderstand. That remote is what git review -s wants to add on its own. If you manually added the remote yourself, then rerunning git review -s is pointless as that command simply sees the remote it wanted to add is already there and does nothing instead. Further testing is required to find out _why_ git review -s fails its test push when trying to add that remote on its own. The answer to these sorts of questions is to _first_ point people back at the documentation, because this problem almost always means an account setup step was missed or performed incorrectly. __ 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] Getting GERRIT error while submitting spec for liberty.
On 2015-04-04 13:38:07 +0200 (+0200), Claudio Pupparo wrote: I had the same problem. I had first to manually add the remote: git remote add gerrit ssh://vikram.choudh...@review.openstack.org:29418/openstack/neutron-specs.git then git review -s worked. You misunderstand. That remote is what git review -s wants to add on its own. If you manually added the remote yourself, then rerunning git review -s is pointless as that command simply sees the remote it wanted to add is already there and does nothing instead. Further testing is required to find out _why_ git review -s fails its test push when trying to add that remote on its own. The answer to these sorts of questions is to _first_ point people back at the documentation, because this problem almost always means an account setup step was missed or performed incorrectly. -- Jeremy Stanley __ 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] [cinder] Report status of Huawei Volume CI from April 1
Please update your Apache configuration to not require downloads. Instructions to do this are here: http://ci.openstack.org/third_party.html#faq-frequently-asked-questions Ramy From: liuxinguo [mailto:liuxin...@huawei.com] Sent: Saturday, April 04, 2015 5:47 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Fanyaohong Subject: [openstack-dev] [cinder] Report status of Huawei Volume CI from April 1 Hello Cinder team, ·Huawei Volume CI has posted to about forty cinder reviews from April 1 to now and will keep reporting stably. · ·It now runs 304 tests, passed 293 and skipped 11. The following are links to the cinder reviews our CI has posted results to, please check it: https://review.openstack.org/12 https://review.openstack.org/163641 https://review.openstack.org/169430 https://review.openstack.org/168177 https://review.openstack.org/168179 https://review.openstack.org/169153 https://review.openstack.org/165798 https://review.openstack.org/167134 https://review.openstack.org/169653 https://review.openstack.org/159704 https://review.openstack.org/154350 https://review.openstack.org/169707 https://review.openstack.org/164527 https://review.openstack.org/165688 https://review.openstack.org/163706 https://review.openstack.org/144409 https://review.openstack.org/169781 https://review.openstack.org/169812 https://review.openstack.org/169831 https://review.openstack.org/165655 https://review.openstack.org/16 https://review.openstack.org/17 https://review.openstack.org/169915 https://review.openstack.org/170156 https://review.openstack.org/170157 https://review.openstack.org/151567 https://review.openstack.org/170199 https://review.openstack.org/170178 https://review.openstack.org/163232 https://review.openstack.org/170588 https://review.openstack.org/152284 https://review.openstack.org/156904 https://review.openstack.org/160682 https://review.openstack.org/170346 https://review.openstack.org/170616 https://review.openstack.org/164692 https://review.openstack.org/161363 https://review.openstack.org/170310 https://review.openstack.org/169858 https://review.openstack.org/152475 https://review.openstack.org/161209 https://review.openstack.org/155607 https://review.openstack.org/168901 https://review.openstack.org/169060 https://review.openstack.org/160209 https://review.openstack.org/163910 https://review.openstack.org/159856 https://review.openstack.org/147476 ·Or you can just check it at here: ·https://review.openstack.org/#/q/project:openstack/cinder,n,z · I will pay very close attention to the status of our CI and keep it running stably. If there is any requirement our CI has not satisfied, please let us know. Thanks and regards, Liu __ 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] [scheduler] [gantt] Please stop using Gantt for discussing about Nova scheduler
On 4/3/15, 8:24 PM, Dugger, Donald D donald.d.dug...@intel.com wrote: The goal is not `splitting for the sake of splitting'. The goal is to have a separate scheduler that is ultimately usable by other projects inside OpenStack. Currently Cinder has its own filter based scheduler (duplicating scheduling code in 2 places seems silly), Neutron will need scheduling services, there are multiple places where a common scheduling service would be beneficial. + 1 -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 -Original Message- From: Ed Leafe [mailto:e...@leafe.com] Sent: Friday, April 3, 2015 10:59 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] [scheduler] [gantt] Please stop using Gantt for discussing about Nova scheduler -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/03/2015 11:42 AM, Dugger, Donald D wrote: Yes the current effort is to clean up the scheduler interfaces but one of the main goals of that clean up is to make it possible to then split out the scheduler to a separate project. I don't want to lose focus on the ultimate goal of creating the split. I don't agree that the ultimate goal is splitting the scheduler. IMO, the goal is to create 1) a clean, robust interface along with 2) a scalable architecture. Those improvements will 1) allow the scheduler to be split cleanly, and 2) justify splitting it out. Splitting for the sake of splitting is pointless. - -- - -- Ed Leafe -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJVHsbeAAoJEKMgtcocwZqLdysQAIJ6nThjqgNgJu1hLW4n6MDY Db57k+37b5M5h6Z633jrXSTWCuqjIwUIW2G1+PQMsXq7FcWguAG7fxhVizE4s0h0 RhucmNQ1GWj6eFNfpSljC0WAdZEDhuXnPcxi2OyMwRr0j2lqYcJvPKBmuobS8Rbl xD9ciIlVELtHPm2dsj1HkB8TO7fgESjdv+I2QPU9C31ubp0CYlwSAPCdAhN9g+B0 WVCEnq+7ADn95G+/z77Wlx6s83KkCh89C+h2ivgGI4mHeWJskXT9lr9lsC342DO9 GoWvDvRF5H9/imx6Jh4avipH55YCZfZ9T+2eOPVoAYkXujPiX13tqM8UkBj7KCDx /FJNatC0aTDPYGMgOW329pGWkP9n2ceW1gMlyHpmMFJHCaAdmM+gqnjnarT1UECr 13yndy9axjubisZ71hdGgBi/Sy1FbG5+XVshWyAUgzoJZurDtg4RhhUdw8n0iQKd SuA3E9Z+PI6gTulp532JdHBVOpsG2P+9QOzLwBEnpSp8WmuU8h2EVMm6A3Zdrf+4 zIUL8lvpDwZ/0KBHSF6WptZspSXe/OwOKlQYO2geHkeARANv3Tv/h3HB/7SW1Bz0 8N5K2aDK/adzfzagrV0S3f201JoFC90JSXgA4dDdtHr8/oUj1kw3QoTACVrvPvYP ayW76hfM68cjJ3DyhXys =5h63 -END PGP SIGNATURE- __ 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 __ 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] Getting GERRIT error while submitting spec for liberty.
Hi All, There was some issue with SSH key. After regenerating and re-adding to my account it worked. Thanks for the help. Thanks Vikram On Sat, Apr 4, 2015 at 5:35 PM, Claudio Pupparo claudio.pupp...@gmail.com wrote: Ok, I've read your answer to Vikram and I'm in the first case, where gerrit version works but git review -s doesn't. I thought by adding manually the remote I have solved the problem. I'll check the step in the documentation again, thank you Jeremy. Claudio Il 04-Apr-15 1:50 PM, Jeremy Stanley ha scritto: On 2015-04-04 13:38:07 +0200 (+0200), Claudio Pupparo wrote: I had the same problem. I had first to manually add the remote: git remote add gerrit ssh://vikram.choudh...@review.openstack.org:29418/openstack/ neutron-specs.git then git review -s worked. You misunderstand. That remote is what git review -s wants to add on its own. If you manually added the remote yourself, then rerunning git review -s is pointless as that command simply sees the remote it wanted to add is already there and does nothing instead. Further testing is required to find out _why_ git review -s fails its test push when trying to add that remote on its own. The answer to these sorts of questions is to _first_ point people back at the documentation, because this problem almost always means an account setup step was missed or performed incorrectly. __ 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
[openstack-dev] [cinder] Report status of Huawei Volume CI from April 1
Hello Cinder team, · Huawei Volume CI has posted to about forty cinder reviews from April 1 to now and will keep reporting stably. · · It now runs 304 tests, passed 293 and skipped 11. The following are links to the cinder reviews our CI has posted results to, please check it: https://review.openstack.org/12 https://review.openstack.org/163641 https://review.openstack.org/169430 https://review.openstack.org/168177 https://review.openstack.org/168179 https://review.openstack.org/169153 https://review.openstack.org/165798 https://review.openstack.org/167134 https://review.openstack.org/169653 https://review.openstack.org/159704 https://review.openstack.org/154350 https://review.openstack.org/169707 https://review.openstack.org/164527 https://review.openstack.org/165688 https://review.openstack.org/163706 https://review.openstack.org/144409 https://review.openstack.org/169781 https://review.openstack.org/169812 https://review.openstack.org/169831 https://review.openstack.org/165655 https://review.openstack.org/16 https://review.openstack.org/17 https://review.openstack.org/169915 https://review.openstack.org/170156 https://review.openstack.org/170157 https://review.openstack.org/151567 https://review.openstack.org/170199 https://review.openstack.org/170178 https://review.openstack.org/163232 https://review.openstack.org/170588 https://review.openstack.org/152284 https://review.openstack.org/156904 https://review.openstack.org/160682 https://review.openstack.org/170346 https://review.openstack.org/170616 https://review.openstack.org/164692 https://review.openstack.org/161363 https://review.openstack.org/170310 https://review.openstack.org/169858 https://review.openstack.org/152475 https://review.openstack.org/161209 https://review.openstack.org/155607 https://review.openstack.org/168901 https://review.openstack.org/169060 https://review.openstack.org/160209 https://review.openstack.org/163910 https://review.openstack.org/159856 https://review.openstack.org/147476 · Or you can just check it at here: · https://review.openstack.org/#/q/project:openstack/cinder,n,z · I will pay very close attention to the status of our CI and keep it running stably. If there is any requirement our CI has not satisfied, please let us know. Thanks and regards, Liu __ 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] SQLite support (migrations, work-arounds, and more), is it worth it?
I totally agree, since this is not used in production and make the dev job more complicated. @Henry If you want help with this, I would be glad to work with you to make this clean up. On Sat, Apr 4, 2015 at 2:55 AM Henry Nash hen...@linux.vnet.ibm.com wrote: Fully support this. I, for one, volunteer to take on a lot of the work needed to clean up any our tests/environment to allow this to a happen. Hardly a month goes by without a fix having to be re-applied to our sql code to get round some problem that didn’t show up in original testing because SQLite is too promiscuous. Henry On 4 Apr 2015, at 01:55, Morgan Fainberg morgan.fainb...@gmail.com wrote: I am looking forward to the Liberty cycle and seeing the special casing we do for SQLite in our migrations (and elsewhere). My inclination is that we should (similar to the deprecation of eventlet) deprecate support for SQLite in Keystone. In Liberty we will have a full functional test suite that can (and will) be used to validate everything against much more real environments instead of in-process “eventlet-like” test-keystone-services; the “Restful test cases” will no longer be part of the standard unit tests (as they are functional testing). With this change I’m inclined to say SQLite (being the non-production usable DB) what it is we should look at dropping migration support for SQLite and the custom work-arounds. Most deployers and developers (as far as I know) use devstack and MySQL or Postgres to really suss out DB interactions. I am looking for feedback from the community on the general stance for SQLite, and more specifically the benefit (if any) of supporting it in Keystone. -- Morgan Fainberg __ 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 __ 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] VPNaaS in Icehouse
Hi Is there any document describing VPNaaS for Icehouse. The document I found are: https://docs.google.com/document/d/1Jphcvnn7PKxqFEFFZQ1_PYkEx5J4aO5J5Q74R_PwgV8/edit?pli=1 Virtual Private Network as a Service (VPNaaS) — Neutron Specs 0.0.0.post402 documentation | | | | | | | | | Virtual Private Network as a Service (VPNaaS) — Neutron Specs 0.0.0.post402 documentationIPSec site connections Manage IPSec site-to-site connections through the VPN as a Serviceextension. Table IPSec site connection attributes Attribute Type Required | | | | View on specs.openstack.org | Preview by Yahoo | | | | | Neutron/VPNaaS - OpenStack | | | | | | | | | Neutron/VPNaaS - OpenStackContents 1 OUTDATED 2 Overview 2.1 DataModel 2.1.1 VPNServices Resource 2.1.2 IKEPolicies Resource 2.1.3 IPsecPolicies Resource 2.1.4 ipsec-site-connection Resource | | | | View on wiki.openstack.org | Preview by Yahoo | | | | | Are these documents applicable for Icehouse ? Also, I have the following questions regarding VPNaaS in Icehouse (or even Juno / Kilo): 1. Is only one subnet local + 1 subnet remote supported per VPN service ?2. Is there always a 1 : 1 mapping between VPNService and VPNServiceConnection ?3. Is the VPN gateway same as the neutron router or can be different ?4. What is the difference between subnet_id and local_cidr ? Regards,Anik __ 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] Problem about Juno Keystone Identity V3
On 04/03/2015 11:09 AM, Amy Zhang wrote: Hi guys, I have done switching Keystone Identity V2 to V3 in Icehouse and it works perfect. However, I use the same way to switch Keystone Identity V2 to V3 in Juno, it doesn't work. It give me the error: ERROR: openstack Internal Server Error (HTTP 500). I traced back to the code, find the error comes from apache, but it doesn't make any sense that apache has problem, it might be some problem of keystone which lead to error of apache. Does any one have any idea of it? Thanks! -- Best regards, Amy (Yun Zhang) __ 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 Bet she's hitting token size issues, as that is an issue in the header going between mod_ WSGI and HTTPD. Try switching to UUID tokens. __ 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] SQLite support (migrations, work-arounds, and more), is it worth it?
yes please [2] On Sat, Apr 4, 2015 at 1:07 PM, Raildo Mascena rail...@gmail.com wrote: I totally agree, since this is not used in production and make the dev job more complicated. @Henry If you want help with this, I would be glad to work with you to make this clean up. On Sat, Apr 4, 2015 at 2:55 AM Henry Nash hen...@linux.vnet.ibm.com wrote: Fully support this. I, for one, volunteer to take on a lot of the work needed to clean up any our tests/environment to allow this to a happen. Hardly a month goes by without a fix having to be re-applied to our sql code to get round some problem that didn’t show up in original testing because SQLite is too promiscuous. Henry On 4 Apr 2015, at 01:55, Morgan Fainberg morgan.fainb...@gmail.com wrote: I am looking forward to the Liberty cycle and seeing the special casing we do for SQLite in our migrations (and elsewhere). My inclination is that we should (similar to the deprecation of eventlet) deprecate support for SQLite in Keystone. In Liberty we will have a full functional test suite that can (and will) be used to validate everything against much more real environments instead of in-process “eventlet-like” test-keystone-services; the “Restful test cases” will no longer be part of the standard unit tests (as they are functional testing). With this change I’m inclined to say SQLite (being the non-production usable DB) what it is we should look at dropping migration support for SQLite and the custom work-arounds. Most deployers and developers (as far as I know) use devstack and MySQL or Postgres to really suss out DB interactions. I am looking for feedback from the community on the general stance for SQLite, and more specifically the benefit (if any) of supporting it in Keystone. -- Morgan Fainberg __ 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 __ 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 -- Rodrigo Duarte Sousa Senior Software Engineer at Advanced OpenStack Brazil Distributed Systems Laboratory MSc in Computer Science Federal University of Campina Grande Campina Grande, PB - Brazil http://rodrigods.com http://lsd.ufcg.edu.br/%7Erodrigods __ 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
