I am using Oxygen for the Opendaylight and after installing the required features I am not able to view switches and host in Web Interface. I have created my topology in mininet.
I have followed the below link
https://docs.opendaylight.org/en/stable-oxygen/user-guide/using-the-opendaylight-user-interface-(dlux).html
That's not really enough info to help. have you checked that mininet switches are
connected to opendaylight from that persepective? I think you can use ovs commands
to see if it shows as is_connected:true (e.g. ovs-vsctl show)
also try doing a GET on the ODL NB REST API, like:
http://$ODL_IP:8181/restconf/operational/opendaylight-inventory:nodes
you can double check that dlux features are installed on the karaf console with
a command like "features:list -i | grep dlux"
btw, please note that because dlux no longer had any contributions to support it,
the project has been archived and it will no longer be a part of releases
after oxygen.
Related
I am trying to use OpenDaylight to communicate with network devices speaking NETCONF.
I have the newest release (NEON) with all NETCONF and RESTCONF features installed. I have tried several ways to access the northbound RESTCONF API. Unfortunately, neither dlux nor apiexplorer seem to work in the newest release.
When I try to access http://localhost:8181/apidoc/explorer or use restconf from APIs of former releases, I get 404 errors.
I am positive that ODL and restconf is running correctly, for I receive answers to my postman GET requests like
<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">
<error>
<error-type>protocol</error-type>
<error-tag>data-missing</error-tag>
<error-message>Mount point does not exist.</error-message>
</error>
</errors>
correct, the GUI frontends like dlux are no longer maintained or released with
OpenDaylight.
The GET response you show is working and telling you that the device you
are trying to retrieve does not exist. Is it mounted? What is the full
GET URL you are using?
here's one that works in a test environment I'm using:
curl -u admin:admin http://$ODL_SYSTEM_IP:8181/restconf/operational/network-topology:network-topology/topology/topology-netconf/node/$DEV_TYPE-netconf-scaling-device-10
but, note that $DEV_TYPE-netconf-scaling-device-10 is already mounted.
The link http://localhost:8181/apidoc/explorer/index.html did the trick. I just had to add the "index.html" at the end. Now it works like a charm.
I'm trying to implement Link aggregation control protocols using Opendaylight controller by following this guide :
On mininet i already running the network topology, configuring the bonding.
On the opendaylight i already running karaf and several feature needed to implement LACP.
The problem is when i already reach this step,
dump-groups command
the dump-groups command doesnt recognized. Attached the the error announcement image.
dump-groups unknown command
I hope you can help me solve this problem guys.
Thank you very much.
Already solved, the problem arise because the openvswitch version in my mininet VM is the old version.
After upgrade the openvswitch became version 2.3.1 the problem solved.
Thanks all.
Is there any opensource Web UI project for OpenWhisk?
I would like use OpenWhisk but not with IBM Bluemix.
Thanks.
There are a couple implementation I was able to find on GitHub, however haven't tested them:
https://github.com/katarzyna-dusza/openwhisk-react-ui
https://github.com/surawhisk/ui
Have you tried the IBM Cloud Functions Shell which combines a command-line interface and a graphical user interface for OpenWhisk. This works with both IBM Bluemix and any OpenWhisk deployment.
I am trying to develop an app using Opendaylight Nitrogen.
For debugging purposes, I want to delete all the flow rules that opendaylight has cached (these get re-installed when the switch reconnects). I want to delete these rules and restart the container to examine behavior. Where does Opendaylight store these (in which file)?
Thanks
Ranga
Delete karaf/target/../journal/ and karaf/target/../snapshots/ when you want to start fresh.
Karf clean deletes the karaf/target/assembly/data directory.
finally, you could also use the REST API to delete the flows on a running
controller. This documentation should help figure that out.
In order to know which revision number the application is built from, we use to give the ears we deploy to Glassfish names like myapp_2012-01-20_rev22123.ear. Then we can simply login to Glassfish and see what version is deployed in the web interface (as the appname is the name of the ear file). A downside of this approach is that we need to do a manual undeploy/redeploy to update the name...
But I would like to script the undeploy/deploy process, and having each version of an ear get a different name is not very suitable to scripting this redeployment process. Glassfish 2 does not support the "list applications" goal that Glassfish 3 has, which I could have used to retrieve the application name to undeploy.
So is there any good strategy that will easily allow us to see what version is deployed of an application, and that does not suffer from the above fault?
It would be preferable if this meant we did not have to change the existing applications (like add a jsp page or something to show the current scm revision), but a change in a Maven build script would be acceptable.
I faced a similar issue, I finally came around it by using maven-buildnumber-plugin and writing a simple servlet to get build information. You can find the details in the blog post I made.
Why not use the built-in GlassFish Server versioning to assign a version number at deploy time? This will also enable you to rollback to prior versions. For example:
asadmin deploy --name MyApplication:2012-01-20_rev22123 MyApplication.ear
There is more information on application versioning here:
http://docs.oracle.com/cd/E18930_01/html/821-2417/gihzx.html#gkhhv
Hope this helps.