Re: [ovirt-users] Hardware critique

[Alex K]

Hi,

You should be ok with the setup.
I am running around 20 vms (linux and windows, small and medium size) with
the half of your specs. With 10G network replica 3 is ok.

Alex

On Wed, Apr 4, 2018, 16:13 Jayme  wrote:

> I'm spec'ing hardware for a 3-node oVirt build (on somewhat of a budget).
> I plan to do 20-30 Linux VMs most of them very light weight + a couple of
> heavier hitting web and DB servers with frequent rsync backups.  Some have
> a lot of small files from large github repos etc.
>
> 3X of the following:
>
> Dell PowerEdge R720
> 2x 2.9 GHz 8 Core E5-2690 (SR0L0)
> 256GB RAM
> PERC H710
> 2x10GB Nic
>
> Boot/OS will likely be two cheaper small sata/ssd in raid 1.
>
> Gluster bricks comprised of 4x2TB WD Gold 7200RPM SATA HDDs in RAID 10 per
> server.  Using a replica 3 setup (and I'm thinking right now with no
> arbiter for extra redundancy, although I'm not sure what the performance
> hit may be as a result).  Will this allow for two host failure or just one?
>
> I've been really struggling with storage choices, it seems very difficult
> to predict the performance of glusterFS due to the variance in hardware
> (everyone is using something different).  I'm not sure if the performance
> will be adequate enough for my needs.
>
> I will be using an all ready existing Netgear XS716T 10GB switch for
> Gluster storage network.
>
> In addition I plan to build another simple glusterFS storage server that I
> can use to georeplicate the gluster volume to for DR purposes and use
> existing hardware to build an independent standby oVirt host that is able
> to start up a few high priority VMs from the georeplicated glusterFS volume
> if for some reason the primary oVirt cluster/glusterFS volume ever failed.
>
> I would love to hear any advice or critiques on this plan.
>
> Thanks!
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Cannot update Node 4.2 to 4.2.2

[Vincent Royer]

Trying to update my nodes to 4.2.2, having a hard time.

I updated the engine, no problems. Migrated VMs off host 1 and put it into
maintenance.  I do a "check upgrade" in the GUI, it finds an update, but
fails to install.

Drop to CLI and try to do it manually

yum update -y

I get lots of dependency errors for missing packages.   A quick google
shows that I may have the incorrect RPMs installed, and should only have
the ovirt-node-ng-image and appliance rpms. So I try to install only those.

So I think I have the right rpms now


But now when I do a yum update it says there are no packages marked for
update.

How to fix this?   Is there anything I have done wrong that I shouldn't do
on my other hosts?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] How to subscribe to Content Delivery Network in oVirt 4.2.2 Cockpit

[Canglin]

In the documentation - chapter 6 "Installing oVirt Node" version 4.2.2.

Step 13.

Once the installation is complete, log in to the Cockpit user interface 
at https:///HostFQDNorIP/:9090 to subscribe the host to the Content 
Delivery Network. Click *Tools* > *Subscriptions* > *Register System* 
and enter your Customer Portal username and password. The system 
automatically subscribes to the *oVirt Node* entitlement.


I am having a hard time finding this in the cockpit.  Any assistance in 
explaining the benefit of this step and where to find would be 
appreciated.  Thanks



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

[Shirly Radco]

Hi,


I have a updated the installation instructions for installing OpenShift
3.9, based on Rich's work , for the oVirt use case.

Please make sure where you get the 3.10 rpm and disable that repo.

This is the PR that includes the metrics store installation of OpenShift 3.9

https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md

It should be merged soon, but you can use it to install.


Please make sure to add the ansible-inventory-origin-39-aio file as
described below.
These are required parameters for the ansible playbook.


Best regards,

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson  wrote:

> I'm sorry.  I misunderstood the request.
>
> We are in the process of updating the instructions for installing viaq
> logging based on upstream origin 3.9 - https://github.com/ViaQ/Main/p
> ull/37
>
> In the meantime, you can follow along on that PR, and we will have
> instructions very soon.
>
>
> On 04/04/2018 08:26 AM, Rich Megginson wrote:
>
>> On 04/04/2018 08:22 AM, Shirly Radco wrote:
>>
>>>
>>>
>>> --
>>>
>>> SHIRLY RADCO
>>>
>>> BI SeNIOR SOFTWARE ENGINEER
>>>
>>> Red Hat Israel 
>>>
>>> 
>>> TRIED. TESTED. TRUSTED. 
>>>
>>>
>>> On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec > phu...@cnc.sk>> wrote:
>>>
>>> almost the same issue, the versio for openshoft release changed to
>>> 3.9
>>>
>>> Failure summary:
>>>
>>>
>>>   1. Hosts:localhost
>>>  Play: Determine openshift_version to configure on first
>>> master
>>>  Task: For an RPM install, abort when the release
>>> requested does
>>> not match the available version.
>>>  Message:  You requested openshift_release 3.9, which is not
>>> matched by
>>>the latest OpenShift RPM we detected as origin-3.10.0
>>>on host localhost.
>>>We will only install the latest RPMs, so please ensure
>>> you are getting the release
>>>you expect. You may need to adjust your Ansible
>>> inventory, modify the repositories
>>>available on the host, or run the appropriate
>>> OpenShift
>>> upgrade playbook.
>>>
>>>
>>> What is the rpm version installed of OpenShift origin?
>>> Do you perhaps have another repo that includes the OpenShift
>>> origin-3.10.0?
>>>
>>
>> origin is the upstream version of OpenShift, which is unsupported.
>>
>> sudo repoquery -i origin
>>
>> This will tell you which repo it came from
>>
>> You will need to disable that repo and uninstall any packages which came
>> from that repo
>>
>> Another mystery is why it is trying to install origin in the first
>> place.  openshift-ansible with openshift_deployment_type=openshift-enterprise
>> should not try to install origin, it should install packages with names
>> like atomic-openshift-master, atomic-openshift-node, etc.
>>
>>
>>>
>>>
>>> On 04/04/2018 14:18, Shirly Radco wrote:
>>> > Adding Nicolas since he hit the same issue.
>>> >
>>> > --
>>> >
>>> > SHIRLY RADCO
>>> >
>>> > BI SeNIOR SOFTWARE ENGINEER
>>> >
>>> > Red Hat Israel 
>>> >
>>> > 
>>> > TRIED. TESTED. TRUSTED. 
>>> >
>>> >
>>> > On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco >> 
>>> > >> wrote:
>>> >
>>> > Hi Peter,
>>> >
>>> > The installation instructions currently support OpenShift 3.6.
>>> >
>>> > I'm now working on updating them to support 3.9.
>>> >
>>> > You currently have 3.10 installed.
>>> >
>>> > Please install OpenShift 3.9 using this repository
>>> > https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
>>> 
>>> >  >> >
>>> >
>>> > And add the following file to your vm
>>> >
>>> > Run:
>>> > vi /root/ansible-inventory-origin-39-aio
>>> >
>>> > Add:
>>> >
>>> > --
>>> > [OSEv3:children]
>>> > nodes
>>> > masters
>>> > etcd
>>> >
>>> > [OSEv3:vars]
>>> > ansible_connection=local
>>> > openshift_release=v3.9
>>> > openshift_logging_install_logging=true
>>> > short_version=3.9
>>> > openshift_deployment_type=origin
>>> >  

Re: [ovirt-users] Engine reports

[Peter Hudec]

[PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
repoquery -i origin
Repository centos-openshift-origin is listed more than once in the
configuration

Name: origin
Version : 3.7.2
Release : 1.el7.git.0.f0186dd
Architecture: x86_64
Size: 957727742
Packager: CBS 
Group   : Unspecified
URL : https://github.com/openshift/origin
Repository  : centos-openshift-origin37-candidate
Summary : Open Source Container Management by Red Hat
Source  : origin-3.7.2-1.el7.git.0.f0186dd.src.rpm
Description :
OpenShift is a distribution of Kubernetes optimized for enterprise
application
development and deployment. OpenShift adds developer and operational centric
tools on top of Kubernetes to enable rapid application development, easy
deployment and scaling, and long-term lifecycle maintenance for small
and large
teams and applications. It provides a secure and multi-tenant
configuration for
Kubernetes allowing you to safely host many different applications and
workloads
on a unified cluster.

On 04/04/2018 16:26, Rich Megginson wrote:
> sudo repoquery -i origin


-- 
*Peter Hudec*
Infraštruktúrny architekt
phu...@cnc.sk 

*CNC, a.s.*
Borská 6, 841 04 Bratislava
Recepcia: +421 2  35 000 100

Mobil:+421 905 997 203
*www.cnc.sk* 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] 回复：Re: hosted-engine deploy error

[dhy336]

thanks, it is work,  I change my hostname by 
hostnamectl.[root@hosted-engine-test1 ~]# hostnamectl set-hostname 
hosted-engine-test1


- 原始邮件 -
发件人：Martin Sivak 
收件人：dhy336 
抄送人：Simone Tiraboschi , users 
主题：Re: [ovirt-users] hosted-engine deploy error
日期：2018年04月04日 19点29分


