From msm at redhat.com Mon Apr 2 22:19:04 2018 From: msm at redhat.com (Michael McCune) Date: Mon, 2 Apr 2018 18:19:04 -0400 Subject: [Openstack-sigs] [api-sig] Any interest in a meetup at the Vancouver Forum? In-Reply-To: References: <429C1B99-4BD5-4608-95B5-D83BB5085958@leafe.com> Message-ID: unless something changes radically between now and then, i most likely will not be able to attend. but i will be there in spirit =) peace o/ On Thu, Mar 29, 2018 at 5:56 PM, Joe Topjian wrote: > I'll be attending the summit/forum in Vancouver. I'm happy to attend any > SDK/API-related sessions or other kinds of meetups. > > On Thu, Mar 29, 2018 at 3:46 PM, Ed Leafe wrote: >> >> Many people from the API-SIG will be attending, so we were hoping to get >> together with people from the SDK community to discuss ways in which we can >> help each other. The main reason for forming a SIG was to break down the >> barriers between API upstream developers and downstream API consumers, so >> this seems like a good time to do just that. >> >> -- Ed Leafe >> >> >> >> >> >> >> _______________________________________________ >> 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 > From stig.openstack at telfer.org Tue Apr 3 19:28:54 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Tue, 3 Apr 2018 20:28:54 +0100 Subject: [Openstack-sigs] [scientific] SIG IRC meeting today, 2100 UTC - Ironic RFEs and Vancouver Forum Message-ID: <1B47D338-00C9-4764-9150-51BACA51F95D@telfer.org> Hi all - We have a Scientific SIG IRC meeting coming up at 2100 UTC today in channel #openstack-meeting. Everyone is welcome. Today’s agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_April_3rd_2018 We’d like to discuss elaborating on the RFEs generated after the PTG on boot-to-ramdisk and kexec. Also, we’d like to talk about how to plan SIG activities around the Vancouver summit, in particular for the Forum. Best wishes, Stig From kennelson11 at gmail.com Tue Apr 3 22:03:46 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 03 Apr 2018 22:03:46 +0000 Subject: [Openstack-sigs] [First Contact] Meeting tonight/tomorrow/today (Depends on your perspective) Message-ID: Hello! Another meeting tonight late/tomorrow depending on where in the world you live :) 0800 UTC Wednesday. Here is the agenda if you have anything to add [1]. Or if you want to add your name to the ping list it is there as well! See you all soon! -Kendall (diablo_rojo) [1] https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda -------------- next part -------------- An HTML attachment was scrubbed... URL: From msm at redhat.com Thu Apr 5 18:08:05 2018 From: msm at redhat.com (Michael McCune) Date: Thu, 5 Apr 2018 14:08:05 -0400 Subject: [Openstack-sigs] [all][api] POST /api-sig/news Message-ID: Greetings OpenStack community, Today's meeting was quite lively with a good discussion about versions and microversions across OpenStack and their usage within the API schema world. We began with a review of outstanding work: elmiko is continuing to work on an update to the microversion history doc[7], and edleafe has reached out[8] to the SDK community to gauge interest in a session for the upcoming Vancouver forum. dtanstur has also also made an update[9] to the HTTP guideline layout that is currently under review. The change was already largely approved; this just improves the appearance of the refactored guidelines. The API-SIG has not confirmed any sessions for the Vancouver forum yet, but we continue to reach out[8] and would ideally like to host a session including the API, SDK and user community groups. The topics and schedule for this session will be highly influenced by input from the larger OpenStack community. If you are interested in seeing this event happen, please add your thoughts to the mailing sent out by edleafe[8]. The next chunk of the meeting was spent discussing the OpenAPI proposal[10] that elmiko has created. The discussion went well and several new ideas were exposed. Additionally, a deep dive into version/microversion usage across the OpenStack ecosystem was exposed with several points being raised about how microversions are used and how they are perceived by end users. There is no firm output from this discussion yet, but elmiko is going to contact interested parties and continue to update the proposal. mordred informed the SIG that he has started working on discover/version things in keystoneauth and should be returning to the related specs within the next few days. and there was much rejoicing. \o/ On the topic of reviews, the SIG has identified one[11] that is ready for freeze this week. Lastly, the SIG reviewed a newly opened bug[12] asking to add a "severity" field to the error structure. After a short discussion, the group agreed that this was not something that should be accepted and have marked it as "won't fix". For more details please see the comments on the bug review. 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 * Add guideline on exposing microversions in SDKs https://review.openstack.org/#/c/532814 # API Guidelines Proposed for Freeze Guidelines that are ready for wider review by the whole community. * Update the errors guidance to use service-type for code https://review.openstack.org/#/c/554921/ # Guidelines Currently Under Review [3] * Break up the HTTP guideline into smaller documents https://review.openstack.org/#/c/554234/ * Add guidance on needing cache-control headers https://review.openstack.org/550468 * 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/444892 [8] http://lists.openstack.org/pipermail/openstack-sigs/2018-March/000353.html [9] https://review.openstack.org/#/c/554234/ [10] https://gist.github.com/elmiko/7d97fef591887aa0c594c3dafad83442 [11] https://review.openstack.org/#/c/554921/ [12] https://bugs.launchpad.net/openstack-api-wg/+bug/1761475 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 dtantsur at redhat.com Fri Apr 6 09:02:56 2018 From: dtantsur at redhat.com (Dmitry Tantsur) Date: Fri, 6 Apr 2018 11:02:56 +0200 Subject: [Openstack-sigs] [openstack-dev] Proposal: The OpenStack Client Library Guide In-Reply-To: <2e195faf-6c1f-6a81-794d-59c97a371fd8@catalyst.net.nz> References: <2e195faf-6c1f-6a81-794d-59c97a371fd8@catalyst.net.nz> Message-ID: <4aaab1f2-1000-5151-115a-f2c19016c8cc@redhat.com> Hi Adrian, Thanks for starting this discussion. I'm adding openstack-sigs ML, please keep it in the loop. We in API SIG are interested in providing guidance on not only writing OpenStack APIs, but also consuming them. For example, we have merged a guideline on consuming API versions: http://specs.openstack.org/openstack/api-wg/guidelines/sdk-exposing-microversions.html More inline. On 04/06/2018 05:55 AM, Adrian Turjak wrote: > Hello fellow OpenStackers, > > As some of you have probably heard me rant, I've been thinking about how > to better solve the problem with various tools that support OpenStack or > are meant to be OpenStack clients/tools which don't always work as > expected by those of us directly in the community. > > Mostly around things like auth and variable name conventions, and things > which often there should really be consistency and overlap. > > The example that most recently triggered this discussion was how > OpenStackClient (and os-client-config) supports certain elements of > clouds.yaml and ENVVAR config, while Terraform supports it differently. > Both you'd often run on the cli and often both in the same terminal, so > it is always weird when certain auth and scoping values don't work the > same. This is being worked on, but little problems like this an an > ongoing problem. > > The proposal, write an authoritative guide/spec on the basics of > implementing a client library or tool for any given language that talks > to OpenStack. > > Elements we ought to cover: > - How all the various auth methods in Keystone work, how the whole authn > and authz process works with Keystone, and how to actually use it to do > what you want. Yes please! > - What common client configuration options exist and how they work > (common variable names, ENVVARs, clouds.yaml), with something like > common ENVVARs documented and a list maintained so there is one > definitive source for what to expect people to be using. Even bigger YES > - Per project guides on how the API might act that helps facilitate > starting to write code against it beyond just the API reference, and > examples of what to expect. Not exactly a duplicate of the API ref, but > more a 'common pitfalls and confusing elements to be ware of' section > that builds on the API ref of each project. Oh yeah, esp. what to be mindful of when writing an SDK in a statically typed language (I had quite some fun with rust-openstack, I guess Terraform had similar issues). > > There are likely other things we want to include, and we need to work > out what those are, but ideally this should be a new documentation > focused project which will result in useful guide on what someone needs > to take any programming language, and write a library that works as we > expect it should against OpenStack. Such a guide would also help any > existing libraries ensure they themselves do fully understand and use > the OpenStack auth and service APIs as expected. It should also help to > ensure programmers working across multiple languages and systems have a > much easier time interacting with all the various libraries they might > touch. > > A lot of this knowledge exists, but it's hard to parse and not well > documented. We have reference implementations of it all in the likes of > OpenStackClient, Keystoneauth1, and the OpenStackSDK itself (which > os-client-config is now a part of), but what we need is a language > agnostic guide rather than the assumption that people will read the code > of our official projects. Even the API ref itself isn't entirely helpful > since in a lot of cases it only covers the most basic of examples for > each API. > > There appears to be interest in something like this, so lets start with > a mailing list discussion, and potentially turn it into something more > official if this leads anywhere useful. :) Count me in :) > > Cheers, > Adrian > > > __________________________________________________________________________ > 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 > From martialmichel at datamachines.io Wed Apr 11 04:06:56 2018 From: martialmichel at datamachines.io (Martial Michel) Date: Wed, 11 Apr 2018 00:06:56 -0400 Subject: [Openstack-sigs] [Scientific] No Scientific SIG IRC meeting on 4/11 Message-ID: With apologies, we must skip this week's Scientific SIG meeting. Thank you -- Martial -------------- next part -------------- An HTML attachment was scrubbed... URL: From luo.lujin at jp.fujitsu.com Fri Apr 13 04:44:53 2018 From: luo.lujin at jp.fujitsu.com (Luo, Lujin) Date: Fri, 13 Apr 2018 04:44:53 +0000 Subject: [Openstack-sigs] [openstack-dev][sig][upgrades] Upgrade SIG IRC meeting poll Message-ID: Hello everyone, Sorry for keeping you waiting! Since we have launched Upgrade SIG [1], we are now happy to invite everyone who is interested to take a vote so that we can find a good time for our regular IRC meeting. Please kindly look at the weekdays in the poll only, not the actual date. Odd week: https://doodle.com/poll/q8qr9iza9kmwax2z Even week: https://doodle.com/poll/ude4rmacmbp4k5xg We expect to alternate meeting times between odd and even weeks to cover different time zones. We'd love that if people can vote before Apr. 22nd. Best, Lujin [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128426.html From stig.openstack at telfer.org Tue Apr 17 18:29:50 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Tue, 17 Apr 2018 19:29:50 +0100 Subject: [Openstack-sigs] [scientific] Meeting: HPCAC round-up, SC 2018 BoF Message-ID: <6FC2F258-F387-4464-BA10-86591AF0A551@telfer.org> Hi All - We have a Scientific SIG IRC meeting coming up at 2100 UTC (about 2.5 hours time) in channel #openstack-meeting. Everyone is welcome. This week’s agenda is available at: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_April_17th_2018 Among other things, we’ll be doing a round-up of the recent HPCAC conference in Lugano, Switzerland, plus planning for SC2018 in November (BoF deadline is imminent). Cheers, Stig -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengh512 at gmail.com Tue Apr 24 02:22:48 2018 From: zhipengh512 at gmail.com (Zhipeng Huang) Date: Tue, 24 Apr 2018 10:22:48 +0800 Subject: [Openstack-sigs] Public Cloud WG PTG Summary Message-ID: Hi team, Sorry for this long overdue summary. During the Dublin PTG as a WG we held two successful discussion sessions on Mon and Tues, and below are the conclusions for this year's planning as far as I could recall. Please feel free to provide further feedback :) - Passport Program v2 - We want to push forward the passport program into the v2 stage this year, including QR code promotion, more member clouds (APAC and North America) and possibly a blockchain experiment (cloud ledger proposal [0]) targeting Berlin Summit if the testnet proves to be successful. - We will be also looking into the possibility of having OpenLab as a special member of Passport Program to help ease some of the difficulties of purely business facing or academic clouds to join the initiative. - Public Cloud Feature List - We will look at a more formal draft of the feature list [1] ready for Vancouver and gather some additional requirement at Vancouver summit. It is also possible for us to do a white paper based upon the feature list content this year, to help user and operators alike better understanding what OpenStack public cloud could offer. - Public Cloud SDK Certification - Chris Hoge, Dims and Melvin have been helping putting up a testing plan for public cloud sdk certification based upon the initial work OpenLab team has achieved. Public Cloud WG will provide a interop-like guideline based upon the testing mechanism. - Public Cloud Meetup - We look forward to have more :) [0] https://docs.google.com/presentation/d/1RYRq1YdYEoZ5KNKwlDDtnunMdoYRAHPjPslnng3VqcI/edit?usp=sharing [1] https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-XSycSkOjqCyMTIedkA/edit?usp=sharing -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: 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 Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengh512 at gmail.com Tue Apr 24 07:22:51 2018 From: zhipengh512 at gmail.com (Zhipeng Huang) Date: Tue, 24 Apr 2018 15:22:51 +0800 Subject: [Openstack-sigs] [publiccloud-wg]KubeCon EU Public Cloud Meetup ? Message-ID: Hi, I'm wondering for people who will attend KubeCon EU is there any interest for a public cloud meetup ? We could discuss many items listed in the ptg summary I just sent out via the meetup :) -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: 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 Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado -------------- next part -------------- An HTML attachment was scrubbed... URL: From stig.openstack at telfer.org Wed Apr 25 08:45:56 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Wed, 25 Apr 2018 09:45:56 +0100 Subject: [Openstack-sigs] [scientific] IRC meeting: Docker and HPC Message-ID: Hello All - We have an IRC meeting at 1100 UTC today in channel #openstack-meeting. Everyone is welcome. Today we have Christian Kniep from Docker joining us to talk about how Docker can be adapted to suit the requirements of HPC workloads. I saw him present on this recently and it should be a very interesting discussion. The full agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_April_25th_2018 Cheers, Stig From msm at redhat.com Thu Apr 26 17:01:39 2018 From: msm at redhat.com (Michael McCune) Date: Thu, 26 Apr 2018 13:01:39 -0400 Subject: [Openstack-sigs] [all][api] POST /api-sig/news Message-ID: Greetings OpenStack community, Today's meeting was quite short and saw a review of everyone's status and the merging of one guideline. We began by sharing our current work and plans for the near future. Although everyone is on tight schedules currently, we discussed the next steps for the work on the OpenAPI proposal [7] and elmiko has mentioned that he will return to updating the microversion patch [8] in the near future. Next was our standard business of reviewing the frozen and open guidelines. The guideline on cache-control headers, which had been frozen last week, received no negative responses from the community, so it was merged. You can find the link to the merged guideline in the section below. As we reviewed our bug status, the group agreed that at some point in the near future we should take another pass at triaging our bugs. This work will take place after the upcoming Vancouver forum. 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 * Add guidance on needing cache-control headers https://review.openstack.org/550468 # 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://gist.github.com/elmiko/7d97fef591887aa0c594c3dafad83442 [8] https://review.openstack.org/#/c/444892/ 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