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