<br
I agree V8, from what I know, is not evil and that the biggest issues around “evil”-ness concern are about data – as discussed in this article.
I think “data in the cloud” raises issues that are more like banking issues - We trust them to hold our money, pay us interest for the right to use it and return it when we want it. Same for google and data in the cloud – services instead of interest plus not misusing the data.
In this vain, I am more concerned about cloud providers accidentally misusing the data and even losing it if they, for example, go out of business. The FDIC at least guarantees the money given to banks (obviously very important now).
Ben Bloch
<br
Nor mine.
.....I concede that “Do No Evil” may be the motto of those who present the option to us, and they may be right. They may not be doing evil.
It wasn’t evil to put carbon dioxide in the atmosphere. It’s evil not to notice that it has consequences, and to consider them before we drown our kid’s back yard.
So let us think about this. Let us bring all of our good collective intellect to bear. Let us see how this can be dealt with. Let us imagine our ways out of the problem in several different direction. Let’s do what we usually do. Let’s have proof of concepts. Lets have running code. Let a hundred flowers bloom. Let’s sort it out.
So that when the kids go thought the snapshots and the scrapbooks after we are gone, they don’t find themselves saying. “This. This is the snapshot of the day when privacy died”.
And the bitterness of that is in the photograph they took of themselves as they did it.
| While true most of the cloud computing companies would like to become your infrastructure provider. They do not think you should be running your own data-center when you could get more bang for your buck from them. As such, most cloud providers are working to improve security of data and computing in the cloud. For example, Amazon has published a white-paper on AWS security that says that some solutions are Sarbanes-Oxley and HIPAA compliant. Additionally some companies are specializing in adding security so you can use the cloud. If a platform shift is to be made, and I think it will, then all of these objections must be overcome. Since I have seen a good amount of focus on that space I suspect it will happen. Regards, Paul Kamp --- On Mon, 9/29/08, Pietrasanta, Mark <Mark.Pie...@aquilent.com> wrote: |
alexis
They were proposing that so that users don't have to keep changing ip
addresses when they change providers.
I'm interested in reading that again, but I can't find it anymore. Was
wondering if anyone here has came across it too.
PS: Hi everyone, I'm new :-)
Warmest regards,
David
It doesn't sound like we are agreeing that violently. I think you see
my point about the Stallman objections being more about SaaS, hence my
moan about people who say SaaS=cloud.
On Tue, Sep 30, 2008 at 8:02 PM, Adwait Ullal <adwait...@gmail.com> wrote:
>
> What if:
>
> a. the API or some other aspect of say, hosting the virtual image changes or
> you need to move your VI from one provider to another
What about it? Moving a VI from one VMM to another is far easier than
(for example) moving a JVM based app from one app server to another.
Even across VMM technologies it's not that painful.
Yes if you connect to specific APIs which you do not control then you
may have portability issues, but that also applies to the LAN-bound
non-cloud case. I don't believe Stallman can be asserting that
lock-in effects do not exist if you deploy and integrate all your apps
locally, even if they are all GPL.
I think Stallman is worried about things like this:
http://www.theregister.co.uk/2007/11/04/4th-amendment_email_privacy/
> b. that your backup is compromised
That does not imply lock-in, it implies a lack of security. Suppose I
run my email server on my laptop and back it up to servers that I own.
One or the other is compromised (laptop or servers). In neither case
am I locked in. Now replace 'servers' with S3 in the example.
Nothing has changed.
> Point is ... privacy is applicable, no matter where you host (though the
> facets may be different) and lock-in occurs the moment you start writing
> code.
So, you are saying that Stallman's arguments apply more or less
equally well to the non-cloud case. And, thus, agreeing with me.
alexis
That's feature from IPv6 given that infrastructure at the location of
the hardware has means to enable the support. The tagging should be
nothing more then declaring the IP address in the VM.
Oscar
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "Cloud Computing" group.
> To post to this group, send email to cloud-c...@googlegroups.com
> To unsubscribe from this group, send email to
> cloud-computi...@googlegroups.com
> To post job listing, send email to jo...@cloudjobs.net (position title, employer and location in subject, description in message body) or visit http://www.cloudjobs.net
> To submit your resume for cloud computing job bank, send it to res...@cloudjobs.net.
> For more options, visit this group at
> http://groups.google.ca/group/cloud-computing?hl=en?hl=en
> Posting guidelines:
> http://groups.google.ca/group/cloud-computing/web/frequently-asked-questions
> To collaborate in group's Wiki (http://sites.google.com/site/cloudcomputingwiki/) send request to cloudmo...@gmail.com
> This group posts are licensed under a Creative Commons Attribution-Share Alike 3.0 United States License http://creativecommons.org/licenses/by-sa/3.0/us/
> -~----------~----~----~----~------~----~------~--~---
I mostly agree with your points, but what do you mean by lock-in occurs
the moment you start writing code? Shouldn't that be prefixed that your
writing your own application dependent code or something alike? I can
think of several pieces of code that prevents lock-in.
Oscar
Cloud is a 'self service' (no sales guys) business model for
supporting 'elastic scale on demand' (pay for what you use, do not pay
once you stop using) for *your own applications*.
Individual Portable IPs would be a very tough concept and bring down the efficiency of the internet routing tables.
However, if you were using a block of IPs larger than a /24 (255 ips), you could get your own block from ARIN/APNIC/RIPE and do your own BGP routing.
This is already a common concept in the non-virtual internet services ecosystem. I don't think I have really seen any cloud providers talking about doing bgp so far however. This would take the complexity to a whole new level.
I think you could achieve the same level of automating portability by clever integration of dns, dhcp and virtual mac addresses.
A few years ago, I helped produce an event at a well-known tech
conference where RMS was also speaking. Our first sign of trouble with
Stallman was that he required acceptance of a FIVE PAGE TERM SHEET --
including line items about hosts taking him to local "folk dancing" --
as conditions of his appearance to speak. Things grew worse from that
point. I will never again have anything to do with the man.
I found the whole episode quite pathetic, callously uncivil, and
altogether too reminiscent of a kind of heroin-fueled narcissism
which, in comparison, could make Kim Jong-il worthy of a Nobel Peace
Prize.
Not to mention the elaborate and rather forced cult of personality
which surrounds both individuals.
Just saying.
Let's try to avoid personal attacks. Thanks.
In that case, he has a very strong techincal argument against both
Gmail and cloud computing, LOL.