[GeoNode-devel] From GeoNode to Rancher... and back
xbartolone at gmail.com
Thu Aug 23 06:38:03 PDT 2018
thanks for starting the discussion and give us some useful clues on the
Certainly Kubernetes is gone to be a standard for orchestrating containers
but I agree with you it's kind of beast to learn and understand well and
probably a bit overwhelming for our purpose around the GeoNode stack even
by the fact that we are not scaling GeoServer yet.
Despite these considerations are true and have a worth I have the
impression that at some point we will be forced to challenge with the
beast, maybe the demarcation line could be the version 3.0. In that sense
we might keep the migration to Rancher 2.0 or in general to have a
kubernetes-ready deployment for GeoNode 3.0. This would allow to start with
a minimal stack and ease the use of kubernetes infrastructure while
learning it step by step.
For GeoNode 2.x I would stay with Rancher 1.6 when the challenge should be
big while relying to the simpler use case with docker-compose if the
scenario doesn't require a management infrastructure.
Don't know if there could be any intermediate solution which would make the
docker-compose deployment more solid. I'm all ears if others have some
advise on such topic.
Il giorno mer 22 ago 2018 alle ore 10:58 G. Allegri <
giovanni.allegri at geo-solutions.it> ha scritto:
> 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
> 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 Allegri
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> 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.
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-devel