Wave Downtime (Sept 14, 10:00PM MTV time) and Migration!

[Greg D]

Hello Wave Users!

We are just about ready to roll-out an overhaul of our Operational
Transformation code. It enables both better stability at the core of
Wave as well as (soon) the opportunity to talk to other Wave Servers
that are being built outside of Google.

In order to do this we need to take Wave down for 8 hours starting at
10:00PM MTV time on Sept 14.

Unfortunately, there isn't any way for us to convert the history of
your current waves to the new infrastructure. The current state of
your waves will remain intact; only the history will be impacted. To
be exact:
- Waves won't show playback for changes made prior to Sept 14 (MTV
time)
- When you open a wave that was changed prior to Sept 14, we will not
be able to show the yellow/pink diff highlighting of exactly what
changed since you last read the wave.

This sort of upgrade is something we can't reasonably do once we've
launched our wider preview on September 30, which means that we need
to perform this upgrade now and another similar one in about a week.

If you have any questions or concerns, please feel free to add to this
Wave:
https://wave.google.com/a/wavesandbox.com/#minimized:nav,minimized:contact,minimized:search,restored:wave:wavesandbox.com!w%252B59rAEB6O%2525C.1

Thanks!

Greg D
Product Manager, Google Wave

[Greg D]

Er, when I said MTV time, I meant US PST. I work out of the Sydney
Australia office and am too used to talking to Google colleagues in
Mountain View!

Thanks!

Greg

> Wave:https://wave.google.com/a/wavesandbox.com/#minimized:nav,minimized:co...

[James Purser]

On Mon, 2009-09-14 at 05:20 -0700, Greg D wrote:
> Er, when I said MTV time, I meant US PST. I work out of the Sydney
> Australia office and am too used to talking to Google colleagues in
> Mountain View!
>
> Thanks!
>
> Greg

Heh no worries, I did have Dire Straits running through my head when I
read that though ;)

James Purser

[Sam Osborne]

Thanks for the info! Will keep it in mind... However, one question: What is that in GMT, please? Thanks :)

2009/9/14 James Purser <jamesr...@gmail.com>

[sim sim]

GMT is Google Man Time

2009/9/14 Sam Osborne <sam.to...@googlemail.com>

[Joel Dietz]

Right now PDT. GMT - 7.

[Denis Zgonjanin]

that's Greenwich Mean Time, in London, England

--
Denis Zgonjanin
Blindside Networks
http://www.blindsidenetworks.com/

[Sam Osborne]

3pm then.. So, for me, basically don't use it for... Wait, today!

2009/9/14 Denis Zgonjanin <me....@gmail.com>

[Daniel Faust]

http://www.wolframalpha.com/input/?i=10pm+pst

Nothing beats wolfram alpha in time/date computations.

[Sam Osborne]

AMAZING!

[Daniel Faust]

Greg D.,

regarding the transition from wavesandbox.com to wave.google.com on
the 30th of September, how are sandbox user accounts going to be
mapped to google.com accounts?

Kind regards,
Daniel

[Brian May]

On Mon, Sep 14, 2009 at 09:46:23AM -0700, Daniel Faust wrote:
>
> http://www.wolframalpha.com/input/?i=10pm+pst

What is this meant to do?

I get:

Wolfram|Alpha isn't sure what to do with your input.

What I find really useful is this site:

http://www.timeanddate.com/worldclock/meetingtime.html?month=9&day=15&year=2009&p1=152&p2=127&p3=-1&p4=-1

From this I see the downtime as

14th 22:00 - 15th 06:00 Las Vegas
15th 05:00 - 15th 13:00 UTC
15th 15:00 - 15th 23:00 Melbourne

So I guess that means the changes haven't yet occurred. Assuming I got the date correct.
--
Brian May <br...@microcomaustralia.com.au>

[Brian May]

On Mon, Sep 14, 2009 at 02:06:35PM -0700, Daniel Faust wrote:
> regarding the transition from wavesandbox.com to wave.google.com on
> the 30th of September, how are sandbox user accounts going to be
> mapped to google.com accounts?

Did you see the discussion here?

http://groups.google.com/group/google-wave-api/browse_thread/thread/e65e750a8f9b045e/68cb26e335496c3f?lnk=gst&q=office+hours+#68cb26e335496c3f

