In this marketing meeting, OpenStack Foundation COO Mark Collier discusses plans to consolidate the number of commercial logos, and how companies offering OpenStack products can participate.

2. Current Commercial Logo Programs

3. Large number of logos is creating confusion
‣ Members companies are confused about which to use
‣ Some use them incorrectly
‣ Users aren’t always clear about the meaning
‣ Goal: simplify by consolidating # of logos

4. Proposed Logo Program Consolidation
Program Name Current Proposed
Built for OpenStack
OpenStack Training
Powered by OpenStack
Storage Powered by
OpenStack
OpenStack Distribution
OpenStack Cloud

5. Summary – two logos for most commercial use
Powered by OpenStack software:
‣ Public Clouds
‣ Distributions
‣ Appliances
Work with or as part of OpenStack
powered clouds:
‣ Compute, Storage, and Networking Hardware
that’s designed to work with OpenStack
‣ Cloud apps that integrate with the APIs
‣ Other potential future uses TBD
And Training for… Training

6. For Extra Credit
‣Using the word “OpenStack” in product names
‣Technical Requirements for “OpenStack Powered”

7. Using the word “OpenStack” in product names
‣ In some cases “OpenStack” can be in a product name
‣ All names need to be approved by the Foundation and
detailed in a signed TM license agreement
‣ The uses we generally approve vary by product type
but are typically:
Product Type
Distribution ACME OpenStack
Public Cloud ACME OpenStack Cloud
Appliance ACME OpenStack-powered widget
Storage specific product ACME widget powered by OpenStack
Storage
Services offering (generally) ACME service for OpenStack
Training ACME Training for OpenStack

8. Technical Requirements for OpenStack Powered:
No change from previous req. for cloud/distro/powered:
‣Use recent version1 of OpenStack code & expose APIs
‣Nova & Swift
‣Must pass FITS tests when available
‣Future updates likely pending #Defcore/TC/Board
decisions, not a gate for this logo consolidation project
1“include the entirety of the OpenStack [Nova & Swift] code from either of the latest two releases and associated milestones”

9. Target Rollout
‣ April 2014 for new licensees
‣ Existing Distro/Cloud licensees can
sign & start updating collateral
starting in April, with goal of having
all transitioned by late 2014
‣ April/May 2014 for new licensees
‣ Existing “Built for” licensees can
sign & start updating collateral
starting in April, with goal of
having all transitioned by late
2014