IBM Carbon UI Framework for Parking Policies
IBM Carbon is developed in the React UI that creates a unified and intuitive user experience across all the IBM Products. It enables Turbonomic to bring in the essence of all UI improvements (New features, Performance enhancements..)
All of the IBM Turbonomic users will be able to use these features and experience the improvements listed below.
- New UI features like Filters, Widgets, Workflow wizards…
- Improved UI elements rendering speed
- Reducing the screen time towards an event or a task completion
What's New?
- Parking Policies and Schedules will be available in the IBM Carbon UX framework
- Additional features & Improvements available in the new UI, that inherits following Carbon UX benefits
Carbon UX benefits
- Light/dark mode support
- Faster time to develop new features
- New components added that can be used instead of being newly developed
- Accessibility primitives to help build more accessible experiences as early as possible to the development process
- Faster load times due to smaller bundle sizes
- New components added that can be used to build off instead of being newly developed
- Accessibility primitives to help build more accessible experiences as early as possible in the development process
How to enable this?
These features are enabled for all IBM Turbonomic customers from Versions 8.15.5 (Parking Policies) & 8.15.6** planned (Parking Schedules), by default
How to use? Feature Introduction & Improvements
Parking Policy Wizard: Identifying the scope of parking resources, leads to automation at scale (Single View with Tabbed navigation)
Single view of multiple policy levels
- All – Total Parking Policies (Across levels)
- Global – Global Scope***
- Cloud Provider – CSP level (AWS/ Azure/GCP)***
- Account – Within a CSP account/subscription***
- Resource Group – Azure only***
Tabbed navigation across levels
- Quick review on all the policies & their priorities
- Easy navigation across policies, to their details
- Review and manage the precedence within levels
New Filters with RegEx Options (Extended from the Parking Landing page UI)
Benefits:
- To Identify results on pattern-based matching inside the Parking policy filters
- This is the extension of filters available in the Parking UI page, to accelerate the search function
- Tags Existence check. To find the workloads which has a specific Tag (Key) without any Value to it
Use Case: For workloads with "Tags" Key & without values assigned to it
Apply the “Unparkable” Parking policy on the resources in my CSP which has the Tag with No values assigned. To restrict applying parking schedules and taking manual parking actions.
Workloads from Unparkable policies with Tag Key "Application" with no Value
Value: Helps to Organize workloads those aren't properly being tagged in the cloud environments and operationalize the tagging policies
Parking Policy Workflow: Precedence of Levels and Priorities
Goal: Executing the automation of Parking actions at scale across teams within an Organization
Managing Policy Precedence & Priority:
Precedence in their levels: Order in which the parking policies will be assessed and executed
- Low > Medium > High > Highest being the flow of Levels inside Parking policy Workflow, where Highest supersede other levels
- Scope determination between levels:
- Scope of workloads resulting within every level remain in their visibility
- Workloads not in the scope of Highest precedence level will be taken into the scope under the immediate next lower precedence level
- Parking schedules will be enforced to the effective & scoped workloads in their order of precedence
Priority falls within every level: It determines the order in which the policy within every level that will be executed
- The workloads scope within the policy works, like the scope determination between levels
- They are executed in the order from top (numbered 1) to bottom (max number) in case of multiple policies that exist within every level
Use Case Example: Parking Policy – Creation and Enforcement
Automate Parking actions for my Virtual machine (Datadog) Workloads that belongs to my Azure Development accounts
Expected Result: Automate the enforcement of Parking schedule to all the Datadog VMs that falls under the Azure Development account. Any changes to the VMs being discovered progressively, gets updated by the Parking policy engine every 10 mins
Selective accounts: Dev
Actual Results:
- The policy created could be seen under the “Account” level with the “Priority = 1” as there are no other policies in that level
- Policy engine refresh the rules and enforce schedule to the workloads in its scope for every 10 minutes. This includes,
- Scope of workloads refreshed based on the recent discovery cycle
- Policy priority changes refreshed if there are multiple policies exist in same level & between levels
Cost$ Savings: Realized
- Cloud Widget: Cumulative Savings scoped on the workloads, time period
- Group by action type, provides the parking driven savings (Action type: Suspend (includes Node & VM Suspend actions from Turbonomic Action Center as well)
- Download the report to validate the savings by individual Parking specific actions
- Scope: To be changes to workloads specific to your environment (say, Groups, Entity Types..)
- Timeframe: Specific time period where the Parking actions were taken
- Action Type: Grouping by "Suspend" action type
What's Next?
Turbonomic version should be upgraded to 8.15.5 & above to use these features, help increasing user experience and improve Parking policies adoption
You can download a 30-day free trial today or meet with an expert and discover how Turbonomic can help continuously assure application performance at the optimal cost. Visit IBM.com/Turbonomic today and get started.
--- IBM Turbonomic Documentation (To know more about Migration of Policies & new UI Design)
https://www.ibm.com/docs/en/tarm/8.15.5?topic=notes-whats-new
--- For more feedback/Add Ideas..
