Deploying software in today’s enterprise environments is an extremely expensive and inefficient process. The cost in terms of resources, time and revenue lost is actually astounding. I was on the phone with a large insurance company recently that was struggling with high costs and time to market issues with their main retail application. Their DBAs were spending over 50% of their time manually deploying 3 releases a day.
Do you have high cost, highly skilled team members deploying software? It shouldn’t be that hard.
As the overall owner of the content for our next xChange global user conference, I always remember that the heart of xChange15 is the breakout session content but the soul of xChange is the array of fantastic customer presentations.
I am delighted to announce that, as of today, you can learn more about the xChange Call for Speakers on the xChange website and then submit your ideas for presentations
This is the first installment of an occasional series of posts in the run up to the launch of ChangeMan 8.1 later this year. As part of the routine pre-launch activities I’ll be chatting to the development team to learn about the cool features that have been added to this latest version.
ChangeMan ZMF is used by some of the largest mainframe development shops in the world. It is typical for these organizations to have hundreds of thousands of components managed and tens of thousands of components in motion. Keeping
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.
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
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
“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.
I’m excited to announce that we’ve made Serena Deployment Automation free for everyone…and free forever. The Community Edition provides full product functionality with deployment to 5 virtual or physical servers. You can add more end points for the new low price of just $1,499.
You can learn more about Serena Deployment Automation and download the Community Edition for free at www.serena.com/freedeploy.
So, let’s get to the why, what and how of it all…
When we started this series we talked about how release engineers have difficulty in keeping up with the rate of change in their environment. Every day a new security patch or software update is applied that changes the known topology of one or more deployment targets.
This is why, some release engineers insist, they have to hand-craft the deployment scripts each and every time.
In an ideal world every target environment would be standardized. But we don’t live in an ideal world. Whether it is our own on-premise platforms, virtualized or cloud platforms we know that their configurations are in a state of constant evolution. This makes it hard for release engineers