Hello,
I have a question regarding the secondary repository synchronization feature.
How can we limit storage usage at each of our industrial sites while still being able to select/assign packages from the private repository to different secondary repositories?
Currently, I don't see a way to synchronize only a portion of the private repository for each site.
Does a secondary repository selection system exist for WAPT packages/OS deployments, etc.?
Is this feature under development? If so, do you have any idea of the target version for its integration?
Thank you for your answers.
Best regards.
[RESOLVED] Secondary repository synchronization rules
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Théo,
the differentiated secondary repository feature (which only synchronizes what the site needs) is currently under development.
Improving the management of remote sites is one of our current priorities. For small sites without secondary repositories, we are integrating the "peercache" feature into the WAPT agent, which allows two machines to share the packages they have downloaded. Peercache is in alpha version internally, and we hope to have it in the next WAPT version, 2.6 or 2.7.
The "proxycache" feature (differentiated repository) will be the next step.
Best regards,
Denis
the differentiated secondary repository feature (which only synchronizes what the site needs) is currently under development.
Improving the management of remote sites is one of our current priorities. For small sites without secondary repositories, we are integrating the "peercache" feature into the WAPT agent, which allows two machines to share the packages they have downloaded. Peercache is in alpha version internally, and we hope to have it in the next WAPT version, 2.6 or 2.7.
The "proxycache" feature (differentiated repository) will be the next step.
Best regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
