August 2018 - Foundation - lists.openinfra.dev

[OpenStack Foundation] OSF Open Infrastructure Projects
by Jonathan Bryce 30 Aug '18

30 Aug '18

Hi everyone, I wanted to provide an update on how things have been progressing with the strategic planning for the OpenStack Foundation (OSF) that we kicked off in 2017 among the TC, UC and Board. Through the course of those discussions last year, we identified several opportunities for the Foundation and community. After the joint meeting in November of 2017, the Board of Directors authorized Foundation staff to start organizing some activities around strategic focus areas and to pilot new open infrastructure projects. At OpenStack Summit Sydney, we announced a new integration strategy, shifting our focus from being solely about the production of the OpenStack software, to more broadly helping organizations embrace open infrastructure: using and combining open source solutions to fill their needs in terms of IT infrastructure. This involves finding common use cases, collaborating across communities, building the required new technology and testing everything end to end[1]. In December 2017, we launched our Kata Containers, our first pilot project [2]. In the first half of 2018, we worked to get Kata off the ground and set up Zuul as a standalone project, and more recently started piloting 2 additional projects, Airship and StarlingX. Through these pilots, we have learned a lot and are now ready to put more structure around the future of our work with additional open infrastructure projects. In June, the Board formed a working group to develop a plan and the policies for this more formal structure. The Board will be reviewing the output of the working group at upcoming meetings, including in September, so now we are looking to get feedback on some of the initial thoughts ahead of the next working group and Board meetings. As laid out at the end of last year, there are two main concepts that will guide the efforts of the Foundation: strategic focus areas (SFAs) and projects. Strategic focus areas (SFA) "Open infrastructure" is an ever-evolving construct, as the computing needs of organizations evolve with the technology. SFAs are driven by usage scenarios and help direct the OSF action to specific segments of the open infrastructure market. The intent is to provide focus and content for use cases without trying to shove every possible type of cloud or deployment scenario into a single bucket. SFAs include all of the activities to achieve a specific strategic outcome (e.g. hosting projects, throwing events, building and managing community activities, education, marketing.) Defining SFAs is part of the regular strategic planning activities of the OSF Board of Directors. Focus areas may be proposed, discussed, approved or abandoned during strategic reviews. Those strategic reviews should happen as-needed, but at least annually. Current SFAs include datacenter cloud, container infrastructure, edge and CI/CD. Projects Projects address the need to build the required new technology to fill the goals of our strategic focus areas. The OSF enables those projects to be successfully set up as open collaborations, by providing IP management, a set of base collaboration rules (the 4 Opens) and upstream and downstream community support services. Open source projects that do not wish to be set up as open collaborations can still be included and integrated in open infrastructure solutions, however they will see little benefit in being hosted by the OSF. SFAs and projects do not form a hierarchy. A project does not "belong" to an SFA, however all projects supported by the OSF help achieve the goals of one or more of our defined SFAs, and all projects supported by the OSF follow the 4 Opens. Projects may be composed of several components or deliverables, as long as they are under a common defined scope and governance. Projects go through several recognition stages which define the level of engagement of OSF resources. Open development hosting OSF members already maintain a community-operated set of development and CI services enabling open collaboration at a massive scale. As we believe that open source software should be developed using open source tools, these services use only free and open source software. This project infrastructure embodies the 4 Opens and enables projects to follow them. The infra team is working to provide these services more broadly and in a non-OpenStack branded way to avoid the confusion that sometimes happens now when all hosted code resides in OpenStack namespaces. Any open source project may be hosted here and does not involve any recognition by the OSF. For projects that are candidates to become OSF-supported projects, we believe that they should start with code, so hosting them on community infrastructure is a recommended prepatory step. Stage 1: Pilot projects As part of meeting the goals of our strategic focus areas, the OSF staff will evaluate projects that fill gaps in open infrastructure adoption or enable specific use cases for OpenStack technologies. The OSF staff (as represented by its Executive Director) can select pilot projects where it identifies promising new technology pieces and encourage them to be set up as an open collaboration following the 4 Opens. The OSF staff then helps the pilot projects by establishing initial branding, setting up project websites, guiding them to set up proper governance, and understanding and adopting the 4 Opens. Such pilot projects may call themselves "a project supported by the OSF". Current pilot projects are Kata containers, Zuul, Airship, and StarlingX. Stage 2: Confirmed projects Within 18 months, a pilot project will be reviewed by the Board, in order to decide on long-term investment of OSF resources to support it. The Board will review the strategic alignment of the project with the Foundation's SFAs, but also their progress in setting up an effective open collaboration. To that effect, the project first needs to have set up a governance model and have produced at least one release since it was selected as a pilot. The Board will take community input in order to inform its decision, in particular, from the technical leadership of existing OSF projects, in terms of complementarity, and 4 Opens adoption. It should also seek the input from open infrastructure users in terms of SFA alignment. At that point the Board may decide to confirm the project as a long-term OSF investment, abandon the pilot or defer its decision. Confirmed projects may call themselves "a top-level project under the OSF". Currently, only the OpenStack project has been recognized by the OSF board (under the bylaws) as a long-term investement for the OSF and therefore belongs to that category. This represents the basic structure of our current thinking after a few iterations. The next Board meeting will be September 18 and we will review this at that meeting so we can move to fleshing out the detailed work that needs to be done to finalize this around the OpenStack Summit Berlin (potential bylaws changes for instance). Thanks, Jonathan 1. http://lists.openstack.org/pipermail/foundation/2017-November/002532.html 2. http://lists.openstack.org/pipermail/foundation/2017-December/002541.html

