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

Akraino Community, In order to facilitate future discussions in clearly delineated forums utilizing open source project best practices we have made changes to the mail lists available for this

Hi all, We have scheduled the second Akraino community call for Thursday, September 13th. Since a lot of the people who have contributed to the blueprint discussion on the mailing list have

So selectively backporting patches from upstream's master into upstream's stable branch. That's something we might want to do in the upstream branch, too, but I can see the need for exceptions to

Hi Frank, On this: “ - Is Akraino look to build the images/containers? Or limit the scope to installers, starting with Airship? If so, which sister project(s) going to build binary

I wasn’t thinking that we would have all these blueprints – so maybe we should update the draft definitions doc on scope of a blueprint. I thought the use case determined the scope. But then a

Are we converging that we are going to do both integration as well as development projects where necessary? I agree integration creates tools to do this better which is one form of development and we

Since I missed the meeting – my comments – I turned on tracking of changes. Thank You, Margaret Chiosi VP Open Ecosystem Team Admin: Sophie Johnson Sophie.johnson1@... +1 (908)

Hi Max: Looking at the logs, it appears you have connectivity issues to your LDAP server. Please note your LDAP server IP and that of the Regional Controller should be the same. Please run the

Hi Max: Looking at the logs, it appears you have connectivity issues to your LDAP server. Please note your LDAP server IP and that of the Regional Controller should be the same. Please run the

Hi, I was going through the emails and the pdfs from the Akraino summit to fully understand the definitions. I think we are getting closer and I am sure the TSC will come out with the official

I think many (most?) vendors who submit a blueprint do intend to support the exact specification of the blueprint they submit. Either as an in-house solution, or commercially as an ecosystem

Well said. +1. Focus on the goal, the end result, and be pragmatic on how to get there. Wenjing From: spatsch To: main<main@...> Subject: Re: [akraino] Akraino Charter Time: 2018-09-07 09:37:35

Catching up on this thread let me make a couple of comments. As we had discussed during the summit I think the TSC is working hard to formalize the precise definition of terms. That will be very

Hi Frank and all, On this: “For example, I very much like the way CNCF handles Kubernetes and its satellite projects like Linkerd, Jaeger, Envoy, Prometheus, etc: Those projects are independent

Hi, I want to set up one edge cloud using Akraino project. I am working on the first step now (installing the regional controller node). As my regional controller is not Dell R740 so i cannot use

Hi, Just one point to the comment: “but vendors will in most cases not support the exact combination as integrated/tested in Akraino,” I think that’s what we can enable with a given

Hi all, Following up on Margaret’s a very good point here: assuming that (for whatever reasons) OPNFV was not able to attract enough developers in the long run, I am wondering if creating a

Agree with Tina. We should avoid pure integration community problem. BR Bill Ren -----邮件原件----- 发件人: main@... [mailto:main@...] 代表 Tapio

Again: Being an integration project doesn't preclude doing development at all! It's simply a question of clarifying the primary mission. If people feel Akraino's main mission is development like in