Bug 1314067 - [Docs] [Backup] [RFE] Undercloud backup/restore procedure for osp-d 8
Summary: [Docs] [Backup] [RFE] Undercloud backup/restore procedure for osp-d 8
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Martin Lopes
QA Contact: Radek Bíba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-02 19:34 UTC by James Slagle
Modified: 2017-09-11 17:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-12 01:42:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description James Slagle 2016-03-02 19:34:52 UTC
We need to make sure the director undercloud backup/restore procedure is documented for osp-d 8.

Here is the documentation for 7:
https://access.redhat.com/documentation/en/red-hat-enterprise-linux-openstack-platform/version-7/back-up-and-restore-red-hat-enterprise-linux-openstack-platform/

I tested out those steps on an osp-d 8 undercloud, and the steps themselves still work with no changes needed.

I would only recommend switching steps 7 and 8 to improve usability. As step 8 is meant to be executed as the root user, but in step 7, we have told the user to switch to the stack user. So, it makes sense to do those steps in the opposite order.

Also in the existing step 7, we say:
sudo yum install -y python-rdomanager-oscplugin

That will still work in osp-d 8, but the package has been renamed to python-tripleoclient, so it would be more correct to say:
sudo yum install -y python-tripleoclient

Comment 2 Andrew Dahms 2016-04-13 04:34:48 UTC
Assigning to Martin for review.

Comment 3 Martin Lopes 2016-04-14 00:52:50 UTC
Thanks for info! Updating guides.

Comment 9 Andrew Dahms 2016-07-12 01:42:47 UTC
This content is now live on the Customer Portal.

Closing.


Note You need to log in before you can comment on or make changes to this bug.