@zblanco I had run into same issues with trucking demo service. Once the cluster is up you can't really have one service start up another (e.g. Storm depends on Zookeeper. But if Zookeeper is down, starting storm will not start zookeeper automatically).
Best you can do is to declare start dependencies for your components so that when user clicks "Start all services" (or does fresh install), the components are started in the right order (e.g. zookeeper first then storm then trucking demo). To do this you would need to modify the role_command_order.json where these dependencies are managed. Note that in Ambari 2.2 and earlier this was defined at the stack level (e.g. /var/lib/ambari-server/resources/stacks/HDP/<version>/role_command_order.json) so you could not override it from within your service code. But in Ambari 2.3 onwards you can override this at the service level itself (see AMBARI-9363)
Simple example of how to do this can be seen in the instructions for doing fresh install of demo Solr service, where we are asking user to modify this file prior to install to declare a dependency of Solr on zookeeper (to ensure Solr is started after zookeeper during install):
https://github.com/abajwa-hw/solr-stack#option-2-automated-deployment-of-fresh-cluster-via-blueprint
Long story short: best option is to update the role_command_order.json, (restart ambari-server) and then have end users use "Start all" to start components in correct order (note: if you don't want to start a specific service, stop it and put it in maintenance mode and it should remain down)
