Activity log for bug #1671757

Date Who What changed Old value New value Message
2017-03-10 09:25:57 Bogdan Dobrelya bug added bug
2017-03-10 09:36:33 Bogdan Dobrelya description The guide https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst#deployment-steps looks missing details for the pre/post steps The guide https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst#deployment-steps looks missing details for the pre/post steps. There is also a mention of the ansible tasks "Similar to the step_config, we allow a series of steps for the per-service upgrade sequence, defined as ansible tasks with a tag e.g "step1" for the first step, "step2" for the second". This would be nice to have some example links to repos or code snippets.
2017-03-10 14:42:33 Emilien Macchi tripleo: status New Triaged
2017-03-10 14:42:41 Emilien Macchi tripleo: importance Undecided High
2017-03-10 14:42:46 Emilien Macchi tripleo: milestone pike-1
2017-03-13 14:17:58 Bogdan Dobrelya description The guide https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst#deployment-steps looks missing details for the pre/post steps. There is also a mention of the ansible tasks "Similar to the step_config, we allow a series of steps for the per-service upgrade sequence, defined as ansible tasks with a tag e.g "step1" for the first step, "step2" for the second". This would be nice to have some example links to repos or code snippets. The guide https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst#deployment-steps looks missing details for the pre/post steps. There is also a mention of the ansible tasks "Similar to the step_config, we allow a series of steps for the per-service upgrade sequence, defined as ansible tasks with a tag e.g "step1" for the first step, "step2" for the second". This would be nice to have some example links to repos or code snippets. Ideally, all steps, including upgrade/containers variations, should be presented in dev docs as UML. It's a burden to keep them updated with ongoing changes. But even having those obsoleted *and* depicted, would make the learning curve less steep.
2017-04-03 11:03:43 Bogdan Dobrelya summary [doc] Document pre/post steps in the tht deployment steps guide [doc] Document pre/post/upgrade/batch ordered and concurrent steps in the tht deployment steps guide
2017-04-03 11:06:33 Bogdan Dobrelya description The guide https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst#deployment-steps looks missing details for the pre/post steps. There is also a mention of the ansible tasks "Similar to the step_config, we allow a series of steps for the per-service upgrade sequence, defined as ansible tasks with a tag e.g "step1" for the first step, "step2" for the second". This would be nice to have some example links to repos or code snippets. Ideally, all steps, including upgrade/containers variations, should be presented in dev docs as UML. It's a burden to keep them updated with ongoing changes. But even having those obsoleted *and* depicted, would make the learning curve less steep. The guide https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst#deployment-steps looks missing details for the pre/post steps. There is also a mention of the ansible tasks "Similar to the step_config, we allow a series of steps for the per-service upgrade sequence, defined as ansible tasks with a tag e.g "step1" for the first step, "step2" for the second". This would be nice to have some example links to repos or code snippets. Ideally, all steps, including upgrade/containers variations, should be presented in dev docs as UML. It's a burden to keep them updated with ongoing changes. But even having those obsoleted *and* depicted, would make the learning curve less steep. Perfectly, those UMLs must be autogenerated with tools like heat stack-preview / tox -e templates and the like. Otherwise, it is likely not doable to follow multiple dev changes done into deployment graphs manually.
2017-04-03 11:06:41 Bogdan Dobrelya bug added subscriber Steven Hardy
2017-04-03 11:07:32 Bogdan Dobrelya bug added subscriber Marios Andreou
2017-04-03 11:07:55 Bogdan Dobrelya tags documentation
2017-04-03 11:14:02 Bogdan Dobrelya bug added subscriber Lars Kellogg-Stedman
2017-04-11 10:56:58 Emilien Macchi tripleo: milestone pike-1 pike-2
2017-04-12 11:27:51 OpenStack Infra tripleo: status Triaged In Progress
2017-04-12 11:27:51 OpenStack Infra tripleo: assignee Bogdan Dobrelya (bogdando)
2017-04-13 14:49:21 Bogdan Dobrelya tripleo: assignee Bogdan Dobrelya (bogdando)
2017-04-13 14:49:25 Bogdan Dobrelya tripleo: status In Progress Triaged
2017-06-08 20:46:43 Emilien Macchi tripleo: milestone pike-2 pike-3
2017-07-30 04:38:26 Emilien Macchi tripleo: milestone pike-3 pike-rc1
2017-08-25 13:41:20 Emilien Macchi tripleo: milestone pike-rc1 pike-rc2
2017-09-05 18:32:54 Emilien Macchi tripleo: milestone pike-rc2 queens-1
2017-10-23 16:08:19 Emilien Macchi tripleo: milestone queens-1 queens-2
2017-12-05 00:05:18 Alex Schultz tripleo: milestone queens-2 queens-3
2018-01-26 00:51:30 Emilien Macchi tripleo: milestone queens-3 queens-rc1
2018-03-02 20:15:57 Alex Schultz tripleo: milestone queens-rc1 rocky-1
2018-04-20 17:03:34 Alex Schultz tripleo: milestone rocky-1 rocky-2
2018-06-05 19:04:30 Emilien Macchi tripleo: milestone rocky-2 rocky-3
2018-07-26 13:42:27 Emilien Macchi tripleo: milestone rocky-3 rocky-rc1
2018-08-14 14:58:34 Alex Schultz tripleo: milestone rocky-rc1 stein-1
2018-10-30 16:13:49 Juan Antonio Osorio Robles tripleo: milestone stein-1 stein-2
2018-12-29 23:57:27 Emilien Macchi tripleo: importance High Undecided
2018-12-29 23:57:27 Emilien Macchi tripleo: status Triaged Expired