seaside.gemstone.com down - unable to build 1.1-dev

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

seaside.gemstone.com down - unable to build 1.1-dev

Torsten Bergmann
http://seaside.gemstone.com/ss/metacello/ is down,
therefore ConfigurationOfPharo can not be used to
build Pharo 1.1. from an updated core.

See http://downforeveryoneorjustme.com/seaside.gemstone.com

Maybe the machine is switched to vmware.com?

However - we should again think about reliable
infrastructure ...

Thx
T.


--
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

Mariano Martinez Peck


On Fri, Jun 11, 2010 at 1:53 PM, Torsten Bergmann <[hidden email]> wrote:
http://seaside.gemstone.com/ss/metacello/ is down,
therefore ConfigurationOfPharo can not be used to
build Pharo 1.1. from an updated core.

See http://downforeveryoneorjustme.com/seaside.gemstone.com

Maybe the machine is switched to vmware.com?

However - we should again think about reliable
infrastructure ...

Once I remeber Dale though about having the code in both repositories: squeaksource and gemstone. And when doing ensureMetacello, checks first in gemstone. If it fails, it tries in squeaksource...at least that was the idea...I don't know if it was implemented or not.

Cheers

mariano

 

Thx
T.


--
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

Schwab,Wilhelm K
In reply to this post by Torsten Bergmann
This is why I want to see separate web images; by not pre-packaging we just transfer the headaches from Pharo's developers to its users, increasing the number of opportunities to have failures, load on servers, etc.

Bill



-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Torsten Bergmann
Sent: Friday, June 11, 2010 6:53 AM
To: [hidden email]
Subject: [Pharo-project] seaside.gemstone.com down - unable to build 1.1-dev

http://seaside.gemstone.com/ss/metacello/ is down, therefore ConfigurationOfPharo can not be used to build Pharo 1.1. from an updated core.

See http://downforeveryoneorjustme.com/seaside.gemstone.com

Maybe the machine is switched to vmware.com?

However - we should again think about reliable infrastructure ...

Thx
T.


--
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

jgfoster
I'm investigating this with GemStone's IT people. I'll give an update as soon as I have something.

James Foster
VMware (formerly GemStone Systems)

On Jun 11, 2010, at 5:42 AM, Schwab,Wilhelm K wrote:

> This is why I want to see separate web images; by not pre-packaging we just transfer the headaches from Pharo's developers to its users, increasing the number of opportunities to have failures, load on servers, etc.
>
> Bill
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Torsten Bergmann
> Sent: Friday, June 11, 2010 6:53 AM
> To: [hidden email]
> Subject: [Pharo-project] seaside.gemstone.com down - unable to build 1.1-dev
>
> http://seaside.gemstone.com/ss/metacello/ is down, therefore ConfigurationOfPharo can not be used to build Pharo 1.1. from an updated core.
>
> See http://downforeveryoneorjustme.com/seaside.gemstone.com
>
> Maybe the machine is switched to vmware.com?
>
> However - we should again think about reliable infrastructure ...
>
> Thx
> T.
>
>
> --
> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

jgfoster
Here is the response I got from IT: "Web cluster fail. We're back up and running on a couple machines; it should be fine now."

James

On Jun 11, 2010, at 7:05 AM, James Foster wrote:

> I'm investigating this with GemStone's IT people. I'll give an update as soon as I have something.
>
> James Foster
> VMware (formerly GemStone Systems)

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

Stéphane Ducasse
Thanks James.

Stef

On Jun 11, 2010, at 5:24 PM, James Foster wrote:

> Here is the response I got from IT: "Web cluster fail. We're back up and running on a couple machines; it should be fine now."
>
> James
>
> On Jun 11, 2010, at 7:05 AM, James Foster wrote:
>
>> I'm investigating this with GemStone's IT people. I'll give an update as soon as I have something.
>>
>> James Foster
>> VMware (formerly GemStone Systems)
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

Dale Henrichs
In reply to this post by Mariano Martinez Peck

With each release I do copy the mcz files (source and configs) to
http://www.squeaksource.com/metacello, however, at the moment it takes
manual intervention to load using the alternate repository. I will spend
some time looking at the problem and see if I can make the switchover to
the alternate repository more automatic for Metacello itself...


As for the outage itself, we lost a critical machine in our data center
and service was restored shortly after 7 am PST.

While talking to our IT folks I found out that now that we have joined
VMWare, our GemStone data center will be moved to a VMWare data center
which will be an upgrade over out current hardware, so we shouldn't see
another outage like this for our server.

Dale

  Mariano Martinez Peck wrote:

>
> On Fri, Jun 11, 2010 at 1:53 PM, Torsten Bergmann <[hidden email]<mailto:[hidden email]>> wrote:
> http://seaside.gemstone.com/ss/metacello/ is down,
> therefore ConfigurationOfPharo can not be used to
> build Pharo 1.1. from an updated core.
>
> See http://downforeveryoneorjustme.com/seaside.gemstone.com
>
> Maybe the machine is switched to vmware.com<http://vmware.com>?
>
> However - we should again think about reliable
> infrastructure ...
>
> Once I remeber Dale though about having the code in both repositories: squeaksource and gemstone. And when doing ensureMetacello, checks first in gemstone. If it fails, it tries in squeaksource...at least that was the idea...I don't know if it was implemented or not.
>
> Cheers
>
> mariano
>
>
>
> Thx
> T.
>
>
> --
> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]<mailto:[hidden email]>
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

