This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9XklncOThLTUfwFAQNGbNX4f828I5OGGz Content-Type: multipart/mixed; boundary="CSTP5JhEfsPNyK0PlfM9nQuRWFwftX3vt"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users <users@ovirt.org> Message-ID: <3f809af7-4e88-68ed-bb65-99a7584ae8a3@gmail.com> Subject: Remote DB: How do you set server_version? --CSTP5JhEfsPNyK0PlfM9nQuRWFwftX3vt Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Greetings, Exploring hosting my engine and ovirt_engine_history db's on my dedicated PostgreSQL server. This is a 9.5 install on a beefy box from the postgresql.org yum repos that I'm using for other SQL needs too. 9.5.12 to be exact. I set up the database just as the documentation says and I'm doing a fresh install of my engine-setup. During the install, right after I give it the details for the remote I get this error: [ ERROR ] Please set: server_version =3D 9.5.9 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* . Huh? Um. OK. $ grep ^server_version postgresql.conf server_version =3D 9.5.9 $ systemctl restart postgresql-9.5.service LOG: syntax error in file "/var/lib/pgsql/9.5/data/postgresql.conf" line 33, n...n ".9" FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors Well that didn't work. Let's try something else. $ grep ^server_version postgresql.conf server_version =3D 9.5.9 $ systemctl restart postgresql-9.5.service LOG: parameter "server_version" cannot be changed FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors Whelp. That didn't work either. I can't seem to find anything in the oVirt docs on setting this. How am I supposed to do this? Thanks! ~Stack~ --CSTP5JhEfsPNyK0PlfM9nQuRWFwftX3vt-- --9XklncOThLTUfwFAQNGbNX4f828I5OGGz Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa6hZqAAoJELkej+ysXJPmSb4QAJ9EhSKTwOeaDF4dgob1Yko2 Z154R/VLPP9nHtAFb/tHZd9zr1zqa9Jr7aU7SmU09epkra4TY/WkdYE7MKpJJdCU hebzncp7Fqr5cooEyQvb4aGEakCVh5yvADcZzVgLO+E72n6DW0ZUNE7HiPqXbKj8 dY8kPM7u4afT4Uga7n7BeQgu2L3M0bgJKR5VOFbwidBfrTqdP3ZXscvqwY12+5Iz arPfDkoab0MBiJIYPNAFXYKa5CRJyr5U+NALwIdXl2FywKgClBLCP+6fCH/UyhMq AzJJZwG/zlCmLOGUJAXG4hh5k8BY+N+zvx3vN7AaU187Rslm5v+q36Ost8N2ugh9 t0JVWDNS8OaZdxu9oKvaKYfDwni9baNNX9mA3Rf90v1TSQEZNPXjIA15Iw84ngPV X833iw9MmmVpfQsrLyjRbDdvBq1+vNhmxCxwloF/ZBoqlid48wHTFB5t5IIZxdUg U8x26/Cz0GTviAr2v98qxIVUh1fKhAF/WFbEK16FwGEmMcOjta/lR63/21d8A2wk 7aOom4ftJfL9jges9LweVN3U/hS66GHMgAxYqmsj/k/OdGBzDiIUqmXfGAhQbT1T ZbhiSMv9/Zj88oBxdE4+zXSuM0C12OPSyrLKac2AGxYRBydv8cxAFIzTuDVxVnNc NFEUgBoZ515dZ6sUaN2V =kS+W -----END PGP SIGNATURE----- --9XklncOThLTUfwFAQNGbNX4f828I5OGGz--
I've been down this road. Postgres won't lie about its version for you. If you want to do this, you have to patch the Ovirt installer[1]. I stopped trying to use my PG cluster at some point - the relationship between the installer and the product combined with the overly restrictive requirements baked into the installer[2]) makes doing so an ongoing hassle. So I treat Ovirt's PG as an black box; disappointing, considering that we are a very heavy PG shop with a lot of expertise and automation I can't use with Ovirt. If nothing has changed (my notes are from a few versions ago), everything you need to correct is in /usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/constants.py Aside from the version, you'll also have to make the knobs for vacuuming match those of your current installation, and I think there was another configurable for something else I'm not remembering right now. Be aware that doing so is accepting an ongoing commitment to monkeying with the installer a lot. At one time I thought doing so was the right tradeoff, but it turns out I was wrong. -j [1] Or you could rebuild PG with a fake version. That option was unavailable here. [2] Not criticizing, just stating a technical fact. How folks apportion their QA resources is their business.
On May 2, 2018, at 12:49 PM, ~Stack~ <i.am.stack@gmail.com> wrote:
Greetings,
Exploring hosting my engine and ovirt_engine_history db's on my dedicated PostgreSQL server.
This is a 9.5 install on a beefy box from the postgresql.org yum repos that I'm using for other SQL needs too. 9.5.12 to be exact. I set up the database just as the documentation says and I'm doing a fresh install of my engine-setup.
During the install, right after I give it the details for the remote I get this error: [ ERROR ] Please set: server_version = 9.5.9 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .
Huh?
Um. OK. $ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service
LOG: syntax error in file "/var/lib/pgsql/9.5/data/postgresql.conf" line 33, n...n ".9" FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Well that didn't work. Let's try something else.
$ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service LOG: parameter "server_version" cannot be changed FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Whelp. That didn't work either. I can't seem to find anything in the oVirt docs on setting this.
How am I supposed to do this?
Thanks! ~Stack~
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, 2 May 2018 at 23:27 Jamie Lawrence <jlawrence@squaretrade.com> wrote:
I've been down this road. Postgres won't lie about its version for you. If you want to do this, you have to patch the Ovirt installer[1]. I stopped trying to use my PG cluster at some point - the relationship between the installer and the product combined with the overly restrictive requirements baked into the installer[2]) makes doing so an ongoing hassle. So I treat Ovirt's PG as an black box; disappointing, considering that we are a very heavy PG shop with a lot of expertise and automation I can't use with Ovirt.
If nothing has changed (my notes are from a few versions ago), everything you need to correct is in
/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/constants.py
Aside from the version, you'll also have to make the knobs for vacuuming match those of your current installation, and I think there was another configurable for something else I'm not remembering right now.
Be aware that doing so is accepting an ongoing commitment to monkeying with the installer a lot. At one time I thought doing so was the right tradeoff, but it turns out I was wrong.
-j
[1] Or you could rebuild PG with a fake version. That option was unavailable here. [2] Not criticizing, just stating a technical fact. How folks apportion their QA resources is their business.
On May 2, 2018, at 12:49 PM, ~Stack~ <i.am.stack@gmail.com> wrote:
Greetings,
Exploring hosting my engine and ovirt_engine_history db's on my dedicated PostgreSQL server.
This is a 9.5 install on a beefy box from the postgresql.org yum repos that I'm using for other SQL needs too. 9.5.12 to be exact. I set up the database just as the documentation says and I'm doing a fresh install of my engine-setup.
During the install, right after I give it the details for the remote I get this error: [ ERROR ] Please set: server_version = 9.5.9 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .
Huh?
Yes it's annoying and I think +Yaniv Dary <ylavi@redhat.com> opened a bug for it after both of got mad at it. Yaniv? Meanwhile let us know if you were able to patch constants.py as suggested.
Um. OK.
$ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service
LOG: syntax error in file "/var/lib/pgsql/9.5/data/postgresql.conf" line 33, n...n ".9" FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Well that didn't work. Let's try something else.
$ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service LOG: parameter "server_version" cannot be changed FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Whelp. That didn't work either. I can't seem to find anything in the oVirt docs on setting this.
How am I supposed to do this?
Thanks! ~Stack~
_______________________________________________ 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
On Thu, May 3, 2018 at 12:13 AM, Roy Golan <rgolan@redhat.com> wrote:
On Wed, 2 May 2018 at 23:27 Jamie Lawrence <jlawrence@squaretrade.com> wrote:
I've been down this road. Postgres won't lie about its version for you. If you want to do this, you have to patch the Ovirt installer[1]. I stopped trying to use my PG cluster at some point - the relationship between the installer and the product combined with the overly restrictive requirements baked into the installer[2]) makes doing so an ongoing hassle. So I treat Ovirt's PG as an black box; disappointing, considering that we are a very heavy PG shop with a lot of expertise and automation I can't use with Ovirt.
Sorry about that, but not sure it's such a bad choice.
If nothing has changed (my notes are from a few versions ago), everything you need to correct is in
/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/constants.py
Aside from the version, you'll also have to make the knobs for vacuuming match those of your current installation, and I think there was another configurable for something else I'm not remembering right now.
Be aware that doing so is accepting an ongoing commitment to monkeying with the installer a lot. At one time I thought doing so was the right tradeoff, but it turns out I was wrong.
-j
[1] Or you could rebuild PG with a fake version. That option was unavailable here. [2] Not criticizing, just stating a technical fact. How folks apportion their QA resources is their business.
On May 2, 2018, at 12:49 PM, ~Stack~ <i.am.stack@gmail.com> wrote:
Greetings,
Exploring hosting my engine and ovirt_engine_history db's on my dedicated PostgreSQL server.
This is a 9.5 install on a beefy box from the postgresql.org yum repos that I'm using for other SQL needs too. 9.5.12 to be exact. I set up the database just as the documentation says and I'm doing a fresh install of my engine-setup.
During the install, right after I give it the details for the remote I get this error: [ ERROR ] Please set: server_version = 9.5.9 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .
Huh?
Yes it's annoying and I think +Yaniv Dary opened a bug for it after both of got mad at it. Yaniv?
Yaniv did, and I asked for details. Comments are welcome: https://bugzilla.redhat.com/show_bug.cgi?id=1573091 Of course, if it's so annoying, and we are so confident in PG's compatibility inside z-stream, we can simply lax the test by checking only x.y but changing no other functionality, and discuss something stronger later on (if at all). Pushed this for now, didn't verify: https://gerrit.ovirt.org/90866 Ideally, "verification" isn't merely checking that it works as expected, but also coming up with means to enhance our confidence that it's indeed safe. But it might not be such a big risk to merge this anyway, even for 4.2.
Meanwhile let us know if you were able to patch constants.py as suggested.
Um. OK. $ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service
LOG: syntax error in file "/var/lib/pgsql/9.5/data/postgresql.conf" line 33, n...n ".9" FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Well that didn't work. Let's try something else.
$ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service LOG: parameter "server_version" cannot be changed FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Whelp. That didn't work either. I can't seem to find anything in the oVirt docs on setting this.
How am I supposed to do this?
Thanks! ~Stack~
_______________________________________________ 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
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
On Thu, May 3, 2018 at 9:53 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Thu, May 3, 2018 at 12:13 AM, Roy Golan <rgolan@redhat.com> wrote:
On Wed, 2 May 2018 at 23:27 Jamie Lawrence <jlawrence@squaretrade.com> wrote:
I've been down this road. Postgres won't lie about its version for you. If you want to do this, you have to patch the Ovirt installer[1]. I stopped trying to use my PG cluster at some point - the relationship between the installer and the product combined with the overly restrictive requirements baked into the installer[2]) makes doing so an ongoing hassle. So I treat Ovirt's PG as an black box; disappointing, considering that we are a very heavy PG shop with a lot of expertise and automation I can't use with Ovirt.
Sorry about that, but not sure it's such a bad choice.
If nothing has changed (my notes are from a few versions ago), everything you need to correct is in
/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/constants.py
Aside from the version, you'll also have to make the knobs for vacuuming match those of your current installation, and I think there was another configurable for something else I'm not remembering right now.
Be aware that doing so is accepting an ongoing commitment to monkeying with the installer a lot. At one time I thought doing so was the right tradeoff, but it turns out I was wrong.
-j
[1] Or you could rebuild PG with a fake version. That option was unavailable here. [2] Not criticizing, just stating a technical fact. How folks apportion their QA resources is their business.
On May 2, 2018, at 12:49 PM, ~Stack~ <i.am.stack@gmail.com> wrote:
Greetings,
Exploring hosting my engine and ovirt_engine_history db's on my dedicated PostgreSQL server.
This is a 9.5 install on a beefy box from the postgresql.org yum repos that I'm using for other SQL needs too. 9.5.12 to be exact. I set up the database just as the documentation says and I'm doing a fresh install of my engine-setup.
During the install, right after I give it the details for the remote I get this error: [ ERROR ] Please set: server_version = 9.5.9 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .
Huh?
Yes it's annoying and I think +Yaniv Dary opened a bug for it after both of got mad at it. Yaniv?
Yaniv did, and I asked for details. Comments are welcome:
Also filed now a bug about the text: https://bugzilla.redhat.com/show_bug.cgi?id=1578276 Feel free to comment there, and/or on the patch linked to it. Thanks.
Of course, if it's so annoying, and we are so confident in PG's compatibility inside z-stream, we can simply lax the test by checking only x.y but changing no other functionality, and discuss something stronger later on (if at all).
Pushed this for now, didn't verify:
https://gerrit.ovirt.org/90866
Ideally, "verification" isn't merely checking that it works as expected, but also coming up with means to enhance our confidence that it's indeed safe.
But it might not be such a big risk to merge this anyway, even for 4.2.
Meanwhile let us know if you were able to patch constants.py as suggested.
Um. OK. $ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service
LOG: syntax error in file "/var/lib/pgsql/9.5/data/postgresql.conf" line 33, n...n ".9" FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Well that didn't work. Let's try something else.
$ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service LOG: parameter "server_version" cannot be changed FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Whelp. That didn't work either. I can't seem to find anything in the oVirt docs on setting this.
How am I supposed to do this?
Thanks! ~Stack~
_______________________________________________ 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
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
-- Didi
=20 I've been down this road. Postgres won't lie about its version for you.= If you want to do this, you have to patch the Ovirt installer[1]. I sto=
=20 If nothing has changed (my notes are from a few versions ago), everythi= ng you need to correct is in =20 /usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/constant= s.py =20 Aside from the version, you'll also have to make the knobs for vacuumin= g match those of your current installation, and I think there was another= configurable for something else I'm not remembering right now. =20 Be aware that doing so is accepting an ongoing commitment to monkeying = with the installer a lot. At one time I thought doing so was the right tr= adeoff, but it turns out I was wrong. =20 -j =20 [1] Or you could rebuild PG with a fake version. That option was unavai= lable here. [2] Not criticizing, just stating a technical fact. How folks apportion=
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HpiV2ZDmbYGAhuqeTKRLo7E4vSrViQ7Vl Content-Type: multipart/mixed; boundary="GulUwkxST3ljqhkU19OlSpFHZWk3hAxVy"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users <users@ovirt.org> Message-ID: <e8f81dc5-40ef-f2e3-5b1f-fd3215742201@gmail.com> Subject: Re: [ovirt-users] Remote DB: How do you set server_version? References: <3f809af7-4e88-68ed-bb65-99a7584ae8a3@gmail.com> <8D262853-F744-4CFA-976C-E393EC9A9996@squaretrade.com> In-Reply-To: <8D262853-F744-4CFA-976C-E393EC9A9996@squaretrade.com> --GulUwkxST3ljqhkU19OlSpFHZWk3hAxVy Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/02/2018 03:26 PM, Jamie Lawrence wrote: pped trying to use my PG cluster at some point - the relationship betwee= n the installer and the product combined with the overly restrictive requ= irements baked into the installer[2]) makes doing so an ongoing hassle. = So I treat Ovirt's PG as an black box; disappointing, considering that we= are a very heavy PG shop with a lot of expertise and automation I can't = use with Ovirt. their QA resources is their business.
Yikes! OK. Thanks for the warning. I've got better things to do with my time. I will just skip this part of exploring. :-) Thank you! ~Stack~ --GulUwkxST3ljqhkU19OlSpFHZWk3hAxVy-- --HpiV2ZDmbYGAhuqeTKRLo7E4vSrViQ7Vl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa6jQkAAoJELkej+ysXJPml+4P/jlEKHKjL0YWpvq/0ZLqmasI s2PyDKK5h01u+idn+WCEH6SQUGZgIB2t3LBvKs1Ej+Cp2bs+BBnJ661TmicUUtSb pT3a6tv4W0hnG/dXOPJEAxe25o5HDprnHlTnmKrdr88ZHx+yVPfUNHhv5Agg0YVw Hi2vKJnSLKCMYaaJd/4wj8ckuQ4sHlp/2PbQ0nCMBJmLaIu7byCOE8Q+Sn4CUQvZ 1BOefVOmg3dshNs/0XGQ761tDTDTbCmzSZqqXGQiLBQOIhyiuskDR0a9Gco1HRP5 iPbY4rYvpfuPpVVIdNsJ9ZYZccMDFMuaYfDGwJi/ltOJSDJJ0LFICWpAT095ysef RORaZ8FJc50fJPzqJHRoSr6nNxWKY2WrMzT/9O5lS6XM7Kp0kHKKUan1bKb2KCmM Z0OlxWIb8HyQ5tUZbCp7+N+do2KfFeR/oCz9nPw+miwTizPZMGBcycd9Q9og+gls BUhOqZHbK1xG6CDKx+pTDZo2Q+Dow3uksntJNvpU0PMZxyivT5jxH3DGgexdvS5k 0Y96+jwqR84DljMzvCM3dTaf1Qs61UYgHuKNQ/uVKjvPY0iVHJj2YO0c+8ybo5f2 GlQ+NURwOAQ0jH3FXuUiMVVIwOjKTRJ9NXTti560tKUlyFQ/4LDaUmtR4kMgXkKj CD/miW2AV8eKUis2zSEO =IxTv -----END PGP SIGNATURE----- --HpiV2ZDmbYGAhuqeTKRLo7E4vSrViQ7Vl--
On Wed, May 2, 2018 at 11:26 PM, Jamie Lawrence <jlawrence@squaretrade.com> wrote:
I've been down this road. Postgres won't lie about its version for you. If you want to do this, you have to patch the Ovirt installer[1]. I stopped trying to use my PG cluster at some point - the relationship between the installer and the product combined with the overly restrictive requirements baked into the installer[2]) makes doing so an ongoing hassle. So I treat Ovirt's PG as an black box; disappointing, considering that we are a very heavy PG shop with a lot of expertise and automation I can't use with Ovirt.
Patches are welcome to improve the way oVirt uses Postgresql, supports various versions, etc. Can you give examples for some of the things you'd do differently? If nothing has changed (my notes are from a few versions ago), everything
you need to correct is in
/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_ common/constants.py
Aside from the version, you'll also have to make the knobs for vacuuming match those of your current installation, and I think there was another configurable for something else I'm not remembering right now.
Be aware that doing so is accepting an ongoing commitment to monkeying with the installer a lot. At one time I thought doing so was the right tradeoff, but it turns out I was wrong.
At least we can start with documenting their location and default values - if that's not the case already, and when/why change them. An ovirt.org blog entry would be welcome too. Y.
-j
[1] Or you could rebuild PG with a fake version. That option was unavailable here. [2] Not criticizing, just stating a technical fact. How folks apportion their QA resources is their business.
On May 2, 2018, at 12:49 PM, ~Stack~ <i.am.stack@gmail.com> wrote:
Greetings,
Exploring hosting my engine and ovirt_engine_history db's on my dedicated PostgreSQL server.
This is a 9.5 install on a beefy box from the postgresql.org yum repos that I'm using for other SQL needs too. 9.5.12 to be exact. I set up the database just as the documentation says and I'm doing a fresh install of my engine-setup.
During the install, right after I give it the details for the remote I get this error: [ ERROR ] Please set: server_version = 9.5.9 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .
Huh?
Um. OK. $ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service
LOG: syntax error in file "/var/lib/pgsql/9.5/data/postgresql.conf" line 33, n...n ".9" FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Well that didn't work. Let's try something else.
$ grep ^server_version postgresql.conf server_version = 9.5.9
$ systemctl restart postgresql-9.5.service LOG: parameter "server_version" cannot be changed FATAL: configuration file "/var/lib/pgsql/9.5/data/postgresql.conf" contains errors
Whelp. That didn't work either. I can't seem to find anything in the oVirt docs on setting this.
How am I supposed to do this?
Thanks! ~Stack~
_______________________________________________ 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
On May 3, 2018, at 12:42 AM, Yaniv Kaul <ykaul@redhat.com> wrote:
Patches are welcome to improve the way oVirt uses Postgresql, supports various versions, etc. Can you give examples for some of the things you'd do differently?
A little pre-ramble - I was trying not to be offensive in talking about this, and hope I didn't bother anyone. For the record, if I were supreme dictator of the project, I might well make the same choices. Attention is limited, DB-flexibility is nowhere near a top-line feature, DB compatibility issues can be complex and subtle, and QA is a limited resource. I don't know that those are the concerns responsible for the current stance, but can totally see good reasons as to why things are they way they are. Anyway, I've been thinking about is an installer mode that treats the DB as Someone Else's Problem - it doesn't try to install, configure or monitor it, instead leaving all config and responsibility for selecting something that works to the administrator. The assumption is that crazy people like me will figure out if things won't work against a given version, and over time the list will be capable of assuming some of that QA responsibility. That leaves the normal path for the bulk of users, and those who want to assume the risk can point at their own clusters where the closest running version is almost always going to be a point-release or three away from whatever Ovirt tests against and configuration is quite different. What I have not done is written any code. I'd like to, but I'm probably several months away from having time. -j
participants (5)
-
Jamie Lawrence -
Roy Golan -
Yaniv Kaul -
Yedidyah Bar David -
~Stack~