Re: Use cases and Blueprints

Margaret Chiosi <margaret.chiosi1@...>

I will be surprised if we can come up with one functional set of components we all agree on based on my OPNFV/ONAP experience.

But we can try.


Thank You,

Margaret Chiosi

VP Open Ecosystem Team


Admin: Sophie Johnson


+1 (908) 541-3590


Futurewei Technologies, Inc.

Fixed Network Solution CC

400 Crossing Blvd

Bridgewater, NJ 08807

(cell) +1-732-216-5507



From: Andrew Wilkinson [mailto:andrew.wilkinson@...]
Sent: Thursday, September 13, 2018 11:40 AM
To: Margaret Chiosi (A) <margaret.chiosi1@...>; main@...
Subject: RE: [Akraino Main] Use cases and Blueprints



I wouldn’t see a Test definition (3) as a ‘blueprint’.


Nor would I see specific functional components (2) developed by the Akraino community as ‘blueprints’ either.


I think using the term blueprint for everything tends to make the term too broad. The term blueprint in common parlance is taken to mean the definition of how to build something (e.g. a building – a house or a shed etc). I could of course be expanded to encompass more (like a test blueprint) but would suggest we keep Akraino blueprints to be more specific and not include  functionality or test schedules.


Rather I propose a blueprint be used to classify a set of options that cab result in distinct POD deployments. The term ‘Network Clod blueprint’ would be used as such.



From: main@... <main@...> On Behalf Of Margaret Chiosi
Sent: Thursday, September 13, 2018 4:22 PM
To: main@...
Subject: Re: [Akraino Main] Use cases and Blueprints


I thought in email folks were ok with the following types of blueprint:
1. Architecture
2. components (Physical/virtual) supporting a specific 'use case'
3. Test

Join to automatically receive all group messages.