- Foundation-board - lists.openinfra.dev

Kata Containers launch update
by Claire Massey 07 Dec '17

07 Dec '17

Hi everyone, This week we unveiled Kata Containers, the first project we are piloting under the Container Infrastructure strategic focus area. We wanted to let you know the launch and activities at KubeCon have been very positive and well received. Initially, the project has given the Foundation the opportunity to engage with new companies in the industry who have not historically supported OpenStack and help build bridges across the cloud native community. In the first 36 hours, we had more than 14,000 pageviews on katacontainer.io, nearly 100K impressions on Twitter, and lots of activity on WeChat. A few highlights from the press: TechCrunch Intel and Hyper partner with the OpenStack Foundation to launch the Kata Containers project <https://techcrunch.com/2017/12/05/intel-and-hyper-partner-with-the-openstac…> eWeek OpenStack Launches Kata Containers Project to Improve Security <http://www.eweek.com/cloud/openstack-launches-kata-containers-project-to-im…> SDx Central OpenStack Launches Open Source ‘Kata Containers’ Project <https://www.sdxcentral.com/articles/news/openstack-launches-open-source-kat…> And supportive tweets from influencers in the Kubernetes and OpenStack communities: https://twitter.com/jessfraz/status/938087837303525382 <https://twitter.com/jessfraz/status/938087837303525382> https://twitter.com/MayaKaczorowski/status/938182876507660289 <https://twitter.com/MayaKaczorowski/status/938182876507660289> https://twitter.com/LachlanEvenson/status/938057796548825089 <https://twitter.com/LachlanEvenson/status/938057796548825089> Thank you to the organizations who are supporting the launch of Kata Containers: 99cloud, AWcloud, Canonical, China Mobile, City Network, CoreOS, Dell/EMC, EasyStack, Fiberhome, Google, Intel, Huawei, Hyper.sh, JD.com, Mirantis, NetApp, Red Hat, SUSE, Tencent, Ucloud, UnitedStack and ZTE. We’re starting to plan 2018 activities for Kata Containers and the container infrastructure area. If your organization is interested in getting involved, please let me know. Thanks, Claire

1 0

Fwd: [OpenStack Foundation] Upstream Long Term Support Releases (was Fwd: [openstack-dev] Developer Mailing List Digest November 11-17)
by Jonathan Bryce 04 Dec '17

04 Dec '17

