8000 VM charging · Issue #162 · southampton/cortex · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Apr 23, 2024. It is now read-only.

VM charging #162

Open
claytonpeters opened this issue Feb 23, 2018 · 4 comments
Open

VM charging #162

claytonpeters opened this issue Feb 23, 2018 · 4 comments

Comments

@claytonpeters
Copy link
Contributor

Update Standard VM process to have mandatory fields for:

  • Owner (i.e. username)
  • Owner Role (i.e. ESD Member, Researcher in ORC)
  • Secondary Owner (i.e. username)
  • Secondary Owner Role (i.e. ESD Manager, Researchers Supervisor)
  • Expire without Power Off - Mark a system as expired (i.e. no longer paid for), but do not shut it down (useful for infrastructure servers)
  • Cost Code
  • Modifiable Cost (in case we've made a deal for some reason)

For charges, it might be worth having an additional table which has the fields:

  • id, system_id, cost_code, date, cost, notes
    So that a system can have multiple charges made against it (e.g. original purchase for 1 year; add 500gb disk for a year; renew everything for 4 years)
@claytonpeters
Copy link
Contributor Author

In an ideal world, this might poke some API to do the charging.

We'll probably want some view somewhere to view the list of charges for a VM

We also need to update the costs, and probably make this configurable.

@jakemalley
Copy link
Contributor

Do you think the "Owner" field is different to the "built for" field we were discussing today?

8000

@claytonpeters
Copy link
Contributor Author
claytonpeters commented Sep 4, 2018 via email

@jakemalley
Copy link
Contributor

All of the following already implemented in v4:

  • Owner (i.e. username)
  • Owner Role (i.e. ESD Member, Researcher in ORC)
  • Secondary Owner (i.e. username)
  • Secondary Owner Role (i.e. ESD Manager, Researchers Supervisor)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants
0