Simplified netconf clustered CRUD test suite in Bug 8086 setup.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the node1, node2 and node3 to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.

Unset tell-based protocol usage

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Suite stops all odl nodes, outcomment usage of tell-based protocol in config file (means make it false by default) and starts all nodes again.

Test suite for netconf device entity ownership handling during outages.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the ${NODE_CONFIGURER}, ${NODE_SETTER} and ${NODE_CHECKER} to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.

Unset tell-based protocol usage

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Suite stops all odl nodes, outcomment usage of tell-based protocol in config file (means make it false by default) and starts all nodes again.

netconf cluster node outage test suite (CRUD operations).

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform one of the basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector while one of the nodes is down and see if they work. Then bring the dead node up and check that it sees the operations that were made while it was down are visible on it as well.

The node is brought down before each of the "Create", "Update" and "Delete" operations and brought and back up after these operations. Before the dead node is brought up, a test case makes sure the operation is properly propagated within the cluster.

Currently each of the 3 operations is done once. "Create" is done while node 1 is down, "Update" while node 2 is down and "Delete" while node 3 is down.

Test suite for netconf device entity ownership handling during outages.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the ${NODE_CONFIGURER}, ${NODE_SETTER} and ${NODE_CHECKER} to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.

netconf clustered CRUD test suite.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the node1, node2 and node3 to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.