If so, apologies for telling you what you already know ;-).
--
Brian May <br...@microcomaustralia.com.au>

[Greg D]

As you might've already noticed, we didn't have the downtime today.
We needed one more day to prepare (migrating all Operations in Wave
takes more work than you might think!). We are moving the downtime 1
day. So Sept 15 (US PST) now at 10:00PM is our target.

Sorry for shifting things around, and thanks for your patience!

Greg

PS - After reading the comment about Dire Straits, I now have, we are
the Sultans of Wave running through my head...

On Sep 14, 10:17 pm, Greg D <gr...@google.com> wrote:

> Wave:https://wave.google.com/a/wavesandbox.com/#minimized:nav,minimized:co...

[Suhas Nandakumar]

Hi All,

  

 May be i am missing out something very basic here .. Isn't the Operational Transformation a generic standard implementation that should be  independent of  any wave server implementation.

  I am not clear on this statement in particular

   " We are just about ready to roll-out an overhaul of our Operational Transformation code. It enables both better stability at the core of  Wave as well as (soon) the opportunity to talk to other Wave Servers that are being built outside of Google."

Can some one enlighten me on relation between OT implementation on different wave servers.

Thanks

./Suhas

[Freddie Pohls]

Probably so....

--
Sent from My Macbook Pro

[Joel Dietz]

OT is the algorithm. I suspect what is being changed is not the algorithm but the code which implements it.

OT is applied in the client and the server. I assume the server is optimized in some fashion which involves batching, and that something about the way it is done now on the server (likely optimization and storage that relies on proprietary Google architecture) prevents the code from being duplicated on other servers. For instance, I would not be surprised if there is some lag time between when any given set of operations is applied in the client and when the same set is applied in the data store.

[Brian May]

On Tue, Sep 15, 2009 at 06:32:12AM -0700, Greg D wrote:
> As you might've already noticed, we didn't have the downtime today.
> We needed one more day to prepare (migrating all Operations in Wave
> takes more work than you might think!). We are moving the downtime 1
> day. So Sept 15 (US PST) now at 10:00PM is our target.

I hope this downtime happens soon... I am looking forward to testing the new
code.

I believe it is now "Wednesday, September 16, 2009 at 1:37:40 AM PDT", and I
haven't noticed any changes yet.
--
Brian May <br...@microcomaustralia.com.au>

[Pierre]

Migration in progress?

Got an error message 'The server encountered a temporary error and
could not complete your request.' when trying to reach
https://wave.google.com/a/wavesandbox.com/

Pierre

[Claudemir Todo Bom]

Looks like it is happening now... just when I got my wave invite! :-)

will have to wait a little more to play with the thing!

[Freddie Pohls]

It happened to me too! When I tried to get on the Sandbox the Google Error came up and said "The server encountered a temporary error and could not complete your request Try again in 30 seconds" Maybe there is an error with the server?

[Nitsuga]

Is it over? I'm kinda confused with all the time differences...

On Sep 16, 3:19 pm, Freddie Pohls <davinci.pohl...@gmail.com> wrote:
> It happened to me too! When I tried to get on the Sandbox the Google Error
> came up and said "The server encountered a temporary error and could not
> complete your request Try again in 30 seconds" Maybe there is an error with
> the server?
>

[Monika Adamczyk]

Looks like it is still down (12.30 EST).

Monika

[Freddie Pohls]

Nope it's still an Error

[Sam Osborne]

It's 6PM GMT over here, and I'm still getting 502 errors at http://wavesandbox.com Anyone else got similar problems? Chrome 4 on Ubuntu/Linux

looks like you are... By the way, to find out time differences, search on Wolfram|Alpha for the time (including time zone, eg PST, GMT etc) and it gives you the difference.

2009/9/16 Freddie Pohls <davinci...@gmail.com>

[Sam Osborne]

Is it finished? It sure looks like it to me, I can NOW get on. 6:48PM GMT

2009/9/16 Sam Osborne <sam.to...@googlemail.com>

[Daniel Faust]

About an hour ago I was getting the "The server encountered a

temporary error and could not

complete your request Try again in 30 seconds" message.

Currently I'm able to log in, but some Waves have no content, and
newly created waves don't get saved (well some get, some don't).
Robots are also not working.