I wanted to highlight this email the Dims sent to the Foundation mailing list. I know many of your companies have expressed interest in longer support terms and this is the opportunity to get involved and help make that a reality. If you want to join efforts around it, I’d suggest either reaching out on the Foundation mailing list or to Dims directly. I’m also happy to answer any questions. Thanks! Jonathan > Begin forwarded message: > > From: Davanum Srinivas <davanum(a)gmail.com> > Subject: [OpenStack Foundation] Upstream Long Term Support Releases (was Fwd: [openstack-dev] Developer Mailing List Digest November 11-17) > Date: November 17, 2017 at 8:31:17 AM CST > To: foundation(a)lists.openstack.org > > Dear Board, > > In the last OpenStack Board meeting, LTS was one of the "big" needs > that was brought up for the health of OpenStack going forward. Please > see the summary below and the etherpad of discussion/proposal at > https://etherpad.openstack.org/p/LTS-proposal > > So far folks from RedHat have added their name (at the bottom of the > etherpad) for getting an effort off the ground. > > I am looking for more folks from the Board, our Platinum and Gold > sponsors to help evangelize this inside their own organizations and > help us move this forward. > > Looking forward to hearing from you all. > > Thanks, > Dims > > ---------- Forwarded message ---------- > From: Mike Perez <thingee(a)gmail.com> > Date: Fri, Nov 17, 2017 at 5:16 AM > Subject: [openstack-dev] Developer Mailing List Digest November 11-17 > To: openstack-dev(a)lists.openstack.org > Cc: openstack-operators(a)lists.openstack.org, user-committee(a)lists.openstack.org > > > Contribute to the Dev Digest by summarizing OpenStack Dev List thread: > > * https://etherpad.openstack.org/p/devdigest > * http://lists.openstack.org/pipermail/openstack-dev/ > > HTML version: https://www.openstack.org/blog/2017/11/developer-mailing-list-digest-novemb… > > Summaries > ========= > * POST /api-sig/news [0] > * Release countdown for week R-14, November 18-24 [1] > [0] - http://lists.openstack.org/pipermail/openstack-dev/2017-November/124633.html > [1] - http://lists.openstack.org/pipermail/openstack-dev/2017-November/124631.html > > > Upstream Long Term Support Releases > =================================== > The Sydney Summit had a very well attended and productive session [0] about to > go about keeping a selection of past releases available and maintained for long > term support (LTS). > > In the past the community has asked for people who are interested in old > branches being maintained for a long time to join the Stable Maintenance team > with the premise that if the stable team grew, it could support more branches > for longer periods. This has been repeated for about years and is not working. > > This discussion is about allowing collaboration on patches beyond end of life > (EOL) and enable whoever steps up to maintain longer lived branches to come up > with a set of tests that actually match their needs with tests that would be > less likely to bitrot due to changing OS/PYPI substrate. We need to lower > expectations of what we're likely to produce will get more brittle the older > the branch gets. Any burden created by taking on more work is absorbed by > people doing the work, as does not unduly impact the folks not interested in > doing the work. > > The idea is to continue the current stable policy more or less as it is. > Development teams take responsibility of a couple of stable branches. At some > point what we now call an EOL branch, instead of deleting it we would leave it > open and establish a new team of people who want to continue to main that > branch. It's anticipated the members of those new teams are coming mostly from > users and distributors. Not all branches are going to attract teams to maintain > them, and that's OK. > > We will stop tagging these branches so the level of support they provide are > understood. Backports and other fixes can be shared, but to consume them, a > user will have to build their own packages. > > Test jobs will run as they are, and the team that maintain the branch could > decide how to deal with them. Fixing the jobs upstream where possible is > preferred, but depending on who is maintaining the branch, the level of support > they are actually providing and the nature of the breakage, removing individual > tests or whole jobs is another option. Using third-party testing came up but is > not required. > > Policies for the new team being formed to maintain these older branches is > being discussed in an etherpad [2]. > > Some feedback in the room expressed they to start one release a year who's > branch isn't deleted after a year. Do one release a year and still keep N-2 > stable releases around. We still do backports to all open stable branches. > Basically do what we're doing now, but once a year. > > Discussion on this suggestion extended to the OpenStack SIG mailing list [1] > suggesting that skip-release upgrades are a much better way to deal with > upgrade pain than extending cycles. Releasing every year instead of a 6 months > means our releases will contain more changes, and the upgrade could become more > painful. We should be release often as we can and makes the upgrades less > painful so versions can be skipped. > > We have so far been able to find people to maintain stable branches for 12-18 > months. Keep N-2 branches for annual releases open would mean extending that > support period to 2+ years. If we're going to do that, we need to address how > we are going to retain contributors. > > When you don't release often enough, the pressure to get a patch "in" > increases. Missing the boat and waiting for another year is not bearable. > > > [0] - https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases > [1] - http://lists.openstack.org/pipermail/openstack-sigs/2017-November/000149.ht… > [2] - https://etherpad.openstack.org/p/LTS-proposal > > -- > Mike Perez (thingee) > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > -- > Davanum Srinivas :: https://twitter.com/dims > _______________________________________________ > Foundation mailing list > Foundation(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

2018 Event Portfolio, PTG Dublin Announcement, OpenStack at KubeCon
by Allison Price 29 Nov '17

29 Nov '17