Hi,
the hostname is invalid for hosted engine because it is set to
localhost.localdomain.
Check the shell prompt, do you see the localhost there?
[root@localhost ~]# hosted-engine --deploy
You can change the hostname by using many different tools, check
https://fedoramagazine.org/set-hostname-fedora/ for examples. Most of
them (if not all) should be valid for CentOS as well.
The hostname you set must be resolvable to IP and that IP has to point
back to the host you are on.
Best regards
Martin Sivak
On Wed, Apr 4, 2018 at 12:50 PM, dhy336  wrote:
> thanks, but i do not know why is my hostname invalid?
>
>
> 在2018年04月04日 18:41，Simone Tiraboschi 写道：
>
>
> On Wed, Apr 4, 2018 at 12:28 PM,  wrote:
>>
>> Hi,
>>
>> I deloy hosted-engine, by this
>> blog,https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/
>>  but I am facing some error.who  may give me  some advise?
>>
>> [root@localhost ~]# hosted-engine --deploy
>
>
> ^^^
>
> The error is here: please set a valid hostname for your host: the engine VM
> should be able to reach it.
> If you add the host as localhost the engine VM will reach itself and it's
> not what we want.
>
> If you don'y have a working DNS system, hosted-engine-setup will ask about
> injecting an entry for you under /etc/hosts on the engine VM but you still
> need a valid hostname.
>
>
>>
>>
>>
>>
>>   --== STORAGE CONFIGURATION ==--
>>
>>   Please specify the storage you would like to use (glusterfs,
>> iscsi, fc, nfs3, nfs4)[nfs3]:
>>   Please specify the full shared storage connection path to use
>> (example: host:/path): 192.168.122.134:/home/exports/hosted-engine
>>
>>   --== HOST NETWORK CONFIGURATION ==--
>>
>>   iptables was detected on your computer, do you wish setup to
>> configure it? (Yes, No)[Yes]:
>>   Please indicate a pingable gateway IP address [192.168.122.1]:
>>   Please indicate a nic to set ovirtmgmt bridge on: (eth0) [eth0]:
>>
>>   --== VM CONFIGURATION ==--
>>
>>   The following appliance have been found on your system:
>>   [1] - The oVirt Engine Appliance image (OVA) -
>> 4.1-20180124.1.el7.centos
>>   [2] - Directly select an OVA file
>>   Please select an appliance (1, 2) [1]:
>> [ INFO  ] Verifying its sha1sum
>> [ INFO  ] Checking OVF archive content (could take a few minutes depending
>> on archive size)
>> [ INFO  ] Checking OVF XML content (could take a few minutes depending on
>> archive size)
>>   Please specify the console type you would like to use to connect
>> to the VM (vnc, spice) [vnc]:
>> [ INFO  ] Detecting host timezone.
>>   Would you like to use cloud-init to customize the appliance on
>> the first boot (Yes, No)[Yes]?
>>   Would you like to generate on-fly a cloud-init ISO image (of
>> no-cloud type)
>>   or do you have an existing one (Generate, Existing)[Generate]?
>>   Please provide the FQDN you would like to use for the engine
>> appliance.
>>   Note: This will be the FQDN of the engine VM you are now going
>> to launch,
>>   it should not point to the base host or to any other existing
>> machine.
>>   Engine VM FQDN: (leave it empty to skip):  []: engine.tchyp.com
>>   Please provide the domain name you would like to use for the
>> engine appliance.
>>   Engine VM domain: [tchyp.com]
>>   Automatically execute engine-setup on the engine appliance on
>> first boot (Yes, No)[Yes]?
>>   Automatically restart the engine VM as a monitored service after
>> engine-setup (Yes, No)[Yes]?
>>   Enter root password that will be used for the engine appliance
>> (leave it empty to skip):
>> [WARNING] Skipping appliance root password
>>   Enter ssh public key for the root user that will be used for the
>> engine appliance (leave it empty to skip):
>> [WARNING] Skipping appliance root ssh public key
>>   Do you want to enable ssh access for the root user (yes, no,
>> without-password) [yes]:
>> [WARNING] The oVirt engine appliance is not configured with a default
>> password, please consider configuring it via cloud-init
>>   Please specify the size of the VM disk in GB: [58]:
>> [WARNING] Minimum requirements not met by available memory: Required: 4096
>> MB. Available: 3064 MB
>>   Please specify the memory size of the VM in MB (Defaults to
>> maximum available): [3064]:
>> [WARNING] Minimum requirements for memory size not met
>>   Continue with specified memory size? (Yes, No) [No]: yes
>>   

Re: [ovirt-users] Install oVirt node without Internet repository

[Pavol Brilla]

Ovirt-node idea is that all you need to create host for oVirt is already
installated from iso on system.

So yes node has repositories, but you dont need them to add host to engine

Just add ovirt-node as host to engine, all needed packages should be
already ready on node.

On Tue, Apr 3, 2018 at 8:29 PM, G, Maghesh Kumar (Nokia - IN/Bangalore) <
magheshkuma...@nokia.com> wrote:

> Hi,
>
>
>
> As guided I have installed ovirt-node using 1 ISO image. But still we have
> same issue.
>
> Please find attached log for your debugging.
>
>
>
> Also would like to tell SSH from ovirt engine node to ovirt node is
> working fine.
>
>
>
> *From:Ovirt Engine Server*
>
>
>
> [root@ovrit-mgmt host-deploy]#
>
> [root@ovrit-mgmt host-deploy]# ssh 192.175.2.234
>
> root@192.175.2.234's password:
>
> Last login: Tue Apr  3 19:11:03 2018 from ovirt-mgmt.banone.nsn-rdnet.net
>
>
>
>   node status: OK
>
>   See `nodectl check` for more information
>
>
>
> Admin Console: https://192.175.2.234:9090/
>
> [root@kvm04 ~]#
>
>
>
> *From: Ovirt Node*
>
> [root@kvm04 log]# ssh 192.175.2.234
>
> The authenticity of host '192.175.2.234 (192.175.2.234)' can't be
> established.
>
> ECDSA key fingerprint is SHA256:rlMHEDBvLz6GK0LQh2n8blEdwYPtMG
> nl8Hzw3Mo2PMQ.
>
> ECDSA key fingerprint is MD5:3a:69:2b:2c:87:c7:3c:55:
> 3d:13:b8:b1:ac:bd:e7:6a.
>
> Are you sure you want to continue connecting (yes/no)? yes
>
> Warning: Permanently added '192.175.2.234' (ECDSA) to the list of known
> hosts.
>
> root@192.175.2.234's password:
>
> Last login: Tue Apr  3 19:25:43 2018 from ovirt-mgmt.banone.nsn-rdnet.net
>
>
>
>   node status: OK
>
>   See `nodectl check` for more information
>
>
>
> Admin Console: https://192.175.2.234:9090/
>
>
>
> [root@kvm04 ~]#
>
>
>
>
>
> *Repository: Still repository is pointing to internet*
>
>
>
> [root@kvm04 ~]# cd /etc/yum.repos.d/
>
> [root@kvm04 yum.repos.d]# ls -ltr
>
> total 40
>
> -rw-r--r--. 1 root root  308 Mar 29 11:42 ovirt-4.2.repo
>
> -rw-r--r--. 1 root root 2571 Mar 29 11:42 ovirt-4.2-dependencies.repo
>
> -rw-r--r--. 1 root root  367 Mar 29 11:42 cockpit-preview-epel-7.repo
>
> -rw-r--r--. 1 root root 3830 Mar 29 11:42 CentOS-Vault.repo
>
> -rw-r--r--. 1 root root 1331 Mar 29 11:42 CentOS-Sources.repo
>
> -rw-r--r--. 1 root root  630 Mar 29 11:42 CentOS-Media.repo
>
> -rw-r--r--. 1 root root  314 Mar 29 11:42 CentOS-fasttrack.repo
>
> -rw-r--r--. 1 root root 1309 Mar 29 11:42 CentOS-CR.repo
>
> -rw-r--r--. 1 root root  649 Mar 29 11:42 CentOS-Debuginfo.repo
>
> -rw-r--r--. 1 root root 1694 Mar 29 11:42 CentOS-Base.repo
>
> [root@kvm04 yum.repos.d]#
>
>
>
>
>
> Regards,
>
> Maghesh
>
>
>
> *From:* Pavol Brilla [mailto:pbri...@redhat.com]
> *Sent:* Tuesday, April 03, 2018 12:32 PM
> *To:* G, Maghesh Kumar (Nokia - IN/Bangalore) 
> *Cc:* users@ovirt.org; in...@ovirt.org
> *Subject:* Re: [ovirt-users] Install oVirt node without Internet
> repository
>
>
>
> Ovirt-node should provide all you need as host on 1 ISO:
>
>
>
> https://www.ovirt.org/node/
>
>
>
> On Mon, Apr 2, 2018 at 12:31 PM, G, Maghesh Kumar (Nokia - IN/Bangalore) <
> magheshkuma...@nokia.com> wrote:
>
> Hi
>
>
>
> Description of problem:
>
> Cannot add host - install fails & Install oVirt node without Internet 
> repository
>
>
>
> Version: Ovirt-4.2
>
> Host is installed with RHEL 7.4
>
>
>
> Actual results:
>
> Host KVM02 installation failed. Command returned failure code 1 during SSH 
> session 'root@192.175.2.231'
>
>
>
> I found that right now on my oVirt Nodes in my test environment *does not
> NOT connect to the internet.*..
>
> Basically, i need the offline repository to access from oVirt nodes
> without Internet access.
>
>
>
> Please guide us how to proceed
>
>
>
> Regards,
>
> Maghesh
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
>
> --
>
> *PAVOL BRILLA*
>
> RHV QUALITY ENGINEER, CLOUD
>
> Red Hat Czech Republic, Brno 
>
> 
>
> *TRIED. TESTED. TRUSTED.* 
>
>
>



-- 

PAVOL BRILLA

RHV QUALITY ENGINEER, CLOUD

Red Hat Czech Republic, Brno 

TRIED. TESTED. TRUSTED. 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

[Rich Megginson]

I'm sorry.  I misunderstood the request.

We are in the process of updating the instructions for installing viaq 
logging based on upstream origin 3.9 - https://github.com/ViaQ/Main/pull/37


