Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Cloud Luminaries: Victoria Livschitz on Using Automation to Achieve Developer Self-Service

DZone's Guide to

Cloud Luminaries: Victoria Livschitz on Using Automation to Achieve Developer Self-Service

· DevOps Zone
Free Resource

The Nexus Suite is uniquely architected for a DevOps native world and creates value early in the development pipeline, provides precise contextual controls at every phase, and accelerates DevOps innovation with automation you can trust. Read how in this ebook.

[This article was written by David Spark.]

"The complete computing system emerges in response to a business need," said Victoria Livschitz (@vlivschitz), CEO ofQubell, of her company’s mission statement.

We’re undergoing an enormous pace of innovation where software is transforming the world in a way we've never seen before. A CIO’s number one fear is how quickly their industry changes. Much of that is happening thanks to DevOps workflows that are hyper reactive to Software Development Life Cycles (SDLCs), explained Livschitz.

In order to deploy a continuous DevOps workflow, you will need to create a series of automation processes. Those will be defined by an understanding between the creator and the user of the automation tool, explained Livschitz in her presentation “Purpose-Defined Computing: The Next Frontier of Automation” at the 2014 Cloud Expo in Santa Clara, California.

“Think about button makers and button users,” said Livschitz. “It's not about giving them tools, but rather creating self-service interfaces.”

Deployment may not be the problem. The real problem may be a configuration change management problem, said Livschitz. If you can automate that process, by understanding the issues of users and creators, then you can solve a major SDLC workflow problem.

Livschitz outlined the three magic buttons every organization needs to create.

  • Launch button: This button will produce a working instance of an application, and will be part of constructing that environment.
  • Destroy button: Environments can't sprawl uncontrollably, nor can they live forever. Destruction of applications are sadly an afterthought, but all tools once launched will eventually die. Upon provisioning you must also think about deprovisioning.
  • Reconfigure button: The job of this button is to take a system from its current state to a new state. This could involve updating the index, patching the OS, or upgrading the schema.

There are more automation buttons you can create, but Livschitz warns that it’s better to have a fewer number of well working buttons, than lots of buttons that are not that reliable.

The DevOps Zone is brought to you in partnership with Sonatype Nexus.  See how the Nexus platform infuses precise open source component intelligence into the DevOps pipeline early, everywhere, and at scale. Read how in this ebook

Topics:

Published at DZone with permission of Kathy Thomas, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}