[ovirt-devel] Fwd: Reminder: Fedora 22 end of life 2016-07-19

FYI -- Messaggio inoltrato -- Da: "Dennis Gilmore" Data: 23/Giu/2016 06:43 Oggetto: Reminder: Fedora 22 end of life 2016-07-19 A: , "test-announce" < test-annou...@lists.fedoraproject.org>, "announce" <

[ovirt-devel] Storage in VDSM questions

Hi! I have a bunch of questions related to storage in VDSM. I would be happy if anybody familiar with the subject can help me with them. 1. What is HSM? IRS? 2. What is SDM? 3. What hsm.spmSchedule() method does? 4. What does domainMonitor.getHostId(vol_info.sd_id) method return? Storage domain

Re: [ovirt-devel] ovirt-system tests 4.0 using 3.6 code

New patch [1] fixed 4.0. Let me know if you want to merge it or try to fix the repos for 4.0 instead. [1] https://gerrit.ovirt.org/#/c/59603/ On Wed, Jun 22, 2016 at 3:03 PM, Eyal Edri wrote: > > > On Wed, Jun 22, 2016 at 2:55 PM, Yaniv Kaul wrote: > >> >>

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 2:17 PM, Martin Sivak wrote: > > That's not automation, its just you (human) building the official build > in > > COPR > > rather in jenkins no? > > It is automated enough for me, I just upload (the equivalent of > tagging) the srpm and it builds it for

Re: [ovirt-devel] ovirt-system tests 4.0 using 3.6 code

On Wed, Jun 22, 2016 at 2:55 PM, Yaniv Kaul wrote: > > > On Wed, Jun 22, 2016 at 2:49 PM, Eyal Edri wrote: > >> >> >> On Wed, Jun 22, 2016 at 2:27 PM, Yaniv Kaul wrote: >> >>> >>> >>> On Wed, Jun 22, 2016 at 12:28 PM, Eyal Edri

Re: [ovirt-devel] Killing XMLRPC on master

On Wed, Jun 22, 2016 at 1:22 PM, Martin Sivak wrote: > > We do not have hierarchical topic system. Please note that we have > > p2p communication and real broker is not part of the scope anymore. > > We only have mini broker implemented in vdsm. > > But then I can't implement

Re: [ovirt-devel] ovirt-system tests 4.0 using 3.6 code

On Wed, Jun 22, 2016 at 2:49 PM, Eyal Edri wrote: > > > On Wed, Jun 22, 2016 at 2:27 PM, Yaniv Kaul wrote: > >> >> >> On Wed, Jun 22, 2016 at 12:28 PM, Eyal Edri wrote: >> >>> After the recent merge of testing install of

Re: [ovirt-devel] ovirt-system tests 4.0 using 3.6 code

On Wed, Jun 22, 2016 at 2:27 PM, Yaniv Kaul wrote: > > > On Wed, Jun 22, 2016 at 12:28 PM, Eyal Edri wrote: > >> After the recent merge of testing install of ovirt-cockpit-dashboard to >> 3.6, >> the 4.0 tests failed also. [1] >> > > They should not have

Re: [ovirt-devel] ovirt-system tests 4.0 using 3.6 code

On Wed, Jun 22, 2016 at 12:28 PM, Eyal Edri wrote: > After the recent merge of testing install of ovirt-cockpit-dashboard to > 3.6, > the 4.0 tests failed also. [1] > They should not have failed. The only reason they could have failed is if there were added deps - and there

Re: [ovirt-devel] Killing XMLRPC on master

> We do not have hierarchical topic system. Please note that we have > p2p communication and real broker is not part of the scope anymore. > We only have mini broker implemented in vdsm. But then I can't implement the parasitic way of listening to data. This is basic functionality when you want

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

> That's not automation, its just you (human) building the official build in > COPR > rather in jenkins no? It is automated enough for me, I just upload (the equivalent of tagging) the srpm and it builds it for all platforms. It is then automatically released in the project repository. COPR is

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 12:49 PM, Martin Sivak wrote: > > What I think we should do is to add support that once an official tag is > > done an official build will be triggered and done. > > The question is can the official build flow be automated? IIRC it > involves > > using

Re: [ovirt-devel] Killing XMLRPC on master

On Wed, Jun 22, 2016 at 12:13 PM, Martin Sivak wrote: > > It is not about having a topic but listing what should be posted to that > > topic. > > That is the whole point of having a hierarchical topic based system. > Engine would listen for anything coming from vdsm, vdsm

Re: [ovirt-devel] Killing XMLRPC on master

> It is not about having a topic but listing what should be posted to that > topic. That is the whole point of having a hierarchical topic based system. Engine would listen for anything coming from vdsm, vdsm would listen for anything that comes from engine using a path wildcard. Just use a

Re: [ovirt-devel] Killing XMLRPC on master

On Wed, Jun 22, 2016 at 11:40 AM, Martin Sivak wrote: > > If we subscribe to engine response queue we receive all the traffic. At > the > > moment there is no way > > to define verbs we listen to. This functionality is only for events. > > Can't we create a new topic /engine/

Re: [ovirt-devel] Killing XMLRPC on master

On Wed, Jun 22, 2016 at 12:24 PM, Piotr Kliczewski wrote: > > > On Wed, Jun 22, 2016 at 10:39 AM, Michal Skrivanek > wrote: >> >> >> On 20 Jun 2016, at 18:41, Piotr Kliczewski wrote: >> >> >> >> On Mon, Jun 20, 2016 at 6:22

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

