Bug 1331224 - [Docs] [Config Ref] Remove references to ZeroMQ
Summary: [Docs] [Config Ref] Remove references to ZeroMQ
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: async
: 8.0 (Liberty)
Assignee: Deepti Navale
QA Contact: Radek Bíba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 03:15 UTC by Andrew Dahms
Modified: 2016-06-06 11:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-06 11:12:51 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Andrew Dahms 2016-04-28 03:15:38 UTC
All references to ZeroMQ must be removed from the Configuration Reference. This applies to all mention in tables, and sections discussing the configuration of ZeroMQ. However, instances where options for ZeroMQ are presented as part of a screen section representing the contents of a configuration file can be retained because they help readers to understand the actual structure of that file.

Comment 1 Andrew Dahms 2016-04-28 03:16:11 UTC
Assigning to Deepti for review.

Comment 4 Radek Bíba 2016-05-02 08:56:20 UTC
Hi Andrew,

Does this bug apply to OSP 7 as well? Should the changes be cherry-picked?

Comment 5 Andrew Dahms 2016-05-02 23:09:35 UTC
Hi Radek,

Thank you for taking a look at the changes.

That sounds like a great idea if it is easy enough to do. Let me know if you can cherry pick the changes across, and I can publish the updates to both OSP 7 and OSP 8.

Kind regards,

Andrew

Comment 6 Radek Bíba 2016-05-03 06:28:07 UTC
I was able to cherry pick the changes, eventually. Please publish the updates.

Comment 7 Andrew Dahms 2016-06-06 11:12:51 UTC
Hi Radek,

Thank you for the needinfo request, and my apologies for the delay in responding to you.

These changes have since been published, and everything looks good.

Closing.

Kind regards,

Andrew


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