Bug 1172295

Hi Rick,

Thank you for raising this bug.

The content in question refers to the integration of OpenStack with RHEV, and is a feature that is only available through this integration.

As such, we can't take the content out because it describes how to use this functionality, but perhaps there is a way we can clarify what is happening here.

Do you have any preferences?

Kind regards,

Andrew

I think the documentation for RHEV needs to be about RHEV.   If there are overlaps with other products, then it should be exceeding clear that these are not about the base product, but only when another product is involved.  Any of these areas need to be highlighted and clearly documented as not being applicable to RHEV.   Similarly,  I would expect OpenStack documentation to have segments that are only applicable when you have certain elements in the mix such as RHEV.   Unless you clearly delineate what is what,  you have a mix of commands that don't match.  

The user manual on my Mazda, for example, talks about 3 different radio models in the section about the radio, but it is clear which controls apply to which model.  They don't just have them all mushed together.

Hi Rick,

Thank you for your response, and my apologies for the delay in getting back to you.

Rather than an overlap between Red Hat Enterprise Virtualization and Red Hat Enterprise Linux OpenStack Platform as such, security groups are a feature that RHEV users can only access when they add a RHEL-OSP environment as an external provider.

A description of external providers and the functionality they provide is presented in Chapter 13. of the Administration Guide - https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Administration_Guide/index.html#chap-External_Providers

As such, while security groups and several other features do indeed relate to RHEL-OSP, they are presented in the Administration Guide as a reference to users looking to harness the capabilities of RHEL-OSP as integrated into their RHEV environment.

While the note on security groups does contain some text designed to explain that security groups are only available on these imported networks, what kind of clarification do you feel we can add here to help users understand that this feature is only available through this integration?

Please let me know what you think.

Kind regards,

Andrew

While the information about neutron is in a 'look here' text box, there is nothing about it to indicate it is *only* for RHEV.   Perhaps change the 
wording to be clearer about that: 

NOTE

If you are using RHEV with OpenStack, you might want to consider the following:

A security group is identified using the ID of that security group as registered in the OpenStacnetwork service. You can find the ID s of security groups for a given tenant by running the
following command on the system on which the OpenStack network service is installed:

Without a little preface, it seems like this little bit of text is just plopped down in the middle of the document.

Hi Rick,

Thank you for your reply.

Understood - we will add a note to the section to help clarify this distinction.

Kind regards,

Andrew

Assigning to Tahlia for review.