Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Nathen Harvey
Nathen Harvey minor updates to the ignite
Signed-off-by: Nathen Harvey <nharvey@chef.io>
Latest commit 18ebab4 Nov 21, 2016
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
LICENSE
README.md
Rugged Enterprise DevSecNetQAGovOps - Nathen Harvey - Ignite.pdf minor updates to the ignite Nov 21, 2016
Rugged Enterprise DevSecNetQAGovOps - Nathen Harvey - Ignite.pptx

README.md

Rugged Enterprise DevSecNetQAGovOps

DevOps is Dead

DevOps is dead.

It’s been a great run. We are approaching the seventh anniversary of DevOpsDays events.

There have been 95 DevOpsDays events since this started

All hope is not lost...let’s review some of the awesome things this movement has brought us and why I think it’s time to move on.

Agile Infrastructure

Historians will look at an open space session at Agile conf as the big bang event for DevOps.

A topic of “Agile Infrastructure” was proposed. This was a time when many people looked at using velcro wire wraps instead of plastic wire ties as being “agile” with their infrastructure.

Of course, this was also the beginning of the cloud and infrastructure as code was becoming a “thing”, too.

Cloud

As clouds formed and we had new, easy ways of deploying and scaling applications. Accessible via an API, mostly reliable, and inexpensive to get started. Sure, there were some stability issues and we had to start thinking about building and scaling resilient systems a bit differently.

Developers Operating

But Developers found new freedom with these APIs. They didn’t need to wait for IT or Operations to provision systems. Developers could build and run their own production systems in the cloud. It was awesome.

Anthrax started playing Public Enemy songs.

Operators Developing

Operations started embracing Infrastructure as Code, started focusing more on measurement and monitoring (Flava Flav), and were concerned about the safety of the cloud (S1Ws). Operations were finding themselves picking up other development practices like using version control systems and writing tests for their code.

Chuck D and Public Enemy wanted to collaborate with the developers.

DevOps

Now Dev and Ops really started working together.

They tore down walls, blew up silos, and started collaborating.

Learning from each other and giving back to the system so that it became much more than just the sum of it’s parts.

DevQAOps

But not everything was perfect.

Had we forgotten about testing? Applications simply do not go directly to production, that’s not safe. QA is required and cannot be left out of the mix.

DevQAOps

DevSecQAOps

Many security teams looked at DevOps and automated workflows being pushed and were scared. Manual processes were viewed as the way to security. After all, we know what commands were executed, we had one person responsible for securing systems, one responsible for securing applications. Overtime, they came to understand the benefits that automation provides: not only can we release fixes faster we can also ensure consistency across the entire infrastructure. Security is now part of DevOps. DevSecQAOps

Enterprise DevSecQAOps

What about the Enterprise?!

Legacy systems, hundreds, thousands, of developers, years of inertia and organizational structure. Clearly DevOps in this environment must be different. What we need is Enterprise DevSecQAOps

Enterprise DevSecNetQAOps

Switches, Firewalls, and all sorts of networking gear can be fully automated these days. We must include the Network Engineers in our club.

Enterprise DevSecQANetOps

Enterprise DevFinSecNetQAOps

You cannot move from the data center to the cloud, from waterfall to agile without changing how budgeting works. You must understand the tradeoffs between capital expenses and operating expenses. How can you provide a yearly budget when you’re going to be building application iteratively and consuming compute and other resources on demand? Clearly, the finance team needs to be part of Enterprise DevFinSecQANetOps!

Enterprise DevFinSecNetQAGovOps

Life, liberty, and the pursuit of happiness. These may not be the first things that come to mind when you think of the government but they are principles on which it was founded.

Bureaucracy, red tape, slow moving, wasteful. These words are likely closer to what comes to your mind. But we have a duty to help the government do better and there are many agencies within the government that want to improve. These people are also part of our DevOps Movement.

Enterprise DevGovFinSecQANetOps

Enterprise DevFinSecNetQAGovOps

PCI-DSS, HIPAA, SOX, many of our organizations fall under one or more regulatory burdens. When the auditors walk in to the building our goal should be to show them that we’re compliant and that we care. Not to appease and excuse them from the building as quickly as possible.

Yes, governance and compliance is also part of DevOps….but the good news is that we can reuse “Gov” to have multiple meanings. We’ll overload that part of the new term.

Enterprise DevHRFinSecNetQAGovOps

Keeping our teams happy, high functioning, and collaborating is, in part, an outcome of good human resource practices. Set aside you possible disdain for the name of the group or the idea that humans are resources to be managed and you’ll have to agree that HR plays a large and important role in your team. Is it possible for you to work on another team for a short period of time? Who drives recruiting in your organization? Can cross-functional teams be created to address a problem or work on a project without needing to change the org chart?

Enterprise DevGovHRFinSecQANetOps!

Rugged Enterprise DevHRFinSecNetQAGovOps

Having security in the room isn’t enough. Security teams need to bring new practices to bear as well. Introducing lean principles to the practice of security and working together with dev and ops is often labeled Rugged DevOps. Some would even argue that DevSecOps and Rugged DevOps are identical terms. We wouldn’t led “Gov” be constrained to one meaning, nor will we let security only have one part of the word! It’s that important!

Rugged Enterprise DevSecNetQAGovOps

Rugged Enterprise DevLegalHRFinSecNetQAGovOps

DevOps is about the community, too. We create, consume, and contribute open source software. Our legal team needs to be involved to make sure that your employees can do all of those things without having to jump through ridiculous hoops. This is the laptop I use to do work, this is the laptop I use to contribute to open source. I never contribute, only consume when in the office.

Rugged Enterprise DevLegalHRFinSecNetQAGovOps

Also, legal wouldn’t allow us to shorten the name of their group. Must be “Legal”

Rugged Enterprise DevLegalHRFinSecNetQAGovCustOps

WAIT!!! How could we forget the customer?! Aren’t we doing all of this to delight the customers? We should be delivering business and customer value. How do we need to change and improve to improve and drive our customer’s success?

Rugged Enterprise DevLegalHRFinSecNetQAGovCustOps!

Sh-flour

What do we call this? Sh-flour? No, it’s Cake! And it’s delicious. All of the ingredients working together to deliver customer delight. We don’t need to list out all of the ingredients, we just take a bite and enjoy.

DevOps

A cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.

Who practices DevOps?

Everyone!

  • We are not generalists – we are well connected specialists
  • We are all DevOps

LICENSE

Creative Commons License
Rugged Enterprise DevSecNetQAGovOps by Nathen Harvey is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

You can’t perform that action at this time.