Sunday, April 29, 2012
“The following conclusion to me is incorrect: Google built internal servers and switches and they are using OpenFlow and therefore the companies that build servers and switches will be under enormous pressure from the network DIY movement and most likely will go out of business.

I think the following conclusion is correct: Google built a network that is adaptable to the compute requirements of their business.”

Compute Conundrum for Vendors « SIWDT

Bingo. It’s not about the network. It’s about getting the damn thing out of the way.
Posted at 5:56pm 2 notes Tags: Google SDN Networking tech
Wednesday, April 18, 2012
“Mr. Hölzle said Google would not be donating its networking software to any open source project. “It is very specialized,” he said.”

Google Opens Up About Its Network - NYTimes.com

Google’s Openflow is not your Openflow.
Posted at 2:27pm Tags: openflow sdn networking tech Google
Tuesday, April 10, 2012
“The cost that has been rising is the cost of complexity — so spending a lot of effort to make things not go wrong. There is an opportunity here for better network management and more control of the complexity, and that to me is worth experimenting with,” Hölzle said. “The real value is in the [software-defined network] and the centralized management of the network.”

How Google is using OpenFlow to lower its network costs — Cloud Computing News

When Urs speaks, datacenter peeps listen.
Posted at 8:28am 3 notes Tags: SDN Google Networks Tech
Thursday, September 8, 2011
“

The problem is we aren’t meeting this challenge. Our infrastructure is broken. Datacenters have the diameter of a microsecond, yet we are still using entire stacks designed for WANs. Real-time requires low and bounded latencies and our stacks can’t provide low latency at scale. We need to fix this problem and towards this end Luiz sets out a research agenda, targeting problems that need to be solved:

* Rethink IO software stack. An OS that makes scheduling decisions 10s of msecs is incompatible with IO devices that response in microseconds.
* Revisit operating systems scheduling.
* Rethink threading models.
* Re-read 1990’s fast messaging papers.
* Make IO design a higher priority. Not just NICs and RDMA, consider CPU design and memory systems.

” High Scalability - High Scalability - The Three Ages of Google - Batch, Warehouse, Instant (via irq)
Posted at 2:20pm 7 notes Reblogged via irq Tags: google datacenter cloud
Thursday, July 14, 2011

Google blew this last quarter out, so I took a closer look and noticed a few things:

1. Geographic revenue breakouts are US, ROW, and wait for it, the UK. WTF? Odd.

2. Holy free cash flow batman.

3. The last time I looked (which apparently was about a year ago) Google was spending about $500m a quarter on capital investments. That number is now: “$917 million, the majority of which was related to land and building purchases, and IT infrastructure investments, including data centers, servers, and networking equipment.”


The press release and such.

Posted at 8:26pm 7 notes Tags: Google Filing Nuggets datacenter
Monday, April 4, 2011
“So after a lot of thought, we’ve decided to bid for Nortel’s patent portfolio in the company’s bankruptcy auction. Today, Nortel selected our bid as the “stalking-horse bid,” which is the starting point against which others will bid prior to the auction. If successful, we hope this portfolio will not only create a disincentive for others to sue Google, but also help us, our partners and the open source community—which is integrally involved in projects like Android and Chrome—continue to innovate. In the absence of meaningful reform, we believe it’s the best long-term solution for Google, our users and our partners.”

Official Google Blog: Patents and innovation (via irq)

Google takes another potential step in becoming an even bigger force in communications, LTE, and more. Avaya bid $475 and then bought Nortel enterprise coms for $900m after outbidding Siemens. I suspect there may be a few interested parties bidding on the patent portfolio - Cisco, RIM, Nokia, Ericsson, heck, even Apple and Microsoft could end up at the party. Fascinating.
Posted at 12:05pm 3 notes Reblogged via irq Tags: Nortel google Patent
Friday, December 3, 2010
“Content creators and distributors are making huge strides in bringing us content in this way, but to do so, many require high-quality video and audio, secure delivery, and other content protection and video optimization technologies. With these tools in place they can easily and effectively give you access to the rich library of content you want to watch, with the immediacy you’ve come to expect.”

Official Google Blog: On demand is in demand: we’ve agreed to acquire Widevine

Google: The Vertically Integrated Content Service Provider?
Posted at 4:42pm Tags: video google
Tuesday, September 21, 2010

Google: We Want a New 100G MSA

Nice review of both what Google wants and how 100G is structured.

Posted at 9:38pm Tags: google 100G optics
Friday, September 3, 2010
“

This project will include:
* an application bundle including a server and web client supporting real-time collaboration using the same structured conversations as the Google Wave system

* a fast and fully-featured wave panel in the web client with complete support for threaded conversations

* a persistent wave store and search implementation for the server (building on contributed patches to implement a MongoDB store)

* refinements to the client-server protocols

* gadget, robot and data API support

* support for importing wave data from wave.google.com

* the ability to federate across other Wave in a Box instances, with some additional configuration

This project will not have the full functionality of Google Wave as you know it today. However, we intend to give developers and enterprising users an opportunity to run wave servers and host waves on their own hardware.

”

Google Wave Developer Blog: Wave open source next steps: “Wave in a Box”

XMPP lives on!
Posted at 8:21pm Tags: google
Saturday, July 24, 2010
“This is a picky wormhole, by the way; it will only suck in data that needs to travel between the researchers’ computers and Google Cloud, leaving other data flows alone. And, as long as the data is traveling in the wormhole, other traffic can’t cause any congestion that would limit throughput. We call these virtual circuits, and the OSCARS software developed here at ESnet provides the ability for our engineers to easily create and manage them.” Direct Wormhole to Google Cloud « Network Matters
Posted at 7:08pm 1 note Tags: Peer with the cloud Google cloud ESnet