X-Git-Url: https://scripts.mit.edu/gitweb/wizard.git/blobdiff_plain/be35f8ddac730fb1100d7cd2b9561e2e3fcc4359..4d911a9cb1eccf1520a53efc3499cdd3a63b2fbc:/TODO diff --git a/TODO b/TODO index 53e33c4..5457c38 100644 --- a/TODO +++ b/TODO @@ -2,54 +2,72 @@ The Git Autoinstaller TODO NOW: -- Make sure massmigrate cleanly ignores already migrated - installs -- Push su code to migrate, not mass-migrate (only do it - as root, this serves as a safe guard) -- Rename massmigrate to mass-migrate -- Move migration code into Wizard, since we already deal - with installation there anyway (this TODO has been updated - accordingly) - -- Make parallel-find.pl use `sudo -u username git describe --tags` - to determine version -- Remove .scripts/version generation in install script -- Make the installer use 'wizard install' - -- Better error message if daemon/scripts-security-upd - is not on scripts-security-upd list - -- Fix retarded logging mechanism - - This is interesting because the non-retarded way would be - to have each subprocess send data through stdout, but - this runs the risk of filling up the tubes. Maybe just - create a log directory and give each process different - files. -- Remove log functionality; we don't care about it besides - for parsing old style installs - -- The great initial deploy: - - Turn on mediawiki new autoinstaller - - Migrate all mediawiki installs +- Keep my sanity when upgrading 1000 installs + - Distinguish between errors(?) + - Custom merge algo: absolute php.ini symlinks to relative symlinks (this + does not seem to have been a problem in practice) + - Custom merge algo: check if it's got extra \r's in the file, + and dos2unix it if it does, before performing the merge + - `vos exa` in order to check what a person's quota is. We can + figure out roughly how big the upgrade is going to be by + doing a size comparison of the tars: `git pull` MUST NOT + fail, otherwise things are left conflicted, and not easy to fix. + - Prune -7 call errors and automatically reprocess them (with a + strike out counter of 3)--this requires better error parsing + - Report stats if I C-C the process + +- Distinguish from logging and reporting (so we can easily send mail + to users) + - Figure out a way of collecting blacklist data from .scripts/blacklisted + and aggregate it together + - Failed migrations should be wired to have wizard commands in them + automatically log to the relevant file. In addition, the seen file + should get updated when one of them gets fixed. + - Failed migration should report how many unmerged files there are + (so we can auto-punt if it's over a threshold) + +- Let users use Wizard when ssh'ed into Scripts + - Make single user mass-migrate work when not logged in as root + +- Make the rest of the world use Wizard + - Make parallel-find.pl use `sudo -u username git describe --tags` + to determine version. Make parallel-find.pl have this have greater + precedence. This also means, however, that we get + full mediawiki-1.2.3-2-abcdef names (Have patch, pending testing and commit) + - Make deployed installer use 'wizard install' /or/ do a migration + after doing a normal install (the latter makes it easier + for mass-rollbacks). + +- Pre-emptively check if daemon/scripts-security-upd + is not on scripts-security-upd list (/mit/moira/bin/blanche) - Redo Wordpress conversion, with an eye for automating everything possible (such as downloading the tarball and unpacking) -- Summary script should be more machine friendly, and should not - output summary charts when I increase specificity - -Some other stuff to do in your copious free time: -- Summary script should do something intelligent when distinguishing - between old-style and new-style installs -- Check how many autoinstalls are missing w bits for - daemon.scripts (this would need pyafs) -- Make scripts AFS patch advertise its existence so we can check for it. - (This might be otherwise possible using `fs sysname`) -- Make 'wizard summary' generate nice pretty graphs of installs by date - (more histograms, will need to check actual .scripts-version files.) -- It should be able to handle installs like Django where there's a component - that gets installed in web_scripts and another directory that gets installed - in Scripts. +- Pay back code debt + - Genericize callAsUser and drop_priviledges in shell + - Summary script should be more machine friendly, and should not + output summary charts when I increase specificity + - Summary script should do something intelligent when distinguishing + between old-style and new-style installs + - Report code in wizard/command/__init__.py is ugly as sin + +- Other stuff + - Don't use the scripts heuristics unless we're on scripts with the + AFS patch. Check with `fs sysname` + - Make 'wizard summary' generate nice pretty graphs of installs by date + (more histograms, will need to check actual .scripts-version files.) + - It should be able to handle installs like Django where there's a component + that gets installed in web_scripts and another directory that gets installed + in Scripts. + - ACLs is a starting point for sending mail to users, but it has + several failure modes: + - Old maintainers who don't care who are still on the ACL + - Private AFS groups that aren't mailing lists and that we + can't get to + A question is whether or not sending mail actually helps us: + many users will probably have to come back to us for help; many + other users won't care. PULLING OUT CONFIGURATION FILES IN AN AUTOMATED MANNER @@ -181,6 +199,9 @@ A 6. Check for empty directories and add stub files as necessary. /- wizard prepare-new -- + Currently not used for anything besides parallel-find.pl, but + we reserve the right to place files in here in the future. + A mkdir .scripts A echo "Deny from all" > .scripts/.htaccess @@ -260,16 +281,8 @@ A 15. Run `wizard mass-upgrade appname`, which applies the update to all workin - The actual application's files, as from the official tarball - - A .scripts directory, which contains the following information: - - * .scripts/.htaccess to prevent this directory from being accessed - from the web. - - * .scripts/old-version (optional) the old value of .scripts-version, - basically used for reverting an install to pre-migrated state. - - * .scripts/lock (generated) which locks the autoinstall during an upgrade - - * .scripts/version (deprecated) + - A .scripts directory, with the intent of holding Scripts specific files + if they become necessary. + * .scripts/lock (generated) which locks an autoinstall during upgrade