November 2018 - Foundation - lists.openinfra.dev

[OpenStack Foundation] TechEvent Telegram Channel
by Yash Pal 16 Nov '18

16 Nov '18

Hi Folks, I writing the mail on behalf of GlobalTechEvent community. We just started Telegram Channel where we are trying to post all Technical Related event which is happening in India right now. If anyone would like to join this channel. Please feel free to join the channel. One more thing if anyone wants to post your Technical related event on our channel you can also connect with @kavingates (on Telegram). Our channel link - https://t.me/GlobalTechEvents Kavin Gates - http://t.me/kavingates Thanks in advance Regards Yash

1 0

[OpenStack Foundation] Feedback on Vision for OpenStack clouds
by Zane Bitter 15 Nov '18

15 Nov '18

Attached is a copy of the 'Vision for OpenStack Clouds' that the TC is working on and which I presented at the board meeting on Monday.[1] If any board members (or anybody else in the community) would like to give feedback, you can do so in any of these places: * In the Forum session today at 14.30 in M8 https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22818/v… * On the Gerrit review https://review.openstack.org/592205 * In this thread thanks, Zane. [1] https://docs.google.com/presentation/d/1wcG7InY2A5y67dt5lC14CI1gQHGZ3db8-ys…

1 0

[OpenStack Foundation] [Diversity] Meeting Cancelled
by Amy 14 Nov '18

14 Nov '18

The meeting for Monday 11/19 is cancelled. Thanks, Amy (spotz)

1 0

[OpenStack Foundation] [all] All Hail our Newest Release Name - OpenStack Train
by Tony Breeds 13 Nov '18

13 Nov '18

Hi everybody! As the subject reads, the "T" release of OpenStack is officially "Train". Unlike recent choices Train was the popular choice so congrats! Thanks to everybody who participated and help with the naming process. Lets make OpenStack Train the release so awesome that people can't help but choo-choo-choose to run it[1]! Yours Tony. [1] Too soon? Too much?

1 0

[OpenStack Foundation] November 12 Board Meeting
by Jonathan Bryce 12 Nov '18

12 Nov '18

Today, the OpenStack Foundation Board of Directors met in person in Berlin with several directors also dialing in remotely. The agenda was posted on the wiki[1]. The Board meeting took place in the first portion of a full-day meeting that brought together the developer community leaders, user committee leaders and Board members for a joint leadership meeting. At the beginning of the meeting, the Board approved several sets of minutes from past meetings that had happened earlier this year. These minutes will be posted to the wiki in the coming days. Next, the OSF staff covered several items. The slides we covered are now linked on the wiki agenda page. First, we reviewed the status of the strategic project governance work that has been ongoing throughout the year. The Board then voted unanimously to approve the most recent iteration of the Bylaws amendments. This is the version that was previously circulated here on the foundation mailing list[2]. Following this approval, the Board updated the initial pilot project resolution from November 2017 to be inline with the new framework. This is an exciting step in the work we’ve been taking on for over a year now as we move to support more and more open infrastructure collaboration in OpenStack and beyond. I want to thank everyone who has participated in the process and given us great feedback in 2017 and 2018. Next up, we will begin to communicate more broadly this week about the progress on these changes, especially as we head into the next step of finalizing these amendments. Some of these changes will require additional approval by the different member classes of the Foundation (Individual, Gold and Platinum). The Platinum Members will vote on them in the coming weeks and the Gold and Individual Members will vote on the Bylaws as part of their 2019 Director elections in January. We also covered some updates around the community and market as we head into the OpenStack Summit Berlin. There’s a lot of great data and information in the slides, but there were a few things that we wanted to specifically highlight. First, we’ve seen a lot of growth in adoption of ironic (in the user survey, it’s grown from being used in 9% of production deployments to 24% in the last 2 years), and want to make sure we’re giving OpenStack Bare Metal Clouds visibility as a very powerful open infrastructure tool. Second, we continue to see very high engagement in the OpenStack project with 70,000 merged changes in the last year. During the Rocky cycle, the community averaged 182 changes every day—that’s a very strong pace of progress. Third, we see big opportunities to continue down the path of building out a community oriented around open infrastructure, and research we’ve done this year shows that users see real benefits in having open choices throughout their stack, including flexibility and control, the ability to innovate quickly, and interoperable options to choose from. After those updates, we previewed some of our early planning for 2019. We want to focus on strengthening OpenStack, especially the developer and user communities and have some specific programs we are looking at building out. We also talked about additional areas that we should be looking at for how we can better support use cases and our existing community. As part of this discussion, we talked about AI and machine learning as an area where we already see a lot of community activity. The Board then approved adding a strategic focus area for AI and machine learning to the existing areas. Finally, we had a brief discussion covering the finances of the Foundation and what potential evolution we might want to see as the scope of the OSF changes over the coming years. This is an item that will have more discussion and probably continue into next year. After this, Arkady Kanevsky gave an update from the Finance Committee to report that the committee has been meeting regularly and we are on track to meet our overall breakeven budget goal for the year. Finally, the Board discussed and adopted several updated 2018.11 guidelines from the Interop Working Group (materials are linked on the wiki). After those items, the Board meeting officially closed and the remainder of the day was filled with updates from the OpenStack Technical Committee, the OpenStack User Committee, and leaders from each of the current four pilot projects. The afternoon presentations for the leadership meeting are also linked on the wiki page and are worth looking through. Thanks to everyone who attended, and again especially all of you who participated in the strategic project work. We’ll continue many of these discussions through the week here in Berlin and I look forward to seeing many of you in person. Jonathan 1. https://wiki.openstack.org/wiki/Governance/Foundation/12Nov2018BoardMeeting 2. http://lists.openstack.org/pipermail/foundation/2018-November/002647.html