> What I think we should do is to add support that once an official tag is > done an official build will be triggered and done. > The question is can the official build flow be automated? IIRC it involves > using tarball + signing or some other manual work which isn't > similar to the way nigthly

Re: [ovirt-devel] Killing XMLRPC on master

> If we subscribe to engine response queue we receive all the traffic. At the > moment there is no way > to define verbs we listen to. This functionality is only for events. Can't we create a new topic /engine/ for each verb and configure vdsm to listen for /engine/*? That would duplicate what we

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 11:21 AM, Martin Sivak wrote: > > - you as packager / maintainer should add your build to the release > > configuration file[1] or send an email with the link to your builds to > the > > person handling the release > > Is there a way to automate this?

Re: [ovirt-devel] Killing XMLRPC on master

Hi, > Wouldn't that mean you need the whole authentication and communication > code duplicated to mom? or is it already in there? Not really, MOM would connect to the local VDSM (as it does now, just with a different protocol), not to engine directly. All data will still flow using the single

[ovirt-devel] ovirt-system tests 4.0 using 3.6 code

After the recent merge of testing install of ovirt-cockpit-dashboard to 3.6, the 4.0 tests failed also. [1] And then I found out that some of the 4.0 tests are linked to 3.6 still, is this intentional? Should we now create a new separate 4.0 test or change the link to master? lrwxrwxrwx. 1 eedri

Re: [ovirt-devel] Killing XMLRPC on master

On Wed, Jun 22, 2016 at 10:39 AM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > On 20 Jun 2016, at 18:41, Piotr Kliczewski wrote: > > > > On Mon, Jun 20, 2016 at 6:22 PM, Nir Soffer wrote: > >> On Mon, Jun 20, 2016 at 11:33 AM, Martin Sivak

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

On Wed, Jun 22, 2016 at 11:21 AM, Martin Sivak wrote: >> - you as packager / maintainer should add your build to the release >> configuration file[1] or send an email with the link to your builds to the >> person handling the release > > Is there a way to automate this? Like

Re: [ovirt-devel] Killing XMLRPC on master

On 22/06/16 10:39, Michal Skrivanek wrote: > bypassing vdsm for mom things is a good idea, but we need to make sure we’re > not killing the rest of the system Wouldn't that mean you need the whole authentication and communication code duplicated to mom? or is it already in there? from a

Re: [ovirt-devel] [TIPS] How to get your package released in oVirt

> - you as packager / maintainer should add your build to the release > configuration file[1] or send an email with the link to your builds to the > person handling the release Is there a way to automate this? Like giving you the URL of the release repository in COPR and using whatever latest

Re: [ovirt-devel] oVirt 3.6.7 Fifth Release Candidate is now available for testing

On Wed, Jun 22, 2016 at 11:13 AM, Sven Kieske wrote: > On 22/06/16 09:50, Yaniv Kaul wrote: > > It's harder to do for minor releases, as they don't have distinct target > > milestones as major versions do. > > For example, 4.0 has 4.0.0-rc1, 4.0.0-rc2, 4.0.0-rc3, etc. > >

Re: [ovirt-devel] oVirt 3.6.7 Fifth Release Candidate is now available for testing

On 22/06/16 09:50, Yaniv Kaul wrote: > It's harder to do for minor releases, as they don't have distinct target > milestones as major versions do. > For example, 4.0 has 4.0.0-rc1, 4.0.0-rc2, 4.0.0-rc3, etc. > 3.6.7 doesn't have that. > Y. But there are no special categories for the 4.0.0 rcs as

Re: [ovirt-devel] new per patch testing for ovirt system tests via standard CI

And of course thanks for David to helping me iron out all the issues :) On Wed, Jun 22, 2016 at 10:56 AM, dcaro wrote: > > +1000! > > On 06/22 10:54, Eyal Edri wrote: > > FYI, > > > > I've added a check-patch check for new patches in ovirt-system-tests, so > it > > will run

Re: [ovirt-devel] new per patch testing for ovirt system tests via standard CI

+1000! On 06/22 10:54, Eyal Edri wrote: > FYI, > > I've added a check-patch check for new patches in ovirt-system-tests, so it > will run the relevant suite according to the new test. > > So if you change something in 'basic_suite_3.6 'for e.g, it will only > trigger the 3.6 tests. > if you

[ovirt-devel] new per patch testing for ovirt system tests via standard CI

FYI, I've added a check-patch check for new patches in ovirt-system-tests, so it will run the relevant suite according to the new test. So if you change something in 'basic_suite_3.6 'for e.g, it will only trigger the 3.6 tests. if you change something in 'common' it will trigger all the tests.

Re: [ovirt-devel] oVirt 3.6.7 Fifth Release Candidate is now available for testing

On Tue, Jun 21, 2016 at 9:54 PM, Sven Kieske wrote: > Hi, > > while I appreciate all the work > that has been done for this release, please > let me add some critic: > > on the old website it was pretty easy to track > down what exactly changed between each release >

[ovirt-devel] [TIPS] How to get your package released in oVirt

Hi, since it seems not clear how to get your package included in a oVirt release, here's the procedure: - a new build planned is communicated to devel@ovirt.org from release engineering team - you as package maintainer should prepare your package to be released with desired version (configure.ac,