Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

1

Use of RESTCONF v/s REST API

asked 2014-11-12 22:48:32 -0800

screwgoth gravatar image

updated 2014-11-12 23:16:45 -0800

I understand that Helium uses the MD-SAL based RESTCONF API (when not using odl-adsal-compatibility feature) and Hydrogen used the AD-SAL based REST API. I have written a Management application which calls all the AD-SAL REST APIs. So, will this AD-SAL REST API support be there always ? Currently, MD-SAL RESTCONF does not give as much info as the REST API. Is this going to be expanded, so that if AD-SAL is not going to be supported, I can get the same info from the RESTCONF APIs ?

edit retag flag offensive close merge delete

Comments

Could you be more specific which information is not provided by RESTCONF API and open enhancement requests for it?

Tony Tkacik ( 2014-11-14 06:38:36 -0800 )edit

I'm basically using ALL the REST APIs from TopologyManager , SwitchManager, Statistics Manager, FlowProgrammer and ConnectionManager. Is the info I get and the config I can set available in the RESTCONF API as well ?

screwgoth ( 2014-11-16 10:17:39 -0800 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2015-01-08 11:59:38 -0800

bsvTag gravatar image

I have the same problem to solve. According to link , AD-SAL may be marked as deprecated in Lithium release, and no one is supporting it in a current release. So, use of MD-SAL is the proper way to make long-term project.

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2014-11-12 22:48:32 -0800

Seen: 1,789 times

Last updated: Jan 08 '15