Dear Michael et al,
Have you investigated how much work would be needed to make the grid work over IPv6, or perhaps use an IPv6 VPN to connect sites but use IPv4 over the VPN to use the grid?
Others have done so (EUCHINAGRID project, afaik) and they only thing they came up to has been, at best, a patch that can provide private-IPv4 over IPv6. But, private we've got already, so that's not any progress.
Have you asked Athanassios Liakopoulos or Kostas Kalevras or Dimitrios Kalogeras to look at ways of solving your problem with the grid and IPv6?
Yes, with a majority of them I had already discussed. And we all agree that if there was IPv4 support in glite it would have been so much better. (Or, if we were grid middleware developers, which we are clearly not).
The bottom line is that experimental allocations are made for experiments that benefit the whole Internet, not just a few schools in one country.
I believe that understanding this as a school experiment is a bit flawed: Has anybody ever done a large VPN-for-VMs IPv4 adress space allocation? I have never heard of something like that (end2end) but perhaps it exists; and am well aware though of some -open/public- IPv6 tunneling solutions. Collecting knowledge from such an endeavour, were thousands of systems with end2end capability run contained in VMs, I believe is worthy for many, the more as multi-cores change the way we understand systems management. In the meantime, we had some more discussions and found out that making a request for public IPv4 address space is OK solely for Virtual Machines, even if the underlying machines already are on public IPv4 address space, as long as the request is indeed justified by real use - and documented. In other words, reserving experimental IPv4 address space is no longer our first option, since normal IPv4 address space appears to be doable. This is something for which we weren't sure earlier, if someone in this wg knows otherwise - in respect to the adress_policy - please let us know. I thank you, and also other recipients in this list, that took time to reply, some privately. Just to clarify what had been the issue, two extra answers:
* If these machines are already internet connected, then no *additional* IP could be needed
The >62000 machines are functioning within 1000s of NATs, in a 10.x.y.z scheme
* If these machines are not already internet connected then having an IP is the least of yoru worries - you have to think how you are going to *route* to them :)
That's done and works just fine already for many years. There you go. cheers, Fotis