I haven't directly used Karaf in a couple years, so I can't speak to what my old team did with my old app, but we had a hell of a time upgrading between point releases of Karaf. Part of that was immaturity at the time in automating our infrastructure, but another part was simply trying to coordinate the underlying framework version across dozens of bundles got to be a hot mess. It reminded me of upgrading major Java versions somewhat but with more surprises. We also maintained a manual features list that we had to keep up to date with our Maven and then later Gradle build; that was irritating, but not as bad as it was when we first started writing the application and were keeping versions in sync across even more places. The speed of development (particularly in the ability to redeploy a single bundle at a time), however, absolutely made up for the arcane process at the time. I was hoping to eventually split up that application into smaller .kar files to allow for easier deployments of the subsystems, but I never had a chance to do that before I left, though I'm not even sure how well that would've helped compared to just dropping jars in the deploy directory for a more granular deployment.
I'm not sure how much you've used Kubernetes, but I wonder how well Karaf Boot could work in that sphere. I still believe strongly in modularity and the ecosystem around it, and if Karaf makes it easier to "migrate to the cloud" so to say (and not just in a superficial matter; modularity should help enforce boundaries that are explicitly needed in distributed systems), then that could be a killer feature. The existing work with clustering looks extremely relevant to this, though I'm not familiar with how that interacts with k8s. On Fri, 17 Aug 2018 at 23:09, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi, > > by the way, what do you mean about remote admin ? Is it something like > the Deployer feature we have in Cave ? > > By the way, I will take some days off next week, but after I will send a > proposal on the mailing list with: > > 1. Release agenda > 2. Karaf Container roadmap > 3. Karaf Vineyard > > Stay tuned ! > > Regards > JB > > On 17/08/2018 22:12, Castor wrote: > > Ohh yeah, at the beginning the mechanism was quite confusing, it still > give > > me some headaches sometimes, like a feature with no dependencies with a > > bundle importing only a servlet triggering a refresh of the whole > platform. > > > > "For the update, I don't know which karaf version you are using, but > > Karaf 4.2.x has some improvements with feature:update." > > > > We are using karaf 4.1.5 right now, we will wait for Karaf 4.2.1 to start > > some testing. > > > > > > "Feel free to create Jira corresponding > > to your ideas, and feel free to contribute. Any help is welcome !" > > > > Will do, i plan to release an open-source version of our remote admin for > > karaf which i am working on my free time, should take a couple months. > > > > Thanks! > > > > > > > > > > jbonofre wrote > >> Hi, > >> > >> Thanks for sharing your experience. > >> > >> I don't say that it's your case, but most of the time, when people > >> complains about refresh, it's because they don't know/understand the > >> underlying mechanisms. > >> Basically, I had the case with a customer that used a bunch of optional > >> import and complain of the refresh: the issue was basically a design > >> error and an mistake in the bundles. > >> > >> For the update, I don't know which karaf version you are using, but > >> Karaf 4.2.x has some improvements with feature:update. > >> > >> About spring-boot like, it's part of the karaf-boot scope. > >> > >> Anyway guys, I think you have very good ideas and it's really great you > >> share your experience/use cases. Feel free to create Jira corresponding > >> to your ideas, and feel free to contribute. Any help is welcome ! > >> > >> Thanks > >> Regards > >> JB > >> > >> On 17/08/2018 21:34, Castor wrote: > >>> I can tell a little about my experience with karaf. > >>> > >>> Here we have an ERP writen in delphi (that was written in natural > before > >>> that) which we need to "upgrade" to a cloud capable software, using the > >>> same > >>> database and mantaining the old software while we rewrite negotial > rules > >>> in > >>> java. Great part of our clients are small-medium with on-premises, so > we > >>> had > >>> to maintain a architecture easy enough for on-premises and able to use > a > >>> cloud structure with clusters and so on. > >>> > >>> So, we are using karaf for that, OSGi services lets us to build > >>> "microservices" and have a easier reuse of Negotial Rules, with common > >>> transactions and so on (icks for XA . > >>> > >>> Well, it works, but we have some headaches, we had to build or own > >>> dependency mechanism, because every single feature refreshed the hell > of > >>> karaf, we also built an remote admin to update services on-the-fly in > >>> every > >>> single customer, it's working quite nicely, we still have some trouble > >>> with > >>> failed bundles, but nothing irremediable. > >>> > >>> Two things that would help us a lot, a spring-boot like app and an > easier > >>> way to update karaf version, for the updates we had to create a updater > >>> which saves a list of negotial bundles, reinstall karaf and restores > the > >>> bundles, it works but it's quite meh. > >>> > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html > >>> > >> > >> -- > >> Jean-Baptiste Onofré > > > >> jbonofre@ > > > >> http://blog.nanthrax.net > >> Talend - http://www.talend.com > > > > > > > > > > > > -- > > Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Matt Sicker <boa...@gmail.com>
