Shlomi,
Thanks for bringing this up.
My main concern currently is stability. .0 releases are usually broken to
some extend. I think, we should come up with better integration testing
before a release. E.g. try to deploy a host with all available compute
resources automatically before a release. Our main goal should be to
improve stability.
Foreman is great if you stick to simple use cases. I believe, there are
some sophisticated use cases (yet quite common in an Enterprise
environment), that should be addressed. We should come up with some
supported use cased and implement them (and eventually test them before
each release).
Feature-wise, what I really miss:
* Bare Metal Bonding Support (RM #9487)
Just as an example, what I mean by supported use cases:
If you use bare metal provisioning, you'll most definitely look into the
discovery plugin. And you'll most definitely also want to use some kind of
network bonding for redundancy. So you have your servers connected to the
same VLAN on multiple interfaces.
After the server is racked, it should boot the discovery image and show up
in Foreman's list of recently discovered hosts. It does detect the bonding
via lldp but does not automatically configure it.
When you configure the bond manually, you fail because you don't know the
mac address of the bonded interface and tftp / dhcp is not provisioned
(partially fixed in RM #17485). Then there is the case, that the os
installs correctly on the first bonded interface and the discovery process
starts again on the second bonded interface. A horrible experience to sum
up. Should be better on an enterprise grade software. Will be better with
1.15. Any help or comments are appreciated.
* Permissions
I think, the permissions system lacks the ability to specify a permission
like this: Allow a user to view a subnet, but don't allow a user to create
a host in that subnet.
* Default Owner of Hosts (RM #14013)
The default owner of hosts should be configurable. The default user might
be a group where the user is a member of.
* Linking of Compute Resources VLANs to Subnet (RM #10539)
Foreman should know more about the Network of a Compute Resource. The
subnet should be linked to VLANs on the Compute Resource. That would
prevent a lot of errors when manually deploying a VM.
* Bulk Actions for Environments, Hostgroups
Environments and Hostgroups need bulk actions via the UI. Would save a lot
of clicks / foreman console sessions.
Timo
Am Mittwoch, 7. Dezember 2016 13:08:52 UTC+1 schrieb Shlomi Zadok:
>
> Hey all,
> I am trying to collect and learn about the things that mostly {piss you
> off,itch} on Foreman.
> It could be little things like a misplaced button or big things. Anything.
>
> So let's start a thread of what are the things that mostly piss you off in
> Foreman.
>
> Here are my contributions to the thread:
>
> * We need to add "compute resource" select to hostgroup, so when I create
> new host(s) I do not have to select a compute resource each time.
> * Associating provisioning templates to an operating system is complicated
> and can be simplified
>
>
> Now: it's your turn :)
>
> Thanks !
>
>
>
>
>
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
