On 01/02/2017 10:13 PM, Jakub Niedermertl wrote:
> Hi Juan,
>
> from time to time I'd like the REST doc to be available on some public
> site. It would allow us to
> * check the documentation without searching for running engine
> * be able to easily link documentations in irc/mails
> * link rest
Hi Juan,
from time to time I'd like the REST doc to be available on some public
site. It would allow us to
* check the documentation without searching for running engine
* be able to easily link documentations in irc/mails
* link rest doc from ovirt.org site doc
Recently I've also heard similar
On Mon, Jan 2, 2017 at 12:02 PM, Piotr Kliczewski
wrote:
> All,
>
> Some time ago during discussion we noticed that we are missing ability
> to send/receive events from vdsm client [1]. Initially we thought that
> having [2] would be enough to support notification
> I would like to collect potential use cases from mom, hosted engine
> and others so we could design the api to enable them
Both MOM and hosted engine need to monitor VM state (up, down) and
migration status (finished), so at least that is needed.
> Do we have any use cases to subscribe to
On Mon, Jan 2, 2017 at 9:57 AM, Gil Shinar wrote:
> Hi,
>
> The above test failed. Here are the VDSM and engine logs:
> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_
> 4.1/88/artifact/exported-artifacts/basic_suite_4.1.sh-
>
On Mon, Jan 2, 2017 at 10:48 AM, Yaniv Bronheim wrote:
> the report in the audit log is miss leading. I used to find on failures
> the logs under /tmp - but in recent versions it usually copied to /var/log
> already when the log says to find it under /tmp/
>
Not sure how
All,
Some time ago during discussion we noticed that we are missing ability
to send/receive events from vdsm client [1]. Initially we thought that
having [2] would be enough to support notification between engine and
vdsm. Now we know we need it for [1].
I would like to collect potential use
the report in the audit log is miss leading. I used to find on failures the
logs under /tmp - but in recent versions it usually copied to /var/log
already when the log says to find it under /tmp/
On Mon, Jan 2, 2017 at 10:53 AM, Sandro Bonazzola
wrote:
>
>
> On Sun, Jan 1,
On Sun, Jan 1, 2017 at 4:59 PM, Yaniv Bronheim wrote:
> Hi,
> I'm not sure if I'm right or wrong so before filing a bug let me know if I
> don't miss anything - I think the audit log on fail deploy that says the
> path for the deploy log is wrong. few times I already faced
Just FYI,
I was just trying to say that these tests run twice for the same patch.
There's no relation for it to be executed by an fc24 build artifacts job!!
Thanks
Gil
On Mon, Jan 2, 2017 at 9:57 AM, Gil Shinar wrote:
> Hi,
>
> The above test failed. Here are the VDSM and
10 matches
Mail list logo