Team, I got two oVirt Servers. One in 4.0.2 and one in 3.6.X I love the new 4.0 dashboard, But I need a way to continue to build reports with ease, 3.6 Can do this with ovirt-reports. How can I make my oVirt 4.0.2 send data for reports to my ovirt reports on 3.6? Thanks for the help team! Regards, -- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
Team,
I got two oVirt Servers. One in 4.0.2 and one in 3.6.X I love the new 4.0 dashboard, But I need a way to continue to build reports with ease, 3.6 Can do this with ovirt-reports. How can I make my oVirt 4.0.2 send data for reports to my ovirt reports on 3.6?
Thanks for the help team!
I didn't try this myself, but pointing your reports setup to the 4.0 dwh database should work. If you have problems, please give more details - it's not clear what exactly you have on each machine. Generally speaking, oVirt does not currently provide tools to make the engine or dwh "send data" elsewhere (a 3.6 reports or whatever). You can try doing this yourself using generic postgresql means/tools. Best -- Didi
David, Thats exactly what I am trying to accomplish. When I re-run the ovirt setup on my 3.6 system, I give it the IP of my ovirt 4.0 machine, Do I leave the DB to the default name? Is there a db user and password on the 4.0 machine? Sorry for so many questions... This is not documented... Thank you for all the help! Regards, -- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org On Sun, Aug 14, 2016, at 02:01 AM, Yedidyah Bar David wrote:
On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
Team,
I got two oVirt Servers. One in 4.0.2 and one in 3.6.X I love the new 4.0 dashboard, But I need a way to continue to build reports with ease, 3.6 Can do this with ovirt-reports. How can I make my oVirt 4.0.2 send data for reports to my ovirt reports on 3.6?
Thanks for the help team!
I didn't try this myself, but pointing your reports setup to the 4.0 dwh database should work. If you have problems, please give more details - it's not clear what exactly you have on each machine.
Generally speaking, oVirt does not currently provide tools to make the engine or dwh "send data" elsewhere (a 3.6 reports or whatever). You can try doing this yourself using generic postgresql means/tools.
Best -- Didi
On Sun, Aug 14, 2016 at 6:57 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
Thats exactly what I am trying to accomplish. When I re-run the ovirt setup on my 3.6 system, I give it the IP of my ovirt 4.0 machine, Do I leave the DB to the default name? Is there a db user and password on the 4.0 machine?
Sorry for so many questions... This is not documented...
Not for 3.6 vs 4.0, but it actually is, here: http://www.ovirt.org/develop/release-management/features/engine/separate-rep... See also: http://www.ovirt.org/develop/release-management/features/engine/separate-dwh... In above, each of engine, dwh, reports is in its own machine. You can do a similar thing with engine+dwh on one and reports on another. Do not hesitate ping back if you are stuck! Best,
Thank you for all the help!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Sun, Aug 14, 2016, at 02:01 AM, Yedidyah Bar David wrote:
On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
Team,
I got two oVirt Servers. One in 4.0.2 and one in 3.6.X I love the new 4.0 dashboard, But I need a way to continue to build reports with ease, 3.6 Can do this with ovirt-reports. How can I make my oVirt 4.0.2 send data for reports to my ovirt reports on 3.6?
Thanks for the help team!
I didn't try this myself, but pointing your reports setup to the 4.0 dwh database should work. If you have problems, please give more details - it's not clear what exactly you have on each machine.
Generally speaking, oVirt does not currently provide tools to make the engine or dwh "send data" elsewhere (a 3.6 reports or whatever). You can try doing this yourself using generic postgresql means/tools.
Best -- Didi
-- Didi
Thanks David! Regards, -- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org On Mon, Aug 15, 2016, at 12:31 AM, Yedidyah Bar David wrote:
On Sun, Aug 14, 2016 at 6:57 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
Thats exactly what I am trying to accomplish. When I re-run the ovirt setup on my 3.6 system, I give it the IP of my ovirt 4.0 machine, Do I leave the DB to the default name? Is there a db user and password on the 4.0 machine?
Sorry for so many questions... This is not documented...
Not for 3.6 vs 4.0, but it actually is, here:
http://www.ovirt.org/develop/release-management/features/engine/separate-rep...
See also:
http://www.ovirt.org/develop/release-management/features/engine/separate-dwh...
In above, each of engine, dwh, reports is in its own machine. You can do a similar thing with engine+dwh on one and reports on another.
Do not hesitate ping back if you are stuck!
Best,
Thank you for all the help!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Sun, Aug 14, 2016, at 02:01 AM, Yedidyah Bar David wrote:
On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
Team,
I got two oVirt Servers. One in 4.0.2 and one in 3.6.X I love the new 4.0 dashboard, But I need a way to continue to build reports with ease, 3.6 Can do this with ovirt-reports. How can I make my oVirt 4.0.2 send data for reports to my ovirt reports on 3.6?
Thanks for the help team!
I didn't try this myself, but pointing your reports setup to the 4.0 dwh database should work. If you have problems, please give more details - it's not clear what exactly you have on each machine.
Generally speaking, oVirt does not currently provide tools to make the engine or dwh "send data" elsewhere (a 3.6 reports or whatever). You can try doing this yourself using generic postgresql means/tools.
Best -- Didi
-- Didi
David, After an attempt to run this remote setup something went really wrong and my dwh went fubar on my ovirt 4.0 I got: 2016-08-15 16:03:34|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|43800 hoursToKeepHourly|1440 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|20 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.0.2 dwhAggregationDebug|false dwhUuid|759f3eb5-5072-4c28-9686-a363eb956077 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** Exception in component tJDBCInput_2 org.postgresql.util.PSQLException: ERROR: relation "history_configuration" does not exist Position: 65 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:283) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCInput_2Process(MinimalVersionCheck.java:1574) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCInput_1Process(MinimalVersionCheck.java:1229) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCConnection_2Process(MinimalVersionCheck.java:782) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCConnection_1Process(MinimalVersionCheck.java:657) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.runJobInTOS(MinimalVersionCheck.java:3089) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.runJob(MinimalVersionCheck.java:2853) at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Process(HistoryETL.java:8009) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryETL.java:11520) 2016-08-15 16:03:34|NAl0ai|349e7f|349e7f|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|6|Java Exception|tJDBCInput_2|org.postgresql.util.PSQLException:ERROR: relation "history_configuration" does not exist Position: 65|1 Exception in component tRunJob_2 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Process(HistoryETL.java:8032) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryETL.java:11520) 2016-08-15 16:03:34|349e7f|349e7f|349e7f|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java Exception|tRunJob_2|java.lang.RuntimeException:Child job running failed|1 2016-08-15 16:03:34|ETL Service Stopped Can you please help? Regards, -- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org On Mon, Aug 15, 2016, at 10:16 AM, Fernando Fuentes wrote:
Thanks David!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Mon, Aug 15, 2016, at 12:31 AM, Yedidyah Bar David wrote:
On Sun, Aug 14, 2016 at 6:57 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
Thats exactly what I am trying to accomplish. When I re-run the ovirt setup on my 3.6 system, I give it the IP of my ovirt 4.0 machine, Do I leave the DB to the default name? Is there a db user and password on the 4.0 machine?
Sorry for so many questions... This is not documented...
Not for 3.6 vs 4.0, but it actually is, here:
http://www.ovirt.org/develop/release-management/features/engine/separate-rep...
See also:
http://www.ovirt.org/develop/release-management/features/engine/separate-dwh...
In above, each of engine, dwh, reports is in its own machine. You can do a similar thing with engine+dwh on one and reports on another.
Do not hesitate ping back if you are stuck!
Best,
Thank you for all the help!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Sun, Aug 14, 2016, at 02:01 AM, Yedidyah Bar David wrote:
On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
Team,
I got two oVirt Servers. One in 4.0.2 and one in 3.6.X I love the new 4.0 dashboard, But I need a way to continue to build reports with ease, 3.6 Can do this with ovirt-reports. How can I make my oVirt 4.0.2 send data for reports to my ovirt reports on 3.6?
Thanks for the help team!
I didn't try this myself, but pointing your reports setup to the 4.0 dwh database should work. If you have problems, please give more details - it's not clear what exactly you have on each machine.
Generally speaking, oVirt does not currently provide tools to make the engine or dwh "send data" elsewhere (a 3.6 reports or whatever). You can try doing this yourself using generic postgresql means/tools.
Best -- Didi
-- Didi
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, Aug 16, 2016 at 12:09 AM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
(Actually it's "Yedidyah" or "Didi", "Bar David" is my surname)
After an attempt to run this remote setup something went really wrong and my dwh went fubar on my ovirt 4.0
I got:
2016-08-15 16:03:34|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|43800 hoursToKeepHourly|1440 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|20 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.0.2 dwhAggregationDebug|false dwhUuid|759f3eb5-5072-4c28-9686-a363eb956077 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** Exception in component tJDBCInput_2 org.postgresql.util.PSQLException: ERROR: relation "history_configuration" does not exist Position: 65 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:283) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCInput_2Process(MinimalVersionCheck.java:1574) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCInput_1Process(MinimalVersionCheck.java:1229) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCConnection_2Process(MinimalVersionCheck.java:782) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.tJDBCConnection_1Process(MinimalVersionCheck.java:657) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.runJobInTOS(MinimalVersionCheck.java:3089) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck.runJob(MinimalVersionCheck.java:2853) at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Process(HistoryETL.java:8009) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryETL.java:11520) 2016-08-15 16:03:34|NAl0ai|349e7f|349e7f|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|6|Java Exception|tJDBCInput_2|org.postgresql.util.PSQLException:ERROR: relation "history_configuration" does not exist Position: 65|1 Exception in component tRunJob_2 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Process(HistoryETL.java:8032) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryETL.java:11520) 2016-08-15 16:03:34|349e7f|349e7f|349e7f|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java Exception|tRunJob_2|java.lang.RuntimeException:Child job running failed|1 2016-08-15 16:03:34|ETL Service Stopped
Can you please help?
Please provide setup logs on the engine and reports machines. All of /var/log/ovirt-engine/setup/* on both of them. Thanks.
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Mon, Aug 15, 2016, at 10:16 AM, Fernando Fuentes wrote:
Thanks David!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Mon, Aug 15, 2016, at 12:31 AM, Yedidyah Bar David wrote:
On Sun, Aug 14, 2016 at 6:57 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
Thats exactly what I am trying to accomplish. When I re-run the ovirt setup on my 3.6 system, I give it the IP of my ovirt 4.0 machine, Do I leave the DB to the default name? Is there a db user and password on the 4.0 machine?
Sorry for so many questions... This is not documented...
Not for 3.6 vs 4.0, but it actually is, here:
http://www.ovirt.org/develop/release-management/features/engine/separate-rep...
See also:
http://www.ovirt.org/develop/release-management/features/engine/separate-dwh...
In above, each of engine, dwh, reports is in its own machine. You can do a similar thing with engine+dwh on one and reports on another.
Do not hesitate ping back if you are stuck!
Best,
Thank you for all the help!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Sun, Aug 14, 2016, at 02:01 AM, Yedidyah Bar David wrote:
On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
Team,
I got two oVirt Servers. One in 4.0.2 and one in 3.6.X I love the new 4.0 dashboard, But I need a way to continue to build reports with ease, 3.6 Can do this with ovirt-reports. How can I make my oVirt 4.0.2 send data for reports to my ovirt reports on 3.6?
Thanks for the help team!
I didn't try this myself, but pointing your reports setup to the 4.0 dwh database should work. If you have problems, please give more details - it's not clear what exactly you have on each machine.
Generally speaking, oVirt does not currently provide tools to make the engine or dwh "send data" elsewhere (a 3.6 reports or whatever). You can try doing this yourself using generic postgresql means/tools.
Best -- Didi
-- Didi
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
This looks like a DWH, not a reports issue. Are you sure you only install reports remotely? Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary On Tue, Aug 16, 2016 at 8:48 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Tue, Aug 16, 2016 at 12:09 AM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
(Actually it's "Yedidyah" or "Didi", "Bar David" is my surname)
After an attempt to run this remote setup something went really wrong and my dwh went fubar on my ovirt 4.0
I got:
2016-08-15 16:03:34|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://
localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl. NonValidatingFactory
hoursToKeepDaily|43800 hoursToKeepHourly|1440 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost: 5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|20 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.0.2 dwhAggregationDebug|false dwhUuid|759f3eb5-5072-4c28-9686-a363eb956077 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** Exception in component tJDBCInput_2 org.postgresql.util.PSQLException: ERROR: relation "history_configuration" does not exist Position: 65 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse( QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults( QueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute( QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute( AbstractJdbc2Statement.java:555) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags( AbstractJdbc2Statement.java:403) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery( AbstractJdbc2Statement.java:283) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck. tJDBCInput_2Process(MinimalVersionCheck.java:1574) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck. tJDBCInput_1Process(MinimalVersionCheck.java:1229) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck. tJDBCConnection_2Process(MinimalVersionCheck.java:782) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck. tJDBCConnection_1Process(MinimalVersionCheck.java:657) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCheck. runJobInTOS(MinimalVersionCheck.java:3089) at ovirt_engine_dwh.minimalversioncheck_4_0. MinimalVersionCheck.runJob(MinimalVersionCheck.java:2853) at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Process( HistoryETL.java:8009) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryETL. java:11520) 2016-08-15 16:03:34|NAl0ai|349e7f|349e7f|OVIRT_ENGINE_DWH| MinimalVersionCheck|Default|6|Java Exception|tJDBCInput_2|org.postgresql.util.PSQLException:ERROR: relation "history_configuration" does not exist Position: 65|1 Exception in component tRunJob_2 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Process( HistoryETL.java:8032) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryETL. java:11520) 2016-08-15 16:03:34|349e7f|349e7f|349e7f|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java Exception|tRunJob_2|java.lang.RuntimeException:Child job running failed|1 2016-08-15 16:03:34|ETL Service Stopped
Can you please help?
Please provide setup logs on the engine and reports machines. All of /var/log/ovirt-engine/setup/* on both of them. Thanks.
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Mon, Aug 15, 2016, at 10:16 AM, Fernando Fuentes wrote:
Thanks David!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Mon, Aug 15, 2016, at 12:31 AM, Yedidyah Bar David wrote:
On Sun, Aug 14, 2016 at 6:57 PM, Fernando Fuentes <
wrote:
David,
Thats exactly what I am trying to accomplish. When I re-run the ovirt setup on my 3.6 system, I give it the IP of my ovirt 4.0 machine, Do I leave the DB to the default name? Is there a db user and password on the 4.0 machine?
Sorry for so many questions... This is not documented...
Not for 3.6 vs 4.0, but it actually is, here:
http://www.ovirt.org/develop/release-management/features/ engine/separate-reports-host/
See also:
http://www.ovirt.org/develop/release-management/features/ engine/separate-dwh-host/
In above, each of engine, dwh, reports is in its own machine. You can do a similar thing with engine+dwh on one and reports on another.
Do not hesitate ping back if you are stuck!
Best,
Thank you for all the help!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Sun, Aug 14, 2016, at 02:01 AM, Yedidyah Bar David wrote:
On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes <
ffuentes@darktcp.net>
wrote: > Team, > > I got two oVirt Servers. One in 4.0.2 and one in 3.6.X > I love the new 4.0 dashboard, But I need a way to continue to build > reports with ease, 3.6 Can do this with ovirt-reports. How can I make my > oVirt 4.0.2 send data for reports to my ovirt reports on 3.6? > > Thanks for the help team!
I didn't try this myself, but pointing your reports setup to the 4.0 dwh database should work. If you have problems, please give more
ffuentes@darktcp.net> details -
it's not clear what exactly you have on each machine.
Generally speaking, oVirt does not currently provide tools to make the engine or dwh "send data" elsewhere (a 3.6 reports or whatever). You can try doing this yourself using generic postgresql means/tools.
Best -- Didi
-- Didi
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 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Yaniv, Thanks for the reply. Didi, Dully noted! Thank you all for the reply. I got it all fixed. Regards, -- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org On Tue, Aug 16, 2016, at 12:56 AM, Yaniv Dary wrote:
This looks like a DWH, not a reports issue. Are you sure you only install reports remotely?
Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary
On Tue, Aug 16, 2016 at 8:48 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Tue, Aug 16, 2016 at 12:09 AM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
(Actually it's "Yedidyah" or "Didi", "Bar David" is my surname)
After an attempt to run this remote setup something went really wrong and my dwh went fubar on my ovirt 4.0
I got:
2016-08-15 16:03:34|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:54- 32/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidati- ngFactory hoursToKeepDaily|43800 hoursToKeepHourly|1440 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engi- ne?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|20 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.0.2 dwhAggregationDebug|false dwhUuid|759f3eb5-5072-4c28-9686-a363eb956077 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** Exception in component tJDBCInput_2 org.postgresql.util.PSQLException: ERROR: relation "history_configuration" does not exist Position: 65 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResp- onse(QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults(Q- ueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExe- cutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(Abstr- actJdbc2Statement.java:555) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFl- ags(AbstractJdbc2Statement.java:403) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(- AbstractJdbc2Statement.java:283) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCh- eck.tJDBCInput_2Process(MinimalVersionCheck.java:1574) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCh- eck.tJDBCInput_1Process(MinimalVersionCheck.java:1229) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCh- eck.tJDBCConnection_2Process(MinimalVersionCheck.java:782) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCh- eck.tJDBCConnection_1Process(MinimalVersionCheck.java:657) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCh- eck.runJobInTOS(MinimalVersionCheck.java:3089) at ovirt_engine_dwh.minimalversioncheck_4_0.MinimalVersionCh- eck.runJob(MinimalVersionCheck.java:2853) at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Proce- ss(HistoryETL.java:8009) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryE- TL.java:11520) 2016-08-15 16:03:34|NAl0ai|349e7f|349e7f|OVIRT_ENGINE_DWH|MinimalVersionChec- k|Default|6|Java Exception|tJDBCInput_2|org.postgresql.util.PSQLException:ERROR: relation "history_configuration" does not exist Position: 65|1 Exception in component tRunJob_2 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.historyetl_4_0.HistoryETL.tRunJob_2Proce- ss(HistoryETL.java:8032) at ovirt_engine_dwh.historyetl_4_0.HistoryETL$3.run(HistoryE- TL.java:11520) 2016-08-15 16:03:34|349e7f|349e7f|349e7f|OVIRT_ENGINE_DWH|HistoryETL|Default- |6|Java Exception|tRunJob_2|java.lang.RuntimeException:Child job running failed|1 2016-08-15 16:03:34|ETL Service Stopped
Can you please help?
Please provide setup logs on the engine and reports machines. All of /var/log/ovirt-engine/setup/* on both of them. Thanks.
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Mon, Aug 15, 2016, at 10:16 AM, Fernando Fuentes wrote:
Thanks David!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Mon, Aug 15, 2016, at 12:31 AM, Yedidyah Bar David wrote:
On Sun, Aug 14, 2016 at 6:57 PM, Fernando Fuentes <ffuentes@darktcp.net> wrote:
David,
Thats exactly what I am trying to accomplish. When I re-run the ovirt setup on my 3.6 system, I give it the IP of my ovirt 4.0 machine, Do I leave the DB to the default name? Is there a db user and password on the 4.0 machine?
Sorry for so many questions... This is not documented...
Not for 3.6 vs 4.0, but it actually is, here:
http://www.ovirt.org/develop/release-management/features/engine/separate-rep...
See also:
http://www.ovirt.org/develop/release-management/features/engine/separate-dwh...
In above, each of engine, dwh, reports is in its own machine. You can do a similar thing with engine+dwh on one and reports on another.
Do not hesitate ping back if you are stuck!
Best,
Thank you for all the help!
Regards,
-- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org
On Sun, Aug 14, 2016, at 02:01 AM, Yedidyah Bar David wrote: > On Sat, Aug 13, 2016 at 10:38 PM, Fernando Fuentes > <ffuentes@darktcp.net> > wrote: > > Team, > > > > I got two oVirt Servers. One in 4.0.2 and one in 3.6.X > > I love the new 4.0 dashboard, But I need a way to continue > > to build > > reports with ease, 3.6 Can do this with ovirt-reports. How > > can I make my > > oVirt 4.0.2 send data for reports to my ovirt reports on > > 3.6? > > > > Thanks for the help team! > > I didn't try this myself, but pointing your reports setup to > the 4.0 dwh > database should work. If you have problems, please give more > details - > it's not clear what exactly you have on each machine. > > Generally speaking, oVirt does not currently provide tools > to make > the engine or dwh "send data" elsewhere (a 3.6 reports or > whatever). > You can try doing this yourself using generic postgresql > means/tools. > > Best > -- > Didi
-- Didi
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 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Fernando Fuentes -
Yaniv Dary -
Yedidyah Bar David