Feature #22277: Automatic Allocation should not set a home server in xen - Xen - Foreman

Actions

Copy link

Feature #22277

closed

Automatic Allocation should not set a home server in xen

Added by Christian Heckelmann almost 7 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Low

Assignee:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Foreman - 1.15.6

Red Hat JIRA:

Description

Using

foreman 1.15.6
tfm-rubygem-fog-xenserver.noarch 0.2.3-1.el7
tfm-rubygem-foreman_xen.noarch 0.5.2-1.fm1_15.el7
xenserver 6.5

Hi @all,

when we are creating new hosts via foreman and using automatic allocation, the xen plugin is always assigning a home server to the VM in Xen and (unfortunately) it's always the same host in the xen pool which ends up filling up this host while, other hosts in this pool are still "empty".

Is it possible to change it when using "automatic allocation" that no home server is set?

Regards,

Christian