Feature #4250

Expose compute profiles via API

Added by Libor Zoubek almost 4 years ago. Updated over 3 years ago.

Status:Closed
Priority:Normal
Assigned To:Joseph Magen
Category:API
Target version:Sprint 23
Difficulty: Bugzilla link:1107714
Found in release: Pull request:
Story points-
Velocity based estimate-
Release1.5.1Release relationshipAuto

Description

I've just upgraded to 1.4 so I could use compute profiles.

Could you please add compute profiles to API?


Related issues

Related to Foreman - Feature #3178: add ability to apply a virtual hardware template at hostg... Closed 10/01/2013
Related to Foreman - Bug #4408: cannot provision VM using API or UI Resolved 02/18/2014
Related to Foreman - Bug #6342: Compute profile should be used when empty volumes and int... Closed 06/23/2014
Related to Hammer CLI - Feature #6344: Commands for read operations around compute profiles and ... Assigned 06/23/2014
Duplicated by Foreman - Feature #4862: API v2 - add api/compute_profiles Duplicate 03/26/2014

Associated revisions

Revision 10ac97b0
Added by Joseph Magen over 3 years ago

fixes #4250 - API v2 - add compute profiles

Revision 9dc100e4
Added by Joseph Magen over 3 years ago

fixes #4250 - API v2 - add compute profiles

(cherry picked from commit 10ac97b0d91a2ef9769cc00d3ddf95e2b50ee545)

History

#1 Updated by Dominic Cleal almost 4 years ago

  • Related to Feature #3178: add ability to apply a virtual hardware template at hostgroup level added

#2 Updated by Dominic Cleal almost 4 years ago

  • Difficulty deleted (easy)

#3 Updated by Dominic Cleal over 3 years ago

Which aspects in particular are the priority?

Being able to manage compute profiles, and their attributes, or just being able to provision using profiles already created?

#4 Updated by Dominic Cleal over 3 years ago

  • Tracker changed from Bug to Feature

#5 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #4408: cannot provision VM using API or UI added

#6 Updated by Libor Zoubek over 3 years ago

Dominic Cleal wrote:

Which aspects in particular are the priority?

Being able to manage compute profiles, and their attributes, or just being able to provision using profiles already created?

Being able to provision using created profiles, especially I need to be able to retrieve profile by name, so I can pass profile_id when creating host.

#7 Updated by Dominic Cleal over 3 years ago

Makes sense, thanks. If we can fix this anyway (see #4408 for a little discussion of why it's broken), then you should be able to use compute_profile_name without an additional lookup (same for all associations in 1.4).

#8 Updated by Dominic Cleal over 3 years ago

  • Duplicated by Feature #4862: API v2 - add api/compute_profiles added

#9 Updated by Joseph Magen over 3 years ago

  • Status changed from New to Ready For Testing

#10 Updated by Dominic Cleal over 3 years ago

  • Assigned To set to Joseph Magen
  • Target version set to Sprint 21

#11 Updated by Dmitri Dolguikh over 3 years ago

  • Target version changed from Sprint 21 to Sprint 22

#12 Updated by Dmitri Dolguikh over 3 years ago

  • Target version changed from Sprint 22 to Sprint 23

#13 Updated by Dmitri Dolguikh over 3 years ago

  • Target version changed from Sprint 23 to Sprint 22

#14 Updated by Dmitri Dolguikh over 3 years ago

  • Target version changed from Sprint 22 to Sprint 23

#15 Updated by Dominic Cleal over 3 years ago

  • Release set to 1.5.1

#16 Updated by Joseph Magen over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#17 Updated by Bryan Kearney over 3 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1107714

#18 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #6342: Compute profile should be used when empty volumes and interfaces passed in compute_attributes added

#19 Updated by Dominic Cleal over 3 years ago

  • Related to Feature #6344: Commands for read operations around compute profiles and attributes added

Also available in: Atom PDF