Hi Ramki,
Good suggestion. I added a paragraph at the top of the doc in the Overview
section to explain what Delegation means and mentioned that some policies won’t
be delegated.
Tim
On Feb 26, 2015, at 3:15 PM, Ramki Krishnan
mailto:r...@brocade.com>> wrote:
Hi Tim, All,
The document is i
s [mailto:thinri...@vmware.com]
Sent: Thursday, February 26, 2015 10:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress][Delegation] Initial workflow design
Inline.
From: "ruby.krishnasw...@orange.com<mailto:ruby.krishnasw.
i 26 février 2015 19:17
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Congress][Delegation] Initial workflow design
Inline.
From: "ruby.krishnasw...@orange.com<mailto:ruby.krishnasw...@orange.com>"
mailto:ruby.krishnasw...@orange.com&g
...@orange.com]
Sent: Friday, February 27, 2015 10:41 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress][Delegation] Initial workflow design
My first suggestion: why don’t we set up call together with Ramki, Yathi, Debo,
as soon as possible
26, 2015 11:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress][Delegation] Initial workflow design
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
es the
policy snippet.
Ruby
De : Tim Hinrichs [mailto:thinri...@vmware.com]
Envoyé : jeudi 26 février 2015 19:17
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Congress][Delegation] Initial workflow design
Inline.
From: "ruby.krishnasw...@
ichs [mailto:thinri...@vmware.com]
Envoyé : jeudi 26 février 2015 19:17
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Congress][Delegation] Initial workflow design
Inline.
From: "ruby.krishnasw...@orange.com<mailto:ruby.krishnasw...@orange.c
g>>
Date: Wednesday, February 25, 2015 at 8:53 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Congress][Delegation] Initial workflow design
Hi Tim, All,
1) Step 3: The VM-plac
(not for usage questions)
Subject: Re: [openstack-dev] [Congress][Delegation] Initial workflow design
Inline.
From: "ruby.krishnasw...@orange.com<mailto:ruby.krishnasw...@orange.com>"
mailto:ruby.krishnasw...@orange.com>>
Reply-To: "OpenStack Development Mailing Li
Hi Tim, All,
The document is in great shape! Any global policies such as those impacting
compute and network (e.g. CPU utilization and network bandwidth utilization)
would be handled in Congress and not delegated. It would be worthwhile to
capture this.
Thanks,
Ramki
From: Tim Hinrichs [mailt
esday, February 25, 2015 at 8:53 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Congress][Delegation] Initial workflow design
Hi Tim, All,
1) Step 3: The VM-placement engine is also a “datalo
ave changed the "example" policy, could we
drill down the set of policies for the PoC (the server under utilization ?)
ð As a reference
Ruby
De : Yathiraj Udupi (yudupi) [mailto:yud...@cisco.com]
Envoyé : mardi 24 février 2015 20:01
À : OpenStack Development Mailing List (not for usage qu
Hi Tim,
Thanks for your updated doc on Delegation from Congress to a domain-specific
policy engine, in this case, you are planning to build a LP-based VM-Placement
engine to be the domain specific policy engine.
I agree your main goal is to first get the delegation interface sorted out. It
wil
13 matches
Mail list logo