1 0

[OpenStack Foundation] [Diversity] Meeting Reminder
by Amy Marrich 27 Aug '18

27 Aug '18

Just a reminder we'll be meeting today in #openstack-diversity at 19:00 UTC Sorry for the late reminder, Amy (spotz)

1 0

[OpenStack Foundation] OpenStack Diversity and Inclusion Survey
by Amy Marrich 15 Aug '18

15 Aug '18

The Diversity and Inclusion WG is asking for your assistance. We have revised the Diversity Survey that was originally distributed to the Community in the Fall of 2015 and are looking to update our view of the OpenStack community and it's diversity. We are pleased to be working with members of the CHAOSS project who have signed confidentiality agreements in order to assist us in the following ways: 1) Assistance in analyzing the results 2) And feeding the results into the CHAOSS software and metrics development work so that we can help other Open Source projects Please take the time to fill out the survey and share it with others in the community. The survey can be found at: https://www.surveymonkey.com/r/OpenStackDiversity Thank you for assisting us in this important task! Amy Marrich (spotz) Diversity and Inclusion Working Group Chair

1 0

[OpenStack Foundation] Berlin Summit Schedule Live!
by Ashlee Ferguson 14 Aug '18

14 Aug '18

The schedule for the Berlin Summit <http://www.openstack.org/summit/berlin-2018/summit-schedule> is live! Check out 100+ sessions, demos, and workshops covering 35+ open source projects in the following Tracks: • CI/CD • Container Infrastructure • Edge Computing • HPC / GPU / AI • Private & Hybrid Cloud • Public Cloud • Telecom & NFV Log in with your OpenStackID <https://openstackid.org/> and start building your schedule now! Register for the Summit <https://openstacksummit2018berlin.eventbrite.com/> - Get your Summit ticket for USD $699 before the price increases on August 21 at 11:59pm PT (August 22 at 6:59 UTC) For speakers with accepted sessions, look for an email from speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> for next steps on registration. Thank you to our Programming Committee! They have once again taken time out of their busy schedules to help create another round of outstanding content for the OpenStack Summit. The OpenStack Foundation relies on the community-nominated Programming Committee, along with your Community Votes to select the content of the summit. If you're curious about this process, you can read more about it here <https://www.openstack.org/summit/berlin-2018/call-for-presentations/selecti…> where we have also listed the Programming Committee members. Interested in sponsoring the Berlin Summit? Learn more here <https://www.openstack.org/summit/berlin-2018/sponsors/#how-to-sponsor> Cheers, Ashlee Ashlee Ferguson OpenStack Foundation ashlee(a)openstack.org

