I added vCenter to MIQ for the first time about a week ago and did not have this experience
I can only think: are you sure you have hosts set up with your vcenter?
I'm new to manageIQ, is there anything else I need to do in Vcenter first ?
You can switch from dashboard to list view on the top right corner of the provider page
If you don't see any error try kicking a full refresh by hitting configuration->refresh relationships and power states
Default Credentials Valid
Hosts 0
And try to find that error in the log, it should have a more informative error message
And what version do you have ?
ERROR -- : [IPAddr::InvalidPrefixError]: invalid length Method:[block (2 levels) in <class:LogProxy>]
ERROR -- : MIQ(ManageIQ::Providers::Vmware::InfraManager::Inventory::Collector#vim_collector) EMS: [vcenter], id: [4] Refresh fail
@zigaSRC Just adding a new approval process for an existing request type isn’t that arduous, there’s an example of doing it for automation request approval here: https://pemcg.gitbooks.io/mastering-automation-in-cloudforms-4-2-and-manage/content/automation_request_approval/chapter.html. I think @mikebutak was referring to implementing a whole new multi-level approval process which is definitely non-trivial.
Implementing a new back-end request & task type would be a lot more work
Hi @pemcg, yes I've seen that example before and from what I understand that's just adding an approval process for all automation requests. There's no way to have multiple/different approval proceses for different state machines/instances, is that correct?
Also what values need to be entered to create an automation request from a button? I haven't managed to find an example for it.
Also what values need to be entered to create an automation request from a button? I haven't managed to find an example for it.
@zigaSRC From a button the easiest thing to do is write a short Ruby method that calls
$evm.execute(‘create_automation_request’,…), for example:options = {}
options[:namespace] = 'Stuff'
options[:class_name] = 'Methods'
options[:instance_name] = 'MyInstance'
options[:user_id] = $evm.vmdb(:user).find_by_userid('pemcg').id
# options[:attrs] = attrs
# options[:miq_zone] = zone
auto_approve = true
$evm.execute('create_automation_request', options, 'admin', auto_approve)
the
options[:user_id] value you could take from the logged in user, something like $evm.root['user'].id
You could try creating the
/System/Policy/AutomationRequest_created instance and call something like InspectMe or object_walker and see what’s available. You might find that the requested namespace, class and instance_name are available, in which case you could implement your own approval process per state machine
@pemcg Okay, thanks! Just thought there would be an easier way to do it since automation is available from the button process dropdown:
That could work...
Thank you for the info for now :)
@zigaSRC This might be useful if you haven’t seen it already: https://pemcg.gitbooks.io/mastering-automation-in-cloudforms-4-2-and-manage/content/ways_of_entering_automate/chapter.html