Script to generate rate limited (msg/sec) load
Finish architecture
Continuation of T/dT, U/dU reasoning
Describing charging dimensions
Rename Billing to Computational aspects and move after Architecture
Finishing (for now) the description of events
Add events modeling.
AquariumEvent and ResourceEvent.
Start describing events
Slight reorg (Implementation -> Domain Modeling).
1. Added terminology2. Moved stuff from the DSL description to the basic terminology3. Started using term `charging` instead of `billing`
More on architecture
Initial architecture blurb
Start describing billing-related stuff.
Split arhitecture in another file to avoid conflicts
More on billing
Bit of text rearrangement, billing descriptions
A great contribution to the paper.
Implementation experience
Some text on Aquarium requirements and benchmarking
Skeleton for the Aquarium architectural description
AMQP consumer enhancement/fixes
Add license header to remaining files
Lots of case study text
Minor changes to last paragraph
Remove duplicate case
Add credit use cases for a company
Now with correct policy definition
Text for the university test case
Skel for the university test case
Minor text changes
Staighten up accounting text
Split credit and debit DSLs
copyin() policy declaration stuff from the wiki
Document skeletons
Documentation template with sphinx
Change policy format to be more composable
UMLGraph-based E-R for basic entities
Example policy file