Re: [LTP] [patch 0/9] Network NS patch
Hi, I hope now a focus is well set to reuse existing tests and pay attention to improve them to value add for container specific features as well, *if needed*. On the way, I had tested few tests in tcp_cmds today and could see positive signs till now. tested tcp_cmds/arp. No issues. tested tcp_cmds/echo. No issues. tested tcp_cmds/finger. No issues. [ applied RSH - SSH changes] tested tcp_cmds/ftp. No issues. [applied RSH - SSH changes] tested tcp_cmds/host. No issues. tested tcp_cmds/netstat. No issues. tested tcp_cmds/perf_lan. No issues. tested tcp_cmds/ping. No issues. I had to change scripts to use SSH instead of insecure RSH, as I could nt setup perfectly in short time. If anyone have tested remaining tcp command tests inside containers you are welcome to update. Thanks, Gowrishankar Sudhir Kumar wrote: On Wed, Sep 17, 2008 at 03:45:08PM +0200, Benjamin Thery wrote: Subrata Modak wrote: Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? I also think this is how most of the testing for netns should be done: run the existing network tests in network namespaces to check there are no regression. No need to rewrite all the network tests for the netns case. My Bad as I could not login to IBM network while attending the QSE Conference and respond to the mails. I have taken up this job(to create a scripts which will run the existing network testcases) after I had a meeting here to discuss the same. Reusability wherever possible is at high priority, and if things go allright I wil be soon able to send the patches doing the same. Also I have developed testcases which do test network namespace features other than the network testcases in LTP. I was waiting for Veerendra's container creation patches to go in LTP so that I can quickly rebase my patches on top of them. Also we are focusing on the testcases that test the specific features of network namespace. But, we also need some additional test cases, for basic netns operations (creation, deletion, moving interface between namespaces) and specific features brought by netns. For example the sysfs tests sent by Veerendra to check what is seen in /sys/class/net from different namespaces, or the test that rename a network interface in a child netns with a name already in use in another namespace. Regards, Benjamin Regards-- Subrata On Wed, 2008-09-10 at 18:40 +0530, Veerendra wrote: Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list -- B e n j a m i n T h e r y - BULL/DT/Open Software RD http://www.bull.com - This SF.Net email is
Re: [LTP] [patch 0/9] Network NS patch
On Wed, Sep 17, 2008 at 03:45:08PM +0200, Benjamin Thery wrote: Subrata Modak wrote: Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? I also think this is how most of the testing for netns should be done: run the existing network tests in network namespaces to check there are no regression. No need to rewrite all the network tests for the netns case. My Bad as I could not login to IBM network while attending the QSE Conference and respond to the mails. I have taken up this job(to create a scripts which will run the existing network testcases) after I had a meeting here to discuss the same. Reusability wherever possible is at high priority, and if things go allright I wil be soon able to send the patches doing the same. Also I have developed testcases which do test network namespace features other than the network testcases in LTP. I was waiting for Veerendra's container creation patches to go in LTP so that I can quickly rebase my patches on top of them. Also we are focusing on the testcases that test the specific features of network namespace. But, we also need some additional test cases, for basic netns operations (creation, deletion, moving interface between namespaces) and specific features brought by netns. For example the sysfs tests sent by Veerendra to check what is seen in /sys/class/net from different namespaces, or the test that rename a network interface in a child netns with a name already in use in another namespace. Regards, Benjamin Regards-- Subrata On Wed, 2008-09-10 at 18:40 +0530, Veerendra wrote: Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list -- B e n j a m i n T h e r y - BULL/DT/Open Software RD http://www.bull.com - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list -- Regards Sudhir Kumar Linux Technology Center IBM, India. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world
Re: [LTP] [patch 0/9] Network NS patch
Subrata Modak wrote: Hi Benjamin, On Wed, 2008-09-17 at 15:45 +0200, Benjamin Thery wrote: Subrata Modak wrote: Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? I also think this is how most of the testing for netns should be done: run the existing network tests in network namespaces to check there are no regression. No need to rewrite all the network tests for the netns case. Thanks for providing your inputs. Veerendra/Sudhir/Gowri, Can you please work on the points mentioned my Benjamin and come out with a nenewed set of patches which addresses the following: 1) Use the existing network tests available in LTP for netns testing, 2) Integrate additional netns testing, as veerendra might have written additional tests (in his 0-9 series patches). Regards-- Subrata But, we also need some additional test cases, for basic netns operations (creation, deletion, moving interface between namespaces) and specific features brought by netns. For example the sysfs tests sent by Veerendra to check what is seen in /sys/class/net from different namespaces, or the test that rename a network interface in a child netns with a name already in use in another namespace. Regards, Benjamin Yes , we are trying to use the existing tests of LTP. And not re-writing the same testcases of LTP. There may be few cases, where we cannot not use existing LTP testcases. In these cases we may re-write them for containers. Most of the testcases submitted are to create the infra-structure to create, delete containers . And I have started the sshd in the containers created. After commenting out the cleanup line in the script; anybody can login into the containers, and *run* other testcases. Regards Veerendra C We can For the same reason, if any Regards-- Subrata On Wed, 2008-09-10 at 18:40 +0530, Veerendra wrote: Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
Re: [LTP] [patch 0/9] Network NS patch
On Thu, 2008-09-18 at 09:12 +0530, Subrata Modak wrote: Hi Benjamin, On Wed, 2008-09-17 at 15:45 +0200, Benjamin Thery wrote: Subrata Modak wrote: Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? I also think this is how most of the testing for netns should be done: run the existing network tests in network namespaces to check there are no regression. No need to rewrite all the network tests for the netns case. Thanks for providing your inputs. Veerendra/Sudhir/Gowri, Can you please work on the points mentioned my Benjamin and come out with a nenewed set of patches which addresses the following: 1) Use the existing network tests available in LTP for netns testing, And i would strongly recommend to use this Approach in the first place itself, rather than we can do this later. I would also not like to let your efforts go waste. So, kindly use the method in point one and then integrate whatever you have worked on now in point 2. I would expect a quicker patch from some of you on this so that i can then include it in September 2008 release. Also, please keep the READMEs very properly and provide me the results of a complete test run on any architecture. Regards-- Subrata 2) Integrate additional netns testing, as veerendra might have written additional tests (in his 0-9 series patches). Regards-- Subrata But, we also need some additional test cases, for basic netns operations (creation, deletion, moving interface between namespaces) and specific features brought by netns. For example the sysfs tests sent by Veerendra to check what is seen in /sys/class/net from different namespaces, or the test that rename a network interface in a child netns with a name already in use in another namespace. Regards, Benjamin Regards-- Subrata On Wed, 2008-09-10 at 18:40 +0530, Veerendra wrote: Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is
Re: [LTP] [patch 0/9] Network NS patch
Hi Veerendra, On Thu, 2008-09-18 at 16:15 +0530, Veerendra wrote: Subrata Modak wrote: Hi Benjamin, On Wed, 2008-09-17 at 15:45 +0200, Benjamin Thery wrote: Subrata Modak wrote: Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? I also think this is how most of the testing for netns should be done: run the existing network tests in network namespaces to check there are no regression. No need to rewrite all the network tests for the netns case. Thanks for providing your inputs. Veerendra/Sudhir/Gowri, Can you please work on the points mentioned my Benjamin and come out with a nenewed set of patches which addresses the following: 1) Use the existing network tests available in LTP for netns testing, 2) Integrate additional netns testing, as veerendra might have written additional tests (in his 0-9 series patches). Regards-- Subrata But, we also need some additional test cases, for basic netns operations (creation, deletion, moving interface between namespaces) and specific features brought by netns. For example the sysfs tests sent by Veerendra to check what is seen in /sys/class/net from different namespaces, or the test that rename a network interface in a child netns with a name already in use in another namespace. Regards, Benjamin Yes , we are trying to use the existing tests of LTP. And not re-writing the same testcases of LTP. There may be few cases, where we cannot not use existing LTP testcases. In these cases we may re-write them for containers. Most of the testcases submitted are to create the infra-structure to create, delete containers . And I have started the sshd in the containers created. After commenting out the cleanup line in the script; anybody can login into the containers, and *run* other testcases. Can you also provide me with the same .config file on the kernel that you have run those tests as well as the test results of the same netns run ? Regards-- Subrata Regards Veerendra C We can For the same reason, if any Regards-- Subrata On Wed, 2008-09-10 at 18:40 +0530, Veerendra wrote: Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
Re: [LTP] [patch 0/9] Network NS patch
Subrata Modak wrote: On Thu, 2008-09-18 at 09:12 +0530, Subrata Modak wrote: Hi Benjamin, On Wed, 2008-09-17 at 15:45 +0200, Benjamin Thery wrote: Subrata Modak wrote: Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? I also think this is how most of the testing for netns should be done: run the existing network tests in network namespaces to check there are no regression. No need to rewrite all the network tests for the netns case. Thanks for providing your inputs. Veerendra/Sudhir/Gowri, Can you please work on the points mentioned my Benjamin and come out with a nenewed set of patches which addresses the following: 1) Use the existing network tests available in LTP for netns testing, And i would strongly recommend to use this Approach in the first place itself, rather than we can do this later. I would also not like to let your efforts go waste. I hope you can understand that there is no infrastructure to create the network namespaces in the LTP now. And in these testcases I am not duplicating my efforts in re-writing the testcases of LTP. I would not like to waste my time in re-writing the existing testcases of LTP. So, kindly use the method in point one and then integrate whatever you have worked on now in point 2. I would expect a quicker patch from some of you on this so that i can then include it in September 2008 release. Also, please keep the READMEs very properly and provide me the results of a complete test run on any architecture. The README is also updated with the details of what kernel config options to be enabled, how to run the testcases and how to use the current setup to write new testcases for the containers. I have the below execution results . The last test is failing only because of the setup is not done for the ftp-server. [EMAIL PROTECTED] netns]# ./runnetnstest.sh parentns.sh0 INFO : PASS: Pinging ChildNS from ParentNS childns.sh0 INFO : PASS: Pinging ParentNS from ChildNS crtchild: PASS Message from syslogd@ at Thu Sep 18 23:41:57 2008 ... mx3755b kernel: unregister_netdevice: waiting for lo to become free. Usage count = 4child_2.sh0 INFO : PASS: CHILD1 is pinging from CHILD2 ! child_1.sh0 INFO : PASS: Child2 is pinging from CHILD1 ! two_children_ns: PASS childns.sh0 INFO : Successfully Renamed device to veth2 Files /tmp/sys_b4_child_killed and /tmp/sys_aftr_child_killed differ crtchild_delchild: PASS childipv6.sh0 INFO : IPv6: Pinging Parent from Child: PASS paripv6.sh0 INFO : IPv6: Pinging child from parent: PASS par_chld_ipv6: PASS childns.sh0 INFO : Pass:Child is able to view parent sysfs parentns.sh0 INFO : Pass: Parent is able to view child sysfs sysfsview: PASS parentns.sh0 INFO : Pinging ChildNS from ParentNS Error: Can't login to 192.168.0.181: childns.sh1 FAIL : ftp failed Error while running the script par_chld_ftp: FAIL 1 ; Regards Veerendra C Regards-- Subrata 2) Integrate additional netns testing, as veerendra might have written additional tests (in his 0-9 series patches). Regards-- Subrata But, we also need some additional test cases, for basic netns operations (creation, deletion, moving interface between namespaces) and specific features brought by netns. For example the sysfs tests sent by Veerendra to check what is seen in /sys/class/net from different namespaces, or the test that rename a network interface in a child netns with a name already in use in another namespace. Regards, Benjamin - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world
Re: [LTP] [patch 0/9] Network NS patch
Hi Benjamin, On Wed, 2008-09-17 at 15:45 +0200, Benjamin Thery wrote: Subrata Modak wrote: Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? I also think this is how most of the testing for netns should be done: run the existing network tests in network namespaces to check there are no regression. No need to rewrite all the network tests for the netns case. Thanks for providing your inputs. Veerendra/Sudhir/Gowri, Can you please work on the points mentioned my Benjamin and come out with a nenewed set of patches which addresses the following: 1) Use the existing network tests available in LTP for netns testing, 2) Integrate additional netns testing, as veerendra might have written additional tests (in his 0-9 series patches). Regards-- Subrata But, we also need some additional test cases, for basic netns operations (creation, deletion, moving interface between namespaces) and specific features brought by netns. For example the sysfs tests sent by Veerendra to check what is seen in /sys/class/net from different namespaces, or the test that rename a network interface in a child netns with a name already in use in another namespace. Regards, Benjamin Regards-- Subrata On Wed, 2008-09-10 at 18:40 +0530, Veerendra wrote: Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
Re: [LTP] [patch 0/9] Network NS patch
Hi Veerendra, Before i go ahead in applying and testing your patches, i would like to point out something. Last week in our private discussion, we identified one of the easiest ways to do NETNS testing. The simplest infrastructure to test this will be using the existing LTP Network tests, and will involve the following procedure: 1) Create your Parent Container on a Remote server, and, start all the networking Daemon services that are required on a remote server in case of normal LTP Network testing, 2) Create multiple child containers in another host, 3) Start the ltp/testscripts/networktests.sh from each of the child container, 4) Analyse the results after the tests are complete. With the above approach, we would have required just one script on the child containers host machine, which would have: 1) Created the containers and all those stuff, 2) Invoked the networktests.sh script from each of the child containers, 3) Other House keeping stuff. I am not sure what other procedure you are employing to test NETNS. Is the above procedure not simple to implement ? Regards-- Subrata On Wed, 2008-09-10 at 18:40 +0530, Veerendra wrote: Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
Re: [LTP] [patch 0/9] Network NS patch
Submitting the series of patches for network namespace of containers . These patches addresses the comments of Benjamin/Serge on the patches I had posted earlier. Also included the ack of Serge. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
[LTP] [patch 0/9] Network NS patch
Subrata, I am sending the updated patches for the network Namespacs . This patches have addressed the review comments of Serge. I have taken care to return error on failure from both the parent NS and child Namespace . Please let me know if there are any more things needs to be taken care. Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
Re: [LTP] [patch 0/9] Network NS patch
Quoting Veerendra ([EMAIL PROTECTED]): Subrata, I am sending the updated patches for the network Namespacs . This patches have addressed the review comments of Serge. I have taken care to return error on failure from both the parent NS and child Namespace . Please let me know if there are any more things needs to be taken care. Regards Veerendra C Veerendra, please send a patch against the previous version, and if you had a compiled list of the issues I'd raised, please send that too. Looking over this whole set to try and find what you may or may not have changed from last time is not ideal. After that I'll ack it, but please look for an ack from Benjamin or Daniel. thanks, -serge - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
Re: [LTP] [PATCH 0/9] Network NS patch ,
Veerendra, I am hoping that you will resend me these Patch series after incorporating Sergei´s comments. Regards-- Subrata On Thu, 2008-08-07 at 19:07 +0530, Veerendra wrote: Hi , Please find the patches for the testing of network NS. The patches are created from the path LTP/testcases/kernel/containers . Signed-off-by: Veerendra C [EMAIL PROTECTED] This patch consists of the files.. containers/Makefile containers/netns/Makefile containers/netns/initialize.sh Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
Re: [LTP] [PATCH 0/9] Network NS patch ,
Veerendra, I didn´t fine [PATCH 9/9] arriving at the mailing list. Is there any patch in that no., or, [PATCH 8/9] was the last one ? Regards-- Subrata On Thu, 2008-08-07 at 19:07 +0530, Veerendra wrote: Hi , Please find the patches for the testing of network NS. The patches are created from the path LTP/testcases/kernel/containers . Signed-off-by: Veerendra C [EMAIL PROTECTED] This patch consists of the files.. containers/Makefile containers/netns/Makefile containers/netns/initialize.sh Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
[LTP] [PATCH 0/9] Network NS patch , renames the child veth device and deletes the child
Signed-off-by: Veerendra C [EMAIL PROTECTED] This patch consists of the files.. containers/netns/crtchild_delchild.c containers/netns/delchild.sh containers/netns/rename_net.sh Regards Veerendra C - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
