[14:01:37] <pilhuhn> We know the basics
[14:01:49] <pilhuhn> now we need to figure out how to bundle that with -services
[14:02:10] <pilhuhn> and how we can trigger via operation (or whatever) the start of a server.
[14:02:21] <pilhuhn> we may need to get credentials from MiQ
[14:03:01] <pilhuhn> for the first round we can assume that the server is already in instrumented and in inventory.
[14:03:04] <pilhuhn> but instrumenting
[14:03:44] <pilhuhn> and in a later step finding it, can not assume we know about it
[14:03:55] <pilhuhn> so in this case we may get a hostname + credentials
[14:04:37] <mazz> is there a JIRA on this?
[14:04:55] <pilhuhn> there is a card in Trello But I can create a jira
[14:05:44] <mazz> i prefer JIRAs to exist for specific agent features to be added.
[14:06:09] <mazz> are you saying we want to use ansible for the "start a server that is in inventory"
[14:06:31] <pilhuhn> I'll add a general hawkular jira. I feel that the agent does not play into this too much
[14:06:40] <mazz> in other words, ansible is going to be our start mechanism
[14:06:44] <pilhuhn> yes
[14:06:54] <mazz> ok
[14:06:55] <pilhuhn> discovery + instrument + start
[14:07:07] <pilhuhn> at least this is what we need to prototype
[14:07:14] <pilhuhn> we know that it can work on its own
[14:07:18] <pilhuhn> you have shown that
[14:07:28] <mazz> right
[14:08:07] <pilhuhn> how the question is on how to trigger that from h-services on behalf of a user (in MiQ)
[14:08:33] <pilhuhn> e.g. operation on server level (or rest call or ...) + calling ansible from there with the right parameters
[14:08:34] <mazz> smells like a new JSON request/response over cmdgw
[14:08:58] <pilhuhn> remember that ansible can query apis to get information and does not require that in files

(Trello: OPR-001 POC)