Dashboard and Menus
When you first login to Workload Manager, you are directed to the main dashboard with the main menu tabs on the left side of the screen. The dashboard and menu tabs you see will vary depending upon the groups and roles your user account is associated with. See OOB Groups, Roles, and Permissions for more context.
The main dashboard summarizes information about your deployments and imported VMs. In addition, if your user account includes the WM_ADMIN role, the dashboard will let you display information about the deployments and imported VMs for all users in your tenant.
The main dashboard has five dashlets:
Summary: This shows total cloud costs and VM hours for the past 30 days and the count of currently running VMs. If you are logged in as an administrator, there is dropdown in the upper left of the dashlet that lets you toggle between data for just your own workloads or all workloads managed by users in your tenant. Toggle buttons in the upper right let you aggregate the data by cloud or application. Links in this dashlet point to more detailed cost and usage reports. See Reports Overview for more information on these reports.
My Plan Usage: This displays the name of the usage plan assigned to your user id. Usage plans restrict how much a user can spend on cloud resources in terms of a dollar amount or VM hours. Workload Manager includes a single out of box unlimited usage plan. As and administrator, you can create additional usage plans. (see Usage Plans and Fees for more details).
Cloud Status: Once you as an administrator have set up cloud regions in Workload Manager (see Clouds for details), the status of those cloud regions will be displayed here.
My Recent Deployments: Once you deploy applications, they will be listed here.
Favorite deployments: You can mark a deployment as a "favorite" via the deployments list page. See Virtual Machine Management for more details.
Notifications: When any important Workload Manager generated messages are produced, they are listed here.
The main menu has the following tabs:
Dashboard: This shows the main dashboard as described above.
App Profiles: This shows the Application Profiles page. From here, you can perform the following actions:
Create a multi-tiered application profile using the drag and drop topology modeler
Deploy an application to a particular deployment environment
Share your application profile with other users
Export and import application profiles
Jump to a list of all deployments associated with an application profile
Benchmark an application
Deployments: This shows the Deployments List page. From here, you can perform the following actions:
View summary information on each deployment (run time, costs)
Perform on-demand actions on a deployment (suspend, resume, terminate)
Drill down to details of a deployment and perform manual scaling of individual tiers and change which policies are applied to the deployment.
Virtual Machines: This shows the Virtual Machines List page. This page has tabs for managed VMs and unmanaged VMs:
Unmanaged VMs are VMs launched using one of the cloud accounts associated with you as a user, but which are not running the management agent. These are typically VMs you launched outside of Workload Manager. You can select any of these VMs and import them. When you do this, the management agent will be installed on the selected VMs and they will become managed VMs.
Managed VMs are VMs that are running the management agent. They include VMs that were formerly unmanaged and then imported, and VMs belonging to applications launched through Workload Manager. You can perform various OOB on-demand actions on these VMs (suspend, resume, terminate) as well as custom on-demand actions.
Environments (visible only to users with at least one of these roles: WM_ADMIN, WM_ENVIRONMENT_MANAGER): Displays the Deployment Environments list page. When you deploy an application, you do so by first selecting a deployment environment. The deployment environment describes what cloud regions an application can be deployed in, with which possible cloud accounts, and with which possible scaling, aging, suspension, and security policies. Administrators create, edit and delete deployment environments and share them with selected users.
Projects (visible only to users with at least one of these roles: WM_ADMIN, WM_PROJECT_MANAGER): Displays the list of projects created by you or shared with you. A project lets you manage the lifecycle of your application by specifying different phases. In each phase, the application will be deployed using the deployment environment and usage plan specified for the phase.
Services (visible only to users with at least one of these roles: WM_ADMIN, WM_SERVICE_MANAGER): Displays the Services List page. Services are the building blocks of multi-tier applications. Workload Manager comes with many OOB services, including VM-based, container-based, and external services. You can also create your own custom services here.
Benchmarks: Displays the list of benchmark test result reports for the application benchmark jobs that you specified and ran from the Application Profiles page.
Repositories: DIsplays the Repositories List page. Here you can add a repository location for storing scripts used by your application during its various lifecycle phases.
Policies (visible only to users with at least one of these roles: WM_ADMIN, WM_ENVIRONMENT_MANAGER): Displays the lists of policies organized by tabs. From here you can create, edit, share and delete policies. The five types of policies are as follows:
Event: Let's you define commands that are executed when a cloud region or a deployment changes state.
Scaling: Let's you define the conditions when a VM-based tier of a deployment will automatically scale up or scale down.
Aging: Let's you define a time limit or cost limit for a deployment, after which the deployment will be automatically terminated.
Suspension: Let's you define the time periods when the VM-based tiers of a deployment will be automatically suspended.
Security: Let's you define firewall rules that can be applied to a deployment as a whole or to particular tiers of a deployment.
Images (visible only to users with at least one of these roles: WM_ADMIN, WM_IMAGE_MANAGER): Displays the Images List page. This is a list of OS base images that are mapped to the actual cloud provider images for each cloud region. Workload Manager includes several OOB images. For many public cloud providers, Workload Manager automatically applies the appropriate mapping of these OOB logical images to cloud provider images. You must set up your own image mapping for private clouds. You can also add your own custom images.
Actions Library (visible only to users with at least one of these roles: WM_ADMIN, WM_DEV_OPS): Displays The Actions Library page which is where you can define and share custom actions of two types:
On-demand Actions. These action can be commands, scripts or invocations of web services. They are made available for use via dropdown menus in the pages where you can view deployment and VM status.
Lifecycle Actions. These action can be commands or scripts. They are made available for use via dropdown menus in the pages where you specify your application profiles and service definitions.
Admin (visible only to users with the WM_ADMIN role): Displays the administrator menu on the left side of the screen and the Clouds Page on the right side for the screen (see below).
The administrator menu has the following tabs:
Main Menu: Brings you back to the main menu on the left side of the screen and the main dashboard on the right side of the screen.
Clouds. This shows the clouds that have been configured for your tenant. From here, you can create, edit and delete clouds. A cloud requires at least one cloud account and at least one cloud region.
Cloud accounts are the cloud provider user credentials needed to launch instances in a cloud region
Cloud regions correspond to geographical regions for public clouds. Some private clouds can have multiple regions, but VMware vCenter clouds and Kubernetes container clouds only have one region. Cloud region parameters for VM-based clouds include the cloud API endpoint address, VM naming and IPAM scripts, storage types, instance types, image mappings, and lifecycle actions.
Extensions: Displays the Extensions List page list. From here you can add or edit one of the two supported extension types: ACI and ServiceNow.
All Reports: Brings you to the Usage Summary report. Using the dropdown next to the report name, you can also view these two other reports: Application Deployments and Running VM History.
System Tags: Displays the System Tags List page. Here you can add system tags, which are text strings, and share them with all subtenants. Once defined, a system tag can be associated with an application profile as a whole, a tier in an application profile, or a deployment environment.
Usage Plans: Displays the Usage Plans List page. A usage plan determines how much total cloud resources a user can consume. You can add plans that limit consumption based on cost or VM-hours. A usage plan, can refer to a bundle (see below). Usage plans are assigned to users through the Suite Admin UI.
Bundles: Displays the Bundles List page which is where you can define a limit on cloud consumption based on budgeted cost or VM-hours used. A bundle is not directly assigned to users. Instead, it may be assigned to a usage plan (see above) which is in turn can be assigned to a users.
- No labels