[email protected] wrote: > From: David Lutterkort <[email protected]> > > --- > server/lib/deltacloud/drivers/mock/mock_driver.rb | 24 > +++++++++++++++++++++ > 1 files changed, 24 insertions(+), 0 deletions(-) > > diff --git a/server/lib/deltacloud/drivers/mock/mock_driver.rb > b/server/lib/deltacloud/drivers/mock/mock_driver.rb > index 907520b..6d99c36 100644 > --- a/server/lib/deltacloud/drivers/mock/mock_driver.rb > +++ b/server/lib/deltacloud/drivers/mock/mock_driver.rb > @@ -75,6 +75,30 @@ class MockDriver < Deltacloud::BaseDriver > }), > ] ) unless defined?( REALMS ) > > + define_hardware_profile('m1-small') do > + cpu 1 > + memory 1.7 * 1024 > + storage 160 > + architecture 'i386' > + end > + > + define_hardware_profile('m1-large') do > + cpu 2 > + memory (7.5*1024 .. 15*1024), :default => 10 * 1024 > + storage [ 850, 1024 ] > + architecture 'x86_64' > + end > + > + define_hardware_profile('m1-xlarge') do > + cpu 4 > + memory (12*1024 .. 32*1024) > + storage [ 1024, 2048, 4096 ] > + architecture 'x86_64' > + end > + > + # Some clouds tell us nothing about hardware profiles (e.g., OpenNebula) > + define_hardware_profile 'opaque' > + > define_instance_states do > start.to( :pending ) .on( :create ) > When we don't define anything about a HW profile, does this mean the instance must define every HWP parameter -- requiring RAM, cpu, storage, arch,etc? Is it valid to leave a single attribute blank in a HWP -- thus making that one param required for any instance that uses it?
Or, instead, does this just mean that we pass along the HWP by name to the provider and we don't know or care what the params are? In this case I'm assuming we can't define any instance-specific overrides either. Scott _______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
