Welcome!

@DevOpsSummit Authors: Liz McMillan, Elizabeth White, Pat Romanski, Yeshim Deniz, SmartBear Blog

Related Topics: @DevOpsSummit, Linux Containers, Containers Expo Blog

@DevOpsSummit: Blog Feed Post

Dual-Mode Enterprise #DevOps | @DevOpsSummit #CloudNative #Serverless #Docker

The trend of treating infrastructure as code is growing in popularity and with good reason

Environment as Code Expands Dual-Mode Enterprise DevOps
By Amy Johnston

The trend of treating infrastructure as code is growing in popularity and with good reason. Programmable infrastructure lets you take advantage of version control, continuous integration, and automated testing — practices that are proven to work for software development and that are essential for DevOps success.

But treating infrastructure as code brings a challenge: after you provision servers, containers, cloud instances, and other parts of your infrastructure based on the specifications that you’ve defined in code, how do you start using them in an automated way?

To meet this challenge, XebiaLabs has introduced the Environment as Code feature in XL Deploy. Environment as Code allows you to define your infrastructure and environments in code, making it easier for Development and Operations to collaborate on configuration management.

The Environment as Code feature builds on Release as Code, which was introduced earlier this year — expanding XebiaLabs’ support for dual-mode DevOps that accommodates different users’ needs. With dual-mode DevOps, you can involve technical and non-technical teams from across the business, from release managers and project managers, to security, compliance and risk teams, to IT management. Environment as Code gives technical team members more flexibility to use code to manage their software delivery pipelines, while less technical team members benefit from XL Deploy’s simple but powerful visual user interface and automatic capture of compliance data.

For example, one of XL Deploy’s most powerful features is dictionaries, which allow you to use placeholders for environment-specific information throughout your applications and configurations. Traditionally, Operations would be responsible for providing the right placeholder values for each environment; but with Environment as Code, it’s easy for developers to share ownership of this data by creating and managing dictionaries in source control alongside their application code.

So, what does defining an Environment as Code look like? Let’s take a look at two environments, TEST and PROD, both of which use Docker. You configure their properties in a Groovy file, which also defines the scope of the changes that XL Deploy should make.

But Environment as Code isn’t only useful for containers and cloud-based infrastructure. It provides the same benefits for middleware configurations. This example shows the definition of a JBoss Domain, an environment, and two dictionaries. It also illustrates that you don’t have to define everything you need in a single Groovy file; you can refer to configuration items that are defined in other files or that are defined in the XL Deploy repository itself.

With Environment as Code, you can synchronize infrastructure data with XL Deploy automatically based on the triggers that make sense for your DevOps pipeline. For example, you can update XL Deploy every time you commit a change in your Puppet code, or every time you create a new AWS EC2 instance or Azure virtual machine — and immediately deploy applications to the newly updated infrastructure. The XL Deploy REST API and command-line interface both allow you to build automatic synchronization when and where you need it.

Many core DevOps tools, such as Jenkins, Puppet, and Chef, are designed for developers, and they offer code as the primary way to manage releases and deployment infrastructure. But a purely technical design doesn’t meet the needs of large enterprises scaling DevOps across hundreds of teams and thousands of users. Enterprises need a strong DevOps orchestration and automation platform to provide the control, visibility, decision support, reporting, compliance, and security that are often lacking in these developer-oriented DevOps point tools. With XebiaLabs, teams can expand DevOps beyond developers and simple development pipelines, moving to full complex release pipelines that span the enterprise.

The post Environment as Code Expands Dual-Mode Enterprise DevOps appeared first on XebiaLabs Blog.

Read the original blog entry...

More Stories By XebiaLabs Blog

XebiaLabs is the technology leader for automation software for DevOps and Continuous Delivery. It focuses on helping companies accelerate the delivery of new software in the most efficient manner. Its products are simple to use, quick to implement, and provide robust enterprise technology.

@DevOpsSummit Stories
"I will be talking about ChatOps and ChatOps as a way to solve some problems in the DevOps space," explained Himanshu Chhetri, CTO of Addteq, in this SYS-CON.tv interview at @DevOpsSummit at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of business. Only 12% still survive. Similar percentages are found throughout enterprises of all sizes.
For better or worse, DevOps has gone mainstream. All doubt was removed when IBM and HP threw up their respective DevOps microsites. Where are we on the hype cycle? It's hard to say for sure but there's a feeling we're heading for the "Peak of Inflated Expectations." What does this mean for the enterprise? Should they avoid DevOps? Definitely not. Should they be cautious though? Absolutely. The truth is that DevOps and the enterprise are at best strange bedfellows. The movement has its roots in the tech community's elite. Open source projects and methodologies driven by the alumni of companies like Netflix, Google and Amazon. This is a great thing for the evolution of DevOps. It can be alienating for Enterprise IT though. Learning about Netflix and their simian armies, or Facebook and their mind-melting scale is fascinating. Can you take it back to the office on Monday morning though?
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Learn how to solve the problem of keeping files in sync between multiple Docker containers. In his session at 16th Cloud Expo, Aaron Brongersma, Senior Infrastructure Engineer at Modulus, discussed using rsync, GlusterFS, EBS and Bit Torrent Sync. He broke down the tools that are needed to help create a seamless user experience. In the end, can we have an environment where we can easily move Docker containers, servers, and volumes without impacting our applications? He shared his results so you can decide for yourself.