In the meantime, you can follow along on that PR, and we will have 
instructions very soon.


On 04/04/2018 08:26 AM, Rich Megginson wrote:

On 04/04/2018 08:22 AM, Shirly Radco wrote:



--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 


TRIED. TESTED. TRUSTED. 


On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec > wrote:


    almost the same issue, the versio for openshoft release changed 
to 3.9


    Failure summary:


      1. Hosts:    localhost
         Play:     Determine openshift_version to configure on first
    master
         Task:     For an RPM install, abort when the release
    requested does
    not match the available version.
         Message:  You requested openshift_release 3.9, which is not
    matched by
                   the latest OpenShift RPM we detected as origin-3.10.0
                   on host localhost.
                   We will only install the latest RPMs, so please 
ensure

    you are getting the release
                   you expect. You may need to adjust your Ansible
    inventory, modify the repositories
                   available on the host, or run the appropriate 
OpenShift

    upgrade playbook.


What is the rpm version installed of OpenShift origin?
Do you perhaps have another repo that includes the OpenShift 
origin-3.10.0?


origin is the upstream version of OpenShift, which is unsupported.

sudo repoquery -i origin

This will tell you which repo it came from

You will need to disable that repo and uninstall any packages which 
came from that repo


Another mystery is why it is trying to install origin in the first 
place.  openshift-ansible with 
openshift_deployment_type=openshift-enterprise should not try to 
install origin, it should install packages with names like 
atomic-openshift-master, atomic-openshift-node, etc.






    On 04/04/2018 14:18, Shirly Radco wrote:
    > Adding Nicolas since he hit the same issue.
    >
    > --
    >
    > SHIRLY RADCO
    >
    > BI SeNIOR SOFTWARE ENGINEER
    >
    > Red Hat Israel 
    >
    > 
    > TRIED. TESTED. TRUSTED. 
    >
    >
    > On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco 

    > >> wrote:
    >
    >     Hi Peter,
    >
    >     The installation instructions currently support OpenShift 3.6.
    >
    >     I'm now working on updating them to support 3.9.
    >
    >     You currently have 3.10 installed.
    >
    >     Please install OpenShift 3.9 using this repository
    > https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo

    >  >
    >
    >     And add the following file to your vm
    >
    >     Run:
    >     vi /root/ansible-inventory-origin-39-aio
    >
    >     Add:
    >
    >     --
    >     [OSEv3:children]
    >     nodes
    >     masters
    >     etcd
    >
    >     [OSEv3:vars]
    >     ansible_connection=local
    >     openshift_release=v3.9
    >     openshift_logging_install_logging=true
    >     short_version=3.9
    >     openshift_deployment_type=origin
    >  openshift_master_identity_providers=[{'mappingMethod': 'lookup',
    >     'challenge': 'true', 'login': 'true', 'kind':
    >     'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
    >     # bug - doesn't use correct tag
    >     openshift_logging_image_version=v3.9
    >  openshift_logging_elasticsearch_proxy_image_version=v1.0.0
    >
    >     openshift_logging_es_allow_external=True
    >     openshift_logging_use_mux=True
    >     openshift_logging_mux_allow_external=True
    >  openshift_logging_mux_file_buffer_storage_type=hostmount
    >  openshift_logging_elasticsearch_storage_type=hostmount
    >
 openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
    >
    >     [nodes]
    >     localhost storage=True openshift_node_labels="{'region':
    'infra'}"
    >     openshift_schedulable=True
    >
    >     [masters]
    >     localhost storage=True openshift_node_labels="{'region':
    'infra'}"
    >     openshift_schedulable=True
    >
    >     [etcd]
    >     localhost storage=True openshift_node_labels="{'region':
    'infra'}"
    >     openshift_schedulable=True
    >
    >
    >     
    >
    >     Save and exit.
    >
    >
    >     ***Please make sure that you use /var as your Elasticsearch
    >     persistent storage directory.
    >
    >     And when you run the 

Re: [ovirt-users] Engine reports

[Rich Megginson]

On 04/04/2018 08:22 AM, Shirly Radco wrote:



--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

  
TRIED. TESTED. TRUSTED. 


On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec > wrote:


almost the same issue, the versio for openshoft release changed to 3.9

Failure summary:


  1. Hosts:    localhost
     Play:     Determine openshift_version to configure on first
master
     Task:     For an RPM install, abort when the release
requested does
not match the available version.
     Message:  You requested openshift_release 3.9, which is not
matched by
               the latest OpenShift RPM we detected as origin-3.10.0
               on host localhost.
               We will only install the latest RPMs, so please ensure
you are getting the release
               you expect. You may need to adjust your Ansible
inventory, modify the repositories
               available on the host, or run the appropriate OpenShift
upgrade playbook.


What is the rpm version installed of OpenShift origin?
Do you perhaps have another repo that includes the OpenShift 
origin-3.10.0?


origin is the upstream version of OpenShift, which is unsupported.

sudo repoquery -i origin

This will tell you which repo it came from

You will need to disable that repo and uninstall any packages which came 
from that repo


Another mystery is why it is trying to install origin in the first 
place.  openshift-ansible with 
openshift_deployment_type=openshift-enterprise should not try to install 
origin, it should install packages with names like 
atomic-openshift-master, atomic-openshift-node, etc.






On 04/04/2018 14:18, Shirly Radco wrote:
> Adding Nicolas since he hit the same issue.
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
>
> 
> TRIED. TESTED. TRUSTED. 
>
>
> On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco 
> >> wrote:
>
>     Hi Peter,
>
>     The installation instructions currently support OpenShift 3.6.
>
>     I'm now working on updating them to support 3.9.
>
>     You currently have 3.10 installed.
>
>     Please install OpenShift 3.9 using this repository
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo

>     >
>
>     And add the following file to your vm
>
>     Run:
>     vi /root/ansible-inventory-origin-39-aio
>
>     Add:
>
>     --
>     [OSEv3:children]
>     nodes
>     masters
>     etcd
>
>     [OSEv3:vars]
>     ansible_connection=local
>     openshift_release=v3.9
>     openshift_logging_install_logging=true
>     short_version=3.9
>     openshift_deployment_type=origin
>     openshift_master_identity_providers=[{'mappingMethod': 'lookup',
>     'challenge': 'true', 'login': 'true', 'kind':
>     'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
>     # bug - doesn't use correct tag
>     openshift_logging_image_version=v3.9
>     openshift_logging_elasticsearch_proxy_image_version=v1.0.0
>
>     openshift_logging_es_allow_external=True
>     openshift_logging_use_mux=True
>     openshift_logging_mux_allow_external=True
>     openshift_logging_mux_file_buffer_storage_type=hostmount
>     openshift_logging_elasticsearch_storage_type=hostmount
>   
 openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
>
>     [nodes]
>     localhost storage=True openshift_node_labels="{'region':
'infra'}"
>     openshift_schedulable=True
>
>     [masters]
>     localhost storage=True openshift_node_labels="{'region':
'infra'}"
>     openshift_schedulable=True
>
>     [etcd]
>     localhost storage=True openshift_node_labels="{'region':
'infra'}"
>     openshift_schedulable=True
>
>
>     
>
>     Save and exit.
>
>
>     ***Please make sure that you use /var as your Elasticsearch
>     persistent storage directory.
>
>     And when you run the OpenShift ansible
>   
 
