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

Krishnasharma's profile - activity

2016-05-25 20:05:34 -0700 received badge  Famous Question (source)
2016-02-16 00:48:35 -0700 received badge  Famous Question (source)
2015-10-28 23:04:39 -0700 commented question SFC All in One setup, No response from SFF

HI, Do you see flows getting installed after SFP is created? Even I am stuck at same point. If you are running on NSH enabled OVS, give remotes-sff-port as 6633. THis might work only if you have flows installed

2015-10-28 22:40:10 -0700 asked a question Flows on OVS are not getting installed

Hi All,

I am trying to work SFC feature. I was able to bring ODL(Lithium-SR1 distribution version) with all necessary packages and was able to create SFF. But I see that there no flows getting added to OVS after SFP is created. Could anyone guide me through ?

2015-10-06 03:45:11 -0700 received badge  Famous Question (source)
2015-09-16 14:56:52 -0700 received badge  Notable Question (source)
2015-09-14 15:47:32 -0700 received badge  Notable Question (source)
2015-09-14 03:54:59 -0700 commented answer Neutron Not working with ODL

Any idea why we get NO hosts available when we try to launch instance from Horizon after succesful creation of network ?

2015-09-14 03:54:59 -0700 received badge  Commentator
2015-09-13 23:34:01 -0700 commented answer Neutron Not working with ODL

I am not getting network option with that local.conf

2015-09-13 23:32:52 -0700 received badge  Notable Question (source)
2015-09-09 05:23:45 -0700 commented answer Neutron Not working with ODL

I am getting "Unable to create the network. No tenant network is available for allocation." error now. Any idea ?

2015-09-09 04:47:16 -0700 commented answer Neutron Not working with ODL

COuld you share your local.conf and ml2_conf.ini ?

2015-09-09 04:44:55 -0700 received badge  Popular Question (source)
2015-09-09 02:49:35 -0700 commented answer Neutron Not working with ODL

I even checked with vlan as tenant network type in ml2_conf.ini But it still says post commit failed. Looks like there is issue with ODL listening to this request.

2015-09-09 02:22:08 -0700 commented answer Neutron Not working with ODL

root@ODLBuildMachine:~/krishna/odl# netstat -nap | grep 8080 tcp6 0 0 :::8080 :::* LISTEN 10384/java root@ODLBuildMachine:~/krishna/odl# ps -eaf | grep 10384 tomcat7 10384 2120 0 Sep07 ? 00:05:46 /usr/lib/jvm/java-7-openjdk-amd64//bin/java -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.awt.headless=true -Xmx128m -XX:+UseConcMarkSweepGC -Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar -Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 -Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp org.apache.catalina.startup.Bootstrap start root 27196 10526 0 14:50 pts/9 00:00:00 grep --color=auto 10384 root@ODLBuildMachine:~/krishna/odl# It's java which is running on 8080. Tenant network type is VxLAN. Should it be VLAN ?

2015-09-08 23:56:26 -0700 commented answer Neutron Not working with ODL

Hi Suman, URL has port as 8080. I did try with only these features odl-base-all odl-aaa-authn odl-restconf odl-nsf-all odl-adsal-northbound odl-mdsal-apidocs odl-ovsdb-openstack odl-ovsdb-northbound odl-dlux-core Still no luck. Any further suggestions will be helpful.

2015-09-07 08:45:37 -0700 received badge  Editor (source)
2015-09-07 08:29:48 -0700 commented question Neutron Not working with ODL

Thanks Mandeep for taking look into my issue. But Helium version also comes with adsal to mdsal compatible features. The URL is not accessible when I access it from browser or using CURL command as well. Ideally it should respond for curl command curl -u admin:admin http://ip-addr:8080/controller/nb/v2/neutron/networks with details of available network. But I get error message. As per suggestion I did check with 8181 port as well but it doesnt click. Thanks for you time Mandeep.

2015-09-07 07:12:02 -0700 asked a question Neutron Not working with ODL

Hi All,

