[ovirt-users] Any monitoring tool provided?

Shirly Radco sradco at redhat.com
Wed Mar 28 05:19:56 UTC 2018


Adding Rich Megginson.

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

On Wed, Mar 28, 2018 at 1:10 AM, Nicolas Vaye <nicolas.vaye at province-sud.nc>
wrote:

> OK, i have removed all libvirt-* packages
>
> i have seen that in the playbook, firewalld will be disable and iptables
> manage the firewall.
>
> I have a problem because my metric server was behind a proxy web and when
> i run
>
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
>
> i get
>
>
> CHECK [memory_availability : localhost] ******************************
> ************************************************************
> **************************************************
>
> fatal: [localhost]: FAILED! => {
>
>     "changed": false,
>
>     "checks": {
>
>         "disk_availability": {},
>
>         "docker_image_availability": {
>
>             "failed": true,
>
>             "failures": [
>
>                 [
>
>                     "OpenShiftCheckException",
>
>                     "One or more required container images are not
> available:\n    cockpit/kubernetes:latest,\n    openshift/origin-deployer:latest,\n
>   openshift/origin-docker-registry:latest,\n    openshift/origin-haproxy-router:latest,\n
>   openshift/origin-pod:latest\nChecked with: skopeo inspect
> [--tls-verify=false] [--creds=<user>:<pass>] docker://<registry>/<image>\nDefault
> registries searched: docker.io\nFailed connecting to: docker.io\n"
>
>                 ]
>
>             ],
>
>             "msg": "One or more required container images are not
> available:\n    cockpit/kubernetes:latest,\n    openshift/origin-deployer:latest,\n
>   openshift/origin-docker-registry:latest,\n    openshift/origin-haproxy-router:latest,\n
>   openshift/origin-pod:latest\nChecked with: skopeo inspect
> [--tls-verify=false] [--creds=<user>:<pass>] docker://<registry>/<image>\nDefault
> registries searched: docker.io\nFailed connecting to: docker.io\n"
>
>         },
>
>         "docker_storage": {
>
>             "skipped": true,
>
>             "skipped_reason": "Disabled by user request"
>
>         },
>
>         "memory_availability": {},
>
>         "package_availability": {
>
>             "changed": false,
>
>             "invocation": {
>
>                 "module_args": {
>
>                     "packages": [
>
>                         "PyYAML",
>
>                         "bash-completion",
>
>                         "bind",
>
>                         "ceph-common",
>
>                         "cockpit-bridge",
>
>                         "cockpit-docker",
>
>                         "cockpit-system",
>
>                         "cockpit-ws",
>
>                         "dnsmasq",
>
>                         "docker",
>
>                         "etcd",
>
>                         "firewalld",
>
>                         "flannel",
>
>                         "glusterfs-fuse",
>
>                         "httpd-tools",
>
>                         "iptables",
>
>                         "iptables-services",
>
>                         "iscsi-initiator-utils",
>
>                         "libselinux-python",
>
>                         "nfs-utils",
>
>                         "ntp",
>
>                         "openssl",
>
>                         "origin",
>
>                         "origin-clients",
>
>                         "origin-master",
>
>                         "origin-node",
>
>                         "origin-sdn-ovs",
>
>                         "pyparted",
>
>                         "python-httplib2",
>
>                         "yum-utils"
>
>                     ]
>
>                 }
>
>             }
>
>         },
>
>         "package_version": {
>
>             "skipped": true,
>
>             "skipped_reason": "Disabled by user request"
>
>         }
>
>     },
>
>     "msg": "One or more checks failed",
>
>     "playbook_context": "install"
>
> }
>
>
> NO MORE HOSTS LEFT ******************************
> ************************************************************
> ***********************************************************************
>
>         to retry, use: --limit @/usr/share/ansible/openshift-
> ansible/playbooks/byo/config.retry
>
>
> PLAY RECAP ************************************************************
> ************************************************************
> *************************************************
>
> localhost                  : ok=67   changed=4    unreachable=0    failed=1
>
>
>
> INSTALLER STATUS ******************************
> ************************************************************
> *************************************************************************
>
> Initialization             : Complete
>
> Health Check               : In Progress
>
>         This phase can be restarted by running: playbooks/byo/openshift-
> checks/pre-install.yml
>
>
>
>
> Failure summary:
>
>
>
>   1. Hosts:    localhost
>
>      Play:     OpenShift Health Checks
>
>      Task:     Run health checks (install) - EL
>
>      Message:  One or more checks failed
>
>      Details:  check "docker_image_availability":
>
>                One or more required container images are not available:
>
>                    cockpit/kubernetes:latest,
>
>                    openshift/origin-deployer:latest,
>
>                    openshift/origin-docker-registry:latest,
>
>                    openshift/origin-haproxy-router:latest,
>
>                    openshift/origin-pod:latest
>
>                Checked with: skopeo inspect [--tls-verify=false]
> [--creds=<user>:<pass>] docker://<registry>/<image>
>
>                Default registries searched: docker.io
>
>                Failed connecting to: docker.io
>
>
>
>
> The execution of "playbooks/byo/config.yml" includes checks designed to
> fail early if the requirements of the playbook are not met. One or more of
> these checks failed. To disregard these results,explicitly disable checks
> by setting an Ansible variable:
>
>    openshift_disable_check=docker_image_availability
>
> Failing check names are shown in the failure details above. Some checks
> may be configurable by variables if your requirements are different from
> the defaults; consult check documentation.
>
> Variables can be set in the inventory or passed on the command line using
> the -e flag to ansible-playbook.
>
>
> How can i set a proxy parameter ?
>
>
> Thanks.
>
> Nicolas VAYE
>
>
> -------- Message initial --------
>
> Date: Tue, 27 Mar 2018 05:32:23 +0000
> Objet: Re: [ovirt-users] Any monitoring tool provided?
> Cc: users at ovirt.org <users at ovirt.org<mailto:%22users at ovirt.org%
> 22%20%3cusers at ovirt.org%3e>>
> À: marceloltmm at gmail.com <marceloltmm at gmail.com<mailto:%
> 22marceloltmm at gmail.com%22%20%3cmarceloltmm at gmail.com%3e>>,
> sradco at redhat.com <sradco at redhat.com<mailto:%22sradco at redhat.com%22%20%
> 3csradco at redhat.com%3e>>
> Reply-to: Nicolas Vaye <nicolas.vaye at province-sud.nc>
> De: Nicolas Vaye <nicolas.vaye at province-sud.nc<mailto:Nicolas%20Vaye%20%
> 3cnicolas.vaye at province-sud.nc%3e>>
>
> Hi Shirly,
>
> I'm trying to install ovirt metric store with ViaQ on Origin.
>
> And on https://github.com/oVirt/ovirt-site/pull/1551/files, you mention
> **WARNING** DO NOT INSTALL `libvirt` on the OpenShift machine!
>
>
> on my VM "metric store", i requested rpm for libvirt and here are the
> results :
>
> [root at ometricstore<mailto:root at ometricstore> .ssh]# rpm -qa | grep libvirt
> libvirt-daemon-driver-secret-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-core-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-logical-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-config-network-3.2.0-14.el7_4.9.x86_64
> libvirt-gconfig-1.0.0-1.el7.x86_64
> libvirt-daemon-driver-storage-disk-3.2.0-14.el7_4.9.x86_64
> libvirt-glib-1.0.0-1.el7.x86_64
> libvirt-libs-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-nwfilter-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-gluster-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-rbd-3.2.0-14.el7_4.9.x86_64
> libvirt-gobject-1.0.0-1.el7.x86_64
> libvirt-daemon-driver-interface-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-scsi-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-qemu-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-kvm-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-network-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-iscsi-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-nodedev-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-mpath-3.2.0-14.el7_4.9.x86_64
> libvirt-daemon-driver-storage-3.2.0-14.el7_4.9.x86_64
>
> should i remove all this package ?
>
>
> Also on the web page https://www.ovirt.org/develop/
> release-management/features/metrics/metrics-store-installation/#run-ovirt-
> metrics-store-installation-playbook, you mention
>
> /usr/share/ovirt-engine-metrics/setup/ansible/configure_ovirt_hosts_for_metrics.sh
> --playbook=ovirt-metrics-store-installation.yml
>
>
> But on my hosted engine 4.2.1.7 with ovirt-engine-metrics-1.1.3.3-1.el7.centos.noarch,
> i notice that the script
>
> configure_ovirt_hosts_for_metrics.sh doesn't exist but there is a
> configure_ovirt_machines_for_metrics.sh script.
>
> Is it the good one ?
>
>
>
> Next, you mention :
> Allow connections on the following ports/protocols:
>
>
> + * tcp ports 22, 80, 443, 8443 (openshift console), 9200 (Elasticsearch)
>
>
> following by
>
> ViaQ on Origin requires these [Yum Repos](centos7-viaq.repo).
>
>
>
>
>
>
>
>
>
>
>     +You will need to install the following packages: docker,
> iptables-services.
>
>
> That means that i must uninstall firewalld ? And the ports/protocols will
> be managed by iptables-services ?
>
> What is the command to allow connections on tcp ports 22,80, 443 etc.... ?
>
> Is it managed automatically with  docker or openshift or other program ?
>
>
>
> Thanks for all.
>
>
> Nicolas VAYE
>
>
> -------- Message initial --------
>
> Date: Sun, 25 Mar 2018 12:01:23 +0300
> Objet: Re: [ovirt-users] Any monitoring tool provided?
> Cc: users <users at ovirt.org<mailto:users at ovirt.org><mailto:users%20%
> 3cusers at ovirt.org%3e>>
> À: Marcelo Leandro <marceloltmm at gmail.com<mailto:marceloltmm at gmail.com
> ><mailto:Marcelo%20Leandro%20%3cmarceloltmm at gmail.com%3e>>
> De: Shirly Radco <sradco at redhat.com<mailto:sradco at redhat.com><mailto:
> Shirly%20Radco%20%3csradco at redhat.com%3e>>
>
>
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel<https://www.redhat.com/>
>
> [https://www.redhat.com/files/brand/email/sig-redhat.png]<ht
> tps://red.ht/sig>
> TRIED. TESTED. TRUSTED.<https://redhat.com/trusted>
>
>
> On Fri, Mar 23, 2018 at 10:29 PM, Marcelo Leandro <marceloltmm at gmail.com
> <mailto:marceloltmm at gmail.com><mailto:marceloltmm at gmail.com>> wrote:
> Hello,
>
> I am try this how to:
>
> https://www.ovirt.org/develop/release-management/features/
> metrics/metrics-store-installation/
>
> but when i run this command:
> /usr/share/ovirt-engine-metrics/setup/ansible/
> configure_ovirt_machines_for_metrics.sh  --playbook=ovirt-metrics-
> store-installation.yml
>
> I am had this error mensagem:
> ansible-playbook: error: no such option: --playbook
>
> my version:
>
> ovirt-engine-metrics-1.0.8-1.el7.centos.noarch
>
>
> Hi,
>
> You are using an old rpm.
>
> Please upgrade to latest, ovirt-engine-metrics-1.1.3.3-1.el7.centos.noarch
>
> I also added some documentation that is still in pull request:
>
> Add Viaq installation guide to the oVirt metrics store repo -
> https://github.com/oVirt/ovirt-site/pull/1551 - This one is meaningful. I
> introduced a lot of automation that save time when installing.
>
> Add prerequisites for installing OpenShift Logging -
> https://github.com/oVirt/ovirt-site/pull/1561
>
> Added how to import dashboards examples to kibana -
> https://github.com/oVirt/ovirt-site/pull/1559
>
> Please review them.I'll try to get them merged asap.
>
>
> Anyone can help me?
>
>
> 2018-03-22 16:28 GMT-03:00 Christopher Cox <ccox at endlessnow.com<mailto:cc
> ox at endlessnow.com><mailto:ccox at endlessnow.com>>:
> On 03/21/2018 10:41 PM, Terry hey wrote:
> Dear all,
>
> Now, we can just read how many storage used, cpu usage on ovirt dashboard.
> But is there any monitoring tool for monitoring virtual machine time to
> time?
> If yes, could you guys give me the procedure?
>
>
> A possible option, for a full OS with network connectivity, is to monitor
> the VM like you would any other host.
>
> We use omd/check_mk.
>
> Right now there isn't an oVirt specific monitor plugin for check_mk.
>
> I know what I said is probably pretty obvious, but just in case.
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org<mailto:Users at ovirt.org><mailto:Users at ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org<mailto:Users at ovirt.org><mailto:Users at ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org<mailto:Users at ovirt.org><mailto:Users at ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org<mailto:Users at ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180328/a69757bf/attachment.html>


More information about the Users mailing list