Page 1 of 1
Multi-site deposit on client
Published: February 6, 2017 - 1:41 PM
by sapeurorca
Hello,
We are looking for a software deployment solution to easily keep our software up to date.
Constraints:
- Numerous remote sites (300) with low bandwidth.
- None of the remote sites have a server; there are only client workstations connected via DHCP.
- All servers are located at a single site.
We would like to have a client workstation at each remote site to act as a repository. Do you think this is possible with WAPT (given that the clients are connected via DHCP)?
Thank you.
Re: Multi-site repository on client
Published: February 6, 2017 - 11:42 PM
by sfonteneau
Hello,
the best solution would be to use Waptboxes (small Linux devices); you would simply need to place one per site.
Alternatively, you could dedicate a client PC at each site to host and synchronize the Wapt packages from the central repository. However, this machine would need to be constantly powered on and have the same IP address (DHCP reservation).
We invite you to contact us to see what we can potentially offer you! ---> +33 2 40 97 57 55
Simon Fonteneau
Re: Multi-site repository on client
Published: February 7, 2017 - 8:49 AM
by sapeurorca
Hello,
we'd like to avoid buying physical devices, as it's very expensive if we have to install one at each site (over 300).
Our goal, as you mentioned, is to use a client PC that also acts as a repository; leaving it powered on and setting up a DHCP reservation wouldn't be a problem.
However, this PC is running Windows 10. To use it as a repository, is it mandatory to install the WAPTserver version, or is just the agent sufficient?
Thank you.
Re: Multi-site repository on client
Published: February 7, 2017 - 9:54 AM
by sfonteneau
The goal is to replicate the repository component (machine packages, group packages, software packages).
[https://www.wapt.fr/fr/doc/Theorique/in ... e-de-depot](https://www.wapt.fr/fr/doc/Theorique/in ... e-de-depot)
Simply install Apache, IIS, or Nginx. (It can even be installed on a Raspberry Pi.)
The inventory component (server, inventory) consumes very little bandwidth.
Clients can therefore continue to connect directly to the Wapt server.
Replication can be done with Syncthing.
We can assist you with your project! ---> +33 2 40 97 57 55
Simon Fonteneau
Re: Multi-site repository on client
Published: February 7, 2017 - 2:57 PM
by sapeurorca
Hello,
thank you very much for the information. If I have a moment, I'll try to call to get more details.
I'll try to look into Syncthing and see how to set up a repository on a client machine.
Thank you.
Re: Multi-site repository on client
Published: February 16, 2017 - 3:26 PM
by Nathanael
Hello,
I'm in a similar situation, only with fewer sites. So I have the same question as you... Have you decided how to do it?
Simon, could you tell us what hardware is recommended for a local WAPT repository?
Thank you,
Best regards,
Nathanaël
Re: Multi-site repository on client
Published: February 18, 2017 - 12:16 PM
by sfonteneau
Re: Multi-site repository on client
Published: February 21, 2017 - 4:03 PM
by Nathanael
THANKS !
Re: Multi-site repository on client
Published: October 7, 2017 - 12:50 AM
by vcardon
sapeurorca wrote: ↑Feb 7, 2017 - 2:57 PM
Hello,
Thank you very much for your information. If I have a little free time, I will try to call to get more information.
I will try to look at Syncthing and see how to set up a repository on a client machine.
Thank you
I urge you to contact us regarding your 300 sites ---> +33 2 40 97 57 55
In the meantime, we have had the opportunity to test and practice some cost-effective solutions for clients with the same requirements as you;
At TIS, we do not believe in the solution of leaving a PC on to serve other PCs on the same site; there are too many user uncertainties. This method is not considered reliable, so no effort beyond exploratory will be undertaken in this direction on our part.
Best regards.
VC