I propose we do the same for the integration project. Any existing content can be moved to whatever instance you feel most at "home", or e.g. in /home on the wmflabs bastion (though beware there will be no backups).
While home directories are not the only use of NFS in integration, it is quite impactful that Jenkins is unable to finish or start new builds during NFS slowness/outage. See also https://phabricator.wikimedia.org/T90610#1344487 <https://phabricator.wikimedia.org/T90610#1344487>. — Krinkle > On 11 Jun 2015, at 22:48, Tyler Cipriani <[email protected]> wrote: > > == tl;dr == > > Next Friday (2015/06/19) NFS home directories for the deployment-prep > project will be replaced with regular old non-NFS home directories. > > == Long version == > > NFS home directories are both a convenience and a pain-point for the > deployment-prep project. > > The convenience of having shared dotfiles across instances has to be > weighed against the giant inconvenience of not being able to login to > any boxen in the project when NFS is having issues. > > A reliably working project out-weighs small conveniences, so we're > ripping out NFS. > > Thanks! > Tyler > > _______________________________________________ > QA mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/qa
_______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
