Welcome!

@DevOpsSummit Authors: Yeshim Deniz, Pat Romanski, Liz McMillan, Zakia Bouachraoui, Elizabeth White

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
Hackers took three days to identify and exploit a known vulnerability in Equifax’s web applications. I will share new data that reveals why three days (at most) is the new normal for DevSecOps teams to move new business /security requirements from design into production. This session aims to enlighten DevOps teams, security and development professionals by sharing results from the 4th annual State of the Software Supply Chain Report -- a blend of public and proprietary data with expert research and analysis.Attendees can join this session to better understand how DevSecOps teams are applying lessons from W. Edwards Deming (circa 1982), Malcolm Goldrath (circa 1984) and Gene Kim (circa 2013) to improve their ability to respond to new business requirements and cyber risks.
DXWorldEXPO LLC announced today that Nutanix has been named "Platinum Sponsor" of CloudEXPO | DevOpsSUMMIT | DXWorldEXPO New York, which will take place November 12-13, 2018 in New York City. Nutanix makes infrastructure invisible, elevating IT to focus on the applications and services that power their business. The Nutanix Enterprise Cloud Platform blends web-scale engineering and consumer-grade design to natively converge server, storage, virtualization and networking into a resilient, software-defined solution with rich machine intelligence.
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more business becomes digital the more stakeholders are interested in this data including how it relates to business. Some of these people have never used a monitoring tool before. They have a question on their mind like "How is my application doing" but no idea how to get a proper answer.
This session will provide an introduction to Cloud driven quality and transformation and highlight the key features that comprise it. A perspective on the cloud transformation lifecycle, transformation levers, and transformation framework will be shared. At Cognizant, we have developed a transformation strategy to enable the migration of business critical workloads to cloud environments. The strategy encompasses a set of transformation levers across the cloud transformation lifecycle to enhance process quality, compliance with organizational policies and implementation of information security and data privacy best practices. These transformation levers cover core areas such as Cloud Assessment, Governance, Assurance, Security and Performance Management. The transformation framework presented during this session will guide corporate clients in the implementation of a successful cloud solu...
So the dumpster is on fire. Again. The site's down. Your boss's face is an ever-deepening purple. And you begin debating whether you should join the #incident channel or call an ambulance to deal with his impending stroke. Yes, we know this is a developer's fault. There's plenty of time for blame later. Postmortems have a macabre name because they were once intended to be Viking-like funerals for someone's job. But we're civilized now. Sort of. So we call them post-incident reviews. Fires are never going to stop. We're human. We miss bugs. Or we fat finger a command - deleting dozens of servers and bringing down S3 in US-EAST-1 for hours - effectively halting the internet. These things happen.