Re: [ovirt-users] Hoste has available updates but nothing in yum
On Sun, Feb 12, 2017 at 8:02 PM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
On Sun, Feb 12, 2017 at 8:45 AM, Yedidyah Bar David
<didi(a)redhat.com> wrote:
>
>
>
> Were these hosts installed as 4.1, or upgraded from 4.0? If upgraded, how?
>
> collectd is a new requirement in 4.1. For your specific case, see also:
>
> https://bugzilla.redhat.com/1405810
>
> Best,
> --
> Didi
They were updated from 4.0.6 using yum update. They are plain CentOS 7.3
hosts
So I have used now on both hosts the command
sudo yum install collectd collectd-disk collectd-netlink collectd-virt
collectd-write_http fluentd rubygem-fluent-plugin-rewrite-tag-filter
rubygem-fluent-plugin-secure-forward
I see that collectd is set to disabled. Is it ok or other necessary actions
to be taken?
It's ok, see [4] below
Do I need to restart any components on hosts or engine after install
of
those packages on hosts?
It's designed so that once you configure stuff [4], no restart is needed.
In particular, vdsm will automatically start sending stuff to collectd
once that's up.
Where should I have noticed wrong data because of not having the
packages in
4.1?
For now, nowhere. The plan is eventually to make this mandatory, stop
maintaining stats in the engine (db) itself, and have the engine rely
on a central elasticsearch store for stats (which affect also scheduling
decisions, etc.).
The bugzilla contains the words "metrics store solution"
and seems
something evolving in a future feature... not already in...
This bug is a blocker for 1402901, which is the tracker for this feature.
If you go there, press the 'tree' link, and there press 'Show Resolved',
you get to [1], where you can see the entire dependency tree for this
feature.
Current state is basically:
1. We (oVirt) do not provide (yet?) means to install/configure elasticsearch,
see [2] and [3] for that. So for now, you should do this manually.
2. Once done, you can configure your hosts to send there metrics, see [4].
Adding also Shirly, the feature owner, in case you have more questions.
We expect some of the referenced bugs to be handled during 4.1.z, and the
rest by 4.2.
That said, we gladly welcome people to already try and test this, and
report success/failure/opinions/etc.
Best,
[1] https://bugzilla.redhat.com/showdependencytree.cgi?id=1402901&hide_re...
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1405812
[3] https://sradcoblog.wordpress.com/
[4] https://bugzilla.redhat.com/show_bug.cgi?id=1405813
--
Didi