cool,
Send me a pick, ill make it in akka,

J


On Mon, May 12, 2014 at 10:13 PM, Timothy Danford
<notifications@github.com>wrote:

> In scheduling-core/src/main/scala/com/tdanford/simulator/Node.scala:
>
> > + * Represents the instance type of a node, like a spot instance
> > + * @param name the name of the instance type (spot)
> > + * @param isSpot is this a "spot" instance, can it be destroyed randomly?  Does the price fluctuate
> > + */
> > +case class InstanceType(name: String, isSpot: Boolean)
> > +
> > +/**
> > + * Represents the basic instance types that can be requested
> > + * such as aws c3.large
> > + * @param name A unique name such as c3.large per vendor
> > + * @param mem The total memory of a node
> > + * @param cpu The cpu count of a node normalized to aws CPUs
> > + * @param io The max sustained IOps of a node
> > + * @param vendor The name of the vendor such as amazon aws
> > + */
> > +case class NodeType(name: String, mem: Int, cpu: Int, io: Int, vendor: String)
>
> We should talk about design -- I don't want to go quite so detailed yet.
> At most I might model memory first.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/tdanford/scheduling-simulator/pull/2/files#r12564156>
> .
>