1 0

[OpenStack Foundation] Speaker Selection Process: OpenStack Summit Berlin
by Jimmy McArthur 13 Aug '18

13 Aug '18

Greetings! The speakers for the OpenStack Summit Berlin will be announced August 14, at 4:00 AM UTC. Ahead of that, we want to take this opportunity to thank our Programming Committee! They have once again taken time out of their busy schedules to help create another round of outstanding content for the OpenStack Summit. The OpenStack Foundation relies on the community-nominated Programming Committee, along with your Community Votes to select the content of the summit. If you're curious about this process, you can read more about it here <https://www.openstack.org/summit/berlin-2018/call-for-presentations/selecti…> where we have also listed the Programming Committee members. If you'd like to nominate yourself or someone you know for the OpenStack Summit Denver Programming Committee, you can do so here: * *https://openstackfoundation.formstack.com/forms/openstackdenver2019_programmingcommitteenom Thanks a bunch and we look forward to seeing everyone in Berlin! Cheers, Jimmy * <https://openstackfoundation.formstack.com/forms/openstackdenver2019_program…>*

3 2

[OpenStack Foundation] [Diversity] Meeting Reminder 8/12 @17:00 UTC
by Amy Marrich 11 Aug '18

11 Aug '18

Just a reminder we will be meeting tomorrow at 19:00 UTC in the #openstack-diversity channel. Agenda is available. [0] Thanks, Amy (spotz) [0] - https://etherpad.openstack.org/p/diversity-wg-agenda

2 2

[OpenStack Foundation] Invitation to OpenStack Board meeting Sept 18, 1pm to 3pm pacific
by messenger＠webex.com 06 Aug '18

06 Aug '18

Hello Foundation Mailing List, The OpenStack Board invites you to participate as an attendee in the following OpenStack board meeting. We will be using WebEx to facilitate the meeting and audio conferencing. Please join the WebEx session then follow the instructions to either join the telephone conference service or to join via VOIP. Topic: OpenStack Board meeting Sept 18, 1pm to 3pm pacific Host: Alan Clark Date: Tuesday, September 18, 2018 Time: 1:00 pm, Pacific Daylight Time (San Francisco, GMT-07:00) Session number: 929 101 327 Session password: This session does not require a password. Agenda: http://wiki.openstack.org/Governance/Foundation ------------------------------------------------------- To join the session ------------------------------------------------------- 1. Go to https://openstack.webex.com/openstack/k2/j.php?MTID=t1cc7e1c5487053bf9c1d8a… 2. Enter your name and email address. 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 add this session to your calendar program (for example Microsoft Outlook), click this link: https://openstack.webex.com/openstack/k2/j.php?MTID=t771d7f825034f3818f1e2b… To view in other time zones or languages, please click the link https://openstack.webex.com/openstack/k2/j.php?MTID=t759d92cea6ad7fcf556be7… ------------------------------------------------------- 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=71… Show toll-free dialing restrictions: https://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 929 101 327 ------------------------------------------------------- For assistance ------------------------------------------------------- You can contact Alan Clark at: aclark(a)suse.com 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] change to Technical Committee leadership structure
by Doug Hellmann 01 Aug '18

01 Aug '18

Last week the Technical Committee approved a change to our charter that creates a formal vice chair position within the TC [1]. Having a vice chair gives us a formal way to designate someone to take over the chair’s duties during an extended absence, which is an important aspect of continuity. Mohammed Naser has generously agreed to serve in the position for this term (up for renewal around the TC elections before the Berlin summit). If you have any questions about this governance change, please do not hesitate to ask here on the list. Doug [1] https://review.openstack.org/#/c/583947/

1 0

[OpenStack Foundation] [DIVERSITY] IRC channel settings
by Amy Marrich 01 Aug '18

01 Aug '18

I have had OpenStack-Infra set #openstack-women and #openstack-diversity so that it requires you to be registered on the nickserv to join. If anyone is not registered and needs help please let me know. This is to combat the recent increase in spam much of which is inappropriate. Thanks for understanding, Amy (spotz)

1 0