The Details page provides deployment details for each deployment that you submit when Deploying an Application.
Accessing Deployment Details
Once deployed, you can access the Deployment Details page in one of two ways:
From the Deployments list page, by clicking on the deployment name as highlighted in the following screenshot:
From the Virtual Machines list page, by clicking on the deployment button as highlighted in the following screenshot:
Either way, you see the Details page as shown in the following screenshot:
The Details page has three sections:
The Topology Panel (right)
The Main Panel (left)
The App logo, state (stopped, running, suspended, etc.), favorites star, deployment name, access link (when applicable), and the job actions dropdown menu are included in the top part of this section.
Click on the job actions dropdown icon to display a menu as visible in the following screenshot – the list of available actions vary based on the current job state.
The suspend operation is not available for pure container or hybrid applications.
The application name, environment name, and cloud region are listed in the lower left section and the truncated names expand on hover as displayed in the following screenshot:
The run time, approx cost (hourly compute charges, projected monthly cost factoring in suspension policy savings, and on hover, the following details as well: projected monthly cost before savings from suspension policy and monthly savings - see figure below), accrued cost (since the job started), deployment owner are listed in the right side of this section. The following screenshot displays the cost factoring details.
The Main Panel
The Main panel has the following subsections:
The Tiers Tab
The Job Details Tab
The History Tab
The Tiers Tab
The Tiers Tab contains a list of per-tier sub-panels:
Up to 5 tiers display initially in the expanded mode (showing the tier header and tier main section). If more tiers exist a Load more button allows you to load 10 more tiers at a time. You can compress/expand each tier by clicking the triangular icon.
The displayed information differs for VM-based tiers and container-based tiers.
The following screenshot displays a VM-based tier.
Tier Header: Service logo, tier state (running, starting, etc.), tier name, approx cost (hourly compute charges, projected monthly cost factoring in suspension policy savings, on hover: projected monthly cost before savings and suspension policy.
Bulk actions are supported on VMs – you can select multiple VMs and perform the action from a menu that appears on the top right corner of the table.
Search VMs using keywords.
Load More: Initially 5 VMs are loaded. You can click Load More to load 5 more VMs or the remaining VMs if this number is less than 5.
The scaling actions dropdown is only present for tiers that scale when the tier is in the running state.
Click the dropdown icon to the right of the tier state to display and select from the available choices for each tier as described in the following table:
Both batch actions or single actions are available to terminate VMs.
Scaling Action Description
Add a VM
If you click Add a VM the system automatically adds one additional VM without any further dialog. The alternate choice is to add multiple VMs as explained in the next row in this table. The following screenshot displays the scaling action location and only displays 1 VM running.
The following screenshot displays the second VM added after clicking the Add a VM option. The status message indicates the VM being added and the running VM count increases by one after the VM is successfully added.
Add Multiple VMs
The dialog box displays a range of VMs that you can add. Enter value and click Apply. The following screenshot displays the subsequent screenshot.
The maximum number of VMs allowed for scale up is based on the maxNodes set for a tier when you model the application.
Remove Multiple VMs
The dialog box displays a range of VMs that you can remove. Enter the value and click Apply.
The minimum number of VMs allowed for scale down is based on minNodes set for a tier when you model the application.
Tier Main Section: For each tier, the main section contains tabs for VMs and Details.
The VMs Tab
The VMs page is divided into sections with self explanatory filters and status details.
The Status buttons display the VM count in a certain state. The buttons are displayed based on the state of VMs (running, stopped, terminated, error, and so forth) in the tier.
The list of VMs details in a tier along with additional information when you hover over most fields. For example, hovering over the IP addresses entry displays a balloon with specific IP addresses as displayed in the following screenshot.
Click the VM name to open a new tab showing VM details.
Click the dropdown icon next to the VNC link to display the VM actions dropdown menu. The list of actions depends on the current VM state as displayed in the following screenshot.
Click the View Task Logs to view a pop up window with the task log messages for that VM in reverse chronological order as as displayed in the following screenshot.
You can select all or some of the VMs in the list using check boxes to the left of each VM entry.
Click on at least one checkbox to view the dropdown menu icon to appear above the list of VMs and to the right as shown in the following screenshot.
Click the dropdown icon to display the VM actions menu applicable to the least common denominator of all VMs selected. The VM action menu corresponding to the one selected error state VM is shown in the following screenshot.
If there are no actions available for a particular VM, than there will not be an actions dropdown available.
The VM Details Tab
This tab contains basic information about the tier such as start time, stop time (if the tier has terminated), current policy settings and tags, and deployment parameters.
If enabled in the deployment environment at the time of deployment, you have the ability to update policy settings and tags. The following screenshot is an example.
Hover over the scaling policy's info icon to view the info balloon displayed in the following screenshot.
You can change or remove an existing scaling policy or add one, if none is set, by clicking the dropdown menu icon next to the scaling policy label as displayed in the following screenshot.
The Change Policy option displays a new dropdown list as displayed in the following screenshot that shows all available scaling policies for this tier based on restriction specified in the application profile's Topology Modeler tab.
Select a policy and click Apply to replace the old policy with a new one.
You can add/remove security policies or tags for a tier by clicking the corresponding Edit link as displayed in the following screenshot.
Container-based tiers differ based on the number of containers per pod.
The following screenshot displays a single container per pod.
The tier header details are the same as the VM-based tier header except for the following factors:
In Approx cost, the projected monthly cost does not factor in suspension policy savings because suspension policies cannot be applied to containerized tiers.
In the Scaling actions dropdown, units are replicas, not VMs.
The main section contains tabs for Replicas and Tier details.
A placement group is represented by a rectangle that you add to the topology modeler canvas by clicking the Create A Group button. See Resource Placement and Validation > Container-Specific Resource Placement for additional details.
The Replicas Tab
The Replicas tab contains the following details:
The Status buttons display the replica count in a certain state. The buttons are displayed based on the state of replica state (running, stopped, terminated, error, and so forth) in the tier.
The list of replica details in a tier along with additional information when you hover over most fields. For example, hovering over the number of parameters provides additional parameter details as displayed in the following screenshot.
The Container Details Tab
The container tier details tab is similar to the VM tier details tab with the following exceptions.
There are no scaling policies for container tiers.
For Kubernetes container tiers, the namespace, and IP addresses and internal endpoints related to the ClusterIP, NodePort and LoadBalancer service types in the tier are listed. See the following screenshot for an example.
The Details Tab
General Information about deployment, for example, Approval/Start time and so forth are listed in the Details tab. This tab also contains actions related to Aging/Suspension/Security Policies (Remove/Change/Add) along with Tags, Global Parameters, and Metadata information. See the Policies section for additional details.
The History Tab
A list of all job state changes and policy changes since the job was deployed, in reverse chronological order are listed in the History tab.
Besides viewing the details on this page, you can perform the following actions:
Click the magnifying glass icon in the upper right to filter the list to entries that contain the text in the filter.
Click the download icon in the upper right to download the complete history as a CSV file.
The History tab provides details on actions taken or incidents that occurred during the life of this deployment. You can download the details on this page to a CSV file.
The Topology Panel
The Topology panel displays the application topology with status indicator lights (red, yellow, green) for each tier. Filter buttons appear above the topology diagram representing all tiers and tiers in various states: running, error. Click on a filter button includes only tiers in that state as displayed in the following screenshot.
|Indicator Color||Application Tier Status|
|Blinking Yellow||The application tier is in the pre-initialization state.|
|Blinking Green||The application tier is initializing.|
|Solid Green||The application tier is up and running.|
|Solid Red||The application tier has an error.|
For all actions, notifications are displayed at the top of the page. Three types of notifications are displayed in the details page:
In Progress – stays on the page during the action.
Success – stays for 7 seconds.
Error – you must specifically acknowledge this notification.
Three or more notifications of the same type are grouped together and you can click View Details to see details for this group.
- No labels