November 2017 - Foundation - lists.openinfra.dev

[OpenStack Foundation] Training session reminder: OpenStack Board Meeting, December 5, 2017, 7am pacific
by messenger＠webex.com 28 Nov '17

28 Nov '17

Hello Foundation Mailing List, Alan Clark invites you to participate as an attendee in the OpenStack Board meeting: Topic: OpenStack Board Meeting, December 5, 2017, 7am pacific Host: Alan Clark Date: Tuesday, December 5, 2017 Time: 7:00 am, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 929 974 880 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=t9593ba2a580b4d36877da4… 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=tf1ff3d2e4f184fb694178a… ------------------------------------------------------- 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=56… Show toll-free dialing restrictions: https://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 929 974 880 ------------------------------------------------------- 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=t1669975fd7fa243186a12e… 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] New edge computing mailing list
by Claire Massey 22 Nov '17

22 Nov '17

Edge computing is an emerging area for open technologies. Throughout the past year, edge has been a key topic of discussion for the OpenStack community at the Boston and Sydney Summits and the OpenDev Conference in San Francisco. Content from those events can be found at openstack.org/edge. In an effort to continue to organize efforts around edge, we’ve created a new mailing list to centralize conversations around the topic. If you’d like to continue to stay involved please subscribe to the new mailing list here: http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing In addition to technical conversations, on the mailing list we will share updates about future edge computing activities including a new series of Working Sessions that will kick off next Tuesday, November 28. If you want to join the weekly calls, meeting details will be posted on the mailing list. Thanks, Claire Massey OpenStack Foundation

1 0

[OpenStack Foundation] Diversity WG
by Amy Marrich 20 Nov '17

20 Nov '17

At the Sydney Summit, there seemed to be interest in re-activating the Diversity WG. I am sending this email to give some background on the group as well as to gauge interest. A charter was proposed to the board May 2015 by Egle Sigler, Kavit Munshi, and Imad Sousou to form the group [1]. The group was formed a short time later with Egle Sigler and Carol Barrett as co-chairs and falling under the oversight of the Board. The main work of the diversity group was the diversity survey and its results which were released prior to the Tokyo Summit in October, 2015 and we had about 20 people show up for the Working Group session held there to go over the results. A working group session was also held at the Austin Summit with about 10 people in attendance. It was not long after the Austin summit that the group membership dwindled down and activity ended. Things that came out of the work of the Diversity WG are the Git and Gerrit Lunch and Learn held at the last 5 summits, the Communication Tools Lunch and Learn held in Barcelona, and the Greeters in Barcelona that were provided by the Women of OpenStack. I feel there is still work to do in this area even if only revisiting the survey and gathering more data that can be evaluated and used to help grow the community. If you are interested in helping to revive the Diversity WG please let me know. The group used the Foundation mailing list ( foundation(a)lists.openstack.org) with the [Diversity] tag and still has the #openstack-diversity channel on Freenode though it is not currently being logged as Egle and myself until recently were the only 2 members. Thanks, Amy Marrich (spotz) [1] https://wiki.openstack.org/wiki/Diversity/ProposedCharter

1 0

[OpenStack Foundation] Invitation to OpenStack Board Meeting, December 5, 2017, 7am pacific
by messenger＠webex.com 20 Nov '17

20 Nov '17

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, December 5, 2017, 7am pacific Host: Alan Clark Date: Tuesday, December 5, 2017 Time: 7:00 am, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 929 974 880 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=t0c148c1f532cd4adf90535… 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=t1669975fd7fa243186a12e… To view in other time zones or languages, please click the link https://openstack.webex.com/openstack/k2/j.php?MTID=t4d76b023c54adb47fa6794… ------------------------------------------------------- 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=56… Show toll-free dialing restrictions: https://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 929 974 880 ------------------------------------------------------- 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] Upstream Long Term Support Releases (was Fwd: [openstack-dev] Developer Mailing List Digest November 11-17)
by Davanum Srinivas 17 Nov '17

17 Nov '17

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

1 0

[OpenStack Foundation] OpenStack and open infrastructure
by Jonathan Bryce 05 Nov '17

05 Nov '17

