Bug 1235997
| Summary: | [Docs] [Director] Support heat templates w/o tuskar when runnng package update | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jan Provaznik <jprovazn> |
| Component: | documentation | Assignee: | Dan Macpherson <dmacpher> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | Director | CC: | adahms, calfonso, jprovazn, jslagle, mburns, nbarcet, rhel-osp-director-maint, yeylon, zbitter |
| Target Milestone: | ga | Keywords: | Documentation, Triaged |
| Target Release: | Director | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-01-04 01:40:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jan Provaznik
2015-06-26 10:07:06 UTC
We need to document the workaround using heat directly. Assigning to Dan for review. Would the workaround be something as simple as: $ heat stack-update -f <template_file> overcloud Or is there more to it? For simplest pkg update w/o rolling updates (updating machines one by one), doing: $ heat stack-update -f <template_file> overcloud -P UpdateIdentifier=timestamp should work. But "openstack overcloud stack update" updates nodes sequentially - it sets breakpoints on each of node and user removes them during update. Doing this manually is possible too because heat CLI supports setting/removing/polling breakpoints, but it would more complicated, worflow looks like this: $ heat stack-update -f <template_file> overcloud -P UpdateIdentifier=timestamp -f env_file_with_breakpoints $ poll if stack-update reached breakpoint $ remove a breakpoint $ iterate above 2 steps I did not test these manual steps (testing this and make doc for it would take more time). Midstream doc patch is here: https://review.gerrithub.io/239621 It seems to me that having users manually drive the workflow by manipulating breakpoints is untenable as a solution. The workflow is designed to prevent e.g. downtime for the controller; it's incredibly difficult to describe and even harder for a user to get right. If we're supporting a --use-tripleo-heat-templates option to "openstack overcloud deploy" then IMHO we also need to add a similar option for all commands, such as "openstack overcloud update stack". "overcloud stack update" command was improved to work with heat templates directly: https://bugzilla.redhat.com/show_bug.cgi?id=1242967 Documentation patch which describes running pkg update both with and without tuskar is here: https://review.gerrithub.io/239621 Looks good to me; moving to VERIFIED. This content is now live on the Customer Portal; closing. |