Intelligent workload management

Intelligent workload management (IWM) is a paradigm for IT systems management arising from the intersection of dynamic infrastructure, virtualization, identity management, and the discipline of software appliance development.[1] IWM enables the management and optimization of computing resources in a secure and compliant manner across physical, virtual and cloud environments to deliver business services for end customers.

The IWM paradigm builds on the traditional concept of workload management whereby processing resources are dynamically assigned to tasks, or "workloads," based on criteria such as business process priorities (for example, in balancing business intelligence queries against online transaction processing[2]), resource availability, security protocols, or event scheduling, but extends the concept into the structure of individual workloads themselves.

Definition of "workload"

In the context of IT systems and data center management, a "workload" can be broadly defined as "the total requests made by users and applications of a system."[3] However, it is also possible to break down the entire workload of a given system into sets of self-contained units. Such a self-contained unit constitutes a "workload" in the narrow sense: an integrated stack consisting of application, middleware, database, and operating system devoted to a specific computing task. Typically, a workload is "platform agnostic," meaning that it can run in physical, virtual or cloud computing environments. Finally, a collection of related workloads which allow end users to complete a specific set of business tasks can be defined as a "business service."[4]

Making workloads "intelligent"

A workload is considered "intelligent" when it a) understands its security protocols and processing requirements so it can self-determine whether it can deploy in the public cloud, the private cloud or only on physical machines; b) recognizes when it is at capacity and can find alternative computing capacity as required to optimize performance; c) carries identity and access controls as well as log management and compliance reporting capabilities with it as it moves across environments; and d) is fully integrated with the business service management layer, ensuring that end user computing requirements are not disrupted by distributed computing resources, and working with current and emergent IT management frameworks.

Intelligent workloads and security in the cloud

The deployment of individual workloads and workload-based business services in the "hybrid distributed data center,"[5] - including physical machines, data centers, private clouds, and the public cloud - raises a host of issues for the efficient management of provisioning, security, and compliance. By making workloads "intelligent" so that they can effectively manage themselves in terms of where they run, how they run, and who can access them, intelligent workload management addresses these issues in a way that is efficient, flexible, and scalable. The 1989 seminal work by D.F. Ferguson, Y. Yemini, and C. Nikolaou "Microeconomic Algorithms for Load Balancing in Distributed Computing Systems" developed a theory by which workloads could be made "intelligent" to manage themselves.[6] This theory has since been patented and was commercialized by the Boston-based company, VMTurbo, in 2009.

gollark: Really, users are the weakest point of lots of technological stuff.
gollark: I've heard of that and vaguely looked at using it, but the server stuff still seems very WIP.
gollark: Although Discord has giant servers now, so good luck leaving without missing tons of stuff!
gollark: If you want to move off Facebook you'll probably worry about losing contact with 293848 people you don't have anywhere else, if you want to move off Skype you might just have something like 5 people in a group with you.
gollark: It mostly doesn't happen unless the existing stuff is also very bad. I suspect it's also easier for somewhat purpose-specific instant messaging than for general social network stuff because the group which has to move with you is smaller and you don't have to migrate giant friend lists or something.

See also

References
  1. Thomas Mendel (October 26, 2009). "IT Management Software Market Update". Forrester. Archived from the original on December 25, 2009. Retrieved 2017-01-10. ...a particularly exciting new category, which we tentatively call process and workload automation, some vendors refer to it as intelligent workload management.
  2. "Dynamic workload management for very large data warehouses: juggling feathers and bowling balls". VLDB Endowment. 2007. Retrieved 2008-11-12.
  3. "What Is Your Definition of Database Workload?". Database Journal. January 8, 2009. Retrieved 2009-11-15.
  4. "IT Services, Business Services, Services...what's next?". HP ITIL v3 Community Blog. March 3, 2008. Retrieved 2009-11-15.
  5. "The Hybrid Distributed Data Center -er- Cloud?". Sun Microsystmes. October 1, 2009. Archived from the original on October 4, 2009. Retrieved 2009-11-15.
  6. Ferguson, D.F.; Yemini, Y.; Nikolaous, C. (1988). "Microeconomic algorithms for load balancing in distributed computer systems". Microeconomic Algorithms for Load Balancing in Distributed Computing Systems. Washington, D.C.: IEEE Computer Society Press. pp. 491–499. doi:10.1109/DCS.1988.12552. ISBN 0-8186-0865-X.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.