REST/CLI: Customizable chain paths

[stevenvanrossem]

It is a good feature request to have custom VNF placement:

• you can add your own version instead of the default 'RoundRobinDcPlacementWithSAPs' algorithm.
• you can specify the datacenter at VNF instantiation via the rest api :
  curl -X PUT http://127.0.0.1:5001/restapi/compute/dc1/server -H 'Content-Type: application/json' -d '{"image":"sonatanfv/sonata-iperf3-vnf"
  or via the son-emu-cli:
  son-emu-cli compute start -d dc1 -n server -i sonatanfv/sonata-iperf3-vnf
• There is also the possibility to add custom paths to the chaining function, although I never tested this:
  https://github.com/sonata-nfv/son-emu/blob/master/src/emuvim/dcemulator/net.py#L537

Can we specify this path through the cli/rest api?

[mpeuster]

I think we can specify it through the networking REST API, or not?

Just for clarification, if you now do:

son-emu-cli compute start -d dc1 -n client -i sonatanfv/sonata-empty-vnf
son-emu-cli compute start -d dc2 -n server -i sonatanfv/sonata-empty-vnf

son-emu-cli network add -b -src client:client-eth0 -dst server:server-eth0

It will automatically use the shortest path between the dc1 and dc2 switch, right?

[stevenvanrossem]

yes, default is shortest path calculation

[stevenvanrossem]

the networking REST api/cli should support this path specification as an extra argument

[mpeuster]

yes, I agree this would be a cool extension 👍