Activity
From 2012-01-26 to 2012-01-26
2012-01-26
- 19:26 User story #2144 (Pending technical review): Bootstrap REST API to manage deployment, PT lib reloading, etc
- Applied in changeset commit:5a2fdaa21a4fee2880e2ec7b042a54631c6946f2.
- 19:25 User story #2144: Bootstrap REST API to manage deployment, PT lib reloading, etc
To sum up:
* the API is available without authentication if configuration property "rudder.rest.allowNonAuthenti...- 17:21 User story #2144 (In progress): Bootstrap REST API to manage deployment, PT lib reloading, etc
- 17:20 User story #2144: Bootstrap REST API to manage deployment, PT lib reloading, etc
- For now, we have decide to have a fully NON-AUTHENTICATED REST API, and let Apache manage that part.
It will be r... - 19:26 Revision 5a2fdaa2 (rudder): Fixes #2144: add a REST API to give status, trigger deployment, etc
- 19:20 User story #2206 (Released): Add a REST PT library reload
- It could be located at: /api/techniqueLibrary/reload
- 19:19 User story #2205 (Released): Add a REST DyngRoups reload
- It could be located at: /api/dyngroup/reload
- 19:16 User story #2204 (Rejected): Add authentication to REST API
- That API need to have some authentication scheme, easily integrable with Lift.
We found these references:
* http... - 18:59 User story #2201 (Discussion): There is no obivous way on Debian systems to detect if a init script is started on boot
- I managed to do it the old way, like we used to do in the SSH PT, but this is a sexy alternative and it actually work...
- 18:12 User story #2201: There is no obivous way on Debian systems to detect if a init script is started on boot
- I just found this: http://packages.debian.org/search?keywords=chkconfig. chkconfig is available for Debian and has be...
- 16:02 User story #2201 (Rejected): There is no obivous way on Debian systems to detect if a init script is started on boot
- There is no evident way on Debian systems to detect if a init script is started on boot !
On SuSE / RedHat systems... - 18:22 Revision 1b260096 (rudder-techniques): Refs #2202: Trivial fixes
- 18:06 User story #2203 (Pending technical review): PT common: Make the common PT copy the CFengine binaries from /opt/rudder/sbin to sys.workdir/bin
- Applied in changeset commit:f186c4e4b5fb6c7c42f143901c2e327ade41ab2d.
- 18:05 User story #2203 (Released): PT common: Make the common PT copy the CFengine binaries from /opt/rudder/sbin to sys.workdir/bin
- PT common: Make the common PT copy the CFengine binaries from /opt/rudder/sbin to sys.workdir/bin
- 18:06 Revision f186c4e4 (rudder-techniques): Fixes #2203: The CFengine binaries are now updated in the workdir if a fresher copy is present in /opt/rudder/sbin
- 18:04 User story #2202 (Pending technical review): PT distributePolicy: Check if all the core rudder daemons are launched and set to start on boot
- Applied in changeset commit:2d187a786414963b362cd8d5e9cca25739930928.
- 18:01 User story #2202 (Released): PT distributePolicy: Check if all the core rudder daemons are launched and set to start on boot
- PT distributePolicy: Check if all the core rudder daemons are launched and set to start on boot
- 18:03 Revision 2d187a78 (rudder-techniques): Fixes #2202: The distributePolicy PT now checks if the core rudder daemons are running and started on boot
- 16:31 Bug #2193 (Pending technical review): When a non modified CR is saved, that leads to a git archiver error
- Applied in changeset commit:8ee19efeb2342b255a24e31f414b424854f9341a.
- 15:24 Bug #2193 (In progress): When a non modified CR is saved, that leads to a git archiver error
- More over, perhaps we don't even show the error when there is really an error, see #2199
- 16:31 Bug #2200 (Pending technical review): The service settings is not Debian compatible
- Applied in changeset commit:1fc9f2cc4db03ed0ff32d72b0b4ac9bf505063df.
- 15:34 Bug #2200 (Released): The service settings is not Debian compatible
- The service settings is not Debian compatible
- 16:31 Revision 85d6729d (rudder-techniques): Merge branch 'branches/rudder/2.3'
- 16:30 Revision 1fc9f2cc (rudder-techniques): Fixes #2200: The servicesManagement PT is now Debian compatible
- 16:30 Revision 8ee19efe (rudder): Fixes #2193; when no modification is actually done to a group/category/PT/PI/CR, do not archive it
- 15:23 Bug #2199 (Released): Git commit error on auto-archive should be a system error in log, not a user one
- The rational behind that is:
* the user see a "save PI error: file was not saved in Git", or "moving group error: ... - 15:06 Bug #2196 (Pending technical review): Restore CR/Croup/policy archives should take there state from the last git commit
- Applied in changeset commit:b5ee448bc6b6607f06870684d7fcfc99a080cb76.
- 14:58 Revision b5ee448b (rudder): Fixes #2196: archive restoration looks for items in Git (last available revision) in place of the FS, so that is there is non commited modification in the FS, they are not taken into account
- 14:45 Architecture #2198 (Released): Create events for all type of action stil lnot historized
- We should create event for node deletion, clear of cache, update of policy server, reload policy template library
- 14:23 Bug #2197 (Rejected): After saving a PI, the selected PI isn't highlighted in the list anymore
- 10:20 Bug #2194: File name is always 'file' in inventory log messages
- Applied in changeset commit:5cc0ea811a9c28fb3dc13068fe88cbc2526ba5d0.
- 10:20 Revision 5cc0ea81 (rudder): Merge branch 'branches/rudder/2.3'
- * branches/rudder/2.3:
Use report file full name in logs, not the parameter name. Fixes #2194 - 10:20 Revision 5cc0ea81 (ldap-inventory): Merge branch 'branches/rudder/2.3'
- * branches/rudder/2.3:
Use report file full name in logs, not the parameter name. Fixes #2194 - 10:19 Revision 48440441 (rudder-techniques): Merge branch 'branches/rudder/2.3'
- * branches/rudder/2.3:
Fixes #2189 : make the generic variable definition multiinstance
Also available in: Atom