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

bsvTag's profile - activity

2015-09-07 21:49:50 -0700 received badge  Famous Question (source)
2015-06-25 18:51:15 -0700 received badge  Notable Question (source)
2015-06-08 00:02:18 -0700 received badge  Popular Question (source)
2015-05-19 06:52:14 -0700 asked a question Update Node Details using MD-SAL

Hi, Is it possible to update generic node information,like description, hardware or manufacturer using PUT /restconf/operational/opendaylight-inventory:nodes/node/ endpoint? As I understand, it's possible, but every time I try to do this, the response is 200, but operational data is not updated. Here is my request:

PUT /restconf/config/opendaylight-inventory:nodes/node/openflow:108556646647878 HTTP/1.1
Host: xxx.xxx.xxx.xx:8181
Authorization: Basic YWRtaW46YWRtaW4=
Accept: application/xml
Content-Type: application/xml
Cache-Control: no-cache

<node xmlns="urn:opendaylight:inventory">
<id>openflow:108556646647878</id>
<description xmlns="urn:opendaylight:flow:inventory">Test</description>
</node>

As I remember, correspondent AD-SAL API worked as expected, but I might be wrong.

2015-01-30 07:51:42 -0700 received badge  Notable Question (source)
2015-01-30 07:51:42 -0700 received badge  Famous Question (source)
2015-01-22 09:42:41 -0700 received badge  Popular Question (source)
2015-01-20 23:08:34 -0700 asked a question MD-SAL documentation

Hi, Recently, I've asked a question about adding flow via MD-SAL API. I used wiki documentation links to build my xml request properly, like flow-node-inventory spec . However, the link is broken since last week. How can I access this information? I've tried API explorer, but as for me, it's doesn't cover all cases, i.e. doesn't show all attributes/tags, which can be posted in xml/json body.

2015-01-20 23:02:57 -0700 received badge  Famous Question (source)
2015-01-20 15:28:53 -0700 received badge  Famous Question (source)
2015-01-16 12:19:03 -0700 commented answer How can I add flow properly, using MD-SAL

I mean tcp-destination-port, not switch port. I can see the installed flow in the switch using 'ovs-ofctl dump-flows' command. However, filter only by destination port doesn't block traffic. I'll do tcpdump/wireshark research soon to find out the reason. May be I'm missing something. Thanks anyways!

2015-01-15 23:43:00 -0700 commented answer How can I add flow properly, using MD-SAL

Chris, I found it also, and fixed it. However, I noticed that port level filtering is not working. Only when I set ipv4-destination , I can block traffic between instances. I'm looking now, what's the problem with port filtering.

2015-01-15 23:34:45 -0700 received badge  Popular Question (source)
2015-01-15 23:34:45 -0700 received badge  Notable Question (source)
2015-01-14 09:36:53 -0700 answered a question FLOW/NODE PROBLEM

I have the same problem as you. However, I can add flows using MD-SAL or AD-SAL rest APIs.

2015-01-14 09:25:10 -0700 commented question How can I add flow properly, using MD-SAL

here it is: cookie=0x0, duration=2134.231s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=32535,tcp,in_port=3,tp_dst=5000 actions=drop

2015-01-14 09:24:51 -0700 commented question How can I add flow properly, using MD-SAL

Chris, I found out, that flow, added via MD-SAL is not accepted by switch. However, I checked AD-SAL flow API, and it looks like it's accepted, however, flow stats are zero.

2015-01-14 08:55:06 -0700 commented question How can I add flow properly, using MD-SAL

Chris, when I call GET /restconf/config/opendaylight-inventory:nodes/node/openflow:257989387785286/table/0/ I can see a list of flows, including my flow.

2015-01-14 04:13:46 -0700 asked a question How can I add flow properly, using MD-SAL

Hi, My environment consists of Openstack(devstack version) with Opendaylight as a switch controller. I have two instances, running in openstack. I'm trying to add flow using MD-SAL, which blocks any communication on a specific port between openstack instances. I follow EndtoEndFlow wiki guide and flow-node-inventory spec, and try to add flow using Postman as follows:

PUT /restconf/config/opendaylight-inventory:nodes/node/openflow:257989387785286/table/0/flow/block5000 HTTP/1.1
Accept: application/xml
Content-Type: application/xml
Authorization: Basic YWRtaW46YWRtaW4=
Cache-Control: no-cache

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<flow xmlns="urn:opendaylight:flow:inventory">
  <priority>2</priority>
  <flow-name>block5000</flow-name>
  <match>
     <in-port>5000</in-port>
  </match>
  <id>block5000</id>
  <table_id>0</table_id>
  <instructions>
    <instruction>
        <order>0</order>
        <apply-actions>
            <action>
               <order>0</order>
               <drop-action/>
            </action>
        </apply-actions>
    </instruction>
  </instructions>
