Feature #4250: Expose compute profiles via API - Foreman

Custom queries

3.7.1 release DONE
3.7.1 release TODO
3.8.0 release DONE
3.8.0 release TODO
3.9.0 release DONE
3.9.0 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Feature #4250

closed

Expose compute profiles via API

Added by Libor Zoubek almost 10 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Joseph Magen

Category:

API

Target version:

1.5.1

Difficulty:

Triaged:

Bugzilla link:

1107714

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

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

Could you please add compute profiles to API?

Related issues 5 (0 open — 5 closed)

Related to Foreman - Feature #3178: add ability to apply a virtual hardware template at hostgroup level	Closed	Joseph Magen	10/01/2013	Actions
Related to Foreman - Bug #4408: cannot provision VM using API or UI	Resolved		02/18/2014	Actions
Related to Foreman - Bug #6342: Compute profile should be used when empty volumes and interfaces passed in compute_attributes	Closed	Tomáš Strachota	06/23/2014	Actions
Related to Hammer CLI - Feature #6344: Commands for read operations around compute profiles and attributes	Closed	Tomáš Strachota		Actions
Has duplicate Foreman - Feature #4862: API v2 - add api/compute_profiles	Duplicate	Joseph Magen	03/26/2014	Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Dominic Cleal almost 10 years ago

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

Actions

Copy link

Updated by Dominic Cleal almost 10 years ago

Difficulty deleted (~~easy~~)

Actions

Copy link

Updated by Dominic Cleal almost 10 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?

Actions

Copy link

Updated by Dominic Cleal almost 10 years ago

Tracker changed from Bug to Feature

Actions

Copy link

Updated by Dominic Cleal almost 10 years ago

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

Actions

Copy link

Updated by Libor Zoubek almost 10 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.

Actions

Copy link

Updated by Dominic Cleal almost 10 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).

Actions

Copy link