DevOpsDays Tokyo Opening
We will open the DevOpsDays Tokyo conference by giving a brief introduction of DevOps, the purpose and goals of the conference, as well as giving some of the sponsors an opportunity to introduce themselves.
Outline/structure of the Session
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Adam Jacob - The Future of DevOps (DevOpsの未来)Adam JacobCTOChef
schedule 1 year agoSold Out!
Adam Jacob氏は、Chef（旧名：Opscode）の創業者の一人で、2008年より同社のCTOに就任。開発責任者として、オープンソースのChef, Habitat, Inspecに加え、Chefの主力製品Chef Automateの開発を行い、体系的なDevOpsフレームワークを世に打ち出した功績が評価されている。また、広くIT業界でDevOpsの普及に貢献し、技術面のみならず、精神面、企業文化面からも非常にわかりやすくDevOpsの魅力を解説するプレゼンテーションには定評がある。
Adam Jacob is the co-founder of Chef (formerly Opscode), and has been the CTO since 2008. He has since been the core designer and developer for the open source Chef, Habitat and Inspect, plus the commercial product, Chef Automate, which is one of the only products in the DevOps market that takes form of a framework. He also is known widely in the industry as one of the most enthusiastic speakers on DevOps as not only technology, but as of its culture and even spiritual aspects.
Jim Borden - Progetによって.NETライブラリーのCIとビルド管理Jim BordenSr. Software EngineerCouchbase, Inc.
schedule 1 year agoSold Out!
If your team is too small, it can lead to time loss for build and testing . With Proget, you can set up several feeds and offer Nuget package builds both inside and outside the company. Using this, it is easy to determine what is happening with every build. Furthermore, if you test with the actual Nuget package, you can release it as-is to nuget.org. At Couchbase, I use this process to release a developer build every other week. Let's learn some ways to use Proget effectively!
Alex Papadimoulis - DevOps for Japan
DevOps represents a simple idea: increase collaboration across teams while automating processes. Although the concept is relatively new to Japan, American IT organizations have been trying to implement DevOps in recent years: many have found success, while others have seen failure.
One of main causes of failure is adopting the wrong culture. Although companies like Netflix and Etsy dominate the DevOps conversation, most enterprises do not have the same problems to solve, nor do they employee the same types of engineers. Thus simply, attempting to emulate Netflix will often yield failure.
It’s similar in Japan; the culture of Japanese IT organizations are quite different from western companies, and attempting to emulate western DevOps practices will often result in failure and other setbacks. Thus, in order to be successful with adopting DevOps practices, those practices must first be adapted for Japan.
In this talk, I’ll compare and contrast the unique cultural differences in Japanese IT organizations and discuss how you can adopt DevOps practices that specifically address those.
Alex Papadimoulis - WinOps: A DevOps tool roundup for Windows
Windows and Linux are very different; not just technologically, but philosophically. Tools are a major component to establishing DevOps, and the lack of Windows-centric tools limited early Windows DevOps adoptions as most initial supporting technologies emerged from Linux and open-source communities. WinOps strives to address the same challenges as DevOps, using different tools with a Windows approach.
This talk will be tool-focused, and give an overview of the major tools used in Windows DevOps environments.
Alex Papadimoulis - Building a DevOps Culture in a Windows Environment
DevOps tools and practices have traditionally been Linux-focused, which has presented a significant adoption hurdle in Windows-based organizations. Windows sysadmins rarely need to use a command line to do their job, let alone Ruby, Git, or other tools. Although tool vendors have tried to make “Windows versions” of their Linux tools, and Microsoft has tried adding “Linux features” to the Windows, many organizations still view DevOps as a square peg in a round hole.
To bring DevOps to Windows-based organizations, it’s important to not only understand the cultural differences between Windows and Linux, but learn how you can build a process that truly crosses development and operation silos, and doesn’t just become “the DevOps team”.