</flow>

However, this flow doesn't block traffic between openstack running instances(I'm using netcat to emulate traffic activity between instances) When I issue GET request:

 GET /restconf/config/opendaylight-inventory:nodes/node/openflow:257989387785286/table/0/ 
 HTTP/1.1
 Accept: application/xml
 Content-Type: application/xml
 Authorization: Basic YWRtaW46YWRtaW4=
 Cache-Control: no-cache

I can see my flow. But I'm not able to get statistics for my flow using /restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/0/ URL. Can anybody point me the problem with my flow and find out the way to get its stats? Thanks.

2015-01-12 03:04:05 -0700 received badge  Necromancer (source)
2015-01-08 11:59:38 -0700 answered a question Use of RESTCONF v/s REST API

I have the same problem to solve. According to link , AD-SAL may be marked as deprecated in Lithium release, and no one is supporting it in a current release. So, use of MD-SAL is the proper way to make long-term project.

2015-01-08 08:07:54 -0700 received badge  Notable Question (source)
2015-01-05 00:52:41 -0700 received badge  Popular Question (source)
2014-12-26 02:18:39 -0700 asked a question Unable to get Container list using AD-SAL in Helium SR1

Hi, I'm trying to get all containers in the system using ContainerManagerNorthbound GET /containers API. On hydrogen there was no problem, but in helium I've got 404 error. Here is the list of installed features, related to AD-SAL:

odl-adsal-all                  | 0.8.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight AD-SAL All Features                  
odl-adsal-core                 | 0.8.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Core                    
odl-adsal-networkconfiguration | 0.0.4-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Network Configuration   
odl-adsal-connection           | 0.1.3-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Connection              
odl-adsal-clustering           | 0.5.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Clustering              
odl-adsal-configuration        | 0.4.4-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Configuration           
odl-adsal-thirdparty           | 0.8.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Third-Party Depenencies 
odl-adsal-northbound           | 0.4.3-Helium-SR1 | x | nsf-0.4.3-Helium-SR1   | OpenDaylight :: AD-SAL :: Northbound APIs

I've looked to web endpoints, and found out, that containermanager web endpoint is missing:

| /controller/nb/v2/connectionmanager          | connectionmanager.northbound (0.1.3.Helium-SR1)         
| /controller/nb/v2/flowprogrammer             | flowprogrammer.northbound (0.4.3.Helium-SR1)            
| /controller/nb/v2/hosttracker                | hosttracker.northbound (0.4.3.Helium-SR1)               
| /controller/nb/v2/networkconfig/bridgedomain | networkconfig.bridgedomain.northbound (0.0.4.Helium-SR1)
| /controller/nb/v2/neutron                    | networkconfig.neutron.northbound (0.4.3.Helium-SR1)     
| /controller/nb/v2/staticroute                | forwarding.staticrouting.northbound (0.4.3.Helium-SR1)  
| /controller/nb/v2/statistics                 | statistics.northbound (0.4.3.Helium-SR1)                
| /controller/nb/v2/subnetservice              | subnets.northbound (0.4.3.Helium-SR1)                   
| /controller/nb/v2/switchmanager              | switchmanager.northbound (0.4.3.Helium-SR1)             
| /controller/nb/v2/topology                   | topology.northbound (0.4.3.Helium-SR1)                  
| /controller/nb/v2/usermanager                | usermanager.northbound (0.0.3.Helium-SR1)

What feature should I install to helium to enable ContainerManagerNorthbound AD-SAL API?

UPDATE

I dig into the logs and found out that containermanager.northbound bundle is not registered in the system. No logs about skipping, and no exceptions related with containermanager classes. I check ./system directory and found the following jars:

 $ find ./ -type f -name "containermanager*.jar"      
 ./system/org/opendaylight/controller/containermanager/0.5.3-Helium-SR1.1/containermanager-0.5.3-Helium-SR1.1.jar
 ./system/org/opendaylight/controller/containermanager.implementation/0.5.3-Helium-SR1.1/containermanager.implementation-0.5.3-Helium-SR1.1.jar
 ./system/org/opendaylight/controller/containermanager.northbound/0.4.3-Helium-SR1.1/containermanager.northbound-0.4.3-Helium-SR1.1.jar
  ./system/org/opendaylight/controller/containermanager.shell/0.5.3-Helium-SR1.1/containermanager.shell-0.5.3-Helium-SR1.1.jar