(https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible


>   
 

Re: [ovirt-users] Engine reports

[Shirly Radco]

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec  wrote:

> almost the same issue, the versio for openshoft release changed to 3.9
>
> Failure summary:
>
>
>   1. Hosts:localhost
>  Play: Determine openshift_version to configure on first master
>  Task: For an RPM install, abort when the release requested does
> not match the available version.
>  Message:  You requested openshift_release 3.9, which is not matched by
>the latest OpenShift RPM we detected as origin-3.10.0
>on host localhost.
>We will only install the latest RPMs, so please ensure
> you are getting the release
>you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>available on the host, or run the appropriate OpenShift
> upgrade playbook.
>
>
What is the rpm version installed of OpenShift origin?
Do you perhaps have another repo that includes the OpenShift origin-3.10.0?



> On 04/04/2018 14:18, Shirly Radco wrote:
> > Adding Nicolas since he hit the same issue.
> >
> > --
> >
> > SHIRLY RADCO
> >
> > BI SeNIOR SOFTWARE ENGINEER
> >
> > Red Hat Israel 
> >
> > 
> > TRIED. TESTED. TRUSTED. 
> >
> >
> > On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco  > > wrote:
> >
> > Hi Peter,
> >
> > The installation instructions currently support OpenShift 3.6.
> >
> > I'm now working on updating them to support 3.9.
> >
> > You currently have 3.10 installed.
> >
> > Please install OpenShift 3.9 using this repository
> > https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
> > 
> >
> > And add the following file to your vm
> >
> > Run:
> > vi /root/ansible-inventory-origin-39-aio
> >
> > Add:
> >
> > --
> > [OSEv3:children]
> > nodes
> > masters
> > etcd
> >
> > [OSEv3:vars]
> > ansible_connection=local
> > openshift_release=v3.9
> > openshift_logging_install_logging=true
> > short_version=3.9
> > openshift_deployment_type=origin
> > openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> > 'challenge': 'true', 'login': 'true', 'kind':
> > 'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> > # bug - doesn't use correct tag
> > openshift_logging_image_version=v3.9
> > openshift_logging_elasticsearch_proxy_image_version=v1.0.0
> >
> > openshift_logging_es_allow_external=True
> > openshift_logging_use_mux=True
> > openshift_logging_mux_allow_external=True
> > openshift_logging_mux_file_buffer_storage_type=hostmount
> > openshift_logging_elasticsearch_storage_type=hostmount
> > openshift_logging_elasticsearch_hostmount_path=/
> var/lib/elasticsearch
> >
> > [nodes]
> > localhost storage=True openshift_node_labels="{'region': 'infra'}"
> > openshift_schedulable=True
> >
> > [masters]
> > localhost storage=True openshift_node_labels="{'region': 'infra'}"
> > openshift_schedulable=True
> >
> > [etcd]
> > localhost storage=True openshift_node_labels="{'region': 'infra'}"
> > openshift_schedulable=True
> >
> >
> > 
> >
> > Save and exit.
> >
> >
> > ***Please make sure that you use /var as your Elasticsearch
> > persistent storage directory.
> >
> > And when you run the OpenShift ansible
> > (https://www.ovirt.org/develop/release-management/
> features/metrics/setting-up-viaq-logging/#running-ansible
> >  features/metrics/setting-up-viaq-logging/#running-ansible>)
> > use the file you just created like this:
> >
> > # cd /usr/share/ansible/openshift-ansible
> > # (or wherever you cloned the git repo if using git)
> > ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> > @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> > playbooks/byo/config.yml
> >
> > Best regards,
> >
> > --
> >
> > SHIRLY RADCO
> >
> > BI SeNIOR SOFTWARE ENGINEER
> >
> > Red Hat Israel 
> >
> > 
> > TRIED. TESTED. TRUSTED. 
> >
> >
> > On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  > > wrote:
> >
> > Tried to install ovirt metrics, but got error
> >
> > ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> > @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> > playbooks/byo/config.yml
> >
> >   1. Hosts:localhost
> >  Play: Determine openshift_version to 

Re: [ovirt-users] Engine reports

[Peter Hudec]

almost the same issue, the versio for openshoft release changed to 3.9

Failure summary:


  1. Hosts:localhost
 Play: Determine openshift_version to configure on first master
 Task: For an RPM install, abort when the release requested does
not match the available version.
 Message:  You requested openshift_release 3.9, which is not matched by
   the latest OpenShift RPM we detected as origin-3.10.0
   on host localhost.
   We will only install the latest RPMs, so please ensure
you are getting the release
   you expect. You may need to adjust your Ansible
inventory, modify the repositories
   available on the host, or run the appropriate OpenShift
upgrade playbook.


On 04/04/2018 14:18, Shirly Radco wrote:
> Adding Nicolas since he hit the same issue.
> 
> --
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
>   
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco  > wrote:
> 
> Hi Peter,
> 
> The installation instructions currently support OpenShift 3.6.
> 
> I'm now working on updating them to support 3.9.
> 
> You currently have 3.10 installed.
> 
> Please install OpenShift 3.9 using this repository 
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
> 
> 
> And add the following file to your vm 
> 
> Run:
> vi /root/ansible-inventory-origin-39-aio
> 
> Add:
> 
> --
> [OSEv3:children]
> nodes
> masters
> etcd
> 
> [OSEv3:vars]
> ansible_connection=local
> openshift_release=v3.9
> openshift_logging_install_logging=true
> short_version=3.9
> openshift_deployment_type=origin
> openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> 'challenge': 'true', 'login': 'true', 'kind':
> 'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> # bug - doesn't use correct tag
> openshift_logging_image_version=v3.9
> openshift_logging_elasticsearch_proxy_image_version=v1.0.0
> 
> openshift_logging_es_allow_external=True
> openshift_logging_use_mux=True
> openshift_logging_mux_allow_external=True
> openshift_logging_mux_file_buffer_storage_type=hostmount
> openshift_logging_elasticsearch_storage_type=hostmount
> openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
> 
> [nodes]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [masters]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [etcd]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> 
> 
> 
> Save and exit.
> 
> 
> ***Please make sure that you use /var as your Elasticsearch
> persistent storage directory.
> 
> And when you run the OpenShift ansible
> 
> (https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible
> 
> )
> use the file you just created like this:
> 
> # cd /usr/share/ansible/openshift-ansible
> # (or wherever you cloned the git repo if using git)
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> playbooks/byo/config.yml
> 
> Best regards,
> 
> --
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
>   
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  > wrote:
> 
> Tried to install ovirt metrics, but got error
> 
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
> 
>   1. Hosts:    localhost
>      Play:     Determine openshift_version to configure on first
> master
>      Task:     For an RPM install, abort when the release
> requested does
> not match the available version.
>      Message:  You requested openshift_release 3.7, which is not
> matched by
>                the latest OpenShift RPM we detected as origin-3.10.0
>                on host localhost.
>                We will only install the latest RPMs, so please
> ensure
> you are getting the release
>                you expect. You may need to adjust your Ansible
> 

[ovirt-users] Decrease downtime for HA

[Daniel Menzel]

Hello,

we're successfully using a setup with 4 Nodes and a replicated Gluster 
for storage. The engine is self hosted. What we're dealing with at the 
moment is the high availability: If a node fails (for example simulated 
by a forced power loss) the engine comes back up online withing ~2min. 
But guests (having the HA option enabled) come back online only after a 
very long grace time of ~5min. As we have a reliable network (40 GbE) 
and reliable servers I think that the default grace times are way too 
high for us - is there any possibility to change those values?


Thanks in advance!
Daniel

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

[Peter Hudec]

Hi SHIRLY,

I had clean server before installing. I will try to follow your advice.

Peter

On 04/04/2018 14:17, Shirly Radco wrote:
> Hi Peter,
> 
> The installation instructions currently support OpenShift 3.6.
> 
> I'm now working on updating them to support 3.9.
> 
> You currently have 3.10 installed.
> 
> Please install OpenShift 3.9 using this repository 
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
> 
> And add the following file to your vm 
> 
> Run:
> vi /root/ansible-inventory-origin-39-aio
> 
> Add:
> 
> --
> [OSEv3:children]
> nodes
> masters
> etcd
> 
> [OSEv3:vars]
> ansible_connection=local
> openshift_release=v3.9
> openshift_logging_install_logging=true
> short_version=3.9
> openshift_deployment_type=origin
> openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> 'challenge': 'true', 'login': 'true', 'kind':
> 'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> # bug - doesn't use correct tag
> openshift_logging_image_version=v3.9
> openshift_logging_elasticsearch_proxy_image_version=v1.0.0
> 
> openshift_logging_es_allow_external=True
> openshift_logging_use_mux=True
> openshift_logging_mux_allow_external=True
> openshift_logging_mux_file_buffer_storage_type=hostmount
> openshift_logging_elasticsearch_storage_type=hostmount
> openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
> 
> [nodes]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [masters]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [etcd]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> 
> 
> 
> Save and exit.
> 
> 
> ***Please make sure that you use /var as your Elasticsearch persistent
> storage directory.
> 
> And when you run the OpenShift ansible
> (https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible)
> use the file you just created like this:
> 
> # cd /usr/share/ansible/openshift-ansible
> # (or wherever you cloned the git repo if using git)
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> playbooks/byo/config.yml
> 
> Best regards,
> 
> --
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
>   
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  > wrote:
> 
> Tried to install ovirt metrics, but got error
> 
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
> 
>   1. Hosts:    localhost
>      Play:     Determine openshift_version to configure on first master
>      Task:     For an RPM install, abort when the release requested does
> not match the available version.
>      Message:  You requested openshift_release 3.7, which is not
> matched by
>                the latest OpenShift RPM we detected as origin-3.10.0
>                on host localhost.
>                We will only install the latest RPMs, so please ensure
> you are getting the release
>                you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>                available on the host, or run the appropriate OpenShift
> upgrade playbook.
> 
>         regards
>                 Peter
> 
> 
> On 04/04/2018 09:13, Fred Rolland wrote:
> > Hi,
> >
> > Check these links:
> >
> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> 
> > 
> https://ovirt.org/develop/release-management/features/metrics/metrics-store/
> 
> 
> >
> > Regards,
> > Fred
> >
> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> >  
>  >>
> > wrote:
> >
> >     Hi,
> >
> >     I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> >     take the reports? I version 3.5, we had Jasper reports module using
> >     which we could take utilization reports. Can we do something similar
> >     here?
> >
> >     --
> >
> >     Thanks & Regards,
> >
> >
> >     Anantha Raghava
> >
> >
> >     Do not print this e-mail unless required. Save Paper & trees.
> >
> >
> >     ___
> >     Users mailing list
> >     Users@ovirt.org 

[ovirt-users] Hardware critique

[Jayme]

I'm spec'ing hardware for a 3-node oVirt build (on somewhat of a budget).
I plan to do 20-30 Linux VMs most of them very light weight + a couple of
heavier hitting web and DB servers with frequent rsync backups.  Some have
a lot of small files from large github repos etc.

3X of the following:

Dell PowerEdge R720
2x 2.9 GHz 8 Core E5-2690 (SR0L0)
256GB RAM
PERC H710
2x10GB Nic

Boot/OS will likely be two cheaper small sata/ssd in raid 1.

Gluster bricks comprised of 4x2TB WD Gold 7200RPM SATA HDDs in RAID 10 per
server.  Using a replica 3 setup (and I'm thinking right now with no
arbiter for extra redundancy, although I'm not sure what the performance
hit may be as a result).  Will this allow for two host failure or just one?

I've been really struggling with storage choices, it seems very difficult
to predict the performance of glusterFS due to the variance in hardware
(everyone is using something different).  I'm not sure if the performance
will be adequate enough for my needs.

I will be using an all ready existing Netgear XS716T 10GB switch for
Gluster storage network.

In addition I plan to build another simple glusterFS storage server that I
can use to georeplicate the gluster volume to for DR purposes and use
existing hardware to build an independent standby oVirt host that is able
to start up a few high priority VMs from the georeplicated glusterFS volume
if for some reason the primary oVirt cluster/glusterFS volume ever failed.

I would love to hear any advice or critiques on this plan.

Thanks!
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

[Shirly Radco]

Adding Nicolas since he hit the same issue.

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco  wrote:

> Hi Peter,
>
> The installation instructions currently support OpenShift 3.6.
>
> I'm now working on updating them to support 3.9.
>
> You currently have 3.10 installed.
>
> Please install OpenShift 3.9 using this repository
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
>
> And add the following file to your vm
>
> Run:
> vi /root/ansible-inventory-origin-39-aio
>
> Add:
>
> --
> [OSEv3:children]
> nodes
> masters
> etcd
>
> [OSEv3:vars]
> ansible_connection=local
> openshift_release=v3.9
> openshift_logging_install_logging=true
> short_version=3.9
> openshift_deployment_type=origin
> openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> 'challenge': 'true', 'login': 'true', 'kind': '
> AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> # bug - doesn't use correct tag
> openshift_logging_image_version=v3.9
> openshift_logging_elasticsearch_proxy_image_version=v1.0.0
>
> openshift_logging_es_allow_external=True
> openshift_logging_use_mux=True
> openshift_logging_mux_allow_external=True
> openshift_logging_mux_file_buffer_storage_type=hostmount
> openshift_logging_elasticsearch_storage_type=hostmount
> openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
>
> [nodes]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
>
> [masters]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
>
> [etcd]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
>
>
> 
>
> Save and exit.
>
>
> ***Please make sure that you use /var as your Elasticsearch persistent
> storage directory.
>
> And when you run the OpenShift ansible (https://www.ovirt.org/
> develop/release-management/features/metrics/setting-up-
> viaq-logging/#running-ansible) use the file you just created like this:
>
> # cd /usr/share/ansible/openshift-ansible
> # (or wherever you cloned the git repo if using git)
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> playbooks/byo/config.yml
>
> Best regards,
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
> 
> TRIED. TESTED. TRUSTED. 
>
> On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  wrote:
>
>> Tried to install ovirt metrics, but got error
>>
>> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
>> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
>> playbooks/byo/config.yml
>>
>>   1. Hosts:localhost
>>  Play: Determine openshift_version to configure on first master
>>  Task: For an RPM install, abort when the release requested does
>> not match the available version.
>>  Message:  You requested openshift_release 3.7, which is not matched
>> by
>>the latest OpenShift RPM we detected as origin-3.10.0
>>on host localhost.
>>We will only install the latest RPMs, so please ensure
>> you are getting the release
>>you expect. You may need to adjust your Ansible
>> inventory, modify the repositories
>>available on the host, or run the appropriate OpenShift
>> upgrade playbook.
>>
>> regards
>> Peter
>>
>>
>> On 04/04/2018 09:13, Fred Rolland wrote:
>> > Hi,
>> >
>> > Check these links:
>> >
>> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
>> > https://ovirt.org/develop/release-management/features/metric
>> s/metrics-store/
>> >
>> > Regards,
>> > Fred
>> >
>> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
>> > >
>> > wrote:
>> >
>> > Hi,
>> >
>> > I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
>> > take the reports? I version 3.5, we had Jasper reports module using
>> > which we could take utilization reports. Can we do something similar
>> > here?
>> >
>> > --
>> >
>> > Thanks & Regards,
>> >
>> >
>> > Anantha Raghava
>> >
>> >
>> > Do not print this e-mail unless required. Save Paper & trees.
>> >
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org 
>> > http://lists.ovirt.org/mailman/listinfo/users
>> > 
>> >
>> >
>> >
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>>
>> --
>> *Peter Hudec*
>> 

Re: [ovirt-users] Engine reports

[Shirly Radco]

Hi Peter,

The installation instructions currently support OpenShift 3.6.

I'm now working on updating them to support 3.9.

You currently have 3.10 installed.

Please install OpenShift 3.9 using this repository
https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo

And add the following file to your vm

Run:
vi /root/ansible-inventory-origin-39-aio

Add:

--
[OSEv3:children]
nodes
masters
etcd

[OSEv3:vars]
ansible_connection=local
openshift_release=v3.9
openshift_logging_install_logging=true
short_version=3.9
openshift_deployment_type=origin
openshift_master_identity_providers=[{'mappingMethod': 'lookup',
'challenge': 'true', 'login': 'true', 'kind':
'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
# bug - doesn't use correct tag
openshift_logging_image_version=v3.9
openshift_logging_elasticsearch_proxy_image_version=v1.0.0

openshift_logging_es_allow_external=True
openshift_logging_use_mux=True
openshift_logging_mux_allow_external=True
openshift_logging_mux_file_buffer_storage_type=hostmount
openshift_logging_elasticsearch_storage_type=hostmount
openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch

[nodes]
localhost storage=True openshift_node_labels="{'region': 'infra'}"
openshift_schedulable=True

[masters]
localhost storage=True openshift_node_labels="{'region': 'infra'}"
openshift_schedulable=True

[etcd]
localhost storage=True openshift_node_labels="{'region': 'infra'}"
openshift_schedulable=True




Save and exit.


***Please make sure that you use /var as your Elasticsearch persistent
storage directory.

And when you run the OpenShift ansible (
https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible)
use the file you just created like this:

# cd /usr/share/ansible/openshift-ansible
# (or wherever you cloned the git repo if using git)
ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e @/root/vars.yaml
-i /root/*ansible-inventory-origin-39-aio* playbooks/byo/config.yml

Best regards,

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  wrote:

> Tried to install ovirt metrics, but got error
>
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
>
>   1. Hosts:localhost
>  Play: Determine openshift_version to configure on first master
>  Task: For an RPM install, abort when the release requested does
> not match the available version.
>  Message:  You requested openshift_release 3.7, which is not matched by
>the latest OpenShift RPM we detected as origin-3.10.0
>on host localhost.
>We will only install the latest RPMs, so please ensure
> you are getting the release
>you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>available on the host, or run the appropriate OpenShift
> upgrade playbook.
>
> regards
> Peter
>
>
> On 04/04/2018 09:13, Fred Rolland wrote:
> > Hi,
> >
> > Check these links:
> >
> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> > https://ovirt.org/develop/release-management/features/
> metrics/metrics-store/
> >
> > Regards,
> > Fred
> >
> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> > >
> > wrote:
> >
> > Hi,
> >
> > I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> > take the reports? I version 3.5, we had Jasper reports module using
> > which we could take utilization reports. Can we do something similar
> > here?
> >
> > --
> >
> > Thanks & Regards,
> >
> >
> > Anantha Raghava
> >
> >
> > Do not print this e-mail unless required. Save Paper & trees.
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org 
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
> --
> *Peter Hudec*
> Infraštruktúrny architekt
> phu...@cnc.sk 
>
> *CNC, a.s.*
> Borská 6, 841 04 Bratislava
> Recepcia: +421 2  35 000 100
>
> Mobil:+421 905 997 203
> *www.cnc.sk* 
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] 【help】Build a local development environment

[Phillip Bailey]

Hi,

You should be able to find all of the necessary details for setting up your
development environment in the ovirt-engine README [1], except for one
additional step [2] that requires you to do a little extra work on the
database.

I hope this helps!

-Phillip Bailey

[1] https://github.com/oVirt/ovirt-engine/blob/master/README.adoc
[2] http://lists.ovirt.org/pipermail/devel/2018-January/032452.html

On Tue, Apr 3, 2018 at 7:22 AM, TT-mao <1523688...@qq.com> wrote:

> Hi, guys:
> I am currently trying to build an ovirt development environment
> (including engine and vdsm) locally using official documentation, but it
> will never build successfully.
> First, I successfully built the rpm package through (
> https://www.ovirt.org/develop/developer-guide/vdsm/developers/)
> But the vdsm rpm package that I built can't be applied to the engine
> environment. Add hosts on the ovirt gui interface. The engine backend will
> reinstall vdsm.
>
> How do you create a local development environment?
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] External Provider https (unknown error)

[Stefan Wendler]

Hi,

I am currently trying to attach Glance (OpenStack Image) and Cinder
(OpenStack Volume) as external provider and am facing a problem when
trying to use https in the Provider-URL on an ovirt 3.6 and 4.1 cluster.

The Provider-URL I am using is in the form:
https://:9292 (or port 8776 for Cinder -  is either a fqdn
or an IP-Address)

Whenever I press the "Test" button in the "Add Provider" dialog I get
the message "Test Failed (unknown error)." There is no entry in any
logfile whatsoever (at least not in any logs that are associated with
ovirt). I would expect an ssl cert dialog here. I can telnet to the
destination ports from the engine and the nodes so Clance and Cinder are
reachable

I have also read that this might happen, if there is a corrupted
/var/lib/ovirt-engine/external_truststore
But this file is not even existing and when i create it by hand, it is
not touched.

How can I get this to work or even get an error message that gives me a
hint where to look?

Thanks for your support,
Stefan





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine deploy error

[Martin Sivak]

Hi,

the hostname is invalid for hosted engine because it is set to
localhost.localdomain.

Check the shell prompt, do you see the localhost there?
[root@localhost ~]# hosted-engine --deploy

You can change the hostname by using many different tools, check
https://fedoramagazine.org/set-hostname-fedora/ for examples. Most of
them (if not all) should be valid for CentOS as well.

The hostname you set must be resolvable to IP and that IP has to point
back to the host you are on.

Best regards

Martin Sivak

On Wed, Apr 4, 2018 at 12:50 PM, dhy336  wrote:
> thanks, but i do not know why is my hostname invalid?
>
>
> 在2018年04月04日 18:41，Simone Tiraboschi 写道：
>
>
> On Wed, Apr 4, 2018 at 12:28 PM,  wrote:
>>
>> Hi,
>>
>> I deloy hosted-engine, by this
>> blog,https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/
>>  but I am facing some error.who  may give me  some advise?
>>
>> [root@localhost ~]# hosted-engine --deploy
>
>
> ^^^
>
> The error is here: please set a valid hostname for your host: the engine VM
> should be able to reach it.
> If you add the host as localhost the engine VM will reach itself and it's
> not what we want.
>
> If you don'y have a working DNS system, hosted-engine-setup will ask about
> injecting an entry for you under /etc/hosts on the engine VM but you still
> need a valid hostname.
>
>
>>
>>
>>
>>
>>   --== STORAGE CONFIGURATION ==--
>>
>>   Please specify the storage you would like to use (glusterfs,
>> iscsi, fc, nfs3, nfs4)[nfs3]:
>>   Please specify the full shared storage connection path to use
>> (example: host:/path): 192.168.122.134:/home/exports/hosted-engine
>>
>>   --== HOST NETWORK CONFIGURATION ==--
>>
>>   iptables was detected on your computer, do you wish setup to
>> configure it? (Yes, No)[Yes]:
>>   Please indicate a pingable gateway IP address [192.168.122.1]:
>>   Please indicate a nic to set ovirtmgmt bridge on: (eth0) [eth0]:
>>
>>   --== VM CONFIGURATION ==--
>>
>>   The following appliance have been found on your system:
>>   [1] - The oVirt Engine Appliance image (OVA) -
>> 4.1-20180124.1.el7.centos
>>   [2] - Directly select an OVA file
>>   Please select an appliance (1, 2) [1]:
>> [ INFO  ] Verifying its sha1sum
>> [ INFO  ] Checking OVF archive content (could take a few minutes depending
>> on archive size)
>> [ INFO  ] Checking OVF XML content (could take a few minutes depending on
>> archive size)
>>   Please specify the console type you would like to use to connect
>> to the VM (vnc, spice) [vnc]:
>> [ INFO  ] Detecting host timezone.
>>   Would you like to use cloud-init to customize the appliance on
>> the first boot (Yes, No)[Yes]?
>>   Would you like to generate on-fly a cloud-init ISO image (of
>> no-cloud type)
>>   or do you have an existing one (Generate, Existing)[Generate]?
>>   Please provide the FQDN you would like to use for the engine
>> appliance.
>>   Note: This will be the FQDN of the engine VM you are now going
>> to launch,
>>   it should not point to the base host or to any other existing
>> machine.
>>   Engine VM FQDN: (leave it empty to skip):  []: engine.tchyp.com
>>   Please provide the domain name you would like to use for the
>> engine appliance.
>>   Engine VM domain: [tchyp.com]
>>   Automatically execute engine-setup on the engine appliance on
>> first boot (Yes, No)[Yes]?
>>   Automatically restart the engine VM as a monitored service after
>> engine-setup (Yes, No)[Yes]?
>>   Enter root password that will be used for the engine appliance
>> (leave it empty to skip):
>> [WARNING] Skipping appliance root password
>>   Enter ssh public key for the root user that will be used for the
>> engine appliance (leave it empty to skip):
>> [WARNING] Skipping appliance root ssh public key
>>   Do you want to enable ssh access for the root user (yes, no,
>> without-password) [yes]:
>> [WARNING] The oVirt engine appliance is not configured with a default
>> password, please consider configuring it via cloud-init
>>   Please specify the size of the VM disk in GB: [58]:
>> [WARNING] Minimum requirements not met by available memory: Required: 4096
>> MB. Available: 3064 MB
>>   Please specify the memory size of the VM in MB (Defaults to
>> maximum available): [3064]:
>> [WARNING] Minimum requirements for memory size not met
>>   Continue with specified memory size? (Yes, No) [No]: yes
>>   The following CPU types are supported by this host:
>>   - model_Haswell-noTSX: Intel Haswell-noTSX Family
>>   - model_SandyBridge: Intel SandyBridge Family
>>   - model_Westmere: Intel Westmere Family
>>   - model_Nehalem: Intel Nehalem Family
>>   - model_Penryn: Intel Penryn Family
>>   - 

Re: [ovirt-users] hosted-engine deploy error

[dhy336]

thanks, but i do not know why is my hostname invalid? 在2018年04月04日 18:41，Simone 
Tiraboschi 写道： On Wed, Apr 4, 2018 at 12:28 PM,  wrote: Hi,   
I deloy hosted-engine, by this 
blog,https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/
  but I am facing some error.who  may give me  some advise? [root@localhost ~]# 
hosted-engine --deploy ^^^ The error is here: please set a valid hostname for 
your host: the engine VM should be able to reach it. If you add the host as 
localhost the engine VM will reach itself and it's not what we want. If you 
don'y have a working DNS system, hosted-engine-setup will ask about injecting 
an entry for you under /etc/hosts on the engine VM but you still need a valid 
hostname.                     --== STORAGE CONFIGURATION ==--                   
  Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs3, 
nfs4)[nfs3]:            Please specify the full shared storage connection path 
to use (example: host:/path): 192.168.122.134:/home/exports/hosted-engine       
              --== HOST NETWORK CONFIGURATION ==--                     iptables 
was detected on your computer, do you wish setup to configure it? (Yes, 
No)[Yes]:            Please indicate a pingable gateway IP address 
[192.168.122.1]:            Please indicate a nic to set ovirtmgmt bridge on: 
(eth0) [eth0]:                      --== VM CONFIGURATION ==--                  
   The following appliance have been found on your system:           [1] - The 
oVirt Engine Appliance image (OVA) - 4.1-20180124.1.el7.centos           [2] - 
Directly select an OVA file           Please select an appliance (1, 2) [1]:  [ 
INFO  ] Verifying its sha1sum [ INFO  ] Checking OVF archive content (could 
take a few minutes depending on archive size) [ INFO  ] Checking OVF XML 
content (could take a few minutes depending on archive size)           Please 
specify the console type you would like to use to connect to the VM (vnc, 
spice) [vnc]:  [ INFO  ] Detecting host timezone.           Would you like to 
use cloud-init to customize the appliance on the first boot (Yes, No)[Yes]?     
       Would you like to generate on-fly a cloud-init ISO image (of no-cloud 
type)           or do you have an existing one (Generate, Existing)[Generate]?  
          Please provide the FQDN you would like to use for the engine 
appliance.           Note: This will be the FQDN of the engine VM you are now 
going to launch,           it should not point to the base host or to any other 
existing machine.           Engine VM FQDN: (leave it empty to skip):  []: 
engine.tchyp.com           Please provide the domain name you would like to use 
for the engine appliance.           Engine VM domain: [tchyp.com]           
Automatically execute engine-setup on the engine appliance on first boot (Yes, 
No)[Yes]?            Automatically restart the engine VM as a monitored service 
after engine-setup (Yes, No)[Yes]?            Enter root password that will be 
used for the engine appliance (leave it empty to skip):  [WARNING] Skipping 
appliance root password           Enter ssh public key for the root user that 
will be used for the engine appliance (leave it empty to skip):  [WARNING] 
Skipping appliance root ssh public key           Do you want to enable ssh 
access for the root user (yes, no, without-password) [yes]:  [WARNING] The 
oVirt engine appliance is not configured with a default password, please 
consider configuring it via cloud-init           Please specify the size of the 
VM disk in GB: [58]:  [WARNING] Minimum requirements not met by available 
memory: Required: 4096 MB. Available: 3064 MB           Please specify the 
memory size of the VM in MB (Defaults to maximum available): [3064]:  [WARNING] 
Minimum requirements for memory size not met           Continue with specified 
memory size? (Yes, No) [No]: yes           The following CPU types are 
supported by this host:           - model_Haswell-noTSX: Intel Haswell-noTSX 
Family           - model_SandyBridge: Intel SandyBridge Family           - 
model_Westmere: Intel Westmere Family           - model_Nehalem: Intel Nehalem 
Family           - model_Penryn: Intel Penryn Family           - model_Conroe: 
Intel Conroe Family           Please specify the CPU type to be used by the VM 
[model_Haswell-noTSX]:            Please specify the number of virtual CPUs for 
the VM (Defaults to appliance OVF value): [4]:            You may specify a 
unicast MAC address for the VM or accept a randomly generated default 
[00:16:3e:5d:72:8a]:            How should the engine VM network be configured 
(DHCP, Static)[DHCP]? Static           Please enter the IP address to be used 
for the engine VM [192.168.122.2]: 192.168.122.211 [ INFO  ] The engine VM will 
be configured to use 192.168.122.211/24           Please provide a 
comma-separated list (max 3) of IP addresses of domain name servers for the 
engine VM           Engine VM DNS (leave 

Re: [ovirt-users] hosted-engine deploy error

[Simone Tiraboschi]

On Wed, Apr 4, 2018 at 12:28 PM,  wrote:

> Hi,
>
> I deloy hosted-engine, by this blog,https://ovirt.org/
> documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/
>  but I am facing some error.who  may give me  some advise?
>
> [root@localhost ~]# hosted-engine --deploy
>

^^^

The error is here: please set a valid hostname for your host: the engine VM
should be able to reach it.
If you add the host as localhost the engine VM will reach itself and it's
not what we want.

If you don'y have a working DNS system, hosted-engine-setup will ask about
injecting an entry for you under /etc/hosts on the engine VM but you still
need a valid hostname.



>
>
>
>   --== STORAGE CONFIGURATION ==--
>
>   Please specify the storage you would like to use (glusterfs,
> iscsi, fc, nfs3, nfs4)[nfs3]:
>   Please specify the full shared storage connection path to use
> (example: host:/path): 192.168.122.134:/home/exports/hosted-engine
>
>   --== HOST NETWORK CONFIGURATION ==--
>
>   iptables was detected on your computer, do you wish setup to
> configure it? (Yes, No)[Yes]:
>   Please indicate a pingable gateway IP address [192.168.122.1]:
>   Please indicate a nic to set ovirtmgmt bridge on: (eth0) [eth0]:
>
>   --== VM CONFIGURATION ==--
>
>   The following appliance have been found on your system:
>   [1] - The oVirt Engine Appliance image (OVA) -
> 4.1-20180124.1.el7.centos
>   [2] - Directly select an OVA file
>   Please select an appliance (1, 2) [1]:
> [ INFO  ] Verifying its sha1sum
> [ INFO  ] Checking OVF archive content (could take a few minutes depending
> on archive size)
> [ INFO  ] Checking OVF XML content (could take a few minutes depending on
> archive size)
>   Please specify the console type you would like to use to connect
> to the VM (vnc, spice) [vnc]:
> [ INFO  ] Detecting host timezone.
>   Would you like to use cloud-init to customize the appliance on
> the first boot (Yes, No)[Yes]?
>   Would you like to generate on-fly a cloud-init ISO image (of
> no-cloud type)
>   or do you have an existing one (Generate, Existing)[Generate]?
>   Please provide the FQDN you would like to use for the engine
> appliance.
>   Note: This will be the FQDN of the engine VM you are now going
> to launch,
>   it should not point to the base host or to any other existing
> machine.
>   Engine VM FQDN: (leave it empty to skip):  []: engine.tchyp.com
>   Please provide the domain name you would like to use for the
> engine appliance.
>   Engine VM domain: [tchyp.com]
>   Automatically execute engine-setup on the engine appliance on
> first boot (Yes, No)[Yes]?
>   Automatically restart the engine VM as a monitored service after
> engine-setup (Yes, No)[Yes]?
>   Enter root password that will be used for the engine appliance
> (leave it empty to skip):
> [WARNING] Skipping appliance root password
>   Enter ssh public key for the root user that will be used for the
> engine appliance (leave it empty to skip):
> [WARNING] Skipping appliance root ssh public key
>   Do you want to enable ssh access for the root user (yes, no,
> without-password) [yes]:
> [WARNING] The oVirt engine appliance is not configured with a default
> password, please consider configuring it via cloud-init
>   Please specify the size of the VM disk in GB: [58]:
> [WARNING] Minimum requirements not met by available memory: Required: 4096
> MB. Available: 3064 MB
>   Please specify the memory size of the VM in MB (Defaults to
> maximum available): [3064]:
> [WARNING] Minimum requirements for memory size not met
>   Continue with specified memory size? (Yes, No) [No]: yes
>   The following CPU types are supported by this host:
>   - model_Haswell-noTSX: Intel Haswell-noTSX Family
>   - model_SandyBridge: Intel SandyBridge Family
>   - model_Westmere: Intel Westmere Family
>   - model_Nehalem: Intel Nehalem Family
>   - model_Penryn: Intel Penryn Family
>   - model_Conroe: Intel Conroe Family
>   Please specify the CPU type to be used by the VM
> [model_Haswell-noTSX]:
>   Please specify the number of virtual CPUs for the VM (Defaults
> to appliance OVF value): [4]:
>   You may specify a unicast MAC address for the VM or accept a
> randomly generated default [00:16:3e:5d:72:8a]:
>   How should the engine VM network be configured (DHCP,
> Static)[DHCP]? Static
>   Please enter the IP address to be used for the engine VM
> [192.168.122.2]: 192.168.122.211
> [ INFO  ] The engine VM will be configured to use 192.168.122.211/24
>   Please provide a comma-separated list (max 3) of IP addresses of
> domain name servers for the engine VM
>   Engine VM DNS (leave it empty to skip) [192.168.122.1]:
>  

[ovirt-users] Now way to install on EFI and ISCSI

[Ralf Schenk]

Hello,

I've a Epyc-based Supermicro Server that should act as ovirt host by
using ovirt-node-next installed on ISCSI Boot Target. I already
installed an EFI bootable OS (Ubuntu 16.04) on the Hardware using ISCSI
Target as Boot-Disk. So far that works.

If I try to install ovirt-node-next (tried
ovirt-node-ng-installer-ovirt-4.2-2018032906.iso,
ovirt-node-ng-installer-ovirt-4.2-2018040306.iso mounted via KVM as CD)
I'm not able to use auto-partitioning nor manual partitioning to set the
system up. Accessing the ISCSI Target (50GB) works. I created all the
mount-points, including /boot and EFI System Partition /boot/efi. The
installer automatically proposes /, /var /home and swap on thinpool LVMs
which is ok.

After having it ready the installer either doesn't accept "Done" as if
no EFI Partition was prepared. If I highlight the EFI Partition and
click Done it works but the Installer overview doesn't allow to start
installation and storage configuration ist marked with a warning sign.

The system is booted definitely via EFI from th installer CD.

Bye
-- 


*Ralf Schenk*
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail *r...@databay.de* 
    
*Databay AG*
Jens-Otto-Krag-Straße 11
D-52146 Würselen
*www.databay.de* 

Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm.
Philipp Hermanns
Aufsichtsratsvorsitzender: Wilhelm Dohmen


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] hosted-engine deploy error

[dhy336]

Hi, I deloy hosted-engine, by this 
blog,https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/
 but I am facing some error.who  may give me  some advise?
[root@localhost ~]# hosted-engine --deploy   

  --== STORAGE CONFIGURATION ==--   Please specify the 
storage you would like to use (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]: 
  Please specify the full shared storage connection path to use (example: 
host:/path): 192.168.122.134:/home/exports/hosted-engine   --== 
HOST NETWORK CONFIGURATION ==--   iptables was detected on your 
computer, do you wish setup to configure it? (Yes, No)[Yes]:   Please 
indicate a pingable gateway IP address [192.168.122.1]:   Please 
indicate a nic to set ovirtmgmt bridge on: (eth0) [eth0]:
--== VM CONFIGURATION ==--   The following appliance have been 
found on your system:   [1] - The oVirt Engine Appliance image 
(OVA) - 4.1-20180124.1.el7.centos[2] - Directly select an OVA 
file  Please select an appliance (1, 2) [1]: [ INFO  ] Verifying its 
sha1sum[ INFO  ] Checking OVF archive content (could take a few minutes 
depending on archive size)[ INFO  ] Checking OVF XML content (could take a few 
minutes depending on archive size)  Please specify the console type you 
would like to use to connect to the VM (vnc, spice) [vnc]: [ INFO  ] Detecting 
host timezone.  Would you like to use cloud-init to customize the 
appliance on the first boot (Yes, No)[Yes]?   Would you like to 
generate on-fly a cloud-init ISO image (of no-cloud type)  or do you 
have an existing one (Generate, Existing)[Generate]?   Please provide 
the FQDN you would like to use for the engine appliance.  Note: This 
will be the FQDN of the engine VM you are now going to launch,  it 
should not point to the base host or to any other existing machine.  
Engine VM FQDN: (leave it empty to skip):  []: engine.tchyp.com  Please 
provide the domain name you would like to use for the engine appliance. 
 Engine VM domain: [tchyp.com]  Automatically execute engine-setup on 
the engine appliance on first boot (Yes, No)[Yes]?   Automatically 
restart the engine VM as a monitored service after engine-setup (Yes, No)[Yes]? 
  Enter root password that will be used for the engine appliance (leave 
it empty to skip): [WARNING] Skipping appliance root password  Enter 
ssh public key for the root user that will be used for the engine appliance 
(leave it empty to skip): [WARNING] Skipping appliance root ssh public key  
Do you want to enable ssh access for the root user (yes, no, 
without-password) [yes]: [WARNING] The oVirt engine appliance is not configured 
with a default password, please consider configuring it via cloud-init  
Please specify the size of the VM disk in GB: [58]: [WARNING] Minimum 
requirements not met by available memory: Required: 4096 MB. Available: 3064 MB 
 Please specify the memory size of the VM in MB (Defaults to maximum 
available): [3064]: [WARNING] Minimum requirements for memory size not met  
Continue with specified memory size? (Yes, No) [No]: yes  The 
following CPU types are supported by this host:- 
model_Haswell-noTSX: Intel Haswell-noTSX Family   - 
model_SandyBridge: Intel SandyBridge Family   - model_Westmere: 
Intel Westmere Family - model_Nehalem: Intel Nehalem Family 
  - model_Penryn: Intel Penryn Family - model_Conroe: 
Intel Conroe Family  Please specify the CPU type to be used by the VM 
[model_Haswell-noTSX]:   Please specify the number of virtual CPUs for 
the VM (Defaults to appliance OVF value): [4]:   You may specify a 
unicast MAC address for the VM or accept a randomly generated default 
[00:16:3e:5d:72:8a]:   How should the engine VM network be configured 
(DHCP, Static)[DHCP]? Static  Please enter the IP address to be used 
for the engine VM [192.168.122.2]: 192.168.122.211[ INFO  ] The engine VM will 
be configured to use 192.168.122.211/24  Please provide a 
comma-separated list (max 3) of IP addresses of domain name servers for the 
engine VM  Engine VM DNS (leave it empty to skip) [192.168.122.1]:  
 Add lines for the appliance itself and for this host to /etc/hosts on the 
engine VM?  Note: ensuring that this host could resolve the engine VM 
hostname is still up to you  (Yes, No)[No]--== 
HOSTED ENGINE CONFIGURATION ==--   Enter engine admin password: 
  Confirm engine admin password:   Please provide the name of 
the SMTP server through which we will send notifications [localhost]:   
Please provide the TCP port 

Re: [ovirt-users] Engine reports

[Fred Rolland]

Shirly, can you take a look?

On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  wrote:

> Tried to install ovirt metrics, but got error
>
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
>
>   1. Hosts:localhost
>  Play: Determine openshift_version to configure on first master
>  Task: For an RPM install, abort when the release requested does
> not match the available version.
>  Message:  You requested openshift_release 3.7, which is not matched by
>the latest OpenShift RPM we detected as origin-3.10.0
>on host localhost.
>We will only install the latest RPMs, so please ensure
> you are getting the release
>you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>available on the host, or run the appropriate OpenShift
> upgrade playbook.
>
> regards
> Peter
>
>
> On 04/04/2018 09:13, Fred Rolland wrote:
> > Hi,
> >
> > Check these links:
> >
> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> > https://ovirt.org/develop/release-management/features/
> metrics/metrics-store/
> >
> > Regards,
> > Fred
> >
> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> > >
> > wrote:
> >
> > Hi,
> >
> > I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> > take the reports? I version 3.5, we had Jasper reports module using
> > which we could take utilization reports. Can we do something similar
> > here?
> >
> > --
> >
> > Thanks & Regards,
> >
> >
> > Anantha Raghava
> >
> >
> > Do not print this e-mail unless required. Save Paper & trees.
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org 
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
> --
> *Peter Hudec*
> Infraštruktúrny architekt
> phu...@cnc.sk 
>
> *CNC, a.s.*
> Borská 6, 841 04 Bratislava
> Recepcia: +421 2  35 000 100
>
> Mobil:+421 905 997 203
> *www.cnc.sk* 
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Snapshot tree

[Yedidyah Bar David]

On Wed, Apr 4, 2018 at 12:21 PM,   wrote:
> Hi,
> Can you confirm that there is no way to have a snapshot tree, like in
> VirtualBox, where one can revert to say "snapshot1" and then branch new
> children snapshot but without loosing any snapshots made after "snapshot1",
> which could have their own children ?

Indeed, oVirt does not have "snapshot trees".

> According to the documentation, it is impoissible, but is there a workaround
> ?

Best workaround I came up with is Right-click a snapshot and choose 'Clone'.
This will create a new VM from (a COW copy of) this snapshot.

Best regards,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Snapshot tree

[spfma . tech]

Hi,
 Can you confirm that there is no way to have a snapshot tree, like in 
VirtualBox, where one can revert to say "snapshot1" and then branch new 
children snapshot but without loosing any snapshots made after "snapshot1", 
which could have their own children ? According to the documentation, it is 
impoissible, but is there a workaround ? Regards 

-
FreeMail powered by mail.fr
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

[Peter Hudec]

Tried to install ovirt metrics, but got error

ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
@/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
playbooks/byo/config.yml

  1. Hosts:localhost
 Play: Determine openshift_version to configure on first master
 Task: For an RPM install, abort when the release requested does
not match the available version.
 Message:  You requested openshift_release 3.7, which is not matched by
   the latest OpenShift RPM we detected as origin-3.10.0
   on host localhost.
   We will only install the latest RPMs, so please ensure
you are getting the release
   you expect. You may need to adjust your Ansible
inventory, modify the repositories
   available on the host, or run the appropriate OpenShift
upgrade playbook.

regards
Peter


On 04/04/2018 09:13, Fred Rolland wrote:
> Hi,
> 
> Check these links:
> 
> https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> https://ovirt.org/develop/release-management/features/metrics/metrics-store/
> 
> Regards,
> Fred
> 
> On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> >
> wrote:
> 
> Hi,
> 
> I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> take the reports? I version 3.5, we had Jasper reports module using
> which we could take utilization reports. Can we do something similar
> here?
> 
> -- 
> 
> Thanks & Regards,
> 
> 
> Anantha Raghava
> 
> 
> Do not print this e-mail unless required. Save Paper & trees.
> 
> 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


-- 
*Peter Hudec*
Infraštruktúrny architekt
phu...@cnc.sk 

*CNC, a.s.*
Borská 6, 841 04 Bratislava
Recepcia: +421 2  35 000 100

Mobil:+421 905 997 203
*www.cnc.sk* 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Q: Change MAC address of an existing VM

[Michael Burman]

Hi,

This will change only the MAC address of that specific vNIC that you are
editing, for this specific VM.

Cheers)

On Wed, Apr 4, 2018 at 10:32 AM, Andrei Verovski 
wrote:

> Hi,
>
> Change MAC address  of an existing VM:
> Compute -> Virtual machines -> Edit network -> Custom Mac Address
>
> This will change MAC address of only ONE VM, right ?
> Not for all VMs connected to the same ovirt-mgmt interface.
>
>
> Thanks
> Andrei
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 

Michael Burman

Senior Quality engineer - rhv network - redhat israel

Red Hat



mbur...@redhat.comM: 0545355725 IM: mburman

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Q: Change MAC address of an existing VM

[Andrei Verovski]

Hi,

Change MAC address  of an existing VM:
Compute -> Virtual machines -> Edit network -> Custom Mac Address

This will change MAC address of only ONE VM, right ?
Not for all VMs connected to the same ovirt-mgmt interface.


Thanks
Andrei

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

[Fred Rolland]

Hi,

Check these links:

https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
https://ovirt.org/develop/release-management/features/metrics/metrics-store/

Regards,
Fred

On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava <
rag...@exzatechconsulting.com> wrote:

> Hi,
>
> I see that oVirt DWH is installed with Version 4.2.x. Now, how do I take
> the reports? I version 3.5, we had Jasper reports module using which we
> could take utilization reports. Can we do something similar here?
> --
>
> Thanks & Regards,
>
>
> Anantha Raghava
>
> Do not print this e-mail unless required. Save Paper & trees.
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] STP and /var/lib/vdsm/persistence files

[spfma . tech]

Hi,
 As these files are generated by oVirt when a modification occurs, how to 
enable STP on bridges by configuration ?
 I haven't been able to find this option in GUI. Editing ifconfig and 
persistence files is OK, but maybe I can modify something that would erase this 
handmade modification and it will be lost. I have only seen unanswered posts 
about this topic. Regards 

-
FreeMail powered by mail.fr
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt non-self-hosted HA

[Yaniv Kaul]

On Wed, Apr 4, 2018 at 12:39 AM, Tom  wrote:

>
>
> Sent from my iPhone
>
> On Apr 3, 2018, at 9:32 AM, Yaniv Kaul  wrote:
>
>
>
> On Tue, Apr 3, 2018 at 3:12 PM, TomK  wrote:
>
>> Hey Guy's,
>>
>> If I'm looking to setup the oVirt engine in an HA configuration off the
>> physical servers hosting my VM's (non self hosted), what are my options
>> here?
>>
>> I want to setup two to four active oVirt engine instances elsewhere and
>> handle the HA via something like haproxy / keepalived to keep the entire
>> experience seamless to the user.
>>
>
> You will need to set up the oVirt engine service as well as the PG
> database (and ovirt-engine-dwhd service and any other service we run next
> to the engine) as highly available module.
> In pacemaker[1], for example.
> You'll need to ensure configuration is also sync'ed between nodes, etc.
> Y.
>
>
> So already have one ovirt engine setup separately on a vm that manages two
> remote physical hosts.  So familiar with the single host approach which I
> would simply replicate.  At least that’s the idea anyway.  Could you please
> expand a bit on the highly available module and  syncing the config between
> hosts?
>

That's a different strategy, which is also legit - you treat this VM as a
highly available resource. Now you do not need to sync the config - just
the VM disk and config.
Perhaps something like
https://www.unixarena.com/2015/12/rhel-7-pacemaker-configuring-ha-kvm-guest.html
.

But if you are already doing that, I'm not sure why you'd prefer this over
hosted-engine setup.
Y.

>
> Cheers,
> Tom
>
>
> [1] https://clusterlabs.org/quickstart-redhat.html
>
>>
>> From what I've seen in oVirt, that seems to be possible without the two
>> oVirt engines even knowing each other's existence but is it something
>> anyone has ever done?  Any recommendations in this case?
>>
>> Having settings replicated would be a bonus but I would be comfortable if
>> they weren't and I handle that myself.
>>
>> --
>> Cheers,
>> Tom K.
>> 
>> -
>>
>> Living on earth is expensive, but it includes a free trip around the sun.
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Persistent dummy interface

[spfma . tech]

Hi,
 Thanks for your reply, that was the idea I had but in a less clean way :-) So 
it is at os level, nothing special in oVirt. I have found the thing fully 
explained here, for reference : 
https://www.centos.org/forums/viewtopic.php?t=53233 Regards 

 Le 03-Apr-2018 13:32:06 +0200, rabidcic...@gmail.com a crit:   
 Sorry was on my phone. Modules-load.d 
  On Tue, Apr 3, 2018, 7:29 AM RabidCicada  wrote: 
 I do this on CentOS with /etc/modules-lomodules-loadad.d. You can stick a file 
in there that is basically just a bash script that loads your driver and then 
does the ip link command all the same time.  
  On Tue, Apr 3, 2018, 4:20 AM  wrote: 
 Hi,
 What is the right way to get a persistent dummy interface ? I need an internal 
network for lab purpoposes, so I created a dummy link "ip link add dummy_1 type 
dummy" and I was able to assign my logical network to it. But how to make it 
persistent ? Of course, after a reboot, the dummy device has gone and the 
server becomes non operational because of this non-compliant network. I have to 
recereate it by hand in order to get things work. Regards  

-
FreeMail powered by mail.fr ___
 Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users 

-
FreeMail powered by mail.fr
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users