View Issue Details

IDProjectCategoryView StatusLast Update
0005984Talerdeployment and operationspublic2019-12-03 13:30
ReporterFlorian DoldAssigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0005984: usability of deployment.git must be improved
DescriptionIn order to upgrade an environment, currently we have to run an arcane set of commands in the right order.

* When taler-deployment-sign is run before taler-deplyoment-keyup, a new and different key is created for the exchange. That's not really acceptable.

* We frequently run info permissions problems on the demo-blue/demo-green split. The corresponding deployment scripts should make sure that permissions are correct.

* The following "tools" should probably be folded into one command:
  (1) taler-deployment-config-generate
  (2) taler-deployment-keyup
  (3) taler-deployment-sign
  (4) taler-deployment-hier (what does this one even do?)
  (And what does taler-deployment-prepare even do? It looks like some unholy amalgamation of the previous commands *plus* running a re-build)

* scripts for taler-deployment-start should probably *also* run some checks after it finishes and print the output of "taler-deployment-arm -I", so it is harder to forget checking manually
TagsNo tags attached.


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-12-03 13:30 Florian Dold New Issue