forked from mbailey/deprec
-
Notifications
You must be signed in to change notification settings - Fork 1
/
TODO.txt
132 lines (78 loc) · 3.15 KB
/
TODO.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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
deprec/TODO.txt
# Mysql - delete initially created accounts
# they stop 'mike'@'%' from working
# http://bugs.mysql.com/bug.php?id=36576
# http://dev.mysql.com/doc/refman/5.0/en/default-privileges.html
DROP USER '';
DROP USER ''@'localhost';
# collectd
+ start on boot (init.d)
+ install php_collection
- auth
- update config.php
($config['datadirs'] = array('/usr/local/var/lib/collectd/');)
+ nginx plugin
- symlink lib on install
- add nagios to collectd group (create group)
+ apache plugin
/etc/apache2/mods-available/status.conf ExtendedStatus On
# nagios
+ pull in commands, services, hostgroups from mon.failmode
* show downloads version/date # shows project not stale
* email OMGWTFTOAST
* mission
* mailing list etiquette
* bus factor 1
* getting contributions
use 'rake gems:install' instead of gems_for_project
* clean out stale tasks (from cap -T)
* check for cdrom line in /etc/apt/sources.list
# deb cdrom:[Ubuntu-Server 7.10 _Gutsy Gibbon_ - Release i386 (20071016)]/ gutsy main restricted
== Milestone 1
ssl problem "ssl_error_rx_record_too_long"
- remove default site?
sort out cert generation
ensure this is installed
NameVirtualHost *:80
<IfModule mod_ssl.c>
NameVirtualHost *:443
</IfModule>
== Milestone 2
* make quieter
* Stop double printing of tasks when linked to canonical name
* unlink ree when normal ruby installed
* check REE is unlinked when ruby-1.8.7 installed
== Milestone 3
# Chef
# Install Server or Client
# Make sure they're in DNS or chef-client will fail with the following:
root@node1:/etc/chef# chef-client
/registrations/node1
/openid/consumer/start
/usr/local/lib/ruby/1.8/net/http.rb:2097:in `error!': 400 "Bad Request" (Net::HTTPServerException)
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/rest.rb:233:in `run_request'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/rest.rb:95:in `post_rest'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/client.rb:223:in `authenticate'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/client.rb:74:in `run'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/application/client.rb:163:in `run_application'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/application/client.rb:161:in `loop'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/application/client.rb:161:in `run_application'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/lib/chef/application.rb:53:in `run'
from /usr/local/lib/ruby/gems/1.8/gems/chef-0.7.0/bin/chef-client:26
from /usr/local/bin/chef-client:19:in `load'
from /usr/local/bin/chef-client:19
$ time cap deprec:chef:install HOSTS=chef2
real 14m17.875s
user 0m7.457s
sys 0m7.979s
! Server setup needs to restart/reload Apache for SSL cert to get picked up
! client - unable to resolve node1 - need to put in /etc/hosts?
client> sudo chef-client
chef web: Registrations -> Validate Registration
client> sudo chef-client
# Chef repo
git://github.com/mbailey/chef-repo.git
! client start script
? how do we push from server?
? where does validation token come from?
! 8.04.2 is worth considering