OpenStack is a project that in a fairly short amount of time has attracted in its ecosystem most of IT giants, becoming one of the largest collaborative software development efforts ever seen. We'll explore how collaboration works in OpenStack and how companies contribute to the project, what drives their motivations. There will also be time to see examples of how development teams are setup internally at some of these companies in order to maximize effective contributions.
How to Maximize Effectiveness of Developers Contributing to Free SoftwareStefano Maffulli
The document discusses how corporations can maximize the effectiveness of their developers contributing to open source software. It recommends that corporations tweak their new product development and customer service processes to align with open source release cycles. Corporations also need to think outside their boundaries and allow developers more freedom to interact and contribute upstream to open source communities. Long term engagement and collaboration with open source communities can help corporations gain benefits like fixes to issues and code improvements.
Lessons learned during +25 years of Open Source and how those can be adapted to define the Open Cloud and at what we can do to see this idea materialise.
De-Risk Data Center Projects With Cisco ServicesCisco Canada
This presentation will discuss Cisco Advanced Services, why to use Cisco Advanced Services and where Cisco Advanced Services can add value to your business.
Building The Next Generation Workplace Cisco Canada
Alan McGinty, Cisco Workplace Resources and Mark Miller, Cisco Global Collaboration Sales presents the next generation workplace at Cisco Connect Toronto 2015.
The Developer is the New CIO: How Vendors Adapt to the Changing LandscapeLauren Cooney
This document summarizes a presentation given by Lauren Cooney of Cisco Systems about how the development landscape is changing and how companies need to adapt. Some of the key points made include: the role of developers is increasing as they have more buying power; everything is becoming programmable; there is a focus on user experience and community; and Cisco needs to change their thinking to focus more on cross-platform development, consistent experiences, and meeting developer needs. The presentation argues that companies must focus on empowering developers internally and externally to be successful in this new landscape.
How to Maximize Effectiveness of Developers Contributing to Free SoftwareStefano Maffulli
The document discusses how corporations can maximize the effectiveness of their developers contributing to open source software. It recommends that corporations tweak their new product development and customer service processes to align with open source release cycles. Corporations also need to think outside their boundaries and allow developers more freedom to interact and contribute upstream to open source communities. Long term engagement and collaboration with open source communities can help corporations gain benefits like fixes to issues and code improvements.
Lessons learned during +25 years of Open Source and how those can be adapted to define the Open Cloud and at what we can do to see this idea materialise.
De-Risk Data Center Projects With Cisco ServicesCisco Canada
This presentation will discuss Cisco Advanced Services, why to use Cisco Advanced Services and where Cisco Advanced Services can add value to your business.
Building The Next Generation Workplace Cisco Canada
Alan McGinty, Cisco Workplace Resources and Mark Miller, Cisco Global Collaboration Sales presents the next generation workplace at Cisco Connect Toronto 2015.
The Developer is the New CIO: How Vendors Adapt to the Changing LandscapeLauren Cooney
This document summarizes a presentation given by Lauren Cooney of Cisco Systems about how the development landscape is changing and how companies need to adapt. Some of the key points made include: the role of developers is increasing as they have more buying power; everything is becoming programmable; there is a focus on user experience and community; and Cisco needs to change their thinking to focus more on cross-platform development, consistent experiences, and meeting developer needs. The presentation argues that companies must focus on empowering developers internally and externally to be successful in this new landscape.
Cw13 the rising stack-how & why open stack is changing it by mark collier-ope...TheInevitableCloud
OpenStack is an open source cloud computing platform that manages large pools of compute, storage, and networking resources. It is developed through an open development process with over 800 developers from 50 companies contributing code. The OpenStack community has grown rapidly, with over 8,000 members from around the world. Many large companies are using OpenStack to power their cloud computing needs, attracted by its open governance model and rapid pace of innovation.
Evolving to Cloud-Native - Nate Schutta (1/2)VMware Tanzu
The document discusses evolving applications to be cloud native by following cloud computing best practices and design principles like microservices, containers, serverless computing, and continuous delivery. It outlines the 12 factors of cloud native applications which emphasize independence, isolation, and automation. While legacy applications may not meet all the principles, the goal is to design new applications and refactor existing ones opportunistically to take advantage of scalability, availability, and agility benefits of cloud computing.
Creating a Collaborative Workplace Culture Webinar SeriesCisco Canada
To increase innovation and productivity, organizations recognize that they have to get better at creating more “collaborative cultures” to leverage the collective knowledge, expertise and experience from within. View the slides from Part 1 of the series: Is it time for a Chief Collaboration Officer? Listen to the recording today: http://bit.ly/1L1SFow
The .NET ecosystem has radically transformed over the past 10 years; in the distant past, Microsoft actively discouraged and dismissed the possibility and viability of OSS categorically. Now, everything is open source and Microsoft is one of the single biggest contributors of open source globally. That same trend is strongly reflected in the .NET community - large companies include banks, insurers, airlines, manufacturers, and health care giants all feel increasingly comfortable using OSS products in the core of applications that generate billions of dollars a year in capital.
In this talk, we're going to cover the scope of the sustainability crisis, how it may affect you, and how to help prevent it both as an OSS user or as a contributor.
This presentation is delivered as part of the Faculty training program at Kristu Jayanthi College, Bangalore. The intent was to help students build competency and contribute to open source projects. Also which will eventually help them to build professional career in open source connected domains.
This event was organized by the SODA Foundation and lots of fabulous speakers delivered the series. Thank you SODA!!!!
PMI Thailand: DevOps / Roles of Project Manager (20-May-2020)Gonzague PATINIER
DevOps seems to be the latest ‘buzzword’ and trend in the IT industry. This is driven by business needs for ever-faster deployment of new functionality and frustrations with the time and effort it takes to get new systems into operations. It is no longer a question of ‘should we adopt DevOps’, but ‘when and how’?
DevOps represents a significant cultural and behavioral change and many organizations fail to address this in their adoption. Gartner defines DevOps as a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. These culture changes include organization changes, impacting structure, roles and responsibilities.
What and where is the role of the project manager in organizations that have transitioned towards adopting DevOPs? Join us and let’s discuss DevOps and answer your questions followed by an informative discussion.
Juniper's plans to reboot the OpenContrail community and transition from a Juniper-led project to a community led project. We need your help. Get involved.
By now, enterprises understand the value of Software as a Service (SaaS) and Infrastructure as a Service (IaaS), but there still is much confusion about Platform as a Service (PaaS). This confusion is one reason why enterprises have been slow to adopt PaaS. Why is there so much confusion? This presentation will help clear up the confusion of all the different types of PaaS offerings in the marketplace.
SESSION TITLE
DevOps - IaC
SESSION THEME
DevOps
SESSION OVERVIEW
This is a hands-on experience workshop on "DevOps - IaC" and Automation from Infrastructure prospective. The session provides valuable insights on How "IaC" is going to be future for traditional DC, VM's and for Cloud, and How to setup or start with "IaC", what tool set and pipelines can be used and followed to move from traditional manual approach to automated DevOps approach.
SESSION AGENDA
What is DevOps? and Why you need DevOps?
What is DevOps - IaC?
Overview of some essential tools like Git, Jenkins, Docker/Ansible
Live Demo
Q&A
SESSION TAKEAWAYS
DevOps - IaC Framework
Overview of Tool Set
Pipeline Creation Overview
Automation Idea
And at last confidence to start a change towards DevOps
DURATION
45 Mins
The document defines DevOps in several quotes emphasizing collaboration between developers and operations teams. It also discusses common DevOps adoption patterns such as separate silos, a separate DevOps team that can become just another silo, collaborating developers and operations teams, and embedding operations within development teams. Finally, it provides contact information for John Turner from Monkey Little to discuss DevOps enablement.
Dell Technologies World 2018 - DevOps & ITILMatt Schneider
The document discusses various DevOps and ITIL concepts related to automation, culture, and process improvement. It provides definitions of DevOps, Agile software development, and ITIL frameworks. It emphasizes establishing a generative culture, automating processes across the product lifecycle, focusing on continual improvement to remove waste, and using measurement to guide decisions. Automation is presented as key to enabling standard changes and benefiting development, operations, and other teams through an improved workflow.
This document discusses the role of database administrators (DBAs) in DevOps environments. It begins with an introduction to DevOps, emphasizing collaboration between developers and IT professionals. It then explores how DBAs are impacted, noting both opportunities for DBAs to influence decisions and embrace automation, as well as risks of being seen as roadblocks. The document provides overviews of various DevOps practices and tools that DBAs can learn, such as configuration management, continuous delivery, and GitHub. It argues that DBAs should update their skills while automating some traditional tasks, and embrace techniques like data virtualization, snapshots, and DataOps to remove databases as roadblocks to DevOps goals.
Red Hat Summit - What are your digital foundations?Eric D. Schabell
This mini-theater talk was given at Red Hat Summit 2017. It covers in 15 minutes the basic story of the foundations needed for digital transformation, based on customer research use cases and one is discussed in detail.
-- Eric D. Schabell, Global Technology Evangelist Director, @ericschabell
Our article in PTK describes how Ansible was used to boost Oracle Fusion Middleware to deliver true Infrastructure-as-Code (IaC) via extreme automation.
PTK Winter 2020 / Issue 72
2016.06 ACT-IAC Partners breakfast: GSA's 18F on DevOps deliveryChristopher Dorobek
The document discusses DevOps and its application in government agencies. It provides examples of how two agencies - the Federal Election Commission (FEC) and Nuclear Regulatory Commission (NRC) - have begun their DevOps journeys. It also outlines key characteristics of DevOps, such as automating processes, measuring outcomes, and creating a collaborative culture. Finally, it discusses how DevOps may evolve in government in the future through greater standardization, automation, measurement practices, and an emphasis on lean and adaptable organizations.
2014 #vBrownBag OpenStack Summit Atlanta Ju Lim -- OpenStack PersonasJu Lim
The document discusses OpenStack personas, which are profiles of fictional users developed based on real user research. It provides an overview of personas and their benefits for product development. Two sample personas, Ben and Daichi, are presented to illustrate how personas describe a user's goals, frustrations, and expectations to help guide design decisions. The document encourages involvement in the OpenStack Personas Working Group and ends with useful links for more information.
This document summarizes OpenStack, an open source cloud computing platform. It has over 1,600 individual contributors from 269 companies. OpenStack has a large global community, with members and developers in over 1,000 and 400 cities respectively. Major companies like PayPal, Concur, and Shutterstock use OpenStack for benefits like cost savings, flexibility, and access to community innovation. The OpenStack Foundation focuses on activities to improve interoperability, education, community connections, and empowering users.
OpenStack aims to be the ubiquitous open source cloud computing platform that can meet the needs of both public and private clouds regardless of size through simplicity and scalability. In three years, OpenStack has expanded beyond compute and object storage to include networking, storage and shared services. It has public clouds in more cities than Amazon and major private cloud users like Best Buy, Bloomberg and PayPal. OpenStack has over 1,000 developers from major IT companies and is the center of cloud innovation.
Cw13 the rising stack-how & why open stack is changing it by mark collier-ope...TheInevitableCloud
OpenStack is an open source cloud computing platform that manages large pools of compute, storage, and networking resources. It is developed through an open development process with over 800 developers from 50 companies contributing code. The OpenStack community has grown rapidly, with over 8,000 members from around the world. Many large companies are using OpenStack to power their cloud computing needs, attracted by its open governance model and rapid pace of innovation.
Evolving to Cloud-Native - Nate Schutta (1/2)VMware Tanzu
The document discusses evolving applications to be cloud native by following cloud computing best practices and design principles like microservices, containers, serverless computing, and continuous delivery. It outlines the 12 factors of cloud native applications which emphasize independence, isolation, and automation. While legacy applications may not meet all the principles, the goal is to design new applications and refactor existing ones opportunistically to take advantage of scalability, availability, and agility benefits of cloud computing.
Creating a Collaborative Workplace Culture Webinar SeriesCisco Canada
To increase innovation and productivity, organizations recognize that they have to get better at creating more “collaborative cultures” to leverage the collective knowledge, expertise and experience from within. View the slides from Part 1 of the series: Is it time for a Chief Collaboration Officer? Listen to the recording today: http://bit.ly/1L1SFow
The .NET ecosystem has radically transformed over the past 10 years; in the distant past, Microsoft actively discouraged and dismissed the possibility and viability of OSS categorically. Now, everything is open source and Microsoft is one of the single biggest contributors of open source globally. That same trend is strongly reflected in the .NET community - large companies include banks, insurers, airlines, manufacturers, and health care giants all feel increasingly comfortable using OSS products in the core of applications that generate billions of dollars a year in capital.
In this talk, we're going to cover the scope of the sustainability crisis, how it may affect you, and how to help prevent it both as an OSS user or as a contributor.
This presentation is delivered as part of the Faculty training program at Kristu Jayanthi College, Bangalore. The intent was to help students build competency and contribute to open source projects. Also which will eventually help them to build professional career in open source connected domains.
This event was organized by the SODA Foundation and lots of fabulous speakers delivered the series. Thank you SODA!!!!
PMI Thailand: DevOps / Roles of Project Manager (20-May-2020)Gonzague PATINIER
DevOps seems to be the latest ‘buzzword’ and trend in the IT industry. This is driven by business needs for ever-faster deployment of new functionality and frustrations with the time and effort it takes to get new systems into operations. It is no longer a question of ‘should we adopt DevOps’, but ‘when and how’?
DevOps represents a significant cultural and behavioral change and many organizations fail to address this in their adoption. Gartner defines DevOps as a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. These culture changes include organization changes, impacting structure, roles and responsibilities.
What and where is the role of the project manager in organizations that have transitioned towards adopting DevOPs? Join us and let’s discuss DevOps and answer your questions followed by an informative discussion.
Juniper's plans to reboot the OpenContrail community and transition from a Juniper-led project to a community led project. We need your help. Get involved.
By now, enterprises understand the value of Software as a Service (SaaS) and Infrastructure as a Service (IaaS), but there still is much confusion about Platform as a Service (PaaS). This confusion is one reason why enterprises have been slow to adopt PaaS. Why is there so much confusion? This presentation will help clear up the confusion of all the different types of PaaS offerings in the marketplace.
SESSION TITLE
DevOps - IaC
SESSION THEME
DevOps
SESSION OVERVIEW
This is a hands-on experience workshop on "DevOps - IaC" and Automation from Infrastructure prospective. The session provides valuable insights on How "IaC" is going to be future for traditional DC, VM's and for Cloud, and How to setup or start with "IaC", what tool set and pipelines can be used and followed to move from traditional manual approach to automated DevOps approach.
SESSION AGENDA
What is DevOps? and Why you need DevOps?
What is DevOps - IaC?
Overview of some essential tools like Git, Jenkins, Docker/Ansible
Live Demo
Q&A
SESSION TAKEAWAYS
DevOps - IaC Framework
Overview of Tool Set
Pipeline Creation Overview
Automation Idea
And at last confidence to start a change towards DevOps
DURATION
45 Mins
The document defines DevOps in several quotes emphasizing collaboration between developers and operations teams. It also discusses common DevOps adoption patterns such as separate silos, a separate DevOps team that can become just another silo, collaborating developers and operations teams, and embedding operations within development teams. Finally, it provides contact information for John Turner from Monkey Little to discuss DevOps enablement.
Dell Technologies World 2018 - DevOps & ITILMatt Schneider
The document discusses various DevOps and ITIL concepts related to automation, culture, and process improvement. It provides definitions of DevOps, Agile software development, and ITIL frameworks. It emphasizes establishing a generative culture, automating processes across the product lifecycle, focusing on continual improvement to remove waste, and using measurement to guide decisions. Automation is presented as key to enabling standard changes and benefiting development, operations, and other teams through an improved workflow.
This document discusses the role of database administrators (DBAs) in DevOps environments. It begins with an introduction to DevOps, emphasizing collaboration between developers and IT professionals. It then explores how DBAs are impacted, noting both opportunities for DBAs to influence decisions and embrace automation, as well as risks of being seen as roadblocks. The document provides overviews of various DevOps practices and tools that DBAs can learn, such as configuration management, continuous delivery, and GitHub. It argues that DBAs should update their skills while automating some traditional tasks, and embrace techniques like data virtualization, snapshots, and DataOps to remove databases as roadblocks to DevOps goals.
Red Hat Summit - What are your digital foundations?Eric D. Schabell
This mini-theater talk was given at Red Hat Summit 2017. It covers in 15 minutes the basic story of the foundations needed for digital transformation, based on customer research use cases and one is discussed in detail.
-- Eric D. Schabell, Global Technology Evangelist Director, @ericschabell
Our article in PTK describes how Ansible was used to boost Oracle Fusion Middleware to deliver true Infrastructure-as-Code (IaC) via extreme automation.
PTK Winter 2020 / Issue 72
2016.06 ACT-IAC Partners breakfast: GSA's 18F on DevOps deliveryChristopher Dorobek
The document discusses DevOps and its application in government agencies. It provides examples of how two agencies - the Federal Election Commission (FEC) and Nuclear Regulatory Commission (NRC) - have begun their DevOps journeys. It also outlines key characteristics of DevOps, such as automating processes, measuring outcomes, and creating a collaborative culture. Finally, it discusses how DevOps may evolve in government in the future through greater standardization, automation, measurement practices, and an emphasis on lean and adaptable organizations.
2014 #vBrownBag OpenStack Summit Atlanta Ju Lim -- OpenStack PersonasJu Lim
The document discusses OpenStack personas, which are profiles of fictional users developed based on real user research. It provides an overview of personas and their benefits for product development. Two sample personas, Ben and Daichi, are presented to illustrate how personas describe a user's goals, frustrations, and expectations to help guide design decisions. The document encourages involvement in the OpenStack Personas Working Group and ends with useful links for more information.
This document summarizes OpenStack, an open source cloud computing platform. It has over 1,600 individual contributors from 269 companies. OpenStack has a large global community, with members and developers in over 1,000 and 400 cities respectively. Major companies like PayPal, Concur, and Shutterstock use OpenStack for benefits like cost savings, flexibility, and access to community innovation. The OpenStack Foundation focuses on activities to improve interoperability, education, community connections, and empowering users.
OpenStack aims to be the ubiquitous open source cloud computing platform that can meet the needs of both public and private clouds regardless of size through simplicity and scalability. In three years, OpenStack has expanded beyond compute and object storage to include networking, storage and shared services. It has public clouds in more cities than Amazon and major private cloud users like Best Buy, Bloomberg and PayPal. OpenStack has over 1,000 developers from major IT companies and is the center of cloud innovation.
How do you agile your global team to contribute to openstackAlexis Monville
This document discusses how the company eNovance uses agile practices to manage their global team working on OpenStack. Key points include:
- Using Scrum values and framework to manage distributed teams across multiple time zones. Communication tools include instant messaging, video conferencing, wikis.
- Onboarding for remote workers includes assigning a buddy, self-training programs, and 2-4 weeks in an office. An Agile Guild shares skills across teams.
- Contributions to OpenStack must be merged upstream before deployment. Real open source involvement is emphasized.
- Agile practices like 2-week sprints and limiting work in progress are applied to both internal development and customer projects involving discovery workshops and iterative design
Jules Fakhoury worked for 3 years at Ormuco, an OpenStack startup. Over this time, he transitioned from technical support to research and development to sales and business development. He learned skills in system administration, software development, and business. Fakhoury discussed how to get started with OpenStack, challenges of working with system administrators and developers, and navigating the business world to bridge the technical and business sides of an OpenStack startup.
OpenStack celebrates its third birthday, July 19, 2013, and this presentation provides an update on the community momentum, as well as what's next. #openstack3bday
Open Source Web Content Management StrategiesKStod
DotNetNuke Co-Founder Shaun Walker shares "Effective Strategies for Evaluating and Eeploying Open Source Content Management Tools" at the Gilbane Conference 2010 in San Francisco
The Agile and Open Source Way (AgileTour Brussels)Alexis Monville
Slides from AgileTour Brussels presentation on September 27th, 2013. More information on AgileTour Brussels: http://atbru.be/
The Agile and Open Source Way is the book for everyone who wants to scale agile in multiple distributed teams. This book will also help you to collaborate upstream with Open Source projects.
Whether you want to improve interactions with other teams inside or outside your company, or just interested in scaling from more than one team, you will find in this publication the information you need, illustrated by a real case.
http://www.the-agile-and-open-source-way.com/
The lessons I learned is that Open source quickly becomes the natural choice wherever commoditization is happening in the software stack. Thus we expect business-to-business open source, which is already a significant trend in recent history, to become an increasingly common form of open source collaboration. Companies who understand the ground rules of business-to-business open source will be better positioned to identify and take advantage of open source opportunities in the competitive spaces that they share with other companies.
So I will share why open strategy is import for the enterprise. And how to do contributions for the open source projects n today’s topic.
Presentation by Mark Collier & Jonathan Bryce April 2012 to industry Analysts in San Francisco covering OpenStack background & and an update on the Foundation plans.
OSCELOT is an open source community that develops educational tools and resources through collaboration. It has grown from a mailing list to over 100 projects with thousands of downloads. The community offers benefits like reducing costs through shared development and providing technical support. Getting involved can range from using existing tools to contributing code, documentation, or other support for projects.
The Internet Society works to promote an open and globally connected Internet through technology development, policy engagement, and operational best practices. It founded the Internet Engineering Task Force (IETF) and runs programs like Deploy360 and Best Current Operational Practices (BCOP) to help operators deploy new technologies and standards. A recent survey found that while many operators are interested in IETF standards work, they face challenges like lack of time and travel budgets in directly engaging with or influencing the IETF process. The Internet Society aims to address these issues and facilitate more communication between operators and the IETF.
This document discusses OpenStack, an open source software project for building public and private clouds. It outlines OpenStack's value in providing freedom from vendor lock-in and credibility through an open, community-driven model. The document proposes establishing standards and a trademark framework to ensure compatibility between OpenStack-powered products and allow the community to effectively promote the brand through shared marketing assets and guidelines.
OpenStack is an open-source cloud computing platform that manages compute, storage, and networking resources throughout a datacenter. It supports both private and public clouds and is used by many large companies. Canonical is a major contributor to OpenStack and offers services to deploy and manage OpenStack clouds on Ubuntu Linux.
Media, messaging and telecommunications convergence is now accepted as the norm. Convergence has resulted in greater consumer choice, lower costs and incredible innovation. It is important to note that even incumbent vendors in this space have much to gain from such convergence as it results in the potential to offer higher value services to customers, thus creating more revenue opportunities.
Enterprise IT has not yet seen convergence come home. We continue to create separation between BPM, SOA, EDA, WOA, SaaS, Cloud computing and more. Unlike the case of telecommunications convergence, however, in the enterprise IT world the incumbents are actually not incentivized to fuel convergence as they continue to "cash in" on old investments, slightly refreshed in some cases.
Fortunately, all hope is not lost! As open standards focused on interoperability become more pervasive, many traditional technological
boundaries are rapidly coming down and falling victim to convergence. Open source further accelerates the process by being the breeding grounds of untethered disruptive innovation resulting in simple, easy to use technologies which are made available freely, thus fueling rapid adoption.
In this talk I explore the growth of convergence in enterprise IT and the radical simplicity it is delivering to enterprise architects & developers.
This document discusses various tools and tactics for prototyping and user testing. It begins by explaining how prototyping during the discovery phase can help validate problems and assumptions. It then discusses using prototyping to test multiple solutions and gain insights to support design decisions. Finally, it provides an overview of different prototyping methods and considerations for tools, fidelity, audience, and platform.
How I Contribute to OpenStack: Hastexo’s Florian HaasRackspace
Florian Haas is the CEO and co-founder of hastexo, a company that provides consultancy and support for OpenStack. He became involved with OpenStack because it has an active, growing community and is making rapid progress. Haas' main contribution was authoring and maintaining the OpenStack High Availability Guide, though he credits his colleague Martin Loschwitz with developing the actual concepts and code. Haas believes the openness of OpenStack allows for very flexible, scalable cloud platforms and that having many developers contributing leads to fewer bugs and easier development of new features.
OpenStack - What is it and why you should know about it!OpenStack
A presentation I did to the inaugural CompCon at ANU in Canberra 29/09/2013.In a phenomenally short time OpenStack has risen to be the dominant platform for building private and public clouds of any scale. With 1000s of contributors and hundreds of companies backing the project, Tristan will demonstrate why you need to know about OpenStack and get involved now.
- What is OpenStack
- History of the project
- Phenomenal growth of the project
- Relevance in Australia and internationally, presenting opportunities to build green field clouds the world over.
- Massive job demand
Similar to How Big Companies Contribute to OpenStack (20)
OpenStack - What is it and why you should know about it!
How Big Companies Contribute to OpenStack
1. How Big Companies Contribute to
OpenStack
Stefano Maffulli, OpenStack Community Manager
2.
3. OpenStack Mission
To produce the
ubiquitous open source cloud computing
platform
that will meet the needs of public and private
clouds regardless of size, by being simple to
implement and massively scalable.
4.
5. Four years in
More than 70 OpenStack User Groups exist and 9,400+
new members have joined in the last year
Community members are located in 139 different
countries around the world
More than 1,200 user surveys have been completed,
detailing OpenStack deployments
6. Community Stats – May 2013
ORGANIZATIONS
TOTAL CONTRIBUTORS
AVERAGE MONTHLY
CONTRIBUTORS
COUNTRIES
998 230 136
209
9,511
INDIVIDUAL MEMBERS
PATCHES MERGED
7,260
7. Community Stats – May 2014
ORGANIZATIONS
CURRENT CONTRIBUTORS
AVERAGE MONTHLY
CONTRIBUTORS
COUNTRIES
2,130 466 139
355
16,266
INDIVIDUAL MEMBERS
PATCHES MERGED
17,209
8. Trends and Themes in Year Four
Maturity of use cases, across more traditional industries
like financial services and retail
“The software in the games
themselves allows users to play a
game and immediately share video of
what you have done in the game with
the rest of the world.” - Joel Johnston
“AT&T has 120 applications
deployed on OpenStack in 7
data centers” – Toby Ford, AVP IT
Operations Strategic Realization
“We’re running a serious business on this
technology, and this is what we have to do
to remain competitive and flexible in this
environment.” – Glenn Ferguson, Head of
Private Cloud Enablement
“I’m trying to lead a revolution to help
empower people when they come to
work in technology.” - Chris Launey,
Direct Cloud Services and Architect at Walt
Disney Company
9. Trends and Themes in Year Four
Focus on operational experience and closing the
feedback loop between operators and developers
11. Trends and Themes in Year Four
Stability, better test coverage and tighter integration
across the software platform
12. Facts
Big
169 git repositories
2.0M+ LOC
22 Official Programs (Integrated and Incubated)
Moving fast
A new release every 6 months
Programs and projects coming in every release
Complex
Hard to deploy and to test
Lots of people from different countries and companies
13.
14.
15. How Is OpenStack Lead?
No traditional management structure
No 'dictator', no 'architect', no 'product manager'
Representative democracy
Technical leaders elected by developers
Technical Committee also elected
Board of Directors mostly elected
16. How Is OpenStack Lead?
Time-based releases, every 6 months
The cadence keeps people focused
Milestones to maintain the rhythm
Roadmap defined via blueprints
Best proposed at the beginning of the cycle
Should have specifications attached
Approved for milestones by PTLs
17. How Is OpenStack Lead?
Lots of communication during the cycle
To manage exceptions
With community leaders, release manager, committees
18. How Is OpenStack Lead?
Communication in real life
Design Summit to begin a new development cycle
Mid-cycle meetings for team
24. Committed Companies
Have invested in OpenStack as a strategy
Independent from level of sponsorship
Lots of developers contributing upstream
Have 'core' reviewers
Get their employees elected as Project Tech Leads
Sell products “based on” OpenStack and may also use
consume OpenStack
Distributions + extras
Public/private clouds
25.
26. Committed Companies
Development teams are organized around OpenStack
Release Cycle
Are deeply involved in the decision making process
Know how and with whom to communicate
Do a lot of code reviews
Help fix things when they break
Provide resources to the community
Give back a lot and visibly, get good karma
Spend karma to get things done, faster
27. Example Agile Teams
Face-to-Face and occasional conversations
Only online conversations are valued
Standup meetings with audio/video, even for in-office
people
Use internal mailing lists, wiki, instant messaging
Regular meetups in person to socialize, outside work
In-person sprints to develop code
28. Example Agile Teams
Product backlog vs Blueprints
Keep the pace, releases scheduled around 6months cycle
Upstream first, avoid maintaining a fork
Define “done” as “patch submitted”, requires keeping a fork
until patch is “merged”
Workflow development very similar to OpenStack's
Code review and automated testing, similar setup
Added stakeholder: community
Requires paying attention to what happens there
29. Involved Companies
Invested in OpenStack for tactical reasons
Developers involved on outskirts first, on core functionalities
when needed
Focus on plugins and drivers
Sell products/services “built for” OpenStack
Ex. hardware and ancillary software
Help a lot to expand ecosystem's value
30. Involved Companies
Development teams organized around internal release cycles
Marginally involved in decision making
Don't know exactly how and with whom to communicate
Focusing on plugins and drivers
Get less karma, have less to spend to speed things up
33. How To Mitigate Friction
Organize Teams around the open source model
Coordinate with release cycle
Get to know the relevant actors
Participate in conversations, online and in real life
Join Summits and mid-cycle meetings
34. How To Mitigate Friction
Adopt OpenStack's constraints in your team
Favor electronic communication, avoid watercooler talks
Make all work visible and exposed
If it doesn't have a URL, it doesn't exist
Favor asynchronous communication
Even if your team is in the same timezone, expect you'll
have to interact with people somewhere else
Avoid locking points
Push code for review early and at any time, use the WIP
to get early comments before it's even ready to merge
35. Too Much To Handle?
Get developers exposed to OpenStack way of doing things
Upstream University, two days free training in Paris
Give mandate to your devs to do work upstream
Makes your team more aware of surroundings
Give them free time to spend upstream, 80/20
If nothing else, do code reviews to get karma
36. What You Gain
Less “your contribution is late or missing tests”
Your developers will know deadlines and best practices
Less “thank you but we don't like how you implemented it”
Your developers will have circulated design ideas before
proposing code
More “Well done, we wish someone did this before”
Your team will fix issues proactively
More karma to get past the dreaded Feature Freeze
PTLs will know that your developers know how to deliver
good code in time and be more willing to grant exceptions
37. November 3-7, 2014 – Paris!
Registration and sponsorships now open!
Call for speakers is open.
Book your travel early, room blocks will fill up
fast!
Travel Assistance Program available.
More details at openstack.org/summit
38. All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License
(unless otherwise specified). "OpenStack" is a registered trademark. The logos, wordmark and icons are subject to
international laws and its use is subject to the trademark policy.
Thank you …
Stefano@openstack.org
http://maffulli.net
@smaffulli
39. Rise of the Superuser
Drive transformation
Give back
http://superuser.opensta
40. All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License
(unless otherwise specified). "OpenStack" is a registered trademark. The logos, wordmark and icons are subject to
international laws and its use is subject to the trademark policy.
Credits and More Content
https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/
https://www.openstack.org/summit/openstack-summit-atlanta-2014/session-videos/presentation/
http://upload.wikimedia.org/wikipedia/commons/4/4a/Artist%27s_concept_of_collision_at_HD_1
http://upload.wikimedia.org/wikipedia/commons/c/c8/Shinkansen_tokyo.jpg
http://activity.openstack.org/dash/browser/scm-companies.html
Editor's Notes
Identity, Image and artifacts, Telemetry, Orchestration, Database
And incubated: data processing (hadoop), DNS as a service, Bare metal, Deployment, Key management
Identity, Image and artifacts, Telemetry, Orchestration, Database
And incubated: data processing (hadoop), DNS as a service, Bare metal, Deployment, Key management
The long tail of those 75 companies committing code in a given month
This is what pundits have been predicting for OpenStack in the past 4 years... it hasn't happened and it won't happen.
Not every company can be Red Hat or IBM or HP or Mirantis and companies selling hardware, developing drivers for OpenStack have value to bring to the table.
Some things that these can do to make things less hard for your developers:
This may require a major shift in corporate culture. Change is hard.
Knowing how OpenStack does things is the first step to manage expectations. Developers will learn how things are done and why.
They are not only transforming their infrastructure, but their business processes and culture
They give back to the community, share knowledge with peers across their industries and help shape the future of OpenStack