1 0

[OpenStack Foundation] Four Opens Doc
by Chris Hoge 12 Nov '18

12 Nov '18

Earlier this year, the OpenStack Foundation staff had the opportunity to brainstorm some ideas about how to express the values behind The Four Opens and how they are applied in practice. As the Foundation grows in scope to include new strategic focus areas and new projects, we felt it was important to provide explanation and guidance on the principles that guide our community. We’ve collected these notes and have written some seeds to start this document. I’ve staged this work into github and have prepared a review to move the work into OpenStack hosting, turning this over to the community to help guide and shape it. This is very much a work in progress, but we have a goal to polish this up and make it an important document that captures our vision and values for the OpenStack development community, guides the establishment of governance for new top-level projects, and is a reference for the open-source development community as a whole. I also want to be clear that the original Four Opens, as listed in the OpenStack governance page, is an OpenStack TC document. This project doesn’t change that. Instead, it is meant to be applied to the Foundation as a whole and be a reference to the new projects that land both as pilot top-level projects and projects hosted by our new infrastructure efforts. Thanks to all of the original authors of the Four-Opens for your visionary work that started this process, and thanks in advance to the community members who will continue to grow and evolve this project. Chris Hoge OpenStack Foundation Four Opens: https://governance.openstack.org/tc/reference/opens.html New Project Review Patch: https://review.openstack.org/#/c/617005/ Four Opens Document Staging: https://github.com/hogepodge/four-opens

1 0

[OpenStack Foundation] Training session reminder: OpenStack Board Meeting 12 November 2018 - Berlin Summit
by messenger＠webex.com 11 Nov '18

11 Nov '18

Hello Foundation Mailing List, Alan Clark invites you to participate as an attendee in the OpenStack Board meeting: Topic: OpenStack Board Meeting 12 November 2018 - Berlin Summit Host: Alan Clark Date: Monday, November 12, 2018 Time: 12:00 am, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 929 150 522 Session password: This session does not require a password. ------------------------------------------------------- To join the session ------------------------------------------------------- 1. Go to https://openstack.webex.com/openstack/k2/j.php?MTID=tafe392d5672848ea979dde… 2. Enter your name and email address (or registration ID). 3. Enter the session password: This session does not require a password. 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link https://openstack.webex.com/openstack/k2/j.php?MTID=te5d312e8cd884a7b821cc0… ------------------------------------------------------- To join the session by phone only ------------------------------------------------------- To receive a call back, provide your phone number when you join the training session, or call the number below and enter the access code. Call-in toll number (US/Canada):1-650-479-3207 Call-in toll-free number (US/Canada):1-855-244-8681 Having trouble dialing in? Try these backup numbers: Call-in toll-free number (US/Canada):1-855-244-8681 Call-in toll number (US/Canada):1-650-479-3207 Global call-in numbers: https://openstack.webex.com/openstack/globalcallin.php?serviceType=TC&ED=72… Show toll-free dialing restrictions: https://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 929 150 522 ------------------------------------------------------- For assistance ------------------------------------------------------- You can contact Alan Clark at: aclark(a)suse.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://openstack.webex.com/openstack/k2/j.php?MTID=t8ea012915b779d2c25029d… https://www.webex.com IMPORTANT NOTICE: This Webex service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.

1 0

[OpenStack Foundation] Diversity and Inclusion at OpenStack Summit
by Amy Marrich 08 Nov '18

08 Nov '18

