While I wait for upgrading 2 customers from 4.8.6 to 4.9.x (hesitating not to break things) and checking the list for Louis publishing the 4.8.7 stretch packages ... ;-) - thanks, Louis!! - I once again wonder how to optimize these updates and minimize the risk of breaking things. One thought is to add a test DC to my ADS/samba-domains, running in a docker container, testing the upgrade there and throw away the container when things are done etc Does anyone do that? I know I already asked that here in september (feels as if it was way earlier): https://lists.samba.org/archive/samba/2018-September/217906.html Maybe I set up a 4.8.6 container and test the upgrading in there. Feedback welcome.
Am 27.11.18 um 21:00 schrieb Stefan G. Weichinger via samba:> While I wait for upgrading 2 customers from 4.8.6 to 4.9.x (hesitating > not to break things) and checking the list for Louis publishing the > 4.8.7 stretch packages ... ;-) - thanks, Louis!! - I once again wonder > how to optimize these updates and minimize the risk of breaking things. > > One thought is to add a test DC to my ADS/samba-domains, running in a > docker container, testing the upgrade there and throw away the container > when things are done etc > > Does anyone do that? > > I know I already asked that here in september (feels as if it was way > earlier): > > https://lists.samba.org/archive/samba/2018-September/217906.html > > Maybe I set up a 4.8.6 container and test the upgrading in there. > > Feedback welcomewhy don't you just use real virtual machines? * clone * test * throw away the old one and/or play around with all sort of snaphsot-versions? after a decade running anything in full virtualization i don't get bare-metal where the first step is not install whatever hypervisor and be it only for hot-migration to new hardware while you get proper backups and snapshots "for free"
On Tue, 2018-11-27 at 21:05 +0100, Reindl Harald via samba wrote:> Am 27.11.18 um 21:00 schrieb Stefan G. Weichinger via samba: > > While I wait for upgrading 2 customers from 4.8.6 to 4.9.x (hesitating > > not to break things) and checking the list for Louis publishing the > > 4.8.7 stretch packages ... ;-) - thanks, Louis!! - I once again wonder > > how to optimize these updates and minimize the risk of breaking things. > > > > One thought is to add a test DC to my ADS/samba-domains, running in a > > docker container, testing the upgrade there and throw away the container > > when things are done etc > > > > Does anyone do that? > > > > I know I already asked that here in september (feels as if it was way > > earlier): > > > > https://lists.samba.org/archive/samba/2018-September/217906.html > > > > Maybe I set up a 4.8.6 container and test the upgrading in there. > > > > Feedback welcome > > > why don't you just use real virtual machines? > > * clone > * testBecause if it connects to the network there will be chaos.> * throw away the old one > > and/or play around with all sort of snaphsot-versions? > > after a decade running anything in full virtualization i don't get > bare-metal where the first step is not install whatever hypervisor and > be it only for hot-migration to new hardware while you get proper > backups and snapshots "for free"Samba 4.9 can back up an existing domain and restore it with a new name to test in the lab. This is the safe way to test upgrades, which should in general be done on a join/demote basis not in-place if at all possible. Andrew Bartlett -- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Development and Support, Catalyst IT https://catalyst.net.nz/services/samba
Am 27.11.18 um 21:05 schrieb Reindl Harald via samba:> why don't you just use real virtual machines? > > * clone > * test > * throw away the old one > > and/or play around with all sort of snaphsot-versions? > > after a decade running anything in full virtualization i don't get > bare-metal where the first step is not install whatever hypervisor and > be it only for hot-migration to new hardware while you get proper > backups and snapshots "for free"Worth a thought or two as well, sure. Right now I have physical DCs in place mostly. The container variant would allow to spawn a DC now and then, test things etc ... it depends on the given environment here, I assume. thanks, Stefan (greetings from/to austria)
On 11/27/18 4:00 PM, Stefan G. Weichinger via samba wrote:> > While I wait for upgrading 2 customers from 4.8.6 to 4.9.x (hesitating > not to break things) and checking the list for Louis publishing the > 4.8.7 stretch packages ... ;-) - thanks, Louis!! - I once again wonder > how to optimize these updates and minimize the risk of breaking things. > > One thought is to add a test DC to my ADS/samba-domains, running in a > docker container, testing the upgrade there and throw away the container > when things are done etc > > Does anyone do that?With a test environment with two clients, a Windows machine (on the same host as a VM, and the host running the container is joined as a file server to the domain running on the container: 1) Shutdown the DC container 2) Backup everything on the mounted volumes of the container where the Samba data is stored (tar --acls --xattrs ...) 3) Recreate the container with the new Samba release 4) Run the tests 5) If there are failures, revert date from the backup Why not test everything on VMs as another response asked? because we run the DC on containers (mutiple independent domains on different networks) Note: On those production DCs we backup too the DC container data volumes just in case, this time with a snapshot but it is irrelevant, tar should work too. The important thing is the DC should be down when the snapshot or tar is created> > I know I already asked that here in september (feels as if it was way > earlier): > > https://lists.samba.org/archive/samba/2018-September/217906.html > > Maybe I set up a 4.8.6 container and test the upgrading in there. > > Feedback welcome. >