Jump to: navigation, search

Difference between revisions of "PublicCloudWorkingGroup"

(OpenStack Public Cloud WG EU Meetup)
Line 16: Line 16:
 
Agreed goals for Sydney summit are :
 
Agreed goals for Sydney summit are :
  
==== OpenStack Public Cloud WG EU Meetup ====
+
==== OpenStack Public Cloud WG EU Meetup Series====
 
* OpenStack UK Day London (26th September)
 
* OpenStack UK Day London (26th September)
* OpenStack Nordic Days Copenhagen (18-19th October)
+
* [https://www.meetup.com/OpenStack-Public-Cloud-WG-Meetup-Copenhagen/ OpenStack Nordic Days Copenhagen] (18-19th October)
  
 
==== Keep "Missing features list" up to date with references to specs, status, commits etc ====
 
==== Keep "Missing features list" up to date with references to specs, status, commits etc ====

Revision as of 01:41, 15 July 2017

Status: Forming

Chairs:

 * Tobias Rydberg <tobias@citynetwork.se>
 * Howard Huang <huangzhipeng@huawei.com>
 * Sean Handley <sean.handley@datacentred.co.uk>

The aim of this group is to represent the interests of the OpenStack public cloud provider community, and to further adoption of OpenStack public cloud usage.

Purpose

  • Internal: we represent the voice of OS-based public cloud providers towards the rest of OS community
  • External: we represent the OS-based cloud providers towards the market (what are our value strengths), the press (what we think), the customers (what we sell), the other non-OS providers (regulation, fair competition etc) especially valid for EU based ones

Scope

Agreed goals for Sydney summit are :

OpenStack Public Cloud WG EU Meetup Series

Keep "Missing features list" up to date with references to specs, status, commits etc

  • Convert items in list to specs when needed
  • Keep the spreadsheet for new items and as reference
  • Set the structure for how to work with the list and the specs

Related docs: https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-XSycSkOjqCyMTIedkA

OpenStack Public Cloud Passport

  • Prepaid Coupons valid for any public cloud participating
  • Design the technical solution
  • Passport in badges at Summit

Related docs: https://docs.google.com/spreadsheets/d/10ID98gJTMd91hmQuKJDfdm6YtC1AjAbcf4QsgnqsPFI

Definition

The NIST definition of a Public Cloud as a deployment model is:

"The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organisation, or some combination of them. It exists on the premises of the cloud provider."

This is further expanded within the context of this Working Group by the following:

  • Multi-tenant;
  • Offers publicly accessible native OpenStack APIs.

Members

No formal membership is required. Please introduce yourself and/or fellow colleagues to this working group using one of the mailing lists below, or by attending one of the IRC meetings.

This group is open to all members of the OpenStack public cloud provider community and supporting vendors.

Communication

The default communication of our members is via the following open community mailing lists:

  • user-committee@lists.openstack.org for coordination of working group activities. Please prefix email subject lines with the tag "[publiccloud-wg]".
  • openstack-operators@lists.openstack.org for operational discussion of public cloud related OpenStack deployment issues. Please prefix email subject lines with the tag "[publiccloud]".


Please use the hashtag "publiccloud-wg" for tagging any etherpad URLs, code, blog posts and/or other social publishing platforms.

Meetings

IRC Meetings

Initial meeting schedule was defined via a Doodle poll carried out after a discussion thread on the openstack-operators and user-committee lists. This is currently :

  • Bi-weekly on odd weeks on Wednesdays at 1400 UTC in IRC channel #openstack-meeting-3

Meeting agenda can be found at https://etherpad.openstack.org/p/publiccloud-wg

Full details (including a calendar file) are available at http://eavesdrop.openstack.org/meetings/publiccloud_wg If you need help getting started with IRC see http://docs.openstack.org/upstream-training/irc.html.

Structure

A single group operating over multiple cycles.