Re: Proposed F19 Feature: NFStest
Hello, On 24/01/13 12:33, Paul Wouters wrote: For libreswan we use a system that generates various VM images using a network install and libvirt, and then fires off multiple VMs, login in over serial, and run various tests and output. Then we compare the output with known good output. This includes a tcpdump of the network. Additionally, we use 9p filesystem mounts to install updated versions and read/write configs/logs, so we can still access binaries and write logs even if IPsec has hosed full network connectivity. Ok... that sounds good... but what does that have to do with testing the NFS 4.0 and 4.1 protocol? Granted I know nothing about libreswan other than I just read in the libreswan-3.0/README, but just don't see how libreswan fits in... Note, NFStest is a set of python scripts that explicitly tests the NFS v4.0 and v4.1 protocol by sending packets and then analysing the network traffic to make sure the correct protocol is being followed. So, again, I just don't see how an IPsec implementation would help with that. steved. There is nothing really specific to libreswan for this, and it could be used generally for other systems that need to perform network based tests. It might be worth it to look at what we have already built and see if we can stick to one version of a testing harness for multiple packages? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NFStest
On 01/29/2013 09:32 AM, Steve Dickson wrote: Ok... that sounds good... but what does that have to do with testing the NFS 4.0 and 4.1 protocol? Granted I know nothing about libreswan other than I just read in the libreswan-3.0/README, but just don't see how libreswan fits in... Note, NFStest is a set of python scripts that explicitly tests the NFS v4.0 and v4.1 protocol by sending packets and then analysing the network traffic to make sure the correct protocol is being followed. So, again, I just don't see how an IPsec implementation would help with that. I just meant, if you have not yet build an infrastructure to launch test cases by firing up KVMs, you could re-use what we have built using KVM, qemu and libvirt. The test harness is independent of IPsec, but we share a similar problem. If the test fails, it might mean network connectivity with the test hosts might be broken, so you need some other mechanism to get the log files of the failure. We use direct 9p filesystem mounts for that (and years ago, we used UML hostfs, but UML is just too broken all the time) If you look at libreswan, eg in testing/pluto/basic-pluto-01, you will see: *init.sh files that run when the VMs are launched to prepare them for the test *run.sh files run on the initiator of the test - i.e. the client. *.console.txt files that are the sanitized outputs *.pcap/txt files that is a complete log of the entire traffic stream. We run tcpdump to capture all traffic (we need to see if traffic indeed got encrypted). Then we sanitize ephemeral data and run a diff. The test flags as failed if there is a diff in daemon state, network traffic or console output. But if you already have a system that can run automated tests on different hosts, I guess ignore all I said :) Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Proposed F19 Feature: NFStest
= Features/NFStest = https://fedoraproject.org/wiki/Features/NFStest Feature owner(s): Steve Dickson ste...@redhat.com Provides a set of tools for testing either the NFS client or the NFS server, most of the functionality is focused mainly on testing the client. == Detailed description == NFStest provides a set of tools for testing either the NFS client or the NFS server, including the framework for developing more tests. These tools include the following: Process command line arguments Provide functionality for PASS/FAIL Provide test grouping functionality Provide multiple client support Logging mechanism Debug info control Mount/Unmount control Create files/directories Provide mechanism to start a packet trace Provide mechanism to simulate a network partition Support for pNFS testing Provide mechanism to automate packet trace inspection ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NFStest
On Thu, 24 Jan 2013, Jaroslav Reznik wrote: = Features/NFStest = https://fedoraproject.org/wiki/Features/NFStest Feature owner(s): Steve Dickson ste...@redhat.com Provides a set of tools for testing either the NFS client or the NFS server, most of the functionality is focused mainly on testing the client. == Detailed description == NFStest provides a set of tools for testing either the NFS client or the NFS server, including the framework for developing more tests. These tools include the following: Process command line arguments Provide functionality for PASS/FAIL Provide test grouping functionality Provide multiple client support Logging mechanism Debug info control Mount/Unmount control Create files/directories Provide mechanism to start a packet trace Provide mechanism to simulate a network partition Support for pNFS testing Provide mechanism to automate packet trace inspection For libreswan we use a system that generates various VM images using a network install and libvirt, and then fires off multiple VMs, login in over serial, and run various tests and output. Then we compare the output with known good output. This includes a tcpdump of the network. Additionally, we use 9p filesystem mounts to install updated versions and read/write configs/logs, so we can still access binaries and write logs even if IPsec has hosed full network connectivity. There is nothing really specific to libreswan for this, and it could be used generally for other systems that need to perform network based tests. It might be worth it to look at what we have already built and see if we can stick to one version of a testing harness for multiple packages? Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Proposed F19 Feature: NFStest
= Features/NFStest = https://fedoraproject.org/wiki/Features/NFStest Feature owner(s): Steve Dickson ste...@redhat.com Provides a set of tools for testing either the NFS client or the NFS server, most of the functionality is focused mainly on testing the client. == Detailed description == NFStest provides a set of tools for testing either the NFS client or the NFS server, including the framework for developing more tests. These tools include the following: Process command line arguments Provide functionality for PASS/FAIL Provide test grouping functionality Provide multiple client support Logging mechanism Debug info control Mount/Unmount control Create files/directories Provide mechanism to start a packet trace Provide mechanism to simulate a network partition Support for pNFS testing Provide mechanism to automate packet trace inspection ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
