Qipeng,

The created-rendered-path API is indeed no longer supported. That API
created the RSP (Rendered Service Path, which is the actual service chain),
but now the RSP gets created when the SFP (Service Function Path) is
created.

I thought this was already fixed in the sfc103 demo, but apparently not :)
I submit this patch to fix that and the number of features you reported
earlier:

https://git.opendaylight.org/gerrit/79533

Regards,

Brady



On Tue, Jan 15, 2019 at 12:38 AM Qipeng Song <[email protected]> wrote:

> Hello everyone!
>
> Recently I’m working on sfc103 demo.However I’m still stuck by the
> following POST request failure:
>
> POST
> http://192.168.1.5:8181/restconf/operations/rendered-service-path:create-rendered-path/
> {
>     "input": {
>         "name": "RSP2",
>         "parent-service-function-path": "SFP2",
>         "symmetric": "true"
>     }
> }
> {"errors":{"error":[{"error-type":"protocol","error-tag":"invalid-value","error-message":"URI
> has bad format. Possible reasons:\n 1.
> \"rendered-service-path:create-rendered-path\" was not found in parent data
> node.\n 2. \"rendered-service-path:create-rendered-path\" is behind mount
> point. Then it should be in format
> \"/yang-ext:mount/rendered-service-path:create-rendered-path\"."}]}}
> Traceback (most recent call last):
>   File "/sfc/sfc-demo/sfc103/update_sfc.py", line 160, in <module>
>     post(controller, DEFAULT_PORT, get_rendered_service_path_uri(),
> get_rendered_service_path_data(), True)
>   File "/sfc/sfc-demo/sfc103/update_sfc.py", line 44, in post
>     r.raise_for_status()
>   File "/usr/lib/python2.7/dist-packages/requests/models.py", line 840, in
> raise_for_status
>     raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 400 Client Error: Bad Request for url:
> http://192.168.1.5:8181/restconf/operations/rendered-service-path:create-rendered-path/
>
>
> I tried to find solutions in the mail archive. I found something related
> to my problem(I put it at the end of this mail). I want to know whether
> this API(created-rendered-path) is supported again in the latest ODL
> version? If no, do we have some workaround to solve this problem?
>
> Thanks very much.
>
> BR,
> Qipeng
>
> >* From: JaimeCaamaño Ruiz
> *>* Date: 2018-11-20 22:27
> *>* To: 喻晶洁
> *>* CC: sfc-dev
> *>* Subject: Re: OpenDaylight sfc-demo question
> *>* Hello
> *>  >* The demo is currently not working because it relies in an ODL API
> *>* (create-rendered-path) that has been removed since fluorine. I will
> *>* work on it in the following days to fix it.
> *>  >* BR
> *>* Jaime.
> *>  >* -----Original Message-----
> *>* From: 喻晶洁  <yujingjie at fiberhome.com 
> <https://lists.opendaylight.org/mailman/listinfo/sfc-dev>>
> *>* To: jcaamano at suse.de 
> <https://lists.opendaylight.org/mailman/listinfo/sfc-dev>
> *>* Subject: OpenDaylight sfc-demo question
> *>* Date: Tue, 20 Nov 2018 20:10:27 +0800
> *>  >* Hi, Dear Jaime,
> *>* I am studying the Opendaylight/sfc project. When doing an experiment
> *>* with sfc-demo/sfc103(https://github.com/opendaylight/sfc/tree/master/ 
> <https://github.com/opendaylight/sfc/tree/master/>
> *>* sf
> *>* c-demo/sfc103), I have a problem as figure below. When I run the
> *>* python
> *>* file setup_sfc.py, the RestAPI error always occur.
> *>* Could you give me some tips?
> *>* Run setup_sfc.py and show:
> *>  >* Run docker-compose and show:
> *>  >* ODL:
> *>  >  >  >* Thanks very much!*
>
>
> _______________________________________________
> sfc-dev mailing list
> [email protected]
> https://lists.opendaylight.org/mailman/listinfo/sfc-dev
>
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to