IBM’s Platform scheduler uses more efficient resource management to enhance on OpenStack’s own scheduler operations.
IBM has launched a proprietary product to work with OpenStack’s resource scheduler, the portion of the cloud software stack that assigns workloads to virtual machine hosts within the cloud.
IBM has a history of mapping out resource schedulers, because of its experience in mainframes and with Tivoli Workload Scheduler LoadLeveler. To boot, the corporate acquired 20-year-old Platform Computing two years ago, adding its Load Sharing Facility to IBM’s scheduler product line.
In making that acquisition, IBM, a supporter of the OpenStack open source code product, is saying unequivocally that OpenStack’s scheduler remains a rudimentary model of the breed and users might want to buy into IBM’s expertise to get the foremost out in their OpenStack clouds.
OpenStack’s scheduler is static, staring at information inside the Nova SQL database before assigning a workload to a server host. (Nova is the provisioning and scheduling element of OpenStack.) However it looks just once, when truly the quantity of labor that applications are doing at the host is continually changing. That results in what Gord Sissons, senior manager of technical marketing manager and a Platform veteran, calls OpenStack’s “Goldilocks problem.” Some hosts running highly active applications become “too hot,” while others with an analogous number are doing less work and are “too cold.”
[Wish to learn more about why OpenStack may well be chosen for personal clouds? See VMware, Mirantis Put OpenStack On vSphere.]
IBM’s Platform Resource Scheduler works on top of OpenStack’s to control workloads in a more dynamic fashion, Sissons explains. “Platform has more of a genuine-time view. It knows a couple of whole set of scheduling metrics that Nova [doesn’t learn about and] ignores.”
Platform can use parallel assignment techniques to distribute workloads over a cluster. When it detects an application is resident on a bunch with too few resources, it moves the virtual machine to a different, less utilized host. It uses VMware’s vMotion, KVM’s Live Motion, or Hyper-V’s Live Migration function to maneuver the running virtual machine.
Once the OpenStack scheduler makes a workload assignment, its view of the job is static — it’s not attempting to find feedback on how hard the server is operating. “It doesn’t consider rescheduling,” Sissons explains.
Platform Resource Scheduler became available in technical preview in November as portion of IBM SmartCloud Orchestrator, IBM’s cloud provisioning software. It’s now available as a separate product that serves as an optional add-directly to Orchestrator or IBM SmartCloud Entry, either one of that are utilized in managing OpenStack clouds. IBM charges for the scheduler in line with what percentage cores it’s running on, however the company declined to give a per-core price with the announcement. Pricing details depend partially at the customer’s implementation, in step with Sissons.
Charles Babcock is an editor-at-large for InformationWeek, having joined the publication in 2003. He’s the previous editor-in-chief of Digital News, former software editor of Computerworld and previous technology editor of Interactive Week.
Private clouds are moving rapidly from concept to production. But some fears about expertise and integration still linger. Also within the Private Clouds Step Up issue of InformationWeek: The general public cloud and the steam engine have more in common than it’s possible you’ll think. (Free registration required.)
More Insights