I generally use a more practical set of definitions.  So many definitions of cloud are religious bullshit and often self serving.

I will share my dictionary, and maybe you can see the practicality in my definitions.

Server (hardware) a single machine with a single OS -- this machine has a single OS, and does not share resources.  You probably need to have puppet,  chef, salt, or ansible to keep this machine current if you are wise.

Server (Software) -- software that provides a single service.  Examples are a web server, mail server, database server, etc.  This must be hosted on some type of hardware.

VM Server -- a machine that hosts Virtual machines.

Virtual Machine -- a simulation of a hardware server that is carved out of a larger virtual server.  Like a hardware server, it will have it's own OS, whi which needs to be managed.

Container Manager -- a software service that allows the running of multiple containers within a hardware server or virtual machine.

Container -- much like a virtual machine, but usually focused on a single software service.  Containers are immutable.  Maintenance of a container means replace with a newer version, never patch.

Orchestrator -- a set of services such as kubernetes,  OpenStack or cloud foundry that manages a cluster of servers running container manager as a single unit.

Cloud -- The model of deployment where machines are deployed via Orchestrator, never to a machine.  This has a serious set of ramifications from the fact that I never know where a software service will be deployed, as it can be moved without my knowledge in order to maintain stable state.

So... in my definitions, cloud can very much be on my own hardware.  Take a set of machines, install CoreOS, Install Kubernetes.   All software are deployed to the cluster/cloud... a private hosted cloud, but a cloud none the less.  I have the same issues as an AWS deployment.  So, a cloud may very well be in my control.  Thus my definitions are the way they are.

I hope that someone will use my unusual definitions to get a cleaner understanding of modern network deployments.

Kevin

Sent from BlueMail
On Apr 16, 2019, at 11:30 PM, Stephen Partington <cryptworks@gmail.com> wrote:
The difference between cluster and cloud is who's problem the hardware maintenance is.

On Tue, Apr 16, 2019 at 8:56 PM Kevin Fries <kevin@fries-biro.com> wrote:
A cluster and a cloud are semantic difference

Kevin Fries

Sent from BlueMail
On Apr 16, 2019, at 9:40 PM, Harold Hartley <wheelie207@ownmail.net> wrote:
It says openstack used to build cloud. I don’t want a cloud.

On Tue, Apr 16, 2019, at 20:38, Stephen Partington wrote:

On Tue, Apr 16, 2019 at 8:22 PM Harold Hartley <wheelie207@ownmail.net> wrote:
> __
> I’ve heard of Beowulf clusters but not sure I’ve heard or read about open stack. Who makes open stack.

> On Tue, Apr 16, 2019, at 20:19, Stephen Partington wrote:
>> this depends on what you want it to be doing. you can do something with OpenStack and that technically is a cluster. or you could get old school and look into beowolf clusters.
>> 
>> On Tue, Apr 16, 2019 at 7:42 PM Harold Hartley <wheelie207@ownmail.net> wrote:
>> > __
>> > I’m looking at building a cluster and I know there are different types. I haven’t fully decided on what I would be using it for.
>> > Well, I have 4 computers about 3 or 4 years old and all have i5 processing with 8 gigs ram in each. I am not sure what size hard drives I want in them. I am looking at doing animations making my own small video movie like and then post on my blog. Even thought of other uses as well.
>> > Would anyone have an idea what type of cluster I should go with. Thanks
>> > 
>> > --
>> > Harold Hartley
>> > 17632 N. 5th place
>> > Phoenix, AZ 85022
>> > 
>> > 
>> > ---------------------------------------------------
>> > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>> > To subscribe, unsubscribe, or to change your mail settings:
>> 
>> 
>> -- 
>> A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button.
>> 
>> Stephen
>> 
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:

> --
>  Harold Hartley
>  17632 N. 5th place
>  Phoenix, AZ 85022

> ---------------------------------------------------
>  PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>  To subscribe, unsubscribe, or to change your mail settings:


-- 
A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button.

Stephen

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:

--
  Harold Hartley
  17632 N. 5th place
  Phoenix, AZ 85022




PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss


--
A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button.

Stephen



PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss