Description of problem:
There is no Openstack discovery possibility both in Cloud and Infra. There is only Amazon, RHEV, VMware and Microsoft provider discovery.
Version-Release number of selected component (if applicable):
Can you provide any doc or description to what discovery means in this context?
Discovery means you tell CFME an IP address range and kinds of providers and it will scan this IP range and add all found providers in the inventory (in UI: Cloud|Infrastructure -> Providers -> Configuration -> Discover ...)
Hm not sure if there is some usecase for this in OpenStack, since you just need IP address to keystone.
John are there some usecases for Discovery for OpenStack providers?
@Mainn this might be relevant now. Similar to e.g. aws, we could use discovery too add multiple Regions (region per manager) in one form.
This bug has been open for more than a year and is assigned to an older release of CloudForms.
If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.
Reopened, this is an RFE targeting a future release and therefore is not related to any current version.
(In reply to Gilles Dubreuil from comment #15)
> Initial discovery for OpenStack undercloud:
> The following part will add authentication (re-directing).
Can we make it for Monday Dev Freeze, there is nobody assigned for review?
Openstack Infrastructure (Director) discovery has been added, using following Pull Requests:
There has been structural re-factor work to the network discovery parts.
Please see https://github.com/ManageIQ/manageiq-network_discovery/issues/8 for more information.
The current status is:
- https://github.com/ManageIQ/manageiq-network_discovery/pull/10 is now obsolete.
- https://github.com/ManageIQ/manageiq-providers-openstack/pull/205 has been merged
- https://github.com/ManageIQ/manageiq/pull/16318 enables Openstack Infra discovery
- https://github.com/ManageIQ/manageiq/pull/16946 activates the new re-factorisation which moved the probes to respective providers.
There is a step back because of name space issue, where the short version is because the name 'Network' is used by ems_infra model (STI) which collide with 'ManageIQ::Network' name. Consequently the latter is renamed to 'ManageIQ::NetworkDiscovery', within following PRs:
Network discovery relocation dust has settled down, now this ready to offer feature once https://github.com/ManageIQ/manageiq/pull/16318 has been merged.
https://github.com/ManageIQ/manageiq/pull/16318 has been merged.
Verified on 18.104.22.168
I have RHOS 11 (Undercloud, 3*Controller, 2*Compute)
[root@sealusa12 ~]# cat clouds.yaml
#BEGIN undercloud PARAMETERS
#END undercloud PARAMETERS
#BEGIN overcloud PARAMETERS
#END overcloud PARAMETERS
Steps to reproduce
1. Login to CFME
2. Browse: Compute --> Infrastructure --> Providers
3. Click: Configuration --> Discover Infrastructure Providers
4. - Mark Openstack Infra
- Enter Subnet Range: 192.168.24.1 , 192.168.24.10
Message is appeared: "Infrastructure Providers: Discovery successfully initiated"
Refresh the page and provider with IP address 192.168.24.2 is discovered
192.168.24.1 and 192.168.24.3 are discovered
192.168.24.2 isn't discovered
Also I've tried to enter the specific IP range 192.168.24.2 , 192.168.24.2
Result: 192.168.24.2 doesn't discover.
I set the Infrastructure Provider manually
1. Browse: Compute --> Clouds --> Providers
2. Click: Configuration
Result: Discover Cloud Providers is grayed out
Ironic SSL port scanning is now covered:
PR merged upstream, back port now doable for Gaprindashvili branch.
For Infra provider:
Verified on 22.214.171.124
For Cloud provider:
Am I right that this feature shouldn't be available for Cloud provider? So actual behavior where "Discover Cloud Providers" is grayed out is correct?
Created attachment 1476605 [details]
Cloud Providers Discovery is grayed out
Confirmed, this BZ should solve Infra provider discovery only. Cloud provider discovery needs to be implemented in a different way.
Verified on 126.96.36.199
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.