files.pharo.org: Moving to new server

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

files.pharo.org: Moving to new server

Marcus Denker-4
Hi,

We will change the DNS to a new server.

This should be transparent, but of course we never know…

Stages:

        1) Change DNS to point to new server of   (TODAY)
                        files.pharo.org
                        get.pharo.org
                        updates.pharo.org

        2) Change DNS Server from NameCheap to new provider  (TOMORROW)
            (this will speed up DNS queries ;-)

        3) enable CDN for the static files.  (NEXT WEEK)


        Marcus and Camillo
Reply | Threaded
Open this post in threaded view
|

Re: files.pharo.org: Moving to new server

Marcus Denker-4

On Apr 18, 2013, at 3:01 PM, Marcus Denker <[hidden email]> wrote:

> Hi,
>
> We will change the DNS to a new server.
>
> This should be transparent, but of course we never know…
>
> Stages:
>
> 1) Change DNS to point to new server of   (TODAY)
> files.pharo.org
> get.pharo.org
> updates.pharo.org
>

Success! DNS has propagated (at least to here) and it works.
I should be more reliable and faster.
       
        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: files.pharo.org: Moving to new server

Camillo Bruni-3
In reply to this post by Marcus Denker-4

On 2013-04-18, at 15:02, Marcus Denker <[hidden email]> wrote:

> Hi,
>
> We will change the DNS to a new server.
>
> This should be transparent, but of course we never know…
>
> Stages:
>
> 1) Change DNS to point to new server of   (TODAY)
> files.pharo.org
> get.pharo.org
> updates.pharo.org
>
> 2) Change DNS Server from NameCheap to new provider  (TOMORROW)
>    (this will speed up DNS queries ;-)
>
> 3) enable CDN for the static files.  (NEXT WEEK)

The CDN should give some speedup for people overseas (US / ASIA), curious to
see how much impact this will have :)
Reply | Threaded
Open this post in threaded view
|

Re: files.pharo.org: Moving to new server

Marcus Denker-4
In reply to this post by Marcus Denker-4

On Apr 18, 2013, at 5:43 PM, Marcus Denker <[hidden email]> wrote:

>
> On Apr 18, 2013, at 3:01 PM, Marcus Denker <[hidden email]> wrote:
>
>> Hi,
>>
>> We will change the DNS to a new server.
>>
>> This should be transparent, but of course we never know…
>>
>> Stages:
>>
>> 1) Change DNS to point to new server of   (TODAY)
>> files.pharo.org
>> get.pharo.org
>> updates.pharo.org
>>
>
> Success! DNS has propagated (at least to here) and it works.
> I should be more reliable and faster.

What is missing is the Platforms Dir…

        http://files.pharo.org/platform/Pharo3.0-mac.zip

Will be fixed soon…

        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: files.pharo.org: Moving to new server

Marcus Denker-4

On Apr 19, 2013, at 7:55 AM, Marcus Denker <[hidden email]> wrote:

>
> On Apr 18, 2013, at 5:43 PM, Marcus Denker <[hidden email]> wrote:
>
>>
>> On Apr 18, 2013, at 3:01 PM, Marcus Denker <[hidden email]> wrote:
>>
>>> Hi,
>>>
>>> We will change the DNS to a new server.
>>>
>>> This should be transparent, but of course we never know…
>>>
>>> Stages:
>>>
>>> 1) Change DNS to point to new server of   (TODAY)
>>> files.pharo.org
>>> get.pharo.org
>>> updates.pharo.org
>>>
>>
>> Success! DNS has propagated (at least to here) and it works.
>> I should be more reliable and faster.
>
> What is missing is the Platforms Dir…
>
> http://files.pharo.org/platform/Pharo3.0-mac.zip
>
> Will be fixed soon…
>

Camillo fixed it.

Next: DNS Server (after Lunch).

This might impact the URL forwards
        ci.pharo.org
        pharo.org

as forwarding is done differently on the new setup.

        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: files.pharo.org: Moving to new server

Marcus Denker-4

On Apr 19, 2013, at 11:21 AM, Marcus Denker <[hidden email]> wrote:

>
>
> Next: DNS Server (after Lunch).
>
> This might impact the URL forwards
> ci.pharo.org
> pharo.org
>
> as forwarding is done differently on the new setup.
>

We decided to do that next week… mostly because URL forwarding like
is was done at namecheap is more complicated with the new DNS provider
(read: they don't do that, as it is not DNS but needs a server).

Instead we managed to the whole update cycle to work again for 3.0 using
the new server (which was more complex than imaginable…).

TODO

for CND
        -> setup server for forwarding DNS entries to URLs
        -> Switch DNS Provider
        -> enable caching CDN

for updating

        -> fix 2.0 like we did 3.0 today
        -> fine-tune changed update process


        Marcus