Thursday, July 21, 2011

Prediction: The "Cloud" and Bandwidth

This post is the start of a new type of post in which I will make predictions for the future of IT.  These are purely my opinion and should be taken as such - don't bet the farm on any of them!

To start it off, here's my first prediction:

When national bandwidth infrastructure improves drastically, the "cloud" finally has a chance to be relevant for storing/retrieving large data efficiently.

By the way, by "cloud", I do mean a private cloud, or a public/shared cloud.

What I mean by this is, right now, so many of us are limited to a few Mbps (usually 3 or less) download speed.  For businesses with symmetric connections, upload speed is roughly the same (3 or less), and for residential areas, unless you can get FIOS or another high speed connection, usually upload is below 1Mbps.

I predict that when we have at least 100Mbps, if not much greater (such as 1Gbps) to the home, and to the business, and transferring bits becomes cheaper and more affordable, having all our data (large and small) live in the cloud can finally be more feasible.  The only problem standing in the way of the cloud at that point is security.  No predictions about that!

Think about trying to back up your servers from your datacenter to a cloud location or off-site.  Got enough bandwidth?  How many hours does it take?  How about backing up your own personal photo collections off-site?  How many hours does it take to get it to a service like Mozy or Carbonite?

These types of services, among others, such as streaming audio and video, will only improve with more bandwidth.  And maybe, just maybe, with more bandwidth, the idea that my operating system lives mostly in the cloud becomes ever closer a reality.  Should we want that?  Again, that's not a prediction for today!

We're hungry for bandwidth.  Who will feed the need?

CentOS 5.5 and NX Server >3.4

If you've set up NX Server on CentOS 5.5 by downloading it directly from the NoMachine website, and you try to connect to your newly minted install using SSH and a DSA key, and you encounter a problem where the server gives you a message something like this:

NX> 203 NXSSH running with pid: NNNN
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options 

NX> 200 Connected to address: NNN.NNN.NNN.NNN on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey 

NX> 204 Authentication failed.

Check to make sure that you have synchronized the name of the authorized_keys file in the NX server.cfg, node.cfg and your sshd_config files.  I discovered that server.cfg and node.cfg were looking for authorized_keys2 and the sshd_config was looking for authorized_keys.  Match those values and restart the server (as described here) and you should have better luck.  Apparently, authorized_keys2 was deprecated a long time ago.

Other useful links: