>> Our test environment currently has the following nodes: >> >> - One combined HLK Studio/controller >> - Four identical HLK client nodes >> - OpenVPN test server >> >> The HLK nodes are all Windows Server 2016 as that is our primary target. >> The OpenVPN test server provides the HLK clients with an IPv6 address >> and IPv6 gateway - this is required for almost all "Run" tests. All of >> the nodes are in Amazon EC2. With the above setup 54 tests pass and 9 fail.
This sounds great. >> The "Support machine" you mentioned is still missing. I will try to set >> it up today and check how many of the currently failing tests start passing. If the failures look network-topology-related, this should be the missing link. The "support machine" should be a second host on the VPN that the HLK server can talk to for generating traffic. If I get access to the HLK machine I'll be inspecting the detailed errors reported by the failing tests. > I looked at "LAN Testing Prerequisites" in HLK documentation and it not > entirely clear what is needed: > > https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/lan-testing-prerequisites > > > The document hints thats we would need to have at least one real > physical HLK client with 4 or 8 cores. It is also mentioned that Windows > Server Core is needed as well. > > Anyways, some of these things may not be applicable to us. I guess the > best we can do is go through the test failures individually and see what > is happening. Guesswork sucks. :( Maybe I can help a little... Windows Server 2016 has two installation modes: Core and Desktop Experience. From what I've read, it just needs to be in Core mode for the test and either kind of installation can be switched to the other. The core and RAM requirements should be acheivable in EC2. Hardware is only required if the driver exposes a hardware feature like Receive-Side Scaling that relates to processor groupings. > One thing to look at is HLK filters. Maybe they can be applied to > prevent inapplicable tests from being run. > > I'm also not sure if passing the all tests entitles us to code > signatures from Microsoft or not. It could be that HLK tests pass, but > the test setup is not valid from signing viewpoint (e.g. not having a > physical 4-8 core server as a HLK client). This is described in the WHCP Guidelines doc linked from the prereqs page: http://go.microsoft.com/fwlink/p/?LinkID=615222 (heads-up: Word doc) If I'm reading this right, the HLK should automatically select all the right tests for the driver. It'll be informative to see what it decides on. VM-based testing is allowed for para-virtualization drivers, which tap-windows6 might qualify as. Apparently there is an Issue Resolution process that is used to officially qualify a driver for this classification. >> Note that right now I'm running the tests against tap-windows-9.22.1 to >> give us a baseline. That way we can check if our recent updates have >> broken (or possibly fixed) something. With 4 HLK clients the runtime of >> the whole test suite is almost reasonable. With one node it took 10+ hours. The idea of a baseline is great. Let's avoid breaking things. :) >> I can definitely grant you access to the HLK controller so that you can >> check what is happening. If you're working today around 16:00-18:00 UTC >> please poke me at #openvpn-devel and we'll get you started. Sorry I wasn't available this round; I'll be available tomorrow 16:00-18:00 UTC unless I hear otherwise from you. So: * Please start a conversation with the certification team through the signing website. They will know for sure which tests are needed and what category of driver tap-windows6 is classified as. * I'll be online during the suggested window in ~22 hours so we can try and resolve the existing test failures. This way we'll be ready with passing tests whatever the classification comes in as. :) Jon
pgpCncx7U8g4E.pgp
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
