Bug 618307
| Summary: | Support custom HW profiles in condor_submit | ||
|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Jan Provaznik <jprovazn> |
| Component: | aeolus-conductor | Assignee: | Ian Main <imain> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 0.3.1 | CC: | clalance, cpelland, deltacloud-maint, sseago, whayutin |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jan Provaznik
2010-07-26 15:52:58 UTC
Here are some of my ramblings from IRC: <clalance> jprovazn: Ah, OK. <clalance> jprovazn: I'll have to check with Slow/the condor people, but I think we can do this. <clalance> jprovazn: What we need is a way to match the providers that support a custom hardware_profile. <clalance> So the requirements, we'd do something like "hardware_profile=custom" <clalance> And the providers that support custom would advertise that in their provider ADs. <clalance> Finally, we would pass the hash as a piece of data into the job. <clalance> And if we matched on a custom one, we would read the custom data in as the hardware profile. <clalance> This will require changes in condor as well. <clalance> But it shouldn't be too awful. I think in the submission to Condor we'll just specify a "cloud engine" HWP, but it's in the matchmaking stage that we'll need to generate the custom HWP (if mapped that way to the matching provider), since we're not allowing arbitrary customization in the UI, only in the provider mapping layer. We can't specify directly in the UI anyway since we don't know what provider the instance is going to at submit time. I'm pretty sure this was done long ago. Moving to MODIFIED. Chris Lalancette moving to on_qa for review hwp are working between ec2, vmware, rhevm release pending... release pending... closing out old bugs perm close |