Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
Hi Tim, I think what you are saying is a reasonable goal in terms of high-level Congress policies not having to depend on the domain-specific solver / policy engines. As long as there are Congress adapters to transform the user’s policies to something that domain-specific solver understands it will be fine. With respect to delegation to solver scheduler, I agree that we need a combination of options (1) and (2). For option (2), in order to leverage the pre-defined constraint classes in Solver Scheduler, it is more like the Congress adapter notifying the Solver Scheduler to include that constraint as part of the current placement decision. Also we have to take it to account that it is not just the user-defined Congress policies that define the placement choices, the already existing infrastructure-specific constraints, in terms of Host capacities, or any other provider specific constraints will have to be included in the placement decision calculation by the solver. The pre-configured scheduler/placement constraints will always have to be included. But some additional policies from Congress can introduce additional constraints. For option (1), new custom constraint class - Solver Scheduler already has an interface BaseLinearConstraint - https://github.com/stackforge/nova-solver-scheduler/blob/master/nova/scheduler/solvers/linearconstraints/__init__.py with methods - get_coefficient_vectors, get_variable_vectors, and get_operations that will be invoked by the main solver class to feed in the variables, and the host metrics, along with some input parameters that used to get additional metadata that can be used to build matrices. Eventually the main solver class builds the LP program by invoking all the classes. So for the Congress delegation scenario, it will be along these lines, where the Congress adapter will have to populate these matrices based on the Datalog policy. So as part of the solver scheduler’s workflow this special CongressConstraint class will have to call the Congress adapter with the variables already known, and get the necessary values. For reference, an example implementation of this constraint class is here - https://github.com/stackforge/nova-solver-scheduler/blob/master/nova/scheduler/solvers/linearconstraints/max_disk_allocation_constraint.py Will need some more thoughts, but the approach seems reasonable. Thanks, Yathi. On 3/18/15, 8:34 AM, Tim Hinrichs thinri...@vmware.commailto:thinri...@vmware.com wrote: I responded in the gdoc. Here’s a copy. One of my goals for delegation is to avoid asking people to write policy statements specific to any particular domain-specific solver. People ought to encode policy however they like, and the system ought to figure out how best to enforce that policy (delegation being one option). Assuming that's a reasonable goal, I see two options for delegation to solverScheduler (1) SolverScheduler exposes a custom constraint class. Congress generates the LP program from the Datalog, similar to what is described in this doc, and gives that LP program as custom constraints to the SolverScheduler. SolverScheduler is then responsible for enforcing that policy both during provisioning of new servers and for monitoring/migrating servers once provisioning is finished. (2) The Congress adapter for SolverScheduler understands the semantics of MemoryCapacityConstraint, identifies when the user has asked for that constraint, and replaces that part of the LP program with the MemoryCapacityConstraint. We probably want a combination of (1) and (2) so that we handle any gaps in the pre-defined constraints that SolverScheduler has, while at the same time leveraging the pre-defined constraints when possible. Tim On Mar 17, 2015, at 6:09 PM, Yathiraj Udupi (yudupi) yud...@cisco.commailto:yud...@cisco.com wrote: Hi Tim, I posted this comment on the doc. I am still pondering over a possibility of have a policy-driven scheduler workflow via the Solver Scheduler placement engine, which is also LP based like you describe in your doc. I know in your initial meeting, you plan to go over your proposal of building a VM placement engine that subscribes to the Congress DSE, I probably will understand the Congress workflows better and see how I could incorporate this proposal to talk to the Solver Scheduler to make the placement decisions. The example you provide in the doc, is a very good scenario, where a VM placement engine should continuously monitor and trigger VM migrations. I am also interested in the case of a policy-driven scheduling for the initial creation of VMs. This is where say people will call Nova APIs and create a new set of VMs. Here the scheduler workflow should address the constraints as imposed from the user's policies. Say the simple policy is Host's free RAM = 0.25 * Memory_Capacity I would like the scheduler to use this policy as defined from Congress, and apply
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
I responded in the gdoc. Here’s a copy.
One of my goals for delegation is to avoid asking people to write policy
statements specific to any particular domain-specific solver. People ought to
encode policy however they like, and the system ought to figure out how best to
enforce that policy (delegation being one option).
Assuming that's a reasonable goal, I see two options for delegation to
solverScheduler
(1) SolverScheduler exposes a custom constraint class. Congress generates the
LP program from the Datalog, similar to what is described in this doc, and
gives that LP program as custom constraints to the SolverScheduler.
SolverScheduler is then responsible for enforcing that policy both during
provisioning of new servers and for monitoring/migrating servers once
provisioning is finished.
(2) The Congress adapter for SolverScheduler understands the semantics of
MemoryCapacityConstraint, identifies when the user has asked for that
constraint, and replaces that part of the LP program with the
MemoryCapacityConstraint.
We probably want a combination of (1) and (2) so that we handle any gaps in the
pre-defined constraints that SolverScheduler has, while at the same time
leveraging the pre-defined constraints when possible.
Tim
On Mar 17, 2015, at 6:09 PM, Yathiraj Udupi (yudupi)
yud...@cisco.commailto:yud...@cisco.com wrote:
Hi Tim,
I posted this comment on the doc. I am still pondering over a possibility of
have a policy-driven scheduler workflow via the Solver Scheduler placement
engine, which is also LP based like you describe in your doc.
I know in your initial meeting, you plan to go over your proposal of building a
VM placement engine that subscribes to the Congress DSE, I probably will
understand the Congress workflows better and see how I could incorporate this
proposal to talk to the Solver Scheduler to make the placement decisions.
The example you provide in the doc, is a very good scenario, where a VM
placement engine should continuously monitor and trigger VM migrations.
I am also interested in the case of a policy-driven scheduling for the initial
creation of VMs. This is where say people will call Nova APIs and create a new
set of VMs. Here the scheduler workflow should address the constraints as
imposed from the user's policies.
Say the simple policy is Host's free RAM = 0.25 * Memory_Capacity
I would like the scheduler to use this policy as defined from Congress, and
apply it during the scheduling as part of the Nova boot call.
I am really interested in and need help in coming up with a solution
integrating Solver Scheduler, so say if I have an implementation of a
MemoryCapacityConstraint, which takes a hint value free_memory_limit (0.25
in this example),
could we have a policy in Datalog
placement_requirement(id) :-
nova:host(id),
solver_scheduler:applicable_constraints(id, [MemoryCapacityConstraint, ]),
applicable_metadata(id, {free_memory_limit: 0.25, })
This policy could be set and delegated by Congress to solver scheduler via the
set_policy API. or the Solver Scheduler can query Congress via a get_policy
API to get this policy, and incorporate it as part of the solver scheduler
workflow ?
Does this sound doable ?
Thanks,
Yathi.
On 3/16/15, 11:05 AM, Tim Hinrichs
thinri...@vmware.commailto:thinri...@vmware.com wrote:
Hi all,
The feedback on the POC delegation proposal has been mostly positive. Several
people have asked for a meeting to discuss further. Given time zone
constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2
days if you want to participate, and we will try to find a day that everyone
can attend.
https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edithttps://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1ksDilJYXV-2D5AXWON8PLMedDKr9NpS8VbT0jIy-5FMIEtI_editd=AwMFAgc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7sm=uiVXAFxgoK-F8a3oNLDykcTSmPGUMW2_kFB_BnUEBFgs=GWRQesGone_FbZRHXZmIcQd5MB20CHkriADqVNVnxiAe=
Thanks!
Tim
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.orgmailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
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 could pick up the constraint?
This then will not require the “solver scheduler” to implement specific
constraint classes such as “MemoryCapacityConstraint”.
We may have rules (not in sense of Datalog ☺ ) for name (e.g. variables or
constants) generation?
Ruby
De : Tim Hinrichs [mailto:thinri...@vmware.com]
Envoyé : mercredi 18 mars 2015 16:34
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
I responded in the gdoc. Here’s a copy.
One of my goals for delegation is to avoid asking people to write policy
statements specific to any particular domain-specific solver. People ought to
encode policy however they like, and the system ought to figure out how best to
enforce that policy (delegation being one option).
Assuming that's a reasonable goal, I see two options for delegation to
solverScheduler
(1) SolverScheduler exposes a custom constraint class. Congress generates the
LP program from the Datalog, similar to what is described in this doc, and
gives that LP program as custom constraints to the SolverScheduler.
SolverScheduler is then responsible for enforcing that policy both during
provisioning of new servers and for monitoring/migrating servers once
provisioning is finished.
(2) The Congress adapter for SolverScheduler understands the semantics of
MemoryCapacityConstraint, identifies when the user has asked for that
constraint, and replaces that part of the LP program with the
MemoryCapacityConstraint.
We probably want a combination of (1) and (2) so that we handle any gaps in the
pre-defined constraints that SolverScheduler has, while at the same time
leveraging the pre-defined constraints when possible.
Tim
On Mar 17, 2015, at 6:09 PM, Yathiraj Udupi (yudupi)
yud...@cisco.commailto:yud...@cisco.com wrote:
Hi Tim,
I posted this comment on the doc. I am still pondering over a possibility of
have a policy-driven scheduler workflow via the Solver Scheduler placement
engine, which is also LP based like you describe in your doc.
I know in your initial meeting, you plan to go over your proposal of building a
VM placement engine that subscribes to the Congress DSE, I probably will
understand the Congress workflows better and see how I could incorporate this
proposal to talk to the Solver Scheduler to make the placement decisions.
The example you provide in the doc, is a very good scenario, where a VM
placement engine should continuously monitor and trigger VM migrations.
I am also interested in the case of a policy-driven scheduling for the initial
creation of VMs. This is where say people will call Nova APIs and create a new
set of VMs. Here the scheduler workflow should address the constraints as
imposed from the user's policies.
Say the simple policy is Host's free RAM = 0.25 * Memory_Capacity
I would like the scheduler to use this policy as defined from Congress, and
apply it during the scheduling as part of the Nova boot call.
I am really interested in and need help in coming up with a solution
integrating Solver Scheduler, so say if I have an implementation of a
MemoryCapacityConstraint, which takes a hint value free_memory_limit (0.25
in this example),
could we have a policy in Datalog
placement_requirement(id) :-
nova:host(id),
solver_scheduler:applicable_constraints(id, [MemoryCapacityConstraint, ]),
applicable_metadata(id, {free_memory_limit: 0.25, })
This policy could be set and delegated by Congress to solver scheduler via the
set_policy API. or the Solver Scheduler can query Congress via a get_policy
API to get this policy, and incorporate it as part of the solver scheduler
workflow ?
Does this sound doable ?
Thanks,
Yathi.
On 3/16/15, 11:05 AM, Tim Hinrichs
thinri...@vmware.commailto:thinri...@vmware.com wrote:
Hi all,
The feedback on the POC delegation proposal has been mostly positive. Several
people have asked for a meeting to discuss further. Given time zone
constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2
days if you want to participate, and we will try to find a day that everyone
can attend.
https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edithttps://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1ksDilJYXV-2D5AXWON8PLMedDKr9NpS8VbT0jIy-5FMIEtI_editd=AwMFAgc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7sm=uiVXAFxgoK-F8a3oNLDykcTSmPGUMW2_kFB_BnUEBFgs=GWRQesGone_FbZRHXZmIcQd5MB20CHkriADqVNVnxiAe=
Thanks!
Tim
__
OpenStack Development Mailing List
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
Ruby,
The Custom constraint class was something Yathiraj mentioned a while back. But
yes the idea is that MemoryCapacityConstraint would be a special case of what
we can express in the custom constraints.
Tim
On Mar 18, 2015, at 10:05 AM,
ruby.krishnasw...@orange.commailto:ruby.krishnasw...@orange.com wrote:
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 could pick up the constraint?
This then will not require the “solver scheduler” to implement specific
constraint classes such as “MemoryCapacityConstraint”.
We may have rules (not in sense of Datalog ☺ ) for name (e.g. variables or
constants) generation?
Ruby
De : Tim Hinrichs [mailto:thinri...@vmware.com]
Envoyé : mercredi 18 mars 2015 16:34
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
I responded in the gdoc. Here’s a copy.
One of my goals for delegation is to avoid asking people to write policy
statements specific to any particular domain-specific solver. People ought to
encode policy however they like, and the system ought to figure out how best to
enforce that policy (delegation being one option).
Assuming that's a reasonable goal, I see two options for delegation to
solverScheduler
(1) SolverScheduler exposes a custom constraint class. Congress generates the
LP program from the Datalog, similar to what is described in this doc, and
gives that LP program as custom constraints to the SolverScheduler.
SolverScheduler is then responsible for enforcing that policy both during
provisioning of new servers and for monitoring/migrating servers once
provisioning is finished.
(2) The Congress adapter for SolverScheduler understands the semantics of
MemoryCapacityConstraint, identifies when the user has asked for that
constraint, and replaces that part of the LP program with the
MemoryCapacityConstraint.
We probably want a combination of (1) and (2) so that we handle any gaps in the
pre-defined constraints that SolverScheduler has, while at the same time
leveraging the pre-defined constraints when possible.
Tim
On Mar 17, 2015, at 6:09 PM, Yathiraj Udupi (yudupi)
yud...@cisco.commailto:yud...@cisco.com wrote:
Hi Tim,
I posted this comment on the doc. I am still pondering over a possibility of
have a policy-driven scheduler workflow via the Solver Scheduler placement
engine, which is also LP based like you describe in your doc.
I know in your initial meeting, you plan to go over your proposal of building a
VM placement engine that subscribes to the Congress DSE, I probably will
understand the Congress workflows better and see how I could incorporate this
proposal to talk to the Solver Scheduler to make the placement decisions.
The example you provide in the doc, is a very good scenario, where a VM
placement engine should continuously monitor and trigger VM migrations.
I am also interested in the case of a policy-driven scheduling for the initial
creation of VMs. This is where say people will call Nova APIs and create a new
set of VMs. Here the scheduler workflow should address the constraints as
imposed from the user's policies.
Say the simple policy is Host's free RAM = 0.25 * Memory_Capacity
I would like the scheduler to use this policy as defined from Congress, and
apply it during the scheduling as part of the Nova boot call.
I am really interested in and need help in coming up with a solution
integrating Solver Scheduler, so say if I have an implementation of a
MemoryCapacityConstraint, which takes a hint value free_memory_limit (0.25
in this example),
could we have a policy in Datalog
placement_requirement(id) :-
nova:host(id),
solver_scheduler:applicable_constraints(id, [MemoryCapacityConstraint, ]),
applicable_metadata(id, {free_memory_limit: 0.25, })
This policy could be set and delegated by Congress to solver scheduler via the
set_policy API. or the Solver Scheduler can query Congress via a get_policy
API to get this policy, and incorporate it as part of the solver scheduler
workflow ?
Does this sound doable ?
Thanks,
Yathi.
On 3/16/15, 11:05 AM, Tim Hinrichs
thinri...@vmware.commailto:thinri...@vmware.com wrote:
Hi all,
The feedback on the POC delegation proposal has been mostly positive. Several
people have asked for a meeting to discuss further. Given time zone
constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2
days if you want to participate, and we will try to find a day that everyone
can attend.
https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edithttps://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1ksDilJYXV-2D5AXWON8PLMedDKr9NpS8VbT0jIy
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
I will also be glad to participate. Thanks, Ramki From: ruby.krishnasw...@orange.com [mailto:ruby.krishnasw...@orange.com] Sent: Tuesday, March 17, 2015 5:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling 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, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2 days if you want to participate, and we will try to find a day that everyone can attend. https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit Thanks! Tim _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
Hi Tim,
I posted this comment on the doc. I am still pondering over a possibility of
have a policy-driven scheduler workflow via the Solver Scheduler placement
engine, which is also LP based like you describe in your doc.
I know in your initial meeting, you plan to go over your proposal of building a
VM placement engine that subscribes to the Congress DSE, I probably will
understand the Congress workflows better and see how I could incorporate this
proposal to talk to the Solver Scheduler to make the placement decisions.
The example you provide in the doc, is a very good scenario, where a VM
placement engine should continuously monitor and trigger VM migrations.
I am also interested in the case of a policy-driven scheduling for the initial
creation of VMs. This is where say people will call Nova APIs and create a new
set of VMs. Here the scheduler workflow should address the constraints as
imposed from the user's policies.
Say the simple policy is Host's free RAM = 0.25 * Memory_Capacity
I would like the scheduler to use this policy as defined from Congress, and
apply it during the scheduling as part of the Nova boot call.
I am really interested in and need help in coming up with a solution
integrating Solver Scheduler, so say if I have an implementation of a
MemoryCapacityConstraint, which takes a hint value free_memory_limit (0.25
in this example),
could we have a policy in Datalog
placement_requirement(id) :-
nova:host(id),
solver_scheduler:applicable_constraints(id, [MemoryCapacityConstraint, ]),
applicable_metadata(id, {free_memory_limit: 0.25, })
This policy could be set and delegated by Congress to solver scheduler via the
set_policy API. or the Solver Scheduler can query Congress via a get_policy
API to get this policy, and incorporate it as part of the solver scheduler
workflow ?
Does this sound doable ?
Thanks,
Yathi.
On 3/16/15, 11:05 AM, Tim Hinrichs
thinri...@vmware.commailto:thinri...@vmware.com wrote:
Hi all,
The feedback on the POC delegation proposal has been mostly positive. Several
people have asked for a meeting to discuss further. Given time zone
constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2
days if you want to participate, and we will try to find a day that everyone
can attend.
https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit
Thanks!
Tim
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
I will like to participate in the discussions. Thanks, Yathi. On 3/16/15, 11:05 AM, Tim Hinrichs thinri...@vmware.commailto:thinri...@vmware.com wrote: Hi all, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2 days if you want to participate, and we will try to find a day that everyone can attend. https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit Thanks! Tim __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
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, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2 days if you want to participate, and we will try to find a day that everyone can attend. https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit Thanks! Tim _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
Hi Tim, I am interest in it. But I am UTC+8 time, so the 8a Pacific is not convenient. No matter, I can read the minutes if it has. I am sorry for not contribute the inter-domain text to delegation draft , I think this IRTF draft mentioned some https://datatracker.ietf.org/doc/draft-norival-nfvrg-nfv-policy-arch/ My basic idea of inter-domain delegation is let global policy engine get all info through a database message bus and make decision centrally. We can use parallel computing and memory based database technology to handle the performance issue. BR Oliver --- Huangyong (Oliver) Network research, Huawei From: Tim Hinrichs [mailto:thinri...@vmware.com] Sent: Tuesday, March 17, 2015 2:05 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Congress] [Delegation] Meeting scheduling Hi all, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2 days if you want to participate, and we will try to find a day that everyone can attend. https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit Thanks! Tim __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] [Delegation] Meeting scheduling
Hi all, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2 days if you want to participate, and we will try to find a day that everyone can attend. https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit Thanks! Tim __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling
interested Thx Uri (Oo-Ree) C: 949-378-7568 From: Tim Hinrichs [mailto:thinri...@vmware.com] Sent: Monday, March 16, 2015 11:05 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Congress] [Delegation] Meeting scheduling Hi all, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2 days if you want to participate, and we will try to find a day that everyone can attend. https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit Thanks! Tim __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
