[openstack-dev] [NFV] - follow up on scheduling discussion
Yathiraj Udupi (yudupi)
yudupi at cisco.com
Tue Jun 10 16:09:12 UTC 2014
In our current implementation of Smart (Solver) Scheduler, the constraints are defined as pluggable modules (just like filter definitions in the filter scheduler) and are pulled in together when necessary to solve the scheduling decision. And regarding the data that we get from different services in storage (cinder) , network and so on, we are currently using their clients to directly get the data to use along with the constraints.
I believe a policy implementation can specify which constraints to use and which data. So the data can potentially be saved in the individual services.
The Gantt project is also planning to have internal DB which will be used for scheduling. That is another option where the unified data can be, when we want to do unified scheduling that we describe in our Smart scheduler project.
I will open to explore options as to where Congress will fit in here, but currently I feel it is one layer above this.
Sent from my LG G2, an AT&T 4G LTE smartphone
------ Original message------
From: Tim Hinrichs
Date: Tue, Jun 10, 2014 8:27 AM
To: OpenStack Development Mailing List (not for usage questions);
Cc: Norival Figueira;Debo Dutta (dedutta);
Subject:Re: [openstack-dev] [NFV] - follow up on scheduling discussion
I see that many of the use cases require information from different OS components, e.g. networking, compute, and storage. One thing to think about is where those constraints are written/stored and how the data the constraints depend on is pulled together. The Congress project might be helpful here, and I’m happy to help explore options. Let me know if you’re interested.
On Jun 4, 2014, at 11:25 AM, ramki Krishnan <ramk at Brocade.com> wrote:
> Thanks for the interest in the NFV scheduling topic. Please find a proposal on "Smart Scheduler (Solver Scheduler) enhancements for NFV: Use Cases, Constraints etc.". https://urldefense.proofpoint.com/v1/url?u=https://docs.google.com/document/d/1k60BQXOMkZS0SIxpFOppGgYp416uXcJVkAFep3Oeju8/edit%23heading%3Dh.wlbclagujw8c&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=%2FZ35AkRhp2kCW4Q3MPeE%2BxY2bqaf%2FKm29ZfiqAKXxeo%3D%0A&m=vTulCeloS8Hc59%2FeAOd32Ri4eqbNqVE%2FeMgNRzGZnz4%3D%0A&s=836991d6daab66b519de3b670db8af001144ddb20e636665b395597aa118538f
> Based on this proposal, we are planning to enhance the existing solver-scheduler blueprint https://urldefense.proofpoint.com/v1/url?u=https://blueprints.launchpad.net/nova/%2Bspec/solver-scheduler&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=%2FZ35AkRhp2kCW4Q3MPeE%2BxY2bqaf%2FKm29ZfiqAKXxeo%3D%0A&m=vTulCeloS8Hc59%2FeAOd32Ri4eqbNqVE%2FeMgNRzGZnz4%3D%0A&s=d1883d82f8d09081b35986987b5f2f9f1d7731f16b2a5251fdbf26c1b26b294d.
> Would love to hear your comments and thoughts. Would be glad to arrange a conference call if needed.
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev