http://cloudvane.net/wp-content/uploads/2023/02/cloudvane_72px.png 0 0 Mario Meir-Huber http://cloudvane.net/wp-content/uploads/2023/02/cloudvane_72px.png Mario Meir-Huber2013-01-17 11:33:282013-01-17 11:33:28Resource Automation in the Cloud: Datacenter Automation and Integration
This is the last post on our series about resource automation in the Cloud. Today, we will look at datacenter automation and integration.
What are the Benefits for Data Center Automation? First of all, it frees up IT staff. If more things are automated, you don’t need to allocate resources for that. Your IT can care about more important things. You should automate things that are repeatable, such as provisioning machines.
With Data Center Integration, you leverage best capabilities of
- Existing systems
Key areas for Datacenter Automation are:
- Reducing labor costs by allowing reduction or reallocation of people
- Improving service levels through faster measurement and reaction times
- Improving efficiency by freeing up skilled resources to do smarter work
- Improving performance and availability by reducing human errors and delays
- Improving productivity by allowing companies to do more work with the same resources
- Improving agility by allowing rapid reaction to change, delivering new processes and applications faster
- Reducing reliance on high-value technical resources and personal knowledge
A key driver for Datacenter Integration and Automation is SOA (Service Oriented Architectures). This allows much better integration of different services all over the datacenter. Drivers for Integration are:
- Flexibility. Rapid response to change, enabling shorter time to value
- Improved performance and availability. Faster reactions producing better service levels
- Compliance. Procedures are documented, controlled and audited
- Return on investment. Do more with less, reduce cost of operations and management
If you decide to automate tasks in your datacenter, there are some areas where you should start:
- The most manual process
- The most time-critical process
- The most error-prone processes
Once these 3 processes are identified, enterprises should
- Break donw high-level processes into smaller, granular components
- Identify where lower-level processes can be „packaged“ and reused in multiple high-level components
- Identify process triggers (e.g. End-user requests, time events) and end-points (e.g. Notifications, validation actions
- Identify linkages and interfaces between steps of each process
- Codify any manual steps wherever possible
Leave a ReplyWant to join the discussion?
Feel free to contribute!