ngcpcfg

Commit Graph

Author	SHA1	Message	Date
Michael Prokop	bd9bf75e4a	TT#11776 Support git v2.9.3 and newer When installing Debian/stretch we fail at this stage: \| ngcpcfg --no-db-sync commit On first glance it looks like a mariadb issue, though actually it's the git status check inside ngcpcfg that's failing. The reason is that starting with git v2.9.3 there's a different output in its "status" output: \| commit 2a0e6cdedab306eccbd297c051035c13d0266343 \| Author: Lars Vogel <lars.vogel@gmail.com> \| Date: Thu Jun 9 20:19:30 2016 +0200 \| \| Use "working tree" instead of "working directory" for git status \| \| Working directory can be easily confused with the current directory. \| In one of my patches I already updated the usage of working directory \| with working tree for the man page but I noticed that git status also \| uses this incorrect term. \| \| Signed-off-by: Lars Vogel <Lars.Vogel@vogella.com> \| Signed-off-by: Junio C Hamano <gitster@pobox.com> In Debian/stretch we've 2.11.0-2 and are affected by this change. Adjust the `git status` checks accordingly to support git in all its versions. NOTE: we should consider switching to `git status --porcelain` (see git commit `fc5af3bbb2` for some history about it) once we've the testsuite in place. Change-Id: If4223a35083d279e746dce5a80bcb86b52f64025	9 years ago
Michael Prokop	4fd512261b	MT#16393 Check for branch 'master' being active Verify that the user is operating on branch master, otherwise the result might be unexpected. If branch master is checked out: \| root@spce:/etc/ngcp-config# ngcpcfg check \| root@spce:/etc/ngcp-config# ngcpcfg status \| [...] \| 2016-02-23 05:48:32: Checking currently active branch: \| 2016-02-23 05:48:32: OK: branch master active If a branch other than 'master' is checked out: \| root@spce:/etc/ngcp-config# ngcpcfg check \| 2016-02-23 05:47:42: Error: branch 'mika' in '/etc/ngcp-config' active - please switch to branch 'master' before continuing. \| root@spce:/etc/ngcp-config# echo $? \| 1 \| root@spce:/etc/ngcp-config# ngcpcfg status \| [...] \| 2016-02-23 05:47:47: Checking currently active branch: \| 2016-02-23 05:47:47: ACTION_NEEDED: branch 'mika' active - please switch to branch 'master' \| [...] Change-Id: I5df92075905cafa3b714211581c8cfe749df04ba	10 years ago
Michael Prokop	c9b62658a1	MT#15973 Report in 'status' action when build/apply run is needed In a previous implementation using timestamps we ran into timing problems on slower systems. So instead lets record the git commit ID of the latest ngcpcfg commit and check whether we have a match between this commit and an according ngcpcfg build. If the "ngcpcfg build" was executed without an "ngcpcfg commit" before then we mark it as dirty since we don't have an according git commit available for testing against. Since that's a common workflow we don't report it as a real problem though, instead we inform the user using: \| OK: nothing to build (latest build newer than latest commit) As we commit AFTER the build in the apply action we can use a workaround for this situation, so build and commit state match with each other in that case then. Change-Id: I48e32db6f42b53fe97a0b88805e7ddbee8576133	10 years ago
Michael Prokop	0d828d4108	MT#15973 Revert "MT#15973 Report in 'status' action when build/apply run is needed" This reverts commit `db373d3927`. Conflicts: etc/ngcp-config/ngcpcfg.cfg Until we've a working solution for this let's revert the broken change so we avoid this being a release stopper. Change-Id: If03d9b3913de23c698b430d583dc7babfcc4ff04	10 years ago
Guillem Jover	301cb7cd3c	MT#16387 Report pending requested reboots There are some times when a configuration, service or system upgrade requires a reboot to take effect. When a component requires a reboot, it will record this fact in the file system through the file «/var/run/reboot-required», and «ngcpcfg status» will notify the user that a reboot has been requested. We use the «/var/run/reboot-required» because it is already being used in the unattended-upgrades package on Debian/Ubuntu which does something similar. Change-Id: I43997bfb83892f67bd57bb55ad3ec0a41a5e088d	10 years ago
Michael Prokop	db373d3927	MT#15973 Report in 'status' action when build/apply run is needed If the latest git commit has a newer timestamp than our latest "build" action then a "build" (or apply) run is required, inform the user about it. Change-Id: I83e2ff47ba54da733d368d78b6616d13d31a66d4	10 years ago
Alexander Lutay	550067a6a8	MT#15803 Check oustanding pull actions only (ignore outstanding push actions) Switch code to new common check function execute_check_shared_storage() Change-Id: I7ba86912d7b5874f9ce0778a2a87b2afb33be5ee	10 years ago
Michael Prokop	d7d48e15a1	MT#15803 Fix usage of HA features in 'ngcpcfg status' `which $function` doesn't work as intended, commit dc984aa2e7 in ngcpcfg-ha.git broke the HA features in 'ngcpcfg status' therefore. Change-Id: I2bb9ed9b3276e63fc6d127559df32ae229a43b33	10 years ago
Victor Seva	eac494cb42	MT#14229 clean shellcheck warnings While at it spread support for testsuite Change-Id: I60c4dae5479827b0d28ffa135105d9dbdf603825	11 years ago
Michael Prokop	2deea0fb39	MT#9557 Provide timestamps in console output Change-Id: I5be915fa876014cbb9c792b03be325d6595daac9	11 years ago
Michael Prokop	fe8b4ad8fd	MT#9287 Implement status logic for usage on carrier systems While at it move further HA/PRO code to ngcpcfg-ha Change-Id: I2d9e9dd236a9aee7e7c1fd40a0392077ebf6c13a	11 years ago
Victor Seva	d9e6ba263d	MT#8067 check nodename no hostname to exclude ourselves	12 years ago
Michael Prokop	def862dd8a	MT#2231 status option: check for pull/push + check state of remote host(s)	12 years ago
Michael Prokop	3436c08361	Initial checkin	13 years ago

14 Commits (5775b115276947c78b74a1726df85551fed79d8b)