Yes, you can mix the approaches together. For instance, you can
package in docker image: karaf runtime + cellar + your apps and then
you mix Kubernetes with Cellar. It's the presentation I did while ago
at ApacheCon.

Regards
JB

On Tue, Oct 4, 2022 at 7:12 AM Ephemeris Lappis
<[email protected]> wrote:
>
> Hello.
>
> Thanks for your explanations.
>
> I understand that your 3rd choice is the only one to get multiple active
> and synchronized instances. But can't I run them as PODs inside a
> Kubernetes namespace, using deployments of an image based on
> Karaf+Cellar, and then using the Jolokia API, for example, to deploy and
> update my applications as  features, targeting any one of the scaled
> instances, and let Cellar synchronizing the other instances ?
>
> We already use Jolokia this way via Ansible playbooks to deploy
> applications, as profiles instead of features, on Fuse clusters...
>
> Thanks again.
>
> Regards.
>
> Ephemeris Lappis
>
> Le 03/10/2022 à 18:36, Jean-Baptiste Onofré a écrit :
> > Hi,
> >
> > In order:
> >
> > 1. Karaf HA Lock: you have one active, other instances are passive
> > 2. Kubernetes: you can orchestrate start/stop of the Karaf docker
> > image, but Kubernetes doesn't sync Karaf instances state (like config,
> > feature installed, etc)
> > 3. Cellar: sync Karaf instances together (you install one feature on
> > one Karaf instance, the feature will be installed on other Karaf
> > instances in the cluster)
> >
> > Regards
> > JB
> >
> > On Mon, Oct 3, 2022 at 5:44 PM Ephemeris Lappis
> > <[email protected]> wrote:
> >> Hello.
> >>
> >> I've just looked at the presentation of Cellar. If I understand it
> >> well, this presentation says that Cellar's main goal is for "big
> >> clusters", allowing automatic synchronization between Karaf instances.
> >> It seems to be really nice in the presentation :) !
> >>
> >> On the other hand, the basic lock mechanism only provides an
> >> active/passive solution.
> >>
> >> What should I prefer if my need is to provide both failover and load
> >> balancing over a limited number of active instances, and not a "big
> >> cluster". Today we use 6 Fuse Karaf instances distributed on 3 VM. Is
> >> Cellar the right way, or did I miss something in the presentation ?
> >>
> >> Another thing : for other kinds of applications my customer manages
> >> several Kubernetes clusters. So I suppose that if a containerized
> >> solution is preferred, it should be running on Kubernetes, since all
> >> the existing DevOps tooling is already based on it.
> >>
> >> The presentation focuses on Mesos/Marathon but also says that
> >> Kubernetes is also an alternative solution. Right ? In this case, what
> >> is the preferred way to package and deploy Karaf : just create a
> >> custom Karaf+Cellar image (the same way the presentation shows), and
> >> then create a Kubernetes deployment with the needed sizing and scaled
> >> replicas ?
> >>
> >> Some examples perhaps ?
> >>
> >> Thanks in advance for your help.
> >>
> >> Regards.
>
> --
> Cet e-mail a été vérifié par le logiciel antivirus d'Avast.
> www.avast.com

Reply via email to