Lars Kurth Community Manager, Xen Project Chairman, Xen Project Advisory Board lars_kurth
Diamond Sponsor Silver Sponsor
Xen & KVM Hackathon Tue 14:00 – 18:00 Virginia Room, 4th floor, Union Street Tower Joint Xen & KVM Social Event Tue 18:30 – 21:00 Shuttle Bus Stop: Union St side @ Sheraton Garage Billiards 1130 Broadway Seattle, WA 98122 (15 min walk, maps are available at registration)
Discussion Groups Lead to take notes (or nominate someone to do so) and post to xen-devel@ Free slots: Come to me or use stickers
Lunch is not provided Lots of venues nearby Maps are available at the event registration desk Developer Meeting Wed 10:00 – 13:30 Lunch provided Seneca, 4th floor, Union Street Tower Sign up via wiki.xenproject.org/wiki/Developer_Meeting/Aug2015 Or come and see me
Subprojects (retired, new, established) Project Initiatives Statistics
Embedded & Auto Windows PV Libvirt, CentOS , … Mirage OS XCP XenServer.org XAPI toolstack (used in XenServer) Xen on ARM PV Xen on ARM non-PV Hypervisor team / subproject : hypervisor and tools PVOPS (Xen enabled Linux) Linux Kernel Dev. BSD’s, Grub, QEMU, FreeRTOS , … AGL, Android, … 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 Hypervisor Developer list traffic : Q3 2003 - now
Embedded & Auto Windows PV In incubation Mirage OS fulfills criteria for graduation (no formal review has been conducted) Mirage OS XAPI toolstack (used in XenServer) Xen on ARM PV Xen on ARM non-PV Hypervisor team / subproject : hypervisor and tools PVOPS (Xen enabled Linux) Linux Kernel Dev. PVOPS & Xen on ARM are complete (achieved their goals) 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 Hypervisor Developer list traffic : Q3 2003 - now
1 Rack at EarthLink in Marlborough, MA More than 4 times test capacity Testing against Linux, BSDs & up/downstreams 24 test machines, planning to expand with another rack Automated performance testing Early stages We do have a lot more test contributions 1200 900 600 Xen Project Rack 300 0 2003 - 2012 2013 2014 2015
(Goal: group A alongside KVM)
the people/companies who drove this Xen Project Test Lab Lead: Ian Jackson Top Test Contributors: Ian Campbell, Wei Liu, Dario Faggioli, Roger Pau Monne, Longtao Pang, Anthony Perard Xen Project – OpenStack CI Loop Lead: Bob Ball Team: Anthony Perard, Antony Messerli, Jim Fehlig, Stefano Stabellini, Konrad Wilk Special Thanks: Rackspace for donating significant hosting capacity to get this project started
Commits Contributors 14000 250 Developers 12000 Employers 200 10000 150 8000 6000 100 4000 50 2000 0 0 2010 2011 2012 2013 2014 2015 2010 2011 2012 2013 2014 2015* *) Up to Aug 11th
2% 24% Hypervisor XAPI Mirage OS 51% Win PV Drivers 23%
Contribution Statistics (Up to Aug 11 th , 2015) Diversity Project Operations
3000 Fairly stable over the last 2500 few years. 2000 1500 1000 Projection Commits 500 0 2011 2012 2013 2014 2015
(contributions > 1%) Citrix Suse 1% 11% Linaro Oracle Intel Verizon Fujitsu Cavium Analog Devices AMD Zentific NSA Xilinx Novetta 88% BitDefender Other
(contributions > 1%, 2015 to Aug 11th) 1% 2% Citrix 4% Suse 12% 5% 1% 1% 1% Linaro Oracle 1% 4% Intel 2% Verizon 3% 4% Fujitsu 4% 49% 2014 2015 Cavium Analog Devices 13% 8% AMD Zentific 64% NSA 18% Xilinx Novetta BitDefender Other
4.0 4.1 4.2 4.3 4.4 4.5 4.6 40 35 Xen 4.x Number of New Major Features 30 25 20 15 10 5 0 2010 2011 2012 2013 2014 2015 2016
Releases Process From Soft to Hard Freeze – created some stress and pain Security Process Allow Service Providers to Upgrade During embargo Pre-disclosure list application Mechanism for pre-disclosure members to collaborate Contributor Training New influx of developers from China (access to Xen Project resources) Gave training in Shanghai, Nanjing and Hangzhou Focus on Designs for complex features Worked generally very well Some issues around sign-off by all stake-holders and ensuring designs are up-to-date
Formalizing Feature Maturity Lifecycle Proposal at lists.xenproject.org/archives/html/xen-devel/2015-06/msg01992.html Important, because “supported features” have to be handled by security@
Started seeing issues Last Year How are we doing Today? What Next? (Stats up to Aug 11 th , 2015)
50.00% July 2013 - Jan 2014 45.00% Feb 2014 - Aug 2014 40.00% Jan 2015 - Jul 2015 35.00% 30.00% 25.00% 20.00% 15.00% 10.00% In 2015, committed 1-4 year 5.00% old patches 0.00% Up to 1 week 1 to 2 weeks 2 to 3 weeks 3 to 6 weeks 6 to 13 weeks 13 to 52 weeks More than 1 year
60 50 40 <1% of reviews 30 1-5% of reviews >5% of reviews 20 10 0 2012 2013 2014 2015
35000 While the This reflects number of reviewers a huge growth 30000 has remained fixed jump in 1 year 25000 On average 20000 Aug 11th 2.1 replies per patch per patch revision 15000 Replies to Patches est. 10000 Patches Posted est. 5000 Replies to Patches Patches Posted 0 2004 - 2010 2011 2012 2013 2014 2015
5 Patches posted & re-posted (without review comments) 4 divided by patches gone into xen.git 3 Qemu 2 Xen 1 0 2012 2013 2014 2015
Increasing number of contributions Not enough review capacity to support growth; we know that review capacity has remained stable Increasing back-log (aka ongoing reviews on xendevel@) Increasing number of review cycles per patch/patch set Note: we know that the average number of review comments per patch version is stable More disagreements amongst maintainers, reviewers & contributors Lower quality contributions, requiring more review cycles More complex contributions, requiring more review cycles Increasing standards required to get code up-streamed (aka quality) Should be able to see patterns in review data A combination of all/some of the above
We have an issue, but we do not understand exactly where The 4 weeks before the 4.6 code freeze was the most stressful freeze in years The Advisory Board is funding development of analysis tools for our review process Insufficient research on what is normal/optimal If you are planning larger contributions You may want to help out with code reviews elsewhere If you are planning to consistently contribute over several years You may want to work towards ”building” Xen maintainers BUT: this is no short term fix Buying time We may be able to buy us time through process changes Discussion: search for “ [xen 4.6 retrospective] ” on xen-devel@ BoF: Xen 4.6 Retrospective Surgery & Developer Meeting
Events, Social Media, Press Coverage Security Vulnerability Coverage
Average monthly web visits grew by 37% Social Media following grew by 92%
1400 1200 1000 800 600 400 200 0 Q1 '13 Q2' 13 Q3' 13 Q4' 13 Q1 '14 Q2 '14 Q3 '14 Q4' 14 Q1' 15 Q2' 15
Security stories are “hot” Xen is widely used, thus security stories “sell” It’s too easy for reporters to write a story Reporters just have to check our page, and know when the next story comes
Pro-active coverage of Xen stories (besides releases)
We discuss PR on publicity@lists.xenproject.org (for our blog and elsewhere) Sign up via lists.xenproject.org Open to all community members Avoid accidental creation of a damaging news story
New Members Please welcome Alibaba / Aliyun Changes in Focus From Operational/Reactive to Strategic Community Support
Images used in this presentation are from – Lars Kurth – Xen Project and other Screen Shots – 123RF.com & Shutterstock.com – Peter Dedina @ flickr (page 17) – Wajahat Mahmood @ flickr (page 33)
Recommend
More recommend