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

[Ramki Krishnan]

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] Initial workflow design

[Ramki Krishnan]

@Ramki:  VM size, could we say that only the in-memory state is migrated? The 
VM’s disk resides on a network-attached storage. Disk will not be migrated.

That is exactly right Ruby.

Thanks,
Ramki

From: ruby.krishnasw...@orange.com [mailto:ruby.krishnasw...@orange.com]
Sent: Thursday, February 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 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 
operation depending on the size of the VM and various other factors; such an 
operation cannot be performed frequently.

I do not know at what frequency data may change.
@Ramki:  VM size, could we say that only the in-memory state is migrated? The 
VM’s disk resides on a network-attached storage. Disk will not be migrated.
In any case I agree that migration (probably) cannot be performed frequently.



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...@orange.com" 
mailto:ruby.krishnasw...@orange.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
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-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 policy engine executes the 
following API call over the DSE”

ð “domain-agnostic” ….



Done.


2) Step 4:



Ok

But finally: if Congress will likely “delegate”



Not sure what you’re suggesting here.


3) Step 5:  Compilation of subpolicy to LP in VM-placement engine



For the PoC, it is likely that the LP program ( in PuLP or some other ML) is 
*not* completely generated by compiler/translator.

ð Right?

Where does the rest of the program originate?  I’m not saying the entire LP 
program is generated from the Datalog constraints; some of it is generated by 
the solver independent of the Datalog.  In the text, I gave the example of 
defining hMemUse[j].


 You also indicate that some category of constraints (“the LP solver 
doesn’t know what the relationship between assign[i][j], hMemUse[j], and 
vMemUse[i] actually is, so the VM-placement engine must also include 
constraints”) .
 These constraints must be “explicitly” written?  (e.g. max_ram_allocation 
etc that are constraints used in the solver-scheduler’s package).

The VM-placement engine does 2 things: (I) translates Datalog to LP and (ii) 
generates additional LP constraints.  (Both work items could leverage any 
constraints that are builtin to a specific solver, e.g. the solver-scheduler.  
The point is that there are 2 distinct, conceptual origins of the LP 
constraints: those that represent the Datalog and those that codify the domain.



 So what “parts” will be generated:
Cost function :
Constraint from Policy : memory usage < 75%

 Then the rest should be “filled” up?

 Could we convene on an intermediary “modeling language”?
@Yathi: do you think we could use some thing like AMPL ? Is this 
proprietary?


A detail: the example “Y[host1] = hMemUse[host1] > 0.75 * hMemCap[host1]”


ð To be changed to a linear form (mi – Mi > 0 then Yi = 1 else Yi = 0) so 
something like (mi – Mi) < 100 yi

Each domain-specific solver can do whatever it wants, so it’s not clear to me 
what the value of choosing a modeling language actually is—unless we want to 
build a library of common functionality that makes the construction of 
domain-specific engine (wrappers) easier.  I’d prefer to spend our energy 
understanding whether the proposed workflow/interface works for a couple of 
different domain-specific policy engines OR to flush this one out and build it.



4) Step 6: This is completely internal to the VM-placement engine (and we 
could say this is “transparent” to Congress)



We should allow configuration of a solver (this itself could be a policy ☺ )

How to invoke the solver API ?



The domain-specific placement engine could send out to DSE (action_handler: 
data)?



I had always envisioned the solver being just a library of code—not an entity 
that

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

[Ramki Krishnan]

1)
Ruby: One of the issues highlighted in OpenStack (scheduler) and also elsewhere 
(e.g. Omega scheduler by google) is :

Reading “host utilization” state from the data bases and DB (nova:host table) 
updates and overhead of maintaining in-memory state uptodate.

ð  This is expensive and current nova-scheduler does face this issue (many 
blogs/discussions).

  While the first goal is a PoC, this will likely become a concern in terms 
of adoption.


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. Could you point 
me to some of these discussions?

Ramki: We have to keep in mind that VM migration could be an expensive 
operation depending on the size of the VM and various other factors; such an 
operation cannot be performed frequently.

2)
>>From document: As soon as the subscription occurs, the DSE sends the 
>>VM-placement engine the current contents of those tables, and when these 
>>tables change, the DSE informs the VM-placement engine in the form of diffs 
>>(aka deltas or updates).

