| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2017-03-01 | Put service stop at step1 and quiesce at step2. |   Sofer Athlan-Guyot | 1 | -1/+1 | |
| In the previous release[1], the services were stopped before the pacemaker services, so that they get a chance to send last message to the database/rabbitmq queue: Let's do the upgrade in the same order. [1] https://github.com/openstack/tripleo-heat-templates/blob/stable/newton/extraconfig/tasks/major_upgrade_controller_pacemaker_2.sh#L13-L71 Change-Id: I1c4045e8b9167396c9dfa4da99973102f1af1218 (cherry picked from commit fb7821378242e595184a38e1e0cb7e9978c0f806) | |||||
| 2017-01-24 | Add glance registry service to disable on upgrade |   Steven Hardy | 1 | -0/+30 | |
| We've broken the upgrade job because anyone upgrading with the glance registry deployed (and defined in their *Services parameters) will try to deploy with the old glance-registry.yaml defined in heat. Instead we define a template which stops and disables the service on upgrade. Closes-Bug: #1659079 Change-Id: I03561954d794afae2be06811375d16611fa45973 | |||||
 |
index : apex-tripleo-heat-templates | |
| Unnamed repository | Grokmirror user |
| aboutsummaryrefslogtreecommitdiffstats |