On Tue, 1 Oct 2019 at 04:35, Miroslav Suchý <msuchy@xxxxxxxxxx> wrote: > > Dne 01. 10. 19 v 9:53 Peter Robinson napsal(a): > > Warrantee generally doesn't cover moves but the DC shipping company > > should have insurance to cover breakages they cause as mistakes > > happen. > > It is hard to claim something if the package does not have any visible damage. And I guess you will not put > accellerometer to every package. > It does not need to be fault of the shipping company. E.g. it happens very often for rotating disk, that it can work for > years. It operate fine as long as it is rotating, but the bearing become dry and once you stop them, the motor does not > have enough power to start the rotation again. > Or - just recently - I had hands on computer which has broken the thing which hold cooler on CPU. Once I get the > computer off the rack and start moving with it, cooler started to move freely in the case. Previously this was not > detected as the cooler just sit on CPU (without any press) and the CPU did not overheated because of lot of fans in case > and cool air in data center. > > So this are the cases which may - and in this scale will - happen. > So parts of this are going to be outside of anything our team can deal with. The packing of the equipment, the shipping, the insurance, the dates in transit, etc can be influenced by us asking (which we have) but in the end will be owned by a different organization in Red Hat. Because of that, I would prefer if we don't spend a lot of time coming up with all the scenarios which could cause problems because there is 0 we can do about it. What we can do is work out what resources are needed for a minimal viable fedora for 2 weeks. What services we can turn off for those 2 weeks or go to a read-only nature in some form. Then focus on what services we could place elsewhere and how we could do that. > -- > Miroslav Suchy, RHCA > Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
