Looping in SDNC list 
([email protected]<mailto:[email protected]>).

Steven,

>From what I can see there are almost no docs at 
>http://onap.readthedocs.io/en/latest/index.html#<http://onap.readthedocs.io/en/latest/index.html>
> - I'm not even sure how the projects are supposed to add docs there.

I've added a task (https://jira.onap.org/browse/SDNC-72) for docs at 
readthedocs in JIRA but since we haven't talked about it there is no date to my 
mind. We will discuss at next call and figure out what is needed and who will 
do it.

In the mean time I believe the API are available as swagger url's/files as 
Brian mentioned - maybe Dan can point to how to access.

Thanks,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. - DataCenter Network Solutions Group

From: [email protected] 
[mailto:[email protected]] On Behalf Of WRIGHT, STEVEN A
Sent: Wednesday, August 30, 2017 1:57 PM
To: FREEMAN, BRIAN D <[email protected]>; TIMONEY, DAN <[email protected]>
Cc: GLOVER, GREG L <[email protected]>; [email protected]
Subject: Re: [onap-discuss] [SDNC] documentation on APIs

The release controlled ONAP documentation, including APIs, should all end up 
somewhere under here: 
http://onap.readthedocs.io/en/latest/index.html#<http://onap.readthedocs.io/en/latest/index.html>

But there's nothing there for SDN-C APIs at the moment.
There's lots of other things missing too, but the API's are kind of important 
... 8^}

best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

[email protected]<mailto:[email protected]>
www.linkedin.com/in/drstevenawright/<http://www.linkedin.com/in/drstevenawright/>

From: FREEMAN, BRIAN D
Sent: Wednesday, August 30, 2017 4:54 PM
To: WRIGHT, STEVEN A <[email protected]<mailto:[email protected]>>; TIMONEY, DAN 
<[email protected]<mailto:[email protected]>>
Cc: GLOVER, GREG L <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: RE: [SDNC] documentation on APIs

The NBI for SDNC is swagger based and I thought Dan had provided those swagger 
url's/files.

Brian


From: WRIGHT, STEVEN A
Sent: Wednesday, August 30, 2017 4:53 PM
To: FREEMAN, BRIAN D <[email protected]<mailto:[email protected]>>; TIMONEY, DAN 
<[email protected]<mailto:[email protected]>>
Cc: GLOVER, GREG L <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: RE: [SDNC] documentation on APIs

The question is when will the API documentation from the SDNC group be 
published at onap.readthedocs.io ?


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

[email protected]<mailto:[email protected]>
www.linkedin.com/in/drstevenawright/<http://www.linkedin.com/in/drstevenawright/>

From: FREEMAN, BRIAN D
Sent: Wednesday, August 30, 2017 4:48 PM
To: WRIGHT, STEVEN A <[email protected]<mailto:[email protected]>>; TIMONEY, DAN 
<[email protected]<mailto:[email protected]>>
Cc: GLOVER, GREG L <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: RE: [SDNC] documentation on APIs

Steven,

I dont understand the question. VNFs dont call SDNC , SDNC uses southbound 
protocols to configure VNFs like netconf, restconf , bgp, pcep, rest and as a 
last resort (and a large precentage) cli.

Brian


From: 
[email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of WRIGHT, STEVEN A
Sent: Wednesday, August 30, 2017 4:34 PM
To: TIMONEY, DAN <[email protected]<mailto:[email protected]>>
Cc: GLOVER, GREG L <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: [onap-discuss] [SDNC] documentation on APIs

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
With the API freeze at the M3 milestone, I am interested in  the availability 
of the Amsterdam release SDN-C API documentation from the SDN-C project.

I could find no  SDN-C API documentation on the Project 
wiki<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Software-2BDefined-2BNetwork-2BController-2BProject&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=74zf3kpCfkwgoHpIvYlXq6ynbNTAJqGK7DUlTv-i_Oo&e=>
 . The Documentation project  provides the documentation tool chain for all 
ONAP projects ( refer Documentation section M1 Release planning documentation). 
The Documentation Project tool chain delivers release-controlled ONAP 
documentation to 
http://onap.readthedocs.io/en/latest/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.readthedocs.io_en_latest_index.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=WqFUeIV9J33yUYM9jeCftWK382JHEjyLzaRvE8v6t_U&e=>

There is currently no documentation on SDN-C APIs available at  
http://onap.readthedocs.io/en/latest/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.readthedocs.io_en_latest_index.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=WqFUeIV9J33yUYM9jeCftWK382JHEjyLzaRvE8v6t_U&e=>
(The documentation tool chain/Jenkins jobs are up and working now for other 
projects)

Can the SDN-C project/PTL  identify a contact person to work on the 
documentation aspects of SDN-C?
Ideally the contact should be identified 
here<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Doc-2BProject-2BCoverage-2BMatrix&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=jE5FjYon5h0GFxI965j3TtjOY0z4dTA-f4OKL15mM3k&e=>.
The general process on documenting projects in ONAP is described 
here<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.readthedocs.io_en_latest_guide_onap-2Ddeveloper_how-2Dto-2Duse-2Ddocs_index.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=A9wJC69-V_nCtWamGiivrj-TtDBgClM5qDOyQ-UTllM&e=>.

VNFs have requirements to support SDN-C APIs. From VNFRQTS project, we are 
trying to complete 
VNFRQTS-87<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_VNFRQTS-2D87&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=JvCpt3cNWnU7uzoOXtXSGwGnSb2CMycgy0JO1F5qAO8&e=>
 in our current sprint-3.   To complete this, we need at least a chapter 
heading available at  
http://onap.readthedocs.io/en/latest/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.readthedocs.io_en_latest_index.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=WqFUeIV9J33yUYM9jeCftWK382JHEjyLzaRvE8v6t_U&e=>
 for our requirements deliverable to point to for SDN-C API documentation. Our 
VNFRQTS Sprint 3 is due to complete September 12, so  we would appreciate if 
you could have the SDN-C API documentation outline up at  
http://onap.readthedocs.io/en/latest/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__onap.readthedocs.io_en_latest_index.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=WqFUeIV9J33yUYM9jeCftWK382JHEjyLzaRvE8v6t_U&e=>
 within the next week.

Please advise if you need help to achieve this.


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

[email protected]<mailto:[email protected]>
www.linkedin.com/in/drstevenawright/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_drstevenawright_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=MAcfvgz4v8eevjz8WPfe_YpJIzVVF-uNqn6RE8e3CC4&s=_0h3pebnRSNODYnNqSQE3rr8iYgc7CcihkddB2WFmXQ&e=>

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to