I am working on integration of ODL(Helium SR3 distribution) with Openstack. Openstack(started using devstack) & OVS are running on one system and ODL is running on another system. As it's evident from all the possible sources available over net, I should be installing necessary packages. I have installed following packages odl-base-all odl-aaa-authn odl-restconf odl-adsal-northbound odl-mdsal-apidocs odl-l2switch-switch odl-ovsdb-all

Now I installed openstack using devstck and is running fine. But I see that openstack tries to communicate to ODL on port 8080 with URL as "odl-ip-addr":8080/controller/nb/v2/neutron.

But this URL is showing 404 error which says that required service is not available on that port. I tried to install odl-nfs-all as well but still dint succeed.

Output of web:list command looks something like this

opendaylight-user@root>web:list

ID | State | Web-State | Level | Web-ContextPath | Name

330 | Active | Deployed | 80 | /oauth2 | aaa-authn-sts (0.1.3.Helium-SR3)
333 | Active | Deployed | 80 | /auth | aaa-idmlight (0.1.3.Helium-SR3)
342 | Active | Deployed | 80 | /oauth2/federation | aaa-authn-federation (0.1.3.Helium-SR3)
346 | Active | Deployed | 80 | /restconf MD SAL Restconf Connector (1.1.3.Helium-SR3)
383 | Active | Failed | 80 | /controller/nb/v2/connectionmanager | connectionmanager.northbound (0.1.5.Helium-SR3)
384 | Active | Failed | 80 | /controller/nb/v2/flowprogrammer | flowprogrammer.northbound (0.4.5.Helium-SR3)
385 | Active | Failed | 80 | /controller/nb/v2/hosttracker | hosttracker.northbound (0.4.5.Helium-SR3)
386 | Active | Failed | 80 | /controller/nb/v2/networkconfig/bridgedomain | networkconfig.bridgedomain.northbound (0.0.6.Helium-SR3) 387 | Active | Failed | 80 | /controller/nb/v2/neutron | networkconfig.neutron.northbound (0.4.5.Helium-SR3)
388 | Active | Failed | 80 | /controller/nb/v2/staticroute | forwarding.staticrouting.northbound (0.4.5.Helium-SR3)
389 | Active | Failed | 80 | /controller/nb/v2/statistics | statistics.northbound (0.4.5.Helium-SR3)
390 | Active | Failed | 80 | /controller/nb/v2/subnetservice | subnets.northbound (0.4.5.Helium-SR3)
391 | Active | Failed | 80 | /controller/nb/v2/switchmanager | switchmanager.northbound (0.4.5.Helium-SR3)
392 | Active | Failed | 80 | /controller/nb/v2/topology | topology.northbound (0.4.5.Helium-SR3)
393 | Active | Failed | 80 | /controller/nb/v2/usermanager | usermanager.northbound (0.0.5.Helium-SR3)
394 | Active | Deployed | 80 | /apidoc | MD SAL Rest Api Doc Generator (1.1.3.Helium-SR3)
409 | Active | Failed | 80 | /ovsdb/nb | OpenDaylight OVSDB Northbound APIs (0.6.3.Helium-SR3)
418 | Active | Failed | 80 | /controller/nb/v2/vtn | manager.northbound (0.2.3.Helium-SR3)
opendaylight-user@root>

I am using Helium SR3 distribution version and have verified that port 8080 is up and listening.

When I try to create network from Openstack UI , I end up getting "Createnetworkpostcommit" falied. I have ensured connectivity from both the systems.

This is the error log when I am creating network from Openstack CLI

devstack@devstack:~/devstack$ neutron net-create --debug --tenant-id c69a198cb6ec436591e96dce4a68aa81 private DEBUG: keystoneclient.session REQ: curl -g -i -X GET http://192.168.0.112:35357/v2.0 -H "Accept: application/json" -H "User-Agent: python-keystoneclient" DEBUG: keystoneclient.session RESP: [200] date: Mon, 07 Sep 2015 15:30:58 GMT content-type: application/json content-length: 424 vary: X-Auth-Token server: Apache/2 ... (more)

