From lebre.adrien at free.fr Tue Jun 5 14:48:55 2018 From: lebre.adrien at free.fr (lebre.adrien at free.fr) Date: Tue, 5 Jun 2018 16:48:55 +0200 (CEST) Subject: [Openstack-sigs] [FEMDC] meetings suspended until further notice In-Reply-To: <67878378.160787292.1528209018026.JavaMail.root@zimbra29-e5.priv.proxad.net> Message-ID: <596449522.160890842.1528210135736.JavaMail.root@zimbra29-e5.priv.proxad.net> Dear all, Following the exchanges we had during the Vancouver summit, in particular the non-sense to maintain/animate two groups targeting similar challenges (ie., the FEMDC SIG [1] and the new Edge Computing Working group [2]), FEMDC meetings are suspended until further notice. If you are interested by Edge Computing discussions, please see information available on the new edge wiki page [2]. Thanks ad_ri3n_ [1]https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds [2]https://wiki.openstack.org/wiki/Edge_Computing_Group From zbitter at redhat.com Tue Jun 5 16:47:01 2018 From: zbitter at redhat.com (Zane Bitter) Date: Tue, 5 Jun 2018 12:47:01 -0400 Subject: [Openstack-sigs] [k8s] Integrating OpenStack with the k8s service catalog Message-ID: <2707a860-77de-b992-737f-9f0c4444f199@redhat.com> Greetings, k8s SIG members. I started a thread about $SUBJECT on openstack-dev that I expect many of y'all might be interested in: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131183.html Please reply on that thread if you are interested in helping or have questions. cheers, Zane. From stig.openstack at telfer.org Wed Jun 6 10:09:48 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Wed, 6 Jun 2018 11:09:48 +0100 Subject: [Openstack-sigs] [scientific] IRC meeting: Roundup and planning for new activities Message-ID: Hi All - We have a Scientific SIG meeting in about an hour (1100 UTC) in channel #openstack-meeting. Everyone is welcome. The agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_June_6th_2018 The main item for discussion is gathering together some “fellow travellers” for building up knowledge on handling access to controlled datasets. Cheers, Stig From stig.openstack at telfer.org Wed Jun 6 12:11:31 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Wed, 6 Jun 2018 13:11:31 +0100 Subject: [Openstack-sigs] [scientific] CFP deadline for Berlin Message-ID: Hi all - There was some discussion in the Scientific SIG meeting about the CFP deadline for Berlin. According to the CFP site [https://www.openstack.org/summit/berlin-2018/call-for-presentations/ ] this is the end of June. Isn’t that quite early? Other conferences have a very long lead time for presentation submission but OpenStack summits have more of a dynamic flow to them. The consensus in the discussion was that people would prefer more time to prepare presentations than this, if that is possible. Cheers, Stig -------------- next part -------------- An HTML attachment was scrubbed... URL: From openstack at medberry.net Wed Jun 6 15:15:57 2018 From: openstack at medberry.net (David Medberry) Date: Wed, 6 Jun 2018 09:15:57 -0600 Subject: [Openstack-sigs] [scientific] CFP deadline for Berlin In-Reply-To: References: Message-ID: Wow, that does indeed seem early (and with little time for thought collecting post Vancouver.) Is this for logistics reasons (visas, etc) or Foundation reasons (change of policy, etc)? On Wed, Jun 6, 2018 at 6:11 AM, Stig Telfer wrote: > Hi all - > > There was some discussion in the Scientific SIG meeting about the CFP > deadline for Berlin. > > According to the CFP site [https://www.openstack.org/ > summit/berlin-2018/call-for-presentations/] this is the end of June. > Isn’t that quite early? Other conferences have a very long lead time for > presentation submission but OpenStack summits have more of a dynamic flow > to them. > > The consensus in the discussion was that people would prefer more time to > prepare presentations than this, if that is possible. > > Cheers, > Stig > > > _______________________________________________ > openstack-sigs mailing list > openstack-sigs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Wed Jun 6 15:18:20 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 6 Jun 2018 15:18:20 +0000 Subject: [Openstack-sigs] [scientific] CFP deadline for Berlin In-Reply-To: References: Message-ID: <20180606151820.splphoottupw2lz5@yuggoth.org> On 2018-06-06 09:15:57 -0600 (-0600), David Medberry wrote: > Wow, that does indeed seem early (and with little time for thought > collecting post Vancouver.) > > Is this for logistics reasons (visas, etc) or Foundation reasons (change of > policy, etc)? [...] Keep in mind that's the deadline for traditional conference presentations at the Summit. On the other hand, Forum sessions get picked much, much closer to the conference date. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From jimmy at openstack.org Wed Jun 6 16:58:05 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 06 Jun 2018 11:58:05 -0500 Subject: [Openstack-sigs] [scientific] CFP deadline for Berlin In-Reply-To: References: Message-ID: <5B18129D.6010105@openstack.org> We are actually still finalizing the due date. We've heard the feedback on the quick turn around and we're planning to push to July. Date TBD, but should be announced very soon. I know it seems like an early deadline, but part of what we're dealing with is trying to get the the date before the Travel Support and Early Bird pricing deadline. This should allow us to give as many people as possible an opportunity to attend. Thanks for the feedback and stay tuned... Cheers, Jimmy Stig Telfer wrote: > Hi all - > > There was some discussion in the Scientific SIG meeting about the CFP > deadline for Berlin. > > According to the CFP site > [https://www.openstack.org/summit/berlin-2018/call-for-presentations/] > this is the end of June. Isn’t that quite early? Other conferences > have a very long lead time for presentation submission but OpenStack > summits have more of a dynamic flow to them. > > The consensus in the discussion was that people would prefer more time > to prepare presentations than this, if that is possible. > > Cheers, > Stig > -------------- next part -------------- An HTML attachment was scrubbed... URL: From msm at redhat.com Thu Jun 7 16:36:31 2018 From: msm at redhat.com (Michael McCune) Date: Thu, 7 Jun 2018 12:36:31 -0400 Subject: [Openstack-sigs] [all][api] POST /api-sig/news Message-ID: Greetings OpenStack community, Today's meeting was brief, covering only 1 major topic. The main topic for the SIG today was the migration of bug tracking from Launchpad to StoryBoard[7]. No firm plans were made to migrate yet, but the group agreed that this migration would be positive from a community alignment perspective and that the number of bugs in conjunction with a low rate of bug addition would make the migration less risky. There was no opposition to the migration, but it was noted that the shift from Launchpad to StoryBoard does represent a paradigm shift and that there is not a 1:1 equivalency between the two. Expect the SIG to continue researching the migration and put forth a plan to shift at some point in the future. Although not a full discussion topic, Chris Dent reinforced the SIG's commitment to attending the forthcoming writeup about micrversion bump plans by mordred. There being no recent changes to pending guidelines nor to bugs, we ended the meeting early. As always if you're interested in helping out, in addition to coming to the meetings, there's also: * The list of bugs [5] indicates several missing or incomplete guidelines. * The existing guidelines [2] always need refreshing to account for changes over time. If you find something that's not quite right, submit a patch [6] to fix it. * Have you done something for which you think guidance would have made things easier but couldn't find any? Submit a patch and help others [6]. # Newly Published Guidelines None # API Guidelines Proposed for Freeze Guidelines that are ready for wider review by the whole community. None # Guidelines Currently Under Review [3] * Update parameter names in microversion sdk spec https://review.openstack.org/#/c/557773/ * Add API-schema guide (still being defined) https://review.openstack.org/#/c/524467/ * A (shrinking) suite of several documents about doing version and service discovery Start at https://review.openstack.org/#/c/459405/ * WIP: microversion architecture archival doc (very early; not yet ready for review) https://review.openstack.org/444892 # Highlighting your API impacting issues If you seek further review and insight from the API SIG about APIs that you are developing or changing, please address your concerns in an email to the OpenStack developer mailing list[1] with the tag "[api]" in the subject. In your email, you should include any relevant reviews, links, and comments to help guide the discussion of the specific challenge you are facing. To learn more about the API SIG mission and the work we do, see our wiki page [4] and guidelines [2]. Thanks for reading and see you next week! # References [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [2] http://specs.openstack.org/openstack/api-wg/ [3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z [4] https://wiki.openstack.org/wiki/API_SIG [5] https://bugs.launchpad.net/openstack-api-wg [6] https://git.openstack.org/cgit/openstack/api-wg [7] https://storyboard.openstack.org/#!/page/about Meeting Agenda https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda Past Meeting Records http://eavesdrop.openstack.org/meetings/api_sig/ Open Bugs https://bugs.launchpad.net/openstack-api-wg From rleander at redhat.com Thu Jun 7 18:24:07 2018 From: rleander at redhat.com (Rain Leander) Date: Thu, 7 Jun 2018 20:24:07 +0200 Subject: [Openstack-sigs] [RDO] Rocky Milestone 2 RDO Test Days June 14-15 Message-ID: Who’s up for a rematch?- Rocky Milestone 2 is here and we’re ready to rumble! Join RDO [0] on June 14 & 15 for an awesome time of taking down bugs and fighting errors in the most recent release [1].- We certainly won’t be pulling any punches. Want to get in on the action? We’re looking for developers, users, operators, quality engineers, writers, and, yes, YOU. If you’re reading this, we think you’re a champion and we want your help! We’ll have packages for the following platforms: * RHEL 7 * CentOS 7 You’ll want a fresh install with latest updates installed so that there’s no hard-to-reproduce interactions with other things. We’ll be collecting feedback, writing up tickets, filing bugs, and answering questions. Even if you only have a few hours to spare, we’d love your help taking this new version for a spin to work out any kinks. Not only will this help identify issues early in the development process, but you can be the one of the first to cut your teeth on the latest versions of your favorite deployment methods like TripleO, PackStack, and Kolla. Interested? We’ll be gathering on #rdo (on Freenode IRC) for any associated questions/discussion, and working through the “Does it work?” tests [2]. As Rocky said, “The world ain’t all sunshine and rainbows,” but with your help, we can keep moving forward and make the RDO world better for those around us. Hope to see you on the 14th & 15th! [0] https://www.rdoproject.org/ [1] https://www.rdoproject.org/testday/ [2] https://www.rdoproject.org/testday/tests/ -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From amotoki at gmail.com Fri Jun 8 08:14:35 2018 From: amotoki at gmail.com (Akihiro Motoki) Date: Fri, 8 Jun 2018 17:14:35 +0900 Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper Translation In-Reply-To: References: <20180529135041.cyjrl3vtpwajhicq@yuggoth.org> <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com> Message-ID: Hi all, # I added edge-computing ML as the edge computing team uses a separate list other than the SIG ML. # The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML. What is the next step of the translation of the edge computing white paper with RST? My temporary translation publishing [1] should not be published as-is due to the CC BY-ND license. This is to prove how it works. I would like to move this forward and am happy to help the setup of a repo if needed. Where can we discuss this? The edge computing group meeting is not listed at http://eavesdrop.openstack.org/ and I don't know when and where it happens. [1] https://amotoki.github.io/edge-computing-whitepaper/ Thanks, Akihiro 2018年5月29日(火) 23:37 Akihiro Motoki : > Hi Ildiko and all, > > I am happy to hear that HTML-based publishing is now on the table :) > I am synced with Ian and Frank on this topic, though I failed to join the > conversation at Vancouver. > RST based process is used much in the community and translation > publishinng of project docs which Ian and us are working on will make the > continuous publishing easier. > I am happy to help setting up a new doc infrastructure and/or publishing > translations. > > Regarding the license, CC BY-ND license turned out a bit too strict in our > collaborative works when I checked the current one. > Hopefully we can get a good conclusion for further similar cases. > > Thanks, > Akihiro > > > > 2018年5月29日(火) 23:19 Ildiko Vancsa : > >> Hi Akihiro and All, >> >> Thank you for your efforts on helping with publishing the white paper in >> additional languages. >> >> I talked to Ian and Frank last week about this topic and the conundrum on >> the Foundation side whether or not to do the print version for the >> translations as that is what slows down the process a lot due to the design >> work it requires. >> >> We got to the conclusion with our team from the Foundation (cc’ed >> Allison, Jimmy and Wes) to do HTML-based publishing to reduce this >> overhead. We need to clarify now on the process and as Jeremy indicated the >> licensing as well. >> >> Thanks, >> Ildikó >> >> >> > On 2018. May 29., at 15:50, Jeremy Stanley wrote: >> > >> > On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: >> > [...] >> >> NOTE: Anyway I need to grant it from the foundation because CC >> >> Attribution-NoDerivatives 4.0 International license does not allow >> >> me to share translations without permission. I updated this files >> >> only for discussion and will close this soon. >> > [...] >> > >> > It seems like this is a really poor choice of license as it's >> > impairing open collaboration. Even Creative Commons suggests that >> > the CC BY-ND license is unsuitable for free cultural works: >> > >> > https://creativecommons.org/share-your-work/public-domain/freeworks/ >> > >> > We should see about getting this changed to CC BY like is used for >> > other collaborative works produced by our community. >> > -- >> > Jeremy Stanley >> > _______________________________________________ >> > openstack-sigs mailing list >> > openstack-sigs at lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> >> >> _______________________________________________ >> openstack-sigs mailing list >> openstack-sigs at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Jun 8 16:16:32 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 8 Jun 2018 18:16:32 +0200 Subject: [Openstack-sigs] [Edge-computing] [OpenStack-I18n] Edge Computing Whitepaper Translation In-Reply-To: References: <20180529135041.cyjrl3vtpwajhicq@yuggoth.org> <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com> Message-ID: <297D0BCC-4EB7-401E-883D-EC5D3BDE1C59@gmail.com> Hi Akihiro, It is on our priority list to put up the translated versions in an online format as well as work out to have the .po files available. Jimmy is looking into it and will give an update once we got some progress. Thanks and Best Regards, Ildikó > On 2018. Jun 8., at 10:14, Akihiro Motoki wrote: > > Hi all, > > # I added edge-computing ML as the edge computing team uses a separate list other than the SIG ML. > # The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML. > > What is the next step of the translation of the edge computing white paper with RST? > My temporary translation publishing [1] should not be published as-is due to the CC BY-ND license. This is to prove how it works. > I would like to move this forward and am happy to help the setup of a repo if needed. > > Where can we discuss this? > The edge computing group meeting is not listed at http://eavesdrop.openstack.org/ and I don't know when and where it happens. > > [1] https://amotoki.github.io/edge-computing-whitepaper/ > > Thanks, > Akihiro > > 2018年5月29日(火) 23:37 Akihiro Motoki : > Hi Ildiko and all, > > I am happy to hear that HTML-based publishing is now on the table :) > I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver. > RST based process is used much in the community and translation publishinng of project docs which Ian and us are working on will make the continuous publishing easier. > I am happy to help setting up a new doc infrastructure and/or publishing translations. > > Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one. > Hopefully we can get a good conclusion for further similar cases. > > Thanks, > Akihiro > > > > 2018年5月29日(火) 23:19 Ildiko Vancsa : > Hi Akihiro and All, > > Thank you for your efforts on helping with publishing the white paper in additional languages. > > I talked to Ian and Frank last week about this topic and the conundrum on the Foundation side whether or not to do the print version for the translations as that is what slows down the process a lot due to the design work it requires. > > We got to the conclusion with our team from the Foundation (cc’ed Allison, Jimmy and Wes) to do HTML-based publishing to reduce this overhead. We need to clarify now on the process and as Jeremy indicated the licensing as well. > > Thanks, > Ildikó > > > > On 2018. May 29., at 15:50, Jeremy Stanley wrote: > > > > On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: > > [...] > >> NOTE: Anyway I need to grant it from the foundation because CC > >> Attribution-NoDerivatives 4.0 International license does not allow > >> me to share translations without permission. I updated this files > >> only for discussion and will close this soon. > > [...] > > > > It seems like this is a really poor choice of license as it's > > impairing open collaboration. Even Creative Commons suggests that > > the CC BY-ND license is unsuitable for free cultural works: > > > > https://creativecommons.org/share-your-work/public-domain/freeworks/ > > > > We should see about getting this changed to CC BY like is used for > > other collaborative works produced by our community. > > -- > > Jeremy Stanley > > _______________________________________________ > > openstack-sigs mailing list > > openstack-sigs at lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > > > _______________________________________________ > openstack-sigs mailing list > openstack-sigs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > _______________________________________________ > Edge-computing mailing list > Edge-computing at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing From sunku.ranganath at intel.com Fri Jun 8 23:54:17 2018 From: sunku.ranganath at intel.com (Ranganath, Sunku) Date: Fri, 8 Jun 2018 23:54:17 +0000 Subject: [Openstack-sigs] [self-healing] OPNFV Barometer & Self-healing Message-ID: Hi All, Telemetry and monitoring are a fundamental aspect required for implementing comprehensive Self-healing. OPNFV Barometer provides the ability to monitor Network Function Virtualization Infrastructure (NFVI) to help with Service Assurance. Barometer home: https://wiki.opnfv.org/display/fastpath/Barometer+Home However the work done by the Barometer community helps out any cloud deployment by exposing various platform metrics including but not limited: - Last level cache - CPU metrics - Memory metrics - Thermals - Fan Speeds - Voltages - Machine check exceptions - RedFish support - IPMI - SNMP support - OVS metrics - DPDK metrics - PMU metrics - Prometheus support, etc. With the ongoing work, the Barometer community is looking forward to work with Self-healing SIG in providing use cases and solutions and help wide variety of audience. Feel free to join in with Barometer community for more questions/comments/feedback. Thanks, Sunku Ranganath -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Fri Jun 8 17:00:13 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 08 Jun 2018 12:00:13 -0500 Subject: [Openstack-sigs] [Edge-computing] [OpenStack-I18n] Edge Computing Whitepaper Translation In-Reply-To: <297D0BCC-4EB7-401E-883D-EC5D3BDE1C59@gmail.com> References: <20180529135041.cyjrl3vtpwajhicq@yuggoth.org> <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com> <297D0BCC-4EB7-401E-883D-EC5D3BDE1C59@gmail.com> Message-ID: <5B1AB61D.409@openstack.org> We are currently targeting June 25 for the initial version of the Edge whitepaper. However, I'll know more by EOW next. Cheers, Jimmy Ildiko Vancsa wrote: > Hi Akihiro, > > It is on our priority list to put up the translated versions in an online format as well as work out to have the .po files available. > > Jimmy is looking into it and will give an update once we got some progress. > > Thanks and Best Regards, > Ildikó > > >> On 2018. Jun 8., at 10:14, Akihiro Motoki wrote: >> >> Hi all, >> >> # I added edge-computing ML as the edge computing team uses a separate list other than the SIG ML. >> # The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML. >> >> What is the next step of the translation of the edge computing white paper with RST? >> My temporary translation publishing [1] should not be published as-is due to the CC BY-ND license. This is to prove how it works. >> I would like to move this forward and am happy to help the setup of a repo if needed. >> >> Where can we discuss this? >> The edge computing group meeting is not listed at http://eavesdrop.openstack.org/ and I don't know when and where it happens. >> >> [1] https://amotoki.github.io/edge-computing-whitepaper/ >> >> Thanks, >> Akihiro >> >> 2018年5月29日(火) 23:37 Akihiro Motoki: >> Hi Ildiko and all, >> >> I am happy to hear that HTML-based publishing is now on the table :) >> I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver. >> RST based process is used much in the community and translation publishinng of project docs which Ian and us are working on will make the continuous publishing easier. >> I am happy to help setting up a new doc infrastructure and/or publishing translations. >> >> Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one. >> Hopefully we can get a good conclusion for further similar cases. >> >> Thanks, >> Akihiro >> >> >> >> 2018年5月29日(火) 23:19 Ildiko Vancsa: >> Hi Akihiro and All, >> >> Thank you for your efforts on helping with publishing the white paper in additional languages. >> >> I talked to Ian and Frank last week about this topic and the conundrum on the Foundation side whether or not to do the print version for the translations as that is what slows down the process a lot due to the design work it requires. >> >> We got to the conclusion with our team from the Foundation (cc’ed Allison, Jimmy and Wes) to do HTML-based publishing to reduce this overhead. We need to clarify now on the process and as Jeremy indicated the licensing as well. >> >> Thanks, >> Ildikó >> >> >>> On 2018. May 29., at 15:50, Jeremy Stanley wrote: >>> >>> On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: >>> [...] >>>> NOTE: Anyway I need to grant it from the foundation because CC >>>> Attribution-NoDerivatives 4.0 International license does not allow >>>> me to share translations without permission. I updated this files >>>> only for discussion and will close this soon. >>> [...] >>> >>> It seems like this is a really poor choice of license as it's >>> impairing open collaboration. Even Creative Commons suggests that >>> the CC BY-ND license is unsuitable for free cultural works: >>> >>> https://creativecommons.org/share-your-work/public-domain/freeworks/ >>> >>> We should see about getting this changed to CC BY like is used for >>> other collaborative works produced by our community. >>> -- >>> Jeremy Stanley >>> _______________________________________________ >>> openstack-sigs mailing list >>> openstack-sigs at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> _______________________________________________ >> openstack-sigs mailing list >> openstack-sigs at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> _______________________________________________ >> Edge-computing mailing list >> Edge-computing at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blair.bethwaite at gmail.com Tue Jun 12 15:12:22 2018 From: blair.bethwaite at gmail.com (Blair Bethwaite) Date: Wed, 13 Jun 2018 01:12:22 +1000 Subject: [Openstack-sigs] [scientific] IRC meeting at 2100 UTC In-Reply-To: <236433A7-F10B-4A29-BA14-A256B36FE359@telfer.org> References: <236433A7-F10B-4A29-BA14-A256B36FE359@telfer.org> Message-ID: Hi all, Scientific SIG IRC meeting in approx 6 hours in channel #openstack-meeting. All comers welcome. Today we plan to start discussing and collecting input on open cloud compatible workload management systems. *https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_June_12th_2018 * -- Cheers, ~Blairo -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Tue Jun 12 19:53:25 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 12 Jun 2018 19:53:25 +0000 Subject: [Openstack-sigs] [first-contact] Forum summary on recommendations for contributing organizations Message-ID: <20180612195325.lr364w6skajhhtow@yuggoth.org> The First Contact SIG met at the Forum in Vancouver to discuss ways in which we can better communicate a set of recommendations to (particularly management at) the organizations employing many of OpenStack's contributors on how they can best ensure the success of their employees within our community. As we're probably all aware, our tooling and processes/workflows present a variety of challenges dependent on the situation of each individual contributor, and it's up to us as a community to help organizations donating their engineering time understand how they can loosen or remove impediments for which they might be directly responsible. As usual, the notes for this session are available in an Etherpad[1]. To open, we mentioned that this discussion evolved out of a set of notes[2] we'd accumulated for creation of a Contributing Organization Guide. It was suggested that this guide should ideally manifest as a one-sheet document under the top level table of contents for The OpenStack Contributor Guide[3]. The idea is that when a contributing organization assigns one of their staff to work upstream with the OpenStack community on some task, that individual can easily provide their manager(s) with a link to this simple document describing things they may need to take into consideration to help make the engagement fruitful and rewarding for everyone involved. We talked about how to carefully frame the voice of the document as a recommendation to improve fidelity of contributors and their organizations with the community, rather than as a proscriptive set of requirements. As engineers we may find it easy to design a specification for the ideal contributor environment, but when the target audience is general management who are themselves used to being the ones directing and setting requirements they're likely to respond far more favorably to explanations for how their organization may best benefit from meeting this set of recommendations. Put another way, a primary goal of this guide is to give new contributors help in "managing upward." We also talked about how it would be good for the OSF business management/ecosystem team to be able to keep this in their (virtual) "back pocket" when talking to representatives of new member companies who are interested in effectively interfacing some of their staff with our community. They're often the point of first contact for organizations who want to get involved in OpenStack, so helping them out means the First Contact SIG gets to further its mission as early as possible in that process. We spent a while getting down into the weeds rehashing different kinds of challenges and their associated mitigations, and sorting them into categories: technical (e.g. developers need access to Gerrit, many kinds of contributors need access to Freenode's IRC network, almost everyone needs to be able to send to and receive from our mailing lists), non-technical (legal agreements, permission to work from home/off hours, travel budget), and educational (notes on actual implications of elected positions/titles, linking to further reading on how performance metrics are challenging and why maintaining forks of our software is counter-productive). Finally, we came up with a handful of action items. One was me sending this summary (only a couple weeks late!), another was Matthew Oliver submitting a patch to the contributor guide repo with our initial stub text. Beyond that, we agreed that we should "soon" plan some follow-up discussions. If you're interested in getting involved with this or any of the First Contact SIG's other work, feel free to reach out through this mailing list or the #openstack-dev channel on the Freenode IRC network, or join in the weekly IRC meeting[4] Wednesdays at 08:00 UTC in #openstack-meeting. [1] https://etherpad.openstack.org/p/Reqs-for-Organisations-Contributing-to-OpenStack [2] https://etherpad.openstack.org/p/Contributing_Organization_Guide [3] https://docs.openstack.org/contributors/ [4] http://eavesdrop.openstack.org/#First_Contact_SIG_Meeting -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From kennelson11 at gmail.com Wed Jun 13 03:52:41 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 13 Jun 2018 05:52:41 +0200 Subject: [Openstack-sigs] [First Contact] Meeting Today Cancelled Message-ID: Hello :) Unfortunately I won't be able to lead today's meeting as I will be boarding a plane and taking off about the time that the meeting is scheduled for. We will have our meeting next week as usual. In the mean time, please make sure to continue looking at 'Welcome,New Contributor' patches and keeping up on ask.o.o :) Only update I have is that I sent out the email to PTLs about them being project liaisons unless otherwise delegated last week. I plan to fill out our wiki page with missing projects and the PTLs of them (no ptl has come back saying they will delegate it so far). After the wiki updates I'll send a follow up on the thread and see if that encourages any action :) If you have topics for next week, please feel free to add them to the agenda [1]! -Kendall (diablo_rojo) [1]https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtantsur at redhat.com Mon Jun 18 16:30:19 2018 From: dtantsur at redhat.com (Dmitry Tantsur) Date: Mon, 18 Jun 2018 18:30:19 +0200 Subject: [Openstack-sigs] [sdk] announcing first release of rust-openstack (+ call for contributors) Message-ID: Hi all, I'd like to announce my hobby project that I've been working on for some time. rust-openstack [1], as the name suggests, is an SDK for OpenStack written in Rust! I released version 0.1.0 last week, and now the project is ready for early testers and contributors. Currently only a small subset of Compute, Networking and Image API is implemented, as well as password authentication against Identity v3. If you're interested in the Rust language, this may be your chance :) I have written a short contributor's guide [2] to help understanding the code structure. Special thanks to the OpenLab project for providing the CI for the project. Cheers, Dmitry [1] https://docs.rs/openstack/latest/openstack/ [2] https://github.com/dtantsur/rust-openstack/blob/master/CONTRIBUTING.md From stig.openstack at telfer.org Wed Jun 20 09:49:40 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Wed, 20 Jun 2018 10:49:40 +0100 Subject: [Openstack-sigs] [scientific] IRC meeting today 1100 UTC: DockerCon, Ceph-RDMA Message-ID: <065712DB-45E8-4086-8185-45E775AE85EF@telfer.org> Hi All - We have a Scientific SIG meeting coming up in about an hour in IRC channel #openstack-meeting. Everyone is welcome. The plan for today is to have a roundup on DockerCon from Martial and an update on where Ceph-RDMA appears to be from Stig. Any other items for discussion are also welcome. Full agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_June_20th_2018 Cheers, Stig From kennelson11 at gmail.com Wed Jun 20 18:24:38 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 20 Jun 2018 11:24:38 -0700 Subject: [Openstack-sigs] [PTG] Updates! Message-ID: Hello Everyone! Wanted to give you some updates on PTG4 planning. We have finalized the list of SIGs/ Groups/WGs/Teams that are attending. They are as follows: - Airship - API SIG - Barbican/Security SIG - Blazar - Chef OpenStack - Cinder - Cyborg - Designate - Documentation - Edge Computing Group - First Contact SIG - Glance - Heat - Horizon - Infrastructure - Interop WG - Ironic - Kata - Keystone - Kolla - LOCI - Manila - Masakari - Mistral - Monasca - Neutron - Nova - Octavia - OpenStack Ansible - OpenStack Charms - OpenStack Helm - OpenStackClient - Operator Meetup Puppet OpenStack - QA - Oslo - Public Cloud WG - Release Management - Requirements - Sahara - Scientific SIG - Self-Healing SIG - SIG- K8s - StarlingX - Swift - TC - TripleO - Upgrades SIG - Watcher - Zuul (pending confirmation) Thierry and I are working on placing them into a strawman schedule to reduce conflicts between related or overlapping groups. We should have more on what that will look like and a draft for you all to review in the next few weeks. We also wanted to remind you all of the Travel Support Program. We are again doing a two phase selection. The first deadline is approaching: July 1st. At this point we have less than a dozen applicants so if you need it or even think you need it, I urge you to apply here[1]. Also! Reminder that we have a finite number of rooms in the hotel block so please book early to make sure you get the discounted rate before they run out. You can book those rooms here[2] (pardon the ugly URL). Can't wait to see you all there! -Kendall Nelson (diablo_rojo) P.S. Gonna try to do a game night again since you all seemed to enjoy it so much last time :) [1] https://openstackfoundation.formstack.com/forms/travelsupportptg_denver_2018 [2] https://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupCorp.mi?resLinkData=Project%20Teams%20Gathering%2C%20Openstack%5Edensa%60opnopna%7Copnopnb%60149.00%60USD%60false%604%609/5/18%609/18/18%608/20/18&app=resvlink&stop_mobi=yes -------------- next part -------------- An HTML attachment was scrubbed... URL: From sombrafam at gmail.com Wed Jun 20 20:55:56 2018 From: sombrafam at gmail.com (Erlon Cruz) Date: Wed, 20 Jun 2018 17:55:56 -0300 Subject: [Openstack-sigs] [openstack-dev] [PTG] Updates! In-Reply-To: References: Message-ID: +1 on the game night! Reserve a room only for that :) Em qua, 20 de jun de 2018 às 15:25, Kendall Nelson escreveu: > Hello Everyone! > > Wanted to give you some updates on PTG4 planning. We have finalized the > list of SIGs/ Groups/WGs/Teams that are attending. They are as follows: > > - > > Airship > - > > API SIG > - > > Barbican/Security SIG > - > > Blazar > - > > Chef OpenStack > - > > Cinder > - > > Cyborg > - > > Designate > - > > Documentation > - > > Edge Computing Group > - > > First Contact SIG > - > > Glance > - > > Heat > - > > Horizon > - > > Infrastructure > - > > Interop WG > > > - > > Ironic > - > > Kata > - > > Keystone > - > > Kolla > - > > LOCI > - > > Manila > - > > Masakari > - > > Mistral > - > > Monasca > - > > Neutron > - > > Nova > - > > Octavia > - > > OpenStack Ansible > - > > OpenStack Charms > - > > OpenStack Helm > - > > OpenStackClient > > > > - > > Operator Meetup > Puppet OpenStack > - > > QA > - > > Oslo > - > > Public Cloud WG > - > > Release Management > - > > Requirements > - > > Sahara > - > > Scientific SIG > - > > Self-Healing SIG > - > > SIG- K8s > - > > StarlingX > - > > Swift > - > > TC > - > > TripleO > - > > Upgrades SIG > - > > Watcher > - > > Zuul (pending confirmation) > > Thierry and I are working on placing them into a strawman schedule to > reduce conflicts between related or overlapping groups. We should have more > on what that will look like and a draft for you all to review in the next > few weeks. > > We also wanted to remind you all of the Travel Support Program. We are > again doing a two phase selection. The first deadline is approaching: July > 1st. At this point we have less than a dozen applicants so if you need it > or even think you need it, I urge you to apply here[1]. > > Also! Reminder that we have a finite number of rooms in the hotel block so > please book early to make sure you get the discounted rate before they run > out. You can book those rooms here[2] (pardon the ugly URL). > > Can't wait to see you all there! > > -Kendall Nelson (diablo_rojo) > > P.S. Gonna try to do a game night again since you all seemed to enjoy it > so much last time :) > > [1] > https://openstackfoundation.formstack.com/forms/travelsupportptg_denver_2018 > > [2] > https://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupCorp.mi?resLinkData=Project%20Teams%20Gathering%2C%20Openstack%5Edensa%60opnopna%7Copnopnb%60149.00%60USD%60false%604%609/5/18%609/18/18%608/20/18&app=resvlink&stop_mobi=yes > > __________________________________________________________________________ > 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: From msm at redhat.com Thu Jun 21 16:56:33 2018 From: msm at redhat.com (Michael McCune) Date: Thu, 21 Jun 2018 12:56:33 -0400 Subject: [Openstack-sigs] [all][api] POST /api-sig/news Message-ID: Greetings OpenStack community, Today's meeting was on the shorter side but covered several topics. We discussed the migration to StoryBoard, and noted that we need to send word to Gilles and the GraphQL experimentors that the board is in place and ready for their usage. The GraphQL work was also highlighted as there has been a review[7] posted along with an update[8] to the mailing list. This work is in its early stages, but significant progress has already been made. Kudos to Gilles and the neutron team! We talked briefly about the upcoming PTG and which days might be available for the SIG, but it is too early for such speculation and the group has tabled the idea for now. The API-SIG StoryBoard is now live[9], although it still has the old "api-wg" name. That will be updated when the infra team does the project rename for us. We encourage all new activity to take place here and we are in the process of cleaning up the older links; stay tuned for more information. There is one new guideline change that is just starting its life in the review process[10]. This is an addition to the guideline on errors and although this review is still in the early stages of development any comments are greatly appreciated. As always if you're interested in helping out, in addition to coming to the meetings, there's also: * The list of bugs [5] indicates several missing or incomplete guidelines. * The existing guidelines [2] always need refreshing to account for changes over time. If you find something that's not quite right, submit a patch [6] to fix it. * Have you done something for which you think guidance would have made things easier but couldn't find any? Submit a patch and help others [6]. # Newly Published Guidelines None # API Guidelines Proposed for Freeze Guidelines that are ready for wider review by the whole community. None # Guidelines Currently Under Review [3] * Expand error code document to expect clarity https://review.openstack.org/#/c/577118/ * Update parameter names in microversion sdk spec https://review.openstack.org/#/c/557773/ * Add API-schema guide (still being defined) https://review.openstack.org/#/c/524467/ * A (shrinking) suite of several documents about doing version and service discovery Start at https://review.openstack.org/#/c/459405/ * WIP: microversion architecture archival doc (very early; not yet ready for review) https://review.openstack.org/444892 # Highlighting your API impacting issues If you seek further review and insight from the API SIG about APIs that you are developing or changing, please address your concerns in an email to the OpenStack developer mailing list[1] with the tag "[api]" in the subject. In your email, you should include any relevant reviews, links, and comments to help guide the discussion of the specific challenge you are facing. To learn more about the API SIG mission and the work we do, see our wiki page [4] and guidelines [2]. Thanks for reading and see you next week! # References [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [2] http://specs.openstack.org/openstack/api-wg/ [3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z [4] https://wiki.openstack.org/wiki/API_SIG [5] https://bugs.launchpad.net/openstack-api-wg [6] https://git.openstack.org/cgit/openstack/api-wg [7] https://review.openstack.org/575120 [8] http://lists.openstack.org/pipermail/openstack-dev/2018-June/131557.html [9] https://storyboard.openstack.org/#!/project/1039 [10] https://review.openstack.org/#/c/577118/ Meeting Agenda https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda Past Meeting Records http://eavesdrop.openstack.org/meetings/api_sig/ Open Bugs https://bugs.launchpad.net/openstack-api-wg From jimmy at openstack.org Mon Jun 25 16:44:26 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Mon, 25 Jun 2018 11:44:26 -0500 Subject: [Openstack-sigs] [OpenStack-I18n] [Edge-computing] Edge Computing Whitepaper Translation In-Reply-To: <5B1AB61D.409@openstack.org> References: <20180529135041.cyjrl3vtpwajhicq@yuggoth.org> <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com> <297D0BCC-4EB7-401E-883D-EC5D3BDE1C59@gmail.com> <5B1AB61D.409@openstack.org> Message-ID: <5B311BEA.9010908@openstack.org> Hi all - I wanted to give a quick update on this. Because of some emergency server issues and last minute projects with the OpenStack website, we've had to push these back. We're targeting July 13th for Edge (and hopefully Containers) whitepaper. I'll also add that as part of the plan, we will be creating a new template in our system to make it MUCH easier to push future whitepaper content directly to Zanata. I realize this feels a little slow and painful and everyone is eager to get it up, but I think we'll have a very good system once we're done. Thank you all for your patience! Jimmy Jimmy McArthur wrote: > We are currently targeting June 25 for the initial version of the Edge > whitepaper. However, I'll know more by EOW next. > > Cheers, > Jimmy > > Ildiko Vancsa wrote: >> Hi Akihiro, >> >> It is on our priority list to put up the translated versions in an online format as well as work out to have the .po files available. >> >> Jimmy is looking into it and will give an update once we got some progress. >> >> Thanks and Best Regards, >> Ildikó >> >> >>> On 2018. Jun 8., at 10:14, Akihiro Motoki wrote: >>> >>> Hi all, >>> >>> # I added edge-computing ML as the edge computing team uses a separate list other than the SIG ML. >>> # The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML. >>> >>> What is the next step of the translation of the edge computing white paper with RST? >>> My temporary translation publishing [1] should not be published as-is due to the CC BY-ND license. This is to prove how it works. >>> I would like to move this forward and am happy to help the setup of a repo if needed. >>> >>> Where can we discuss this? >>> The edge computing group meeting is not listed athttp://eavesdrop.openstack.org/ and I don't know when and where it happens. >>> >>> [1]https://amotoki.github.io/edge-computing-whitepaper/ >>> >>> Thanks, >>> Akihiro >>> >>> 2018年5月29日(火) 23:37 Akihiro Motoki: >>> Hi Ildiko and all, >>> >>> I am happy to hear that HTML-based publishing is now on the table :) >>> I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver. >>> RST based process is used much in the community and translation publishinng of project docs which Ian and us are working on will make the continuous publishing easier. >>> I am happy to help setting up a new doc infrastructure and/or publishing translations. >>> >>> Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one. >>> Hopefully we can get a good conclusion for further similar cases. >>> >>> Thanks, >>> Akihiro >>> >>> >>> >>> 2018年5月29日(火) 23:19 Ildiko Vancsa: >>> Hi Akihiro and All, >>> >>> Thank you for your efforts on helping with publishing the white paper in additional languages. >>> >>> I talked to Ian and Frank last week about this topic and the conundrum on the Foundation side whether or not to do the print version for the translations as that is what slows down the process a lot due to the design work it requires. >>> >>> We got to the conclusion with our team from the Foundation (cc’ed Allison, Jimmy and Wes) to do HTML-based publishing to reduce this overhead. We need to clarify now on the process and as Jeremy indicated the licensing as well. >>> >>> Thanks, >>> Ildikó >>> >>> >>>> On 2018. May 29., at 15:50, Jeremy Stanley wrote: >>>> >>>> On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: >>>> [...] >>>>> NOTE: Anyway I need to grant it from the foundation because CC >>>>> Attribution-NoDerivatives 4.0 International license does not allow >>>>> me to share translations without permission. I updated this files >>>>> only for discussion and will close this soon. >>>> [...] >>>> >>>> It seems like this is a really poor choice of license as it's >>>> impairing open collaboration. Even Creative Commons suggests that >>>> the CC BY-ND license is unsuitable for free cultural works: >>>> >>>> https://creativecommons.org/share-your-work/public-domain/freeworks/ >>>> >>>> We should see about getting this changed to CC BY like is used for >>>> other collaborative works produced by our community. >>>> -- >>>> Jeremy Stanley >>>> _______________________________________________ >>>> openstack-sigs mailing list >>>> openstack-sigs at lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >>> _______________________________________________ >>> openstack-sigs mailing list >>> openstack-sigs at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >>> _______________________________________________ >>> Edge-computing mailing list >>> Edge-computing at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing >> > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengfeiyoiua at gmail.com Tue Jun 26 13:45:03 2018 From: chengfeiyoiua at gmail.com (FEI CHENG) Date: Tue, 26 Jun 2018 21:45:03 +0800 Subject: [Openstack-sigs] [first contact] Interesting in Security SIG Message-ID: Dear all, I am new to the list, so I would like to give a short introduction: I come from Huawei Technologies and recently start to participate in the OpenStack security work. I am very interested in the Security SIG, unfortunately, I do not find any developments from the mailing list. Could you please give me some information or some suggestions about it? Thank you very much. :) :) Best regards, Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From lhinds at redhat.com Tue Jun 26 14:02:06 2018 From: lhinds at redhat.com (Luke Hinds) Date: Tue, 26 Jun 2018 15:02:06 +0100 Subject: [Openstack-sigs] [first contact] Interesting in Security SIG In-Reply-To: References: Message-ID: On Tue, Jun 26, 2018 at 2:45 PM, FEI CHENG wrote: > Dear all, > > I am new to the list, so I would like to give a short introduction: I come > from Huawei > Technologies and recently start to participate in the OpenStack security > work. > > I am very interested in the Security SIG, unfortunately, I do not find any > developments from the mailing list. Could you please give me some > information or some suggestions about it? Thank you very much. :) :) > > Best regards, > Ting > > _______________________________________________ > openstack-sigs mailing list > openstack-sigs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > > Hello Fei, https://wiki.openstack.org/wiki/Security-SIG We meet every Thursday on IRC as well: http://eavesdrop.openstack.org/#Security_SIG_meeting Regards, Luke -------------- next part -------------- An HTML attachment was scrubbed... URL: From martialmichel at datamachines.io Tue Jun 26 19:13:58 2018 From: martialmichel at datamachines.io (Martial Michel) Date: Tue, 26 Jun 2018 15:13:58 -0400 Subject: [Openstack-sigs] [Scientific] Scientific SIG meeting today at 2100 UTC Message-ID: IRC Meeting June 27th 2018 2018-06-27 2100 UTC in channel #openstack-meeting 1. Presentation: Utilizing Distributed Clouds for Compute and Storage - Marcus Ebert to present, discuss and answer questions - Video link https://youtu.be/QAda-ee-9Ko - Slides link https://goo.gl/g9EmWg 2. AOB Everybody welcome as usual :) -- Martial Michel, PhD Director of Scientific Computing Data Machines Corp. [ datamachines.io ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From ellstripes at gmail.com Tue Jun 26 18:06:57 2018 From: ellstripes at gmail.com (Ell Marquez) Date: Tue, 26 Jun 2018 13:06:57 -0500 Subject: [Openstack-sigs] OpenStack Mentorship Program Relaunch Message-ID: Hello all, We are happy to announce the relaunch of the OpenStack Mentoring program, and we are kicking off with some changes to the program that we hope will better serve the community. Previously mentoring occurred through one on one partnering of mentor and mentee; this new program will focus on providing mentorship through goal-focused cohorts of mentors. This change will allow mentoring responsibilities to be shared among each group's mentors. The initial cohorts will be: - Get your first patch merged - First CFP submission / Give your first talk - Become COA certified / study for COA - Deploy your first Cloud If you are interested in joining as a mentor or mentee, please sign up at : Mentor Signup: https://openstackfoundation.formstack.com/forms/mentoring_co horts_mentors Mentee Signup: https://openstackfoundation.formstack.com/forms/mentoring_co horts_mentees freenode irc room: #openstack-mentoring Cheers, Ell Marquez and Jill Rouleau -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at openstack.org Thu Jun 28 08:47:31 2018 From: thierry at openstack.org (Thierry Carrez) Date: Thu, 28 Jun 2018 10:47:31 +0200 Subject: [Openstack-sigs] [all] [ptg] PTG high-level schedule Message-ID: Hi everyone, In the attached picture you will find the proposed schedule for the various tracks at the Denver PTG in September. We did our best to avoid the key conflicts that the track leads (PTLs, SIG leads...) mentioned in their PTG survey responses, although there was no perfect solution that would avoid all conflicts. If there is a critical conflict that was missed, please let us know, but otherwise we are not planning to change this proposal. You'll notice that: - The Ops meetup team is still evaluating what days would be best for the Ops meetup that will be co-located with the PTG. We'll communicate about it as soon as we have the information. - Keystone track is split in two: one day on Monday for cross-project discussions around identity management, and two days on Thursday/Friday for team discussions. - The "Ask me anything" project helproom on Monday/Tuesday is for horizontal support teams (infrastructure, release management, stable maint, requirements...) to provide support for other teams, SIGs and workgroups and answer their questions. Goal champions should also be available there to help with Stein goal completion questions. - Like in Dublin, a number of tracks do not get pre-allocated time, and will be scheduled on the spot in available rooms at the time that makes the most sense for the participants. - Every track will be able to book extra time and space in available extra rooms at the event. To find more information about the event, register or book a room at the event hotel, visit: https://www.openstack.org/ptg Note that the first round of applications for travel support to the event is closing at the end of this week ! Apply if you need financial help attending the event: https://openstackfoundation.formstack.com/forms/travelsupportptg_denver_2018 See you there ! -- Thierry Carrez (ttx) -------------- next part -------------- A non-text attachment was scrubbed... Name: ptg4.png Type: image/png Size: 80930 bytes Desc: not available URL: From msm at redhat.com Thu Jun 28 18:04:08 2018 From: msm at redhat.com (Michael McCune) Date: Thu, 28 Jun 2018 14:04:08 -0400 Subject: [Openstack-sigs] [all][api] POST /api-sig/news Message-ID: Greetings OpenStack community, Today's meeting covered a few topics, but was mainly focused on a few updates to the errors guideline. We began with a review of last week's actions. Ed Leafe has sent an email[7] to mailing list to let the folks working on the GraphQL experiments know that the API-SIG StoryBoard was available for them to use to track their progress. We mentioned the proposed time slot[7] for the API-SIG at the upcoming PTG, but as we are still a few months out from that event no other actions were proposed. Next we moved into a discussion of two guideline updates[8][9] that Chris Dent is proposing. The first review adds concrete examples for the error responses described in the guideline, and the second adds some clarifying language and background on the intent of error codes. During discussion among the group, a few minor areas of improvement were identified and recorded on the reviews with updates to be made by Chris. We discussed the transition to StoryBoard[10] during our bug discussion, noting the places where the workflow differs from Launchpad. Chris also showed us a Board[11] that he created to help figure out how to best use this new tool. As always if you're interested in helping out, in addition to coming to the meetings, there's also: * The list of bugs [5] indicates several missing or incomplete guidelines. * The existing guidelines [2] always need refreshing to account for changes over time. If you find something that's not quite right, submit a patch [6] to fix it. * Have you done something for which you think guidance would have made things easier but couldn't find any? Submit a patch and help others [6]. # Newly Published Guidelines None # API Guidelines Proposed for Freeze Guidelines that are ready for wider review by the whole community. None # Guidelines Currently Under Review [3] * Add links to errors-example.json https://review.openstack.org/#/c/578369/ * Expand error code document to expect clarity https://review.openstack.org/#/c/577118/ * Update parameter names in microversion sdk spec https://review.openstack.org/#/c/557773/ * Add API-schema guide (still being defined) https://review.openstack.org/#/c/524467/ * A (shrinking) suite of several documents about doing version and service discovery Start at https://review.openstack.org/#/c/459405/ * WIP: microversion architecture archival doc (very early; not yet ready for review) https://review.openstack.org/444892 # Highlighting your API impacting issues If you seek further review and insight from the API SIG about APIs that you are developing or changing, please address your concerns in an email to the OpenStack developer mailing list[1] with the tag "[api]" in the subject. In your email, you should include any relevant reviews, links, and comments to help guide the discussion of the specific challenge you are facing. To learn more about the API SIG mission and the work we do, see our wiki page [4] and guidelines [2]. Thanks for reading and see you next week! # References [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [2] http://specs.openstack.org/openstack/api-wg/ [3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z [4] https://wiki.openstack.org/wiki/API_SIG [5] https://bugs.launchpad.net/openstack-api-wg [6] https://git.openstack.org/cgit/openstack/api-wg [7] http://lists.openstack.org/pipermail/openstack-dev/2018-June/131881.html [8] https://review.openstack.org/#/c/578369/ [9] https://review.openstack.org/#/c/577118/ [10] https://storyboard.openstack.org/#!/project/1039 [11] https://storyboard.openstack.org/#!/board/91 Meeting Agenda https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda Past Meeting Records http://eavesdrop.openstack.org/meetings/api_sig/ Open Bugs https://bugs.launchpad.net/openstack-api-wg From jean-philippe at evrard.me Fri Jun 29 12:43:40 2018 From: jean-philippe at evrard.me (Jean-Philippe Evrard) Date: Fri, 29 Jun 2018 14:43:40 +0200 Subject: [Openstack-sigs] [all] [ptg] PTG high-level schedule In-Reply-To: References: Message-ID: Schedule lgtm. Looking forward to be there.