[ovirt-users] Info on testing ovirt 4.0.5 and gluster

[knarra]

On 11/16/2016 03:51 PM, Gianluca Cecchi wrote:
> On Wed, Nov 16, 2016 at 9:55 AM, knarra <knarra at redhat.com 
> <mailto:knarra at redhat.com>> wrote:
>
>     On 11/16/2016 01:28 PM, Gianluca Cecchi wrote:
>>     On Wed, Nov 16, 2016 at 7:59 AM, knarra <knarra at redhat.com
>>     <mailto:knarra at redhat.com>> wrote:
>>
>>         Hi Gianluca,
>>
>>             yes, you are right. Now second and third host can be
>>         directly added from UI. Before adding the second and third
>>         host please make sure that the following steps are done for
>>         hyperconverged setup.
>>
>>         1) On Hosted engine vm run the command 'engine-config -s
>>         AllowClusterWithVirtGlusterEnabled=true'
>>
>>         2) Restart ovirt-engine by running the command 'service
>>         ovirt-engine restart'
>>
>>         3) /Edit Cluster/>/Default/>/Enable the gluster service/.
>>
>>         4) Create separate storage domains for each gluster volume.
>>         You can see that hosted_storage gets imported into the UI
>>         automatically when one storage domain is created in the UI.
>>
>>         5) Add second and third host from UI.
>>
>>         Hope this helps
>>
>>         Thanks
>>         kasturi
>>
>>
>>     Hello,
>>     thanks for your answer.
>>     Basically I'm following Jason guide here for 4.0:
>>     https://www.ovirt.org/blog/2016/08/up-and-running-with-ovirt-4-0-and-gluster-storage/
>>     <https://www.ovirt.org/blog/2016/08/up-and-running-with-ovirt-4-0-and-gluster-storage/>
>>
>>     I arrived just before the second/third host deploy actions.
>>     I verified that
>>
>>     1) actually seems already in place
>>     [root at ovengine ~]# engine-config -g
>>     AllowClusterWithVirtGlusterEnabled
>>     AllowClusterWithVirtGlusterEnabled: true version: general
>>     [root at ovengine ~]#
>>
>>     3) Already done
>>
>>     2) Already done after step 3)
>>
>>
>>     I see that in Jason guide steps 4) and 5) are reversed.
>>     Are they interchangeable or is that using the web admin deploy
>>     method requires that storage domains are already set up before
>>     adding second host?
>     Before adding second host, it requires hosted_storage domain to be
>     imported into the UI. For this to happen we need to atleast add
>     one domain. With out creating a storage domain you can try adding
>     the second host and you will be given a message to add the domain
>     first.
>>
>>     Gianluca
>
>
>
> Thanks for clarifications.
> It worked smoothly; all the three hosts are now up; going to test 
> urther functionalities.
> Fine!
>
> In the host-deploy logs for the 3 hosts I only see for the third host 
> (and for the first file of the two ones generated for first host) 
> these kinds of warning:
>
>
> 2016-11-16 11:09:48 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:863 execute-result: ('/bin/systemctl', 'start', 
> 'tuned.service'), rc=0
> 2016-11-16 11:09:48 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:921 execute-output: ('/bin/systemctl', 'start', 
> 'tuned.service') stdout:
>
>
> 2016-11-16 11:09:48 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:926 execute-output: ('/bin/systemctl', 'start', 
> 'tuned.service') stderr:
>
>
> 2016-11-16 11:09:48 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned 
> plugin.executeRaw:813 execute: ('/sbin/tuned-adm', 'profile', 
> 'rhs-virtualization'), executable='None', cwd='None', env=None
> 2016-11-16 11:09:49 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned 
> plugin.executeRaw:863 execute-result: ('/sbin/tuned-adm', 'profile', 
> 'rhs-virtualization'), rc=1
> 2016-11-16 11:09:49 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned 
> plugin.execute:921 execute-output: ('/sbin/tuned-adm', 'profile', 
> 'rhs-virtualization') stdout:
>
>
> 2016-11-16 11:09:49 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned 
> plugin.execute:926 execute-output: ('/sbin/tuned-adm', 'profile', 
> 'rhs-virtualization') stderr:
> Requested profile 'rhs-virtualization' doesn't exist.
>
> 2016-11-16 11:09:49 WARNING otopi.plugins.ovirt_host_deploy.tune.tuned 
> tuned._misc:105 Cannot set tuned profile
>
> Do I have to worry about them?
>
> Thanks again
> Gianluca

you could safely ignore these messages. There are some tuned profiles 
which engine tries to set on the node. If those profiles does not exist 
on the node engine throws these kind of messages.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20161116/2f3cde98/attachment-0001.html>