oVirt is based on libvirt and it is the upstream for RHV product.
1 Like
If you know you are not going to grow and you will not need live migrations which are supported but you need to configure everything manually, sure, libvirt will work. My point was rather that our integration with libvirt is quite limiting, you canât do much compared to VMWare or RHV/ovirt.
Create a script to delete them, however every upgrade will add them back. Foreman is very flexible, we can provision Windows, BSDs, switches⌠the list goes on and on.
Foreman should auto associate the most âdefaultâ ones for you. Then it depends on your workflow, PXE BIOS, PXE UEFI, compute resource via cloud-init, user data or combination, ssh finish workflow. See our Provisioning guide for more details.
ok, I see, plain kickstart is simple but more advanced like live migrations are a different pair of shoes.
Ok, I will think about the âdeleteâ thing.
Yes, it did associate the most common ones, but when trying to tweak them, the list feels so cluttered. I try to âremove that from my sightâ that for now are not relevant. Thatâs why I asked, could one somewhere selectivly uninstall some of it. (same as with Zabbix, a lot of stuff is there by default).
Probably I need to still get more used to âworkflowsââŚ
Actually, now I learned how to use that page âproperlyâ (at least for Partition Tables): by using the filter, e.g. by OS Family.
As said, one feels overwhelmed by the long list of provisioning templates, for all kind of potential OS families (SUSE, Red Hat, Debian, âŚ). A bit annoying that it shows all of them alwaysâŚ
So I had created a bookmark for those containing the word âclemensâ (my customized clones) or âKickstartâ - by just typing that word in the search field.
Now I discovered that one can build more advanced filters/bookmarks. Once one clicks into that field to type something, there even comes a popup box which âencouragesâ the user to how to build a filter, in my case very useful: family=RedHat.
Kind of a mystery to me, how I missed that in my earlier use⌠was I just so focused on typing something that I was totally oblivious to that list of filter criteria popping up there? Dunno. Sometimes when trying to get one thing done one is blind to such things, I guessâŚ
Now I have for Partition Tables a bookmark âRedHatâ, because they are (for now) all what I care about. Is there a way to set this bookmark/filter be there on default? So when I come to that page itâs be default on (if I would want to see all, clicking the âxâ is faster than having to select a bookmark). Didnât find any setting for âDefault bookmark/filter for Partition Tablesâ, in Global Settings, for exampleâŚ
Perhaps this could be emphasized in the documentation a bit better.
For example here:
https://theforeman.org/manuals/2.0/index.html#4.4.3ProvisioningTemplates
Foreman comes with pre-created templates for the more common OSs, but you will need to review these. [XXX] All these templates are locked by default,
At that [XXX] could be something like:
You can create a filter that shows you only those provisioning templates relevant for your current/common use cases, and bookmark that filter.
How would I go to make a suggestion to changes to the documentation? Fork it in github, commit my changes in a branch, make a pull request?
The filter itself is not that intuitive to use for me yet - what do â~â and â^â do? Where is that documented?
How would I filter Provisioning Templates "all that start with âKickâ - all that I tried with e.g.:
name = âKick*â or name ~ âKick.*â
donât show any. As long as I donât put the closing quote it worksâŚ
(an interesting effect is when I type just âkickâ in the field, for those it shows also the PXEGrub and PXELinux templates⌠Magic 
This brings an interesting idea of ability to filter templates by OS family. We have recently added few metadata fields to the database and it should be doable. So when you are interested only letâs say RedHat family, you should be able to do such filter.
See the README in the guides/ subfolder. Thanks for taking care!
Yes, I believe thatâs exactly what I did, so that filter feature exists (I would say).
For the âPartition Tablesâ table/page usage itâs relatively straightforward, as it has the column âOS Familyâ right in the table.
For âProvisioning Templatesâ it offers as one filter key âoperatingsystemâ and setting that â= CentOSâ kind of filters / give me the ones I need; but itâs not as âuniversalâ as âOS familyâ (if a company would have, letâs say, Fedora, Centos and RHEL installations).
The main improvement Iâd wish here for would be to configure one filter as default.
And documentation/instructions/information what the â~â and â^â operators in a filter do. Perhaps they are well-known/self-evident to ruby/puppet verterans, but not to me. â~â I might speculate whether itâs perhaps related to regular expressions, but I didnât get any match to workâŚ
ah, ok, found it: Foreman :: Manual (section 4.1.5, Searching).
So itâs more SQL-style match characters ( _ and % ). It should also work with * but didnât for me⌠at least not in quoted string ;-/ . Ok, needs more experiementing.
Yeah we use a custom syntax that translate into SQL queries actually. The library we use is named scoped_search.
1 Like