View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005469||Taler||deployment and operations||public||2018-11-04 17:43||2019-12-20 19:12|
|Reporter||Christian Grothoff||Assigned To||Marcello Stanisci|
|Platform||i7||OS||Debian GNU/Linux||OS Version||squeeze|
|Product Version||git (master)|
|Target Version||0.6||Fixed in Version||0.6|
|Summary||0005469: deploy taler-auditor-httpd|
|Description||We need to deploy the (new) auditor's HTTPD. It should run on auditor.[test/demo].taler.net. The "/" page itself can/should be hijacked to continue to point to the current page.|
Furthermore, before calling 'taler-auditor-sign', we must now run 'taler-auditor-exchange' to add the exchange's master public key and base-URL to the auditor's database.
Please ask me if any of this is unclear.
|Tags||No tags attached.|
I just checked the code, and 'taler-auditor-sign' has the "-m" option that's there for the sole purpose of fetching a exchange's key.
Are you sure we have to call that 'taler-auditor-exchange' tool anyway?
||Yes, that's the only one that adds (or removes) the exchange's URL and master public key to the auditor's database.|
11212f1 @deployment.git adds this invocation.
right now, we are mixing the exchange's and auditor's
deployment; that means that in one script we create the exchange
keys, get them signed by the auditor, and also register the
exchange key+url at the auditor. This will never happen IRL,
but I assume it is okay to get the demo running.
||Given that "/" is also served (statically taking content from auditor.git), this one can be closed now.|
||Well, in reality those steps will have to be interleaved properly as part of the business processes between exchange and auditor. Doing so in the deployment script is fine.|
||Reopening since the 'demo' side doesn't have the auditor deployed yet (what's just missing are a few Nginx rules); this is because we don't want to touch it until next release.|
||Yes, that's the only one that adds (or removes) the exchange's URL and master public key to the auditor's database. https://goo.gl/KyvnZF|
The auditor page is now served, although clicking on 'add auditor' leads to nothing.
Also the BB worker that builds nightly PDF-reports is setup, although the "tex" compilation into PDF breaks in the following way: https://buildbot.taler.net/#/builders/13/builds/3
This breakage was already observed in the test deployment, and got a bug filed: 0005742.
So strictly speaking, this one is solved.
|2018-11-04 17:43||Christian Grothoff||New Issue|
|2018-11-04 17:43||Christian Grothoff||Status||new => assigned|
|2018-11-04 17:43||Christian Grothoff||Assigned To||=> Marcello Stanisci|
|2018-11-29 17:20||Marcello Stanisci||Note Added: 0013370|
|2018-11-29 17:24||Christian Grothoff||Note Added: 0013371|
|2018-11-29 17:51||Marcello Stanisci||Note Added: 0013372|
|2018-11-29 18:03||Marcello Stanisci||Status||assigned => resolved|
|2018-11-29 18:03||Marcello Stanisci||Resolution||open => fixed|
|2018-11-29 18:03||Marcello Stanisci||Note Added: 0013373|
|2018-11-29 18:21||Christian Grothoff||Note Added: 0013374|
|2018-11-29 18:21||Christian Grothoff||Fixed in Version||=> 0.6|
|2018-12-06 13:19||Marcello Stanisci||Relationship added||child of 0005461|
|2018-12-07 18:46||Marcello Stanisci||Status||resolved => new|
|2018-12-07 18:46||Marcello Stanisci||Resolution||fixed => reopened|
|2018-12-07 18:46||Marcello Stanisci||Note Added: 0013392|
|2018-12-07 18:46||Marcello Stanisci||Status||new => assigned|
|2018-12-07 18:48||Marcello Stanisci||Relationship deleted||child of 0005461|
|2018-12-07 18:51||Marcello Stanisci||Relationship added||has duplicate 0005461|
|2019-05-03 16:04||kevlevrone||Note Added: 0014379|
|2019-06-05 18:35||Marcello Stanisci||Note Added: 0014508|
|2019-06-05 18:38||Marcello Stanisci||Status||assigned => resolved|
|2019-12-20 19:12||Christian Grothoff||Status||resolved => closed|