Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-17 Thread Tim Hinrichs
implementation (of a policy) read it in directly? Ruby De : Tim Hinrichs [mailto:thinri...@vmware.com] Envoyé : jeudi 12 février 2015 19:03 À : OpenStack Development Mailing List (not for usage questions) Objet : Re: [openstack-dev] [Congress][Delegation] Google doc for working notes Hi Debo and Yathiraj

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-16 Thread ruby.krishnaswamy
2015 19:03 À : OpenStack Development Mailing List (not for usage questions) Objet : Re: [openstack-dev] [Congress][Delegation] Google doc for working notes Hi Debo and Yathiraj, I took a third look at the solver-scheduler docs and code with your comments in mind. A few things jumped out. 1

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-13 Thread Debojyoti Dutta
Tim Wanted to clarify a bit. As I have mentioned before: Solver scheduler is work done before this work (Datalog-constraints) but we had kept it very generic to be integrated with something like congress. In fact Ramki (who was one of the members of the original thread when you reached out to

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-13 Thread ruby.krishnaswamy
modelling language (e.g. PuLP). So this is likely to be a major change to the scheduler? Ruby De : Debojyoti Dutta [mailto:ddu...@gmail.com] Envoyé : vendredi 13 février 2015 14:06 À : OpenStack Development Mailing List (not for usage questions) Objet : Re: [openstack-dev] [Congress][Delegation

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-13 Thread Tim Hinrichs
Hi Debo and Yathi, We’re completely on the same page here. We’ve known about the solver-scheduler for a while now (I even attended your Atlanta talk), and I always expected Congress would integrate with it. As you say, now it’s a matter of getting down to the details. A bit on the context…

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-13 Thread Yathiraj Udupi (yudupi)
Hi Tim, Glad to collaborate and work towards nailing down the details. Yeah in terms of policy enforcement from Congress, it makes sense to delegate to domain-specific policy engines. It will be good to go through this PoC and to start thinking about the integration points of Congress with

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-12 Thread Yathiraj Udupi (yudupi)
Hi Tim, Thanks for your response. Excited too to extend the collaboration and ensure there is no need to duplicate effort in the open source community. My responses inline. 1) Choice of LP solver. I see solver-scheduler uses Pulp, which was on the Congress short list as well. So we’re

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-12 Thread Tim Hinrichs
Hi Debo and Yathiraj, I took a third look at the solver-scheduler docs and code with your comments in mind. A few things jumped out. 1) Choice of LP solver. I see solver-scheduler uses Pulp, which was on the Congress short list as well. So we’re highly aligned on the choice of underlying

[openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-11 Thread Tim Hinrichs
Hi all, A (growing) group of folks are interested in working on the problem of delegating policy from Congress to domain-specific policy engines. We started looking at an NFV use case: migrating VMs to reduce energy consumption. In particular we’re looking into building a VM-placement policy

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

2015-02-11 Thread Debojyoti Dutta
Hi Tim: moving our thread to the mailer. Excited to collaborate! From: Debo~ Dutta dedu...@cisco.com Date: Wednesday, February 11, 2015 at 4:48 PM To: Tim Hinrichs thinri...@vmware.com Cc: Yathiraj Udupi (yudupi) yud...@cisco.com, Gokul B Kandiraju go...@us.ibm.com, Prabhakar Kudva