forked from jss-emr/jss-scm
-
Notifications
You must be signed in to change notification settings - Fork 0
/
developer-log
93 lines (78 loc) · 3.92 KB
/
developer-log
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
# Command to run vagrant provision
STAGE="deploy" vagrant provision
Stages
------
Provision
Stop Bahmni
Deploy Bahmni
Start Bahmni
Development: Deploy Bahmni on running platform
Convention (case included)
--------------------------
variable_name, resource_name, class_name
file-name.pp
Do not use wget. Provisioning should work in low/no network sites as well.
Make sure the resource definitions have checks so that when run again they are fast and leave the system in correct state
Class with arguments only if we would declare more than one of those resources.
Use the order of definition to express the order of execution, "require" is really not required.
Define the resources based on what it creates rather and what it does
Use test.pp instead of commenting includes
Good Puppet Doc here: http://docs.puppetlabs.com/learning/
http://www.ibm.com/developerworks/linux/library/l-lpic1-v3-102-5/
Technical debt
--------------
0. Enable acpi - https://wiki.archlinux.org/index.php/Acpid
1. We have a pattern - create a shell script using a template file and then execute the same script. Can this be done via a single custom resource type
2. Make all the actions idempotent, i.e. do nothing if already in the state required
3. There are a lot of classes where we had to set path, set user, group etc. Find out if there is a way to set this in one place and get this to work.
4. All the shell scripts are currently dumped in temp dir. May be we should have sub-folders inside it as well
5. Deployment classes do not need to "require" Provision classes. Eventually we should not need this but currently we are not confident whether running same class twice would have an affect or not.
6. How to avoid running provision on vagrant reload.
7. The packaging of containing unnecessary items in it
8. Tomcat memory should be configurable
9. Need to ensure that all passwords are cleaned up after deployment/provisioning - or better not save password anywhere
10. puppet mysql/postgres replication running via puppet code
11. Refactor puppet scripts to keep all the environment specific variables in a single file (tomcat memory parameter)
12. Active passive deployment via command line instead of changing the files
TODO
----
pydot
createrepo
puppet
git
select datname from pg_database where datdba=(select usesysid from pg_user where usename='openerp') and datname not in ('template1', 'template0', 'postgres') order by datname
select datname from pg_database where datdba=(select usesysid from pg_user where usename='openerp') and datname not in ('template1', 'template0', 'postgres') order by datname
select datname from pg_database where datdba=(select usesysid from pg_user where usename='openerp') and datname not in ('template1', 'template0', 'postgres') order by datname
select datname from pg_database where datdba=(select usesysid from pg_user where usename='openerp') and datname not in ('template1', 'template0', 'postgres') order by datname
select datname from pg_database where datdba=(select usesysid from pg_user where usename='openerp') and datname not in ('template1', 'template0', 'postgres') order by datname
select datname from pg_database where datdba=(select usesysid from pg_user where usename='openerp') and datname not in ('template1', 'template0', 'postgres') order by datname
Things to go in package
-----------------------
REST extension
Issues
------
all openerp module dependencies
dump on vinay's machine
missing eggs
log file sizes
git ignore test.pp
crontab email delete
remaining
---------
reports
lsyncd
The migration process didn't exit after it finished. Something to do with threads.
Both the backup failed when run from puppet
Support tasks
-------------
Monitoring
Backup should stop postgres and take backup
Setup network so that subdomains, sub-nets and domain work correctly
Network to allow ssh from outside.
Setup key based auth for machines.
Take backup of zero shell.
Performance
-----------
Understand
----------
How to find the checksum for a file from puppet