View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005016 | Taler | deployment and operations | public | 2017-05-18 13:02 | 2018-04-15 18:34 |
| Reporter | Marcello Stanisci | Assigned To | Marcello Stanisci | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.5 | Fixed in Version | 0.5 | ||
| Summary | 0005016: exchange key and standalone db | ||||
| Description | 1. The deployment utility taler-deployment-config-generate needs the exchange's public key. Currently, no utility generates the key before taler-deployment-config-generate. The "bootstrap" utility could do this. 2. The standalone deployment uses a postgres db instance run as a ARM service, so before calling taler-deployment-build (which calls the various testcases) the postgres-standalone-service should be launched (manually or by some script). | ||||
| Tags | No tags attached. | ||||
| As of 2. A possible fix might be adding a '--no-check' flag to taler-deployment-build, so that it only installs. After a successful installation, then the user manually starts the db and (if needed) she calls taler-deployment-build again which will run the tests this time. | |
| The 'gnunet-ecc' tool (with -g1) can be used to generate the keys. Should be trivial to extend the script to call gnunet-ecc if the file does not exist, right? | |
| No need to generate master public key: we keep it under version, therefore just copy it when deploying. The database is just started manually, and 'onboarding' docs (d1a404e) mention how to do it. Bank and other involved codebases have been adapted to this. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-18 13:02 | Marcello Stanisci | New Issue | |
| 2017-05-18 13:02 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2017-05-18 13:02 | Marcello Stanisci | Status | new => assigned |
| 2017-05-18 14:07 | Marcello Stanisci | Note Added: 0012140 | |
| 2017-12-14 14:56 | Christian Grothoff | Product Version | => git (master) |
| 2017-12-14 14:56 | Christian Grothoff | Target Version | => 0.6 |
| 2017-12-14 14:56 | Christian Grothoff | Note Added: 0012687 | |
| 2017-12-26 18:04 | Marcello Stanisci | Status | assigned => informing |
| 2017-12-26 18:04 | Marcello Stanisci | Resolution | open => fixed |
| 2017-12-26 18:04 | Marcello Stanisci | Note Added: 0012704 | |
| 2017-12-28 16:28 | Christian Grothoff | Fixed in Version | => 0.5 |
| 2017-12-28 16:28 | Christian Grothoff | Target Version | 0.6 => 0.5 |
| 2018-04-15 18:34 | Christian Grothoff | Status | informing => closed |