Saturday, 13 May 2017
Free Minecraft Premium
Free Minecraft Premium: I just got a free redeem code from this site http://minecraftupgrade.com
Tuesday, 3 March 2015
Comparison of top DevOps tools (Pros and Cons)
|
Tools
|
Puppet
3.0
|
Chef
11.4
|
Ansible
1.3
|
Salt
0.17
|
|
Pros
|
Modules can be written in Ruby.
Web UI handles reporting,
inventorying, and real-time node management
|
Cookbooks and recipes can
leverage Ruby
Centralized JSON-based
"data bags" allow scripts to populate variables during runtime
Web UI lets you search and
inventory nodes, view node activity, and assign Cookbooks, roles, and nodes.
|
Modules can be written in any lang.
No agent required on managed
clients.
Web UI lets you configure
users, teams, and inventories, and apply Playbooks to inventories.
Extremely simple to set up and
manage
|
State files can be simple configuration
templates or complex Python or PyDSL scripts.
Can communicate with clients
through SSH/local agent
Web UI offers views of running
jobs, minion status, and event logs, execute commands on clients
Extremely scalable.
|
|
Cons
|
Requires learning Puppet DSL or Ruby
Installation process lacking in error checking and error
reporting
|
Requires knowledge of Ruby programming
Currently lacks functional push commands
Documentation is sometimes vague
|
Lacks support for Windows clients
Web UI doesn't tie into an existing Ansible deployment
automatically; inventories must be imported
|
Web UI is not as mature or complete as competitors
Lacks deep reporting capabilities
|
|
Pricing
|
Free open source version;
Puppet Enterprise costs $100 per machine per year
|
Free
open source version; Enterprise Chef free for 5 machines, $120 per month for
20 machines, $300 per month for 50 machines, $600 per month for 100 machines,
and so on
|
Free open source version; AWX
free for 10 machines, then $100 or $250 per machine per year depending on
support
|
Free open source version;
SaltStack Enterprise costs $150 per node per year, with volume discounts and
site licenses available
|
Thursday, 19 February 2015
Survey: Nearly Everybody Will be Using DevOps by End of 2015
DevOps adoption is expected to reach 93 percent by
the end of 2015, according to a new survey commissioned byRackspace. A
big portion of that number consists of respondents who have already implemented
DevOps practices (66 percent), with more than a quarter of respondents planning
to implement DevOps by the end of the year. A significant majority (close to 80
percent) of respondents are using some sort of outsourced DevOps services, a
key finding for providers that have services that help customers use DevOps
tools and practices, such as Rackspace.
DevOps combines many of the roles of systems
administrators and developers. It is a set of principles driving greater
collaboration between the different groups responsible for taking a product or
service to market. IT automation products are DevOps tools, and agile software
development is the cornerstone of DevOps, as the overall environment is
becoming more dynamic. Major technology shifts of Internet business and
collaboration technologies, open source software, and cloud computing are
prompting the shift.
Rackspace has reason
to both commission the survey and tout the results. It has been building up its DevOps services, and the survey
supports this strategy. The Texas company has focused on managed services for
cloud in order to distance itself from other cloud infrastructure service
providers.
It’s known for its “Fanatical Support,” a message and philosophy
the company is evolving for the cloud services world. Fanatical support extended to DevOps and automation last year, and 18 new
services were launched this year. DevOps Automation is the highest tier of
managed services.
Vanson Bourne performed the study, interviewing
around 700 IT decision makers across the U.S., U.K., and Australia. The key
takeaways, according to Chris Jackson, CTO of DevOps at Rackspace, are that the
operations team is the primary driving force behind the change to DevOps, and
customer satisfaction is the biggest benefit.
Given that DevOps is still in its infancy, such high
penetration is almost hard to fathom. It is also hard to capture the maturity
and stage of a company’s DevOps transition. The survey does examine which
DevOps practices have been implemented, with half saying that development and
operations teams have been fully integrated, suggesting mature DevOps adoption:
A granular breakdown
of how DevOps is being executed across the organization, courtesy of Rackspace
The survey shows
that DevOps is important, almost all companies strategizing how to move to this
approach. The key priority for future implementations is to align DevOps goals
with business goals. “The results of the DevOps Adoption Study validate that there is
significant recognition among global businesses that DevOps is fundamental to
fully exploiting the cloud in the pursuit of driving rapid innovation,” said Prashanth
Chandrasekar, GM of Rackspace’s DevOps Business .
What’s
the big deal about DevOps?
The biggest business benefit of switching to DevOps
is the increase in customer satisfaction (over 60 percent), according to the
survey. Other benefits include a reduced spend on IT infrastructure and a
reduction in application downtime or failure rates, cited by about half of
respondents as the biggest benefits. One third reported increase in sales and
employee engagement as the benefits.\
Over 700 IT decision
makers breakdown the IT benefits of DevOps (Source: Rackspace)
“Through cultural alignment,
automated deployments, and agile infrastructure, businesses are using DevOps
methodologies to reduce time to market by responding rapidly to customer feedback — ultimately driving significant
business value and efficiency,” said Chandrasekar.
The technical benefits of DevOps are faster delivery
of new features, a more stable operating environment, increased innovation, and
better collaboration.
Monday, 19 January 2015
DevOps implementation
- Scoping - Define a clear scope of what you intend to put under the DevOps services umbrella. Also which applications would you want to start with at the outset. A phased approach with a smaller non business critical application is the way to go about it as opposed to the Big Bang approach.
- Human Resource - You may want to start with your star performer of course but make sure that he has these three most important skills : scalable and flexible, promptness and process orientation. Also, the most ideal candidate for your DevOps core team would be a system admin with good scripting/automation skills or the agile-admin as they are more popularly called today.
- Process framework - Whether you want to start with ITIL first and then integrate agile/scrum into the process or vice-versa. This is very important so as to prioritize from the inception so that right processes can be tweaked based on ITIL principles or agile methodology.
- Defining KPI's - Changing the KPI's like MTTR and MTBF has to be revisited and new metrics should be defined, implemented and measured. .This measurement is key to understanding the business and operations benefits that the company achieves with DevOps implementation.
- Automate - Automation through tools and scripts is one of the key tenets of DevOps. The sole objective of DevOps is to achieve Quality @ the speed of delivery which requires processes to be automated and applying lean methodology by eliminating redundant processes.
It is very imperative that the team is educated of the culture of continuous testing, integration and delivery which is built into the process to achieve the expected efficiency from DevOps implementation.
Monday, 22 December 2014
DevOps ..contd
DevOps
is soon getting synonymous with management of IT automation. DevOps is more of an organization’s culture
than the actual process. It is a stronger collaboration between developers
and operations engineers. Developers are expected to turnaround new
developments faster and operations engineers are expected to maintain up-time by following a set of defined processes. While change is the daily routine of Developers, for the operations engineer it is an absolute alien (more of 'follow the process').
DevOps predominantly
is an extension of Agile methodology. In layman’s term, it would mean putting a system administrator in the agile development process. On the ground, it
involves a lot of coordination between teams where tools play a very important
role in streamlining communication, documentation and tracking. These tools are
used for app/infra automation like automating the testing process, deployment and release process, change process, etc., as described below:
Change Management
Objective: To enable beneficial changes to be made, with minimum
disruption to IT services.
Release & Deploy Management
Objective: To plan, schedule and control the movement of releases
to test and live environments.
Incident Management
Objective: The primary objective of Incident Management is to
return the IT service to users as quickly as possible.
Knowledge Management
Objective: The primary purpose of Knowledge Management is to
improve efficiency by reducing the need to rediscover knowledge.
Commonly used tools:
Automation: Puppet, Chef, CFEngine, Ansible,
Salt Stack, Docker
Functional
Testing: Cucumber,
QTP, Rational, Selenium, Visual Studio Test Professional
Configuration Testing:
ScriptRock
Continuous Integration:
Jenkins, Travis CI, Ant, Circle CI
Continuous
delivery:
IBM Tivoli
Content Management
System: SharePoint, Wiki, Joomla.
Monitoring
and graphical analysis: Nagios, NewRelic,
Ganglia, iperf, AWS
While ITIL develops process culture in an organization and brings process maturity, agile helps in accelerating the processes ensuring faster time to market. With the right process combination and marriage of ITIL with agile, an organization can reap the benefits of speed and improved customer satisfaction; which the industry today has termed as " DevOps".
Tuesday, 4 November 2014
Friday, 16 May 2014
Defining Priorities
It is customary that Priority of issues
has four to five levels. It is most commonly marked with the numbers 1-4 or 1-5,
where "1" is the highest and "4/5" is the lowest priority.
PRIORITY = IMPACT X URGENCY .
Below is how the ITIL priority matrix looks like:
·
Impact - Is defined by the criticality of downtime is
for the business. Usually measured by the number of users affected. For e.g.: If
one or more application/ services are down.
·
Urgency - it is usually defined in SLA for the
specific IT service. If more than one service is impacted, parameters for the
higher urgency service will be taken into account.
Friday, 4 April 2014
Managing SLA’s using COBIT
Objectives:
Objective 1: SLA framework: Management
should define a framework to promote the definition of formal SLAs. Define the
minimal contents such as availability, reliability, performance, capacity for
growth and levels of support provided to users. Users and IT function should
have a written agreement that describes service level in qualitative and
quantitative terms and responsibilities of both parties.
Objective 2: Aspects of SLAs: Explicit
agreement should be reached on the aspects that an SLA should cover (e.g.,
availability, reliability and performance).
Objective 3: Performance procedures: Management
should implement procedures to ensure that the manner and responsibilities for performance
governing relations between all the involved parties are established,
coordinated, maintained and communicated to all departments.
Objective 4: Monitoring and reporting: A service
level manager should be appointed for monitoring and reporting on the
achievement of the specified service performance criteria and all problems
encountered during processing.
Objective 5: Review of SLAs and contracts: A regular
review process for SLAs and underpinning contracts with third-party service
providers should be in place.
Objective 6: Chargeable items: Management
should include provisions for chargeable items in the SLAs
(Rewards and Penalties)
Objective 7: Service improvement program: A process
to ensure that users and service level managers regularly agree on a service
improvement program for pursuing cost-justified improvements.
Maturity levels:
|
Maturity
Level
|
State
|
Indicators
|
|
0
|
Nonexistent
|
Management
has not recognized the need for a process for defining service levels.
|
|
1
|
Initial/ad
hoc
|
There is
an awareness of the need to manage service levels, but the process is
informal.
|
|
2
|
Repeatable
and intuitive
|
There
are agreed-upon service level agreements, but they are informal and not
revised. Service level reporting is incomplete.
|
|
3
|
Defined
process
|
The
service level agreement process is in place with checkpoints for reassessing
service levels and customer satisfaction.
|
|
4
|
Managed
and measurable
|
Performance
measures are increasingly reflecting end-user needs, rather than only IT
goals.
|
|
5
|
Optimised
|
Service
levels are continuously reevaluated to ensure alignment of IT and business
objectives.
|
Tuesday, 25 March 2014
Friday, 14 March 2014
ITIL metrics (KPI's for Configuration Management):
Following are ITIL V3 key performance indicators for configuration management:
- Percentage improvement in maintenance scheduling over the life of an asset
- Degree of alignment between provided maintenance and business support
- Assets identified as the cause of service failures
- Improved speed for incident management to identify faulty CIs and restore service
- Impact of incidents and errors affecting particular CI types
- Percentage reuse and redistribution of under-utilized resources and assets
- Ratio of used licences against paid for licences (should be close to 100%)
- Achieved accuracy in budgets and charges for the assets utilized by each customer or business unit
- Percentage reduction in business impact of outages and incidents caused by Configuration Management
- Average cost per user for licences
- Improved audit compliance
Wednesday, 5 March 2014
ITIL metrics (KPI's for Problem Management) :
Following are ITIL V3 key performance indicators for problem management:
- Total number of problems recorded in the period
- Percentage of problems resolved within SLA targets; percentage not resolved within SLA targets
- Number and percentage of problems that exceed target resolution times
- Backlog of existing problems and the trend
- Number of major problems, including opened, closed, backlog
- Percentage of Major problem Reviews successfully performed
- Number of Known Errors added to the KEDB
- Percentage accuracy of the KEDB (from audits of the database)
- Percentage of Major problem Reviews completed successfully and on time
- Average cost of handling a problem
Friday, 28 February 2014
ITIL metrics (KPI's for Change Management) :
Following are ITIL V3 key performance indicators for change management:
- Number of changes implemented to services that met customer requirements (for e.g. quality/cost/time as a percentage of all changes)
- Reduction in the number of disruptions to services, defects, and rework caused by inaccurate specification, and poor or incomplete impact assessment
- Reduction in the number of unauthorized changes
- Reduction in the backlog of change requests
- Reduction in the number and percentage of unplanned changes and emergency fixes
- Change success rate (percentage of changes successful; i.e. number of RFCs approved)
- Reduction in the number of changes in which remediation is required
- Reduction in the number of failed changes
- Average time to implement based on urgency/priority/change type
- Incidents attributable to changes
- Benefits of change expressed as the value of improvements made or value of negative impacts prevented or terminated as compared with the costs of the change process
Friday, 21 February 2014
ITIL metrics (KPI's for Incident Management)
Following are ITIL V3 key performance indicators for incident management:
- Total number of incidents ( Measurement for control)
- Breakdown of incidents at each stage (for example, logged, work in progress, and closed)
- Current incident backlog
- Number and percentage of major incidents
- Average time to achieve incident resolution
- Percentage of incidents handled within target response time; incident response-time targets may be specified in SLA's, for example, by impact and urgency codes
- Average cost per incident ( To be measured against the cost investment such as tool, infra, people etc. against the invoices generated for the group for a given period of time.
- Number of incidents reopened and as a percentage of the total
- Number and percentage of incidents escalated/ routed (wrong assignment)
- Number and percentage of incidents incorrectly categorized
- Breakdown of incidents by time of day (for effective workforce planning and scheduling)
Tuesday, 4 February 2014
Friday, 31 January 2014
ITIL myths busted
Let us use this post and try to defy the logic of "seeing
is believing", to a certain extent, if not completely. What we see
around us in our day to day life may build few perceptions and most of the
times they are not "facts". The below post tries to bust the
top myths about ITIL and why they do not qualify to be called "facts".
# 1: ITIL is for the "Tech Savvy"
If ITIL is implemented with an inclination towards only IT, then
there are fairly high chances that the return on investment in terms of time
and money is not worthwhile. When business objectives (pre-implementation
of ITIL) are defined, both IT as well as business aspects should be thoroughly
chalked out.
So, though the operational people are the ones who would
eventually implement/ practice ITIL , yet the management buy-in plays a vital
role in the success and eventual ROI. The strategy phase in ITIL V3 which
discusses in detail about the various processes are generally governed by the
executive (non-technical) staff of an organization. Also, the CSI phase that
cuts across all the other 4 phases in Version 3 revolves around continuous
improvement and is more inclined towards improvements than technology.
# 2: By following ITIL processes, I will automatically get
the results I want.
ITIL will give you the guidelnes of best or good practices that
are supposed to be followed to derive maximum returns out of your investments
in terms of process maturity, customer satisfaction, cost savings, revenue
generation etc. The important aspect to remember here is that the desired
outcome should dictate the process and not the other way around.
Moreover, the process must achieve the desired results in an efficient
manner; else you may want to have a relook at redesigning the process or
changing it to achieve the desired results.
# 3: ITIL training will reap benefits for my organization
By now, you would have read on the internet that there
are plethora of companies who have trained their employees on ITIL
but have not realized its benefits to the optimum. The reasons behind
this, as one would see is,
·
No
concrete business objective or direction
·
Lack
of management involvement
·
Lack
of measurement and metrics
There is no ready to use recipe to realize maximum benefit
out of ITIL implementation. The ways to realize the benefits (stated in
myth # 1 above) to the optimum would vary from organization to organization.
Apart from ITIL education, few others aspects that should be built in to obtain
the desired result are management buy in, clear objectives/ goals, developing
the process culture (preparation for change), integrating processes,
reviews, audits etc
So seeing may not always be believing but doing certainly is.
Sunday, 26 January 2014
ITIL V3 2011 Edition compared with 2007 edition
For those who may not be aware, ITIL had undergone a
review and the “ITIL V3 2011 edition” was released on 29 July 2011. The good
news is that all the current certified ITIL V3 folks will not have to upgrade
their certifications to the 2011 edition as this is just an update and not an
upgrade (not a new version). Another reason for celebration is that the
fundamental principles and concepts of lifecycle approach of V3 would still
hold good.
Few major changes in the phases that have been
incorporated under the 2011 edition as opposed to the 2007 edition of ITIL V3
are:
·
Service Strategy
o
It contains the newly defined process of strategy management for
IT services. Business strategy and IT strategy are two different topics wherein
business strategy defines IT strategy, and IT strategy supports business
strategy (a more detailed explanation around Business Service Management)
o
Business relationship management and demand management are now covered
as processes in Service Strategy. There are templates that describes each of
the processes making their purposes easy to comprehend.
o
The entire world is taking about Cloud and how can our ITIL not
be affected by it. There are explanations on how cloud impacts ITSM and few
cloud concepts, types and components are also covered in it.
·
Service Design
o
The ‘design coordination’ process has been added to clarify the
flow of activity in the service design lifecycle stage.
o
More clarity on transition of a service from pipeline to
catalogue to retired has been discussed.
·
Service Transition
o
An improved, structured, better interrelationships of the
configuration management system (CMS) and service knowledge management system
(SKMS) have been introduced to help understand the concepts better.
o
The evaluation process has been renamed ‘change evaluation’ with
more clarity on the purpose of how to use this process.
·
Service Operation
o
Clarification on how basic events flow into filters and rule
engines to produce meaningful information has been covered.
o
A new process flow has been introduced suggesting a set of
activities and steps to be followed for the request fulfillment process,
including the decision points for escalating requests to service transition as
change proposals or incident management as incidents.
o
Clarification and difference between Application management and
Application development has been highlighted along with the key activities of
application management in each of the stages.
·
Continual service improvement
o
The concept of a continual service improvement register has been
introduced to record improvement opportunities, categorize them, and identify
effort required and potential benefits. The intention to gather this
information is to determine and prioritize improvement initiatives.
o
CSI model has been renamed to CSI approach as it tasks about an
approach to improvement of an IT service.
Few generic changes across the phases:
Quite interestingly, the 2011 contains lists of
various inputs and outputs of the phases along with examples across the service life-cycle. This definitely makes all the life-cycle phases more cohesive and
helps a user understand how the different life-cycle stages are interrelated.
Please take cognizance that there are quite a lot of
minor changes in the 2011 edition but I have tried to list down all the major
changes that in a way affects the way the ITIL V3 version has been used thus
far.
Subscribe to:
Posts (Atom)





