Hi, Dianne.
I have some additional informations.
I'll comment inline below.
On Wed, 17 Jun 2009 00:30:30 -0400
Subhendu Ghosh <sghosh@redhat.com> wrote:
> Colelli, Dianne wrote:
> > I have some questions regarding the Interoperability test.
> >
> > * Has anyone virtualized the Unified Topology? We are considering
> > using VMWare to virtualize this setup, but before diving in, I
> > wanted to get some feedback and thoughts from other users. Does
> > anyone know any reasons why virtualizing this network would not
> > work?
>
> I had done some TAHI testing with RHEL + FreeBSD on VMware back in 2006/2007
> and clock drifts caused random TAHI tests to fail. This was specially true of
> the long-lived test cases that test timeouts over 2-3 hr periods. The
> virtualized network was not an issue as VMWare provides a clean network
> bridge. Getting serial port connection between instances for test automation
> was a real pain.
Actually, IPv6 Ready Logo Program doesn't allow to use any virtualization. :-)
When you obtain the logo, please prepare actual boxes.
> > * I was also wondering if anyone had information on the size of the
> > data and logs created during the Interoperability test on each
> > PC? We have some space constraints that we need to be mindful of.
>
> Each Self test 52 MB + interoperability 1 MB (total compressed - 3.4 MB)
>
> > * Finally, is the requirement for the 4 target nodes to be all
> > separate platforms an IPV6 Ready requirement or a tahi
> > requirement? We don’t fully get the emphasis placed on varying
> > the OS versions, when a broader range of OS’s are not included
> > (like Microsoft or Sun, etc.).
> >
> >
>
> Separate platforms is an IPv6 Ready Logo requirement. TAHI provides the
> Self-Test suites for conformance verification. TAHI it self has not
> requirements other than TN node requirements.
Yes, that is IPv6 Ready Logo Program requirements.
That program requires to test with two different vendors on each of test interfaces.
Talking about IPv6 Core Protocols test, three test interfaces are defined.
They are
IF1: host to host
counterpart devices: vendor A, vendor B
IF2: host to router
counterpart devices: vendor C, vendor D
IF3: router to router
counterpart devices: vendor E, vendor F
If your box is the host implementation, you must perform the test with vendor A throungh D.
If your box is the router implementation, you must perform the test with vendor C through F.
Thanks,
>
> -regards
> Subhendu
>
>
> --
> Subhendu Ghosh
> Red Hat
> Email: sghosh@redhat.com
>
>
>
>
--
Yukiyo Akisada <akisada@tahi.org>