2015-09-07 01:23:41 -0700 received badge  Enthusiast
2015-09-04 07:04:41 -0700 commented answer resource error using port 8080?

Hi Chris, Even I am running on the same issue. I am actually working on integration of Openstack with ODL. But looks like 8080 port is not up. 227 | Active | Failed | 80 | /controller/nb/v2/neutron | networkconfig.neutron.northbound (0.4.5.Helium-SR3) Could you help ?

2015-08-31 10:11:48 -0700 received badge  Popular Question (source)
2015-08-28 02:55:28 -0700 answered a question ERROR: PostgreSQL ODBC driver was not found on Lithium.

Hi ,

Thanks for your reply. I found work around for this issue. Lithium distribution version doesn't seem to work if we directly it from precompiled files. I built the vtn cordinator from src. That looks to work fine and I was able to create vBridges and vRouters as well.

I totally accept that there are some documentation issues. To put it in straight terms don't run VTN cordinator from pre-compiled Lithium distribution. Build it fresh on your own system (VM/native Ubuntu). You will not see this issue.

Thanks & Regards, Krishna Sharma

2015-08-28 02:47:29 -0700 received badge  Popular Question (source)
2015-08-28 02:46:36 -0700 asked a question DLUX not active on Lithium Distribution

Hi ,

I was working with Lithium distribution version and after installing Dlux , it is not active and I am not able to connect it from my browser.

Following is the output

opendaylight-user@root>feature:install odl-l2switch-all odl-dlux-all odl-restconf-all odl-mdsal-all Refreshing bundles org.eclipse.persistence.moxy (138), org.jboss.netty (178), org.eclipse.persistence.core (137), com.google.guava (64) opendaylight-user@root>la | grep dlux 282 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.core
283 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.common.login
284 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.common.authentication
285 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.common.navigation
286 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.common.topbar
287 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.common.general
288 | GracePeriod | 90 | 0.2.1.Lithium-SR1 | dlux.common.layout
289 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.topology
290 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.node
292 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.yangui
293 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.common.yangutils
294 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.common.sigmatopology
295 | GracePeriod | 80 | 0.2.1.Lithium-SR1 | dlux.yangvisualizer
opendaylight-user@root> opendaylight-user@root> opendaylight-user@root>

But all other features look to be fine for example l2switch feature is active

opendaylight-user@root>la | grep l2switch 199 | Active | 80 | 0.2.1.Lithium-SR1 | org.opendaylight.l2switch.packethandler.packethandler-model
206 | Active | 80 | 0.2.1.Lithium-SR1 | org.opendaylight.l2switch.loopremover.loopremover-model
209 | Active | 80 | 0.2.1.Lithium-SR1 | org.opendaylight.l2switch.addresstracker.addresstracker-model
212 | Active | 80 | 0.2.1.Lithium-SR1 | org.opendaylight.l2switch.hosttracker.hosttracker-model
opendaylight-user@root>

If anyone has faced this prob or if there is any work around for this, please update me.

Thanks in advance

2015-08-20 23:17:27 -0700 asked a question ERROR: PostgreSQL ODBC driver was not found on Lithium.

Hi , I am trying to install VTN coordinator on Ubuntu 14.04 VM with Lithium distribution release as per this link. https://wiki.opendaylight.org/view/Release/Lithium/VTN/Installation_Guide But I am hitting ERROR: PostgreSQL ODBC driver was not found while doing db setup. Am I missing anything ?

I have installed odbc-postgresql and have followed all the steps.

2015-08-20 23:01:47 -0700 commented answer PostgreSQL ODBC driver was not found during install of VTN Coordinator

Hi , I am trying to install VTN coordinator on Ubuntu 14.04 VM with Lithium distribution release as per this link. https://wiki.opendaylight.org/view/Release/Lithium/VTN/Installation_Guide But I am hitting ERROR: PostgreSQL ODBC driver was not found while doing db setup. Am I missing anything ?