Hi everyone, I wanted to provide a preview of some updates on the Foundation we’ll be talking about in Sydney. This email is a little long, so here’s the quick summary—read on for more detail. We’re seeing some common issues that open infrastructure users are running into when deploying OpenStack and other open source infrastructure projects together, and we want to improve this situation through Foundation efforts focused on the overall state of integration and operations for these users. 1) Planning to reorganize some Foundation community activities more around use cases such as datacenter cloud infrastructure (traditional OpenStack use case), CI/CD (very common use case), container infrastructure (rapidly growing use case), and edge infrastructure (emerging use case) 2) Supporting additional user-driven OSS projects to facilitate integration in these use case (not necessarily OpenStack-branded or part of the existing OpenStack datacenter infrastructure cloud services) 3) Expanding ongoing testing of OpenStack + other open source cloud tools (e.g. OpenStack in CNCF CI, new "OpenLab" testing effort, encouraging broader use of Zuul v3) Now the longer version. As some of you may know a joint leadership group made up of the TC, the UC, the Board and Foundation staff has been doing some work this year to look at where we are 5 years in and what we should be thinking about over the next few years. As we’ve talked about a lot of different aspects of OpenStack and also talked with users, we’ve seen some common trends emerge. First, we continue to see a lot of growth in OpenStack deployments. Second, we also see increasing diversity in the kinds of use cases organizations are deploying OpenStack to serve. We’ve also seen that many users are having difficulty with consuming all of the OpenStack services along with the numerous other open technologies that they often combine. While some of these issues are being helped by more mature commercial offerings in the market, in some cases there are areas that present us with opportunities as a community of developers and users working together. One of the biggest needs is for better integration between open infrastructure components up and down the stack, and we have identified four key elements to improve the state of integration and operations by directing Foundation efforts and activities along these lines. JOINT USE CASES For a successful integration, we need user-driven reasons to combine components. We have hundreds of reasons from users all over the world. Organizations like Yahoo! Japan, eBay, AT&T, Liveperson, Commonwealth, Fico, GAP, Target, JD.com, SKT, GE Healthcare, SAP, China Railway, Fiberhome, Walmart, and China Telecom all combine OpenStack software with other open source tools including Kubernetes, Ceph and Cloud Foundry to solve real business problems. To better define the use cases, we’re planning to organize some of our activities across problem domains: • Datacenter cloud infrastructure • Container infrastructure • Edge infrastructure • CI/CD infrastructure • In the future other drivers of infrastructure usage like machine learning and AI The OpenStack project has always been about enabling truly open collaboration across the industry to produce open source infrastructure software. Tackling these use cases more directly brings our open collaboration model to new areas and new organizations. It will also bring in new users and resources that will benefit our core cloud infrastructure components, users and resources that may not have previously seen where their needs fit in with one single giant thing called "OpenStack." CROSS-COMMUNITY COLLABORATION We have to get the communities together, build trust and deliver standard interfaces we can count on between the components. Interoperability efforts are key to ensuring that these integrations are repeatable, stable and production quality. Within the OpenStack community, we have many upstream contributors to other projects, and often organize events that bring together the developers and users across the communities. FOSTERING NEW OPEN INFRASTRUCTURE PROJECTS The rate of open source innovation has skyrocketed in the last 5 years, however, many projects are developed independently of the production environments in which they must run. We need new projects that focus on the practical implications of deploying large open source software projects together and operating them reliably for years. Lifecycle management of OpenStack has been a top need for users and projects like TripleO, Kolla, OpenStack-Ansible and the new openstack-helm project are tackling this problem head on. When you look outside of the OpenStack core, you see issues such as container security that are preventing adoption among regulated industries. Edge computing and edge clouds represent an incredible opportunity, but have specific deployment and security needs that may require specialized components. These technology components are critical to deployment success and are often being developed separately inside of user organizations. We can help these users open source and collaborate together to build these systems even though some may not necessarily be OpenStack-branded or part of the existing OpenStack datacenter infrastructure cloud services. TESTING OF END-TO-END SYSTEMS Once we have identified a valid use case, ramped up the collaboration and built the tools that make the integration a reality, we need to test the entire end-to-end stack to ensure stability and performance. Many open source communities have excellent internal continuous testing, but users do not run our software in silos, and we can’t test in silos. The OPNFV XCI cross-community CI system is an example that implements this concept today. The new OpenLab initiative from OpenStack community members takes this concept to even more of these projects. The OpenStack Foundation manages a large and growing global community of developers and users who are building and deploying open source software for managing infrastructure in all forms. This is a really exciting mission to be on right now, and I think that updating our strategy to support more integration and operation work is key to helping our users succeed not just with OpenStack clouds, but with their broader open infrastructure ambitions. For those of you who will be in Sydney, we'll be talking more about this and we have a Forum session set up as well on Wednesday in room C4.11: https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20597/o… Thanks, Jonathan

1 0

[OpenStack Foundation] Training session reminder: OpenStack Board and Leadership Meeting, November 5, 2017 at the Sydney OpenStack Summit
by messenger＠webex.com 03 Nov '17

03 Nov '17

Hello Foundation Mailing List, Alan Clark invites you to participate as an attendee in the OpenStack Board meeting: Topic: OpenStack Board and Leadership Meeting, November 5, 2017 at the Sydney OpenStack Summit Host: Alan Clark Date: Saturday, November 4, 2017 Time: 3:00 pm, Pacific Daylight Time (San Francisco, GMT-07:00) Session number: 927 178 747 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=tbc59b21e747a42ee90de51… 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=td8883032963842c68d8163… ------------------------------------------------------- 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=54… Show toll-free dialing restrictions: https://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 927 178 747 ------------------------------------------------------- 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=td9c65c603c054898b4ebc5… 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