Bryan,
I have been meaning to speak to you about where the servers for
Auto integration testing should reside. Do I read correctly your suggestion
that the proposed LaaS (hosting provider yet to be selected) lab? This could
make sense as this seem precisely the sort of cross project use case for a
shared lab… I do worry this is a bit further out with many questions to be
answered first.
NOTE: I know that I owe some hardware recommendation for the ARM
server spec in LaaS wiki page, our engineers just have their heads down on
Euphrates. I am others have been a bit shocked to see discussion of ONAP
scenarios ideally having 150GB (I think it was 256GB before) DRAM recommended.
I hope for ONAP’s sake this is a special case for certain scenarios- seems very
high and potentially leading to a requirement for really expensive servers (not
just the memory itself).
Any elaboration on this memory requirement?
Any distinction between controllers and compute nodes, or is this not an
appropriate distinction with regards to ONAP?
Regards,
Bob
Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman
From: [email protected]
[mailto:[email protected]] On Behalf Of Ed Warnicke
Sent: Wednesday, August 2, 2017 5:39 PM
To: SULLIVAN, BRYAN L <[email protected]>
Cc: [email protected]
Subject: Re: [opnfv-tech-discuss] ONAP-OPNFV Lab Integration Status
Brian,
Apologies, I've been underwater this week, and will need to get to this next
week. I *did* want you to know you'd been heard.
Ed
On Thu, Jul 27, 2017 at 7:11 AM, SULLIVAN, BRYAN L
<[email protected]<mailto:[email protected]>> wrote:
Hi Ed,
This is an update on the ONAP-OPNFV lab integration discussion we had after the
OPNFV Summit. I’d appreciate your passing on this info to the ONAP TSC and will
keep you updated as it progresses.
The concept for lab integration is shown at Lab as a
Service<https://wiki.opnfv.org/display/INF/Lab+as+a+Service> in which on-demand
or automated (CI/CD) ONAP-OPNFV lab integration is one scenario (Use Case: ONAP
Developer Access to On-Demand OPNFV+ONAP POD). In the OPNFV Infra team calls we
are continuing to discuss such topics as:
* How we would resource development of the dashboard and other functions
that would enable this
* Whether in some cases we should integrate ONAP as a deployed component in
an OPNFV POD (e.g. as earlier considered by the Opera
project<https://wiki.opnfv.org/display/OPERA/Opera+Home>), and if so what would
be impact on
* Hardware requirements: our current understanding is that this is at
least 150GB for ONAP VMs
* Deploy job duration, when including ONAP deployment
* Whether it will be possible to deploy only specific ONAP components as
needed for a particular test or scenario
* This will be considered as part of the proposed Auto project ref’d
below
* What labs would host the LaaS components for ONAP
We need to come to a pretty good understanding of those aspects before, as a
community, we reach out to ONAP with a specific proposal. In the meantime
however, as we address those questions, OPNFV projects will continue to work on
them tactically:
* As of the OPNFV Summit, the Opera project team has set a goal to continue
that ONAP deployment focus as described in the video of the talk:
<https://www.youtube.com/watch?v=CiJwC-ClcHE> ONAP Integration with OPNFV via
Opera - Yingjun Li, Chengli Wang<https://www.youtube.com/watch?v=CiJwC-ClcHE>
* ONAP-Automated OPNFV
(Auto)<https://wiki.opnfv.org/pages/viewpage.action?pageId=12387216> is a new
project proposal which will focus on integration/verification of specific ONAP
components over time, as compared to
Opera’s<https://wiki.opnfv.org/display/OPERA/Opera+Home> goal of developing
OPNFV-installer supported scenarios that can deploy and verify ONAP as a whole.
* How the Auto and Opera projects will collaborate across these different
project focuses is a discussion we will have leading up to OPNFV TSC
presentation of the Auto project proposal in a couple of weeks.
I’ll keep you updated as this progresses.
Thanks,
Bryan Sullivan | AT&T
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
