mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-01 21:50:13 +08:00
Xingyu.Wang
GitHub
commit
237190eaf3
@ -1,68 +0,0 @@
|
||||
Translating by Bestony
|
||||
Scaling Collaboration in DevOps
|
||||
=================================
|
||||
|
||||
|
||||
|
||||
Those familiar with DevOps generally agree that it is equally as much about culture as it is about technology. There are certainly tools and practices involved in the effective implementation of DevOps, but the foundation of DevOps success is how well [teams and individuals collaborate][1] across the enterprise to get things done more rapidly, efficiently and effectively.
|
||||
|
||||
Most DevOps platforms and tools are designed with scalability in mind. DevOps environments often run in the cloud and tend to be volatile. It’s important for the software that supports DevOps to be able to scale in real time to address spikes and lulls in demand. The same thing is true for the human element as well, but scaling collaboration is a whole different story.
|
||||
|
||||
Collaboration across the enterprise is critical for DevOps success. Great code and development needs to make it over the finish line to production to benefit customers. The challenge organizations face is how to do that seamlessly and with as much speed and automation as possible without sacrificing quality or performance. How can businesses streamline code development and deployment, while maintaining visibility, governance and compliance?
|
||||
|
||||
### Emerging Trends
|
||||
|
||||
First, I want to provide some background and share some data gathered by 451 Research on DevOps and DevOps adoption in general. Cloud, agile and DevOps capabilities are important for organizations today—both in perception and reality. 451 sees enterprise adoption of these things, as well as container technologies, growing—including increased usage in production environments.
|
||||
|
||||
There are a number of advantages to embracing these technologies and methodologies, such as increased flexibility and speed, reduction of costs, improvements in resilience and reliability, and fitness for new or emerging applications. According to 451 Research, organizations also face some barriers including a lack of familiarity and required skills internally, the immaturity of these emerging technologies, and cost and security concerns.
|
||||
|
||||
In the “[Voice of the Enterprise: SDI Q4 2015 survey][2],” 451 Research found that more than half of the respondents (51.7 percent) consider themselves to be late adopters, or even the last adopters of new technology. The flip side of that is that almost half (48.3 percent) label themselves as first or early adopters.
|
||||
|
||||
Those general sentiments are reflected in the survey responses to other questions. When asked about implementation of containers, 50.3 percent stated it is not in their plans at all, while the remaining 49.7 percent are in some state of planning, pilot or active use of container technologies. Nearly two-thirds (65.1 percent) indicated that they use agile development methodologies for application development, but only 39.6 percent responded that they’ve embraced DevOps approaches. Nevertheless, while agile software development has been in the industry for years, 451 notes the impressive adoption of containers and DevOps, given they are emergent trends.
|
||||
|
||||
When asked what the top three IT pain points are, the leading responses were cost or budget, insufficient staff and legacy software issues. As organizations move to cloud, DevOps, and containers issues such as these will need to be addressed, along with how to scale both technologies and collaboration effectively.
|
||||
|
||||
### The Current State
|
||||
|
||||
The industry—driven in large part by the DevOps revolution—is in the midst of a sea change, where software development is becoming more highly integrated across the entire business. The creation of software is less segregated and is more and more a function of collaboration and socialization.
|
||||
|
||||
Concepts and methodologies that were novel or niche just a few years ago have matured quickly to become the mainstream technologies and frameworks that are driving value today. Businesses rely on concepts such as agile, lean, virtualization, cloud, automation and microservices to streamline development and enable them to work more effectively and efficiently at the same time.
|
||||
|
||||
To adapt and evolve, enterprises need to accomplish a number of key tasks. The challenge companies face today is how to accelerate development while reducing costs. Organizations need to eliminate the barriers that exist between IT and the rest of the business, and work cooperatively toward a strategy that provides more effectiveness in a technology-driven, competitive environment.
|
||||
|
||||
Agile, cloud, DevOps and containers all play a role in that process, but the one thing that binds it all is effective collaboration. Each of these technologies and methodologies provides unique benefits, but the real value comes from the organization as a whole—and the tools and platforms used by the organization—being able to collaborate at scale. Successful DevOps implementations also require participation from other stakeholders beyond development and IT operations teams, including security, database, storage and line-of-business teams.
|
||||
|
||||
### Collaboration-as-a-Platform
|
||||
|
||||
There are services and platforms online—such as GitHub—that facilitate and streamline collaboration. The online platform functions as a code repository, but the value extends beyond just providing a place to store code.
|
||||
|
||||
Such a [collaboration platform][4] helps developers and teams collaborate more effectively because it provides a community where the code and process can be shared and discussed. Managers can monitor progress and track what code is shipping next. Developers can experiment with new ideas in a safe environment before taking those experiments to a live production environment, and new ideas and experiments can be effectively communicated to the appropriate teams.
|
||||
|
||||
One of the keys to more agile development and DevOps is to allow developers to test things and gather relevant feedback quickly. The goal is to produce quality code and features faster, not to waste time setting up and managing infrastructure or scheduling more meetings to talk about it. The GitHub platform, for example, enables more effective and scalable collaboration because code review can occur when it is most convenient for the participants. There is no need to try and coordinate and schedule code review meetings, so the developers can continue to work uninterrupted, resulting in greater productivity and job satisfaction.
|
||||
|
||||
Steven Anderson of Sendachi noted that GitHub is a collaboration platform, but it’s also a place for your tools to work with you, too. This means it can help not only with collaboration and continuous integration, but also with code quality.
|
||||
|
||||
One of the benefits of a collaboration platform is that large teams of developers can be broken down into smaller teams that can focus more efficiently on specific components. It also allows things such as document sharing alongside code development to blur the lines between technical and non-technical contributions and enable increased collaboration and visibility.
|
||||
|
||||
### Collaboration is Key
|
||||
|
||||
The importance of collaboration can’t be stressed enough. It is a key tenet of DevOps culture, and it’s vital to agile development and maintaining a competitive edge in today’s world. Executive or management support and internal evangelism are important. Organizations also need to embrace the culture shift—blending skills across functional areas toward a common goal.
|
||||
|
||||
With that culture established, though, effective collaboration is crucial. A collaboration platform is an essential element of collaborating at scale because it streamlines productivity and reduces redundancy and effort, and yields higher quality results at the same time.
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://devops.com/2016/05/16/scaling-collaboration-devops/
|
||||
|
||||
作者：[TONY BRADLEY][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: http://devops.com/author/tonybsg/
|
||||
[1]: http://devops.com/2014/12/15/four-strategies-supporting-devops-collaboration/
|
||||
[2]: https://451research.com/
|
||||
[3]: https://451research.com/customer-insight-voice-of-the-enterprise-overview
|
||||
[4]: http://devops.com/events/analytics-of-collaboration-on-github/
|
||||
70
translated/tech/20160516 Scaling Collaboration in DevOps.md
Normal file
70
translated/tech/20160516 Scaling Collaboration in DevOps.md
Normal file
@ -0,0 +1,70 @@
|
||||
Devops的弹性合作
|
||||
=================================
|
||||
|
||||
|
||||
|
||||
那些熟悉Devops的人普遍认同这样的文化关乎科技。当然，工具和参与是Devops有效实施的必要。但是Devops成功的基础是[团队合作][1]在企业做事更迅速，有效
|
||||
|
||||
|
||||
大多数的DevOps平台和工具的设计具有可扩展性的理念。DevOps环境通常运行在云端，并且容易发生变化。为了支持DevOps实时规模解决需求激增，软件变得很重要。同样的事情是真实的人为因素，但缩放合作是一个完整的不同的故事。
|
||||
|
||||
|
||||
跨企业协同是DevOps成功的关键。好的代码和发展是需要的。面临的挑战是如何做到无缝和尽可能多的速度和自动化，而不牺牲质量或性能。企业如何才能简化代码的开发和部署，同时保持知名度，治理和合规？
|
||||
|
||||
### 新兴趋势
|
||||
|
||||
首先，我先提供一些背景，分享一些通过451研究公司 关于devops的研究而获取的数据。云、敏捷和Devops 在今天是非常重要的，不管是理念还是现实。451研究公司看到企业通过这些东西，还包括容器技术、增长大量的用在生产环境中。
|
||||
|
||||
拥抱这些技术和方法有许多优点，比如提高灵活性和速度，降低成本，提高弹性和可靠性，适应新的或新兴的应用。根据451公司的研究，组织也面临着一些障碍，包括缺乏熟悉和所需的技能，这些新兴技术的不成熟，成本和安全问题。
|
||||
|
||||
在 “[Voice of the Enterprise: SDI Q4 2015 survey][2],” 451公司发行超过一半的受访者者(最后为57.1%)考虑到他们是最终调查者或新兴科技。另一方面，近半受访者（48.3 %）认为自己是第一个或早起的采用者。
|
||||
|
||||
这些普遍性的情绪表现在对其他问题的调查中。当问起容器的执行情况时，50.3%的人表示这不在他们的计划中。49.7%的人是在进行计划、试点或积极使用容器技术。近2/3（65.1%）的人表示，他们用敏捷开发的应用开发，但是只有39.6%的回应，他们正在积极拥抱DevOps。然而，敏捷软件开发已经在行业内存在了多年，451公司注意到通过容器和Devops的提升给他们了很现实的趋势。
|
||||
|
||||
当被问及首要的三个痛点是什么，被提及最多的是成本或预算，工作人员和遗留软件问题。随着企业向云，DevOps，和容器等转型，这些都需要加以解决，以及如何规模技术和协作的有效。
|
||||
|
||||
### 当前状况
|
||||
|
||||
由Devops革命在很大程度上带动产生巨大变化的行业，使得软件开发变得更加高度集成的整个业务。软件的创造是不分种族的，而且更多是协作和社会化的功能。
|
||||
|
||||
在推动价值的今天，几年前的概念和方法已经成熟，很快就成为今天的主流技术和框架。企业依靠如敏捷、精益、虚拟化、云计算、自动化等概念来简化开发，同时使工作更加有效。
|
||||
|
||||
为适应和发展，企业需要完成一系列的关键任务。当今面临的挑战是如何加快发展的同时降低成本。组织需要消除它和其他业务之间存在的障碍，并在一个由技术驱动的竞争环境中提供更多有效的战略合作。
|
||||
|
||||
敏捷、云计算、Devops和容器在这个过程中起着重要的作用，但是有一件事情，他们都是有效的合作。每一种技术和方法都提供了独特的优势，但真正的价值来自于组织的整体能够进行规模协同和组织所使用的工具和平台。成功的DevOps的实现也需要其他利益相关者的参与，发展IT运营团队，包括安全、数据库、存储和业务队伍。
|
||||
|
||||
### 合作即平台
|
||||
|
||||
有一些在线的服务和平台，比如Github,促进了流式合作。它的功能是一个在线代码库，但是所产生的价值远超出了存储代码。
|
||||
|
||||
|
||||
这样一个[协作平台][4] 有助于开发人员和团队合作，因为它提供了一个代码和程序的社区可以共享和讨论。管理者可以监视进度和跟踪下一个代码是什么开发人员可以在一个安全的环境中进行实验，然后把这些实验的生活环境，新的想法和实验可以有效地传达给适当的团队。
|
||||
|
||||
更敏捷开发和DevOps的关键之一是允许开发人员测试并收集相关的快速反馈。目标是生产高质量的代码和功能，而不是浪费时间建立和管理基础设施或者安排更多的会议来讨论这个问题。比如GitHub平台，能够更有效的和可扩展的协作是因为代码审查可以由参与者最方便的进行。没有必要尝试协调和安排代码审查会议，使开发人员可以继续不间断地工作，从而产生更大的生产力和工作满意度。
|
||||
|
||||
Sendachi的Steven Anderson 指出，Github是一个协作平台，但它也是一个和你一起工作的工具。这样意味着他不仅可以帮助协作和持续集成，还影响了代码质量
|
||||
|
||||
合作平台的好处之一是，大型团队的开发人员可以分解成更小的团队，可以更有效地专注于特定的组件。它还允许诸如文件共享、模糊代码开发技术和非技术的贡献，增加了协作和可见性
|
||||
|
||||
### 合作是关键
|
||||
|
||||
合作的重要性不言而喻。合作是Devops文化的关键，也是当今世界能够进行敏捷开发和保持竞争优势的重要的一点。执行或管理的支持以及内部的传道是很重要的。组织还需要拥抱文化的转变---朝着目标混合技能跨越职能领域
|
||||
|
||||
当这样的文化建立起来，有效的合作是至关重要的。一个合作平台是规模合作的必要组件，因为简化了生产活动，并且减少了冗余和尝试，同时还产生了更高质量的结果。
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://devops.com/2016/05/16/scaling-collaboration-devops/
|
||||
|
||||
作者：[TONY BRADLEY][a]
|
||||
译者：[Bestony](https://github.com/Bestony)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: http://devops.com/author/tonybsg/
|
||||
[1]: http://devops.com/2014/12/15/four-strategies-supporting-devops-collaboration/
|
||||
[2]: https://451research.com/
|
||||
[3]: https://451research.com/customer-insight-voice-of-the-enterprise-overview
|
||||
[4]: http://devops.com/events/analytics-of-collaboration-on-github/
|
||||
Loading…
Reference in New Issue
Block a user