This document discusses achieving visibility and insight across OpenStack projects through an integration pilot powered by Wikidsmart. It describes current challenges with a lack of integration between project content and silos of information. The Wikidsmart demo shows faceted search and tracing a patch across tools. Potential next steps include offering a public Wikidsmart portal for searching and dashboards, and a private portal for corporate members to bridge internal and community content.

1. Achieving Visibility and Insight
Across OpenStack Projects
Stefano Maffulli, OpenStack Foundation, Community Manager
Sanjiva Nath, zAgile, CEO and Founder

2. Agenda
‣ OpenStack Integration Pilot Overview (10 minutes)
‣ Demo of Pilot, Powered by Wikidsmart (10 minutes)
‣ More About zAgile and Wikidsmart (10 minutes)
‣ Potential Next Steps (5 minutes)
‣ Q&A (10 minutes)

3. Silos of Content and Concepts
Tools Collaboration
Requirements Version Code Continuous
Wiki & Issues Control Review Integration Email
Lists
GUI • General
• Developer
• Documentation
• Community
• Operators
Data Social
Store
(File Launc
Launc GitHub
GitHub Gerrit
Gerrit Jenkins
Jenkins
Structure / hPad
hPad
Repository)
Concepts, • Reviewer • Component
• Project • Users
• Users
Features, • Pages • Users • Code
• Comment • Build IRC
• Commit • Version
Logic, etc. • Issue/Task • Version
• Files • License

4. Current Integration Challenges
‣ General lack of integration amongst Projects’ content
‣ Interoperability, Traceability, Faceted search
‣ Project leaders: dashboard of status for milestones, activity of
contributors, translations, documentation, bugs, etc.
‣ OpenStack community management:
‣ Lack of integration/traceability/reconciliation/visibility
‣ Community member collaboration with OpenStack:
‣ No consistency/interoperability of internal content with that of
the OpenStack community
‣ Community members want to harvest community-generated
knowledgebase for their own customers more efficiently,
integrate this info with internal knowledgebase

5. Pilot Results: Architecture

6. Sample Questions to Answer
‣ Pilot
‣ Who are the most and least active users?
‣ What is the trend of bugs fixed over time?
‣ Which company has been active with specific project parts?
‣ Beyond the Pilot
‣ Show public information combined in a cohesive way with my
private information and enable interoperability of content
amongst tools and applications
‣ How much did this company pay, and what is that with
respect to the cost of the feature? their contribution?
their participation?
‣ Show accountability of the community in terms
of cost and value

7. Overlapping Community and Corporate Content
RackSpace
Content
HP
OpenStack Content
Content
Cisco Nebula
Content Content

8. Wikidsmart Demo
• Faceted Search:
– Finding precise information, quickly and easily
• Follow the life of a patch:
– Git -> Bug tracker -> Person -> Company
– What else is the company/person working on?
– What were they doing in the past?
• Bug report:
– What person in which company filed it?
– See the discussions, the patch, who authored it?
8

9. How Wikidsmart Works
9

10. OpenStack Pilot Architecture Review

11. A Wikidsmart, Coherent Information System
Tools Collaboration
Email
GUI IRC
Lists
Wikidsmart Context Server’s Knowledge Model
Domain
Concepts,
Features,
Logic, etc. Other
(CRM Help
Software Engineering: Concepts, Processes, People Social Desk, etc.)
Data
Store Social
11

12. More about zAgile
and Wikidsmart
12

13. zAgile Corporate Overview
• Mission: Integrate Teams, Tools, Processes, and Knowledge
– First targeting Application Lifecycle Management / Software Engineering
– Platform extensible to any domain and applications
• Founded: 2006 in San Francisco, launched v1.0 in 2009
Technology Services
• Partners
• Press Coverage
• Selected Customers
2008-2012 Proprietary and Confidential, zAgile, Inc. 13

14. Wikidsmart Platform Benefits
• Instant Integration
• No development required, integrations are pre-built
• Each connector instantly integrates all tools and applications
• Smart Solutions
• Cohesion of content flow between tools and apps
• New, template-based, composite applications
• Insightful Information
• Easily find content with faceted, precision search
• Lineage/Traceability: Traverse tangential artifacts/concepts
• Dashboards & reports bridge content between tools and teams
• Future-Proof Platform
• Open Source, Open Standards, Any Tools and Applications
2008-2012 Proprietary and Confidential, zAgile, Inc. 14

15. Potential Next Steps

16. Recap: Sample Questions to Answer
‣ Pilot
‣ Who are the most and least active users?
‣ What is the trend of bugs fixed over time?
‣ Which company has been active with specific project parts?
‣ Beyond the Pilot
‣ Show public information combined in a cohesive way with my
private information and enable interoperability of content
amongst tools and applications
‣ How much did this company pay, and what is that with
respect to the cost of the feature? their contribution?
their participation?
‣ Show accountability of the community in terms
of cost and value

17. OpenStack Can Offer Value-Added Integration
‣ Public Portal (Everyone)
‣ Wikidsmart integration, search, and dashboards offered
either as Free or Subscription
‣ Private Portal (Corporate Members)
‣ Wikidsmart integration, search, and dashboards offered
as a Subscription
‣ Bridges internal corporate content with OpenStack
community sites

18. OpenStack Can Offer Value-Added Integration
‣ See OpenStack Blog for links
‣ Recorded webinar
‣ Social Media and Community: LinkedIn, Twitter, Mailing
Lists, etc.
‣ Survey (3 checkbox questions, 1 comment box)
http://svy.mk/PCzRVW
‣ Now: Q&A
‣ Stefano Maffulli: stefano@openstack.org
‣ Sanjiva Nath: snath@zagile.com