After spending sometime on this, I believe we should not remove the 'target' tab for any existing resources or deployed application.
Doing #1 is easy and that's how console plugin is designed.
Doing #2 is relatively easy, as there is capability built in for filtering when generating the tree node.
I am recommending not to do #3 based on the following reasons. Note that #3 was not requested during the planning meeting.
1. This target tabs is NOT related to clustering management. It reflects what the resources or application is targeted. If there is no cluster/standalone instance created in the domain, this target tabs/info will never be shown to user.
2. If user is only using console, they will not see those tabs. The target tab will be there ONLY if the user really want to have cluster, they need to go through the trouble of creating and managing the cluster (since they can't see this cluster's config in console) in CLI, and then go back to the console to refer to it.
3. Removing this tab means console will not be able to show accurate info about the resource/applications. If the user is using CLI to create a cluster, deploy an application to that cluster, i am not sure how the console can show this correctly. Showing the application is deployed, but without this target info will be the exact UI for a DAS only domain, user will think that the application is deployed to DAS when in fact its not.
4. Too many pages UI and the logic behind this pages has to be modified. This is going to do more harm to the qualify of the console than removing them.
5. If the goal is to discourage user to use the clustering feature in GF 4.0, then the following should be enough.
a. no cluster / standalone instances/ nodes page appear in console
b. only server-config is shown.
c. do not allow user to target the cluster during application deployment and resource creation.