Bob McWhirter wrote:
Howdy folks--
Been thinking about the flavor/hardware problem some, and he's my initial thoughts:
We should remove "flavors" as they exist now, and replace them with "hardware profiles" (or some other name).
These would specify the different profiles available, in terms of min/ max capabilities for each profile.
For a cloud provider with completely flexible instances, it might have 1 profile something akin to
memory: 0GB-64GB, default=2gb disk: 0GB-1TB, default=200gb cpu: 1-8, default=2
So in this case the profile doesn't specify the exact HW config. This still leaves the question of whether the exact memory, etc. params are determined by the user creating the instance or by the cloud by some default/automatic process by the driver and/or cloud provider. In addition we will need to add fields to the Instance model to track what the _actual_ memory, disk, and cpu values are for an instance, whether user-selected or chosen by the cloud.
For something like EC2, min==max, and it'd have a profile per instance type.
Upon instantiating an instance from an image, you'd select, and optionally parameterize a hardware profile for the instance. EC2, no parameterization/customization is possible. For RIMU etc, you could feed it what you want.
Yes, so to support the parameterization we'll also need memory, disk, and cpu added to the instance model so we will know what portion of the range was selected by the user or cloud.
We may also need a flag indicating mutability of the hardware post- launch, in case a provider allows adding CPU/disk/RAM on-the-fly.
Thoughts?
-Bob _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel