On Tue, Aug 5, 2014 at 3:31 PM, Itamar Heim <[email protected]> wrote: > On 08/05/2014 09:36 PM, Trey Dockendorf wrote: >> >> On Tue, Aug 5, 2014 at 12:32 PM, ybronhei <[email protected]> wrote: >>> >>> Hey, >>> >>> Just noticed something that I forgot about.. >>> before filing new BZ, see in ovirt-host-deploy README.environment [1] the >>> section: >>> VDSM/configOverride(bool) [True] >>> Override vdsm configuration file. >>> >>> changing it to false will keep your vdsm.conf file as is after deploying >>> the >>> host again (what happens after node upgrade) >>> >>> [1] >>> https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment >>> >>> please check if that what you meant.. >>> >>> Thanks, >>> Yaniv Bronhaim. >>> >> >> I was unaware of that package. I will check that out as that seems to >> be what I am looking for. >> >> I have not filed this in BZ and will hold off pending >> ovirt-host-deploy. If you feel a BZ is still necessary then please do >> file one and I would be happy to provide input if it would help. >> >> Right now this is my workflow. >> >> 1. Foreman provisions bare-metal server with CentOS 6.5 >> 2. Once provisioned and system rebooted Puppet applies puppet-ovirt >> [1] module that adds the necessary yum repos, and installs packages. >> Part of my Puppet deployment is basic things like sudo management >> (vdsm's sudo is account for), sssd configuration, and other aspects >> that are needed by every system in my infrastructure. Part of the >> ovirt::node Puppet class is managing vdsm.conf, and in my case that >> means ensuring iSER is enabled for iSCSI over IB. >> 3. Once host is online and has had the full Puppet catalog applied I >> log into ovirt-engine web interface and add those host (pulling it's >> data via the Foreman provider). > > > just wondering (and i may have missed this in the thread) - if you want bare > metal provisioning and foreman, why not just use the new 3.5 integration > doing that: > http://www.ovirt.org/Features/AdvancedForemanIntegration > > it will call foreman, do bare metal provision with the hostgroup you chose, > then foreman will call add host in the engine on your behalf? > > (doesn't limit you from either extending ovirt-host-deploy plugins, or using > more puppet modules via the hostgroup). >
I was actually looking forward to using those features but haven't yet had a chance to test 3.5 as I have no spare hardware at the moment. The Foreman Integration is definitely on my radar as we rely very heavily on Foreman. Thanks, - Trey _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
