|
Re: Akraino Charter
I don’t love the idea of using the term BluePrint for the functional development projects. I think the term is already overloaded enough, and there is already some confusion between the term blueprint as it applies to OpenStack and an Akraino Integration blueprint.
I like the term blueprint as it applies to things are being ‘built’ or integrated from multiple sources, with potentially multiple regulations (or standards) to apply and potentially with very different components (HW, VIM, MW or APIs) etc. Using the same term to apply to a more focused and singular project may be pretty confusing.
Perhaps we could do something more consistent with what OPNFV is doing? Using project proposals/plans to define and propose new functional projects. -glenn
From: main@... [mailto:main@...]
On Behalf Of Wenjing Chu
Sent: Wednesday, September 05, 2018 11:04 AM To: main@... Subject: Re: [akraino] Akraino Charter
Visibility is the same whether we call it project or blueprint. I’m fine with either name.
From: Thomas Nadeau To: main<main@...> Subject: Re: [akraino] Akraino Charter Time: 2018-09-05 08:00:05
The idea for doing everything in blueprints is that it brings visibility into any work that impacts the project to both the TSC, but also clearly in writing so any others (i.e.: integration, testing, etc...) that might be external to the project have clear information about what is planned or underway. On a related note, I view blue prints as being largely analogous to epics, and in the same way are a good way to plan for a current or future release, and just a good way to organize the moving parts of a large project like this one potentially can turn out to be.
--Tom
On Tue, Sep 4, 2018 at 7:30 PM Wenjing Chu <Wenjing.Chu@...> wrote:
|
||||
|
|
||||
|
Use cases and Blueprints
Srini
Hi,
In last Akraino developer conference and break-out session, some clarity started to emerge. But.. several questions remain on the granularity of blueprint. My intention of this email is to start the conversation by asking some high level questions.
For every use case, there would be set of deployments. For each deployment, there would be blueprints. For a given deployment, intention is to have small number of blueprints.
For instance, in case of 5G use case, the deployments can be as follows:
- Core network cloud deployment - Multi-server edge cloud deployment - Single server edge cloud deployment - Two server edge cloud deployment - Headless edge deployment - Service Orchestration deployment - Regional Cloud controller deployment - Regional orchestration deployment
One blueprint in each of above deployments is expected to satisfy 5G use case. For each deployment, intention is to have as minimum number of blueprints to choose from.
For example, for Multi-Server edge cloud deployment, following blueprints are one possibility:
- Openstack-x86HW-Ubuntu-NoSDNCtrl-v1 - K8S-x86HW-Ubuntu-OVN-SRIOVCtrl-v1
There are few questions raised and we are wondering whether there is a need to have modularity in the blue prints.
1. A given Edge Cloud may not have all uniform servers. Some servers may be legacy, some may be with latest processor ). In future, they may be added with some add-on accelerators or there could be compute nodes with next generation processors. Also, compute nodes could be from different OEMs. Every time there is new node introduced or enhanced with new add-on accelerators, would it be considered as a new blueprint or is that considered as new version of existing blueprint? New version? 2. Is OS version expected to be common across all servers? If there is a flexibility, adding a new OS version considered as new blueprint or a new version of existing blueprint? New version? 3. Any support for new site level orchestrator requires new blueprint. Yes? 4. Any support for new SDN controller requires new blueprint. Yes? 5. Any support for new fabric switches requires new blueprint. Yes? 6. Any addition of additional SW packages to NFVI requires new blueprint. Yes? 7. If there is a version change in Openstack (say moving from Newton to Pike), SDN Controller or K8S, does it require new blueprint or a new version of the blueprint? New version?
Just few questions for discussions J
Thanks Srini
|
||||
|
|
||||
|
Re: Akraino Charter
ildiko@...
Hi,
toggle quoted message
Show quoted text
I got a little confused on one part of the description below. What does “is also a home for Edge related open source projects for the functionality where there is a gap in the open source community” mean exactly? Is Akraino a mid-stream project meaning that beyond integration and testing it will also identify gaps and work together with other communities to address them in the open source projects? Or saying it is the home for those gaps means that it would be Akraino hosting the code for that missing functionality? Thanks, Ildikó On 2018. Sep 4., at 11:49, Srini <srinivasa.r.addepalli@...> wrote: |
||||
|
|
||||
|
Locked
Re: Akraino community call on Thursday September 6 11-12 Eastern Time
Tapio Tallgren <tapio.tallgren@...>
Yes, the idea is that this would be a weekly call.
From: main@... <main@...> on behalf of Margaret Chiosi <margaret.chiosi1@...>
Sent: Wednesday, September 5, 2018 11:00:41 PM To: main@... Subject: Re: [akraino] Akraino community call on Thursday September 6 11-12 Eastern Time Is this the weekly call set?
Thank You, Margaret Chiosi VP Open Ecosystem Team Admin: Sophie Johnson Sophie.johnson1@... +1 (908) 541-3590 Futurewei Technologies, Inc. Fixed Network Solution CC 400 Crossing Blvd Bridgewater, NJ 08807 (cell) +1-732-216-5507 -----Original Message----- From: main@... [mailto:main@...] On Behalf Of Tapio Tallgren Sent: Wednesday, September 05, 2018 3:34 PM To: main@... Subject: [akraino] Akraino community call on Thursday September 6 11-12 Eastern Time Hi all, Similar to other open source projects, Akraino will have a regular community call where members of the developer community can discuss issues in more depth than what can be done in for example the Technical Steering Committee (TSC) calls. The very first call be on Thursday, September 6th, starting at 11 Eastern Time. The topics in the community call will vary depending on the ongoing discussions in the mailing lists. For this first event, I can give a summary of the developer event and give an overview on the governance documents that the TSC is working on. A discussion topic is blueprints and horizontal projects -- these may not be the final names. Link to the event is: https://wiki.akraino.org/display/AK/Technical+Community Welcome to join! |
||||
|
|
||||
|
Locked
Re: Akraino community call on Thursday September 6 11-12 Eastern Time
Margaret Chiosi <margaret.chiosi1@...>
Is this the weekly call set?
toggle quoted message
Show quoted text
Thank You, Margaret Chiosi VP Open Ecosystem Team Admin: Sophie Johnson Sophie.johnson1@... +1 (908) 541-3590 Futurewei Technologies, Inc. Fixed Network Solution CC 400 Crossing Blvd Bridgewater, NJ 08807 (cell) +1-732-216-5507 -----Original Message-----
From: main@... [mailto:main@...] On Behalf Of Tapio Tallgren Sent: Wednesday, September 05, 2018 3:34 PM To: main@... Subject: [akraino] Akraino community call on Thursday September 6 11-12 Eastern Time Hi all, Similar to other open source projects, Akraino will have a regular community call where members of the developer community can discuss issues in more depth than what can be done in for example the Technical Steering Committee (TSC) calls. The very first call be on Thursday, September 6th, starting at 11 Eastern Time. The topics in the community call will vary depending on the ongoing discussions in the mailing lists. For this first event, I can give a summary of the developer event and give an overview on the governance documents that the TSC is working on. A discussion topic is blueprints and horizontal projects -- these may not be the final names. Link to the event is: https://wiki.akraino.org/display/AK/Technical+Community Welcome to join! |
||||
|
|
||||
|
Locked
Akraino community call on Thursday September 6 11-12 Eastern Time
Tapio Tallgren <tapio.tallgren@...>
Hi all,
Similar to other open source projects, Akraino will have a regular community call where members of the developer community can discuss issues in more depth than what can be done in for example the Technical Steering Committee (TSC) calls. The very first call be on Thursday, September 6th, starting at 11 Eastern Time. The topics in the community call will vary depending on the ongoing discussions in the mailing lists. For this first event, I can give a summary of the developer event and give an overview on the governance documents that the TSC is working on. A discussion topic is blueprints and horizontal projects -- these may not be the final names. Link to the event is: https://wiki.akraino.org/display/AK/Technical+Community Welcome to join! |
||||
|
|
||||
|
Re: Akraino Charter
Thomas Nadeau
Cool. I think we are all on the same page now. --Tom On Wed, Sep 5, 2018 at 2:23 PM Wenjing Chu <Wenjing.Chu@...> wrote:
|
||||
|
|
||||
|
Re: Akraino Charter
Wenjing Chu <Wenjing.Chu@...>
Visibility is the same whether we call it project or blueprint. I’m fine with either name.
Do note that if blueprint A and blueprint B share a component developed within Akraino, we will then need to create another blueprint C, as you suggested, and A and B would have dependency on C. The key point here that Srini brought up is that we explicitly state that functionality development is in scope for Akraino. Wenjing From: Thomas Nadeau
To: main<main@...>
Subject: Re: [akraino] Akraino Charter
Time: 2018-09-05 08:00:05
The idea for doing everything in blueprints is that it brings visibility into any work that impacts the project to both the TSC, but also clearly in writing so any others (i.e.: integration, testing, etc...) that might be external to the project
have clear information about what is planned or underway. On a related note, I view blue prints as being largely analogous to epics, and in the same way are a good way to plan for a current or future release, and just a good way to organize the moving parts
of a large project like this one potentially can turn out to be.
--Tom
|
||||
|
|
||||
|
Re: Akraino Charter
Thomas Nadeau
The idea for doing everything in blueprints is that it brings visibility into any work that impacts the project to both the TSC, but also clearly in writing so any others (i.e.: integration, testing, etc...) that might be external to the project have clear information about what is planned or underway. On a related note, I view blue prints as being largely analogous to epics, and in the same way are a good way to plan for a current or future release, and just a good way to organize the moving parts of a large project like this one potentially can turn out to be. --Tom On Tue, Sep 4, 2018 at 7:30 PM Wenjing Chu <Wenjing.Chu@...> wrote:
|
||||
|
|
||||
|
Re: Akraino Charter
Wenjing Chu <Wenjing.Chu@...>
As long as we agree that such work should take place in Akraino, then it’s just naming. Yes, we could have a “non-integration blueprint”, but it seems really confusing to me.
Wenjing
From: main@... [mailto:main@...]
On Behalf Of Thomas Nadeau
Sent: Tuesday, September 04, 2018 1:34 PM To: main@... Subject: Re: [akraino] Akraino Charter
On Tue, Sep 4, 2018 at 2:47 PM Wenjing Chu <Wenjing.Chu@...> wrote:
Why wouldn't you do a blueprint for those too - perhaps a shorter blue print?
--Tom
|
||||
|
|
||||
|
Re: Akraino Charter
Thomas Nadeau
On Tue, Sep 4, 2018 at 2:47 PM Wenjing Chu <Wenjing.Chu@...> wrote:
Why wouldn't you do a blueprint for those too - perhaps a shorter blue print? --Tom
|
||||
|
|
||||
|
Re: Akraino Charter
Pasi Vaananen
On 09/04/2018 12:49 PM, Srini wrote:
It is not clear at all whether Akraino is the right owner for the APIs or not --- many other projects and communities are working on addressing the pieces of this rather large & diverse puzzle (ONAP, CNCF/k8s, various projects in OPNFV & OpenStack, etc. etc.), and IMHO, the last think that we need is more duplication for the ongoing efforts which would result in even more fragmentation of the landscape. So, whenever possible, optimally Akraino would pull from upstreams like OPNFV does and identify/address the gaps. Obviously in the cases where there is nothing (or existing approaches are deemed unsuitable / unfixable after careful consideration), Akraino could be in good position to resolve. I am saying the above, as ownership of the APIs does and should
belong to the projects implementing them, not something like
Akraino. If it is identifying, selecting and requesting additions
/ modifications, or Akraino hosted development projects, then that
would be ok. Blueprint for the infrastructure is expected to make
some selections for the projects that go in, so that implicitly
makes some picks on the APIs as well - but that would not make
Akraino "developer" for such cases, more like Endorser / selector. That said, there is very much confusion between the ONAP edge as
well as Akraino (on both sides) on who is going to do what and
when which should get resolved sooner rather than later, as the
context of the comment was "regional orchestration". Pasi
|
||||
|
|
||||
|
Re: Akraino Charter
Wenjing Chu <Wenjing.Chu@...>
Very good point. We do need to clarify this as soon as possible.
In the initial draft on blueprints, I proposed that we (a) use “project” as a unit for all the development work in Akraino, and (b) categorize projects into 2 types: functional projects and blueprint integration projects. (b) is similar to what Kandan called “vertical” and “horizontal”, but uses terms closer to those in other communities.
- Functional projects develop functionalities to fill identified gaps. - Integration projects are responsible to deliver end-to-end ‘blueprints’. Integration projects can utilize the outputs of functional projects, and all upstream open source projects.
Wenjing
From: main@... [mailto:main@...]
On Behalf Of Srini
Sent: Tuesday, September 04, 2018 9:50 AM To: main@... Subject: [akraino] Akraino Charter
Hi Akraino TSC,
In the last developer conference, TSC has taken an AI to come out with the Akraino charter definition. Much of the discussion on last developer conference is mostly about blueprints, except for one break-out session.
In regional orchestration, Edge API and AI breakout session, we talked about the need for them and the consensus is that Akraino project is the right place to develop them. In one of the Kandan’s presentation, it was clear that Akraino is not only for developing blueprints for various use cases, but is also a home for Edge related open source projects for the functionality where there is a gap in the open source community. Please consider making the Akraino charter clear on the aspect of development projects to avoid any confusion.
Thanks Srini
|
||||
|
|
||||
|
Akraino Charter
Srini
Hi Akraino TSC,
In the last developer conference, TSC has taken an AI to come out with the Akraino charter definition. Much of the discussion on last developer conference is mostly about blueprints, except for one break-out session.
In regional orchestration, Edge API and AI breakout session, we talked about the need for them and the consensus is that Akraino project is the right place to develop them. In one of the Kandan’s presentation, it was clear that Akraino is not only for developing blueprints for various use cases, but is also a home for Edge related open source projects for the functionality where there is a gap in the open source community. Please consider making the Akraino charter clear on the aspect of development projects to avoid any confusion.
Thanks Srini
|
||||
|
|
||||
|
Locked
Akraino Edge Stack: Availability of Slides from Presentations
Annie Fisher <afisher@...>
Greetings all, Slide decks from the presentations from the Akraino Developer Summit are uploaded to the wiki: https://wiki.akraino.org/display/AK/Akraino+Edge+Stack+-+Summit+2018 Reminder: You will need your LF ID to log-in to the Arkaino Wiki. If you need to create and LF ID or need help in retrieving your password, please find the directions to do so below: Creating a Linux Foundation ID:
If you do not know your password, or if you do not have a password because you created your account by clicking on the Google, Facebook, or Github buttons, you must reset your password. To reset your password, visit https://identity.linuxfoundation.org/ and ensure you are logged out. Then, click “Request n Annie Fisher, MPA CSM Program Manager, The Linux FoundationLocation & Time-zone: San Francisco, CA, PT |
||||
|
|
||||
|
Locked
Akraino Edge Stack: Remote access for Day 1
Annie Fisher <afisher@...>
Greetings all, We'd like to thank AT&T for making arrangements for remote access for DAY 1 of the Arkraino Edge Stack Developer Summit. PLEASE NOTE: Remote access will NOT be available for Day 2. All slide decks from all sessions will be available on the wiki shortly following the event. Please utilize the following options for access and you'll find the agenda for the day attached. Programming will begin at 8:45 a.m. with the Welcome Address by Arpit Joshipura, General Manager, Linux Foundation. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/928744900 Or iPhone one-tap : US: +16465588656,,928744900# or +16699006833,,928744900# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free) Meeting ID: 928 744 900 International numbers available: https://zoom.us/u/dlhyg3aHO Annie Fisher, MPA CSM Program Manager, The Linux FoundationLocation & Time-zone: San Francisco, CA, PT |
||||
|
|
||||
|
Locked
Re: Invitation: Akraino Edge Stack Developer Summit // August 23-34 // Middleton, NJ
Ponnath, Krishna (Nokia - US/Plano)
Thanks a lot . Really looking forward to the dial in option.
Krishna
From: main@... <main@...>
On Behalf Of Annie Fisher
Sent: Monday, August 20, 2018 2:34 PM To: main@... Cc: tianjijiang@... Subject: Re: [akraino] Invitation: Akraino Edge Stack Developer Summit // August 23-34 // Middleton, NJ
Greetings Melvin,
Thank you for your email. We are working with the site team to record the sessions and possibly have a dial-in option. We will send out this information tomorrow, if possible.
Regardless, all decks will be collected and distributed after the event.
Cheers, Anne
Annie Fisher, MPA CSM Program Manager, The Linux Foundation Location & Time-zone: San Francisco, CA, PT email: afisher@...
On Mon, Aug 20, 2018 at 12:31 PM Melvin Hillsman <mrhillsman@...> wrote:
|
||||
|
|
||||
|
Locked
Re: Invitation: Akraino Edge Stack Developer Summit // August 23-34 // Middleton, NJ
Annie Fisher <afisher@...>
Greetings Melvin, Thank you for your email. We are working with the site team to record the sessions and possibly have a dial-in option. We will send out this information tomorrow, if possible. Regardless, all decks will be collected and distributed after the event. Cheers, Anne Annie Fisher, MPA CSM Program Manager, The Linux FoundationLocation & Time-zone: San Francisco, CA, PT On Mon, Aug 20, 2018 at 12:31 PM Melvin Hillsman <mrhillsman@...> wrote:
|
||||
|
|
||||
|
Locked
Re: Invitation: Akraino Edge Stack Developer Summit // August 23-34 // Middleton, NJ
Is there any possibility this will be recorded and/or streamed? On Mon, Aug 20, 2018 at 2:24 PM Annie Fisher <afisher@...> wrote:
|
||||
|
|
||||
|
Locked
Re: Invitation: Akraino Edge Stack Developer Summit // August 23-34 // Middleton, NJ
Annie Fisher <afisher@...>
Greetings Tianji, Thank you for your email. We'd love to have you at the event and have fixed the registration page, so please register now for the event. Cheers, Annie Annie Fisher, MPA CSM Program Manager, The Linux FoundationLocation & Time-zone: San Francisco, CA, PT On Mon, Aug 20, 2018 at 12:07 PM Tianji Jiang <tianjijiang@...> wrote:
|
||||
|
|
