From alanclark at openstack.org Wed Feb 5 17:20:33 2020 From: alanclark at openstack.org (Alan Clark) Date: Wed, 5 Feb 2020 10:20:33 -0700 Subject: [Foundation Board] OpenStack Board Meeting 17 March 2020, 1pm-3pm pacific Message-ID: <044101d5dc48$949c3980$bdd4ac80$@openstack.org> Meeting Date: 17 March, 2020 Time: 1pm -3pm pacific Agenda: https://wiki.openstack.org/wiki/Governance/Foundation/17March2020BoardMeetin g The OpenStack Foundation Board of Directors will meet at 1:00pm - 3:00pm Pacific time on March 17, 2020. This will be a conference call meeting. To join the session by phone or computer: Videoconference: https://zoom.us/j/9574980705 International dial-in (audio only): https://zoom.us/zoomconference (conference ID #9574980705) To join the session by phone only: +1 669 900 6833 US (San Jose) OR +1 646 876 9923 US (New York) Meeting ID: 957 498 0705 Please mark your calendars. Thanks, AlanClark -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at openstack.org Fri Feb 21 16:18:14 2020 From: thierry at openstack.org (Thierry Carrez) Date: Fri, 21 Feb 2020 17:18:14 +0100 Subject: [Foundation Board] Looking for volunteers to lead Interoperability working group Message-ID: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> Hi, newly-elected and returning board members, During the last meeting, Alan called for new volunteers to join board committees like the Compensation committee or the Finance committee. While not strictly a committee, the Interoperability working group (formerly known as DefCore committee) is a OSF board working group that leads the definition of new versions of our Interoperability guidelines, which are used to grant the rights to use various trademarks such as "OpenStack-Powered platform". The group was previously led by Egle Sigler and Mark Voelker, who as of 2020 are no longer part of the board. Its main task is to get consensus on which APIs are necessary to be offered and which sections of code are necessary to be run to call your deployment "an OpenStack cloud". Technically, that translates into the definition of a set of Tempest tests matching the required API calls, so that products and deployments can assert the trademark through a suite of tools called RefStack. This work is critical in driving interoperability between OpenStack deployments, which is an essential benefit of using OpenStack software in hybrid usage scenarios. Representing all facets of our community, the Board is uniquely positioned to define what that consensus looks like and evolve it over time. Who is interested in participating in that workgroup ? I'm available to answer any question you may have about the process, and for questions I don't have the answer to, I copied Egle on this email so that she can bring additional context if needed. Thanks! -- Thierry Carrez (ttx) From Arkady.Kanevsky at dell.com Fri Feb 21 18:31:08 2020 From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com) Date: Fri, 21 Feb 2020 18:31:08 +0000 Subject: [Foundation Board] Looking for volunteers to lead Interoperability working group In-Reply-To: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> References: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> Message-ID: <4c06354b86ab4f91bd81be3f0fd5df2f@AUSX13MPS308.AMER.DELL.COM> Thierry, Is the ask for one of board members to take over overseer responsibility for interop group? Or just have more participation in interop group? Or something else? Thanks, Arkady -----Original Message----- From: Thierry Carrez Sent: Friday, February 21, 2020 10:18 AM To: Cc: Egle Sigler Subject: [Foundation Board] Looking for volunteers to lead Interoperability working group [EXTERNAL EMAIL] Hi, newly-elected and returning board members, During the last meeting, Alan called for new volunteers to join board committees like the Compensation committee or the Finance committee. While not strictly a committee, the Interoperability working group (formerly known as DefCore committee) is a OSF board working group that leads the definition of new versions of our Interoperability guidelines, which are used to grant the rights to use various trademarks such as "OpenStack-Powered platform". The group was previously led by Egle Sigler and Mark Voelker, who as of 2020 are no longer part of the board. Its main task is to get consensus on which APIs are necessary to be offered and which sections of code are necessary to be run to call your deployment "an OpenStack cloud". Technically, that translates into the definition of a set of Tempest tests matching the required API calls, so that products and deployments can assert the trademark through a suite of tools called RefStack. This work is critical in driving interoperability between OpenStack deployments, which is an essential benefit of using OpenStack software in hybrid usage scenarios. Representing all facets of our community, the Board is uniquely positioned to define what that consensus looks like and evolve it over time. Who is interested in participating in that workgroup ? I'm available to answer any question you may have about the process, and for questions I don't have the answer to, I copied Egle on this email so that she can bring additional context if needed. Thanks! -- Thierry Carrez (ttx) _______________________________________________ Foundation-board mailing list Foundation-board at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board From pramchan at yahoo.com Sat Feb 22 03:23:58 2020 From: pramchan at yahoo.com (prakash RAMCHANDRAN) Date: Sat, 22 Feb 2020 03:23:58 +0000 (UTC) Subject: [Foundation Board] Looking for volunteers to lead Intero In-Reply-To: <4c06354b86ab4f91bd81be3f0fd5df2f@AUSX13MPS308.AMER.DELL.COM> References: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> <4c06354b86ab4f91bd81be3f0fd5df2f@AUSX13MPS308.AMER.DELL.COM> Message-ID: <209268870.6582209.1582341838309@mail.yahoo.com> Sure,I had participated in this with Sean Rob and Rocky and aware of the flow, let us review first the 5H1W approach to define  Collect data points to prove the assumption below. Why: Interoperability has become need of the hour, under both market, secutity  & privacy and political impact of country first globally. Who: Service providers seek Interoperability to choose best of the breed clouds for next gen workloads , maintaining legacy and moving to ZTP, CI/CD, LCM to cut Capex, Opex and TTM through Clouded native Build and Deploy cycles. When and Where: Before SP move workloads  to BM  Containers, CNF from VM and VNFs and use both approaches for Multi and Hybrid Clouds. How soon? Depends between now and 5G scale deployments. All this will show up in their DC at Network Edge as opposed to Central Cloud. What: Get the CSP and SP or Gov NOCs an Interoperable BM platform with validated Designs for workload movements and hence Interoperable between current ang future Cloud innovations both Multi and Hybrid clouds. HowOpenStack and Open Infra can play it's role as below.1. Intra OpenStack api confornance status for T+U released. Which Vendors habe motivation to seek compliance for OpenSrack and hence updates needed to Tempest test suites for the Delta or feature gaps. 2. Cloud Interoperability goals to try evolve strategy for BM cloud as part of Open Infrastructure initiative. Will this intrest GSMA CNTT folks and Intel to promote this? Can we use Prowl , ltmg, Jenkins +x along with Zuul working with Metal and Airship , which are part of our eco system? Other wish list we can add but giving a push to what ttx strongly believes, we need to review and gather resources to address. With Arkady showing interest I believe Dell, Ericson, Mirantis, Redhat and AT&T should be sought to help themselves through this initiative. TTX Please find a bridge and let's get intrested members to the call next or weeks as ee plan March F2F board meeting. ThanksPrakash. Sent from Yahoo Mail on Android On Fri, Feb 21, 2020 at 10:31 AM, Arkady.Kanevsky at dell.com wrote: Thierry, Is the ask for one of board members to take over overseer responsibility for interop group? Or just have more participation in interop group? Or something else? Thanks, Arkady -----Original Message----- From: Thierry Carrez Sent: Friday, February 21, 2020 10:18 AM To: Cc: Egle Sigler Subject: [Foundation Board] Looking for volunteers to lead Interoperability working group [EXTERNAL EMAIL] Hi, newly-elected and returning board members, During the last meeting, Alan called for new volunteers to join board committees like the Compensation committee or the Finance committee. While not strictly a committee, the Interoperability working group (formerly known as DefCore committee) is a OSF board working group that leads the definition of new versions of our Interoperability guidelines, which are used to grant the rights to use various trademarks such as "OpenStack-Powered platform". The group was previously led by Egle Sigler and Mark Voelker, who as of 2020 are no longer part of the board. Its main task is to get consensus on which APIs are necessary to be offered and which sections of code are necessary to be run to call your deployment "an OpenStack cloud". Technically, that translates into the definition of a set of Tempest tests matching the required API calls, so that products and deployments can assert the trademark through a suite of tools called RefStack. This work is critical in driving interoperability between OpenStack deployments, which is an essential benefit of using OpenStack software in hybrid usage scenarios. Representing all facets of our community, the Board is uniquely positioned to define what that consensus looks like and evolve it over time. Who is interested in participating in that workgroup ? I'm available to answer any question you may have about the process, and for questions I don't have the answer to, I copied Egle on this email so that she can bring additional context if needed. Thanks! -- Thierry Carrez (ttx) _______________________________________________ Foundation-board mailing list Foundation-board at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board _______________________________________________ Foundation-board mailing list Foundation-board at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arkady.Kanevsky at dell.com Mon Feb 24 14:26:54 2020 From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com) Date: Mon, 24 Feb 2020 14:26:54 +0000 Subject: [Foundation Board] Looking for volunteers to lead Interoperability working group In-Reply-To: <01be7248-1770-b07e-e409-c9609168a801@openstack.org> References: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> <4c06354b86ab4f91bd81be3f0fd5df2f@AUSX13MPS308.AMER.DELL.COM> <01be7248-1770-b07e-e409-c9609168a801@openstack.org> Message-ID: <7af6d2da47ac4ce1ae9648eaafc4b0af@AUSX13MPS308.AMER.DELL.COM> Thanks Thierry. Either Prakash or me or both will follow with Egle. I would like to follow on the impact of interop. Maybe cover it in questionnaire. Thanks, Arkady -----Original Message----- From: Thierry Carrez Sent: Monday, February 24, 2020 7:29 AM To: Kanevsky, Arkady; foundation-board at lists.openstack.org Cc: egle.sigler at rackspace.com Subject: Re: [Foundation Board] Looking for volunteers to lead Interoperability working group [EXTERNAL EMAIL] Arkady.Kanevsky at dell.com wrote: > Is the ask for one of board members to take over overseer responsibility for interop group? > Or just have more participation in interop group? > Or something else? At this point the group is empty, so I'd say that in order to be successful we need new leaders to take over and drive future guidelines evolution. I'm sure former participants can answer questions and provide some context, but new blood is definitely needed. Regards, -- Thierry From kurt at garloff.de Fri Feb 21 19:15:19 2020 From: kurt at garloff.de (Kurt Garloff) Date: Fri, 21 Feb 2020 20:15:19 +0100 Subject: [Foundation Board] Looking for volunteers to lead Interoperability working group In-Reply-To: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> References: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> Message-ID: <4747BE8A-A78D-4E18-B799-7C17551698E3@garloff.de> Hi Thierry, Thanks for bringing this up! Egle and Mark have done very good work and I want to express my gratefulness to them! I have participated in that group before, though unfortunately have not been able to do so in 2019. I am willing and able to participate again, but I don't have the depth that Egle and Mark have. I'm certainly happy to help and be the liaison to the board. And I fully agree that this WG continues to be very important! @Egle: Please share your thoughts how this can work out! Thanks, -- Kurt On 21 February 2020 17:18:14 CET, Thierry Carrez wrote: >Hi, newly-elected and returning board members, > >During the last meeting, Alan called for new volunteers to join board >committees like the Compensation committee or the Finance committee. > >While not strictly a committee, the Interoperability working group >(formerly known as DefCore committee) is a OSF board working group that > >leads the definition of new versions of our Interoperability >guidelines, >which are used to grant the rights to use various trademarks such as >"OpenStack-Powered platform". > >The group was previously led by Egle Sigler and Mark Voelker, who as of > >2020 are no longer part of the board. Its main task is to get consensus > >on which APIs are necessary to be offered and which sections of code >are >necessary to be run to call your deployment "an OpenStack cloud". >Technically, that translates into the definition of a set of Tempest >tests matching the required API calls, so that products and deployments > >can assert the trademark through a suite of tools called RefStack. > >This work is critical in driving interoperability between OpenStack >deployments, which is an essential benefit of using OpenStack software >in hybrid usage scenarios. Representing all facets of our community, >the >Board is uniquely positioned to define what that consensus looks like >and evolve it over time. > >Who is interested in participating in that workgroup ? I'm available to > >answer any question you may have about the process, and for questions I > >don't have the answer to, I copied Egle on this email so that she can >bring additional context if needed. > >Thanks! > >-- >Thierry Carrez (ttx) > >_______________________________________________ >Foundation-board mailing list >Foundation-board at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board -- Kurt Garloff , Cologne, Germany (Sent from Mobile with K9.) -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at openstack.org Mon Feb 24 13:28:37 2020 From: thierry at openstack.org (Thierry Carrez) Date: Mon, 24 Feb 2020 14:28:37 +0100 Subject: [Foundation Board] Looking for volunteers to lead Interoperability working group In-Reply-To: <4c06354b86ab4f91bd81be3f0fd5df2f@AUSX13MPS308.AMER.DELL.COM> References: <4dbac683-e397-faf9-44a9-673e74830fe1@openstack.org> <4c06354b86ab4f91bd81be3f0fd5df2f@AUSX13MPS308.AMER.DELL.COM> Message-ID: <01be7248-1770-b07e-e409-c9609168a801@openstack.org> Arkady.Kanevsky at dell.com wrote: > Is the ask for one of board members to take over overseer responsibility for interop group? > Or just have more participation in interop group? > Or something else? At this point the group is empty, so I'd say that in order to be successful we need new leaders to take over and drive future guidelines evolution. I'm sure former participants can answer questions and provide some context, but new blood is definitely needed. Regards, -- Thierry From claire at openstack.org Fri Feb 28 20:46:37 2020 From: claire at openstack.org (Claire Massey) Date: Fri, 28 Feb 2020 14:46:37 -0600 Subject: [Foundation Board] OpenInfra Labs initiative Message-ID: <7D557D37-4B13-4A82-854F-F5F319228771@openstack.org> Hi everyone, I wanted to give you a quick update on an exciting new initiative OSF is supporting. OpenInfra Labs (OILabs) is the new effort we've been gradually working to establish in partnership with the Mass Open Cloud (MOC) community. MOC is a well established group that involves five of the top research universities in the world: Boston University, Harvard, MIT, Northeastern and University of Massachusetts. MOC has three interrelated goals: operating a production cloud, enabling more production clouds to be built and enabling industry innovation. OILabs is created with the further goal to expand the existing community and simplify and standardize how different institutions deploy and operate open source cloud and cloud native infrastructure software. Initially, the project will prioritize the needs of the MOC. Longer term the goal is to see more organizations globally (especially in the academic and research space) stand up multiple consistent clouds that can enable hybrid and federated use cases. The MOC group runs several large cloud environments that are used by thousands of users across the participating universities as well as through a Massachusetts startup initiative. They have created tools to do a lot of this and would like to open them up and collaborate more with other universities and public clouds. They are also big believers in OpenStack and want it to become easier to use in academic and research environments so that people don't just choose hyperscale public clouds or proprietary software options. OILabs aligns with OSF’s priorities in a few ways: It's a very direct attempt to improve usability and viability of the core OpenStack services. It also creates OpenStack marketing opportunities through new use cases. It's also a direct attempt to integrate OpenStack with K8s and other key open source infrastructure software, especially within the academic market. The MOC previously had involvement with a number of our member and sponsor companies, including Red Hat, Intel, NetApp, Dell, Cisco, Fujitsu and Mellanox, so it’s already strategically aligned across the OSF ecosystem. So what's next with OILabs? We’ve set up some basic collaboration channels and pushed a landing page: https://openinfralabs.org/ . Next week, March 2-3, the MOC community is hosting an Open Cloud Workshop at Boston University that covers several open efforts. OSF will be participating by attending the workshop and community leaders including Mohammed Naser, Julia Kreger and Jonathan Bryce are also leading a few sessions. The full schedule of keynotes, talks, deep dives and BoF sessions is available here . As we look into 2020, OSF will focus efforts on helping OILabs collaborate in the open, giving their efforts more visibility, and helping to raise funding for these efforts with an eye towards it becoming an OSF Pilot Project. If you want to get involved in any of these areas, please let us know. Thanks, Claire -------------- next part -------------- An HTML attachment was scrubbed... URL: