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

2015-02-16 Thread ruby.krishnaswamy
Hi Tim What I'd like to see is the best of both worlds. Users write Datalog policies describing whatever VM-placement policy they want. If the policy they've written is on the solver-scheduler's list of options, we use the hard-coded implementation, but if the policy isn't on that list we

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

2015-02-13 Thread ruby.krishnaswamy
Hello Debo/Tim My understanding is that with Congress things like filters (e.g. anti-affinity or other aggregates) will be replaced to be written as policies with Datalog. Goals (a Policy), Constraints (policies in Congress) will also get translated to (for example) linear programs in some

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

2015-03-18 Thread ruby.krishnaswamy
Hello o) custom constraint class What did you mean by the “custom” constraint class? Did you mean we specify a “meta model” to specify constraints? And then each “Policy” specifying a constraint ( ) will lead to generation of the constraint in that meta-model. Then the solver-scheduler

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

2015-03-17 Thread ruby.krishnaswamy
Hi I'd like to participate. By when will you fix the meeting date ? Ruby De : Tim Hinrichs [mailto:thinri...@vmware.com] Envoyé : lundi 16 mars 2015 19:05 À : OpenStack Development Mailing List (not for usage questions) Objet : [openstack-dev] [Congress] [Delegation] Meeting scheduling Hi all,

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

2015-02-27 Thread ruby.krishnaswamy
My first suggestion: why don’t we set up call together with Ramki, Yathi, Debo, as soon as possible ? - How to go forward concretely with the 8 steps for the PoC (details within each step), oIncluding nova integration points - Identify “friction points” in the details

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

2015-02-26 Thread ruby.krishnaswamy
Tim:“So you’re saying we won’t have fresh enough data to make policy decisions? If the data changes so frequently that we can’t get an accurate view, then I’m guessing we shouldn’t be migrating based on that data anyway.” Ramki: We have to keep in mind that VM migration could be an expensive

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

2015-02-25 Thread ruby.krishnaswamy
Hi Tim, All, 1) Step 3: The VM-placement engine is also a datalog engine . Right? When policies are delegated: when policies are inserted? When the VM-placement engine has already registered itself all policies are given to it? In our example, this would mean the domain-specific

Re: [openstack-dev] [Murano][Congress] Application placement use case

2015-07-01 Thread ruby.krishnaswamy
Hi Did you mean placement at “two levels”. First to select the region and then within each region, Nova scheduler will place on hosts. But where will the capabilities of each region (based on which placement decision will be made) be stored? Will each region be queried to obtain this