On Tue, Jun 07, 2016 at 08:14:36PM -0400, Craig Constantine wrote:
> If they seem mixed up, it's probably the fault of my too-quick writing.
>
> I don't want to run VMs on cloud services. So that leads me in the direction
> of building services (eg some web site facing a customer extranet) directly
> on cloud components.
>
> The "why build my own", instead of using some service, is simply that it's a
> requirement to have absolute admin and physical control (aka "everything must
> be inside the glass house"). However, I also need to look into hosted
> "private cloud" services; That might fly in terms of the admin/physical
> control requirement.
Got it.
The "services" run on clouds are provided by daemons, same as
you are used to everywhere else. They need to be load-balanced
in front and have HA storage in back. It is trendy for the
daemons all to have HTTP-accessible APIs, which have the
advantage of being networked and easily load-balanced, and have
the disadvantage of having to make network roundtrips for
everything.
The "cloud" is a set of machines that are managed by a system
like OpenStack, which arranges for services to come up, go down,
get billed, and so forth. The cloud management system can work
directly on real machines ("bare iron") or manage VMs or
containers. Nothing runs directly "on the cloud", that's just a
metaphor.
There is no free lunch.
-dsr-
--
https://randomstring.org/~dsr/eula.html is hereby incorporated by reference.
there is no justice, there is just us.
_______________________________________________
Discuss mailing list
Discuss@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