The OpenStack Summit Sydney is a wrap! Thank you to our attendees and sponsors! Check out the 50 things you missed in Sydney <http://superuser.openstack.org/articles/openstack-sydney-summit-recap-50-th…> as well as over 100 articles covering the event <https://docs.google.com/document/d/1SEKx8DFpBwPjxkgtABUgzMzRt18ZHHbxSl-tTQN…>. OpenStack Events 2018 Sponsorship Opportunities The 2018 OpenStack Foundation events portfolio <https://www.openstack.org/assets/events/2018EventPortfolio-1127.pdf> is now live, including sponsorship opportunities for both Summits, PTGs and OpenDev! As we’re adding more events, we’re also improving the sponsorship packages, including lowering the cost of headline or premier sponsorship of the Summit. These changes are designed to make it easier for our established sponsors to participate in new activities and help us grow the open infrastructure landscape in 2018. You can also expect to see exciting new projects and tracks at our events, covering areas such as container infrastructure, edge computing, CI/CD and machine learning. Stay tuned! OpenStack Summit Vancouver Summit registration opening this week Sponsor sales <https://www.openstack.org/summit/vancouver-2018> open on December 14 at 11:00am CST/17:00 UTC Join us on Thursday, November 30th at 9:00am PST for a webinar where we will highlight what is new for Vancouver and answer any questions about the prospectus and contract process: https://zoom.us/j/630399748 <https://zoom.us/j/630399748> US: +1-669-900-6833 or +1-408-638-0968 or +1-646-876-9923 Meeting ID: 630 399 748 International numbers available: https://zoom.us/zoomconference?m=OvXz5wRp2Ctrtlp74cWpgXUQ0U3-qekR <https://zoom.us/zoomconference?m=OvXz5wRp2Ctrtlp74cWpgXUQ0U3-qekR> Dublin PTG The “Rocky” release Project Teams Gathering will be held at Croke Park in Dublin, Ireland February 26-March 2nd Registration is now live: https://rockyptg.eventbrite.com <https://rockyptg.eventbrite.com/> For more information on hotel block, travel support, visas, and sponsorship opportunities, check out https://www.openstack.org/ptg <https://www.openstack.org/ptg> OpenStack at KubeCon NA | December 6-8 The OpenStack community will have a booth at KubeCon. If your organization is sponsoring, the Foundation is planning to distribute small placards & stickers to show your support for OpenStack and open infrastructure in your booth. If you have a booth and would like a placard, please email denise(a)openstack.org <mailto:denise@openstack.org>. We’ll be promoting joint OpenStack + Kubernetes users like LivePerson, the new Public Cloud Passport <http://www.openstack.org/passport> program and OpenLab <http://www.openlabtesting.org/>, the testing effort which is initially focused on gophercloud, Terraform and Kubernetes. Mark your calendar for these sessions (all times CST at the event in Austin): OpenStack community update <http://events.linuxfoundation.org/events/kubecon-and-cloudnativecon-north-a…>, Thursday 3:50 - 4:25 pm. Containerized Cinder for Bare Metal Kubernetes <http://events.linuxfoundation.org/events/kubecon-and-cloudnativecon-north-a…>, Friday 2:45 - 3:20. SkyTV OpenStack + Kubernetes user story <http://events.linuxfoundation.org/events/kubecon-and-cloudnativecon-north-a…>, Friday 4:25 - 5:00 pm. OpenStack SIG working session, Friday 3:40 - 5:20 pm. And yes, we’re going to roll into a happy hour! Steve Gordon & Chris Hoge are co-chairing the session and accepting agenda items. Please join us and send your teams -- we need resources and help with OpenLab end-to-end testing and updating/maintaining the OpenStack provider for Kubernetes! https://etherpad.openstack.org/p/AUS-kubernetes-sig-openstack-deep-dive <https://etherpad.openstack.org/p/AUS-kubernetes-sig-openstack-deep-dive> Participate in cross-community storytelling sessions with OpenStack and Kubernetes community leadership: https://etherpad.openstack.org/p/kubecon-brainstorm-2017 <https://etherpad.openstack.org/p/kubecon-brainstorm-2017> If you are attending KubeCon and would like to volunteer to staff the OpenStack booth, please select a day and time here <https://docs.google.com/spreadsheets/d/10vCQLKQonxztkueeomWXOqo_TKGSOAOZeAG…>.

1 0

OpenLab Forum Session
by Lauren Sell 04 Nov '17

04 Nov '17

Monday at 5:10 - 5:50 pm https://www.openstack.org/summit/sydney-2017/summit-schedule/global-search?… Copying Melvin and Leong, so we can share back notes/plans from the Forum session with the Board, and potentially dive deeper at a future board meeting.

1 0

Board High Five Meeting, Wednesday November 8, 4:10pm
by Alan Clark 26 Oct '17

26 Oct '17

Directors, The Board High Five Mtg is scheduled on Wednesday, 4:10-4:40pm, in Room C2.6 on Level 2. This meeting has been slated for every Summit in case a quick meeting is needed during the Summit. Reality has shown that these meetings have been a great moment to reflect on and summarize the Summit. Thanks, AlanClark

1 0

Platinum Membership Opening
by Jonathan Bryce 26 Oct '17

26 Oct '17

Hi everyone, IBM’s Platinum Membership of the OpenStack Foundation will end this year which will result in a Platinum opening starting January 2018. The Board will consider candidates to fill the Platinum spot at an upcoming meeting. The Platinum Member Agreement (http://www.openstack.org/legal/platinum-member-policy/ <http://www.openstack.org/legal/platinum-member-policy/>) covers the process for new Platinum Members to be elected in broad terms in Section 4. You can also review the general framework the Board uses to consider new Gold and Platinum members: https://wiki.openstack.org/wiki/Governance/Foundation/PotentialMemberCriter… <https://wiki.openstack.org/wiki/Governance/Foundation/PotentialMemberCriter…> Please reach out to me if your organization is interested or if you have any questions. Thanks, Jonathan

2 1

Board Resignation
by Jessica Field 11 Oct '17

11 Oct '17

Hi Board, I’ve enjoyed my time working with you all on the Board, however due to other pressing commitments, I have decided to resign from my role on the OpenStack Board of Directors and other community activities effective immediately. I feel it is best for me to pass this role to Tristan, as he is better suited to fulfil the requirements of this position and to devote the required time and resources to fulfil this role. It has been a pleasure being part of the OpenStack Board. I have enjoyed working alongside you all and doing what I can to continue Tristan’s longstanding and dedicated effort to build the OpenStack presence in Australia. I wish you all the best and hope to catch up with you sometime in the near future. Regards, Jess Jessica Field | Marketing Director Email: jess(a)aptira.com<mailto:jess@aptira.com> | Mobile: 0432 087 253<tel:0432087253> General Enquiries: +61 2 8030 2333 <tel:61280302333> | Australia Toll Free: 1800 APTIRA<tel:1800278472> [cid:image001.jpg@01D34292.8CD082D0]<https://www.aptira.com/>

5 5

Oct 13 call to discuss strategy around additional projects
by Claire Massey 11 Oct '17

11 Oct '17

Hi everyone, As mentioned in the board meeting yesterday, a group has formed to help define the strategic focus areas for supporting additional new projects under OpenStack Foundation management. This Friday, October 13, at 9:00am CST (14:00 UTC) we will host a second meeting for those who have expressed interest in being part of this effort. If you have not already expressed interest in this effort but would like to participate in the call, please email me and I’ll send you the invite. During the call on Friday we will continue the discussion around our key principles, project guidelines and structure that we'd like to get your feedback on. This is a collection of our thoughts, input we’ve already received and information we’d make available to incoming projects: https://docs.google.com/presentation/d/1vhBRo7jLG0fmzktdnG1EhHwE5L7eYdIFkux… <https://docs.google.com/presentation/d/1vhBRo7jLG0fmzktdnG1EhHwE5L7eYdIFkux…> The permissions should be set to “anyone with the link can comment” but please let me know if you have trouble accessing the document, and I can send it as an attachment. Thanks, Claire

1 0

OpenStack Deliverables Map -- Feedback Request
by Lauren Sell 11 Oct '17

11 Oct '17

Hi everyone, One more follow up note from me today. In the joint leadership meeting we presented a map of OpenStack deliverables, which includes a new structure to categorize OpenStack projects. The goal is to better communicate “what is OpenStack?” by bucketing the projects according to functionality and simplifying the appearance of the project ecosystem. The map also hides many of the supporting projects, like libraries, to focus on the user-centric deliverables view. Here’s a link to the presentation the working group put together with the map: https://docs.google.com/presentation/d/1qQ1oCjhEE3bjtjkPydGhyeR6vFyuyFeOhbw… <https://docs.google.com/presentation/d/1qQ1oCjhEE3bjtjkPydGhyeR6vFyuyFeOhbw…> We’re looking for feedback on the map on slide #3 and the buckets listed on slide #5 (which would equate to git repo directories). If you are unable to view the google presentation, please let me know, and I’ll email you the PDF. Next steps: 1. Please add any feedback to this etherpad by September 19th — https://etherpad.openstack.org/p/map-feedback <https://etherpad.openstack.org/p/map-feedback> 2. Thierry and I are going to review/consolidate the feedback and work with the Foundation design team to do another rev of the diagram. 3. Once we have the next version ready, we’ll share it back and likely set up a meeting to refine/debate any final points. The goal is to present the new map by Sydney, but we still need to work through the timeline for updating directory names / Github mirrors and communicating that to all appropriate stakeholders. Thanks, Lauren

4 5

Re: [Foundation Board] Board Resignation
by Steven Dake (stdake) 11 Oct '17

11 Oct '17

Jessica, Sad to see you depart. I wish you well. Regards, -steve From: Jessica Field <jess(a)aptira.com> Date: Tuesday, October 10, 2017 at 7:17 PM To: "Foundation-board(a)lists.openstack.org" <foundation-board(a)lists.openstack.org> Cc: Tristan Goode <tristan(a)aptira.com> Subject: [Foundation Board] Board Resignation Hi Board, I’ve enjoyed my time working with you all on the Board, however due to other pressing commitments, I have decided to resign from my role on the OpenStack Board of Directors and other community activities effective immediately. I feel it is best for me to pass this role to Tristan, as he is better suited to fulfil the requirements of this position and to devote the required time and resources to fulfil this role. It has been a pleasure being part of the OpenStack Board. I have enjoyed working alongside you all and doing what I can to continue Tristan’s longstanding and dedicated effort to build the OpenStack presence in Australia. I wish you all the best and hope to catch up with you sometime in the near future. Regards, Jess Jessica Field | Marketing Director Email: jess(a)aptira.com<mailto:jess@aptira.com> | Mobile: 0432 087 253<tel:0432087253> General Enquiries: +61 2 8030 2333 <tel:61280302333> | Australia Toll Free: 1800 APTIRA<tel:1800278472> [cid:image001.jpg@01D3424F.CAAF92F0]<https://www.aptira.com/>

1 0