<div dir="ltr">+1<br><div class="gmail_extra"><br><div class="gmail_quote">2017-04-25 0:23 GMT+08:00 <span dir="ltr"><<a href="mailto:openstack-dev-request@lists.openstack.org" target="_blank">openstack-dev-request@lists.openstack.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send OpenStack-dev mailing list submissions to<br>
<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openstack-dev-request@lists.openstack.org">openstack-dev-request@lists.<wbr>openstack.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openstack-dev-owner@lists.openstack.org">openstack-dev-owner@lists.<wbr>openstack.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OpenStack-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [oslo] Update Review dashboard links (ChangBo Guo)<br>
2. Re: [tripleo] Final project logo files (Emilien Macchi)<br>
3. Re: [nova] about usage of /consoles (Chen CH Ji)<br>
4. Re: [tricircle]mascot for the Tricircle project (Morales, Victor)<br>
5. [mistral][tripleo] mistralclient release needed<br>
(Juan Antonio Osorio)<br>
6. Ops Team Meeting 042417 Canceled (Melvin Hillsman)<br>
7. Re: [ironic] New mascot design (Loo, Ruby)<br>
8. Re: [oslo] Update Review dashboard links (ChangBo Guo)<br>
9. Re: [tripleo] Final project logo files (Carlos Camacho Gonzalez)<br>
10. [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Jadhav, Pooja)<br>
11. Re: [ironic] New mascot design (Dmitry Tantsur)<br>
12. Re: [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Doug Hellmann)<br>
13. Re: [kolla] OpenStack Kolla-Kubernetes Workshop: Demystifying<br>
the Gate - video conferencing information (sasi kiran)<br>
14. Re: Project Navigator Updates - Feedback Request (Yuval Brik)<br>
15. Re: [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Eric Fried)<br>
16. [keystone] mascot v2.0 (Lance Bragstad)<br>
17. Re: Project Navigator Updates - Feedback Request (Dmitry Tantsur)<br>
18. Re: [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Jay Pipes)<br>
19. Re: Project Navigator Updates - Feedback Request (Jimmy McArthur)<br>
20. [neutron] CI team meeting on Apr 25 canceled (Ihar Hrachyshka)<br>
21. Re: [mistral][tripleo] mistralclient release needed<br>
(Renat Akhmerov)<br>
22. Re: [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Eric Fried)<br>
23. Re: [ceilometer]Looking for endpoint where event passed after<br>
first time (Hui Xiang)<br>
24. Re: [Release-job-failures][<wbr>mistral] Release of<br>
openstack/python-mistralclient failed (Doug Hellmann)<br>
25. Re: [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Doug Hellmann)<br>
26. Re: [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Jay Pipes)<br>
27. Re: [Release-job-failures][<wbr>mistral] Release of<br>
openstack/python-mistralclient failed (Renat Akhmerov)<br>
28. [barbican] Nominating Jeremy Liu for Barbican Core<br>
(Dave McCowan (dmccowan))<br>
29. Re: [nova][oslo.utils] Bug-1680130 Check validation of UUID<br>
length (Matt Riedemann)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Mon, 24 Apr 2017 20:04:24 +0800<br>
From: ChangBo Guo <<a href="mailto:glongwave@gmail.com">glongwave@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] [oslo] Update Review dashboard links<br>
Message-ID:<br>
<<a href="mailto:CANWmB0WiriDjjwCwbBVC2_YageEKmZgffNnz7Oh2%2BDSebTT5PA@mail.gmail.com">CANWmB0WiriDjjwCwbBVC2_<wbr>YageEKmZgffNnz7Oh2+DSebTT5PA@<wbr>mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I just posted a update of our Review dashboard config files in<br>
<a href="https://review.openstack.org/#/c/459247/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/459247/</a>.<br>
the main.dash was copied from oslo-incubator with adding missing libraries.<br>
I must divid 35 libraries into 4 groups becuase each dashboard allows up to<br>
10 queries.<br>
<br>
<br>
The output can be used directly , hope this will be useful.<br>
<br>
# ./build_dashboards.sh /home/changboguo/code/os/<wbr>gerrit-dash-creator<br>
/home/changboguo/code/os/oslo.<wbr>tools/dashboards/<br>
<br>
------------------------------<wbr>----------<br>
libs_part1<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=%28project%3A%5Eopenstack%2Foslo.%2A+OR+project%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Fcastellan+OR+project%3Aopenstack%2Ffuturist+OR%0Aproject%3Aopenstack%2Fautomaton+OR+project%3Aopenstack%2Ddev%2Fcookiecutter+OR%0Aproject%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Ddev%2Foslo%2Dcookiecutter+OR+project%3Aopenstack%2Fmox3%29%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+One%29&Oslo+Specs=project%3Aopenstack%2Foslo%2Dspecs&automaton=project%3Aopenstack%2Fautomaton&castellan=project%3Aopenstack%2Fcastellan&cookiecutter=project%3Aopenstack%2Ddev%2Fcookiecutter&debtcollector=project%3Aopenstack%2Fdebtcollector&futurist=project%3Aopenstack%2Ffuturist&mox3=project%3Aopenstack%2Fmox3&oslo%2Dcookiecutter=project%3Aopenstack%2Ddev%2Fcookiecutter&oslo.cache=project%3Aopenstack%2Foslo.cache" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%<wbr>28project%3A%5Eopenstack%<wbr>2Foslo.%2A+OR+project%<wbr>3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<wbr>2Fcastellan+OR+project%<wbr>3Aopenstack%2Ffuturist+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Fautomaton+OR+project%<wbr>3Aopenstack%2Ddev%<wbr>2Fcookiecutter+OR%0Aproject%<wbr>3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<wbr>2Ddev%2Foslo%2Dcookiecutter+<wbr>OR+project%3Aopenstack%2Fmox3%<wbr>29%0Astatus%3Aopen+NOT+owner%<wbr>3Aself&title=Oslo+Review+<wbr>Inbox%28Part+One%29&Oslo+<wbr>Specs=project%3Aopenstack%<wbr>2Foslo%2Dspecs&automaton=<wbr>project%3Aopenstack%<wbr>2Fautomaton&castellan=project%<wbr>3Aopenstack%2Fcastellan&<wbr>cookiecutter=project%<wbr>3Aopenstack%2Ddev%<wbr>2Fcookiecutter&debtcollector=<wbr>project%3Aopenstack%<wbr>2Fdebtcollector&futurist=<wbr>project%3Aopenstack%<wbr>2Ffuturist&mox3=project%<wbr>3Aopenstack%2Fmox3&oslo%<wbr>2Dcookiecutter=project%<wbr>3Aopenstack%2Ddev%<wbr>2Fcookiecutter&oslo.cache=<wbr>project%3Aopenstack%2Foslo.<wbr>cache</a><br>
<br>
------------------------------<wbr>----------<br>
libs_part2<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=project%3A%5Eopenstack%2Foslo.%2A%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+Two%29&oslo.privsep=project%3Aopenstack%2Foslo.privsep&oslo.reports=project%3Aopenstack%2Foslo.reports&oslo.rootwrap=project%3Aopenstack%2Foslo.rootwrap&oslo.serialization=project%3Aopenstack%2Foslo.serialization&oslo.service=project%3Aopenstack%2Foslo.service&oslo.tools=project%3Aopenstack%2Foslo.tools&oslo.utils=project%3Aopenstack%2Foslo.utils&oslo.versionedobjects=project%3Aopenstack%2Foslo.versionedobjects&oslo.vmware=project%3Aopenstack%2Foslo.vmware" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=project%<wbr>3A%5Eopenstack%2Foslo.%2A%<wbr>0Astatus%3Aopen+NOT+owner%<wbr>3Aself&title=Oslo+Review+<wbr>Inbox%28Part+Two%29&oslo.<wbr>privsep=project%3Aopenstack%<wbr>2Foslo.privsep&oslo.reports=<wbr>project%3Aopenstack%2Foslo.<wbr>reports&oslo.rootwrap=project%<wbr>3Aopenstack%2Foslo.rootwrap&<wbr>oslo.serialization=project%<wbr>3Aopenstack%2Foslo.<wbr>serialization&oslo.service=<wbr>project%3Aopenstack%2Foslo.<wbr>service&oslo.tools=project%<wbr>3Aopenstack%2Foslo.tools&oslo.<wbr>utils=project%3Aopenstack%<wbr>2Foslo.utils&oslo.<wbr>versionedobjects=project%<wbr>3Aopenstack%2Foslo.<wbr>versionedobjects&oslo.vmware=<wbr>project%3Aopenstack%2Foslo.<wbr>vmware</a><br>
<br>
------------------------------<wbr>----------<br>
libs_part3<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=project%3A%5Eopenstack%2Foslo.%2A%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+Three%29&oslo.concurrency=project%3Aopenstack%2Foslo.concurrency&oslo.config=project%3Aopenstack%2Foslo.config&oslo.context=project%3Aopenstack%2Foslo.context&oslo.db=project%3Aopenstack%2Foslo.db&oslo.i18n=project%3Aopenstack%2Foslo.i18n&oslo.log=project%3Aopenstack%2Foslo.log&oslo.messaging=project%3Aopenstack%2Foslo.messaging&oslo.middleware=project%3Aopenstack%2Foslo.middleware&oslo.policy=project%3Aopenstack%2Foslo.policy" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=project%<wbr>3A%5Eopenstack%2Foslo.%2A%<wbr>0Astatus%3Aopen+NOT+owner%<wbr>3Aself&title=Oslo+Review+<wbr>Inbox%28Part+Three%29&oslo.<wbr>concurrency=project%<wbr>3Aopenstack%2Foslo.<wbr>concurrency&oslo.config=<wbr>project%3Aopenstack%2Foslo.<wbr>config&oslo.context=project%<wbr>3Aopenstack%2Foslo.context&<wbr>oslo.db=project%3Aopenstack%<wbr>2Foslo.db&oslo.i18n=project%<wbr>3Aopenstack%2Foslo.i18n&oslo.<wbr>log=project%3Aopenstack%<wbr>2Foslo.log&oslo.messaging=<wbr>project%3Aopenstack%2Foslo.<wbr>messaging&oslo.middleware=<wbr>project%3Aopenstack%2Foslo.<wbr>middleware&oslo.policy=<wbr>project%3Aopenstack%2Foslo.<wbr>policy</a><br>
<br>
------------------------------<wbr>----------<br>
libs_part4<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=%28project%3A%5Eopenstack%2Foslosphinx+OR+project%3Aopenstack%2Foslotest+OR%0Aproject%3Aopenstack%2Fstevedore+OR+project%3Aopenstack%2Ftaskflow+OR%0Aproject%3Aopenstack%2Ftooz+OR+project%3Aopenstack%2Ddev%2Fpbr%29%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+Two%29&oslosphinx=project%3Aopenstack%2Foslosphinx&oslotest=project%3Aopenstack%2Foslotest&osprofiler=project%3Aopenstack%2Fosprofiler&pbr=project%3Aopenstack%2Ddev%2Fpbr&pylockfile=project%3Aopenstack%2Fpylockfile&stevedore=project%3Aopenstack%2Fstevedore&taskflow=project%3Aopenstack%2Ftaskflow&tooz=project%3Aopenstack%2Ftooz" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%<wbr>28project%3A%5Eopenstack%<wbr>2Foslosphinx+OR+project%<wbr>3Aopenstack%2Foslotest+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Fstevedore+OR+project%<wbr>3Aopenstack%2Ftaskflow+OR%<wbr>0Aproject%3Aopenstack%2Ftooz+<wbr>OR+project%3Aopenstack%2Ddev%<wbr>2Fpbr%29%0Astatus%3Aopen+NOT+<wbr>owner%3Aself&title=Oslo+<wbr>Review+Inbox%28Part+Two%29&<wbr>oslosphinx=project%<wbr>3Aopenstack%2Foslosphinx&<wbr>oslotest=project%3Aopenstack%<wbr>2Foslotest&osprofiler=project%<wbr>3Aopenstack%2Fosprofiler&pbr=<wbr>project%3Aopenstack%2Ddev%<wbr>2Fpbr&pylockfile=project%<wbr>3Aopenstack%2Fpylockfile&<wbr>stevedore=project%3Aopenstack%<wbr>2Fstevedore&taskflow=project%<wbr>3Aopenstack%2Ftaskflow&tooz=<wbr>project%3Aopenstack%2Ftooz</a><br>
<br>
------------------------------<wbr>----------<br>
main<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=%28project%3A%5Eopenstack%2Foslo.%2A+OR+project%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Fpylockfile+OR+project%3Aopenstack%2Fcastellan+OR%0Aproject%3Aopenstack%2Ffuturist+OR+project%3Aopenstack%2Fautomaton+OR%0Aproject%3Aopenstack%2Fstevedore+OR+project%3Aopenstack%2Ftaskflow+OR%0Aproject%3Aopenstack%2Ftooz+OR+project%3Aopenstack%2Ddev%2Fcookiecutter+OR%0Aproject%3Aopenstack%2Ddev%2Fpbr+OR+project%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Ddev%2Foslo%2Dcookiecutter+OR+project%3Aopenstack%2Fmox3%29%0Astatus%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%0ANOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself&title=Oslo+Review+Inbox&Oslo+Specs=project%3Aopenstack%2Foslo%2Dspecs&Bug+Fixes=topic%3A%5Ebug%2F.%2A&Blueprints=message%3A%22Blueprint%22&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50&New+Contributors=reviewer%3A10068&Passed+Jenkins%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1+limit%3A50&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%<wbr>28project%3A%5Eopenstack%<wbr>2Foslo.%2A+OR+project%<wbr>3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<wbr>2Fpylockfile+OR+project%<wbr>3Aopenstack%2Fcastellan+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Ffuturist+OR+project%<wbr>3Aopenstack%2Fautomaton+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Fstevedore+OR+project%<wbr>3Aopenstack%2Ftaskflow+OR%<wbr>0Aproject%3Aopenstack%2Ftooz+<wbr>OR+project%3Aopenstack%2Ddev%<wbr>2Fcookiecutter+OR%0Aproject%<wbr>3Aopenstack%2Ddev%2Fpbr+OR+<wbr>project%3Aopenstack%<wbr>2Fdebtcollector+OR%0Aproject%<wbr>3Aopenstack%2Ddev%2Foslo%<wbr>2Dcookiecutter+OR+project%<wbr>3Aopenstack%2Fmox3%29%<wbr>0Astatus%3Aopen+NOT+owner%<wbr>3Aself+NOT+label%3AWorkflow%<wbr>3C%3D%2D1+label%3AVerified%3E%<wbr>3D1%0ANOT+label%3ACode%<wbr>2DReview%3C%3D%2D1%2Cself+NOT+<wbr>label%3ACode%2DReview%3E%3D1%<wbr>2Cself&title=Oslo+Review+<wbr>Inbox&Oslo+Specs=project%<wbr>3Aopenstack%2Foslo%2Dspecs&<wbr>Bug+Fixes=topic%3A%5Ebug%2F.%<wbr>2A&Blueprints=message%3A%<wbr>22Blueprint%22&Needs+Feedback+<wbr>%28Changes+older+than+5+days+<wbr>that+have+not+been+reviewed+<wbr>by+anyone%29=NOT+label%3ACode%<wbr>2DReview%3C%3D2+age%3A5d&You+<wbr>are+a+reviewer%2C+but+haven%<wbr>27t+voted+in+the+current+<wbr>revision=reviewer%3Aself&<wbr>Needs+final+%2B2=label%3ACode%<wbr>2DReview%3E%3D2+limit%3A50&<wbr>New+Contributors=reviewer%<wbr>3A10068&Passed+Jenkins%2C+No+<wbr>Negative+Feedback=NOT+label%<wbr>3ACode%2DReview%3E%3D2+NOT+<wbr>label%3ACode%2DReview%3C%3D%<wbr>2D1+limit%3A50&Wayward+<wbr>Changes+%28Changes+with+no+<wbr>code+review+in+the+last+2days%<wbr>29=NOT+label%3ACode%2DReview%<wbr>3C%3D2+age%3A2d</a><br>
<br>
<br>
--<br>
ChangBo Guo(gcb)<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/8fe59a93/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/8fe59a93/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 24 Apr 2017 08:04:12 -0400<br>
From: Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [tripleo] Final project logo files<br>
Message-ID:<br>
<CACu=<a href="mailto:hytnhQG-4FTjBiONiDOn3rwwdCq3yofa7_nEXz%2BDM8TDYA@mail.gmail.com">hytnhQG-<wbr>4FTjBiONiDOn3rwwdCq3yofa7_<wbr>nEXz+DM8TDYA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Fri, Apr 21, 2017 at 6:06 PM, Heidi Joy Tretheway<br>
<<a href="mailto:heidijoy@openstack.org">heidijoy@openstack.org</a>> wrote:<br>
> Hello TripleO team!<br>
><br>
> Thanks to your input on the last round (which corrected the owls eyes to have a yellow circle, and make the mascot not cross-eyed), we have a final version for your team.<br>
><br>
> Here’s a quick look at the logo:<br>
> <a href="https://www.dropbox.com/s/ejfa7holov7u1g5/OpenStack_Project_Tripleo_vertical.jpg?dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/s/<wbr>ejfa7holov7u1g5/OpenStack_<wbr>Project_Tripleo_vertical.jpg?<wbr>dl=0</a><br>
><br>
> And here’s a folder with all 10 variations:<br>
> <a href="https://www.dropbox.com/sh/zvmw0j1bm14dk6w/AAD2je5lCaB5ZUlLjCjhPlYYa?dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/sh/<wbr>zvmw0j1bm14dk6w/<wbr>AAD2je5lCaB5ZUlLjCjhPlYYa?dl=0</a><br>
><br>
> We’ll post these to a public repo and on <a href="http://openstack.org/project-mascots" rel="noreferrer" target="_blank">openstack.org/project-mascots</a> soon. Thanks again for your input!<br>
<br>
Thank you very much for this work, unless we have more feedback this<br>
week, you can go ahead and push it online!<br>
<br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
<br>
--<br>
Emilien Macchi<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 24 Apr 2017 20:16:50 +0800<br>
From: "Chen CH Ji" <<a href="mailto:jichenjc@cn.ibm.com">jichenjc@cn.ibm.com</a>><br>
To: "OpenStack Development Mailing List \(not for usage questions\)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [nova] about usage of /consoles<br>
Message-ID:<br>
<<a href="mailto:OFA259E5C6.CF9914A3-ON0025810C.00420D54-4825810C.0043758A@notes.na.collabserv.com">OFA259E5C6.CF9914A3-<wbr>ON0025810C.00420D54-4825810C.<wbr>0043758A@notes.na.collabserv.<wbr>com</a>><br>
<br>
Content-Type: text/plain; charset="gb2312"<br>
<br>
Thanks for the info, looks like this is xen only stuff, not sure whether<br>
this is needed for now or we can remove it<br>
remote_consoles seems related to some general console but not specific to<br>
xvp,<br>
<br>
so <a href="https://review.openstack.org/459266" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>459266</a> just for some info to api reader and<br>
if we are sure xen don't use it any more, we can remove it totally.<br>
<br>
Best Regards!<br>
<br>
Kevin (Chen) Ji 纪 晨<br>
<br>
Engineer, zVM Development, CSTL<br>
Notes: Chen CH Ji/China/IBM@IBMCN Internet: <a href="mailto:jichenjc@cn.ibm.com">jichenjc@cn.ibm.com</a><br>
Phone: <a href="tel:%2B86-10-82451493" value="+861082451493">+86-10-82451493</a><br>
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,<br>
Beijing 100193, PRC<br>
<br>
<br>
<br>
From: Markus Zoeller <<a href="mailto:mzoeller@linux.vnet.ibm.com">mzoeller@linux.vnet.ibm.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
Date: 04/21/2017 08:35 PM<br>
Subject: Re: [openstack-dev] [nova] about usage of /consoles<br>
<br>
<br>
<br>
On <a href="tel:21.04.2017%2012" value="+12104201712">21.04.2017 12</a>:12, Chen CH Ji wrote:<br>
><br>
> Per <a href="https://bugs.launchpad.net/nova/+bug/1682303" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>nova/+bug/1682303</a> , POST with return 200<br>
> while GET returns [] is weird<br>
> what's the purpose of /consoles? looks like<br>
> <a href="https://github.com/openstack/nova/blob/master/nova/console/rpcapi.py#L72" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/console/<wbr>rpcapi.py#L72</a><br>
> will send a rpc message and which service is the reciever of this message<br>
> and handle it? Thanks<br>
><br>
> Best Regards!<br>
><br>
> Kevin (Chen) Ji 纪 晨<br>
<br>
Looks like this API works for the "Xen VNC proxy" service only. The<br>
console manager triggers the console creation here:<br>
<a href="https://github.com/openstack/nova/blob/66c661258873e2544e286099c4bc027c26c851c4/nova/console/manager.py#L79" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/<wbr>66c661258873e2544e286099c4bc02<wbr>7c26c851c4/nova/console/<wbr>manager.py#L79</a><br>
<br>
<br>
The XVPConsoleProxy implements it here:<br>
<a href="https://github.com/openstack/nova/blob/46b3a3ca1ac3a5ffdc7c5420263223f2d3b9a660/nova/console/xvp.py#L56-L58" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/<wbr>46b3a3ca1ac3a5ffdc7c5420263223<wbr>f2d3b9a660/nova/console/xvp.<wbr>py#L56-L58</a><br>
<br>
<br>
Looks like that service runs with default Devstack settings as service<br>
"nova-xvpvncproxy":<br>
<a href="https://github.com/openstack-dev/devstack/blob/f3b2f4c85307b14f115a020f5eaf6c92026b55b4/lib/nova#L892-L892" rel="noreferrer" target="_blank">https://github.com/openstack-<wbr>dev/devstack/blob/<wbr>f3b2f4c85307b14f115a020f5eaf6c<wbr>92026b55b4/lib/nova#L892-L892</a><br>
<br>
<br>
The API microversion 2.6 introduced a consolidation of the remote consoles:<br>
<a href="https://github.com/openstack/nova/blob/3e032fd45be28c6098235ce336e675d03ebc6619/nova/api/openstack/compute/schemas/remote_consoles.py#L101-L102" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/<wbr>3e032fd45be28c6098235ce336e675<wbr>d03ebc6619/nova/api/openstack/<wbr>compute/schemas/remote_<wbr>consoles.py#L101-L102</a><br>
<br>
<br>
Could it be that the "GET /console" API shouldn't be available anymore<br>
since microversion 2.6?<br>
<br>
api-ref about the consoles:<br>
<a href="https://developer.openstack.org/api-ref/compute/?expanded=get-vnc-console-os-getvncconsole-action-deprecated-detail,create-remote-console-detail" rel="noreferrer" target="_blank">https://developer.openstack.<wbr>org/api-ref/compute/?expanded=<wbr>get-vnc-console-os-<wbr>getvncconsole-action-<wbr>deprecated-detail,create-<wbr>remote-console-detail</a><br>
<br>
<br>
--<br>
Regards, Markus Zoeller (markus_z)<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/3066d620/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/3066d620/<wbr>attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: graycol.gif<br>
Type: image/gif<br>
Size: 105 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/3066d620/attachment-0001.gif" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/3066d620/<wbr>attachment-0001.gif</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 24 Apr 2017 12:47:25 +0000<br>
From: "Morales, Victor" <<a href="mailto:victor.morales@intel.com">victor.morales@intel.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [tricircle]mascot for the Tricircle<br>
project<br>
Message-ID: <<a href="mailto:FB94B956-E4A8-4EA1-8B21-7C6A12F6EC81@intel.com">FB94B956-E4A8-4EA1-8B21-<wbr>7C6A12F6EC81@intel.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
+1<br>
<br>
From: Zhipeng Huang <<a href="mailto:zhipengh512@gmail.com">zhipengh512@gmail.com</a>><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Date: Monday, April 24, 2017 at 3:06 AM<br>
To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [tricircle]mascot for the Tricircle project<br>
<br>
perfect XD<br>
<br>
On Mon, Apr 24, 2017 at 2:59 PM, joehuang <<a href="mailto:joehuang@huawei.com">joehuang@huawei.com</a><mailto:<a href="mailto:joehuang@huawei.com">jo<wbr>ehuang@huawei.com</a>>> wrote:<br>
Hello, team,<br>
<br>
What about the mascot of Tricircle project?<br>
<br>
Your comments are welcome.<br>
<br>
Best Regards<br>
Chaoyi Huang(joehuang)<br>
<br>
<br>
From: Heidi Joy Tretheway [<a href="mailto:heidijoy@openstack.org">heidijoy@openstack.org</a><<wbr>mailto:<a href="mailto:heidijoy@openstack.org">heidijoy@openstack.org</a>><wbr>]<br>
Sent: 22 April 2017 6:15<br>
To: joehuang<br>
Subject: Re: Question about the Tricircle mascot<br>
Hi Joe,<br>
Following up on your team’s mascot request, our illustrators came back with a beautiful piece. Would you please let me know what your team thinks?<br>
<br>
[cid:image001.png@01D2BCCF.<wbr>02FAD1D0]<br>
<br>
<br>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-<wbr>dev-request@lists.openstack.<wbr>org?subject:unsubscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
<br>
--<br>
Zhipeng (Howard) Huang<br>
<br>
Standard Engineer<br>
IT Standard & Patent/IT Product Line<br>
Huawei Technologies Co,. Ltd<br>
Email: <a href="mailto:huangzhipeng@huawei.com">huangzhipeng@huawei.com</a><<wbr>mailto:<a href="mailto:huangzhipeng@huawei.com">huangzhipeng@huawei.com</a><wbr>><br>
Office: Huawei Industrial Base, Longgang, Shenzhen<br>
<br>
(Previous)<br>
Research Assistant<br>
Mobile Ad-Hoc Network Lab, Calit2<br>
University of California, Irvine<br>
Email: <a href="mailto:zhipengh@uci.edu">zhipengh@uci.edu</a><mailto:<a href="mailto:zhipengh@uci.edu">zhipen<wbr>gh@uci.edu</a>><br>
Office: Calit2 Building Room 2402<br>
<br>
OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/55c1178e/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/55c1178e/<wbr>attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.png<br>
Type: image/png<br>
Size: 25027 bytes<br>
Desc: image001.png<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/55c1178e/attachment-0001.png" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/55c1178e/<wbr>attachment-0001.png</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 24 Apr 2017 16:08:20 +0300<br>
From: Juan Antonio Osorio <<a href="mailto:jaosorior@gmail.com">jaosorior@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] [mistral][tripleo] mistralclient release<br>
needed<br>
Message-ID:<br>
<CAG=EsMOroag9oV=0ggdP_ZN=<a href="mailto:p505K83ZaDL5Pz%2B7_OMStirrJA@mail.gmail.com">p505<wbr>K83ZaDL5Pz+7_OMStirrJA@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hey,<br>
<br>
We're trying to migrate the undercloud to use keystone v3. But we're<br>
currently blocked by having an older version of mistralclient available. We<br>
would really use a release to move forward.<br>
<br>
For reference, this is the commit we need to use in mistralclient<br>
<a href="https://github.com/openstack/python-mistralclient/commit/83b3d0d39cb8072682fac74f6a40877030e91c18" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>python-mistralclient/commit/<wbr>83b3d0d39cb8072682fac74f6a4087<wbr>7030e91c18</a><br>
<br>
And this is the commit that's attempting to migrate to keystone v3 in<br>
tripleo: <a href="https://review.openstack.org/#/c/446752/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/446752/</a><br>
<br>
--<br>
Juan Antonio Osorio R.<br>
e-mail: <a href="mailto:jaosorior@gmail.com">jaosorior@gmail.com</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/4aa12ff7/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/4aa12ff7/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Mon, 24 Apr 2017 08:21:02 -0500<br>
From: Melvin Hillsman <<a href="mailto:mrhillsman@gmail.com">mrhillsman@gmail.com</a>><br>
To: OpenStack Operators <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.<wbr>openstack.org</a>>,<br>
OpenStack Mailing List <<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><wbr>>, OpenStack Dev<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] Ops Team Meeting 042417 Canceled<br>
Message-ID:<br>
<<a href="mailto:CAMVtB2HLk2UhXDTNoOwZdHdke%2BpfXOsoZ7tgwLWNVjdtYJfWxA@mail.gmail.com">CAMVtB2HLk2UhXDTNoOwZdHdke+<wbr>pfXOsoZ7tgwLWNVjdtYJfWxA@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hey everyone,<br>
<br>
Apologies for the late notice. Unless someone can facilitate the ops team<br>
meeting we will have to cancel for today:<br>
<br>
<a href="http://eavesdrop.openstack.org/#OpenStack_OSOps_Team" rel="noreferrer" target="_blank">http://eavesdrop.openstack.<wbr>org/#OpenStack_OSOps_Team</a><br>
<br>
--<br>
Kind regards,<br>
<br>
Melvin Hillsman<br>
OpenStack Engineer, Rackspace<br>
<br>
<a href="mailto:mrhillsman@gmail.com">mrhillsman@gmail.com</a><br>
phone: <a href="tel:%28210%29%20312-1267" value="+12103121267">(210) 312-1267</a><br>
mobile: <a href="tel:%28210%29%20413-1659" value="+12104131659">(210) 413-1659</a><br>
<a href="http://rackspace.com" rel="noreferrer" target="_blank">http://rackspace.com</a><br>
<br>
Learner | Ideation | Belief | Responsibility | Command<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/c83f9d29/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/c83f9d29/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Mon, 24 Apr 2017 13:30:40 +0000<br>
From: "Loo, Ruby" <<a href="mailto:ruby.loo@intel.com">ruby.loo@intel.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [ironic] New mascot design<br>
Message-ID: <<a href="mailto:6BAF8589-72B2-4AAE-902F-6B6D7DE0AFFD@intel.com">6BAF8589-72B2-4AAE-902F-<wbr>6B6D7DE0AFFD@intel.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thank you Heidi!<br>
<br>
> Long live Pixie Boots!<br>
<br>
May (s)he reign forever :D<br>
<br>
--ruby<br>
<br>
From: Heidi Joy Tretheway <<a href="mailto:heidijoy@openstack.org">heidijoy@openstack.org</a>><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Date: Friday, April 21, 2017 at 6:02 PM<br>
To: "<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] [ironic] New mascot design<br>
<br>
Hello Ironic team,<br>
Thanks for your comments on the last round. Here is the latest Pixie Boots mascot (in every variation) ready for your downloading pleasure. We’ll also be updating these to a public repo and to <a href="http://openstack.org/project-mascots" rel="noreferrer" target="_blank">openstack.org/project-mascots</a>, but please be patient as our fab web team is slammed with Summit stuff.<br>
<br>
Here’s a quick look at the mascot:<br>
<a href="https://www.dropbox.com/s/qf8lent6ncpq0ip/OpenStack_Project_Ironic_vertical.jpg?dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/s/<wbr>qf8lent6ncpq0ip/OpenStack_<wbr>Project_Ironic_vertical.jpg?<wbr>dl=0</a><br>
<br>
And here’s a dropbox with all 10 versions:<br>
<a href="https://www.dropbox.com/sh/w14cufsymu9hxiw/AAA5eJTW42AC-C0qPkMi4i1ra?dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/sh/<wbr>w14cufsymu9hxiw/AAA5eJTW42AC-<wbr>C0qPkMi4i1ra?dl=0</a><br>
<br>
Long live Pixie Boots!<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.<wbr>openstack.org</a><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack<wbr>-dev-request@lists.openstack.<wbr>org</a>>?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/55b4011e/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/55b4011e/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Mon, 24 Apr 2017 21:33:39 +0800<br>
From: ChangBo Guo <<a href="mailto:glongwave@gmail.com">glongwave@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [oslo] Update Review dashboard links<br>
Message-ID:<br>
<CANWmB0W7J_<wbr>PHcnz4CtcH02JLH4Opu2tkgFnazB=<a href="mailto:D4LmqYe8LEA@mail.gmail.com">D<wbr>4LmqYe8LEA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
There is tinny update the latest links are:<br>
<br>
libs_part1<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=%28project%3A%5Eopenstack%2Foslo.%2A+OR+project%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Fcastellan+OR+project%3Aopenstack%2Ffuturist+OR%0Aproject%3Aopenstack%2Fautomaton+OR+project%3Aopenstack%2Ddev%2Fcookiecutter+OR%0Aproject%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Ddev%2Foslo%2Dcookiecutter+OR+project%3Aopenstack%2Fmox3%29%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+One%29&Oslo+Specs=project%3Aopenstack%2Foslo%2Dspecs&automaton=project%3Aopenstack%2Fautomaton&castellan=project%3Aopenstack%2Fcastellan&cookiecutter=project%3Aopenstack%2Ddev%2Fcookiecutter&debtcollector=project%3Aopenstack%2Fdebtcollector&futurist=project%3Aopenstack%2Ffuturist&mox3=project%3Aopenstack%2Fmox3&oslo%2Dcookiecutter=project%3Aopenstack%2Ddev%2Foslo%2Dcookiecutter&oslo.cache=project%3Aopenstack%2Foslo.cache" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%<wbr>28project%3A%5Eopenstack%<wbr>2Foslo.%2A+OR+project%<wbr>3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<wbr>2Fcastellan+OR+project%<wbr>3Aopenstack%2Ffuturist+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Fautomaton+OR+project%<wbr>3Aopenstack%2Ddev%<wbr>2Fcookiecutter+OR%0Aproject%<wbr>3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<wbr>2Ddev%2Foslo%2Dcookiecutter+<wbr>OR+project%3Aopenstack%2Fmox3%<wbr>29%0Astatus%3Aopen+NOT+owner%<wbr>3Aself&title=Oslo+Review+<wbr>Inbox%28Part+One%29&Oslo+<wbr>Specs=project%3Aopenstack%<wbr>2Foslo%2Dspecs&automaton=<wbr>project%3Aopenstack%<wbr>2Fautomaton&castellan=project%<wbr>3Aopenstack%2Fcastellan&<wbr>cookiecutter=project%<wbr>3Aopenstack%2Ddev%<wbr>2Fcookiecutter&debtcollector=<wbr>project%3Aopenstack%<wbr>2Fdebtcollector&futurist=<wbr>project%3Aopenstack%<wbr>2Ffuturist&mox3=project%<wbr>3Aopenstack%2Fmox3&oslo%<wbr>2Dcookiecutter=project%<wbr>3Aopenstack%2Ddev%2Foslo%<wbr>2Dcookiecutter&oslo.cache=<wbr>project%3Aopenstack%2Foslo.<wbr>cache</a><br>
<br>
------------------------------<wbr>----------<br>
libs_part2<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=project%3A%5Eopenstack%2Foslo.%2A%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+Two%29&oslo.privsep=project%3Aopenstack%2Foslo.privsep&oslo.reports=project%3Aopenstack%2Foslo.reports&oslo.rootwrap=project%3Aopenstack%2Foslo.rootwrap&oslo.serialization=project%3Aopenstack%2Foslo.serialization&oslo.service=project%3Aopenstack%2Foslo.service&oslo.tools=project%3Aopenstack%2Foslo.tools&oslo.utils=project%3Aopenstack%2Foslo.utils&oslo.versionedobjects=project%3Aopenstack%2Foslo.versionedobjects&oslo.vmware=project%3Aopenstack%2Foslo.vmware" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=project%<wbr>3A%5Eopenstack%2Foslo.%2A%<wbr>0Astatus%3Aopen+NOT+owner%<wbr>3Aself&title=Oslo+Review+<wbr>Inbox%28Part+Two%29&oslo.<wbr>privsep=project%3Aopenstack%<wbr>2Foslo.privsep&oslo.reports=<wbr>project%3Aopenstack%2Foslo.<wbr>reports&oslo.rootwrap=project%<wbr>3Aopenstack%2Foslo.rootwrap&<wbr>oslo.serialization=project%<wbr>3Aopenstack%2Foslo.<wbr>serialization&oslo.service=<wbr>project%3Aopenstack%2Foslo.<wbr>service&oslo.tools=project%<wbr>3Aopenstack%2Foslo.tools&oslo.<wbr>utils=project%3Aopenstack%<wbr>2Foslo.utils&oslo.<wbr>versionedobjects=project%<wbr>3Aopenstack%2Foslo.<wbr>versionedobjects&oslo.vmware=<wbr>project%3Aopenstack%2Foslo.<wbr>vmware</a><br>
<br>
------------------------------<wbr>----------<br>
libs_part3<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=project%3A%5Eopenstack%2Foslo.%2A%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+Three%29&oslo.concurrency=project%3Aopenstack%2Foslo.concurrency&oslo.config=project%3Aopenstack%2Foslo.config&oslo.context=project%3Aopenstack%2Foslo.context&oslo.db=project%3Aopenstack%2Foslo.db&oslo.i18n=project%3Aopenstack%2Foslo.i18n&oslo.log=project%3Aopenstack%2Foslo.log&oslo.messaging=project%3Aopenstack%2Foslo.messaging&oslo.middleware=project%3Aopenstack%2Foslo.middleware&oslo.policy=project%3Aopenstack%2Foslo.policy" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=project%<wbr>3A%5Eopenstack%2Foslo.%2A%<wbr>0Astatus%3Aopen+NOT+owner%<wbr>3Aself&title=Oslo+Review+<wbr>Inbox%28Part+Three%29&oslo.<wbr>concurrency=project%<wbr>3Aopenstack%2Foslo.<wbr>concurrency&oslo.config=<wbr>project%3Aopenstack%2Foslo.<wbr>config&oslo.context=project%<wbr>3Aopenstack%2Foslo.context&<wbr>oslo.db=project%3Aopenstack%<wbr>2Foslo.db&oslo.i18n=project%<wbr>3Aopenstack%2Foslo.i18n&oslo.<wbr>log=project%3Aopenstack%<wbr>2Foslo.log&oslo.messaging=<wbr>project%3Aopenstack%2Foslo.<wbr>messaging&oslo.middleware=<wbr>project%3Aopenstack%2Foslo.<wbr>middleware&oslo.policy=<wbr>project%3Aopenstack%2Foslo.<wbr>policy</a><br>
<br>
------------------------------<wbr>----------<br>
libs_part4<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=%28project%3A%5Eopenstack%2Foslosphinx+OR+project%3Aopenstack%2Foslotest+OR%0Aproject%3Aopenstack%2Fstevedore+OR+project%3Aopenstack%2Ftaskflow+OR%0Aproject%3Aopenstack%2Ftooz+OR+project%3Aopenstack%2Ddev%2Fpbr%29%0Astatus%3Aopen+NOT+owner%3Aself&title=Oslo+Review+Inbox%28Part+Four%29&oslosphinx=project%3Aopenstack%2Foslosphinx&oslotest=project%3Aopenstack%2Foslotest&osprofiler=project%3Aopenstack%2Fosprofiler&pbr=project%3Aopenstack%2Ddev%2Fpbr&pylockfile=project%3Aopenstack%2Fpylockfile&stevedore=project%3Aopenstack%2Fstevedore&taskflow=project%3Aopenstack%2Ftaskflow&tooz=project%3Aopenstack%2Ftooz" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%<wbr>28project%3A%5Eopenstack%<wbr>2Foslosphinx+OR+project%<wbr>3Aopenstack%2Foslotest+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Fstevedore+OR+project%<wbr>3Aopenstack%2Ftaskflow+OR%<wbr>0Aproject%3Aopenstack%2Ftooz+<wbr>OR+project%3Aopenstack%2Ddev%<wbr>2Fpbr%29%0Astatus%3Aopen+NOT+<wbr>owner%3Aself&title=Oslo+<wbr>Review+Inbox%28Part+Four%29&<wbr>oslosphinx=project%<wbr>3Aopenstack%2Foslosphinx&<wbr>oslotest=project%3Aopenstack%<wbr>2Foslotest&osprofiler=project%<wbr>3Aopenstack%2Fosprofiler&pbr=<wbr>project%3Aopenstack%2Ddev%<wbr>2Fpbr&pylockfile=project%<wbr>3Aopenstack%2Fpylockfile&<wbr>stevedore=project%3Aopenstack%<wbr>2Fstevedore&taskflow=project%<wbr>3Aopenstack%2Ftaskflow&tooz=<wbr>project%3Aopenstack%2Ftooz</a><br>
<br>
------------------------------<wbr>----------<br>
main<br>
------------------------------<wbr>----------<br>
<a href="https://review.openstack.org/#/dashboard/?foreach=%28project%3A%5Eopenstack%2Foslo.%2A+OR+project%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Fpylockfile+OR+project%3Aopenstack%2Fcastellan+OR%0Aproject%3Aopenstack%2Ffuturist+OR+project%3Aopenstack%2Fautomaton+OR%0Aproject%3Aopenstack%2Fstevedore+OR+project%3Aopenstack%2Ftaskflow+OR%0Aproject%3Aopenstack%2Ftooz+OR+project%3Aopenstack%2Ddev%2Fcookiecutter+OR%0Aproject%3Aopenstack%2Ddev%2Fpbr+OR+project%3Aopenstack%2Fdebtcollector+OR%0Aproject%3Aopenstack%2Ddev%2Foslo%2Dcookiecutter+OR+project%3Aopenstack%2Fmox3%29%0Astatus%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%0ANOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself&title=Oslo+Review+Inbox&Oslo+Specs=project%3Aopenstack%2Foslo%2Dspecs&Bug+Fixes=topic%3A%5Ebug%2F.%2A&Blueprints=message%3A%22Blueprint%22&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50&New+Contributors=reviewer%3A10068&Passed+Jenkins%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1+limit%3A50&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%<wbr>28project%3A%5Eopenstack%<wbr>2Foslo.%2A+OR+project%<wbr>3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<wbr>2Fpylockfile+OR+project%<wbr>3Aopenstack%2Fcastellan+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Ffuturist+OR+project%<wbr>3Aopenstack%2Fautomaton+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Fstevedore+OR+project%<wbr>3Aopenstack%2Ftaskflow+OR%<wbr>0Aproject%3Aopenstack%2Ftooz+<wbr>OR+project%3Aopenstack%2Ddev%<wbr>2Fcookiecutter+OR%0Aproject%<wbr>3Aopenstack%2Ddev%2Fpbr+OR+<wbr>project%3Aopenstack%<wbr>2Fdebtcollector+OR%0Aproject%<wbr>3Aopenstack%2Ddev%2Foslo%<wbr>2Dcookiecutter+OR+project%<wbr>3Aopenstack%2Fmox3%29%<wbr>0Astatus%3Aopen+NOT+owner%<wbr>3Aself+NOT+label%3AWorkflow%<wbr>3C%3D%2D1+label%3AVerified%3E%<wbr>3D1%0ANOT+label%3ACode%<wbr>2DReview%3C%3D%2D1%2Cself+NOT+<wbr>label%3ACode%2DReview%3E%3D1%<wbr>2Cself&title=Oslo+Review+<wbr>Inbox&Oslo+Specs=project%<wbr>3Aopenstack%2Foslo%2Dspecs&<wbr>Bug+Fixes=topic%3A%5Ebug%2F.%<wbr>2A&Blueprints=message%3A%<wbr>22Blueprint%22&Needs+Feedback+<wbr>%28Changes+older+than+5+days+<wbr>that+have+not+been+reviewed+<wbr>by+anyone%29=NOT+label%3ACode%<wbr>2DReview%3C%3D2+age%3A5d&You+<wbr>are+a+reviewer%2C+but+haven%<wbr>27t+voted+in+the+current+<wbr>revision=reviewer%3Aself&<wbr>Needs+final+%2B2=label%3ACode%<wbr>2DReview%3E%3D2+limit%3A50&<wbr>New+Contributors=reviewer%<wbr>3A10068&Passed+Jenkins%2C+No+<wbr>Negative+Feedback=NOT+label%<wbr>3ACode%2DReview%3E%3D2+NOT+<wbr>label%3ACode%2DReview%3C%3D%<wbr>2D1+limit%3A50&Wayward+<wbr>Changes+%28Changes+with+no+<wbr>code+review+in+the+last+2days%<wbr>29=NOT+label%3ACode%2DReview%<wbr>3C%3D2+age%3A2d</a><br>
<br>
<br>
2017-04-24 20:04 GMT+08:00 ChangBo Guo <<a href="mailto:glongwave@gmail.com">glongwave@gmail.com</a>>:<br>
<br>
> I just posted a update of our Review dashboard config files in<br>
> <a href="https://review.openstack.org/#/c/459247/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/459247/</a>.<br>
> the main.dash was copied from oslo-incubator with adding missing<br>
> libraries.<br>
> I must divid 35 libraries into 4 groups becuase each dashboard allows up<br>
> to 10 queries.<br>
><br>
><br>
> The output can be used directly , hope this will be useful.<br>
><br>
> # ./build_dashboards.sh /home/changboguo/code/os/<wbr>gerrit-dash-creator<br>
> /home/changboguo/code/os/oslo.<wbr>tools/dashboards/<br>
><br>
> ------------------------------<wbr>----------<br>
> libs_part1<br>
> ------------------------------<wbr>----------<br>
> <a href="https://review.openstack.org/#/dashboard/?foreach=%" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%</a><br>
> 28project%3A%5Eopenstack%<wbr>2Foslo.%2A+OR+project%<br>
> 3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<br>
> 2Fcastellan+OR+project%<wbr>3Aopenstack%2Ffuturist+OR%<wbr>0Aproject%3Aopenstack%<br>
> 2Fautomaton+OR+project%<wbr>3Aopenstack%2Ddev%<wbr>2Fcookiecutter+OR%0Aproject%<br>
> 3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<br>
> 2Ddev%2Foslo%2Dcookiecutter+<wbr>OR+project%3Aopenstack%2Fmox3%<br>
> 29%0Astatus%3Aopen+NOT+owner%<wbr>3Aself&title=Oslo+Review+<br>
> Inbox%28Part+One%29&Oslo+<wbr>Specs=project%3Aopenstack%<br>
> 2Foslo%2Dspecs&automaton=<wbr>project%3Aopenstack%<br>
> 2Fautomaton&castellan=project%<wbr>3Aopenstack%2Fcastellan&<br>
> cookiecutter=project%<wbr>3Aopenstack%2Ddev%<wbr>2Fcookiecutter&debtcollector=<br>
> project%3Aopenstack%<wbr>2Fdebtcollector&futurist=<wbr>project%3Aopenstack%<br>
> 2Ffuturist&mox3=project%<wbr>3Aopenstack%2Fmox3&oslo%<wbr>2Dcookiecutter=project%<br>
> 3Aopenstack%2Ddev%<wbr>2Fcookiecutter&oslo.cache=<wbr>project%3Aopenstack%2Foslo.<br>
> cache<br>
><br>
> ------------------------------<wbr>----------<br>
> libs_part2<br>
> ------------------------------<wbr>----------<br>
> <a href="https://review.openstack.org/#/dashboard/?foreach=project%" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=project%</a><br>
> 3A%5Eopenstack%2Foslo.%2A%<wbr>0Astatus%3Aopen+NOT+owner%<br>
> 3Aself&title=Oslo+Review+<wbr>Inbox%28Part+Two%29&oslo.<br>
> privsep=project%3Aopenstack%<wbr>2Foslo.privsep&oslo.reports=<br>
> project%3Aopenstack%2Foslo.<wbr>reports&oslo.rootwrap=project%<br>
> 3Aopenstack%2Foslo.rootwrap&<wbr>oslo.serialization=project%<wbr>3Aopenstack%2Foslo.<br>
> serialization&oslo.service=<wbr>project%3Aopenstack%2Foslo.<br>
> service&oslo.tools=project%<wbr>3Aopenstack%2Foslo.tools&oslo.<br>
> utils=project%3Aopenstack%<wbr>2Foslo.utils&oslo.<wbr>versionedobjects=project%<br>
> 3Aopenstack%2Foslo.<wbr>versionedobjects&oslo.vmware=<br>
> project%3Aopenstack%2Foslo.<wbr>vmware<br>
><br>
> ------------------------------<wbr>----------<br>
> libs_part3<br>
> ------------------------------<wbr>----------<br>
> <a href="https://review.openstack.org/#/dashboard/?foreach=project%" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=project%</a><br>
> 3A%5Eopenstack%2Foslo.%2A%<wbr>0Astatus%3Aopen+NOT+owner%<br>
> 3Aself&title=Oslo+Review+<wbr>Inbox%28Part+Three%29&oslo.<wbr>concurrency=project%<br>
> 3Aopenstack%2Foslo.<wbr>concurrency&oslo.config=<wbr>project%3Aopenstack%2Foslo.<br>
> config&oslo.context=project%<wbr>3Aopenstack%2Foslo.context&<br>
> oslo.db=project%3Aopenstack%<wbr>2Foslo.db&oslo.i18n=project%<br>
> 3Aopenstack%2Foslo.i18n&oslo.<wbr>log=project%3Aopenstack%<br>
> 2Foslo.log&oslo.messaging=<wbr>project%3Aopenstack%2Foslo.<br>
> messaging&oslo.middleware=<wbr>project%3Aopenstack%2Foslo.<br>
> middleware&oslo.policy=<wbr>project%3Aopenstack%2Foslo.<wbr>policy<br>
><br>
> ------------------------------<wbr>----------<br>
> libs_part4<br>
> ------------------------------<wbr>----------<br>
> <a href="https://review.openstack.org/#/dashboard/?foreach=%" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%</a><br>
> 28project%3A%5Eopenstack%<wbr>2Foslosphinx+OR+project%<br>
> 3Aopenstack%2Foslotest+OR%<wbr>0Aproject%3Aopenstack%<wbr>2Fstevedore+OR+project%<br>
> 3Aopenstack%2Ftaskflow+OR%<wbr>0Aproject%3Aopenstack%2Ftooz+<br>
> OR+project%3Aopenstack%2Ddev%<wbr>2Fpbr%29%0Astatus%3Aopen+NOT+<br>
> owner%3Aself&title=Oslo+<wbr>Review+Inbox%28Part+Two%29&<wbr>oslosphinx=project%<br>
> 3Aopenstack%2Foslosphinx&<wbr>oslotest=project%3Aopenstack%<br>
> 2Foslotest&osprofiler=project%<wbr>3Aopenstack%2Fosprofiler&pbr=<br>
> project%3Aopenstack%2Ddev%<wbr>2Fpbr&pylockfile=project%<br>
> 3Aopenstack%2Fpylockfile&<wbr>stevedore=project%3Aopenstack%<br>
> 2Fstevedore&taskflow=project%<wbr>3Aopenstack%2Ftaskflow&tooz=<br>
> project%3Aopenstack%2Ftooz<br>
><br>
> ------------------------------<wbr>----------<br>
> main<br>
> ------------------------------<wbr>----------<br>
> <a href="https://review.openstack.org/#/dashboard/?foreach=%" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/dashboard/?foreach=%</a><br>
> 28project%3A%5Eopenstack%<wbr>2Foslo.%2A+OR+project%<br>
> 3Aopenstack%2Fdebtcollector+<wbr>OR%0Aproject%3Aopenstack%<br>
> 2Fpylockfile+OR+project%<wbr>3Aopenstack%2Fcastellan+OR%<wbr>0Aproject%3Aopenstack%<br>
> 2Ffuturist+OR+project%<wbr>3Aopenstack%2Fautomaton+OR%<wbr>0Aproject%3Aopenstack%<br>
> 2Fstevedore+OR+project%<wbr>3Aopenstack%2Ftaskflow+OR%<br>
> 0Aproject%3Aopenstack%2Ftooz+<wbr>OR+project%3Aopenstack%2Ddev%<br>
> 2Fcookiecutter+OR%0Aproject%<wbr>3Aopenstack%2Ddev%2Fpbr+OR+<br>
> project%3Aopenstack%<wbr>2Fdebtcollector+OR%0Aproject%<wbr>3Aopenstack%2Ddev%2Foslo%<br>
> 2Dcookiecutter+OR+project%<wbr>3Aopenstack%2Fmox3%29%<wbr>0Astatus%3Aopen+NOT+owner%<br>
> 3Aself+NOT+label%3AWorkflow%<wbr>3C%3D%2D1+label%3AVerified%3E%<br>
> 3D1%0ANOT+label%3ACode%<wbr>2DReview%3C%3D%2D1%2Cself+NOT+<br>
> label%3ACode%2DReview%3E%3D1%<wbr>2Cself&title=Oslo+Review+<br>
> Inbox&Oslo+Specs=project%<wbr>3Aopenstack%2Foslo%2Dspecs&<br>
> Bug+Fixes=topic%3A%5Ebug%2F.%<wbr>2A&Blueprints=message%3A%<br>
> 22Blueprint%22&Needs+Feedback+<wbr>%28Changes+older+than+5+days+<br>
> that+have+not+been+reviewed+<wbr>by+anyone%29=NOT+label%3ACode%<br>
> 2DReview%3C%3D2+age%3A5d&You+<wbr>are+a+reviewer%2C+but+haven%<br>
> 27t+voted+in+the+current+<wbr>revision=reviewer%3Aself&<br>
> Needs+final+%2B2=label%3ACode%<wbr>2DReview%3E%3D2+limit%3A50&<br>
> New+Contributors=reviewer%<wbr>3A10068&Passed+Jenkins%2C+No+<br>
> Negative+Feedback=NOT+label%<wbr>3ACode%2DReview%3E%3D2+NOT+<br>
> label%3ACode%2DReview%3C%3D%<wbr>2D1+limit%3A50&Wayward+<br>
> Changes+%28Changes+with+no+<wbr>code+review+in+the+last+2days%<br>
> 29=NOT+label%3ACode%2DReview%<wbr>3C%3D2+age%3A2d<br>
><br>
><br>
> --<br>
> ChangBo Guo(gcb)<br>
><br>
<br>
<br>
<br>
--<br>
ChangBo Guo(gcb)<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/d81eeaa2/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/d81eeaa2/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Mon, 24 Apr 2017 15:42:09 +0200<br>
From: Carlos Camacho Gonzalez <<a href="mailto:ccamacho@redhat.com">ccamacho@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [tripleo] Final project logo files<br>
Message-ID:<br>
<CANYJBfYjS0-NzE79==<a href="mailto:mUNj02pJRbthLKSiARUXOgG9PocuTRRQ@mail.gmail.com">mUNj02pJRb<wbr>thLKSiARUXOgG9PocuTRRQ@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thank you all!<br>
<br>
On Mon, Apr 24, 2017 at 2:04 PM, Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>> wrote:<br>
<br>
> On Fri, Apr 21, 2017 at 6:06 PM, Heidi Joy Tretheway<br>
> <<a href="mailto:heidijoy@openstack.org">heidijoy@openstack.org</a>> wrote:<br>
> > Hello TripleO team!<br>
> ><br>
> > Thanks to your input on the last round (which corrected the owls eyes to<br>
> have a yellow circle, and make the mascot not cross-eyed), we have a final<br>
> version for your team.<br>
> ><br>
> > Here’s a quick look at the logo:<br>
> > <a href="https://www.dropbox.com/s/ejfa7holov7u1g5/OpenStack_" rel="noreferrer" target="_blank">https://www.dropbox.com/s/<wbr>ejfa7holov7u1g5/OpenStack_</a><br>
> Project_Tripleo_vertical.jpg?<wbr>dl=0<br>
> ><br>
> > And here’s a folder with all 10 variations:<br>
> > <a href="https://www.dropbox.com/sh/zvmw0j1bm14dk6w/" rel="noreferrer" target="_blank">https://www.dropbox.com/sh/<wbr>zvmw0j1bm14dk6w/</a><br>
> AAD2je5lCaB5ZUlLjCjhPlYYa?dl=0<br>
> ><br>
> > We’ll post these to a public repo and on <a href="http://openstack.org/project-mascots" rel="noreferrer" target="_blank">openstack.org/project-mascots</a><br>
> soon. Thanks again for your input!<br>
><br>
> Thank you very much for this work, unless we have more feedback this<br>
> week, you can go ahead and push it online!<br>
><br>
> ><br>
> > ______________________________<wbr>______________________________<br>
> ______________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject</a>:<br>
> unsubscribe<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
><br>
><br>
> --<br>
> Emilien Macchi<br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/fd53d28c/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/fd53d28c/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Mon, 24 Apr 2017 13:45:07 +0000<br>
From: "Jadhav, Pooja" <<a href="mailto:Pooja.Jadhav@nttdata.com">Pooja.Jadhav@nttdata.com</a>><br>
To: "<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID:<br>
<<a href="mailto:MWHPR1201MB0208AE99AC59222103A81C0A8E1F0@MWHPR1201MB0208.namprd12.prod.outlook.com">MWHPR1201MB0208AE99AC59222103<wbr>A81C0A8E1F0@MWHPR1201MB0208.<wbr>namprd12.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Devs,<br>
<br>
I want your opinion about bug: <a href="https://bugs.launchpad.net/nova/+bug/1680130" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>nova/+bug/1680130</a><br>
<br>
When user passes incorrect formatted UUID, volume UUID like: 11111111-2222-4444-5555--<wbr>666666666666(please note double hyphen) for attaching a volume to an instance using "volume-attach" API then it results into DBDataError with following error message: "Data too long for column 'volume_id'". The reason is in database "block_device_mapping" table has "volume_id" field of 36 characters only so while inserting data to the table through 'BlockDeviceMapping' object it raises DBDaTaError.<br>
<br>
In current code, volume_id is of 'UUID' format so it uses "is_uuid_like"[4] method of oslo_utils and in this method, it removes all the hyphens and checks 32 length UUID and returns true or false. As "11111111-2222-4444-5555--<wbr>666666666666" this UUID treated as valid and further it goes into database table for insertion, as its size is more than 36 characters it gives DBDataError.<br>
<br>
There are various solutions we can apply to validate volume UUID in this case:<br>
<br>
Solution 1:<br>
We can restrict the length of volume UUID using maxlength property in schema validation.<br>
<br>
Advantage:<br>
This solution is better than solution 2 and 3 as we can restrict the invalid UUID at schema [1] level itself by adding 'maxLength'[2].<br>
<br>
Solution 2:<br>
Before creating a volume BDM object, we can check that the provided volume is actually present or not.<br>
<br>
Advantage:<br>
Volume BDM creation can be avoided if the volume does not exists.<br>
<br>
Disadvantage:<br>
IMO this solution is not better because we need to change the current code. Because in the current code after creating volume BDM it is checking volume is exists or not.<br>
We have to check volume existence before creating volume BDM object. For that we need to modify the "_check_attach_and_reserve_<wbr>volume" method [3]. But this method get used at 3 places. According to it, we have to modify all the occurrences as per behavior.<br>
<br>
Solution 3:<br>
We can check UUID in central place means in "is_uuid_like" method of oslo_utils [4].<br>
<br>
Advantage:<br>
If we change the "is_uuid_like" method then same issue might be solved for the rest of the APIs.<br>
<br>
Disadvantage:<br>
IMO this also not a better solution because if we change the "is_uuid_like" method then it will affect on several different projects.<br>
<br>
Please let me know your opinion for the same.<br>
<br>
[1] <a href="https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/volumes.py#L65" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>openstack/compute/schemas/<wbr>volumes.py#L65</a><br>
<br>
[2] <a href="https://github.com/openstack/nova/blob/master/nova/api/validation/parameter_types.py#L297" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>validation/parameter_types.py#<wbr>L297</a><br>
<br>
[3] <a href="https://github.com/openstack/nova/blob/master/nova/compute/api.py#L3721" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/compute/<wbr>api.py#L3721</a><br>
<br>
[4] <a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L45" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L45</a><br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>__________<br>
Disclaimer: This email and any attachments are sent in strictest confidence<br>
for the sole use of the addressee and may contain legally privileged,<br>
confidential, and proprietary data. If you are not the intended recipient,<br>
please advise the sender by replying promptly to this email and then delete<br>
and destroy this email and any attachments without any further use, copying<br>
or forwarding.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/85f6b1f6/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/85f6b1f6/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Mon, 24 Apr 2017 15:48:55 +0200<br>
From: Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com">dtantsur@redhat.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
Subject: Re: [openstack-dev] [ironic] New mascot design<br>
Message-ID: <<a href="mailto:392c4d06-9cbd-8476-42a6-e23d19cbf211@redhat.com">392c4d06-9cbd-8476-42a6-<wbr>e23d19cbf211@redhat.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
On 04/22/2017 12:02 AM, Heidi Joy Tretheway wrote:<br>
> Hello Ironic team,<br>
> Thanks for your comments on the last round. Here is the latest Pixie Boots mascot (in every variation) ready for your downloading pleasure. We’ll also be updating these to a public repo and to <a href="http://openstack.org/project-mascots" rel="noreferrer" target="_blank">openstack.org/project-mascots</a>, but please be patient as our fab web team is slammed with Summit stuff.<br>
><br>
> Here’s a quick look at the mascot:<br>
> <a href="https://www.dropbox.com/s/qf8lent6ncpq0ip/OpenStack_Project_Ironic_vertical.jpg?dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/s/<wbr>qf8lent6ncpq0ip/OpenStack_<wbr>Project_Ironic_vertical.jpg?<wbr>dl=0</a><br>
><br>
> And here’s a dropbox with all 10 versions:<br>
> <a href="https://www.dropbox.com/sh/w14cufsymu9hxiw/AAA5eJTW42AC-C0qPkMi4i1ra?dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/sh/<wbr>w14cufsymu9hxiw/AAA5eJTW42AC-<wbr>C0qPkMi4i1ra?dl=0</a><br>
<br>
This is awesome, thank you very much!<br>
<br>
><br>
> Long live Pixie Boots!<br>
<br>
\o/<br>
<br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 12<br>
Date: Mon, 24 Apr 2017 09:53:45 -0400<br>
From: Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID: <1493041919-sup-1166@lrrr.<wbr>local><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Excerpts from Jadhav, Pooja's message of 2017-04-24 13:45:07 +0000:<br>
> Hi Devs,<br>
><br>
> I want your opinion about bug: <a href="https://bugs.launchpad.net/nova/+bug/1680130" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>nova/+bug/1680130</a><br>
><br>
> When user passes incorrect formatted UUID, volume UUID like: 11111111-2222-4444-5555--<wbr>666666666666(please note double hyphen) for attaching a volume to an instance using "volume-attach" API then it results into DBDataError with following error message: "Data too long for column 'volume_id'". The reason is in database "block_device_mapping" table has "volume_id" field of 36 characters only so while inserting data to the table through 'BlockDeviceMapping' object it raises DBDaTaError.<br>
><br>
> In current code, volume_id is of 'UUID' format so it uses "is_uuid_like"[4] method of oslo_utils and in this method, it removes all the hyphens and checks 32 length UUID and returns true or false. As "11111111-2222-4444-5555--<wbr>666666666666" this UUID treated as valid and further it goes into database table for insertion, as its size is more than 36 characters it gives DBDataError.<br>
><br>
> There are various solutions we can apply to validate volume UUID in this case:<br>
><br>
> Solution 1:<br>
> We can restrict the length of volume UUID using maxlength property in schema validation.<br>
><br>
> Advantage:<br>
> This solution is better than solution 2 and 3 as we can restrict the invalid UUID at schema [1] level itself by adding 'maxLength'[2].<br>
><br>
> Solution 2:<br>
> Before creating a volume BDM object, we can check that the provided volume is actually present or not.<br>
><br>
> Advantage:<br>
> Volume BDM creation can be avoided if the volume does not exists.<br>
><br>
> Disadvantage:<br>
> IMO this solution is not better because we need to change the current code. Because in the current code after creating volume BDM it is checking volume is exists or not.<br>
> We have to check volume existence before creating volume BDM object. For that we need to modify the "_check_attach_and_reserve_<wbr>volume" method [3]. But this method get used at 3 places. According to it, we have to modify all the occurrences as per behavior.<br>
><br>
> Solution 3:<br>
> We can check UUID in central place means in "is_uuid_like" method of oslo_utils [4].<br>
><br>
> Advantage:<br>
> If we change the "is_uuid_like" method then same issue might be solved for the rest of the APIs.<br>
><br>
> Disadvantage:<br>
> IMO this also not a better solution because if we change the "is_uuid_like" method then it will affect on several different projects.<br>
<br>
Another option would be to convert the input value to a canonical form.<br>
So if is_uuid_like() returns true, then pass the value to a new function<br>
format_canonical_uuid() which would format it with the proper number of<br>
hyphens. That value could then be stored correctly.<br>
<br>
Doug<br>
<br>
><br>
> Please let me know your opinion for the same.<br>
><br>
> [1] <a href="https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/volumes.py#L65" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>openstack/compute/schemas/<wbr>volumes.py#L65</a><br>
><br>
> [2] <a href="https://github.com/openstack/nova/blob/master/nova/api/validation/parameter_types.py#L297" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>validation/parameter_types.py#<wbr>L297</a><br>
><br>
> [3] <a href="https://github.com/openstack/nova/blob/master/nova/compute/api.py#L3721" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/compute/<wbr>api.py#L3721</a><br>
><br>
> [4] <a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L45" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L45</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 13<br>
Date: Mon, 24 Apr 2017 15:56:43 +0200<br>
From: sasi kiran <<a href="mailto:sasikiran2007@gmail.com">sasikiran2007@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [kolla] OpenStack Kolla-Kubernetes<br>
Workshop: Demystifying the Gate - video conferencing information<br>
Message-ID:<br>
<CAFEOG0SW8VJt2+<wbr>TMNj1Dtnhmbm0SgFvegYywq=<a href="mailto:Hzq-CNriVEJg@mail.gmail.com">Hzq-<wbr>CNriVEJg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi,<br>
<br>
I'm interested to join for this session.<br>
<br>
Could you please let us know if there is any tollfree number inorder to<br>
call from India & Hungary or joining webex is sufficient enough for audio<br>
even?<br>
<br>
BR,<br>
Sasikiran<br>
<br>
On Sun, Apr 23, 2017 at 2:59 AM, Steven Dake (stdake) <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>><br>
wrote:<br>
<br>
> As proposed earlier on the mailing list, A 2 week 6 session workshop has<br>
> been organized From April 25th – May 4th Tu/W/Th for 45 minutes in length.<br>
><br>
><br>
><br>
> The agenda for this workshop is as follows:<br>
><br>
><br>
><br>
> Learn how OpenStack’s kolla-kubernetes gating functions to enable yourself<br>
> to contribute more effectively to kolla-kubernetes. This workshop will run<br>
> for two weeks on Tuesday, Wednesday and Thursday for 45 minutes beginning<br>
> April 25th, 2017 and concluding May 4th, 2017 via Webex. There is no<br>
> need to actually have a camera; the only purpose of the video conferencing<br>
> is to share a screen. The workshop will be recorded.<br>
><br>
><br>
><br>
> Connection details are below:<br>
><br>
><br>
><br>
> I am using Webex for this video conferencing session. Webex now supports<br>
> Windows, Mac, and Linux. To connect via Linux, use the web based version<br>
> of Webex (not the client). For those that can’t install a client, the web<br>
> based version should meet your organization’s security requirements.<br>
><br>
><br>
><br>
> If your struggling to join the meeting, please join #openstack-kolla and<br>
> speak up there.<br>
><br>
><br>
><br>
> Regards<br>
><br>
> -stevve<br>
><br>
><br>
><br>
> *OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate*<br>
><br>
> Every Tuesday, Wednesday, Thursday, from Tuesday, April 25, 2017, to<br>
> Thursday, May 4, 2017<br>
><br>
> 17:00 UTC | 45 minutes<br>
><br>
><br>
><br>
> <a href="https://cisco.webex.com/ciscosales/j.php?MTID=" rel="noreferrer" target="_blank">https://cisco.webex.com/<wbr>ciscosales/j.php?MTID=</a><br>
> m726d1915a1fa61470a810c9c9b01a<wbr>4ef<br>
><br>
><br>
><br>
> Meeting number:<br>
><br>
> 202 310 134<br>
><br>
> Meeting password:<br>
><br>
> openstack (67367822 from phones)<br>
><br>
><br>
><br>
><br>
><br>
> *Join by phone*<br>
><br>
> *+1-866-432-9903 <(866)%20432-9903>* Call-in toll-free number (US/Canada)<br>
><br>
> *+1-408-525-6800 <(408)%20525-6800>* Call-in toll number (US/Canada)<br>
><br>
> Access code: 202 310 134<br>
><br>
> Global call-in numbers<br>
> <<a href="https://cisco.webex.com/ciscosales/globalcallin.php?serviceType=MC&ED=383520252&tollFree=1" rel="noreferrer" target="_blank">https://cisco.webex.com/<wbr>ciscosales/globalcallin.php?<wbr>serviceType=MC&ED=383520252&<wbr>tollFree=1</a>><br>
> | Toll-free calling restrictions<br>
> <<a href="https://www.webex.com/pdf/tollfree_restrictions.pdf" rel="noreferrer" target="_blank">https://www.webex.com/pdf/<wbr>tollfree_restrictions.pdf</a>><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Add this meeting<br>
> <<a href="https://cisco.webex.com/ciscosales/j.php?MTID=mcbc11be7ec7607e78d9ec079735bf0bb" rel="noreferrer" target="_blank">https://cisco.webex.com/<wbr>ciscosales/j.php?MTID=<wbr>mcbc11be7ec7607e78d9ec079735bf<wbr>0bb</a>><br>
> to your calendar. (Cannot add from mobile devices.)<br>
><br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/c3dbb48b/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/c3dbb48b/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 14<br>
Date: Mon, 24 Apr 2017 14:06:06 +0000<br>
From: Yuval Brik <<a href="mailto:yuval.brik@toganetworks.com">yuval.brik@toganetworks.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] Project Navigator Updates - Feedback<br>
Request<br>
Message-ID:<br>
<<a href="mailto:HE1PR0202MB27647B7E6ABF7F3E496E873AEE1F0@HE1PR0202MB2764.eurprd02.prod.outlook.com">HE1PR0202MB27647B7E6ABF7F3E49<wbr>6E873AEE1F0@HE1PR0202MB2764.<wbr>eurprd02.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Missed this thread. Seems like Karbor is listed under "Security, Identity & Compliance" instead of "Storage, Backup & Recovery".<br>
<br>
Couldn't find where these categories are taken from.<br>
<br>
How can I fix that?<br>
<br>
<br>
--Yuval<br>
<br>
______________________________<wbr>__<br>
From: Lauren Sell <<a href="mailto:lauren@openstack.org">lauren@openstack.org</a>><br>
Sent: Friday, March 24, 2017 7:57:52 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: [openstack-dev] Project Navigator Updates - Feedback Request<br>
<br>
Hi everyone,<br>
<br>
We’ve been talking for some time about updating the project navigator, and we have a draft ready to share for community feedback before we launch and publicize it. One of the big goals coming out of the joint TC/UC/Board meeting a few weeks ago[1] was to help better communicate ‘what is openstack?’ and this is one step in that direction.<br>
<br>
A few goals in mind for the redesign:<br>
- Represent all official, user-facing projects and deployment services in the navigator<br>
- Better categorize the projects by function in a way that makes sense to prospective users (this may evolve over time as we work on mapping the OpenStack landscape)<br>
- Help users understand which projects are mature and stable vs emerging<br>
- Highlight popular project sets and sample configurations based on different use cases to help users get started<br>
<br>
For a bit of context, we’re working to give each OpenStack official project a stronger platform as we think of OpenStack as a framework of composable infrastructure services that can be used individually or together as a powerful system. This includes the project mascots (so we in effect have logos to promote each component separately), updates to the project navigator, and bringing back the “project updates” track at the Summit to give each PTL/core team a chance to provide an update on their project roadmap (to be recorded and promoted in the project navigator among other places!).<br>
<br>
We want your feedback on the project navigator v2 before it launches. Please take a look at the current version on the staging site and provide feedback on this thread.<br>
<br>
<a href="http://devbranch.openstack.org/software/project-navigator/" rel="noreferrer" target="_blank">http://devbranch.openstack.<wbr>org/software/project-<wbr>navigator/</a><br>
<br>
Please review the overall concept and the data and description for your project specifically. The data is primarily pulled from TC tags[2] and Ops tags[3]. You’ll notice some projects have more information available than others for various reasons. That’s one reason we decided to downplay the maturity metric for now and the data on some pages is hidden. If you think your project is missing data, please check out the repositories and submit changes or again respond to this thread.<br>
<br>
Also know this will continue to evolve and we are open to feedback. As I mentioned, a team that formed at the joint strategy session a few weeks ago is tackling how we map OpenStack projects, which may be reflected in the categories. And I suspect we’ll continue to build out additional tags and better data sources to be incorporated.<br>
<br>
Thanks for your feedback and help.<br>
<br>
Best,<br>
Lauren<br>
<br>
[1] <a href="http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/" rel="noreferrer" target="_blank">http://superuser.openstack.<wbr>org/articles/community-<wbr>leadership-charts-course-<wbr>openstack/</a><br>
[2] <a href="https://governance.openstack.org/tc/reference/tags/" rel="noreferrer" target="_blank">https://governance.openstack.<wbr>org/tc/reference/tags/</a><br>
[3] <a href="https://wiki.openstack.org/wiki/Operations/Tags" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/Operations/Tags</a><br>
<br>
------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-------------------------<br>
This email and any files transmitted and/or attachments with it are confidential and proprietary information of<br>
Toga Networks Ltd., and intended solely for the use of the individual or entity to whom they are addressed.<br>
If you have received this email in error please notify the system manager. This message contains confidential<br>
information of Toga Networks Ltd., and is intended only for the individual named. If you are not the named<br>
addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately<br>
by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not<br>
the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on<br>
the contents of this information is strictly prohibited.<br>
------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/81258baa/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/81258baa/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 15<br>
Date: Mon, 24 Apr 2017 09:07:30 -0500<br>
From: Eric Fried <openstack@fried.cc><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID: <63487ec7-5cd4-4d60-fa75-<wbr>42ee0f0a0e04@fried.cc><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
+1. Provide a sanitize_uuid() or similar, which may be as simple as:<br>
<br>
def sanitize_uuid(val):<br>
try:<br>
return uuid.UUID(val)<br>
except ValueError:<br>
raise SomePossiblyNewException(...)<br>
<br>
UUID consumers are encouraged, but not required, to use it - so we<br>
retain backward compatibility overall, and fixes like this one can be<br>
implemented individually.<br>
<br>
On 04/24/2017 08:53 AM, Doug Hellmann wrote:<br>
> Excerpts from Jadhav, Pooja's message of 2017-04-24 13:45:07 +0000:<br>
>> Hi Devs,<br>
>><br>
>> I want your opinion about bug: <a href="https://bugs.launchpad.net/nova/+bug/1680130" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>nova/+bug/1680130</a><br>
>><br>
>> When user passes incorrect formatted UUID, volume UUID like: 11111111-2222-4444-5555--<wbr>666666666666(please note double hyphen) for attaching a volume to an instance using "volume-attach" API then it results into DBDataError with following error message: "Data too long for column 'volume_id'". The reason is in database "block_device_mapping" table has "volume_id" field of 36 characters only so while inserting data to the table through 'BlockDeviceMapping' object it raises DBDaTaError.<br>
>><br>
>> In current code, volume_id is of 'UUID' format so it uses "is_uuid_like"[4] method of oslo_utils and in this method, it removes all the hyphens and checks 32 length UUID and returns true or false. As "11111111-2222-4444-5555--<wbr>666666666666" this UUID treated as valid and further it goes into database table for insertion, as its size is more than 36 characters it gives DBDataError.<br>
>><br>
>> There are various solutions we can apply to validate volume UUID in this case:<br>
>><br>
>> Solution 1:<br>
>> We can restrict the length of volume UUID using maxlength property in schema validation.<br>
>><br>
>> Advantage:<br>
>> This solution is better than solution 2 and 3 as we can restrict the invalid UUID at schema [1] level itself by adding 'maxLength'[2].<br>
>><br>
>> Solution 2:<br>
>> Before creating a volume BDM object, we can check that the provided volume is actually present or not.<br>
>><br>
>> Advantage:<br>
>> Volume BDM creation can be avoided if the volume does not exists.<br>
>><br>
>> Disadvantage:<br>
>> IMO this solution is not better because we need to change the current code. Because in the current code after creating volume BDM it is checking volume is exists or not.<br>
>> We have to check volume existence before creating volume BDM object. For that we need to modify the "_check_attach_and_reserve_<wbr>volume" method [3]. But this method get used at 3 places. According to it, we have to modify all the occurrences as per behavior.<br>
>><br>
>> Solution 3:<br>
>> We can check UUID in central place means in "is_uuid_like" method of oslo_utils [4].<br>
>><br>
>> Advantage:<br>
>> If we change the "is_uuid_like" method then same issue might be solved for the rest of the APIs.<br>
>><br>
>> Disadvantage:<br>
>> IMO this also not a better solution because if we change the "is_uuid_like" method then it will affect on several different projects.<br>
><br>
> Another option would be to convert the input value to a canonical form.<br>
> So if is_uuid_like() returns true, then pass the value to a new function<br>
> format_canonical_uuid() which would format it with the proper number of<br>
> hyphens. That value could then be stored correctly.<br>
><br>
> Doug<br>
><br>
>><br>
>> Please let me know your opinion for the same.<br>
>><br>
>> [1] <a href="https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/volumes.py#L65" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>openstack/compute/schemas/<wbr>volumes.py#L65</a><br>
>><br>
>> [2] <a href="https://github.com/openstack/nova/blob/master/nova/api/validation/parameter_types.py#L297" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>validation/parameter_types.py#<wbr>L297</a><br>
>><br>
>> [3] <a href="https://github.com/openstack/nova/blob/master/nova/compute/api.py#L3721" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/compute/<wbr>api.py#L3721</a><br>
>><br>
>> [4] <a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L45" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L45</a><br>
>><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 16<br>
Date: Mon, 24 Apr 2017 09:13:52 -0500<br>
From: Lance Bragstad <<a href="mailto:lbragstad@gmail.com">lbragstad@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] [keystone] mascot v2.0<br>
Message-ID:<br>
<<a href="mailto:CAE6oFcF6KQ6OUFL1jHhX6z7DG_iBEAP3bPjJdV3GZsbSRxj_hA@mail.gmail.com">CAE6oFcF6KQ6OUFL1jHhX6z7DG_<wbr>iBEAP3bPjJdV3GZsbSRxj_hA@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Based on some feedback of the original mascot, the Foundation passed along<br>
another revision that incorporates a keyhole into the turtle shell. There<br>
are two versions [0] [1]. We can choose to adopt one of the new formats, or<br>
stick with the one we already have.<br>
<br>
I have it on our agenda for tomorrow's meeting.<br>
<br>
Thanks!<br>
<br>
<br>
[0]<br>
<a href="https://drive.google.com/open?id=0B5G9bO9bw3ObeHk4RG1MS1Zfak16cDdtWjlqUlBlRDRQTUZn" rel="noreferrer" target="_blank">https://drive.google.com/open?<wbr>id=<wbr>0B5G9bO9bw3ObeHk4RG1MS1Zfak16c<wbr>DdtWjlqUlBlRDRQTUZn</a><br>
[1]<br>
<a href="https://drive.google.com/open?id=0B5G9bO9bw3ObRTdEV041Y0lfb1pmNV9QZWlBOTkzOGNOMnNN" rel="noreferrer" target="_blank">https://drive.google.com/open?<wbr>id=<wbr>0B5G9bO9bw3ObRTdEV041Y0lfb1pmN<wbr>V9QZWlBOTkzOGNOMnNN</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/58fa409b/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/58fa409b/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 17<br>
Date: Mon, 24 Apr 2017 16:29:14 +0200<br>
From: Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com">dtantsur@redhat.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
Subject: Re: [openstack-dev] Project Navigator Updates - Feedback<br>
Request<br>
Message-ID: <<a href="mailto:903b6c50-787e-844c-dd52-5861ab765489@redhat.com">903b6c50-787e-844c-dd52-<wbr>5861ab765489@redhat.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Quick question, sorry for top-posting. How does it represent projects that have<br>
several API services, like Baremetal or Telemetry?<br>
<br>
On 03/24/2017 05:57 PM, Lauren Sell wrote:<br>
> Hi everyone,<br>
><br>
> We’ve been talking for some time about updating the project navigator, and we<br>
> have a draft ready to share for community feedback before we launch and<br>
> publicize it. One of the big goals coming out of the joint TC/UC/Board meeting a<br>
> few weeks ago[1] was to help better communicate ‘what is openstack?’ and this is<br>
> one step in that direction.<br>
><br>
> A few goals in mind for the redesign:<br>
> - Represent all official, user-facing projects and deployment services in the<br>
> navigator<br>
> - Better categorize the projects by function in a way that makes sense to<br>
> prospective users (this may evolve over time as we work on mapping the OpenStack<br>
> landscape)<br>
> - Help users understand which projects are mature and stable vs emerging<br>
> - Highlight popular project sets and sample configurations based on different<br>
> use cases to help users get started<br>
><br>
> For a bit of context, we’re working to give each OpenStack official project a<br>
> stronger platform as we think of OpenStack as a framework of composable<br>
> infrastructure services that can be used individually or together as a powerful<br>
> system. This includes the project mascots (so we in effect have logos to promote<br>
> each component separately), updates to the project navigator, and bringing back<br>
> the “project updates” track at the Summit to give each PTL/core team a chance to<br>
> provide an update on their project roadmap (to be recorded and promoted in the<br>
> project navigator among other places!).<br>
><br>
> We want your feedback on the project navigator v2 before it launches. Please<br>
> take a look at the current version on the staging site and provide feedback on<br>
> this thread.<br>
><br>
> <a href="http://devbranch.openstack.org/software/project-navigator/" rel="noreferrer" target="_blank">http://devbranch.openstack.<wbr>org/software/project-<wbr>navigator/</a><br>
><br>
> Please review the overall concept and the data and description for your project<br>
> specifically. The data is primarily pulled from TC tags[2] and Ops tags[3].<br>
> You’ll notice some projects have more information available than others for<br>
> various reasons. That’s one reason we decided to downplay the maturity metric<br>
> for now and the data on some pages is hidden. If you think your project is<br>
> missing data, please check out the repositories and submit changes or again<br>
> respond to this thread.<br>
><br>
> Also know this will continue to evolve and we are open to feedback. As I<br>
> mentioned, a team that formed at the joint strategy session a few weeks ago is<br>
> tackling how we map OpenStack projects, which may be reflected in the<br>
> categories. And I suspect we’ll continue to build out additional tags and better<br>
> data sources to be incorporated.<br>
><br>
> Thanks for your feedback and help.<br>
><br>
> Best,<br>
> Lauren<br>
><br>
> [1]<br>
> <a href="http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/" rel="noreferrer" target="_blank">http://superuser.openstack.<wbr>org/articles/community-<wbr>leadership-charts-course-<wbr>openstack/</a><br>
> [2] <a href="https://governance.openstack.org/tc/reference/tags/" rel="noreferrer" target="_blank">https://governance.openstack.<wbr>org/tc/reference/tags/</a><br>
> [3] <a href="https://wiki.openstack.org/wiki/Operations/Tags" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/Operations/Tags</a><br>
><br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 18<br>
Date: Mon, 24 Apr 2017 10:44:47 -0400<br>
From: Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
Subject: Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID: <<a href="mailto:04f40145-690b-6c18-5b97-616be638f8b7@gmail.com">04f40145-690b-6c18-5b97-<wbr>616be638f8b7@gmail.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
On 04/24/2017 09:45 AM, Jadhav, Pooja wrote:<br>
> Solution 3:<br>
><br>
> We can check UUID in central place means in "is_uuid_like" method of<br>
> oslo_utils [4].<br>
<br>
This gets my vote. It's a bug in the is_uuid_like() function, IMHO, that<br>
is returns True for badly-formatted UUID values (like having two<br>
consecutive hyphens).<br>
<br>
FTR, the fix would be pretty simple. Just change this [1] line from this:<br>
<br>
return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
<br>
to this:<br>
<br>
# Disallow two consecutive hyphens<br>
if '--' in val:<br>
raise TypeError<br>
return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
<br>
Fix it there and you fix this issue for all projects that use it.<br>
<br>
Best,<br>
-jay<br>
<br>
[1]<br>
<a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L56" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L56</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 19<br>
Date: Mon, 24 Apr 2017 09:50:00 -0500<br>
From: Jimmy McArthur <<a href="mailto:jimmy@openstack.org">jimmy@openstack.org</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] Project Navigator Updates - Feedback<br>
Request<br>
Message-ID: <<a href="mailto:58FE1098.6010303@openstack.org">58FE1098.6010303@openstack.<wbr>org</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Dmitry,<br>
<br>
It's a good question. Right now, not very well. For this update, we<br>
worked to get as many projects as we could updated within the existing<br>
template. Post-Boston, we will revisit projects that have multiple API<br>
services (or otherwise don't quite fit into the project template) to see<br>
how we can better represent them within the navigator. If you have any<br>
thoughts on the matter, please feel free to send them our way.<br>
<br>
Thank you!<br>
Jimmy<br>
<br>
> Dmitry Tantsur <mailto:<a href="mailto:dtantsur@redhat.com">dtantsur@redhat.com</a>><br>
> April 24, 2017 at 9:29 AM<br>
> Quick question, sorry for top-posting. How does it represent projects<br>
> that have several API services, like Baremetal or Telemetry?<br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
><br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/6d316fd9/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/6d316fd9/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 20<br>
Date: Mon, 24 Apr 2017 07:51:55 -0700<br>
From: Ihar Hrachyshka <<a href="mailto:ihrachys@redhat.com">ihrachys@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] [neutron] CI team meeting on Apr 25 canceled<br>
Message-ID:<br>
<CAKwN9=<a href="mailto:D2dBuyFLYeDauAS9820SnYrg2VH5_P8wbT205nYojOOQ@mail.gmail.com">D2dBuyFLYeDauAS9820SnY<wbr>rg2VH5_P8wbT205nYojOOQ@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi,<br>
<br>
sorry for late update, but I will not be offline for the time of the<br>
meeting, so I guess we will cancel.<br>
<br>
Ihar<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/8166b3b6/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/8166b3b6/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 21<br>
Date: Mon, 24 Apr 2017 21:57:51 +0700<br>
From: Renat Akhmerov <<a href="mailto:renat.akhmerov@gmail.com">renat.akhmerov@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [mistral][tripleo] mistralclient release<br>
needed<br>
Message-ID: <be4dec2e-098c-42e7-afcf-<wbr>87c800941a5b@Spark><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi, it was released as 3.1.0 recently.<br>
<br>
Renat<br>
<br>
On 24 Apr 2017, 20:14 +0700, Juan Antonio Osorio <<a href="mailto:jaosorior@gmail.com">jaosorior@gmail.com</a>>, wrote:<br>
> Hey,<br>
><br>
> We're trying to migrate the undercloud to use keystone v3. But we're currently blocked by having an older version of mistralclient available. We would really use a release to move forward.<br>
><br>
> For reference, this is the commit we need to use in mistralclient <a href="https://github.com/openstack/python-mistralclient/commit/83b3d0d39cb8072682fac74f6a40877030e91c18" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>python-mistralclient/commit/<wbr>83b3d0d39cb8072682fac74f6a4087<wbr>7030e91c18</a><br>
><br>
> And this is the commit that's attempting to migrate to keystone v3 in tripleo: <a href="https://review.openstack.org/#/c/446752/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/446752/</a><br>
><br>
> --<br>
> Juan Antonio Osorio R.<br>
> e-mail: <a href="mailto:jaosorior@gmail.com">jaosorior@gmail.com</a><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/e1e3d61d/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/e1e3d61d/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 22<br>
Date: Mon, 24 Apr 2017 10:00:40 -0500<br>
From: Eric Fried <openstack@fried.cc><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID: <6ec0c382-130a-070a-528e-<wbr>5fcf6f41de38@fried.cc><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
That's not the only way you can break this, though. For example,<br>
'12-3-45-6-78-12-3456-781-234-<wbr>56-781-234-56-79' still passes the<br>
modified is_uuid_like(), but still manifests the bug.<br>
<br>
Trying to get is_uuid_like() to cover all possible formatting snafus<br>
while still allowing the same formats as before (e.g. without any<br>
hyphens at all) is a rabbit hole of mystical depths.<br>
<br>
On 04/24/2017 09:44 AM, Jay Pipes wrote:<br>
> On 04/24/2017 09:45 AM, Jadhav, Pooja wrote:<br>
>> Solution 3:<br>
>><br>
>> We can check UUID in central place means in "is_uuid_like" method of<br>
>> oslo_utils [4].<br>
><br>
> This gets my vote. It's a bug in the is_uuid_like() function, IMHO, that<br>
> is returns True for badly-formatted UUID values (like having two<br>
> consecutive hyphens).<br>
><br>
> FTR, the fix would be pretty simple. Just change this [1] line from this:<br>
><br>
> return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
><br>
> to this:<br>
><br>
> # Disallow two consecutive hyphens<br>
> if '--' in val:<br>
> raise TypeError<br>
> return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
><br>
> Fix it there and you fix this issue for all projects that use it.<br>
><br>
> Best,<br>
> -jay<br>
><br>
> [1]<br>
> <a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L56" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L56</a><br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 23<br>
Date: Mon, 24 Apr 2017 23:04:14 +0800<br>
From: Hui Xiang <<a href="mailto:xianghuir@gmail.com">xianghuir@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [ceilometer]Looking for endpoint where<br>
event passed after first time<br>
Message-ID:<br>
<<a href="mailto:CAPbR-pt5fX_Upsmgr5gt%2BUnaWsodcYP4EvyiOiXcD0CDU3HtXw@mail.gmail.com">CAPbR-pt5fX_Upsmgr5gt+<wbr>UnaWsodcYP4EvyiOiXcD0CDU3HtXw@<wbr>mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks gordon!! that explains why I can't trace the event since I have<br>
multi notification agents.<br>
<br>
On Thu, Apr 20, 2017 at 8:48 PM, gordon chung <<a href="mailto:gord@live.ca">gord@live.ca</a>> wrote:<br>
<br>
><br>
><br>
> On 20/04/17 01:46 AM, Hui Xiang wrote:<br>
> > And yes I have known that ceilometer notification agent will listen for<br>
> > the notification topics, but my question is which file/class will do it.<br>
> > When I am debugging the code, at the first time when the event send out<br>
> > to ceilometer exchange notification topic, EventsNotificationEndpoint<br>
> > in event/endpoint.py will handle it, however, when I send the same<br>
> > event again, with log/pdb enabled, the event is not processed in<br>
> > EventsNotificationEndpoint any more, and I can't find where it is done.<br>
> > It looks so weird or maybe that is by design for some reason? The<br>
> > behavior is same with/without definition in event_definition.yaml<br>
><br>
> this listener[1] is loading EventsNotificationEndpoint. if you look at<br>
> EventsNotificationEndpoint, you can see it picks up stuff on .info and<br>
> .error topics and normalises them to Event obj.<br>
><br>
> i'm assuming you're using oslo.messaging to push to queue as well. i<br>
> don't think the system works if you are pushing your own format to queue.<br>
><br>
><br>
> ><br>
> > So I wonder how is different for the workflow by sending same events<br>
> twice.<br>
><br>
> there is no difference. only difference is a different agent might be<br>
> handling it (if you have multiple notification agents)<br>
><br>
> [1]<br>
> <a href="https://github.com/openstack/ceilometer/blob/stable/mitaka/" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>ceilometer/blob/stable/mitaka/</a><br>
> ceilometer/notification.py#<wbr>L242-L245<br>
><br>
> --<br>
> gord<br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/b2e024f7/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/b2e024f7/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 24<br>
Date: Mon, 24 Apr 2017 11:12:25 -0400<br>
From: Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
Subject: Re: [openstack-dev] [Release-job-failures][<wbr>mistral] Release<br>
of openstack/python-mistralclient failed<br>
Message-ID: <1493046624-sup-6057@lrrr.<wbr>local><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
A recent patch in python-mistralclient added a release note that was<br>
poorly formatted, so it broke announcement job for the 3.1.0 release.<br>
<br>
I've proposed a fix for the note file in<br>
<a href="https://review.openstack.org/459341" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>459341</a> and I've proposed the project-config<br>
changes to add the jobs to avoid allowing similar failures in the future<br>
in <a href="https://review.openstack.org/459343" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>459343</a><br>
<br>
I also regenerated the announcement email by hand.<br>
<br>
Doug<br>
<br>
Excerpts from jenkins's message of 2017-04-24 13:41:24 +0000:<br>
> Build failed.<br>
><br>
> - python-mistralclient-tarball <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-tarball/e2b9206/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-tarball/e2b9206/</a> : SUCCESS in 4m 08s<br>
> - python-mistralclient-tarball-<wbr>signing <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-tarball-signing/2a5465a/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-tarball-signing/<wbr>2a5465a/</a> : SUCCESS in 52s<br>
> - python-mistralclient-pypi-<wbr>both-upload <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-pypi-both-upload/551cc60/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-pypi-both-<wbr>upload/551cc60/</a> : SUCCESS in 26s<br>
> - python-mistralclient-announce-<wbr>release <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-announce-release/a578383/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-announce-<wbr>release/a578383/</a> : FAILURE in 3m 12s<br>
> - propose-python-mistralclient-<wbr>update-constraints <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/propose-python-mistralclient-update-constraints/d356cb1/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/propose-<wbr>python-mistralclient-update-<wbr>constraints/d356cb1/</a> : SUCCESS in 1m 01s<br>
> - python-mistralclient-docs-<wbr>tags-only <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-docs-tags-only/141c4cb/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-docs-tags-only/<wbr>141c4cb/</a> : SUCCESS in 4m 04s<br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 25<br>
Date: Mon, 24 Apr 2017 11:15:47 -0400<br>
From: Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID: <1493046897-sup-2956@lrrr.<wbr>local><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Excerpts from Jay Pipes's message of 2017-04-24 10:44:47 -0400:<br>
> On 04/24/2017 09:45 AM, Jadhav, Pooja wrote:<br>
> > Solution 3:<br>
> ><br>
> > We can check UUID in central place means in "is_uuid_like" method of<br>
> > oslo_utils [4].<br>
><br>
> This gets my vote. It's a bug in the is_uuid_like() function, IMHO, that<br>
> is returns True for badly-formatted UUID values (like having two<br>
> consecutive hyphens).<br>
><br>
> FTR, the fix would be pretty simple. Just change this [1] line from this:<br>
><br>
> return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
><br>
> to this:<br>
><br>
> # Disallow two consecutive hyphens<br>
> if '--' in val:<br>
> raise TypeError<br>
> return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
><br>
> Fix it there and you fix this issue for all projects that use it.<br>
><br>
> Best,<br>
> -jay<br>
><br>
> [1]<br>
> <a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L56" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L56</a><br>
><br>
<br>
I think the point of that function was to be a little forgiving of<br>
typos, since we use UUIDs so much in the command line interfaces.<br>
<br>
Doug<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 26<br>
Date: Mon, 24 Apr 2017 11:16:31 -0400<br>
From: Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
Subject: Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID: <<a href="mailto:47ea90eb-ea23-d1a3-3256-379c848c0592@gmail.com">47ea90eb-ea23-d1a3-3256-<wbr>379c848c0592@gmail.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
On 04/24/2017 11:00 AM, Eric Fried wrote:<br>
> That's not the only way you can break this, though. For example,<br>
> '12-3-45-6-78-12-3456-781-234-<wbr>56-781-234-56-79' still passes the<br>
> modified is_uuid_like(), but still manifests the bug.<br>
><br>
> Trying to get is_uuid_like() to cover all possible formatting snafus<br>
> while still allowing the same formats as before (e.g. without any<br>
> hyphens at all) is a rabbit hole of mystical depths.<br>
<br>
Not necessarily a rabbit hole of mystical depths. :)<br>
<br>
We only care about hyphens. So, we could have this check instead:<br>
<br>
if val.count('-') not in (0, 4):<br>
raise TypeError<br>
<br>
Best,<br>
-jay<br>
<br>
> On 04/24/2017 09:44 AM, Jay Pipes wrote:<br>
>> On 04/24/2017 09:45 AM, Jadhav, Pooja wrote:<br>
>>> Solution 3:<br>
>>><br>
>>> We can check UUID in central place means in "is_uuid_like" method of<br>
>>> oslo_utils [4].<br>
>><br>
>> This gets my vote. It's a bug in the is_uuid_like() function, IMHO, that<br>
>> is returns True for badly-formatted UUID values (like having two<br>
>> consecutive hyphens).<br>
>><br>
>> FTR, the fix would be pretty simple. Just change this [1] line from this:<br>
>><br>
>> return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
>><br>
>> to this:<br>
>><br>
>> # Disallow two consecutive hyphens<br>
>> if '--' in val:<br>
>> raise TypeError<br>
>> return str(uuid.UUID(val)).replace('-<wbr>', '') == _format_uuid_string(val)<br>
>><br>
>> Fix it there and you fix this issue for all projects that use it.<br>
>><br>
>> Best,<br>
>> -jay<br>
>><br>
>> [1]<br>
>> <a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L56" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L56</a><br>
>><br>
>><br>
>> ______________________________<wbr>______________________________<wbr>______________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 27<br>
Date: Mon, 24 Apr 2017 22:20:01 +0700<br>
From: Renat Akhmerov <<a href="mailto:renat.akhmerov@gmail.com">renat.akhmerov@gmail.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a>, "OpenStack Development Mailing<br>
List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: Re: [openstack-dev] [Release-job-failures][<wbr>mistral] Release<br>
of openstack/python-mistralclient failed<br>
Message-ID: <2240db2b-9019-4d58-b307-<wbr>5dd1d0d62a4f@Spark><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Ok, thanks Doug.<br>
<br>
Renat<br>
<br>
On 24 Apr 2017, 22:16 +0700, Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>>, wrote:<br>
> A recent patch in python-mistralclient added a release note that was<br>
> poorly formatted, so it broke announcement job for the 3.1.0 release.<br>
><br>
> I've proposed a fix for the note file in<br>
> <a href="https://review.openstack.org/459341" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>459341</a> and I've proposed the project-config<br>
> changes to add the jobs to avoid allowing similar failures in the future<br>
> in <a href="https://review.openstack.org/459343" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>459343</a><br>
><br>
> I also regenerated the announcement email by hand.<br>
><br>
> Doug<br>
><br>
> Excerpts from jenkins's message of 2017-04-24 13:41:24 +0000:<br>
> > Build failed.<br>
> ><br>
> > - python-mistralclient-tarball <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-tarball/e2b9206/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-tarball/e2b9206/</a> : SUCCESS in 4m 08s<br>
> > - python-mistralclient-tarball-<wbr>signing <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-tarball-signing/2a5465a/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-tarball-signing/<wbr>2a5465a/</a> : SUCCESS in 52s<br>
> > - python-mistralclient-pypi-<wbr>both-upload <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-pypi-both-upload/551cc60/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-pypi-both-<wbr>upload/551cc60/</a> : SUCCESS in 26s<br>
> > - python-mistralclient-announce-<wbr>release <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-announce-release/a578383/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-announce-<wbr>release/a578383/</a> : FAILURE in 3m 12s<br>
> > - propose-python-mistralclient-<wbr>update-constraints <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/propose-python-mistralclient-update-constraints/d356cb1/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/propose-<wbr>python-mistralclient-update-<wbr>constraints/d356cb1/</a> : SUCCESS in 1m 01s<br>
> > - python-mistralclient-docs-<wbr>tags-only <a href="http://logs.openstack.org/88/888ad722abbd8308da91b15360a2e8d2fb582d65/release/python-mistralclient-docs-tags-only/141c4cb/" rel="noreferrer" target="_blank">http://logs.openstack.org/88/<wbr>888ad722abbd8308da91b15360a2e8<wbr>d2fb582d65/release/python-<wbr>mistralclient-docs-tags-only/<wbr>141c4cb/</a> : SUCCESS in 4m 04s<br>
> ><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/de034619/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/de034619/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 28<br>
Date: Mon, 24 Apr 2017 16:13:24 +0000<br>
From: "Dave McCowan (dmccowan)" <<a href="mailto:dmccowan@cisco.com">dmccowan@cisco.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
Subject: [openstack-dev] [barbican] Nominating Jeremy Liu for Barbican<br>
Core<br>
Message-ID: <<a href="mailto:D5239C61.48533%25dmccowan@cisco.com">D5239C61.48533%dmccowan@<wbr>cisco.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I'm pleased to nominate Jeremy Liu for Barbican core.<br>
<br>
He's been a top reviewer and contributor to Barbican since Newton and his efforts are very much appreciated.<br>
<br>
<a href="http://stackalytics.com/?module=barbican-group&user_id=liujiong&release=pike" rel="noreferrer" target="_blank">http://stackalytics.com/?<wbr>module=barbican-group&user_id=<wbr>liujiong&release=pike</a><br>
<br>
Barbicaneers, please indicate your agreement by responding with +1.<br>
<br>
--Dave<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20170424/9b848455/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/<wbr>attachments/20170424/9b848455/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 29<br>
Date: Mon, 24 Apr 2017 11:23:19 -0500<br>
From: Matt Riedemann <<a href="mailto:mriedemos@gmail.com">mriedemos@gmail.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
Subject: Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check<br>
validation of UUID length<br>
Message-ID: <<a href="mailto:f148b3bf-a756-77b5-6fee-cc5e126b0e9b@gmail.com">f148b3bf-a756-77b5-6fee-<wbr>cc5e126b0e9b@gmail.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
On 4/24/2017 8:45 AM, Jadhav, Pooja wrote:<br>
> Hi Devs,<br>
><br>
><br>
><br>
> I want your opinion about bug: <a href="https://bugs.launchpad.net/nova/+bug/1680130" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>nova/+bug/1680130</a><br>
><br>
><br>
><br>
> When user passes incorrect formatted UUID, volume UUID like:<br>
> 11111111-2222-4444-5555--<wbr>666666666666(please note double hyphen) for<br>
> attaching a volume to an instance using "volume-attach" API then it<br>
> results into DBDataError with following error message: "Data too long<br>
> for column 'volume_id'". The reason is in database<br>
> "block_device_mapping" table has "volume_id" field of 36 characters only<br>
> so while inserting data to the table through 'BlockDeviceMapping' object<br>
> it raises DBDaTaError.<br>
><br>
><br>
><br>
> In current code, volume_id is of ‘UUID’ format so it uses<br>
> "is_uuid_like"[4] method of oslo_utils and in this method, it removes<br>
> all the hyphens and checks 32 length UUID and returns true or false. As<br>
> "11111111-2222-4444-5555--<wbr>666666666666" this UUID treated as valid and<br>
> further it goes into database table for insertion, as its size is more<br>
> than 36 characters it gives DBDataError.<br>
><br>
><br>
><br>
> There are various solutions we can apply to validate volume UUID in this<br>
> case:<br>
><br>
><br>
><br>
> Solution 1:<br>
><br>
> We can restrict the length of volume UUID using maxlength property in<br>
> schema validation.<br>
><br>
><br>
><br>
> Advantage:<br>
><br>
> This solution is better than solution 2 and 3 as we can restrict the<br>
> invalid UUID at schema [1] level itself by adding 'maxLength'[2].<br>
><br>
><br>
><br>
><br>
> Solution 2:<br>
><br>
> Before creating a volume BDM object, we can check that the provided<br>
> volume is actually present or not.<br>
><br>
><br>
><br>
> Advantage:<br>
><br>
> Volume BDM creation can be avoided if the volume does not<br>
> exists.<br>
><br>
><br>
><br>
> Disadvantage:<br>
><br>
> IMO this solution is not better because we need to change the current<br>
> code. Because in the current code after creating volume BDM it is<br>
> checking volume is exists or not.<br>
><br>
> We have to check volume existence before creating volume BDM object. For<br>
> that we need to modify the "_check_attach_and_reserve_<wbr>volume" method<br>
> [3]. But this method get used at 3 places. According to it, we have to<br>
> modify all the occurrences as per behavior.<br>
><br>
><br>
><br>
> Solution 3:<br>
><br>
> We can check UUID in central place means in "is_uuid_like" method of<br>
> oslo_utils [4].<br>
><br>
><br>
><br>
> Advantage:<br>
><br>
> If we change the "is_uuid_like" method then same issue might be solved<br>
> for the rest of the APIs.<br>
><br>
><br>
><br>
><br>
> Disadvantage:<br>
><br>
> IMO this also not a better solution because if we change the<br>
> "is_uuid_like" method then it will affect on several different projects.<br>
><br>
><br>
><br>
> Please let me know your opinion for the<br>
> same.<br>
><br>
><br>
><br>
> [1]<br>
> <a href="https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/volumes.py#L65" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>openstack/compute/schemas/<wbr>volumes.py#L65</a><br>
><br>
><br>
><br>
> [2]<br>
> <a href="https://github.com/openstack/nova/blob/master/nova/api/validation/parameter_types.py#L297" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/api/<wbr>validation/parameter_types.py#<wbr>L297</a><br>
><br>
><br>
><br>
> [3] <a href="https://github.com/openstack/nova/blob/master/nova/compute/api.py#L3721" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/master/nova/compute/<wbr>api.py#L3721</a><br>
><br>
><br>
><br>
> [4]<br>
> <a href="https://github.com/openstack/oslo.utils/blob/master/oslo_utils/uuidutils.py#L45" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>oslo.utils/blob/master/oslo_<wbr>utils/uuidutils.py#L45</a><br>
><br>
><br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>__________<br>
> Disclaimer: This email and any attachments are sent in strictest confidence<br>
> for the sole use of the addressee and may contain legally privileged,<br>
> confidential, and proprietary data. If you are not the intended recipient,<br>
> please advise the sender by replying promptly to this email and then delete<br>
> and destroy this email and any attachments without any further use, copying<br>
> or forwarding.<br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
Is "11111111-2222-4444-5555--<wbr>666666666666" actually getting past the<br>
jsonschema validation check when attaching a volume to a server? Because<br>
that's looking for a uuid:<br>
<br>
<a href="https://github.com/openstack/nova/blob/0039231719d2a02c59e7cd76631e2ff03cc86b0d/nova/api/validation/parameter_types.py#L298" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>nova/blob/<wbr>0039231719d2a02c59e7cd76631e2f<wbr>f03cc86b0d/nova/api/<wbr>validation/parameter_types.py#<wbr>L298</a><br>
<br>
--<br>
<br>
Thanks,<br>
<br>
Matt<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.<wbr>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
End of OpenStack-dev Digest, Vol 60, Issue 44<br>
******************************<wbr>***************<br>
</blockquote></div><br></div></div>