[BZ 970784] After successful bundle deployment, discover new resources

After a successful bundle deployment, initiate resource discovery for all the affected resources. This should ensure that user doesn't have to manually add new resources to their inventory (or force discovery process).
On Friday, September 12, 2014 10:43:12 AM jshaughn wrote:
> It may be the person writing the bundle that knows best what he's doing and
> what may need to happen at deploy-time, but I think it's the deployer that
> may even be the better person.  He knows the bundle and he knows the target
> systems.  We could certainly add support as far back as the bundle recipe
> itself, and then allow overrides along the way.  But for now, I think
> support at the Deployment level would be reasonable.  So, maybe adding
> something like BundleDeployment.discoveryDelay (with a defined default) and
> applying it to the resource deployments (it should be accessible through
> BundleResourceDeployment I think).  This would not cause an API change.  It
> would mean a new wizard field to allow for capturing the setting.
> 

+1, the deployer is the one who should decide

> I suppose we could even extend a default setting to the plugin descriptor on
> target types but I'd defer that until some undefined future.
> 
> If we have something like a 5 minute default people may never even have to
> worry about setting it.
>

This is quite conservative and I'd say it'd make our lives a little bit more 
difficult if we ever figure out how to link bundles to resources - a lot can 
happen in that 5 minute timeframe so we'd possibly get some false positives.

I would maybe go the other way and set the default to cca 30s (and make people 
aware of that default right in the wizard). If they know their stuff takes 
longer than that they can adjust.

> What do you guys think?
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/rhq-project/rhq/pull/123/files#r17491964