Martin, do we really need postfix? Aren't we allowing to use external smtp server?

Postfix is definitely not needed. Hosted engine can use any SMTP server on network to send the email.

Post fix is completely optional.

(In reply to Doron Fediuck from comment #3)
> Post fix is completely optional.

Hi Doron,
Are the error reporting through the SMTP supported for the RHEVH just as they're supported for RHEL6.x/7.x?

(In reply to Nikolai Sednev from comment #4)
> (In reply to Doron Fediuck from comment #3)
> > Post fix is completely optional.
> 
> Hi Doron,
> Are the error reporting through the SMTP supported for the RHEVH just as
> they're supported for RHEL6.x/7.x?

Hi, email notifications are optional and require additional configuration. The main reporting is done to the log file(s).

Having said that, re-opening to revisit for 4.0.

(In reply to Doron Fediuck from comment #5)
> (In reply to Nikolai Sednev from comment #4)
> > (In reply to Doron Fediuck from comment #3)
> > > Post fix is completely optional.
> > 
> > Hi Doron,
> > Are the error reporting through the SMTP supported for the RHEVH just as
> > they're supported for RHEL6.x/7.x?
> 
> Hi, email notifications are optional and require additional configuration.
> The main reporting is done to the log file(s).
> 
> Having said that, re-opening to revisit for 4.0.

Hi Doron,

Shouldn't postfix dependency be removed from RHEL based ovirt-hosted-engine-setup-1.3.2.3-1.el7ev.noarch? 

"hosted-engine --deploy" procedure requires from customer to fill in the SMTP if it is desired, if not added during first deployment, there is no easy and user-friendly way to add SMTP later, while using "hosted-engine --deploy" procedure. If for RHEL based deployments SMTP might be added later using some manual configuration, then how should it be supported for RHEVH?

Sorry for a small off-topic, is there a Syslog server support available or planned for the hosted-engine (agent/broker)?

Just to answer the syslog question. The local logging of hosted engine is configured using /etc/ovirt-hosted-engine-ha/agent-log.conf and Python
provides SyslogHandler
https://docs.python.org/2/library/logging.handlers.html#sysloghandler that can be configured there.

We do not really have any example about this, but it should work. You have to do it on every host though, it is not centralized.


With regards to the postfix dependency.. if the setup is not sending any emails (and I do not think it is) then there should probably be no RPM dependency on postfix.

pulling in postifx would add another 17MB to the image.
An increase of ~2.5%.

Moran, do we want to take this increase considering that postfix is an optional depdendency?
Users could still use MTAs on remote machines.

(In reply to Fabian Deutsch from comment #8)
> pulling in postifx would add another 17MB to the image.
> An increase of ~2.5%.
> 
> Moran, do we want to take this increase considering that postfix is an
> optional depdendency?
> Users could still use MTAs on remote machines.

my questions back to you are:
-will users will be capable to have this functionality if they desire it later on?
-what would be the impact for the user who decided to configure those configure those params on rhevh HE setup.

(In reply to Moran Goldboim from comment #9)
> my questions back to you are:
> -will users will be capable to have this functionality if they desire it
> later on?

They can not install postfix on the host where they are currently running HE.
But they can - always - configure the host to use an MTA on a remote host.

> -what would be the impact for the user who decided to configure those
> configure those params on rhevh HE setup.

IIUIC the MTA is used to emit HA related notifications via email.
If postifx is not available on the current host, then a remote host can be configured during the HE setup.

Is this correct, Simone?

Yes, this is correct. The user can configure a different SMTP server if localhost cannot be used.

Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Just adding this here:
postfix-2.10.1-6.el7.x86_64 exists for ovirt-node-ng-installer-ovirt-4.0-2016051906.iso 
libvirt-client-1.2.17-13.el7_2.4.x86_64
qemu-kvm-tools-ev-2.3.0-31.el7_2.10.1.x86_64
qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64
qemu-img-ev-2.3.0-31.el7_2.10.1.x86_64
qemu-kvm-common-ev-2.3.0-31.el7_2.10.1.x86_64
mom-0.5.3-1.1.el7.noarch
vdsm-4.17.999-1155.gitcf216a0.el7.centos.x86_64
sanlock-3.2.4-2.el7_2.x86_64
ovirt-vmconsole-host-1.0.2-0.0.master.20160517094103.git06df50a.el7.noarch
ovirt-setup-lib-1.0.2-0.0.master.20160502125738.gitf05af9e.el7.centos.noarch
ovirt-release40-4.0.0-0.3.beta1.noarch
ovirt-vmconsole-1.0.2-0.0.master.20160517094103.git06df50a.el7.noarch
ovirt-engine-sdk-python-3.6.5.1-0.1.20160507.git5fb7e0e.el7.centos.noarch
ovirt-host-deploy-1.5.0-0.1.alpha1.el7.centos.noarch
ovirt-hosted-engine-setup-2.0.0-0.1.beta1.el7.centos.noarch
ovirt-release-host-node-4.0.0-0.3.beta1.el7.noarch
ovirt-hosted-engine-ha-2.0.0-0.1.beta1.el7.centos.noarch
ovirt-node-ng-image-update-placeholder-4.0.0-0.3.beta1.el7.noarch
CentOS Linux release 7.2.1511 (Core) 
Linux 3.10.0-327.18.2.el7.x86_64 #1 SMP Thu May 12 11:03:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Linux version 3.10.0-327.18.2.el7.x86_64 (builder.centos.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu May 12 11:03:55 UTC 2016

Test version:
rhev-hypervisor7-ng-4.0-20160527.0
imgbased-0.7.0-0.1.el7ev.noarch

postfix and mailx are exist on above build, and deploy hosted engine can successful.
# rpm -qa | grep postfix
postfix-2.10.1-6.el7.x86_64

# rpm -qa | grep mailx
mailx-12.5-12.el7_0.x86_64

So the bug is fixed, change bug status to VERIFIED.

Martin, did you say that you wanted to remove "local MTA" support?

oVirt 4.0.0 has been released, closing current release.