November 2013 - Foundation - lists.openinfra.dev

[OpenStack Foundation] openstack.org is down - why is it still hosted outside of openstack-infra?
by Sean Dague 13 Nov '13

13 Nov '13

So this morning openstack.org is down, returning 500 errors. This remains one of the few pieces of openstack infrastructure that is not hosted and run by the openstack-infra team. It means that fixing openstack.org is not possible by the global development team on openstack-infra. I really think that needs to stop. We have a world class infrastructure team in the community that hosts nearly everything else in *.openstack.org. It does so across multiple openstack clouds. It does so using the best practices of devops, with nearly everything under puppet control. And it does so with a global team which means pretty extensive TZ coverage (not perfect yet, but growing). Can someone explain why openstack.org is run separately from the openstack-infra effort, and what the plan is going forward? -Sean -- Sean Dague http://dague.net

1 0

Re: [OpenStack Foundation] OpenStack core and interoperability -> Meeting 11/20 in SFO
by Rob_Hirschfeld＠Dell.com 13 Nov '13

13 Nov '13

Thanks Josh. I thought to add the specific that we know so far. If any can join, we're talking about Wed 11/20 at the Piston SFO office. The meeting will be *all day* but you can attend parts IMHO, this is planning for the kick-off, not the actual kick-off. However, we need to decide quickly if a by-laws change is needed. That's the primary objective for this meeting. Here's a tentative agenda (to be ordered based on availability of Mark Radcliff) Objective: Determine if a by-laws change is needed & plan for kick-off. Some topics to review: * Process & Logistics * Name of committee (Alan was suggesting "elephant" as a follow on for "spider") * Should be change the bylaws to be more process (less project) oriented? If so, how/when? * Review the principles, make sure the text makes sense * Identify "elephants" in the process that we need to address/avoid/postpone * Timeline for implementation * Identify technical gaps (beyond RefStack) * RefStack review & planning * Discuss community involvement process From: Joshua McKenty [mailto:joshua@pistoncloud.com] Sent: Monday, November 11, 2013 12:59 PM To: Jeremy Stanley; Hirschfeld, Rob Cc: foundation(a)lists.openstack.org Subject: Re: [OpenStack Foundation] OpenStack core and interoperability Rob Hirschfeld and I are chairing the newly approved Interoperability Committee, and we have a kickoff meeting next week. I'm reasonably confident that we'll have a preliminary model for FITS certification by the time of the Icehouse Summit. We're going to repurpose the existing FITS mailing list for this, so if you want to follow along, you should sign up there. -- Joshua McKenty Chief Technology Officer Piston Cloud Computing, Inc. +1 (650) 242-5683 +1 (650) 283-6846 http://www.pistoncloud.com "Oh, Westley, we'll never survive!" "Nonsense. You're only saying that because no one ever has." On Nov 10, 2013, at 3:03 PM, Jeremy Stanley <fungi(a)yuggoth.org<mailto:fungi@yuggoth.org>> wrote: On 2013-10-31 18:06:03 -0500 (-0500), Mark Collier wrote: [...] As of January 1st, 2012, your product must pass any Faithful Implementation Test Suite (FITS) defined by the Technical Committee that will be made available on http://www.openstack.org /FITS , to verify that you are implementing a sufficiently current and complete version of the software (and exposing associated APIs) to ensure compatibility and interoperability. [...] "OpenStack FITS. Coming soon. The OpenStack Faithful Implementation Test Suite will be available in early 2012." I guess we're a little behind there. Is there any benefit to revising that ETA or do we wait until there's a more solid timeline established? -- Jeremy Stanley _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org<mailto:Foundation@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

3 3

Re: [OpenStack Foundation] OpenStack core and interoperability
by Monty Taylor 11 Nov '13

11 Nov '13

This is how it works now. You're required to run the code. Thing is, this is about legal contracts. So enforcement is hazy. Essentially, if hp signs a trademark usage thing that says we have to run it, our own lawyers won't let us do different. I think the first step is to say "OpenStack requires you run the code" ... Then as violations are brought to our attention, we look in to it. On a parallel tack, compatible is testable. I think it's also useful. An OpenStack could not be compatible based on config. You could be compatible with being an OpenStack. Mark McLoughlin <markmc(a)redhat.com> wrote: >On Thu, 2013-10-31 at 13:55 -0500, Mark Collier wrote: >> The OpenStack Mission is to: >> >> To produce the ubiquitous OpenSource Cloud Computing platform that >> will meet the needs of public and private clouds regardless of size, >> by being simple to implement and massively scalable. >> >> IMHO the operative (action) word is "produce." This is why I agree >> with Monty that it is critical that if we start somewhere, it should >> be with a program based on people running the code, who have a vested >> interest in the code's continual evolution and survival. If we take >> our eye of of that it could invite fragmentation and dilution of any >> meaning for "what is openstack". >> >> >> That said, it seems to me that technically speaking, we might only >> need 1 set of tests that could feed the two distinct programs being >> described ("openstack cloud" and "compatible"). So there might be to >> two (marketing/business/logo) *programs* with unique requirements >> other than testing, but with one test suite. >> >> >> Therefore, IMHO, the best place to start is with the development of >> the test itself while continuing to discuss the ways in which the >> results might be applied to two distinct (logo) *prorgrams*. Now I >> understand that you cant develop a test in the absence of requirements >> such as which projects to include, but we could probably come up with >> a sensible starting point and add additional coverage over time >> (increasing test coverage not necessarily implying that each must pass >> to qualify for a specific program). > >Ok, I'd be totally cool with all that ... if I had any idea how we were >going to go about creating "a program based on people running the code". >I see a near bottomless pit of issues we'd need to work through before >putting that into place and I don't want to block making >interoperability progress on these issues. > >Am I missing something? What's (roughly) your take on how such a program >would work? > >To be clear, I mean - assuming we know what code should be required to >run - how do we express those requirements precisely and certify that >providers are meeting them? > >Thanks, >Mark. > >

