Project
Each of your service resources (e.g. individual virtual machines) can be tagged with a 'Project' categorisation. This categorisation is optional, but enables CloudCreator reports to answer questions such as:
- How much did the resources consumed by each project cost last month?
- What projects does CloudCreator believe will spend more this month, than last month?
Topics
Using Project Codes for Financial Governance
A use case for Project Codes is for financial governance of a project that spans two clouds.
Use Case:
- You have a project called 'MigrateSystemX'.
- The purpose is to migrate an existing system named 'X' from vCloud Standard to public Azure.
- You want to monitor the costs before, during and after the migration.
Project Codes can help you do this in the following ways:
Project Stage |
Action / Benefit |
Before |
In CloudCreator, add the Project code 'MigrateSystemX' to all vCloud Standard resources associated with system 'X'.
The next morning:
|
During |
As new resources associated with the project are created in public Azure, add the Project code 'MigrateSystemX' to them. See How Each Service Applies Project Codes below.
The next morning:
|
After |
Post 'go-live' of the Azure system, and after you have decommissioned the vCloud Standard resources, running the same report will show just the ongoing Azure costs.
Filtering the CloudCreator dashboards by the Project Code 'MigrateSystemX' will show the system 'X' costs 'before', 'during' and 'after' the project, as shown here:
|
How Each Service Applies Project Codes
Project codes are applied at the resource level. The method differs by service, as described below.
Service | Description |
NZ Services |
For New Zealand hosted services (excluding Azure Stack), each resource can be assigned a project code inside CloudCreator.
|
AWS (offshore) |
AWS provides a 'tag' feature that lets you store your own 'attribute' information against each resource. This is the best place to store project information.
Early each day CloudCreator loads resource tags with the key ‘Project’.
Note:
|
Azure (offshore) Azure Stack |
Azure and Azure Stack provide a 'tag' feature that lets you store your own 'attribute' information against each resource. For public cloud services, this is the best place to store project information.
Currently CloudCreator only loads tags from Azure (offshore). Next, CloudCreator will load tags from Azure Stack.
Early each day CloudCreator loads resource tags with the key 'Project'.
Note:
|