clean deploy.
20170808 build better - 5 containers now ( - still missing traversal:8446,
api:8443 and model-loader)
after AAI-134<https://jira.onap.org/browse/AAI-134> resources:8447 is up -
however the wait check is still failing
I would think that the commit should have fixed this - p
Hi Kenny,
According to pre-Email, since ESR has been approved as a sub project of AAI and
the original committers from AAI may not that clear about the code of ESR. So I
hope Qi Sun and I could be added as committers of AAI and have the authority
to review the ESR code. And Jimmy(PTL of AAI
Hello ONAP Community Members:
We have confirmed the following high level agenda for the next ONAP
Developer Face to Face meeting to be held at the Nokia facility in
Paris-Saclay, France.
Monday, Sept. 25th, 13:00 - 17:00: Early Bird Sessions (Optional) for
those able to arrive on Monday
Tuesday,
Hi all,
Please find here the updated agenda with preliminary questions received from
Architecture subcommittee (thanks, Chris!):
1.Usecase subcommittee will present R1 use cases (Yoav/Kang - vCPE,
Chengli/Yang - vVoLTE) and provide brief overview of R2 discussions, including
emphas
I am pleased to announce the availability of the ONAP Bitergia dashboard to the
Community.
http://onap.biterg.io/ No password is required.
The dashboard offers the view for 4 different data sources:
* Git: https://onap.biterg.io/app/kibana#/dashboard/Git
* Gerrit: https://onap.biterg.io/app/kib
Hi, Brian
Maybe here is the old question. Is there a common model for WAN description
in SDN-C? If no, where should SDN-C get the input of adapter?
Thank you!
黄卓垚huangzhuoyao
职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.
深圳市南山区科技南路55号中兴
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20170809T13Z
DTEND:20170809T14Z
DTSTAMP:20170808T073229Z
ORGANIZER;CN=ONAP:mailto:f26tu6tqeqou1li98n7uvq66d0@group.calendar.google.c
om
UID:2n2h4j8ig0q2p3nku
If you look at the SLI-API tutorial for VoLTE on the wiki you can get a sense
of how this is accomplished. Here a set node is used but all the value’s could
references to context memory variables.
Device.* schema is defined by the adaptor (in this case the DC Gateway vendor’s
API)
As a
The adaptor should define its inputs as parameters in the adaptor node.
The schema for those paramters can be defined by the adaptor/vendor.
The directed graph will map from the WAN model into the vendor specific mode in
the adaptor.
We are going to recomend using a model called the GENERIC-RES