GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What is the difference between cloud computing, private cloud, and remote access.
I did it several years ago on client via ssh connecting the server, to start the application on the server remotely and displaying the same locally. Files can be saved either locally or on the server. What I did NOT test is whether X forwarding works if the client, the remote workstation, only has a basic OS running without GUI. Can X forwarding work? That is, connecting the server on the client via "ssh -X server_IP". Can it work?
Now it comes to my notice that cloud computing, private cloud, does the same job. I haven't had an in-depth penetration on its documentation. But the principle sounds to me similar. The only difference is the remote client can start/connect server_B on Server_A after connecting the later.
Please shed me some light. Pointers would be appreciated. TIA
Think of cloud computing as running a program like OpenOffice or something like that in a web browser. It only changes specific files, and generally not on the server. The server may host the actual program, but you don't save anything to the server. Or you can take Pandora.com as an example. They serve a media player, but you can't do anything else to the system aside from playing files.
Remote access is like using the computer as though you were in front of it, but you're really 2 states away. You can make system changes and such. You can save a file to the desktop. GotoMyPC is an example of remote access. It's as if you were actually typing on the keyboard at that computer.
Cloud vs. Private Cloud is just a reference to an internet application (Pandora.com) vs. an intranet application (something like an OpenOffice.org application for your business not intended for the general public). Private cloud generally speaks of businesses who have a network internal to the company. Whether or not it connects to the internet is irrelevant. The cloud applications are provided within that business. You access the applications through a web browser.
Think of cloud computing as an entry into Boardroom Bullshit Bingo. It is nothing more than the mainframe/terminal vs. standalone PC argument that has been erupting on a regular basis since the dawn of personal computing.
IMHO, 'cloud' is a buzzword, and a dangerous one at that. It's 'dangerous' because it encourages people to not actually think about where their data is, and under what terms and conditions it is stored. To take a simple example, a British company using a cloud service or provider based in the USA is subjecting their data to US law, quite probably without being aware of the full implications of that.
You might say that the idea of "cloud" is that: you don't know (or care) where 'the server' is.
Likewise: the servers don't care where their 'daily bread' is coming from.
In an ideal scenario, "computing resources" and "computing clients" would find each other in a way that "load-balances itself."
I actually put together my random thoughts on that subject, sometime long ago, here... (Go ahead: print it off and line your parakeet's cage with it. I won't mind.)
Distribution: Ubuntu Server v8.04 / v11.10 & Mac OsX (mainly for FCP & video/audio)
Posts: 35
Rep:
Cloud Computing and Hosting
Hi,
I wanted to set up my new inexpensive hosting service on a Cloud type system to 'keep up with Joneses', but after recently attending the NY/NJ Linux End User Summit and firing questions at both the IBM and Novell Reps (both were pushing their Cloud systems) "How Secure Is It", as neither would say "it's secure", I've decided not to Host on a Cloud. I'll use a feather mattress instead.
I've decided instead to build a 'Cloud Like' system where members can add and remove utilities if, and when, they need them saving money in the long run - instead of signing up with a huge package of extras where most only use 20-25% of them.
Why pay for what you don't use !!!
The advantages of less latency than hosting on a cluster in a mirrored server farm is not enough of an incentive to out way the low security.
Bottom line is, Cloud is just another name for the Web - and spreading your data on multiple servers all over the Web can, in no way, be secure.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.