Bug 1627753

Rich, Please update the required rsyslog packages.

Packages required for PCP:
pcp-zeroconf
pcp
pcp-selinux
pcp-conf
pcp-libs
pcp-export-pcp2elasticsearch

(In reply to Shirly Radco from comment #1)
> Rich, Please update the required rsyslog packages.

Note that these packages will be available in RHEL 7.6.

For now:

rsyslog
rsyslog-omelasticsearch
rsyslog-mmjsonparse
rsyslog-mmnormalize

Note that these will pull in other dependencies from RHEL 7.6 such as libfastjson, liblognorm, libestr, etc.

In the future, you may want these additional packages:

rsyslog-gssapi
rsyslog-kafka
rsyslog-relp

Forgot to add the rsyslog dependencies - you'll need either the latest rhel 7.6 or rhlog versions of these packages:

libfastjson
liblognorm
libestr

rsyslog may also pull in the following packages:

logrotate
gnutls
trousers

Ok, so minimal set of packages to be required in 4.3.0:
pcp-zeroconf
pcp
pcp-selinux
pcp-conf
pcp-libs
pcp-export-pcp2elasticsearch
rsyslog
rsyslog-omelasticsearch
rsyslog-mmjsonparse
rsyslog-mmnormalize

Shirly, what should we do about fluentd requirements? keep them or drop them?

I'm thinking about upgrade scenario where both 4.2 hosts and 4.3 hosts are on the same datacenter with cluster compatibility 4.2 until all the hosts get updated.
What should happen in this case? Note that 4.3 hosts may be used by 4.2 engine in 4.2 compatibility mode.

(In reply to Sandro Bonazzola from comment #5)
> Ok, so minimal set of packages to be required in 4.3.0:
> pcp-zeroconf
> pcp
> pcp-selinux
> pcp-conf
> pcp-libs
> pcp-export-pcp2elasticsearch
> rsyslog
> rsyslog-omelasticsearch
> rsyslog-mmjsonparse
> rsyslog-mmnormalize

and 

libfastjson
liblognorm
libestr

> 
> Shirly, what should we do about fluentd requirements? keep them or drop them?
> 
> I'm thinking about upgrade scenario where both 4.2 hosts and 4.3 hosts are
> on the same datacenter with cluster compatibility 4.2 until all the hosts
> get updated.
> What should happen in this case? Note that 4.3 hosts may be used by 4.2
> engine in 4.2 compatibility mode.

Fluentd can still be used in upstream but we won't keep the packages in d/s.

Fluentd, rsyslog and pcp can send the data to elasticsearch.
The only issue I see is making sure the naming stays the same.
I'll try to keep it backwards compatible. Not sure on limitations at this point.

I'm not willing to have differences between up and down stream.

The role supports installing fluentd but we will not install it in 4.3. There will be no differences between up and down stream.
But if upstream users want, they can update the role vars to install fluentd.
The role will be based on the linux-system-roles that includes the functionality.

(In reply to Rich Megginson from comment #6)
> (In reply to Sandro Bonazzola from comment #5)
> > Ok, so minimal set of packages to be required in 4.3.0:
> > pcp-zeroconf
> > pcp
> > pcp-selinux
> > pcp-conf
> > pcp-libs
> > pcp-export-pcp2elasticsearch
> > rsyslog
> > rsyslog-omelasticsearch
> > rsyslog-mmjsonparse
> > rsyslog-mmnormalize
> 
> and 
> 
> libfastjson
> liblognorm
> libestr
> 
> > 
> > Shirly, what should we do about fluentd requirements? keep them or drop them?
> > 
> > I'm thinking about upgrade scenario where both 4.2 hosts and 4.3 hosts are
> > on the same datacenter with cluster compatibility 4.2 until all the hosts
> > get updated.
> > What should happen in this case? Note that 4.3 hosts may be used by 4.2
> > engine in 4.2 compatibility mode.

Why is rsyslog-mmjsonparse required for oVirt ?
And if it is not, Can any of the other dependencies be dropped:
libfastjson, liblognorm, libestr ?

(In reply to Shirly Radco from comment #10)
> (In reply to Rich Megginson from comment #6)
> > (In reply to Sandro Bonazzola from comment #5)
> > > Ok, so minimal set of packages to be required in 4.3.0:
> > > pcp-zeroconf
> > > pcp
> > > pcp-selinux
> > > pcp-conf
> > > pcp-libs
> > > pcp-export-pcp2elasticsearch
> > > rsyslog
> > > rsyslog-omelasticsearch
> > > rsyslog-mmjsonparse
> > > rsyslog-mmnormalize
> > 
> > and 
> > 
> > libfastjson
> > liblognorm
> > libestr
> > 
> > > 
> > > Shirly, what should we do about fluentd requirements? keep them or drop them?
> > > 
> > > I'm thinking about upgrade scenario where both 4.2 hosts and 4.3 hosts are
> > > on the same datacenter with cluster compatibility 4.2 until all the hosts
> > > get updated.
> > > What should happen in this case? Note that 4.3 hosts may be used by 4.2
> > > engine in 4.2 compatibility mode.
> 
> Why is rsyslog-mmjsonparse required for oVirt ?

It isn't if you have no json logs.

> And if it is not, Can any of the other dependencies be dropped:
> libfastjson, liblognorm, libestr ?

No, because you need rsyslog-mmnormalize, and those libraries are required by rsyslog-mmnormalize.

But - what difference does it make to have rsyslog-mmjsonparse or not?  Is it just one extra dependency you would rather not have to have?

For 4.3.0 we require the rsyslog packages. PCP was postponed for now.
rsyslog
rsyslog-omelasticsearch
rsyslog-mmjsonparse
rsyslog-mmnormalize
libfastjson
liblognorm
libestr

(In reply to Shirly Radco from comment #12)
> For 4.3.0 we require the rsyslog packages. PCP was postponed for now.
> rsyslog
> rsyslog-omelasticsearch

this one is rsyslog-elasticsearch

> rsyslog-mmjsonparse
> rsyslog-mmnormalize
> libfastjson
> liblognorm
> libestr

Should we explain how to uninstall fluentd?

(In reply to Rolfe Dlugy-Hegwer from comment #14)
> Should we explain how to uninstall fluentd?

I think that just removing the rpm using yum should be enough. Shirly?

I disable and stop the service when configuring Rsyslog.
Is removing the package required?

(In reply to Shirly Radco from comment #16)
> I disable and stop the service when configuring Rsyslog.
> Is removing the package required?

No, not required, but I think user should be aware at documentation level we are leaving unused packages around after upgrade.

I see you updated the doc text. I updated it as well.

Verified in ovirt-host-4.3.1-1.el7ev.

Fluentd depencencies were replaced with rsyslog.

# yum deplist ovirt-host* | grep fluent
# yum deplist ovirt-host* | grep rsyslog
  dependency: rsyslog
   provider: rsyslog.x86_64 8.24.0-34.el7
  dependency: rsyslog-elasticsearch
   provider: rsyslog-elasticsearch.x86_64 8.24.0-34.el7
  dependency: rsyslog-mmjsonparse
   provider: rsyslog-mmjsonparse.x86_64 8.24.0-34.el7
  dependency: rsyslog-mmnormalize
   provider: rsyslog-mmnormalize.x86_64 8.24.0-34.el7

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.