Organization of services

[VladoPortos]

Hi,

I'm still trying to wrap my head around the concept in Squest and mostly I get it, and I must say its great, somehow this does exactly what I wanted.

I just trying to wrap my head around how the catalogue should be organized...

For example VMs, this is clear, create "service" called "VMs" and add create action there that calls "create_vm" workflow... and I end up with instance representing the VM.

What if I want to install and manage software on that instance ? For example install nginx, we have flow that accept server name and install nginx there...

Is there an way to set this up, that I can install/uninstall or even restart "element" attached to instance.. this can be also for example docker container on VM....

Or do I think about it wrong ?

[Sispheor]

That's a day 2 operation. An "update" kind of operation.

[VladoPortos]

Ah I see, however from what i just tested when I perform "update" operation it does not track it as an "item" for that instance right ? Like I would have update operation that would be called "add app" and it would ask for app name, or from pre defined list and go and installs it... I do not see that app mentioned in the instance I executed the update operation on. I assume its more of along do an OS update and such.

Maybe I could have separate service catalogue for apps only and track it via that ?

Sorry if I sound dumb, just don't have anybody to ask about it :D and maybe I'm trying to achieve something in place that is not meant for it.

[Sispheor]

If it's an update operation it's not going to add an item in instance list. The idea is that your playbook update the squest instance with a json that contains for example the list of installed apps.

[VladoPortos]

Ah I have seen the call back API in documentation, I'll have a look at it. Thanks.