Tranquil IT Forum

Hello,
I'm currently doing my final internship and I've been asked to set up WAPT.

However, I'm having some trouble with the wapt-get.ini file. I think I understand the difference between an update (updating the repository's package list)
and
an upgrade (updating packages on the workstations).
Nevertheless, I have some questions regarding modifying the ini file.

The `task_period` corresponds to the frequency at which these actions are performed (in minutes, I assume). So, if the `waptupgrade_task_period` line is not set (=0), will the system be in manual mode, or is it better to completely remove the line and only configure `waptupdate_task_period`?

I should mention that we want to be able to manually control when we decide to launch software updates, and without the target computers requesting updates from the server, in order to avoid network congestion.

Thank you in advance.

Mika wrote:Hello,
I am currently doing my final internship and I have been asked to set up Wapt.

Excellent internship project, you should congratulate your internship supervisor ^^

Mika wrote:Hello,

I'm having some issues with the wapt-get.ini file. I think I understand the difference between an update (updating the repository's package list)
and
an upgrade (updating packages on the machines).
However, I have some questions about modifying the ini file.

The task_period corresponds to the frequency at which these actions are performed (in minutes, I assume), so if the waptupgrade_task_period line is not set (=0), will the system be in manual mode, or is it better to completely delete the line and only configure waptupdate_task_period?

As mentioned in the documentation, waptupgrade_task_period is not active by default because it would unnecessarily trigger installations in the middle of the day

On the other hand waptupdate_task_period is set to 120 minutes by default.

This allows the Wapt client to check every two hours for updates and pre-download them to c:\wapt\cache if necessary. This is also done at system startup. The installation can then be performed at shutdown using waptexit, triggered by the user (with wapttray), or by an administrator launching an upgrade from the console. The load is generally balanced quite well because the systems are not all started at the same time in the morning.

Mika wrote: I would like to clarify that we want to be able to manually control when we decide to launch software updates, and without the target computers having to ask the server, in order to avoid network congestion.

Thank you in advance.

On a LAN, there's no particular congestion; I have experience with a network of 500 machines on 100 Mbps connections with a single WAPT server. However, if you have remote sites (low-bandwidth VPN connection), it might be wise to set up synchronized remote repositories. The WAPT package would be downloaded only once by the replicated repository, and then clients would download from it.

The other solution would be to implement a bandwidth limitation for Wapt.

Simon

Thank you for your responsiveness and for allowing me to move forward on the project.