Show More
@@ -0,0 +1,31 b'' | |||
|
1 | ========================================= | |
|
2 | Notes on the IPython configuration system | |
|
3 | ========================================= | |
|
4 | ||
|
5 | To start, an IPython process needs: | |
|
6 | ||
|
7 | * Configuration files | |
|
8 | * Command line options | |
|
9 | * Additional files (FURL files, extra scripts, etc.) | |
|
10 | ||
|
11 | It feeds these things into the core logic of the process, and as output, | |
|
12 | produces: | |
|
13 | ||
|
14 | * Log files | |
|
15 | * Security files | |
|
16 | ||
|
17 | There are a number of things that complicate this: | |
|
18 | ||
|
19 | * A process may need to be started on a different host that doesn't have | |
|
20 | any of the config files or additional files. Those files need to be | |
|
21 | moved over and put in a staging area. The process then needs to be told | |
|
22 | about them. | |
|
23 | * The location of the output files should somehow be set by config files or | |
|
24 | command line options. | |
|
25 | * Our config files are very hierarchical, but command line options are flat, | |
|
26 | making it difficult to relate command line options to config files. | |
|
27 | * Some processes (like ipcluster and the daemons) have to manage the input and | |
|
28 | output files for multiple different subprocesses, each possibly on a | |
|
29 | different host. Ahhhh! | |
|
30 | * Our configurations are not singletons. A given user will likely have | |
|
31 | many different configurations for different clusters. |
General Comments 0
You need to be logged in to leave comments.
Login now