[JIRA] (OVIRT-1763) Increase entropy for hosts

Wednesday, 15 November 2017

This is a multi-part message in MIME format...

------------=_1510756591-26566-475
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

    [
https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jir...
] 

Barak Korren edited comment on OVIRT-1763 at 11/15/17 2:36 PM:
---------------------------------------------------------------

[~ederevea] OST uses a simple check to determine if to run in RAM or not:

{code}
# if above RAM_THRESHOLD KBs are available in /dev/shm, run there
RAM_THRESHOLD=15000000

# ...

get_run_path() {
     local avail_shm
     avail_shm=$(df --output=avail /dev/shm | sed 1d)
     [[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \
         mkdir -p "/dev/shm/ost" && \
         echo "/dev/shm/ost/deployment-$SUITE" || \
         echo "$PWD/deployment-$SUITE"
}
{code}

This seems to be 15G so we need to figure out why wasn't this available when these
lines ran (These lines are amount the very first things that run when an OST suit starts
up, so its unlikely to be cause by anything the suit is doing)

Code quoted above is part of '{{automation/suit.sh}}' in OST:
https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=blob;f=automat...

was (Author: bkorren(a)redhat.com):
[~ederevea] OST uses a simple check to determine if to run in RAM or not:

{code}
# if above RAM_THRESHOLD KBs are available in /dev/shm, run there
RAM_THRESHOLD=15000000

# ...

get_run_path() {
     local avail_shm
     avail_shm=$(df --output=avail /dev/shm | sed 1d)
     [[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \
         mkdir -p "/dev/shm/ost" && \
         echo "/dev/shm/ost/deployment-$SUITE" || \
         echo "$PWD/deployment-$SUITE"
}
{code}

This seems to be 15G so we need to figure out why wasn't this available when these
lines ran (These lines are amount the very first things that run when an OST suit starts
up, so its unlikely to be cause by anything the suit is doing)

...
 Increase entropy for hosts
 --------------------------

                 Key: OVIRT-1763
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763
             Project: oVirt - virtualization made easy
          Issue Type: Bug
            Reporter: Dafna Ron
            Assignee: infra

 we had a failure in ost that was really hard to debug:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/
 There are no failures in the logs and the test itself was terminated by a timeout.
 It took the vms a long time to download packages and install and didi seems to think that
this is due to limited entropy on the physical host. 
 we need to review this issue and increase the entropy on the hosts.  

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100071)

------------=_1510756591-26566-475
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jir...
]</pre>
<h3>Barak Korren edited comment on OVIRT-1763 at 11/15/17 2:36 PM:</h3>
<p>[~ederevea] OST uses a simple check to determine if to run in RAM or
not:</p>
<p>{code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there
RAM_THRESHOLD=15000000</p>
<p># &hellip;</p>
<p>get_run_path() {</p>
<pre>local avail_shm
avail_shm=$(df --output=avail /dev/shm | sed 1d)
[[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] &amp;&amp; \
    mkdir -p "/dev/shm/ost" &amp;&amp; \
    echo "/dev/shm/ost/deployment-$SUITE" || \
    echo "$PWD/deployment-$SUITE"</pre>
<p>} {code}</p>
<p>This seems to be 15G so we need to figure out why wasn't this available when
these lines ran (These lines are amount the very first things that run when an OST suit
starts up, so its unlikely to be cause by anything the suit is doing)</p>
<p>Code quoted above is part of &lsquo;{{automation/suit.sh}}&rsquo; in OST:
<a
href="https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=blo...
<p>was (Author: bkorren(a)redhat.com): [~ederevea] OST uses a simple check to
determine if to run in RAM or not:</p>
<p>{code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there
RAM_THRESHOLD=15000000</p>
<p># &hellip;</p>
<p>get_run_path() {</p>
<pre>local avail_shm
avail_shm=$(df --output=avail /dev/shm | sed 1d)
[[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] &amp;&amp; \
    mkdir -p "/dev/shm/ost" &amp;&amp; \
    echo "/dev/shm/ost/deployment-$SUITE" || \
    echo "$PWD/deployment-$SUITE"</pre>
<p>} {code}</p>
<p>This seems to be 15G so we need to figure out why wasn't this available when
these lines ran (These lines are amount the very first things that run when an OST suit
starts up, so its unlikely to be cause by anything the suit is doing)</p>
<blockquote><h3>Increase entropy for hosts</h3>
<pre>     Key: OVIRT-1763
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763
 Project: oVirt - virtualization made easy
         Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra</pre>
<p>we had a failure in ost that was really hard to debug: <a
href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/...
There are no failures in the logs and the test itself was terminated by a timeout. It took
the vms a long time to download packages and install and didi seems to think that this is
due to limited entropy on the physical host. we need to review this issue and increase the
entropy on the hosts.</p></blockquote>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100071)</p>

------------=_1510756591-26566-475--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011