search

ansible / pinakes

Apache License 2.0
18 stars 2 forks source link

suggestions #534

Open euprogramador opened 2 years ago

euprogramador commented 2 years ago

I find the project interesting and very good to expose the automations in an easier way.

At some point do you intend to extend the current model to manage instances and their automations?

Let's say that the user requests the creation of a rhel machine, the creation would generate an item in the catalog that represents the created machine, and could have a specific menu where the user could trigger other specific automations for that item, such as restarting the machine , or other things...

What do you think of the idea?

eclarizio commented 2 years ago

@euprogramador I don't think this is something that the Pinakes project is meant to handle. We're directly connecting with Controller in order to run playbooks, and we aren't providing any of the automation, that's all handled within Controller. This allows us to stay general and not specifically care about what exactly the automation is doing, and managing instances I believe is a different space.

In theory, you could set up your example within Pinakes by using a product connected to a playbook that creates a RHEL machine, and then other products connected to a "restart machine" playbook, or other automation triggering playbooks that simply take in the IP address to know which machine to run the automation on. All that's missing there is a fancy specific menu to manage your RHEL machine.

I think what you're broadly asking for is outside the scope of this project, at least for the foreseeable future. However, we did have some other somewhat related future plans with setting up products that could be ran before and after a main product, as well as setting up products to be used as a "return order" product. So for example if you have a playbook that creates a VM, the "return order" product would be tied to a playbook that retires it.

sean-m-sullivan commented 2 years ago

It is possible to setup a template or workflow to input the name of the machine in the survey, and if your initial order playbook refreshed the inventory after creation, they could then use another order to do the acting. So this is possible with the current Pinakes, you just need to make sure the jobs are setup to do so. :)