1. Status of Cloud Accounting and future plans
Greg Corbett, Adrian Coveney and Carlos Fernandez
Repository:
Portal:

2. Current status APEL accounts for: And groups the usage by
Duration (Wall and CPU), Network traffic, Memory and Disk
And groups the usage by
Site and CloudComputeService
Month and Year
GlobalUserName, VO, VOGroup and VORole,
Status, CloudType, Image and CpuCount
BenchmarkType and Benchmark
Data and views shown in the Accounting Portal

3. Upcoming Fixes and Changes
CpuCount summaries conflicting in repository and portal when they only differ by CpuCount
Server side issue, fixed in patch applied this week
Portal will need to update their schema as well
Usage gets assigned to the month the VM was started in
Server side design limitation, changed in pending release – upgrade scheduled for w/c 26th March
Minor portal changes implemented in the devel-next instance
Portal upgrades dependant on Portal effort available

4. Other Issues What does CpuDuration mean?
caso 1.1.1: CpuDuration = WallDuration * CpuCount
oneacct-export 0.4.6: CpuDuration = WallDuration
Some suspended states still use resources and hence should be accounted for, currently we don’t propagate SuspendDuration to the portal
Benchmark and Network fields unused

5. Upcoming and Future Work
Upgrade Central server to and then 1.7.0
providing support for Long Running VMs
Add RecordCreateTime to usage record (V0.5?)
Simplifies Long Running VM logic
Add ‘Accelerators in Cloud Accounting’ fields to usage record (V0.6?)
Add support for Block storage and IP as separate usage records
Incorporate pricing information

6. Accelerators in Cloud Accounting
Some work already conducted with Viet
Draft additions to the cloud usage record suggested
Viet modified caso to support these new fields
APEL developed support for loading these new fields into the database and summarising them.
Pipeline of Site sending usage record to APEL and then APEL summarising not tested.

7. Accelerators in Cloud Accounting
Usage Record Property
Type
Null
Definition
AcceleratorCount
decimal No
A count of the Accelerators attached to the VM.
AcceleratorProcessors
int(11)
Total number of cores
AcceleratorDuration
Yes
Actual usage duration of the Accelerator (in case some systems could report actual usage).
AcceleratorWallDuration
Connected time
AcceleratorBenchmarkType
varchar(255)
Name of benchmark used for normalization of times
AcceleratorBenchmark
Value of benchmark of Accelerator
AcceleratorType  ?

8. Block Storage and IP Accounting
Site requirements need to be collected
Then a draft schema can be produced
APEL, caso and oneacct can then develop support of this
Testing
Questions
Separate usage record with related Cloud fields?
Summarise by related Cloud fields so Cloud-Block Storage/IP summaries match up 1 to 1?

9. Pricing Information Follow the grid model?
Rates for time are stored against the site in GOCDB.
Transparent to collectors/repository
Dedicated views and reports in the Portal turn time into euros as a metric.
If cloud sites are distinct from grid sites in GOCDB then they can decide their own rates
If a site has grid and cloud under the same GOCDB then they'd have to agree on a common rate for grid and cloud.
Alternatively we could add and extra parameter to GOCDB for the rate for  cloud-walltime.

10. Other Work (outside FedCloud)
SSM Support for
IPv6
Ubuntu
Argo Messaging Service
Accounting of Containers for Sea DataCloud, with data being stored and aggregated in an Elastic Search Cluster

11. Any questions?