5 - Keep my sanity when upgrading 1000 installs
6 - Replace gaierror with a more descriptive name (this is a DNS error)
8 - Make the rest of the world use Wizard
9 - Make parallel-find.pl use `sudo -u username git describe --tags`
10 to determine version. Make parallel-find.pl have this have greater
11 precedence. This also means, however, that we get
12 full mediawiki-1.2.3-2-abcdef names (Have patch, pending testing and commit)
13 - Make deployed installer use 'wizard install' /or/ do a migration
14 after doing a normal install (the latter makes it easier
17 - Pre-emptively check if daemon/scripts-security-upd
18 is not on scripts-security-upd list (/mit/moira/bin/blanche)
20 - Redo Wordpress conversion, with an eye for automating everything
21 possible (such as downloading the tarball and unpacking)
23 - Web application for installing autoinstalls has a hard problem
24 with credentials (as well as installations that are not conducted
25 on an Athena machine.) Possible solutions include asking the user
26 to SSH into an athena machine and run a bunch of commands, or writing
27 a Java applet (possibly in Clojure or Scala) which gets filesystem
28 permissions and then performs the operations.
31 - Genericize callAsUser and drop_priviledges in shell
32 - Summary script should be more machine friendly, and should not
33 output summary charts when I increase specificity
34 - Summary script should do something intelligent when distinguishing
35 between old-style and new-style installs
36 - Report code in wizard/command/__init__.py is ugly as sin. Also,
37 the Report object should operate at a higher level of abstraction
38 so we don't have to manually increment fails. (in fact, that should
39 probably be called something different). The by-percent errors should
41 - Indents in upgrade.py are getting pretty ridiculous; more breaking
42 into functions is probably a good idea
43 - Move resolutions in mediawiki.py to a text file? (the parsing overhead
45 - Investigate QuotaParseErrors
46 - If a process is C-ced, it can result in a upgrade that has
47 an updated filesystem but not updated database. Make this more
49 - PHP end of file allows omitted semicolon, can result in parse error
50 if merge resolutions aren't careful.
53 - Make single user mass-migrate work when not logged in as root
54 - Don't use the scripts heuristics unless we're on scripts with the
55 AFS patch. Check with `fs sysname`
56 - Make 'wizard summary' generate nice pretty graphs of installs by date
57 (more histograms, will need to check actual .scripts-version files.)
58 - It should be able to handle installs like Django where there's a component
59 that gets installed in web_scripts and another directory that gets installed
61 - ACLs is a starting point for sending mail to users, but it has
62 several failure modes:
63 - Old maintainers who don't care who are still on the ACL
64 - Private AFS groups that aren't mailing lists and that we
66 A question is whether or not sending mail actually helps us:
67 many users will probably have to come back to us for help; many
68 other users won't care.
70 PULLING OUT CONFIGURATION FILES IN AN AUTOMATED MANNER
72 advancedpoll: Template file to fill out
73 django: Noodles of template files
74 gallery2: Multistage install process
76 mediawiki: One-step install process
77 phpbb: Multistage install process
78 phpical: Template file
81 wordpress: Multistage install process
83 COMMIT MESSAGE FIELDS:
85 Installed-by: username@hostname
86 Pre-commit-by: Real Name <username@mit.edu>
87 Upgraded-by: Real Name <username@mit.edu>
88 Migrated-by: Real Name <username@mit.edu>
89 Wizard-revision: abcdef1234567890
90 Wizard-args: /wizard/bin/wizard foo bar baz
94 Committer: Real Name <username@mit.edu>
95 Author: lockername locker <lockername@scripts.mit.edu>
99 - It is not required nor expected for update scripts to exist for all
100 intervening versions that were present pre-migration; only for it
101 to work on the most recent migration.
103 - Currently all repositories are initialized with --shared, which
104 means they have basically ~no space footprint. However, it
105 also means that /mit/scripts/wizard/srv MUST NOT lose revs after
110 * Some parts of the infrastructure will not be touched, although I plan
111 on documenting them. Specifically, we will be keeping:
113 - parallel-find.pl, and the resulting
114 /mit/scripts/.htaccess/scripts/sec-tools/store/scriptslist
116 * The new procedure for generating an update is as follows:
117 (check out the mass-migration instructions for something in this spirit,
118 although uglier in some ways; A indicates the step /should/ be automated)
120 0. ssh into not-backward, temporarily give the daemon.scripts-security-upd
121 bits by blanching it on system:scripts-security-upd, and run parallel-find.pl
123 1. Have the Git repository and working copy for the project on hand.
125 2. Checkout the pristine branch
127 3. Run wizard `prepare-pristine APP-VERSION`
129 4. Checkout the master branch
131 5. [FOR EXISTING REPOSITORIES]
132 Merge the pristine branch in. Resolve any conflicts that our
133 patches have with new changes. Do NOT let Git auto-commit it
134 with --no-commit (otherwise, you want to git commit --amend
135 to keep our history clean
137 [FOR NEW REPOSITORIES]
138 Check if any patches are needed to make the application work
139 on Scripts (ideally, it shouldn't.) Run
140 `wizard prepare-new` to setup common filesets for our repositories.
142 If you are running a PHP script, there is usually a php.ini file
143 that we package. You can see previous instances of this patch
144 at /mit/scripts/deploy/php.ini/ as well as in the repositories
145 of any already migrated scripts. We hope to make these changes
146 unnecessary once PHP 5.3 arrives.
148 6. Check if there are any special update procedures, and update
149 the wizard.app.APPNAME module accordingly (or create it, if
152 7. Run 'wizard prepare-config' on a scripts server while in a checkout
153 of this newest version. This will prepare a new version of the
154 configuration file based on the application's latest installer.
155 Manually merge back in any custom changes we may have made.
156 Check if any of the regular expressions need tweaking by inspecting
157 the configuration files for user-specific gunk, and modify
158 wizard.app.APPNAME accordingly.
160 8. Commit your changes, and tag as v1.2.3-scripts (or scripts2, if
161 you are amending an install without an upstream changes)
163 NOTE: These steps should be run on a scripts server
165 9. Test the new update procedure using our test scripts. See integration
166 tests for more information on how to do this.
168 http://scripts.mit.edu/wizard/testing.html#acceptance-tests
170 GET APPROVAL BEFORE PROCEEDING ANY FURTHER
172 NOTE: The following commands are to be run on not-backward.mit.edu.
173 You'll need to add daemon.scripts-security-upd to
174 scripts-security-upd to get bits to do this. Make sure you remove
175 these bits when you're done.
177 10. Run `wizard research appname`
178 which uses Git commands to check how many
179 working copies apply the change cleanly, and writes out a logfile
180 with the working copies that don't apply cleanly. It also tells
181 us about "corrupt" working copies, i.e. working copies that
182 have over a certain threshold of changes.
184 11. Run `wizard mass-upgrade appname`, which applies the update to all working
187 12. Run parallel-find.pl to update our inventory
189 * For mass importing into the repository, there are a few extra things:
191 * Many applications had patches associated with them. Be sure to
192 apply them, so later merges work better.
194 # the following operation might require -p1
195 patch -p0 < ../app-1.2.3/app-1.2.3.patch # [FIDDLY BIT]
197 * When running updates, if the patch has changed you will have to
198 do a special procedure for your merge:
200 git checkout pristine
201 # NOTE: Now, the tricky part (this is different from a real update)
202 git symbolic-ref HEAD refs/heads/master
203 # NOTE: Now, we think we're on the master branch, but we have
204 # pristine copy checked out
205 # NOTE: -p0 might need to be twiddled
206 patch -p0 < ../app-1.2.3/app-1.2.3.patch
208 # reconstitute .scripts directory
209 git checkout v1.2.2-scripts -- .scripts
211 # NOTE: Fake the merge
212 git rev-parse pristine > .git/MERGE_HEAD
214 You could also just try your luck with a manual merge using the patch
217 * The repository for a given application will contain the following files:
219 - The actual application's files, as from the official tarball
221 - A .scripts directory, with the intent of holding Scripts specific files
222 if they become necessary.