Hello,
Is it possible to remove the 'Bare Metal' option from New Host -> Deploy on
(or re-order the list so its not first)?
I'm using openstack exclusively and when users jump in to provision a new
vm they always have to select that drop down which is a bit confusing to
new users.
This page
<Blog Landing Page | Red Hat Developer;
has some info that looks useful, but I'm not sure where I can configure
something like this post-install. Also I'd still like to be able to use DNS
integration and this seems like the equivalent to disabling unattended mode.
Thanks,
Steve
> Hello,
>
> Is it possible to remove the 'Bare Metal' option from New Host -> Deploy on
> (or re-order the list so its not first)?
>
> I'm using openstack exclusively and when users jump in to provision a new
> vm they always have to select that drop down which is a bit confusing to
> new users.
>
> This page
> <http://developerblog.redhat.com/2013/07/12/managing-openstack-with-the-foreman/>
> has some info that looks useful, but I'm not sure where I can configure
> something like this post-install. Also I'd still like to be able to use DNS
> integration and this seems like the equivalent to disabling unattended mode.
Unfortunately I don't think changing the default 'Deploy on' option is
on Issues - Foreman.
Alternatively you can create a host group with the Openstack compute
resource and all other related options. That way users would just select
this host group and everything would get set automatically (including
the deploy on option).
I would say this is not on anyone's 'backlog', but perhaps it could be
a setting under Settings > Provisioning, so if you feel like
contributing such a thing, we can probably help you out on IRC on
#theforeman-dev.
···
On 04/08, steved0ca wrote:
>
> Thanks,
> Steve
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
–
Daniel Lobato Garcia
@eLobatoss
blog.daniellobato.me
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato
It isn't possible to set the compute resource (deploy on) setting on a
host group, but you can associate a compute profile so once you set the
combination of CR + host group then the VM settings are filled out.
Feature #5790: Default "Deploy on" value for host groups. - Foreman is one such ticket requesting
that the CR itself is added to the host group. There's another
Bug #1875: user restricted to compute resource(s) can create baremetal hosts - Foreman & related tracks making the
bare metal (non-CR) case restricted by permissions.
···
On 09/04/15 07:16, Daniel Lobato Garcia wrote:
> On 04/08, steved0ca wrote:
>> Hello,
>>
>> Is it possible to remove the 'Bare Metal' option from New Host -> Deploy on
>> (or re-order the list so its not first)?
>>
>> I'm using openstack exclusively and when users jump in to provision a new
>> vm they always have to select that drop down which is a bit confusing to
>> new users.
>>
>> This page
>>
>> has some info that looks useful, but I'm not sure where I can configure
>> something like this post-install. Also I'd still like to be able to use DNS
>> integration and this seems like the equivalent to disabling unattended mode.
>
> Unfortunately I don't think changing the default 'Deploy on' option is
> on http://projects.theforeman.org/issues/.
>
> Alternatively you can create a host group with the Openstack compute
> resource and all other related options. That way users would just select
> this host group and everything would get set automatically (including
> the deploy on option).
–
Dominic Cleal
Red Hat Engineering
