Eclipse Community Forums: Oomph » p2 bundle pools and caching

Home » Eclipse Projects » Oomph » p2 bundle pools and caching(Eclipse oxygen documentation)

p2 bundle pools and caching [message #1780619]

Wed, 24 January 2018 16:01

Eclipse User

If I look at this documentation page it states that "Oomph provides a technology layer on top of p2 to improve the behavior and performance of caching".

Is there some description of this layer
How does it work?
Can it be configured?

I would like to maintain for the organization a shared set of bundle pools on a network share but when user install products/projects using my supplied catalog and that network share bundle pool, I would like the bundles they require to be installed locally on their desktop for speed and for reliability when the network share is unavailable.

Would this technology help me?

Re: p2 bundle pools and caching [message #1780636 is a reply to message #1780619]

Thu, 25 January 2018 02:08

Eclipse User

No, as usual, the documentation is sparse. There's some general documentation about p2's concepts in this regard here:
https://wiki.eclipse.org/Equinox/p2/Getting_Started
The general idea is that the bundle pool is a shared global p2 org.eclipse.equinox.p2.repository.artifact.IArtifactRepository repository that will be used to resolve artifacts and will cache those artifacts when they are downloaded when you install anything into your IDE or resolve a target platform using Oomph's Targlets. The installer by default will create installations that use a shared bundle pool and the user can configure where that is using the menu in simple mode or the little icon control on the first page in advanced mode next to the "Bundle Pool:" dropdown.

But what you describe as your requirements/desires sounds different from this concept. I think you want to create a mirror of some other update sites:
https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_mirror.html
You can use p2's technology to create update sites that contain things composed from other update sites. Such an update site is both an org.eclipse.equinox.p2.repository.metadata.IMetadataRepository and a IArtifactRepository . You could maintain one or more such update sites on your network and you can reference them by file:/ in your setups. It would work in just the normal way, finding the IUs that need to be installed from the content metadata and then downloading (in this case copying from the network drive) the artifacts from the repo to the user's shared bundle pool.

Re: p2 bundle pools and caching [message #1780681 is a reply to message #1780636]

Thu, 25 January 2018 11:49

Eclipse User

Ed, thanks for the reply that is very useful.

As an additional question, can the location for the p2 shared bundle pool with cached artifacts copied to the users desktop from a network share and then used by eclipse installer? The advantage is that there is no need for the artifact mirroring and there is not need to alter the setup file with the new file URI location of the artifact mirrors.

Are there reasons this would not be workable (assuming I can maintain this bundle pool using a tool like robocopy on windows)?

Re: p2 bundle pools and caching [message #1780710 is a reply to message #1780681]

Fri, 26 January 2018 03:46

Eclipse User

I'm not sure how this would work. The point is that once the artifacts are in the pool, they will not need to be copied from anywhere else ever again, so I don't see a big advantage of trying to put something in place ahead of time. After all, if you're going to specify product setups that use a local p2 update site (mirrored to contain what you need internally), and that update site URL is a file: URL for a network file system, all the artifacts needed by any specific user will be copied by direct file transfer across the file system once and only once. Or is your plan to point at external http URLs for the update sites?

Re: p2 bundle pools and caching [message #1780771 is a reply to message #1780710]

Fri, 26 January 2018 14:13

Eclipse User

The plan would be to leave it pointing at the external http update site but have them retrieved from the .p2/pool that would be copied to the users desktop. We do not want the .p2/pool to be on a network share as it would make running eclipse slow and prone to network share outages.

Previous Topic:	Update Resource for Checkstyle rule changes
Next Topic:	EGit update site broken?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 15 03:19:18 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter