Red Hat Bugzilla – Bug 867928
CFCE User Guide section 4.2.3 Setting Up a Cloud Resource Provider Connection update
Last modified: 2012-12-10 17:10:55 EST
Description of problem:
The instructions in CFCE user guide  only work for creating a new EC2 cloud resource provider. RHEVM and Vsphere require a config file edit and a re-run of aeolus-configure -p [rhevm|vsphere] per install guide .
Version-Release number of selected component (if applicable):
Steps to create new vsphere or rhevm cloud resource provider:
1. edit /etc/aeolus-configure/nodes/rhevm_configure or /etc/aeolus-configure/nodes/vsphere_configure
2. run aeolus-configure -p [vsphere|rhevm]
We need to verify that re-running aeolus-configure doesn't break anything. For example, if in LDAP mode does aeolus-configure revert the config back to local users?
(In reply to comment #0)
> Description of problem:
> The instructions in CFCE user guide  only work for creating a new EC2
> cloud resource provider. RHEVM and Vsphere require a config file edit and a
> re-run of aeolus-configure -p [rhevm|vsphere] per install guide .
> Steps to create new vsphere or rhevm cloud resource provider:
> 1. edit /etc/aeolus-configure/nodes/rhevm_configure or
> 2. run aeolus-configure -p [vsphere|rhevm]
I can place a reference from this procedure citing the Appendix in the Installation Guide for configuration instructions.
I'll also add the aeolus-configure -p [vsphere|rhevm] to the Appendix in the Installation Guide.
> We need to verify that re-running aeolus-configure doesn't break anything.
> For example, if in LDAP mode does aeolus-configure revert the config back to
> local users?
I wouldn't say this is a documentation bug just yet. This sounds more like a software bug because, theoretically, an admin should be able to run aeolus-configure without affecting LDAP settings.
I'd recommend testing this and, if the problem exists, opening a bug to fix the issue. However, if this is something that can't be fixed before 1.1, we can add some documentation (possibly as a Release Note).
Changed relevant content in book. Will be available next brew of the book.
Re-running aeolus-configure -p vsphere|rhevm reverts authorization mode to database. So if LDAP, one needs to edit the files and restart services.
1. edit /etc/aeolus-conductor/settings.yml
2. edit /etc/ldap_fluff.yml
3. `aeolus-services restart`
(In reply to comment #5)
> Re-running aeolus-configure -p vsphere|rhevm reverts authorization mode to
> database. So if LDAP, one needs to edit the files and restart services.
> 1. edit /etc/aeolus-conductor/settings.yml
> 2. edit /etc/ldap_fluff.yml
> 3. `aeolus-services restart`
Or include the desired LDAP command-line arguments when re-running aeolus-configure? Although I think we already document setting up LDAP using the method described in comment#5. Probably best to stick with that?
Agree that sticking with the suggestion in comment 5 & the existing docs is probably the best idea at this point.
Does aeolus-configure overwrite the /etc/ldap_fluff.yml file or not? I would assume not since aeolus-configure doesn't seem to touch LDAP settings (yet), which means step 2 in comment #5 of the above bug isn't needed. This would be a good thing since rewriting the LDAP settings each time you run aeolus-configure is a little cumbersome.
This documentation has now been dropped to translation ahead of publication. For any further issues, please open a new a bug.
This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug.