Archive for the ‘DevOps’ Category

[caption id="" align="alignnone" width="327"] We are not reinventing the wheel here but we are perfecting it.[/caption]

A couple of weeks ago I wrote about downloading the new Serena Deployment Automation Appliance. This is the free, community edition of the exceptionally advanced Deployment Automation technology we introduced last year. You can get your own copy, free forever, at the



Our next DevOps Drive-In webcast features application deployment automation and database deployment automation working together. Register here for the September 18th event. Read on for some background on the topic.

With the explosion in the use of Agile



“Drinking our own champagne” is how we approach technology here at Serena. If we have a our own tool that supports part of the application development lifecycle we use it for our own development efforts. In fact the Serena development teams deploy the beta versions of our solutions straight into their production environments because they want exploit the cool-new-stuff just as much as you do!

When I sat down today to start writing about automated deployment in modern enterprises I thought I’d follow the Serena mantra and “drink our own champagne” too. So I



System’s programmers on the mainframe have a pretty difficult time these days. More and more complexity, rampant growth of z/Linux, Websphere and RD&T boxes. Draconian constraints, compliance and governance mandates to be applied. All with fewer and fewer resources. It is a common problem.

Serena is here to help. Our ChangeMan SSM technology is designed to be the SysProg’s best friend and unswerving ally.

Sitting quietly in the background monitoring system datasets and members like the APF authorized libraries, the LINKLIST datasets, console commands and any



UPDATE: Patrick was unable to speak last week, so we rescheduled the webcast to this Thursday at Noon ET / 9 am PT. Please register here.


 

Patrick Debois coined the term “DevOps” as part of the first DevOpsDays nearly 5 years ago. Now DevOps is a major movement in the smallest start-ups and the largest enterprises.

I welcome you to join me



(This is the conclusion of a 7-part series. Read part 1, part 2, part 3,



Myth: Errors happen: It’s software

Errors do occur. They occur for a reason. Often those reasons are out of our control. Someone changes an IP Address of a server. Someone changes the password to the back office system. Someone changes the name of a shared .DLL.

Of course in a well-managed and carefully controlled environment those kinds of things shouldn’t happen without the proper authentication, notification and approval. And the infamous “someone” is a responsible professional who calculates the impact of their changes and collaborates with everyone to minimize that impact. In a perfect world.

In the real world change is constant and calculating the consequences of change



As the DevOps movement approaches its 5 year anniversary, the question remains: is the movement ready to cross the chasm into mainstream IT? 

Stories of unicorns abound, and if we believe the vendors and early adopter case studies for the enterprise, we would be feeling that we are on the other side of the chasm, ready to get inside the tornado, change the culture and



Myth: Each deployment needs me

Helicopters have been described as “10,000 parts flying together in close formation. It is the mechanic’s job to keep that formation as tight as possible.”

Modern software applications comprise of millions of parts when you consider the huge chunks of code we bind into our applications from the database, security, web server, communications, encryption and authentication vendors. Add to that the seemingly infinite numbers of dependencies on external web services and internal CRM and financial systems.

There are 100 million lines of code in the Ford Taurus

But, just like the helicopter’s mechanic, the



Myth: Emergency fixes are different

“I don’t want to know why it happened: I just want you to fix it!” was what I was told early one morning by the Director of Sales. And she was right: getting the online store back online was the most important thing for the business. Blamestorming would come later.

There is a temptation at 3:00 am to just do whatever it takes to bring the system back on the air even if that means bypassing protocols and procedures designed to protect system integrity. Sales-and-Marketing and Audit-and-Compliance might not see eye-to-eye on this approach.

So why do emergency fixes have to be different? This myth is all about time. The time it takes to write the script.