| Info |
|---|
CloudAware Application is a logical unit that allows to organize your resources according to a naming convention or a tag of your choice, or any other custom logic you customers wish to apply. |
CloudAware Applications may be created to distinguish:
Department, Team, Site, Project within your enterpriseorganization
Customers, if you 're are an MSP
Purchasers, if you 're are a reseller, etc
Creating a Cloudaware application also makes sense in such cases when, for example, :
1) there are AWS, /Azure/GCE and Physical servers in your Cloudaware environment and you need to provide access to view AWS data only, or ;
2) only 1 one specific AWS instance should be available for the application user, etc. Note
Note that the sooner you create the application, the better since billing and cost data is not retrospective - it may be collected and shown in the app a Cloudaware application only starting the day when the application was created.
...
Multi-cloud and non-cloud support
Cascades give you provide the ability to attach object hierarchies by attaching a single object
Inventory automation using auto-attachment rules
Ability The ability to attach objects that are not taggable or exceed the tag limit.
Prerequisites
Think of the assets resources that should be attached to the application you will be working on. You may create a list view showing running AWS instances, for exampleCloudaware application. Consider the logic that can be used for attaching assets in question to different tiers of the application.
Application Creation
1. Log in to your Cloudaware account. Locate the section CLOUDAWARE in Navigator → Applications.
...
6. Locate the resources in question on a list view, e.g. Running Instances. Check the boxes and click Attach To The Application.
...
7. You will be offered to select Select the appropriate application and a tier. Review the objects that will be attached and click Attach.
If you can't attach one or few of the selected objects to a selected tier or see a warning like below , it may mean that these pops up, one or several selected objects are already attached to another application:
...
You can continue Continue OR if it is preferable, you can detach them clicking Detach Objects.
...
Consistency is one of the main challenges you customers face when you try to be organized. Once managing their cloud and non-cloud environment. One of the best practices is to follow relationships between objects and use these relationships to get consistent and auto-updatable inventory.
Cloudaware applications support cascades. This means that , meaning that all related objects will be cascadingly attached once a resource is attached to the application, all related objects will be cascadingly attached as well. For example, once you attach an AWS EC2 Instance, all related corresponding EBS Volumes or Network Interfaces will also be attached.
When choosing what selecting an object to attach to a Cloudaware application, check if there is another object is above it in the hierarchy that can cascadingly attach itbe connected first. For example, it's better to attach an AWS ELB Load Balancer than its related instances, it's better to attach a AWS Elastic Beanstalk Application than a AWS Elastic Beanstalk Environment, and it’s it's always better to attach URLs.
Try to minimize manual attachments. When you manually attach somethingFor example, there is a logic for choosing an objects behind it. It's much better to implement selecting objects that need to be attached to a specific application. Implementing that logic in an auto-attachment process , is much better because Cloudaware will keep track of new objects assets that comply with your the defined logic. If you still need to attach something by hand, try to add some objects manually, attach only truly static resources.
...
Auto-Attachment Processes
Cascades The cascades are good sound, but they only work for big extensive services with lots of many interconnected objects. What would you should one do with all objects that have no relationships with each other? The answer is to implement the process that will monitor your assets and , automatically validate them against defined rules, and choose the application accordingly. These are auto-attachment rules.
Cloudaware application auto-attachment rules are are based on on Salesforce Workflow Rule functionality functionality. A workflow rule is like an IF/THEN statement. IF part of the statement is called criteria, THEN part of the statement is called actions. The For example, the simplest of workflows will check for a specific values value on an object and then update the 'Application Tier Client Name' field on it with a specific particular value. The value should be set to the applications application tier's name.
Note that 'Application Tier Client Name' consists of 2 parts: Application name and Application Tier name for example: AWS - Production (see the example below).
...
6. Click Activate to activate your workflow.
The object Objects will be automatically attached to an the appropriate application within 1 hour.
...
Attachment Logic Examples
if
Namestarts withprod, set Tier Name to"The Application - The Tier"if
tag:CustomerequalsCustomerAset , set Tier Name to"The Customer App - The Tier"if
tag:Applicationis not empty andtag:Tieris not empty, set Tier Name totag:Application+" - "+tag:Tier
You Customers can create even more complicated auto-attachment rules combining workflow rules with formula fields or with formula fields or even updating them via API from an external system. Almost any complicated complex object classification logic is possible using workflows and formulas.
Object Re-
...
Attachment After Application Tier Client Name Change
If the Application Tier Client Name is changed, objects will be re-attached in in 1 hour hour. However, there may be a delay in jobs delays are possible if a customer didndoesn't log in to their Cloudaware account for some time.