[GeoNode-devel] From GeoNode to Rancher... and back (G. Allegri)

Wed Aug 22 23:53:11 PDT 2018

Hi Giovanni,

thanks a lot for sharing your insights! For a relaunch of a content heavy
geonode I´ve had a look at Rancher as setup as well. The two reasons
I’ ve decided against it are:

The ability to scale on different hosts is nice, but can get quite expensive
as well. (Among others we host at AWS which looks cheap only at first glance). 
So after a stress test of a standard docker setup runing on EC2 large with Jmeter
I´ve decided that this should much do it for the project needs.. So what I´m trying to
say is that one has to consider if the ablity of cloud scaling pays off compared 
to the costs.

The second reason is, if I´m not really in the need of cloud scaling, and using maybe
only one Rancher host, the GUI does not provide a „killer feature“ that would convince me
using it. To get an overview what is happening docker stats is fine for me.
If one really needs a GUI showing metrics a separate container running monit, scout, 
prometheus or some other framework can be a solid alternative. 

Last but not least. You guys did a great rework of geonode-project and it´s installation. 
Again if I´m not in the need of cloud scaling 'docker-compose up' is now much
faster than setting up Rancher and geonode by use of a catalog. 

Just my two cents. I´m looking forward hearing of other experinces.

Cheers,

Toni

-----------------------------------------------
CSGIS

-----------------------------------------------
Kolonnadenstraße 1
04109 Leipzig
-----------------------------------------------
Mobil	+49/ (0) 176 6680 3198
Tel 		+49/ (0) 341 24 04 738
Fax 		+49/ (0) 341 24 04 73
Web		http://csgis.de
-----------------------------------------------

Hinweis gemäß § 33 BDSG
Daten der Verfahrensbeteiligten werden gespeichert. Dieses Dokument ist ausschließlich für den 
Adressaten bestimmt. Der Inhalt der E-Mail ist vertraulich. Falls Sie diese E-Mail versehentlich 
erhalten haben, rufen Sie uns unter obiger Rufnummer umgehend an und löschen Sie diese Nachricht 
von Ihrem Computer. Jegliche Art von Reproduktionen, Verbreitung, Vervielfältigung, Veränderung, 
Verteilung und/oder Veröffentlichung dieser E-Mail ist verboten.

> Am 22.08.2018 um 21:00 schrieb geonode-devel-request at lists.osgeo.org:
> 
> Send geonode-devel mailing list submissions to
> 	geonode-devel at lists.osgeo.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.osgeo.org/mailman/listinfo/geonode-devel
> or, via email, send a message with subject or body 'help' to
> 	geonode-devel-request at lists.osgeo.org
> 
> You can reach the person managing the list at
> 	geonode-devel-owner at lists.osgeo.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of geonode-devel digest..."
> 
> 
> Today's Topics:
> 
>   1. From GeoNode to Rancher... and back (G. Allegri)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 22 Aug 2018 10:58:18 +0200
> From: "G. Allegri" <giovanni.allegri at geo-solutions.it>
> To: geonode-devel <geonode-devel at lists.osgeo.org>
> Subject: [GeoNode-devel] From GeoNode to Rancher... and back
> Message-ID:
> 	<CAB4g1=wjK=mK1KEkzEGw7CXL07jikzRqQoQGHKWm4XK8PgfPEw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hello everyone,
> 
> since some months we (GeoSolutions) have spent an amount of time analysing,
> developing and experimenting with GeoNode, Docker and Rancher (1.6). The
> purpose, that we know also others from the community share, was to test
> GeoNode within a "cloud oriented" context, supporting services
> orchestration for the GeoNode stack, aimed to simplify deployment,
> horizontal scaling, updating, etc.
> 
> Rancher seemed the right way to go, because it supports Docker and Docker
> compose, has lots of batteries included and it provides a straightforward
> management through its nice web console.
> After some months with it Rancher 2 was about to be released. As you may
> know it's deeply different from the 1.x. Although a (not complete) layer of
> compatibility is provided, reality is that their "Cattle" orchestrator has
> been substituted for Kubernetes, which has become an industry standard and,
> probably, the most widespread solution for cloud services orchestration.
> 
> Kubernetes seems a bit oversized for our purposes and for the typical
> deployment scenarios for GeoNode. It requires a significative investment of
> resources to learn it, set it up and manage / mantain it. Rancher 2
> simplifies some aspects, but it won't preserve you from knowing and
> tweeking the underlying engine and services (networking, schedulers, etc.).
> On the opposite side, simpler approaches often lead to tailored made
> solutions, integrating different pieces together (for management,
> networking, service discovery, config, scheduling, health checks, load
> balancing, etc.). It can be easier at the beginning but it risks to become
> a nightmare and even more expensive then investing on a solution like
> Kubernetes.
> 
> Long story short, we would like to confront with those of you that share
> similar goals, to know your opinions and experience on that.
> It would be great if a shared approach could be found. Sharing to grow
> everyone, together ;)
> 
> All the best,
> Giovanni
> 
> 
> -- 
> Giovanni Allegri
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> <https://maps.google.com/?q=Via+di+Montramito+3/A%0D+55054+%C2%A0Massarosa&entry=gmail&source=g>
> 55054  Massarosa
> <https://maps.google.com/?q=Via+di+Montramito+3/A%0D+55054+%C2%A0Massarosa&entry=gmail&source=g>
> (LU)
> Italy
> phone: +39 0584 962313 <+39%200584%20962313>
> fax:     +39 0584 1660272 <+39%200584%20166%200272>
> 
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
> 
> -------------------------------------------------------
> 
> 
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
> 
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20180822/c28e93da/attachment-0001.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-devel
> 
> 
> ------------------------------
> 
> End of geonode-devel Digest, Vol 43, Issue 16
> *********************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20180823/a281563f/attachment.html>