Open Stack

Hi everyone,

I had taken an action item at our last meeting to discuss the OpenStack
compatible mark[1] and other options that we might have available to
publicize/promote ISVs that validate their ability to either run on top of
OpenStack or support integration with OpenStack (monitoring, etc.)

Lauren, Heidi, and I had a conference call last week to discuss the
objective of this group and whether we could leverage OpenStack Foundation
assets (marks, web site, etc.) to showcase participants.  First of all, I
want to let everyone know that Lauren and Heidi both were very supportive
of the team and wanted to let everyone know that they sincerely appreciate
the work this team is doing!

The OpenStack Foundation will only grant marks for components/applications
that actually interface with the OpenStack API and, therefore, only the
packages that we have been calling "Support ISVs" would be eligible.  The
good news is that monitoring solutions are already covered by the
"OpenStack Compatible" mark (Zenoss, for example, already has rights to use
OpenStack Compatible).  We can discuss this further in our next call this
Friday, including what would be the next steps, to get the "Support ISVs"
listed in the etherpad started on this journey.

The category that we have been calling "Compatible ISVs" might require a
new name inside our team.  This is due to the fact that they would not be
eligible for the "OpenStack Compatible" program since they do not
necessarily have to interface with OpenStack API to successfully run on top
of OpenStack clouds.  If we don't change the name then it might become
confusing since there is already an "OpenStack compatible" program which
means something else.

The foundation is definitely interested in pursuing some method to promote
the ISV solutions that go through the process of validating that they can
run on top of OpenStack clouds.  We, ISV interop, have discussed certain
possible outputs (deployment doc covering how to install on top of
OpenStack, white paper, etc.) that these organizations might generate as a
part of the validation process... The foundation might be able to create a
section for an "enterprise application directory" which could provide some
details on the process that the ISV solutions went through to be a part of
this page along with links to the ISV website and the generated content.

Carol and I will be in Austin, TX the week of the 27th and it was suggested
that we might schedule an in-person meeting with Lauren, Heidi, and
additional staff to kick-off the "enterprise application directory"
initiative.   A few questions that I have are:

   - Do you think Carol and I being there is sufficient representation from
   the team or should we try to open a conference bridge as well so that all
   the key members can be present (I will have to validate if this is an
   option of course)?  Dave, any chance you could fly in for a day? :)
   - To make sufficient progress at this meeting, we would need to have a
   plan and timeline established for the ISV interop that we can share in this
   meeting.  Is having a preliminary plan, timeline, high-level site
   requirements, and a summary of the test plan for verifying ISV
   interoperability ready before July 27th an achievable goal for the team?

Happy to continue this topic onour call but I wanted to send out the email
to start the discussion.  Take care and talk to you soon!

[1] July 10th Etherpad:
https://etherpad.openstack.org/p/Enterprise-Business-ISV
-- 
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/enterprise-wg/attachments/20150709/4811676f/attachment.html>