On Sep 16, 7:46 pm, Sam Osborne <sam.tosbo...@googlemail.com> wrote:
> It's 6PM GMT over here, and I'm still getting 502 errors athttp://wavesandbox.comAnyone else got similar problems? Chrome 4 on
> Ubuntu/Linuxlooks like you are... By the way, to find out time differences,

> search on Wolfram|Alpha for the time (including time zone, eg PST, GMT etc)
> and it gives you the difference.
>

> 2009/9/16 Freddie Pohls <davinci.pohl...@gmail.com>

[Eric Kidd]

On Sep 16, 4:33 am, Joel Dietz <jdi...@gmail.com> wrote:
> OT is the algorithm. I suspect what is being changed is not the algorithm
> but the code which implements it.

[Please take this with a grain of salt, because it's based on reading
the FedOne OT code and looking at the Google Wave debugger. :-) ]

As I understand it, Google is still fine-tuning the OT algorithm, and
they want to make a few changes before they go live. For example, the
OT code running on wavesandbox.com is considerably older than the OT
code in the open source FedOne server. And there's a newer, unreleased
version of the OT code which tweaks the compositing algorithm and
makes some other changes.

Presumably, once Google gets the details of the OT algorithm right,
they will turn on federation. I'm looking forward to that day eagerly,
because it will be easier to write scalable robots once we have access
to the raw WaveDocumentOperations.

Cheers,
Eric

P.S. The Wave server came back up within the last 15 minutes, AFAICT.
I can create new waves, and I can see old waves in my search results,
but old waves are currently inaccessible.

[Daniel Faust]

Now it's working.

[Sam Osborne]

Looks like we've got a new Uploading Waves thing... There's a Syncing above the Inbox pane. Looks good!

2009/9/16 Daniel Faust <sound...@gmail.com>

Now it's working.

[DanielleMorrill]

I am still getting a 502 error as well. Firefox on Mac OSX

On Sep 16, 10:46 am, Sam Osborne <sam.tosbo...@googlemail.com> wrote:
> It's 6PM GMT over here, and I'm still getting 502 errors athttp://wavesandbox.comAnyone else got similar problems? Chrome 4 on
> Ubuntu/Linuxlooks like you are... By the way, to find out time differences,

> search on Wolfram|Alpha for the time (including time zone, eg PST, GMT etc)
> and it gives you the difference.
>

> 2009/9/16 Freddie Pohls <davinci.pohl...@gmail.com>

[WaveyGravey]

FYI - I'm able to access the wavesandbox now.

[Pierre]

Wave is back...
8pm GMT/UTC - 1pm PST

[Jason Wagner]

It's back!

On Sep 16, 1:46 pm, Sam Osborne <sam.tosbo...@googlemail.com> wrote:
> It's 6PM GMT over here, and I'm still getting 502 errors athttp://wavesandbox.comAnyone else got similar problems? Chrome 4 on
> Ubuntu/Linuxlooks like you are... By the way, to find out time differences,

> search on Wolfram|Alpha for the time (including time zone, eg PST, GMT etc)
> and it gives you the difference.
>

> 2009/9/16 Freddie Pohls <davinci.pohl...@gmail.com>

[gengstrand]

I'm not having any problems at all with either the wave or the robot.

On Sep 16, 11:46 am, Sam Osborne <sam.tosbo...@googlemail.com> wrote:
> It's 6PM GMT over here, and I'm still getting 502 errors athttp://wavesandbox.comAnyone else got similar problems? Chrome 4 on
> Ubuntu/Linuxlooks like you are... By the way, to find out time differences,

> search on Wolfram|Alpha for the time (including time zone, eg PST, GMT etc)
> and it gives you the difference.
>

> 2009/9/16 Freddie Pohls <davinci.pohl...@gmail.com>

[AP]

Guys chk this out...

http://microreviews.org/lissn-twitter-and-google-wave-combined-and-simplified/

On Sep 16, 10:47 pm, Jason Wagner <jcw5...@gmail.com> wrote:
> It's back!
>
> On Sep 16, 1:46 pm, Sam Osborne <sam.tosbo...@googlemail.com> wrote:
>
>
>

> > It's 6PM GMT over here, and I'm still getting 502 errors athttp://wavesandbox.comAnyoneelse got similar problems? Chrome 4 on