Professional Documents
Culture Documents
DC Automation 2
DC Automation 2
Are you?
reduce downtime
Executive summary
IT departments have been working on automation for a long time. However, the
results have fallen short of expectations. While individual areas may have good
automation, whether through point solutions or custom development, overall
processes often require manual tasks or significant scripting to join disparate pieces
together. As a result, IT departments are forced to operate in fire-fighting mode,
rushing from emergency to emergency without time to focus on strategic tasks and
goals. Even simple questions require significant effort and expertise to answer.
REAL-WORLD RESULTS
Cisco Media Services reduced the time to
provision servers from 24 hours to 20-25
minutes.
The result is a lack of efficiency in the data center, which can lead to outages and
downtime. Compliance audits often cover only a portion of the IT estate. Whats more,
documentation is incomplete and time-consuming to generate, and remediation
efforts are hampered by disconnected processes. Communication across teams is
inefficient, frequently working only thanks to informal relationships. All this makes it
very hard for managers to base their decision-making on the real state of IT.
BMC has extensive experience in automating data center configuration management
tasks across physical, virtual, and cloud-based systems. This experience has been
codified into mature solutions that have been tested by some of the worlds most
demanding IT organizations. BMCs Data Center Automation solutions are structured
around three fundamental areas of value:
Learn: View the state of IT in real time, compare configurations to each other, and
automate repetitive configuration management tasks
Resolve: Identify drift from desired state, audit regularly for compliance to policies,
and remediate discrepancies automatically
Business challenge
As ITs role in the business increases and demands placed on it continue to grow old models are
falling short of satisfying requirements. Where manual tasks, homegrown scripts, and the occasional
point solution might have been enough to keep the lights on in the data center in the past, new
expectations of agility, flexibility, and cost savings have made that model obsolete. Businesses expect a
rapid and reliable turnaround on requests for IT support. Complex and diverse IT infrastructures, different
teams operating without strong communications and processes, and increased requirements make
operating a data center far from a solved problem.
Learn
Change is a constant and nowhere more so than in a data center. This means that the first task is to
understand the real-time state of IT. Analyzing live configurations, you can eliminate the delays that
traditionally occur while a reference database is updated or a discovery process is executed. Whats more,
because BMC Data Center Automation solutions work on actual configurations, regardless of how they are
applied, these solutions can co-exist with your existing tools or even with manual actions. This helps
adoption enormously by avoiding discontinuities and disruptions in working processes.
Once a live view is achieved, it is important to be able to compare configurations, whether between
different members of the same group (these two systems should be the same, but they behave
differently) or over time (it was working yesterday, what changed?). These are the sorts of repetitive
actions that traditionally have consumed an enormous amount of IT personnels time.
Finally, it is necessary to deploy new configurations without requiring manual connections to each
system or new scripts for each task. Repetitive actions (add a user, edit a configuration file, change
permissions on a folder, restart a service, etc.) are individually small, but together take up a significant
proportion of IT staffs time with frustrating tasks that interrupt more strategic work.
Resolve
The pace of change is increasing as business expectations of IT become more sophisticated and more
frequent. The first step to change management, therefore, is to identify changes. To do so, a reference
configuration is needed. This might be a live reference environment, an historical snapshot of the
environment when it was in a known good state, or a policy configuration that reflects security baselines,
operational best practices, or industry-standard policies, such as Sarbanes-Oxley or PCI. The changes
need to be identified in sufficient detail to avoid both false positives and false negatives.
Compliance to the desired state is a process, not an event. Even if the system starts out compliant, it
will inevitably drift from that initial state as various manual and automated changes occur. For example,
components are restarted or updated, users are created or deleted, patches are applied, and so on. That
means that regular audits need to be performed against all applicable systems. The targets of an audit
might be static or dynamic, meaning either a fixed list or a group defined according to certain properties
(all systems in the DMZ or all systems with component X).
To be effective, compliance needs to encompass more than just audits. An audit will almost always
unearth discrepancies differences from the expected and desired configuration. Trying to fix those
by hand is not only time-consuming, but also requires documentation updates to ensure that the issue
was resolved and the system is now compliant not to mention the possibility that new errors might be
introduced by accident during the remediation process. Automated remediation is the way to avoid this
vicious cycle, enabling administrators to bring configurations into compliance with one click. Of course,
not all configurations can or should be identical, so support for documenting temporary or permanent
exceptions is also needed. These exceptions can then be taken into account for subsequent audits,
avoiding over- or under-reporting of compliance violations.
Control
As your processes become more automated, greater control is needed. Many organizations already
have best practices in place, and now need only integrate those best practices into the newly automated
internal IT processes. Discrepancies can be automatically documented as incidents, creating audit trails for
routine events, without requiring manual action by IT staff. Change and maintenance windows also can be
enforced automatically, and related changes can be managed together, avoiding collisions and conflicts.
To ensure full coverage of the change process, automatic change requests are created without
requiring user action to ensure that all changes have an associated record. Routine changes can be
Key Benefits
Reduce the unit cost of IT
Avoid security breaches and
outages due to configuration
errors
Increase and document
compliance levels, avoiding
penalties
BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the
U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks,
service marks, and logos may be registered or pending registration in the U.S. or in other countries. IBM and z/OS are the
trademarks or registered trademark of International Business Machines Corporation in the United States, other countries, or
both. All other trademarks or registered trademarks are the property of their respective owners. 2007, 2010, 2012 BMC
Software, Inc. All rights reserved. Origin date: 1/10
*403704*
Learn more
With deep roots in automation of servers,
network devices, and databases and
market-proven experience BMC can help you
address both your immediate and long- term
data center automation goals. To learn more,
please visit www.bmc.com/automation.