[INTPAK-17] Run ODL tests in RPM tests Created: 01/Nov/17  Updated: 04/Apr/18

Status: Open
Project: integration-packaging
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Medium
Reporter: Daniel Farrell Assignee: Daniel Farrell
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Should talk to Int/Test (jluhrsen) about suggestions for some basic sanity tests we can run against ODL after a deployment (RPM/puppet-opendaylight/ansible-opendaylight/VM/container).

Imported from Trello



 Comments   
Comment by Daniel Farrell [ 24/Jan/18 ]

jluhrsen - Any suggestions for some simple tests I can run against ODL after it's installed to check if it's working?

Comment by Jamo Luhrsen [ 24/Jan/18 ]

dfarrell07 which features are installed? odl-netivrt-openstack?

off the top of my head:

  • curl -i -u "admin:admin" http://${ODL_IP}:8181/restconf/streams
    • should return 200 and a small json response {"streams":{}}
  • check netstat that certain ports are lit up
    • 6633 (openflow) AND 6653 actually
    • 6640 (ovsdb)
    • 8181 (restconf) or whatever port the deploy tweaked it to
  • curl to this guy:  restconf/operational/network-topology:network-topology/topology/netvirt:1
    • should get a 200 and this: {"topology":[ {"topology-id":"netvirt:1"}

      ]}

  • we could find smart things to grep from karaf.log
  • we could pull down the opnfv/cperf docker container and run some robot suites pretty easily. I have some work to do that in other places I could dig up and see if it "just works". We couldn't really do netvirt csit (it requires openstack too), but there are some basic things (e.g. aaa CSIT) that might work pretty nicely

that's probably a good starting point and would be a nice feather in our (YOUR) hat.

Comment by Daniel Farrell [ 07/Feb/18 ]

https://git.opendaylight.org/gerrit/#/c/67592/

https://git.opendaylight.org/gerrit/#/c/67759/

Generated at Wed Feb 07 20:03:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.