All: Earlier this morning, I was pulling in the stats from Bitergia, and got this message: Gear 847edb45aea84198838f915be6faa066 is using 91.2% of disk quota I know updating the size of the gear was something on the list of things to do, but I was under the impression we'd updated the size of the gear. On investigation, Michael Scherer discovered that the mysql database is taking up 5.9 GB, and the logs 2 GB. Is there anything we can do to mitigate the size of these instances? Also, you have probably heard about the HeartBleed OpenSSL vulnerability [1], but just in case, we need to make sure this has been addressed. OpenShift should be fine, but any service using TLS needs to be updated ASAP. Michael has already checked, and puppetmaster and lists.ovirt.org appear to be okay. Thanks, Brian -- Brian Proffitt - oVirt Community Manager Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC
--=-sZi3T9jwaHmx8dgnAF7A Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le mardi 08 avril 2014 =C3=A0 08:24 -0400, Brian Proffitt a =C3=A9crit :
All: =20 Earlier this morning, I was pulling in the stats from Bitergia, and got t= his message: =20 Gear 847edb45aea84198838f915be6faa066 is using 91.2% of disk quota =20 I know updating the size of the gear was something on the list of things= =20 to do, but I was under the impression we'd updated the size of the gear. =20 On investigation, Michael Scherer discovered that the mysql database is= =20 taking up 5.9 GB, and the logs 2 GB. Is there anything we can do to mitig= ate the size of these instances?=20
Also, you have probably heard about the HeartBleed OpenSSL vulnerability = [1], but=20 just in case, we need to make sure this has been addressed. OpenShift sho=
We can erase the logs.=20 We can also try to see if the db can be shrinked, but I am not sure it can be done. uld be fine,=20
but any service using TLS needs to be updated ASAP. Michael has already c= hecked, and=20 puppetmaster and lists.ovirt.org appear to be okay.
That's ok on lists because there is no tls at all. And I just checked the foreman https with a small reproducer, better update anyway. --=20 Michael Scherer Open Source and Standards, Sysadmin --=-sZi3T9jwaHmx8dgnAF7A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAABAgAGBQJTQ/MhAAoJEE89Wa+PrSK9j6wQAIU+vEhOwSv5SEVRIpJH0iJD U1sbLL1j+YRC6T00yhnP+E5e0Q95wPAaT1lPryz4sbHvFs9EAMLNzHDymPZ1zCl8 YNdEQRROK96yIE6aolsskZuBQ6gYF8IevqFhbkHvYwf4gC01N1CgqOWHiqGVQm4z ysKzuwLQFysMo1dfK/zGyo8M5isvuQymNgz9v9uXgxsgxXc+DBq03FXg3ua0pqQu HlkY73P8WsQdBdeLS+f7VWxPr0X4sgzhrEbRbUFNPGnHiVcY1Ahpvu1Aujfxueeo Uxe3H0oCsTQPgtm5sWIpphIt/OsCgYle4d7jLYUWexzVSxhQxf2GEL3B8GD/YK7V mb6zm62SIcRGeVCsRB1rPOPRbg3P47EpQnGp8XN+sk0eWs9+vVl32S/VKyq+bvdi YN1OIucpKuzw4HHr/3PznR/JmLIsqPVE7Q8IDHi8cn2FknYFElxY+d8KPMW7HDnc 8CmRpHq0rd7CXo0W+OjhgX7msYaQqPHElOarrh6l7uc5IwtIepXPqRsu/EZHm8nn Kvl/f17MGXVEX5KI7SfeEYIifqjjUQLkBJAcQLswmEZG80RJl5/c8oA1Uh2v93+Q 9onCo3We62OSet/xCs/X3toHb1M8G8fXB544TwSHRmEV8our5gP+jELv17pglDzF N+P0OjK+MmS4IO1ymE9y =+3u0 -----END PGP SIGNATURE----- --=-sZi3T9jwaHmx8dgnAF7A--
Hi Brian, This is a long-standing issue, and I'd like to see it addressed long-term. The main issue is this one: https://www.openshift.com/forums/openshift/ibdata1-file-eating-my-quota The solution is to move to a scalable OpenShift application (which solves the ibdata issue), use the external database in the MediaWiki gear, and dump & load the database from the old database to the new one. We could take advantage of the opportunity to handle log files better, and add website analytics to the website with Piwik. To that end, we recently (~6 weeks ago) sorted out the long-standing issue of adding new admins to oVirt, and had more gears added to the project. So it should be straightforward to take care of this now. Cheers, Dave. On 04/08/2014 02:24 PM, Brian Proffitt wrote:
All:
Earlier this morning, I was pulling in the stats from Bitergia, and got this message:
Gear 847edb45aea84198838f915be6faa066 is using 91.2% of disk quota
I know updating the size of the gear was something on the list of things to do, but I was under the impression we'd updated the size of the gear.
On investigation, Michael Scherer discovered that the mysql database is taking up 5.9 GB, and the logs 2 GB. Is there anything we can do to mitigate the size of these instances?
Also, you have probably heard about the HeartBleed OpenSSL vulnerability [1], but just in case, we need to make sure this has been addressed. OpenShift should be fine, but any service using TLS needs to be updated ASAP. Michael has already checked, and puppetmaster and lists.ovirt.org appear to be okay.
Thanks, Brian
-- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
participants (3)
-
Brian Proffitt -
Dave Neary -
Michael Scherer