[ietf78-tech] URGENT! Re: VMware images, where are they.

Chris Elliott chelliot at pobox.com
Thu Jun 17 08:25:37 PDT 2010


We can have Verilan route 130.129.5/24 to ripe...

Just kidding. Not worth the trouble for a week.

Enjoy!
Chris.

P.S. Billo--thanks on the reply to all. Works great. Now I get to blame you
when I accidentally post that embarrassing message to a list...

On Thu, Jun 17, 2010 at 11:11 AM, Menno Schepers <mschepers at ripe.net> wrote:

> ACK.
>
> Will leave it alone until you say it's safe for us to announce..
>
> Might not even bother announcing it and instead setup a linux box to serve
> as NAT gateway for the IETF vm's to acess the interwebs and SSH access
> server, from which you can then SSH further onto the machiens.
>
> -Menno
>
>
>
> On 6/17/10 17:01 , Jim Martin wrote:
>
>>  I just realized that we have a conflict with 130.129/16. Please don't
>> announce it!
>>
>> The ICANN meeting is in Brussles next week and our friends at Verilan
>> asked to borrow the block. Announcing it out of ripe would cause lots of
>> trouble right about now. Sorry!
>>
>> We can advertise it after next week.
>>
>> -Jim
>>
>> Sent from my iPhone
>>
>> On Jun 17, 2010, at 7:55 AM, Chris Elliott <chelliot at pobox.com
>> <mailto:chelliot at pobox.com>> wrote:
>>
>>  You should be seeing about 60kBps. Which means it should take about 20
>>> hours to download. Please let me know if that's about what you're
>>> seeing now.
>>>
>>> On Thu, Jun 17, 2010 at 10:53 AM, Chris Elliott <
>>> <mailto:chelliot at pobox.com>chelliot at pobox.com
>>> <mailto:chelliot at pobox.com>> wrote:
>>>
>>>    Menno,
>>>
>>>    I see you copying the files to <http://osx6.ripe.net>osx6.ripe.net
>>>    <http://osx6.ripe.net>. Wej (Bill Jensen) was also copying them up
>>>    to the Univ. of Wisconsin. I've asked him to hold off so you can
>>>    better utilize my meager upload bandwidth.
>>>
>>>    Hopefully it'll speed up now. Please let me know if you have any
>>>    problems or if it's just too slow. I could sneaker-net them to
>>>    somewhere with a bigger pipe, if necessary.
>>>
>>>    Chris.
>>>
>>>    On Thu, Jun 17, 2010 at 10:49 AM, Menno Schepers <
>>>    <mailto:mschepers at ripe.net>mschepers at ripe.net
>>>    <mailto:mschepers at ripe.net>> wrote:
>>>
>>>        Hi Chris,
>>>
>>>        Thanks, I'm downloading them since this morning:
>>>
>>>        ietf-mgmt.before.ietf78.tgz 29% 1176MB 59.9KB/s 13:20:27 ET
>>>
>>>        Should be in by Monday. Then I'll try to fire 'm up.
>>>
>>>        -Menno
>>>
>>>
>>>        On 6/17/10 06:45 , Chris Elliott wrote:
>>>
>>>            Menno,
>>>
>>>            OK--VM's are intact and I've tried to undo some of the
>>>            damage we did in
>>>            Anaheim with funky addressing, etc.
>>>
>>>            You can get to the VM images here:
>>>
>>>            scp
>>>            <mailto:ietf78 at chelliot.dyndns.org>ietf78 at chelliot.dyndns.org
>>>            <mailto:ietf78 at chelliot.dyndns.org>
>>>            <
>>>            <http://chelliot.dyndns.org>http://chelliot.dyndns.org
>>> >://Users/ietf78/ietf-*
>>>            <local_path>
>>>
>>>
>>>            The two files are ietf-mgmt.before.ietf78.tgz and
>>>            ietf-services.before.ietf78.tgz. There's the main VM and a
>>>            snapshot in each.
>>>
>>>            The password is ******, but replace the e's with 3's. This
>>>            is also the
>>>
>>>            password for the admin accounts on the VM's.
>>>
>>>            Note that this is my home machine, so it may take quite a
>>>            while to get
>>>            them. They are 3.9 and 3.1G respectively.
>>>
>>>            ietf-services is on 130.129.5.6 and expects a router at
>>>            130.129.5.1.
>>>            Ditto for v6. Note that it will become a DNS/DHCP/etc.
>>>            server, so don't
>>>            put it somewhere that will be an issue.
>>>            ietf-mgmt is on both 130.129.1.12 and 130.129.5.12. Ditto
>>>            on v6 here as
>>>            well. Expects a router at .1. Will probably start trying
>>>            to manage
>>>            things on 130.129/16, but shouldn't do any harm. Expects
>>>            to get DNS from
>>>            ietf-services at 130.129.5.6, as well as probably NTP, etc.
>>>
>>>            Despite the addressing table I sent out earlier, it
>>>            appears that
>>>            ietf-mgmt is expecting 130.129.1.0 to be a /24, not /23.
>>>            However, as a
>>>            host, it won't really matter much if the router is setup
>>>            to do proxy
>>>            arp. And for our purposes now, it makes no difference.
>>>
>>>            I cranked down the memory and CPU's on the VM's. You might
>>>            want to crank
>>>            them back up, depending on the host system. They were 1G
>>>            mem or so and
>>>            ietf-services had two cores allocated to it. They're down
>>>            to 512M and
>>>            one core each. Had to fit them on my core duo 2G machine...
>>>
>>>            Please let me know if this works for you.
>>>
>>>            Enjoy!
>>>            Chris.
>>>
>>>            On Wed, Jun 16, 2010 at 5:22 PM, Chris Elliott <
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com>
>>>            <mailto: <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com>>> wrote:
>>>
>>>            Forgot to copy the list...wish there was some way to
>>>            default to
>>>            reply all in gmail...
>>>
>>>            On Wed, Jun 16, 2010 at 5:21 PM, Chris Elliott <
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com>
>>>            <mailto: <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com>>> wrote:
>>>
>>>            Menno,
>>>
>>>            I have found the VM's. I'm bringing the up on my laptop
>>>            briefly
>>>            so I can get you the requisite information on them. I will
>>>            then
>>>            find a place to share them so you can download them. They are
>>>            about 13GB total, so I will need to find somewhere to put
>>>            them.
>>>            I can host them here at my house, but it'll be a bit slow. If
>>>            you have a site I can drop them that would probably be better.
>>>
>>>
>>>            In the meantime, here's some details:
>>>
>>>
>>>            VLAN's: I just uploaded an old document that I found on the
>>>            VLAN's we've used. It's from IETF72 Dublin. However, I think
>>>            it's close enough to start with. I've put it in a Google Docs
>>>            spreadsheet that's here:
>>>
>>>            <
>>> http://spreadsheets.google.com/ccc?key=0AhIPTCjz0stDdDgtX0oxcndoNUtPdkRXWmdKdERFQnc&hl=en
>>> >
>>> http://spreadsheets.google.com/ccc?key=0AhIPTCjz0stDdDgtX0oxcndoNUtPdkRXWmdKdERFQnc&hl=en
>>>            <
>>> http://spreadsheets.google.com/ccc?key=0AhIPTCjz0stDdDgtX0oxcndoNUtPdkRXWmdKdERFQnc&hl=en
>>> >
>>>            <
>>>            <
>>> http://spreadsheets.google.com/ccc?key=0AhIPTCjz0stDdDgtX0oxcndoNUtPdkRXWmdKdERFQnc&hl=en
>>> >
>>> http://spreadsheets.google.com/ccc?key=0AhIPTCjz0stDdDgtX0oxcndoNUtPdkRXWmdKdERFQnc&hl=en
>>>            <
>>> http://spreadsheets.google.com/ccc?key=0AhIPTCjz0stDdDgtX0oxcndoNUtPdkRXWmdKdERFQnc&hl=en
>>> >>
>>>
>>>            This document is editable by anyone that has this link. Please
>>>            feel free to update it as needed. This applies to anyone
>>>            on this
>>>            list.
>>>
>>>            I'm also attaching a text version.
>>>
>>>            Once we have the VM's up we can use the Wiki to hold this kind
>>>            of information.
>>>
>>>
>>>            Addressing: This is all from memory, and out of date. I'll
>>>            update once I get the VM's running.
>>>
>>>            The routers typically live at (IPv4) .1, .2, and .3, with
>>>            .1 the
>>>            virtual router address, on all the subnets. I believe that
>>>            it's
>>>            the equivalent for v6 (:1, :2, :3), but someone slap me if I'm
>>>            wrong.
>>>
>>>            The VM host machine and the VM's live primarily on the Server
>>>            VLAN (vlan 5, 130.129.5.0/24 <http://130.129.5.0/24> <
>>>            <http://130.129.5.0/24>http://130.129.5.0/24>,
>>>
>>>            2001:df8:0:5::/64), but may have additional interfaces. For
>>>            example, the Management VM also has an address on the
>>>            Management
>>>            VLAN (vlan 1, 130.129.1.0/23 <http://130.129.1.0/23> <
>>>            <http://130.129.1.0/23>http://130.129.1.0/23>,
>>>
>>>            2001:df8::/64).
>>>
>>>            The host machines we've used with Verilan were called
>>>            Peter and
>>>            Egon and were addressed at 130.129.5.6 and 130.129.5.7, with a
>>>            virtual address at 130.129.5.5 used for services like DNS
>>>            (equivalent addresses for v6). However, we transistioned to
>>>            using VM's and I can't remember for sure what their addresses
>>>            were (.10 and .11???). Once I find the VM's...
>>>
>>>
>>>            Enjoy!
>>>            Chris.
>>>
>>>
>>>            On Wed, Jun 16, 2010 at 4:59 AM, Menno Schepers
>>>            < <mailto:mschepers at ripe.net>mschepers at ripe.net
>>>            <mailto:mschepers at ripe.net> <mailto:
>>>            <mailto:mschepers at ripe.net>mschepers at ripe.net
>>>            <mailto:mschepers at ripe.net>>> wrote:
>>>
>>>            Hi,
>>>
>>>            Can we get the VMware images of the virtuals? If you could
>>>            send me a
>>>            login details for ssh so I could scp them to here or
>>>            something similar
>>>            that would be great.
>>>
>>>            Also a list of used vlan's and their IP ranges and gateway
>>>            ip's used for
>>>            the router.
>>>
>>>            -Menno
>>>            _______________________________________________
>>>            ietf78-tech mailing list
>>>            <mailto:ietf78-tech at daedelus.com>ietf78-tech at daedelus.com
>>>            <mailto:ietf78-tech at daedelus.com> <mailto:
>>>            <mailto:ietf78-tech at daedelus.com>ietf78-tech at daedelus.com
>>>            <mailto:ietf78-tech at daedelus.com>>
>>>
>>>            <http://www.daedelus.com/mailman/listinfo/ietf78-tech>
>>> http://www.daedelus.com/mailman/listinfo/ietf78-tech
>>>
>>>
>>>
>>>
>>>            --
>>>            Chris Elliott
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com> <mailto:
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com>>
>>>
>>>
>>>
>>>
>>>            --
>>>            Chris Elliott
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com> <mailto:
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com>>
>>>
>>>
>>>
>>>
>>>            --
>>>            Chris Elliott
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com> <mailto:
>>>            <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>            <mailto:chelliot at pobox.com>>
>>>
>>>
>>>
>>>
>>>
>>>    --
>>>    Chris Elliott
>>>    <mailto:chelliot at pobox.com>chelliot at pobox.com
>>>    <mailto:chelliot at pobox.com>
>>>
>>>
>>>
>>>
>>> --
>>> Chris Elliott
>>> <mailto:chelliot at pobox.com>chelliot at pobox.com <mailto:chelliot at pobox.com
>>> >
>>>
>>> _______________________________________________
>>> ietf78-tech mailing list
>>> ietf78-tech at daedelus.com <mailto:ietf78-tech at daedelus.com>
>>> http://www.daedelus.com/mailman/listinfo/ietf78-tech
>>>
>>
>


-- 
Chris Elliott
chelliot at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.daedelus.com/pipermail/ietf78-tech/attachments/20100617/3232f6a6/attachment-0001.html 


More information about the ietf78-tech mailing list