Re: [wpkg-users] Remote site repositories
Mandi! Rainer Meier In chel di` si favelave... If you are fine with hard-wiring a client-server association, then I've remember, some past thread, that probably are well suited for the wiki... We have just discussed that probably the best way to lock a client to a ''server'' is to use machine auth, but that works only for WPKGClient (AFAIK) and with a ''pure'' MS AD, does not work in a Samba domain. If network 192.168.1.0/24 then SOFTWARE=\\192.168.1.x\wpkg\software If network 192.168.2.0/24 then SOFTWARE=\\192.168.2.x\\wpkg\software I'm a bit curious. How do you check network address with cmd? I've googled around a bit, but... -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Remote site repositories
Hi Marco, On 15.05.2012 09:45, Marco Gaiarin wrote: If network 192.168.1.0/24 then SOFTWARE=\\192.168.1.x\wpkg\software If network 192.168.2.0/24 then SOFTWARE=\\192.168.2.x\\wpkg\software I'm a bit curious. How do you check network address with cmd? I've googled around a bit, but... Using recent WPKG version you don't have to match it via cmd.exe (although you could potentially using ipconfig | findstr...). But you could also define conditional variables in profiles. profiles profile id=site1 variable name=SOFTWARE value=\\server1\wpkg\software condition check type=host condition=ipaddress value=^192\.\168\.1 / /condition /variable variable name=SOFTWARE value=\\server2\wpkg\software condition check type=host condition=ipaddress value=^192\.\168\.2 / /condition /variable ... /profile /profiles NOTE: It's entirely untested, I have just put this XML sniplet together in my mind... As you see the purpose is that the SOFTWARE variable is defined on a profile by WPKG. The variable is conditional and depends on the value of the IP address. If the IP address does not match, then the whole variable statement is ignored. Therefore only one of the SOFTWARE variables will be assigned. You can also use regular expressions to match different ranges. If you're going to use this, then please report if it works for you as I did not test it myself. More details about extended host attribute matching for IP addresses: http://wpkg.org/Extended_host_attribute_matching#ipaddresses br, Rainer - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Remote site repositories
Mandi! Donny Brooks In chel di` si favelave... We are currently running our wpkg setup with just one central repository or software store. However we have samba home servers for all of our individual sections, some of which are remote offices. These remote offices internet connection back to us is via a T1 and can get backlogged easily. I am looking into a way to enable the users at these locations to be able to pull packages from a share on their local server rather than pull across the T1 ad be figthing with all of our other users also. I still want to keep the configs and base wpkg centralized so as to make administration easier. I could use rsync and cron to keep the remote packages up to date also. My issue is how to implement this? Would I simply change the individual people's profile.xml SOFTWARE variable to point to the share on their local server? Thanks in advance for an input. I use this setup. I manage 10-15 WPKG ''server'', all recipe (packages) base are kept in sync using csync2, while profile and hosts setup are local. Every installation have a different client config file (i use wpkg client, so settings.xml) that point to the right software repository, that i keep in sync with unison. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Remote site repositories
On Monday, May 14, 2012 10:32 AM CDT, Marco Gaiarin g...@sv.lnf.it wrote: Mandi! Donny Brooks In chel di` si favelave... We are currently running our wpkg setup with just one central repository or software store. However we have samba home servers for all of our individual sections, some of which are remote offices. These remote offices internet connection back to us is via a T1 and can get backlogged easily. I am looking into a way to enable the users at these locations to be able to pull packages from a share on their local server rather than pull across the T1 ad be figthing with all of our other users also. I still want to keep the configs and base wpkg centralized so as to make administration easier. I could use rsync and cron to keep the remote packages up to date also. My issue is how to implement this? Would I simply change the individual people's profile.xml SOFTWARE variable to point to the share on their local server? Thanks in advance for an input. I use this setup. I manage 10-15 WPKG ''server'', all recipe (packages) base are kept in sync using csync2, while profile and hosts setup are local. Every installation have a different client config file (i use wpkg client, so settings.xml) that point to the right software repository, that i keep in sync with unison. -- dott. Marco GaiarinGNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.ittel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users Thanks for that. So if I read correctly you actually have separate servers for each location? Meaning you have each locations wpkg client software pointing to their local server rather than a centralized one? Then you just make changes to the central settings.xml and it propogates to the other servers? -- Donny B. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Remote site repositories
Mandi! Donny Brooks In chel di` si favelave... Thanks for that. So if I read correctly you actually have separate servers for each location? Meaning you have each locations wpkg client software pointing to their local server rather than a centralized one? Then you just make changes to the central settings.xml and it propogates to the other servers? Really, i've a centralized recipe (package/*.xml) database, while i have local hosts/profile management to handle some local differences. So i keep in sync package/*.xml and %SOFTWARE%, and handle the rest locally. [but it is my setup, every ''level'' of local/sync setup are possible] -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Remote site repositories
On Monday, May 14, 2012 11:06 AM CDT, Marco Gaiarin g...@sv.lnf.it wrote: Mandi! Donny Brooks In chel di` si favelave... Thanks for that. So if I read correctly you actually have separate servers for each location? Meaning you have each locations wpkg client software pointing to their local server rather than a centralized one? Then you just make changes to the central settings.xml and it propogates to the other servers? Really, i've a centralized recipe (package/*.xml) database, while i have local hosts/profile management to handle some local differences. So i keep in sync package/*.xml and %SOFTWARE%, and handle the rest locally. [but it is my setup, every ''level'' of local/sync setup are possible] -- dott. Marco GaiarinGNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.ittel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users I understand. So what I was thinking of doing with the clients still going back to the centralized wpkg server for configs but pulling software from local servers should work if I read correctly. I just wanted to make sure I wouldn't mess anything completely up before I started testing a small group. Thanks again. -- Donny B. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Remote site repositories
Hi Donny, On 14.05.2012 18:14, Donny Brooks wrote: I understand. So what I was thinking of doing with the clients still going back to the centralized wpkg server for configs but pulling software from local servers should work if I read correctly. I just wanted to make sure I wouldn't mess anything completely up before I started testing a small group. Thanks again. Yes this is supposed to work. But there are other possible solutions as well. You could also set up a local DNS server (or use hosts resolution or whatever you prefer to redirect users to the right local WPKG Server. Especially nowadays many clients are portable/mobile and often carried from one location to another. When a client is carried from location A to location B it would still access servers from location A (this time remotely). So if you can (local DNS servers available) I would recommend setting up a hostname dedicated for WPKG like wpkg.domain.tld and then configure all clients the same way. So if a client on location A connects to \\wpkg.domain.tld\wpkg-share then it connects to the local server in location A and if the client is temporary moved to location B then it uses the local WPKG server on location B without re-configuration. Of course this only works if you can either have a server with the same IP in both locations or with the same hostname resolved differently in different locations. If you are fine with hard-wiring a client-server association, then you might also consider defining the SOFWARE variable on profile level. Grouping all hosts of one location into a profile and defining SOFTWARE at profile level. This way you can even change the hostname any time without having to roll out new WPKG configuration to the clients. Although even in this method roaming clients would not automatically connect to the corresponding local server automatically but always try to connect to the WPKG server which is hard-wired in profile. Well, thinking about more possibilities there might be an option to define different SOFTWARE variable values depending on IP ranges or other host properties using conditional variables. A mapping like If network 192.168.1.0/24 then SOFTWARE=\\192.168.1.x\wpkg\software If network 192.168.2.0/24 then SOFTWARE=\\192.168.2.x\\wpkg\software This way if a host uses DHCP and is roaming between to IP networks it would always connect to the local server. In any case I would recommend the DNS resolver solution outlined above. br, Rainer - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Remote site repositories
On Monday, May 14, 2012 12:05 PM CDT, Rainer Meier r.me...@wpkg.org wrote: Hi Donny, On 14.05.2012 18:14, Donny Brooks wrote: I understand. So what I was thinking of doing with the clients still going back to the centralized wpkg server for configs but pulling software from local servers should work if I read correctly. I just wanted to make sure I wouldn't mess anything completely up before I started testing a small group. Thanks again. Yes this is supposed to work. But there are other possible solutions as well. You could also set up a local DNS server (or use hosts resolution or whatever you prefer to redirect users to the right local WPKG Server. Especially nowadays many clients are portable/mobile and often carried from one location to another. When a client is carried from location A to location B it would still access servers from location A (this time remotely). So if you can (local DNS servers available) I would recommend setting up a hostname dedicated for WPKG like wpkg.domain.tld and then configure all clients the same way. So if a client on location A connects to \\wpkg.domain.tld\wpkg-share then it connects to the local server in location A and if the client is temporary moved to location B then it uses the local WPKG server on location B without re-configuration. Of course this only works if you can either have a server with the same IP in both locations or with the same hostname resolved differently in different locations. If you are fine with hard-wiring a client-server association, then you might also consider defining the SOFWARE variable on profile level. Grouping all hosts of one location into a profile and defining SOFTWARE at profile level. This way you can even change the hostname any time without having to roll out new WPKG configuration to the clients. Although even in this method roaming clients would not automatically connect to the corresponding local server automatically but always try to connect to the WPKG server which is hard-wired in profile. Well, thinking about more possibilities there might be an option to define different SOFTWARE variable values depending on IP ranges or other host properties using conditional variables. A mapping like If network 192.168.1.0/24 then SOFTWARE=\\192.168.1.x\wpkg\software If network 192.168.2.0/24 then SOFTWARE=\\192.168.2.x\\wpkg\software This way if a host uses DHCP and is roaming between to IP networks it would always connect to the local server. In any case I would recommend the DNS resolver solution outlined above. br, Rainer Thanks for the detailed explination Rainer. With our setup I think that the best way to do this would be your last sugestion about the IF network deal. This is because each location and/or division has their own /24 network. We do not have any machines that traverse to other networks so the migratory nature is not an issue. Thanks again for the information. -- Donny B. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
