|
ONS NA 2019 Un-Conference - Leverage OPNFV Test Frameworks
Please note this un-conference discussion on Fri 4/5 15:10
Short Description: Explore opportunities for your LFN project to accelerate development of test frameworks, tools and methods through
Please note this un-conference discussion on Fri 4/5 15:10
Short Description: Explore opportunities for your LFN project to accelerate development of test frameworks, tools and methods through
|
By
Trevor Cooper
·
#79
·
|
|
04/05/2019 Akarino TSC F2F
04/02 & 04/05 TSC F2F Meeting
When:
Tuesday, 2nd April 2018
Friday, 5th April 2018
Where:
San Francisco Bay Area, Santa Clara, CA (further details to follow) or Zoom Dial In
Organizer:
tsc@...
An
04/02 & 04/05 TSC F2F Meeting
When:
Tuesday, 2nd April 2018
Friday, 5th April 2018
Where:
San Francisco Bay Area, Santa Clara, CA (further details to follow) or Zoom Dial In
Organizer:
tsc@...
An
|
By
Sujata Tibrewala
·
#78
·
|
|
Re: Akraino Mail Lists Update - ACTION REQUIRED
Akraino Community,
Reminder: If you have not done so, please take a minute to subscribe to the new subgroups created for TSC and Technical-Discussions if you would like to be included in those
Akraino Community,
Reminder: If you have not done so, please take a minute to subscribe to the new subgroups created for TSC and Technical-Discussions if you would like to be included in those
|
By
Jacqueline Z Cardoso
·
#77
·
|
|
Re: [tsc-private] Akraino Blueprint Technical Charter
+1 like the organization proposal
Thank You,
Margaret Chiosi
VP Open Ecosystem Team
Admin: Sophie Johnson
Sophie.johnson1@...
+1 (908) 541-3590
Futurewei Technologies, Inc.
Fixed Network
+1 like the organization proposal
Thank You,
Margaret Chiosi
VP Open Ecosystem Team
Admin: Sophie Johnson
Sophie.johnson1@...
+1 (908) 541-3590
Futurewei Technologies, Inc.
Fixed Network
|
By
Margaret Chiosi <margaret.chiosi1@...>
·
#76
·
|
|
FW: [tsc-private] Akraino Blueprint Technical Charter
Resending to main@... as requested by moderator. So some may already seen this - apologies if so.
There is also very interesting suggestion from Frank of a higher level classification
Resending to main@... as requested by moderator. So some may already seen this - apologies if so.
There is also very interesting suggestion from Frank of a higher level classification
|
By
Andrew Wilkinson
·
#75
·
|
|
Re: Use cases and Blueprints
Looks like the main@ list is rejecting new topics now. I guess the intention is moving all these to:
technical-discuss@...
or
tsc@...
Right now, these new groups have very few subscribers. You
Looks like the main@ list is rejecting new topics now. I guess the intention is moving all these to:
technical-discuss@...
or
tsc@...
Right now, these new groups have very few subscribers. You
|
By
Wenjing Chu <Wenjing.Chu@...>
·
#74
·
|
|
Re: Use cases and Blueprints
We (TSC) are putting together a draft with all the terminologies this community to use and a process around it. As we promised in the yesterday’s community call, we will review the draft on next
We (TSC) are putting together a draft with all the terminologies this community to use and a process around it. As we promised in the yesterday’s community call, we will review the draft on next
|
By
KATHIRVEL, KANDAN
·
#73
·
|
|
Re: Use cases and Blueprints
I may have missed some threads, but I thought we were discussing
1) Integration Blueprints (architecture)
2) Functional Blueprints (components)
I agree with some of the other comments
I may have missed some threads, but I thought we were discussing
1) Integration Blueprints (architecture)
2) Functional Blueprints (components)
I agree with some of the other comments
|
By
Glenn Seiler
·
#72
·
|
|
Re: Use cases and Blueprints
Actually I would have thought integration meant ‘testing’ and functional meant architectureJ
But as long as we define the different blueprints and the definition of them.
Thank You,
Margaret
Actually I would have thought integration meant ‘testing’ and functional meant architectureJ
But as long as we define the different blueprints and the definition of them.
Thank You,
Margaret
|
By
Margaret Chiosi <margaret.chiosi1@...>
·
#71
·
|
|
Re: Use cases and Blueprints
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
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
|
By
Margaret Chiosi <margaret.chiosi1@...>
·
#70
·
|
|
Re: Akraino Mail Lists Update - ACTION REQUIRED
--snip--
My understanding of the underlying list platform we're using is that the
main list can't be renamed.
-Andy-
--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation
--snip--
My understanding of the underlying list platform we're using is that the
main list can't be renamed.
-Andy-
--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation
|
By
Andrew Grimberg
·
#69
·
|
|
Re: Use cases and Blueprints
<andrew.wilkinson@...> wrote:
I tend to agree. The term "blueprint" in Akraino is already confusing
enough, even without using it also in the OpenStack Blueprint kind of
sense ;)
--
Frank
<andrew.wilkinson@...> wrote:
I tend to agree. The term "blueprint" in Akraino is already confusing
enough, even without using it also in the OpenStack Blueprint kind of
sense ;)
--
Frank
|
By
fzdarsky@...
·
#68
·
|
|
Re: Akraino Mail Lists Update - ACTION REQUIRED
<agrimberg@...> wrote:
Understood, np. Sorry for the noise.
--
Frank Zdarsky | NFV&SDN Technology Strategy, Office of the CTO | Red Hat
e: fzdarsky@... | irc:
<agrimberg@...> wrote:
Understood, np. Sorry for the noise.
--
Frank Zdarsky | NFV&SDN Technology Strategy, Office of the CTO | Red Hat
e: fzdarsky@... | irc:
|
By
fzdarsky@...
·
#67
·
|
|
Re: 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
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
|
By
Andrew Wilkinson
·
#66
·
|
|
Re: Akraino Mail Lists Update - ACTION REQUIRED
<jserafin@...> wrote:
Would it make sense to rename this to "announce@..." then?
--
Frank Zdarsky | NFV&SDN Technology Strategy, Office of the CTO | Red Hat
e: fzdarsky@... |
<jserafin@...> wrote:
Would it make sense to rename this to "announce@..." then?
--
Frank Zdarsky | NFV&SDN Technology Strategy, Office of the CTO | Red Hat
e: fzdarsky@... |
|
By
fzdarsky@...
·
#65
·
|
|
Re: 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
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
|
By
Margaret Chiosi <margaret.chiosi1@...>
·
#64
·
|
|
Akraino Mail Lists Update - ACTION REQUIRED
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
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
|
By
Jacqueline Z Cardoso
·
#63
·
|
|
locked
Topics for Akraino community call on September 13th?
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
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
|
By
Tapio Tallgren
·
#61
·
|
|
Re: Akraino Charter
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
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
|
By
fzdarsky@...
·
#60
·
|
|
Re: Akraino Charter
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
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
|
By
Srini
·
#59
·
|