Ramki: Is the criteria for table change programmable? This would be useful to 
generate significant change events based on application needs.

Thanks,
Ramki

From: Tim Hinrichs [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...@orange.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
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-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 policy engine executes the 
following API call over the DSE”

ð “domain-agnostic” ….



Done.


2) Step 4:



Ok

But finally: if Congress will likely “delegate”



Not sure what you’re suggesting here.


3) Step 5:  Compilation of subpolicy to LP in VM-placement engine



For the PoC, it is likely that the LP program ( in PuLP or some other ML) is 
*not* completely generated by compiler/translator.

ð Right?

Where does the rest of the program originate?  I’m not saying the entire LP 
program is generated from the Datalog constraints; some of it is generated by 
the solver independent of the Datalog.  In the text, I gave the example of 
defining hMemUse[j].


 You also indicate that some category of constraints (“the LP solver 
doesn’t know what the relationship between assign[i][j], hMemUse[j], and 
vMemUse[i] actually is, so the VM-placement engine must also include 
constraints”) .
 These constraints must be “explicitly” written?  (e.g. max_ram_allocation 
etc that are constraints used in the solver-scheduler’s package).

The VM-placement engine does 2 things: (I) translates Datalog to LP and (ii) 
generates additional LP constraints.  (Both work items could leverage any 
constraints that are builtin to a specific solver, e.g. the solver-scheduler.  
The point is that there are 2 distinct, conceptual origins of the LP 
constraints: those that represent the Datalog and those that codify the domain.



 So what “parts” will be generated:
Cost function :
Constraint from Policy : memory usage < 75%

 Then the rest should be “filled” up?

 Could we convene on an intermediary “modeling language”?
@Yathi: do you think we could use some thing like AMPL ? Is this 
proprietary?


A detail: the example “Y[host1] = hMemUse[host1] > 0.75 * hMemCap[host1]”


ð To be changed to a linear form (mi – Mi > 0 then Yi = 1 else Yi = 0) so 
something like (mi – Mi) < 100 yi

Each domain-specific solver can do whatever it wants, so it’s not clear to me 
what the value of choosing a modeling language actually is—unless we want to 
build a library of common functionality that makes the construction of 
domain-specific engine (wrappers) easier.  I’d prefer to spend our energy 
understanding whether the proposed workflow/interface works for a couple of 
different domain-specific policy engines OR to flush this one out and build it.



4) Step 6: This is completely internal to the VM-placement engine (and we 
could say this is “transparent” to Congress)



We should allow configuration of a solver (this itself could be a policy ☺ )

How to invoke th

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

[Ramki Krishnan]

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 [mailto:thinri...@vmware.com]
Sent: Monday, February 23, 2015 11:28 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Congress][Delegation] Initial workflow design


Hi all,



I made a heavy editing pass of the Delegation google doc, incorporating many of 
your comments and my latest investigations into VM-placement.  I left the old 
stuff in place at the end of the doc and put the new stuff at the top.



My goal was to propose an end-to-end workflow for a PoC that we could put 
together quickly to help us explore the delegation interface.  We should 
iterate on this design until we have something that we think is workable.   And 
by all means pipe up if you think we need a totally different starting point to 
begin the iteration.



(BTW I'm thinking of the integration with solver-scheduler as a long-term 
solution to VM-placement, once we get the delegation interface sorted out.)



https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit#



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] NFV in OpenStack use cases and context

[ramki Krishnan]

++ Yathi.

-Original Message-
From: ramki Krishnan [mailto:r...@brocade.com] 
Sent: Thursday, June 12, 2014 12:48 PM
To: OpenStack Development Mailing List (not for usage questions); Alan Kavanagh
Cc: Norival Figueira
Subject: Re: [openstack-dev] NFV in OpenStack use cases and context

Yathi - many thanks for adding more NFV context.

Alan - many thanks for the interest and would be glad to have further 
discussions.

Thanks,
Ramki

-Original Message-
From: Yathiraj Udupi (yudupi) [mailto:yud...@cisco.com]
Sent: Thursday, June 12, 2014 11:53 AM
To: Alan Kavanagh
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] NFV in OpenStack use cases and context

Hi Alan, 