6 6

[OpenStack Foundation] November 4 Board Meeting
by Jonathan Bryce 07 Nov '13

07 Nov '13

The Foundation Board of Directors met in Hong Kong on Monday November 4th. Almost all of the directors were present in person with a few joining by phone. The agenda was posted on the wiki prior to the meeting: https://wiki.openstack.org/wiki/Governance/Foundation/4Nov2013BoardMeeting The meeting lasted the full day, and the morning session was used to review new Gold Member applications. After hearing from representatives from each applicant company, the Board discussed the applications at length and voted to approve Aptira, Hitachi and Huawei and new Gold Members of the Foundation. Over lunch, I provided an update on the 3rd quarter activities of the Foundation and the high level priorities for 2014. In 2014, we want to build on the momentum and growth we have seen by creating stronger connections between the various members of the community whether they are developing the software, using OpenStack as cloud operator or cloud end-user, or helping to organize community activities. There are many opportunities to do through the events we support, initiatives like the training marketplace and by helping new members easily find the resources they need to contribute to or deploy the software or engage in whatever way is appropriate. One goal I’m excited about from a Foundation perspective is around working to publish and share the information we have gather from users and the community at large in more ways, including with consumable APIs where possible. We will be talking more about these activities as we head towards 2014 and get some of these programs kicked off. At the end of the session, the Board voted to approve the proposed budget for 2014. In the remainder of the afternoon, the Board discussed the work of several working groups including the core definition group. The Board approved the guiding principles that have been developed through the community meetings on the topic this year and created a committee to move to the next step of establishing the process for testing and certification around those core concepts. The Board also reviewed and approved the transparency policy (https://docs.google.com/a/openstack.org/document/d/1sGBtza-mjRXcDzFBSS9aUrY…) that has been developed this year. There were also updates from other committees, but I had to step out of the end of the meeting to take care of some Summit business. Other attendees who were present may be able to provide information of the final committee updates. One thing to note is that the Election Committee will be holding a town hall over lunch at the Summit in Hong Kong today from 12:50pm - 1:40pm in the Exhibit Hall Demo Theater. It has been a busy and exciting week in Hong Kong and it’s been great to see many of you here in person. Jonathan

1 0

[OpenStack Foundation] Training session reminder: OpenStack Board Meeting November 4, 2013 Full Day Meeting
by messenger＠webex.com 03 Nov '13

03 Nov '13

Hello Foundation Mailing List, Alan Clark invites you to participate as an attendee in the OpenStack Board meeting: Topic: OpenStack Board Meeting November 4, 2013 Full Day Meeting Host: Alan Clark Date: Sunday, November 3, 2013 Time: 5:00 pm, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 498 221 402 Session password: This session does not require a password. ------------------------------------------------------- To join the session ------------------------------------------------------- 1. Go to https://openstack.webex.com/openstack/k2/j.php?ED=23813653&UID=74180448&HMA… 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?ED=23813653&UID=74180448&HMA… ------------------------------------------------------- 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=23… Show toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 498 221 402 ------------------------------------------------------- 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?AT=down&ED=23813653&EF=MA&UU… http://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] Invitation to OpenStack Board Meeting November 4, 2013 Full Day Meeting
by messenger＠webex.com 02 Nov '13

02 Nov '13

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 November 4, 2013 Full Day Meeting Host: Alan Clark Date: Sunday, November 3, 2013 Time: 5:00 pm, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 498 221 402 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?ED=23813653&UID=74180448&HMA… 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?AT=down&ED=23813653&EF=MA&UU… To view in other time zones or languages, please click the link https://openstack.webex.com/openstack/k2/j.php?ED=23813653&UID=74180448&ORT… ------------------------------------------------------- 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=23… Show toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 498 221 402 ------------------------------------------------------- For assistance ------------------------------------------------------- You can contact Alan Clark at: aclark(a)suse.com http://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