Juju resource map
Provider-agnostic descriptions of what a given cloud provides, intersects with constraints
== Comment ==
This has been re-targeted for uds-r. Is there expected different outcome from the session held at uds-q? -- Daviey
Blueprint information
- Status:
- Complete
- Approver:
- Robbie Williamson
- Priority:
- Undefined
- Drafter:
- Ubuntu Server
- Direction:
- Needs approval
- Assignee:
- William Reade
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Antonio Rosales
Related branches
Whiteboard
Etherpad from discussion at UDS-Q:
ACTIONS:
- Propose format/features to juju mailing list
We have a simple/beautiful way to map what images exist in EC2, but it's specific to EC2
- https:/
- currently we hardcode a lot of data, we want to extend this for other providers and even private clouds
The problem to solve:
- You want a platform-agnostic charm, but the charm will have some requirements (say, kernel version/package version/network support)
- but we have no way of knowing which providers provide those resources via API queries at the moment
- Resource map is the solution, but many providers
== Resources we are mapping ==
* cpu
- "what is a cpu?" or core?
- "# Cores" or "# of concurrent threads" ?
- ECU is a rough measurement that is at least repeatable, "CPU" is harder to define.
* ram
- kind/speed of memory?
- swap amount? (some providers have 0 swap, eg older OpenVZ)
* storage
* cost
- instance cost is clear usually (flat price per hour)
- spot instances, etc mess with this though
- bandwidth costs? (often on sliding scales...)
- storage costs?
- can get very thorny and JuJu will have no way of knowing the precise marginal cost
* HVM?
* GPU
- is there an "ECU" equivalent for GPUs?
* EBS
* software-level stuff (Ubuntu version etc)
== Current Python expression for EC2 ==
_InstanceType = namedtuple(
INSTANCE_TYPES = {
# t1.micro cpu is "up to 2", but in practice "very little"
"t1.micro": _InstanceType(
"m1.small": _InstanceType(
"m1.medium": _InstanceType(
"m1.large": _InstanceType(
"m1.xlarge": _InstanceType(
"m2.xlarge": _InstanceType(
"m2.2xlarge": _InstanceType(
"m2.4xlarge": _InstanceType(
"c1.medium": _InstanceType(
"c1.xlarge": _InstanceType(
"cc1.4xlarge": _InstanceType(
"cc2.8xlarge": _InstanceType(
# also has fancy GPUs we can't currently describe
"cg1.4xlarge": _InstanceType(
== Desire ==
User/third party can provide thier own resource maps as well
- needed for custom charms and private clouds, eg you could have an arbitrary resource like "secure machines in my data center"
Resource map as a file downloaded from a URL
- make an extensible file format (eg YAML) and allow user to provide his own extensions to the resource map (eg to describe his private cloud, or describe new resources he cares about)
- would be nice to have user-provided custom URL (or rather additional URLs) to give new information/
== API ==
- It would be nice if we could build the resource map by querying APIs directly. OpenStack we can query easily (or modify the API if needed), EC2 we don't really have control over.
- Could we expect a third party to provide
- libcloud API queries might be useful here
Work Items
Dependency tree

* Blueprints in grey have been implemented.