Our Smart (Solver) Scheduler blueprint
(https://blueprints.launchpad.net/nova/+spec/solver-scheduler ) has been in the 
works in the Nova community since late 2013.  We have demoed at the Hong Kong 
summit, as well as the Atlanta summit,  use cases using this smart scheduler 
for better, optimized resource placement with complex constrained scenarios.  
So to let you know this work was started as a smart way of doing scheduling, 
applicable in general and not limited to NFV.  Currently we feel NFV is a 
killer app for driving this blueprint and work ahead, however is applicable for 
all kinds of resource placement scenarios. 

We will be very interested in finding out more about your blueprints that you 
are referring to here, and see how it can be integrated as part of our future 
roadmap. 

Thanks,
Yathi. 


On 6/12/14, 10:55 AM, "Alan Kavanagh"  wrote:

>Hi Ramki
>
>Really like the smart scheduler idea, we made a couple of blueprints 
>that are related to ensuring you have the right information to build a 
>constrained based scheduler. I do however want to point out that this 
>is not NFV specific but is useful for all applications and services of 
>which NFV is one.
>
>/Alan
>
>-Original Message-
>From: ramki Krishnan [mailto:r...@brocade.com]
>Sent: June-10-14 6:06 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Cc: Chris Wright; Nicolas Lemieux; Norival Figueira
>Subject: Re: [openstack-dev] NFV in OpenStack use cases and context
>
>Hi Steve,
>
>Forgot to mention, the "Smart Scheduler (Solver Scheduler) enhancements 
>for NFV: Use Cases, Constraints etc." is a good example of an NFV use 
>case deep dive for OpenStack.
>
>https://urldefense.proofpoint.com/v1/url?u=https://docs.google.com/docu
>men
>t/d/1k60BQXOMkZS0SIxpFOppGgYp416uXcJVkAFep3Oeju8/edit%23heading%3Dh.wlb
>cla
>gujw8c&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=%2FZ35AkRhp2kCW4Q3MPeE%2Bx
>Y2b
>qaf%2FKm29ZfiqAKXxeo%3D%0A&m=vTulCeloS8Hc59%2FeAOd32Ri4eqbNqVE%2FeMgNRz
>GZn
>z4%3D%0A&s=836991d6daab66b519de3b670db8af001144ddb20e636665b395597aa118
>538
>f
>
>Thanks,
>Ramki
>
>-Original Message-
>From: ramki Krishnan
>Sent: Tuesday, June 10, 2014 3:01 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Cc: Chris Wright; Nicolas Lemieux; Norival Figueira
>Subject: RE: NFV in OpenStack use cases and context
>
>Hi Steve,
>
>We are have OpenStack gap analysis documents in ETSI NFV under member 
>only access. I can work on getting public version of the documents (at 
>least a draft) to fuel the kick start.
>
>Thanks,
>Ramki
>
>-Original Message-
>From: Steve Gordon [mailto:sgor...@redhat.com]
>Sent: Tuesday, June 10, 2014 12:06 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Cc: Chris Wright; Nicolas Lemieux
>Subject: Re: [openstack-dev] [NFV] Re: NFV in OpenStack use cases and 
>context
>
>- Original Message -
>> From: "Steve Gordon" 
>> To: "Stephen Wong" 
>> 
>> - Original Message -
>> > From: "Stephen Wong" 
>> > To: "ITAI MENDELSOHN (ITAI)" ,
>> > "OpenStack Development Mailing List (not for usage questions)"
>> > 
>> > 
>> > Hi,
>> > 
>> > Perhaps I have missed it somewhere in the email thread? Where 
>> > is the use case => bp document we are supposed to do for this week?
>> > Has it been created yet?
>> > 
>> > Thanks,
>> > - Stephen
>> 
>> Hi,
>> 
>> Itai is referring to the ETSI NFV use cases document [1] and the 
>> discussion is around how we distill those - or a subset of them - 
>> into a more consumable format for an OpenStack audience on the Wiki.
>> At this point I think the best approach is to simply start entering 
>> one of them (perhaps #5) into the Wiki and go from there. Ideally 
>> this would form a basis for discussing the format etc.
>> 

Re: [openstack-dev] NFV in OpenStack use cases and context

[ramki Krishnan]

Yathi - many thanks for adding more NFV context.

Alan - many thanks for the interest and would be glad to have further 
discussions.

Thanks,
Ramki

-Original Message-
From: Yathiraj Udupi (yudupi) [mailto:yud...@cisco.com] 
Sent: Thursday, June 12, 2014 11:53 AM
To: Alan Kavanagh
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] NFV in OpenStack use cases and context

Hi Alan, 

Our Smart (Solver) Scheduler blueprint
(https://blueprints.launchpad.net/nova/+spec/solver-scheduler ) has been in the 
works in the Nova community since late 2013.  We have demoed at the Hong Kong 
summit, as well as the Atlanta summit,  use cases using this smart scheduler 
for better, optimized resource placement with complex constrained scenarios.  
So to let you know this work was started as a smart way of doing scheduling, 
applicable in general and not limited to NFV.  Currently we feel NFV is a 
killer app for driving this blueprint and work ahead, however is applicable for 
all kinds of resource placement scenarios. 

We will be very interested in finding out more about your blueprints that you 
are referring to here, and see how it can be integrated as part of our future 
roadmap. 

Thanks,
Yathi. 


On 6/12/14, 10:55 AM, "Alan Kavanagh"  wrote:

>Hi Ramki
>
>Really like the smart scheduler idea, we made a couple of blueprints 
>that are related to ensuring you have the right information to build a 
>constrained based scheduler. I do however want to point out that this 
>is not NFV specific but is useful for all applications and services of 
>which NFV is one.
>
>/Alan
>
>-Original Message-
>From: ramki Krishnan [mailto:r...@brocade.com]
>Sent: June-10-14 6:06 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Cc: Chris Wright; Nicolas Lemieux; Norival Figueira
>Subject: Re: [openstack-dev] NFV in OpenStack use cases and context
>
>Hi Steve,
>
>Forgot to mention, the "Smart Scheduler (Solver Scheduler) enhancements 
>for NFV: Use Cases, Constraints etc." is a good example of an NFV use 
>case deep dive for OpenStack.
>
>https://urldefense.proofpoint.com/v1/url?u=https://docs.google.com/docu
>men 
>t/d/1k60BQXOMkZS0SIxpFOppGgYp416uXcJVkAFep3Oeju8/edit%23heading%3Dh.wlb
>cla 
>gujw8c&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=%2FZ35AkRhp2kCW4Q3MPeE%2Bx
>Y2b 
>qaf%2FKm29ZfiqAKXxeo%3D%0A&m=vTulCeloS8Hc59%2FeAOd32Ri4eqbNqVE%2FeMgNRz
>GZn
>z4%3D%0A&s=836991d6daab66b519de3b670db8af001144ddb20e636665b395597aa118
>538
>f
>
>Thanks,
>Ramki
>
>-Original Message-
>From: ramki Krishnan
>Sent: Tuesday, June 10, 2014 3:01 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Cc: Chris Wright; Nicolas Lemieux; Norival Figueira
>Subject: RE: NFV in OpenStack use cases and context
>
>Hi Steve,
>
>We are have OpenStack gap analysis documents in ETSI NFV under member 
>only access. I can work on getting public version of the documents (at 
>least a draft) to fuel the kick start.
>
>Thanks,
>Ramki
>
>-Original Message-
>From: Steve Gordon [mailto:sgor...@redhat.com]
>Sent: Tuesday, June 10, 2014 12:06 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Cc: Chris Wright; Nicolas Lemieux
>Subject: Re: [openstack-dev] [NFV] Re: NFV in OpenStack use cases and 
>context
>
>- Original Message -
>> From: "Steve Gordon" 
>> To: "Stephen Wong" 
>> 
>> - Original Message -
>> > From: "Stephen Wong" 
>> > To: "ITAI MENDELSOHN (ITAI)" ,
>> > "OpenStack Development Mailing List (not for usage questions)"
>> > 
>> > 
>> > Hi,
>> > 
>> > Perhaps I have missed it somewhere in the email thread? Where 
>> > is the use case => bp document we are supposed to do for this week? 
>> > Has it been created yet?
>> > 
>> > Thanks,
>> > - Stephen
>> 
>> Hi,
>> 
>> Itai is referring to the ETSI NFV use cases document [1] and the 
>> discussion is around how we distill those - or a subset of them - 
>> into a more consumable format for an OpenStack audience on the Wiki. 
>> At this point I think the best approach is to simply start entering 
>> one of them (perhaps #5) into the Wiki and go from there. Ideally 
>> this would form a basis for discussing the format etc.
>> 
>> Thanks,
>> 
>> Steve
>> 
>> [1]
>> http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NF
>> V
>> 001v010101p.pdf
>
>To try and kick start things I have created a table on the wiki [1] 
>based on the *DRAFT* NFV P

Re: [openstack-dev] NFV in OpenStack use cases and context

[ramki Krishnan]

Hi Cu Volker,

Many thanks for catching this. I will fix this shortly.

Thanks,
Ramki

-Original Message-
From: Volker Lötterle [mailto:openst...@systems-networking.de] 
Sent: Tuesday, June 10, 2014 7:48 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] NFV in OpenStack use cases and context

Hi Ramki,

On 11.06.2014 00:06, ramki Krishnan wrote:>
>
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
>

there are a two typo on the last line of the docoment, IMHO:

x1+x2+x3 >= 20 VMs, x1 <= 10 VMs, x2 <= 10 VMs, x3 <= 10 VMs
y1+y2+y3 >= 2 Gbps, y1 = 0, y2 <= 10Gbps, y3 <= 10Gbps

cu Volker


-- 


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] NFV in OpenStack use cases and context

[ramki Krishnan]

Hi Steve,

Forgot to mention, the "Smart Scheduler (Solver Scheduler) enhancements for 
NFV: Use Cases, Constraints etc." is a good example of an NFV use case deep 
dive for OpenStack.

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

Thanks,
Ramki

-Original Message-
From: ramki Krishnan 
Sent: Tuesday, June 10, 2014 3:01 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Chris Wright; Nicolas Lemieux; Norival Figueira
Subject: RE: NFV in OpenStack use cases and context

Hi Steve,

We are have OpenStack gap analysis documents in ETSI NFV under member only 
access. I can work on getting public version of the documents (at least a 
draft) to fuel the kick start.

Thanks,
Ramki

-Original Message-
From: Steve Gordon [mailto:sgor...@redhat.com]
Sent: Tuesday, June 10, 2014 12:06 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Chris Wright; Nicolas Lemieux
Subject: Re: [openstack-dev] [NFV] Re: NFV in OpenStack use cases and context

- Original Message -
> From: "Steve Gordon" 
> To: "Stephen Wong" 
> 
> - Original Message -
> > From: "Stephen Wong" 
> > To: "ITAI MENDELSOHN (ITAI)" ,
> > "OpenStack Development Mailing List (not for usage questions)" 
> > 
> > 
> > Hi,
> > 
> > Perhaps I have missed it somewhere in the email thread? Where is 
> > the use case => bp document we are supposed to do for this week? Has 
> > it been created yet?
> > 
> > Thanks,
> > - Stephen
> 
> Hi,
> 
> Itai is referring to the ETSI NFV use cases document [1] and the 
> discussion is around how we distill those - or a subset of them - into 
> a more consumable format for an OpenStack audience on the Wiki. At 
> this point I think the best approach is to simply start entering one 
> of them (perhaps #5) into the Wiki and go from there. Ideally this 
> would form a basis for discussing the format etc.
> 
> Thanks,
> 
> Steve
> 
> [1]
> http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV
> 001v010101p.pdf

To try and kick start things I have created a table on the wiki [1] based on 
the *DRAFT* NFV Performance & Portability Best Practises document [2]. This 
really lists workload types rather than specific applications, although I've 
put in an examples column we can populate with them.

I find it a useful way to quickly break down some of the characteristics of NFV 
applications at a glance. What do people think of this as something to start 
with? Remember, it's a wiki! So anyone is welcome to either expand the table or 
start adding more concrete user stories (e.g. around ETSI NFV use case number 5 
that Itai and I have been referring to, or any other VNF for that matter) in 
this section (we may/want need to create a separate page but for now it seems 
OK to get started here).

Thanks,

Steve

[1] https://wiki.openstack.org/wiki/Meetings/NFV#Use_Cases
[2] 
http://docbox.etsi.org/ISG/NFV/Open/Latest_Drafts/NFV-PER001v009%20-%20NFV%20Performance%20&%20Portability%20Best%20Practises.pdf

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] NFV in OpenStack use cases and context

[ramki Krishnan]

Hi Steve,

We are have OpenStack gap analysis documents in ETSI NFV under member only 
access. I can work on getting public version of the documents (at least a 
draft) to fuel the kick start.

Thanks,
Ramki

-Original Message-
From: Steve Gordon [mailto:sgor...@redhat.com] 
Sent: Tuesday, June 10, 2014 12:06 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Chris Wright; Nicolas Lemieux
Subject: Re: [openstack-dev] [NFV] Re: NFV in OpenStack use cases and context

- Original Message -
> From: "Steve Gordon" 
> To: "Stephen Wong" 
> 
> - Original Message -
> > From: "Stephen Wong" 
> > To: "ITAI MENDELSOHN (ITAI)" ,
> > "OpenStack Development Mailing List (not for usage questions)" 
> > 
> > 
> > Hi,
> > 
> > Perhaps I have missed it somewhere in the email thread? Where is 
> > the use case => bp document we are supposed to do for this week? Has 
> > it been created yet?
> > 
> > Thanks,
> > - Stephen
> 
> Hi,
> 
> Itai is referring to the ETSI NFV use cases document [1] and the 
> discussion is around how we distill those - or a subset of them - into 
> a more consumable format for an OpenStack audience on the Wiki. At 
> this point I think the best approach is to simply start entering one 
> of them (perhaps #5) into the Wiki and go from there. Ideally this 
> would form a basis for discussing the format etc.
> 
> Thanks,
> 
> Steve
> 
> [1]
> http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV
> 001v010101p.pdf

To try and kick start things I have created a table on the wiki [1] based on 
the *DRAFT* NFV Performance & Portability Best Practises document [2]. This 
really lists workload types rather than specific applications, although I've 
put in an examples column we can populate with them.

I find it a useful way to quickly break down some of the characteristics of NFV 
applications at a glance. What do people think of this as something to start 
with? Remember, it's a wiki! So anyone is welcome to either expand the table or 
start adding more concrete user stories (e.g. around ETSI NFV use case number 5 
that Itai and I have been referring to, or any other VNF for that matter) in 
this section (we may/want need to create a separate page but for now it seems 
OK to get started here).

Thanks,

Steve

[1] https://wiki.openstack.org/wiki/Meetings/NFV#Use_Cases
[2] 
http://docbox.etsi.org/ISG/NFV/Open/Latest_Drafts/NFV-PER001v009%20-%20NFV%20Performance%20&%20Portability%20Best%20Practises.pdf

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [NFV] - follow up on scheduling discussion

[ramki Krishnan]

Hi Tim,

Agree, Congress is a good place to store the scheduling constraints.

Thanks,
Ramki

-Original Message-
From: Tim Hinrichs [mailto:thinri...@vmware.com] 
Sent: Tuesday, June 10, 2014 8:21 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Norival Figueira; Debo Dutta (dedutta) (dedu...@cisco.com)
Subject: Re: [openstack-dev] [NFV] - follow up on scheduling discussion

Hi all,

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.

https://wiki.openstack.org/wiki/Congress

Tim  



On Jun 4, 2014, at 11:25 AM, ramki Krishnan  wrote:

> All,
> 
> 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.
> 
> Thanks,
> Ramki
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=%2FZ35AkRhp2kCW4Q3MPeE%2BxY2bqaf%2FKm29ZfiqAKXxeo%3D%0A&m=vTulCeloS8Hc59%2FeAOd32Ri4eqbNqVE%2FeMgNRzGZnz4%3D%0A&s=7df001977efa968a09f3fae30b16ae35f4278a7bc82fcb3cdbbc9639cc505503


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [NFV] - follow up on scheduling discussion

[ramki Krishnan]

All,

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://docs.google.com/document/d/1k60BQXOMkZS0SIxpFOppGgYp416uXcJVkAFep3Oeju8/edit#heading=h.wlbclagujw8c

Based on this proposal, we are planning to enhance the existing 
solver-scheduler blueprint 
https://blueprints.launchpad.net/nova/+spec/solver-scheduler.

Would love to hear your comments and thoughts. Would be glad to arrange a 
conference call if needed.

Thanks,
Ramki


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] test message - please ignore

[ramki Krishnan]

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev