You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Paul Spencer <pa...@apache.org> on 2015/04/22 15:22:37 UTC
Deploying application and patches to disconnected servers?
I have an application composed of standard features/bundles, like CXF and MyFaces, and features/bundles developed by my company. The application is deployed to many server that have no internet connection. What is the best way to distribute the application and updates?
Based on some research I have identified the following options:
- Create a custom Karaf distribution containing all features and bundles. I suspect this will result in building a complete distribution for a patch and extra effort to preserve and reapply configuration during the patching process.
- Use a standard, or slightly customized, Karaf distribution with a separate Maven repository containing all features and bundles. Patching would require adding the patched feature/module to the distributed Maven repository.
- Use a standard, or slightly customized, Karaf distribution with a Cave OBR repository. All features and bundles would need to be added to the Cave repository and distributed. Patching would require adding the patched feature/module to the distributed Cave repository.
Are there other options worth considering?
What is the advantage of using an OBR repository over a Maven repository?
Paul Spencer
Re: Deploying application and patches to disconnected servers?
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Paul,
the benefit will be it's OBR based.
If you use a Osgi Bundle Repository (OBR), when installing a bundle with an
OBR present, the resolver will try to resolve the dependencies according to
the descripton of the required capabilties. So for example the imports are
resolved via the OBR but also the require-capabilties like services etc.
This will also make sure that if a required capability is already
sufficiently satisfied with the current set of bundles, another bundle will
not be install.
regards, Achim
2015-04-23 4:11 GMT+02:00 Paul Spencer <pa...@apache.org>:
> Achim,
> At this point there is no need for a cluster implementation. The
> application is deployed in multiple standalone Karaf instances within a
> facility and there are many facilities. Assuming a repository based
> distribution model, I anticipate each instance will get features and
> bundles from one Maven/OBR repository located within the facility. Patches
> will be pushed to each repository so each instance can be patches on its
> own schedule. So what are the advantages and disadvantages of front ending
> a Maven repository with Cave?
>
> Paul Spencer
>
> > On Apr 22, 2015, at 9:47 AM, Achim Nierbeck <bc...@googlemail.com>
> wrote:
> >
> > Hi,
> >
> > you forgot to add Karaf Cellar in your list ;)
> >
> > No, most likely cellar could be another scenario for you. It's
> especially usefull for farming / distributing your bundles across the
> cluster.
> > In combination with a Maven Repo or OBR it might be very helpful for
> your scenario.
> >
> > regards, Achim
> >
> >
> > 2015-04-22 15:22 GMT+02:00 Paul Spencer <pa...@apache.org>:
> > I have an application composed of standard features/bundles, like CXF
> and MyFaces, and features/bundles developed by my company. The
> application is deployed to many server that have no internet connection.
> What is the best way to distribute the application and updates?
> >
> > Based on some research I have identified the following options:
> >
> > - Create a custom Karaf distribution containing all features and
> bundles. I suspect this will result in building a complete distribution
> for a patch and extra effort to preserve and reapply configuration during
> the patching process.
> >
> > - Use a standard, or slightly customized, Karaf distribution with a
> separate Maven repository containing all features and bundles. Patching
> would require adding the patched feature/module to the distributed Maven
> repository.
> >
> > - Use a standard, or slightly customized, Karaf distribution with a Cave
> OBR repository. All features and bundles would need to be added to the
> Cave repository and distributed. Patching would require adding the patched
> feature/module to the distributed Cave repository.
> >
> > Are there other options worth considering?
> >
> > What is the advantage of using an OBR repository over a Maven repository?
> >
> > Paul Spencer
> >
> >
> >
> > --
> >
> > Apache Member
> > Apache Karaf <http://karaf.apache.org/> Committer & PMC
> > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
> & Project Lead
> > blog <http://notizblog.nierbeck.de/>
> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
> >
> > Software Architect / Project Manager / Scrum Master
> >
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Deploying application and patches to disconnected servers?
Posted by Paul Spencer <pa...@apache.org>.
Achim,
At this point there is no need for a cluster implementation. The application is deployed in multiple standalone Karaf instances within a facility and there are many facilities. Assuming a repository based distribution model, I anticipate each instance will get features and bundles from one Maven/OBR repository located within the facility. Patches will be pushed to each repository so each instance can be patches on its own schedule. So what are the advantages and disadvantages of front ending a Maven repository with Cave?
Paul Spencer
> On Apr 22, 2015, at 9:47 AM, Achim Nierbeck <bc...@googlemail.com> wrote:
>
> Hi,
>
> you forgot to add Karaf Cellar in your list ;)
>
> No, most likely cellar could be another scenario for you. It's especially usefull for farming / distributing your bundles across the cluster.
> In combination with a Maven Repo or OBR it might be very helpful for your scenario.
>
> regards, Achim
>
>
> 2015-04-22 15:22 GMT+02:00 Paul Spencer <pa...@apache.org>:
> I have an application composed of standard features/bundles, like CXF and MyFaces, and features/bundles developed by my company. The application is deployed to many server that have no internet connection. What is the best way to distribute the application and updates?
>
> Based on some research I have identified the following options:
>
> - Create a custom Karaf distribution containing all features and bundles. I suspect this will result in building a complete distribution for a patch and extra effort to preserve and reapply configuration during the patching process.
>
> - Use a standard, or slightly customized, Karaf distribution with a separate Maven repository containing all features and bundles. Patching would require adding the patched feature/module to the distributed Maven repository.
>
> - Use a standard, or slightly customized, Karaf distribution with a Cave OBR repository. All features and bundles would need to be added to the Cave repository and distributed. Patching would require adding the patched feature/module to the distributed Cave repository.
>
> Are there other options worth considering?
>
> What is the advantage of using an OBR repository over a Maven repository?
>
> Paul Spencer
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
Re: Deploying application and patches to disconnected servers?
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
you forgot to add Karaf Cellar in your list ;)
No, most likely cellar could be another scenario for you. It's especially
usefull for farming / distributing your bundles across the cluster.
In combination with a Maven Repo or OBR it might be very helpful for your
scenario.
regards, Achim
2015-04-22 15:22 GMT+02:00 Paul Spencer <pa...@apache.org>:
> I have an application composed of standard features/bundles, like CXF and
> MyFaces, and features/bundles developed by my company. The application is
> deployed to many server that have no internet connection. What is the best
> way to distribute the application and updates?
>
> Based on some research I have identified the following options:
>
> - Create a custom Karaf distribution containing all features and bundles.
> I suspect this will result in building a complete distribution for a patch
> and extra effort to preserve and reapply configuration during the patching
> process.
>
> - Use a standard, or slightly customized, Karaf distribution with a
> separate Maven repository containing all features and bundles. Patching
> would require adding the patched feature/module to the distributed Maven
> repository.
>
> - Use a standard, or slightly customized, Karaf distribution with a Cave
> OBR repository. All features and bundles would need to be added to the
> Cave repository and distributed. Patching would require adding the patched
> feature/module to the distributed Cave repository.
>
> Are there other options worth considering?
>
> What is the advantage of using an OBR repository over a Maven repository?
>
> Paul Spencer
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master