Here's some of my ramblings from IRC; summary is that we can do it, it just needs to be implemented:

* clalance was reading the code in parallel
<clalance> int deltacloud_create_instance(struct deltacloud_api *api, const char *image_id,
<clalance>           const char *name, const char *realm_id,
<clalance>           const char *hardware_profile,
<clalance>           struct deltacloud_instance *inst)
<clalance> So I just take a "hardware_profile" string in.
<clalance> And then I put it into the request as a POST parameter:
<clalance>   if (hardware_profile != NULL) {
<clalance>     safehwp = curl_escape(hardware_profile, 0);
<clalance>     if (safehwp == NULL)
<clalance>       error = 1;
<clalance>     fprintf(paramfp, "&hwp_id=%s", safehwp);
<clalance>   }
* clalance now wonders how the ruby client is going to achieve this
<clalance> Oh, I see.
<clalance> It will take the hash, and for each variable in the hash, make a new parameter called hwp_<key>
<clalance> OK.
<clalance> I can make the C library do this, it just doesn't at present.

We definitely need this functionality in the scheduler. However we're not going to allow arbitrary HW Profile customization in the UI. We'll be using HW Profile customization in the mapping layer between "cloud engine" HWPs and "provider" HWPs. So the user would pick "cloud engine small", which might map to a regular HWP on ec2 (doesn't allow customization) but to a customized profile on RHEV.

This is now done, so switching it over to MODIFIED.

Chris Lalancette

moving to on_qa for review

HWP are working between ec2, vmware, and rhevm..
moving to verified

release pending...

release pending...

closing out old bugs

perm close