-
Notifications
You must be signed in to change notification settings - Fork 0
/
to-do.txt
80 lines (50 loc) · 2.24 KB
/
to-do.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
- yum clean expire-cache
instead of yum clean all
faster
- zc.zk
- Fix property links:
- get_properties
- dict(props)
- iter(props)
- option on import to ignore ephemeral nodes
- zc.recipe.rhrc: process management needs better error handling.
If the process fails to start, a stop command should be issued.
The reason for issueing the stop command is that the process may
have started, but be running incorrectly and times out. In this
case, we want to stop it if it's running.
(Of course, we should make sure other bits are cleaned up too, if
they aren't already.)
- ISSUE: We need to be wary of lb recovery latency. If an elb takes a
process out while it's down, it may take a minute or more to put it
back. This means that it may not be enough to wait till a process
is accepting requests. We may need to wait till a process is
getting requests.
Alternatively, we can make sure that a process restarts fast enough
that it's not considered unhealthy. This might be another reason to
use a resumelb.
- ISSUE: If we screw up and deploy something that's broken enough to
not start, we should probably stop deploying it.
- ISSUE: How do we delete customers?
- ISSUE: We're careful about the versions of app RPMS, but not their
dependencies.
Later
-----
- Agent: when staging, we'll typically need to install dev rpms and
other dependencies that would normallt appear in the spec file.
Workaround: have stage-build insert rpms. <shrug>
- Need a --force/-f option in agent.
- Fix zimagent to remove monitors when agent.d files are removed and
add monitors when agent.d files are added **without restart**!!!
- zc.zk logging snafus:
- exceptions on shut down
- dealing with replacement of the log file.
- Include log file in zdaemon configs, so that the logtail command works.
- Allow for a variation of
hostagent that configures aws. This could largely function like the
existing host agent, except:
- probably want to store ".deployed" files in S3, rather than on a
particular host.
- Need special case in hamdling RPM/opt garbage collection. We
don't want a local host agent to remove an RPM needed for AWS, but
not locally, and the other way around.
- OS and move to bitbucket