Simon Denier-3

On 11 juin 2010, at 18:52, Dale Henrichs wrote:

>
> With each release I do copy the mcz files (source and configs) to http://www.squeaksource.com/metacello, however, at the moment it takes manual intervention to load using the alternate repository. I will spend some time looking at the problem and see if I can make the switchover to the alternate repository more automatic for Metacello itself...


That's good to know. Do you do this copy automatically yet? Or is it still manual?


>
>
> As for the outage itself, we lost a critical machine in our data center and service was restored shortly after 7 am PST.
>
> While talking to our IT folks I found out that now that we have joined VMWare, our GemStone data center will be moved to a VMWare data center which will be an upgrade over out current hardware, so we shouldn't see another outage like this for our server.
>
> Dale
>
> Mariano Martinez Peck wrote:
>> On Fri, Jun 11, 2010 at 1:53 PM, Torsten Bergmann <[hidden email]<mailto:[hidden email]>> wrote:
>> http://seaside.gemstone.com/ss/metacello/ is down,
>> therefore ConfigurationOfPharo can not be used to
>> build Pharo 1.1. from an updated core.
>> See http://downforeveryoneorjustme.com/seaside.gemstone.com
>> Maybe the machine is switched to vmware.com<http://vmware.com>?
>> However - we should again think about reliable
>> infrastructure ...
>> Once I remeber Dale though about having the code in both repositories: squeaksource and gemstone. And when doing ensureMetacello, checks first in gemstone. If it fails, it tries in squeaksource...at least that was the idea...I don't know if it was implemented or not.
>> Cheers
>> mariano
>> Thx
>> T.
>> --
>> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
>> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]<mailto:[hidden email]>
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
 Simon




_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

Dale Henrichs
Simon Denier wrote:
> On 11 juin 2010, at 18:52, Dale Henrichs wrote:
>
>> With each release I do copy the mcz files (source and configs) to http://www.squeaksource.com/metacello, however, at the moment it takes manual intervention to load using the alternate repository. I will spend some time looking at the problem and see if I can make the switchover to the alternate repository more automatic for Metacello itself...
>
>
> That's good to know. Do you do this copy automatically yet? Or is it still manual?
>
>

Manual with 1.0-beta.26.3, but I'm thinking I can get it to switch over
automatically. this week I should be able to get back into the swing of
things ...

Dale

>>
>> As for the outage itself, we lost a critical machine in our data center and service was restored shortly after 7 am PST.
>>
>> While talking to our IT folks I found out that now that we have joined VMWare, our GemStone data center will be moved to a VMWare data center which will be an upgrade over out current hardware, so we shouldn't see another outage like this for our server.
>>
>> Dale
>>
>> Mariano Martinez Peck wrote:
>>> On Fri, Jun 11, 2010 at 1:53 PM, Torsten Bergmann <[hidden email]<mailto:[hidden email]>> wrote:
>>> http://seaside.gemstone.com/ss/metacello/ is down,
>>> therefore ConfigurationOfPharo can not be used to
>>> build Pharo 1.1. from an updated core.
>>> See http://downforeveryoneorjustme.com/seaside.gemstone.com
>>> Maybe the machine is switched to vmware.com<http://vmware.com>?
>>> However - we should again think about reliable
>>> infrastructure ...
>>> Once I remeber Dale though about having the code in both repositories: squeaksource and gemstone. And when doing ensureMetacello, checks first in gemstone. If it fails, it tries in squeaksource...at least that was the idea...I don't know if it was implemented or not.
>>> Cheers
>>> mariano
>>> Thx
>>> T.
>>> --
>>> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
>>> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]<mailto:[hidden email]>
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
>  Simon
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: seaside.gemstone.com down - unable to build 1.1-dev

Dale Henrichs
In reply to this post by Simon Denier-3
Simon Denier wrote:
> On 11 juin 2010, at 18:52, Dale Henrichs wrote:
>
>> With each release I do copy the mcz files (source and configs) to http://www.squeaksource.com/metacello, however, at the moment it takes manual intervention to load using the alternate repository. I will spend some time looking at the problem and see if I can make the switchover to the alternate repository more automatic for Metacello itself...
>
>
> That's good to know. Do you do this copy automatically yet? Or is it still manual?

Simon,

Upon rereading your mail, I think that my first response was off base
... the answer is that it is semi-automatic in that I use the method
ConfigurationOfMetacello class>>releaseMetacelloVersion to do all of the
copying ... I've used it for the last several releases and since it is
running smoothly I will probably add it to the OB-Metacello menu in some
form - assuming that that is what you mean by automatic?

Dale

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project