95th Resolution Approach
Important:The product name for this user guide has changed from Foundation and Cloudscape to Business Service Discovery and Migration Planning. Previous UI pages known as Foundation have changed to Business Service Discovery. Previous UI pages known as CloudScape have changed to Migration Planning.
This approach utilizes the RSG-95th Highly Connected Stack. By running the auto-generation of application stacks with the 95th Percentile option selected, you will generate a group called RSG-95th Highly Connected Stack – which will be a small subset of heavily connected nodes.
| • | Step One: Review and Disposition Each Host in the 95th Group |
| • | Step Two: Create a New Application Stack |
| • | Step Three: Re-Run the Auto Generate Groups Algorithm Without the 95th Group |
Step One: Review and Disposition Each Host in the 95th Group
Review and disposition each host in the 95th Group… “What is this host used for?”. Typically, you will have knowledge of these hosts since they are so heavily connected. You should disposition each host within the group into one of two categories:
| • | Services—These would be hosts that are offering a service to the rest of your environment. We have attempted to capture some of these in our RISC Service Group(s) such as exchange, Citrix, NFS, etc, but we have not scripted for every service that can be offered. Something like antivirus, authentication, logging, etc. would be examples of services. To disposition a Service, create a new application stack (antivirus for example). Once this is complete move that host by right clicking the host and selecting Edit Stack Membership. |
| • | Application Stacks—These would be hosts that are a part of an application stack. These could be things like a shared DB. There are two ways to disposition a member of an application stack. For environments with heavily shared architectures (think large jboss layers or large shared DBs) proceed to Step Two, otherwise disposition Application Stacks by simply leaving them in the 95th Group and proceeding to step two. |
Step Two: Create a New Application Stack
Important:This is only for environments with heavily shared architectures as noted in Step One: Review and Disposition Each Host in the 95th Group; otherwise skip this step.
Create a new application stack (Shared DB for example). Move the server(s) that are part of that cluster (or it might just be a single db server) into the new application stack you just created.
You can immediately view the connections of that application stack and see where that server or cluster is communicating. You would likely see other AutoApp-xxx stacks. If this communication is important (such as DB traffic), it is an indication that these application stacks are likely front ends running off of the DB. If the DB is shared, you can leave it there, and rename the front end groups (e.g. AutoApp-xxx becomes Main SAP FrontEnd) or you can move the servers from AutoApp-xxx into the new group you built for the server(s) you pulled from the 95th group.
You repeat this process until the 95th group is empty. If you want to do a second round, you can re-run the auto-grouping and select the 95th group again. Since the original top 5% were grouped into Application Stacks, a new set of top 5% hosts will be identified and included in the 95th group, and can now be rationalized and grouped using the same methods as in Step One: Review and Disposition Each Host in the 95th Group.
This approach is very effective in environments with heavily shared architectures (think large jboss layers or shared DBs).
Step Three: Re-Run the Auto Generate Groups Algorithm Without the 95th Group
Re-run the Auto Generate Groups algorithm without the 95th group. This will place any remaining workloads, not in a saved or confirmed Application Stack, into an AutoApp_XXX stack based on connectivity. Proceed to the Visualization and Movement Approach.
Note:Any application stacks not saved or confirmed upon re-execution of the algorithm will be deleted and rebuilt. Only those Application Stacks that have been saved or confirmed will remain intact.