So, it looks like it should be deployed normally... But no success.

This API is related with other AD-SAL APIs, like

  • adding user links in topology(/{containerName}/userLink/{name}),
  • adding properties to node connectors using switch API (/controller/nb/v2/switchmanager/{containerName}/nodeconnector/{nodeType}/{nodeId}/{nodeConnectorType}/{nodeConnectorId}/property/{propertyName}/{propertyValue}),
  • other APIs with {containerName} parameter.
2014-12-26 00:44:37 -0700 received badge  Popular Question (source)
2014-12-26 00:44:37 -0700 received badge  Notable Question (source)
2014-12-26 00:44:37 -0700 received badge  Famous Question (source)
2014-12-26 00:43:51 -0700 received badge  Famous Question (source)
2014-12-06 05:36:12 -0700 received badge  Notable Question (source)
2014-11-28 06:50:43 -0700 received badge  Popular Question (source)
2014-11-26 02:28:19 -0700 received badge  Enthusiast
2014-11-25 23:46:04 -0700 commented question L3 Router with OpenDaylight and OpenStack

I'm on the same way. Stack logs might be helpful. Note, that document is a little bit old. Currently, openstack already has integration with opendaylight since icehouse release. Look at the following link: http://www.siliconloons.com/opendaylight-integration-with-openstack-has-merged-into-icehouse/

2014-11-25 10:10:59 -0700 asked a question Strange behavior of BridgeDomain Configuration Northbound APIs in Opendaylight Hydrogen

Hi, I'm using Opendaylight Hydrogen pre-built zip release. When I try to call create bridge API, I've got 404 error with strange status description. I tried to execute API as follows:

POST http://localhost:8080/controller/nb/v2/networkconfig/bridgedomain/bridge/STUB/mgmt1/bridge1

The response status is 404 with description "Requested Plugin Service Not available".

What does it mean? Am I missing something to install or config?

2014-11-25 09:49:49 -0700 asked a question Openstack Neutron REST API

Hi, I'm trying to test Opendaylight Hydrogen/Openstack Neutron REST API in my multi-node lab (devstack with neutron networking) I found out, that some of APIs are returning 404 error:

  • GET /controller/nb/v2/neutron/fw/firewalls
  • GET /controller/nb/v2/neutron/fw/firewalls_rules
  • GET /controller/nb/v2/neutron/loadbalancers
  • GET /controller/nb/v2/neutron/healthmonitors

Recently, ad-sal wiki documentation was broken. Now it's ok. However, I've noticed, that Neutron REST API resources set is much less than previously. I used the following link to check Neutron Northbound APIs. The full set of Neutron APIs was as follows:

  • NeutronFirewallNorthbound
  • NeutronFirewallPolicyNorthbound
  • NeutronFirewallRulesNorthbound
  • NeutronFloatingIPsNorthbound
  • NeutronLoadBalancerHealthMonitorNorthbound
  • NeutronLoadBalancerListenerNorthbound
  • NeutronLoadBalancerNorthbound
  • NeutronLoadBalancerPoolMembersNorthbound
  • NeutronLoadBalancerPoolNorthbound
  • NeutronNetworksNorthbound
  • NeutronPortsNorthbound
  • NeutronRoutersNorthbound
  • NeutronSecurityGroupsNorthbound
  • NeutronSecurityRulesNorthbound
  • NeutronSubnetsNorthbound

Now it's reduced to the following list:

  • NeutronFloatingIPsNorthbound
  • NeutronNetworksNorthbound
  • NeutronPortsNorthbound
  • NeutronRoutersNorthbound
  • NeutronSubnetsNorthbound

Is it a build issue or these APIs are removed as non-implemented?

2014-11-24 05:59:19 -0700 answered a question HydrogenVirtualization

Hi, Currently, opendaylight integration is merged into devstack already. So, you may try to follow this guide also

2014-11-20 10:47:03 -0700 received badge  Famous Question (source)
2014-11-18 01:46:56 -0700 received badge  Notable Question (source)
2014-11-17 10:48:21 -0700 marked best answer Why is AD-SAL docs dissapeared from opendaylight wiki?

Hi, From last week, I can't access any link on OpenDayLight REST API It always shows 404 error. Looks like link is broken. Can anyone clarify, is AD-SAL API deprecated since hellium release? Should I switch to MD-SAL ? Does MD-SAL APIs return the same data as it works with AD-SAL API?

2014-11-17 10:46:23 -0700 received badge  Popular Question (source)