I just wanted to pass on a few things we have going on during Summit that might be of interest! *Diversity and Inclusion GroupMe* - Is it your first summit and you don't know anyone else? Maybe you just don't want to travel to and from the venue alone? In the tradition of WoO, I have created a GroupMe so people can communicate with each other. If you would like to be added to the group please let me know and I'll get you added! *Night Watch Tour *- On Wednesday night at 10PM, members of the community will be meeting up to go on a private Night Watch Tour[0]! This is a non-alcoholic activity for those wanting to get with other Stackers, but don't want to partake in the Pub Crawl! We've been doing these since Boston and they're a lot of fun. The cost is 15 euros cash and I do need you to RSVP to me as we will need to get a second guide if we grow too large! Summit sessions you may wish to attend: Tuesday - *Speed Mentoring Lunch* [1] 12:30 -1:40 - We are still looking for both Mentors and Mentees for the session so please RSVP! This is another great way to meet people in the community, learn more and give back!!! *Cohort Mentoring BoF* [2] 4:20 - 5:00 - Come talk to the people in charge of the Cohort Mentoring program and see how you can get involved as a Mentor or Mentee! *D&I WG Update* [3] 5:10- 5:50 - Learn what we've been up to, how you can get involved, and what's next. Wednesday - *Git and Gerrit Hands-On Workshop* [4] 3:20 - 4:20 - So you've seen some exciting stuff this week but don't know how to get setup to start contributing? This session is for you in that we'll walk you through getting your logins, your system configured and if time allows even how to submit a bug and patch! Thursday - *Mentoring Program Reboot* [5] 3:20 - 4:00 - Learn about the importance of mentoring, the changes in the OPenStack mentoring programs and how you can get involved. Hope to see everyone in Berlin next week! Please feel free to contact me or grab me in the hall next week with any questions or to join in the fun! Amy Marrich (spotz) Diversity and Inclusion WG Chair [0] - http://baerentouren.de/nachtwache_en.html [1] - https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22873/s… [2] - https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22892/l… [3] - https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22893/d… [4] - https://www.openstack.org/summit/berlin-2018/summit-schedule/events/21943/g… [5] - https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22443/m…

1 1

[OpenStack Foundation] [all] Results of the T release naming poll. open
by Tony Breeds 07 Nov '18

07 Nov '18

Hello all! The results of the naming poll are in! **PLEASE REMEMBER** that these now have to go through legal vetting. So it is too soon to say 'OpenStack Train' is our next release, given that previous polls have had some issues with the top choice. In any case, the names will be sent off to legal for vetting. As soon as we have a final winner, I'll let you all know. https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_aac97f1cbb6c61df&rkey=7… Result 1. Train (Condorcet winner: wins contests with all other choices) 2. Tiger loses to Train by 142–70 3. Timber loses to Train by 142–72, loses to Tiger by 100–76 4. Trail loses to Train by 150–55, loses to Timber by 93–62 5. Telluride loses to Train by 155–56, loses to Trail by 81–69 6. Teller loses to Train by 158–46, loses to Telluride by 70–67 7. Treasure loses to Train by 151–52, loses to Teller by 68–67 8. Teakettle loses to Train by 158–49, loses to Treasure by 75–67 9. Tincup loses to Train by 157–47, loses to Teakettle by 67–60 10. Turret loses to Train by 158–48, loses to Tincup by 75–56 11. Thomas loses to Train by 159–42, loses to Turret by 66–63 12. Trinidad loses to Train by 153–44, loses to Thomas by 70–56 13. Troublesome loses to Train by 165–41, loses to Trinidad by 69–62 14. Thornton loses to Train by 163–35, loses to Troublesome by 62–59 15. Tyrone loses to Train by 163–35, loses to Thornton by 58–38 16. Tarryall loses to Train by 170–31, loses to Tyrone by 54–50 17. Timnath loses to Train by 170–23, loses to Tarryall by 60–32 18. Tiny Town loses to Train by 168–29, loses to Timnath by 45–43 19. Torreys loses to Train by 167–29, loses to Tiny Town by 48–40 20. Trussville loses to Train by 169–25, loses to Torreys by 43–34

1 0

[OpenStack Foundation] [all]Naming the T release of OpenStack -- Poll open
by Tony Breeds 05 Nov '18

05 Nov '18

Hi folks, It is time again to cast your vote for the naming of the T Release. As with last time we'll use a public polling option over per user private URLs for voting. This means, everybody should proceed to use the following URL to cast their vote: https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e4… We've selected a public poll to ensure that the whole community, not just gerrit change owners get a vote. Also the size of our community has grown such that we can overwhelm CIVS if using private urls. A public can mean that users behind NAT, proxy servers or firewalls may receive an message saying that your vote has already been lodged, if this happens please try another IP. Because this is a public poll, results will currently be only viewable by myself until the poll closes. Once closed, I'll post the URL making the results viewable to everybody. This was done to avoid everybody seeing the results while the public poll is running. The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results will be posted shortly after. [1] https://governance.openstack.org/tc/reference/release-naming.html --- According to the Release Naming Process, this poll is to determine the community preferences for the name of the T release of OpenStack. It is possible that the top choice is not viable for legal reasons, so the second or later community preference could wind up being the name. Release Name Criteria --------------------- Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again. The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable. The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process. The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo". Names which do not meet these criteria but otherwise sound really cool should be added to a separate section of the wiki page and the TC may make an exception for one or more of them to be considered in the Condorcet poll. The naming official is responsible for presenting the list of exceptional names for consideration to the TC before the poll opens. Exact Geographic Region ----------------------- The Geographic Region from where names for the S release will come is Colorado Proposed Names -------------- * Tarryall * Teakettle * Teller * Telluride * Thomas : the Tank Engine * Thornton * Tiger * Tincup * Timnath * Timber * Tiny Town * Torreys * Trail * Trinidad * Treasure * Troublesome * Trussville * Turret * Tyrone Proposed Names that do not meet the criteria (accepted by the TC) ----------------------------------------------------------------- * Train🚂 : Many Attendees of the first Denver PTG have a story to tell about the trains near the PTG hotel. We could celebrate those stories with this name Yours Tony.

2 3