Hi, I'm trying to design a generic service as a template for the most apps we run across our environment. Unfortunately we aren't able to manage nor decide what procedures or methods they use to manage their applications. Our company is organised as many other companies in several departments and teams/groups which in charge get infrastructure service from our team. The point is, we are mainly responsible for Solaris and every stuff directly related to it like the smf manifests but the other teams provide the most scripts. Surely they have to manage upgrades and maintenance tasks to their apps which in turn might change the scripts. This is the point where we sometimes run in trouble because the are failing to start after this. Many times are simple errors the cause of the failure and many other times are technicians with less (or none) know how changing parameters they better don't. The focus of my post is to ask if there is a possibility to add an hash like md5 or even any other signature to ensure the originality of external start/stop procedures within a service. We manage to allow other teams to start, refresh and stop their services without our intervention (action_authorization) but we need a mechanism to force the originality of such external procedures because we check them before the service is imported. Any suggestions?
Cheers rsantos This message posted from opensolaris.org
