[openstack-dev] [FEMDC] Use Cases

Paul-Andre Raymond paul-andre.raymond at nexius.com
Wed Jul 5 18:53:34 UTC 2017

Following our discussion today, I have added a slide (see slide 11) in the google docs about  not underestimating the importance of networking for our use cases.
Specifically, to fully describe a use case, It would be useful to flesh out the following aspects.

The performance of a specific use case will depend specifically on how networking implementation is done in Edge Node.
1- Do we use Neutron or something else? (e.g. Tricircle)
2- Is networking in Edge node at L2, or is it done at L3?
3- Is there a need for encryption (between edge and central nodes)? Is there a performance impact (e.g. MTU)?
4- How is Control plane separated from User Plane?

This completes an action I took today.



From: Paul-André Raymond <paul-andre.raymond at nexius.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Wednesday, July 5, 2017 at 12:53 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [FEMDC] Use Cases


I look forward to continue discussions on how to structure use cases during our FEMDC call today.

You will find some slides on google doc that describe my thinking.

You will see in there that I feel a use case should include:

  1.  A Deployment Scenario (e.g. NFV or Edge or Federation)
  2.  A Service Use Case  (e.g. IOT, or Mobility or AR or …)
  3.  Openstack component distribution use case  (Regions or Cells or other)
  4.  User plane use case (e.g. Failure scenario)
  5.  Control Plane Use case (e.g. node commissioning or decommissioning)

Please let me know your comments.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170705/b4338389/attachment.html>

More information about the OpenStack-dev mailing list