Dev Ops or DevOps defined
In IT software development, Dev Ops describes an agile, co-operative relationship between Development and IT Operations. The goal of DevOps is to change and improve the relationship by advocating better communication and collaboration.
The relationship between the two is more usually a standoff than co-operation, where Ops protests that it’s been lobbed a ‘ticking time bomb’ of new deployments from Dev, that it can’t manage, modify, remediate or enhance. That why achieving harmony and co-operation is so important.
DevOps is good for business
Apart from resolving this stand-off, DevOps plays a key role in successful deployments, largely because of its key objectives:
- Delivering capabilities to business users faster
- Reducing the failure rate of new releases
- Minimising the lead time between fixes
- Improving system quality, and
- Speeding up mean-time to recovery in the event of failures introduced into production systems.
DevOps has been compared to the Holy Grail: if its objectives can be achieved by closely aligning the activities of Dev and Ops teams, it will speed up your response to the business’s demands and better support its vision.
Dev Ops and failures
Recent research from ZeroTurnaround found that 60% of the failures in Dev Ops projects are caused by human error or lack of automation. And IDC’s 2014 survey of Fortune 1000 companies found that trying to adapt current tools to deliver DevOps practices has a failure rate of 80%.
These are the findings from IDC’s 2014 survey of Fortune 1000 corporations:
- Average total cost of unplanned application downtime per year:$1.25 billion to $2.5 billion
- Average hourly cost of an infrastructure failure:$100,000 per hour
- Averagecost of a critical application failure per hour: $500,000 to $1 million
- Average number of deployments per month are expected to double in two years.
- Reducing the incidence and cost of failures and downtime is clearly critical, yet to do so and make DevOps a reality, IDC says you’ll need better tools.
- A recent study by the Project Management Institute (PMI) shows you’ll need better communications too, as poor communications account for 30% of project failures.
Dev Ops and Continuous Delivery
Clearly human error and lack of automation are major causes of systems failure, which will do nothing to encourage or support DevOps in your organizations. Clear, too, is the role of automation in reversing failures and encouraging Dev Ops.
How it works is this: automation enables Continuous Delivery or delivery of rapid, reliable and repeatable software changes, in small, manageable batches.
By doing this organizations can get new initiatives to market faster, and eliminate manual processes so that building of new environments is repeatable and consistent. Continuous Delivery is based on the principles of Dev Ops, which ensure closer collaboration of project teams and greater productivity, and automation makes it possible. Find out more in the Blueprint for Continuous Delivery and DevOps for Oracle.
Dev Ops and Oracle
Many enterprises in Finance, Utilities, Government, Retail and Transport choose Oracle for their integrated technology solutions. Yet, many of these deployments are diverse and complex, making the achievement of both Continuous Delivery and DevOps a real challenge.
In Oracle deployments, the need for automation is high, especially as complex deployments may have 50 to 100 Oracle application assets deployed, using many distinct Oracle products and hundreds of clusters across multiple environments. Managing these to deliver capabilities to business users rapidly with reduced failure rates would be impossible without automation. Read more in the Blueprint for Continuous Delivery and DevOps for Oracle.
Dev Ops tools
Smart enterprises are automating everything - including the provisioning of infrastructure, databases, middleware and applications - and look for the flexibility to do so either on premise or in the cloud, or in a hybrid of both.
Smart tools for Dev Ops and Continuous Delivery should enable you to:
- Build & configure complex environments in hours
- Provision & manage high availability, clustered environments on demand
- Configure environments once and build them the same way each and every time
- Design environments via a simple user interface
- Use pre-defined pattern templates, or easily design and configure your own
- Deploy your infrastructure, databases, middleware and applications where you want them, including public or private clouds, hybrid clouds or in a mix of cloud and on-premise scenarios - giving you real power & choice.
Find out more in the Blueprint for Continuous Delivery and DevOps for Oracle.
Smart tools for Dev Ops
Automating the building of complex Oracle environments is one thing; maintaining them efficiently is quite another. So is real-time trouble-shooting to ensure high availability.
The smartest diagnostic toolsets enable easy maintenance and trouble-shooting, with advanced capabilities via real-time dashboards:
- Deploying and verifying configuration change and measuring configuration drift
- Preventing configuration drift
- Managing user-induced changes to environments
- Detecting and preventing failures before they happen
- Eliminating inconsistencies between environments, and instability
- Harvesting configurations from existing environments and moving them back to the CD product to produce identical builds.
Real-time diagnostics provide even greater value, if they can also:
- Be used in manually-built environments
- Be used for Oracle and non-Oracle deployments
- Enable export of detailed technical configuration reports for distribution and remediation by BAU.
Learn more about LimePoint’s smart suite for Continuous Delivery and DevOps for Oracle called EnvironMint.