1. What is the nature and description of the request?

Currently, we need to run systemctl command to manage AAP services:

systemctl --user stop automation-gateway*
systemctl --user stop automation-eda*
systemctl --user stop automation-controller*
systemctl --user stop automation-hub*
systemctl --user stop redis-*
systemctl --user stop receptor
systemctl --user stop postgresql 

Since controlling all these services manually is tedious, it's more rational to have a single parent systemd target file. It would be great if we have "aap-services.target" systemd target file to manage all AAP related services like "automation-controller-service" command in RPM installation.

1. Why does the customer need this? (List the business requirements here)

For the containerized version, an efficient method for managing these services has not yet been established, so we anticipate significant potential customer demand.

1. How would you like to achieve this? (List the functional requirements here)

I think I can achieve this to put single aap-services.target file like this:

# aap-services.target[Unit]
Description=AAP Services Group

[Install]
WantedBy=default.target 

Then put single line for all of systemd unit files for AAP:

PartOf=aap-services.target 

1. List any affected known dependencies: Doc, UI etc..
   Docs, Installer

1. Github Link if any
   WIP