[ovirt-devel] Re: Request for adding ovirt-engine-sdk-go as an incubator project under oVirt

2019-01-15 Thread Joey Ma 
Sincerely thanks for your supports. I will surely commit myself to proceed
with the contributions to this project and others on oVirt.

Regards,
Joey

On Tue, Jan 15, 2019 at 11:53 PM Ondra Machacek  wrote:

>
>
> On 1/15/19 10:39 AM, Martin Perina wrote:
> > On Tue, Jan 15, 2019 at 10:35 AM Sandro Bonazzola 
> > wrote:
> >
> >>
> >>
> >> Il giorno mar 15 gen 2019 alle ore 10:07 Joey Ma 
> ha
> >> scritto:
> >>
> >>>
> >>>
> >>> On Tue, Jan 15, 2019 at 4:07 PM Sandro Bonazzola 
> >>> wrote:
> >>>
> 
> 
>  Il giorno mar 15 gen 2019 alle ore 03:09 Joey Ma  >
>  ha scritto:
> 
> > Hi fellows,
> >
> > My name is Joey. Now I'm maintaining the project
> ovirt-engine-sdk-go[1]
> > which provides a Golang based sdk for oVirt engine REST API.
> >
> > During the past year, I was keeping in touch Ondra, Juan and Martin.
> > It's very appreciated that they helped me a lot to improve the sdk
> and also
> > added me into the oVirt developer team[2] in github. Both Ondra and
> I think
> > that the project is in great shape and ready for production use. :-)
> >
> > The original plan is to add the project into oVirt 4.3 official
> > release. While according to the schedules[3] for 4.3, maybe there's
> no
> > enough time to make it done due to some additional CI work.
> >
> > So if I may ask, is that possible to add the project as an oVirt
> > incubator project first, by transferring the project from my personal
> > account to oVirt orgnization in github or gerrit? And then accept it
> as a
> > full oVirt project after all the graduation requirements are matched.
> >
> > Thank you all in advance.
> >
> > Regards,
> > Joey
> >
> >
>  Hi Joey, before submitting the incubation request to the oVirt Board,
>  I'm reviewing the process:
>  https://ovirt.org/develop/projects/incubating-an-subproject.html
>  Your project integrates with oVirt API extending them for Go language
>  support so on this we are ok.
>  Are you committing to maintain the project supporting the release
>  schedule of oVirt project?
> 
> >>>
> >>> Yes, for sure.
> >>>
> >>>
>  License of the project is ASL 2.0 so it's in approved licenses.
>  Project has 4 releases and 1 maintainer so it classify as project in
>  developing stage. It's a small project so I believe that the
> classification
>  here is not really correct.
> 
> >>>
> >>> Yes, agreed.
> >>>
> >>>
>  Project has 5 contributors so the onboarding requires 3 "+1" votes.
>  My only concern is that last release is 4.0.6 and dates October 2018.
> I
>  would expect a 4.3.0 release aligned with oVirt Engine 4.3 API.
> 
> >>>
> >>> I use 4.0.x to represent that it's not an official release. Current
> 4.0.6
> >>> is keeping in sync with the official Java sdk 4.2.5 release. While
> maybe I
> >>> should have followed the Python sdk instead, which is already in 4.2.9
> :-)
> >>>
> >>>
>  I think that if you can release such version, I can give my +1 to
>  onboarding this project in incubation state and propose it to the
> Board.
> 
> >>>
> >>> OK. I just released 4.3.0 a couple of minutes ago, which adopted the
> >>> metamodel-1.3.0 and model-4.3.20 for sdk generation.
> >>>
> >>
> >> Ok, so, +1 on my side. Ondra? Martin?
> >>
> >
> > Definitely +1 from me.
> >
> > Joey, thanks a lot for the great work you have done so far on the project
> > and please continue with your contributions!
>
> +1 Thanks a lot for your contribution!
>
> >
> >>
> >>
> >>
> >>>
> >>> In any case, thanks for your commitment improving oVirt, very nice job!
> 
> >>>
> >>> That's my pleasure. Great thanks for your help.
> >>>
> >>>
> 
> 
> 
> > [1]: https://github.com/imjoey/ovirt-engine-sdk-go
> > [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460
> > [3]:
> >
> https://www.ovirt.org/develop/release-management/releases/4.3/release-management.html
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> >
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OCABRD46XI6ADAIBMADJICMSJEXOWQM7/
> >
> 
> 
>  --
> 
>  SANDRO BONAZZOLA
> 
>  MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> 
>  Red Hat EMEA 
> 
>  sbona...@redhat.com
>  
> 
> >>>
> >>
> >> --
> >>
> >> SANDRO BONAZZOLA
> >>
> >> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> >>
> >> Red Hat EMEA 
> >>
> >> sbona...@redhat.com
> >> 
> >>
> >
> >
>
___
Devel

[ovirt-devel] Re: [VDSM] Network tests started to fail on Fedora 28 in travis

2019-01-15 Thread Nir Soffer 
On Tue, Jan 15, 2019 at 8:51 PM Nir Soffer  wrote:

>  ERROR at setup of TestOvsApiBase.test_execute_a_single_command
> 
> @pytest.fixture(scope='session', autouse=True)
> def ovs_service():
> service = OvsService()
> with xfail_when_running_on_travis_with_centos():
> >   service.setup()
> network/integration/ovs/conftest.py:38:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _
> self = 
> def setup(self):
> if not self.ovs_init_state_is_up:
> cmd.exec_sync([OVS_CTL, '--system-id=random', 'start'])
> >   assert self.is_service_running()
> E   AssertionError
> This line looks wrong:
>
>  with xfail_when_running_on_travis_with_centos()
>
> The test fail on Fedora:
> https://travis-ci.org/nirs/vdsm/jobs/480027211
> https://travis-ci.org/nirs/vdsm/jobs/480027212
>
> works on CentOS:
> https://travis-ci.org/nirs/vdsm/jobs/480027210
>
> Looks like we need to switch the check to Fedora.
>
> I think this started to fail today, after I rebuild the Fedora 28 image:
> https://gerrit.ovirt.org/c/96847/
>
> maybe an update in Fedora is related?
>

Whatever the reason, this fixes the build:
https://gerrit.ovirt.org/c/96928/

Green again:
https://travis-ci.org/nirs/vdsm/builds/480043578



>
> Nir
>
>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/RTC346UUU3WJ6VEWIFDN6AT47ZIMUZM7/

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

2019-01-15 Thread Martin Perina 
On Tue, Jan 15, 2019 at 6:28 PM Martin Perina  wrote:

> There is way how to replace directory from previous package version with a
> symlink in new version, we are already using this in other roles. Ondro,
> could you please share the details about this hack?
>

Ahh, sorry, I see that your are already using this hack:
https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/ovirt-ansible-hosted-engine-setup.spec.in#L25
But why is this not working? We have already used that in ovirt-infra role
several times:

1. during the upgrade from 4.1, when we split roles to multiple packages (1
role per RPM)

https://github.com/oVirt/ovirt-ansible-infra/commit/79b62e77f8d1d1cf24f04fb3e80a15327dd884d7

2. when we needed to overcome latest case sensitive issues in galaxy. And
in both cases packages were upgraded successfully

https://github.com/oVirt/ovirt-ansible-infra/commit/a80002d4966241b819625ec5c9e534e108f4029c

So what's different in the hosted-engine role case?

>
>
> On Tue, 15 Jan 2019, 13:24 Simone Tiraboschi 
>>
>>
>> On Tue, Jan 15, 2019 at 11:15 AM Yedidyah Bar David 
>> wrote:
>>
>>> On Tue, Jan 15, 2019 at 11:38 AM Dafna Ron  wrote:
>>> >
>>> > The last ovirt-engine package ran on Jan 11th and this failure
>>> happened on the 14th so the appliance package is suppose to be newer then
>>> the engine and should be running fine.
>>> > if this is not the case, then I suggest that the maintainers of the
>>> project see what is needed to be updated and trigger a new package build
>>> (which is why I was alerting to the failure)
>>> >
>>> > Thanks,
>>> > Dafna
>>> >
>>> >
>>> > On Tue, Jan 15, 2019 at 6:51 AM Yedidyah Bar David 
>>> wrote:
>>> >>
>>> >> On Mon, Jan 14, 2019 at 2:15 PM Dafna Ron  wrote:
>>> >> >
>>> >> > Hi,
>>> >> >
>>> >> > we are failing test 001_upgrade_engine.test_initialize_engine on
>>> ovirt 4.2 for project ovirt-ansible-hosted-engine-setup.
>>> >> >
>>> >> > Patch reported by CQ:
>>> >> >
>>> >> >
>>> https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d38719de663cb8ade13eb8bdff2d1e6f
>>> - Rename the role - replacing '-' with '_'
>>> >> >
>>> >> > Ido, can you please check this issue?
>>> >> >
>>> >> > failed build:
>>> >> >
>>> >> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/
>>>
>>> This build has a single failure:
>>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/testReport/junit/(root)/001_upgrade_engine/running_tests___upgrade_from_release_suite_el7_x86_64___test_initialize_engine/
>>>
>>> which is in the upgrade_from_release suite, not hosted-engine.
>>>
>>> However, I looked at the logs, and the root cause indeed seems to be
>>> related to hosted-engine, as the CQ identified (Nice!), which is:
>>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/artifact/upgrade-from-release-suite.el7.x86_64/lago_logs/lago.log/*view*/
>>>
>>> 2019-01-14 10:38:38,168::ssh.py::ssh::58::lago.ssh::DEBUG::Running
>>> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine: yum -y update
>>> ovirt-*setup*
>>> 2019-01-14 10:38:39,732::ssh.py::ssh::81::lago.ssh::DEBUG::Command
>>> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine returned with 1
>>> 2019-01-14 10:38:39,733::ssh.py::ssh::89::lago.ssh::DEBUG::Command
>>> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine output:
>>>  Loaded plugins: fastestmirror, versionlock
>>> Determining fastest mirrors
>>> Excluding 9 updates due to versionlock (use "yum versionlock status"
>>> to show them)
>>> Resolving Dependencies
>>> --> Running transaction check
>>> ---> Package ovirt-ansible-engine-setup.noarch 0:1.1.5-1.el7 will be
>>> updated
>>> ---> Package ovirt-ansible-engine-setup.noarch
>>> 0:1.1.7-0.1.master.20181219093302.el7 will be an update
>>> ---> Package ovirt-ansible-hosted-engine-setup.noarch 0:1.0.2-1.el7
>>> will be updated
>>> ---> Package ovirt-ansible-hosted-engine-setup.noarch
>>> 0:1.0.6-0.1.master.20190114102323.el7 will be an update
>>> ---> Package ovirt-engine-dwh-setup.noarch 0:4.2.4.3-1.el7 will be
>>> updated
>>> ---> Package ovirt-engine-dwh-setup.noarch
>>> 0:4.2.5-0.0.master.20180708055101.el7 will be an update
>>> ---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
>>> 0:1.3.8-1.el7 will be updated
>>> ---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
>>> 0:1.3.9-0.0.master.gitc39177c.el7 will be an update
>>> --> Processing Dependency: ovirt-engine-extension-aaa-ldap =
>>> 1.3.9-0.0.master.gitc39177c.el7 for package:
>>>
>>> ovirt-engine-extension-aaa-ldap-setup-1.3.9-0.0.master.gitc39177c.el7.noarch
>>> ---> Package ovirt-engine-setup.noarch 0:4.2.7.5-1.el7 will be updated
>>> ---> Package ovirt-engine-setup.noarch
>>> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
>>> ---> Package ovirt-engine-setup-base.noarch 0:4.2.7.5-1.el7 will be
>>> updated
>>> ---> Package ovirt-engine-setup-base.noarch
>>> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
>>>

[ovirt-devel] [VDSM] Network tests started to fail on Fedora 28 in travis

2019-01-15 Thread Nir Soffer 
 ERROR at setup of TestOvsApiBase.test_execute_a_single_command

@pytest.fixture(scope='session', autouse=True)
def ovs_service():
service = OvsService()
with xfail_when_running_on_travis_with_centos():
>   service.setup()
network/integration/ovs/conftest.py:38:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _
self = 
def setup(self):
if not self.ovs_init_state_is_up:
cmd.exec_sync([OVS_CTL, '--system-id=random', 'start'])
>   assert self.is_service_running()
E   AssertionError
This line looks wrong:

 with xfail_when_running_on_travis_with_centos()

The test fail on Fedora:
https://travis-ci.org/nirs/vdsm/jobs/480027211
https://travis-ci.org/nirs/vdsm/jobs/480027212

works on CentOS:
https://travis-ci.org/nirs/vdsm/jobs/480027210

Looks like we need to switch the check to Fedora.

I think this started to fail today, after I rebuild the Fedora 28 image:
https://gerrit.ovirt.org/c/96847/

maybe an update in Fedora is related?

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DAOTOJOSODAD3L3H35DNSTKN6ST6PI73/

[ovirt-devel] Re: [VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again

2019-01-15 Thread Nir Soffer 
On Tue, Jan 15, 2019 at 8:41 PM Nir Soffer  wrote:

>
> On Tue, Jan 15, 2019 at 12:56 PM Nir Soffer  wrote:
>
>> On Sun, Jan 13, 2019 at 10:34 AM Edward Haas  wrote:
>>
>>>
>>> Thank you Nir.
>>> I added an assert message to this last one.
>>> It should not happen at all, it is very strange.
>>>
>>> https://gerrit.ovirt.org/#/c/96849/
>>>
>>> Thanks,
>>> Edy.
>>>
>>> On Sun, Jan 13, 2019 at 9:21 AM Nir Soffer  wrote:
>>>
 Another network test that did not fail for long time, failed again today.

 Build:

 https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_standard-check-patch/runs/1484/nodes/127/steps/407/log/?start=0

 ==
 FAIL: test_local_auto_with_static_address_without_ra_server 
 (network.netinfo_test.TestIPv6Addresses)
 --
 Traceback (most recent call last):
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
  line 333, in wrapper
 return f(*args, **kwargs)
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
  line 194, in wrapper
 return f(*args, **kwargs)
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/netinfo_test.py",
  line 399, in test_local_auto_with_static_address_without_ra_server
 self.assertEqual(2, len(ip_addrs))
 AssertionError: 2 != 4
  >> begin captured logging << 
 2019-01-13 07:08:43,598 DEBUG (MainThread) [root] /sbin/ip link add name 
 dummy_PU7TA type dummy (cwd None) (cmdutils:133)
 2019-01-13 07:08:43,619 DEBUG (MainThread) [root] SUCCESS:  = ''; 
  = 0 (cmdutils:141)
 2019-01-13 07:08:43,624 DEBUG (netlink/events) [root] START thread 
  (func=>>> method Monitor._scan of >>> 0x7f0817ca1610>>, args=(), kwargs={}) (concurrent:193)
 2019-01-13 07:08:43,627 DEBUG (MainThread) [root] /sbin/ip link set dev 
 dummy_PU7TA up (cwd None) (cmdutils:133)
 2019-01-13 07:08:43,647 DEBUG (MainThread) [root] SUCCESS:  = ''; 
  = 0 (cmdutils:141)
 2019-01-13 07:08:43,653 DEBUG (netlink/events) [root] FINISH thread 
  (concurrent:196)
 2019-01-13 07:08:43,655 DEBUG (MainThread) [root] /sbin/ip -6 addr add dev 
 dummy_PU7TA 2001::88/64 (cwd None) (cmdutils:133)
 2019-01-13 07:08:43,669 DEBUG (MainThread) [root] SUCCESS:  = ''; 
  = 0 (cmdutils:141)
 2019-01-13 07:08:43,677 DEBUG (MainThread) [root] /sbin/ip link del dev 
 dummy_PU7TA (cwd None) (cmdutils:133)
 2019-01-13 07:08:43,696 DEBUG (MainThread) [root] SUCCESS:  = ''; 
  = 0 (cmdutils:141)
 - >> end captured logging << -



 On Fri, Jan 4, 2019 at 7:30 PM Nir Soffer  wrote:

> We had this failure a lot in the past and it seems to be resolve, but
> I see it again today:
>
> ==
> FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
>  line 333, in wrapper
> return f(*args, **kwargs)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>  line 226, in test_add_delete_ipv6
> self._test_add_delete(IPV6_A_WITH_PREFIXLEN, IPV6_B_WITH_PREFIXLEN)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>  line 247, in _test_add_delete
> self._assert_has_no_address(nic, ip_b)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>  line 344, in _assert_has_no_address
> self._assert_address_not_in(address_with_prefixlen, addresses)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>  line 352, in _assert_address_not_in
> self.assertNotIn(address_with_prefixlen, addresses_list)
> AssertionError: '2002:99::1/64' unexpectedly found in ['2002:99::1/64', 
> '2001:99::1/64', 'fe80::6:23ff:fead:ed34/64']
>  >> begin captured logging << 
> 2019-01-04 16:01:53,543 DEBUG (MainThread) [root] /sbin/ip link add name 
> dummy_NKzY1 type dummy (cwd None) (cmdutils:133)
> 2019-01-04 16:01:53,559 DEBUG (MainThread) [root] SUCCESS:  = ''; 
>  = 0 (cmdutils:141)
> 2019-01-04 16:01:53,563 DEBUG (netlink/events) [root] START thread 
>  (func= method Monitor._scan of  0x7f271d654cd0>>, args=(), kwargs={}) (concurrent:193)
>

[ovirt-devel] Re: [VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again

2019-01-15 Thread Nir Soffer 
On Tue, Jan 15, 2019 at 12:56 PM Nir Soffer  wrote:

> On Sun, Jan 13, 2019 at 10:34 AM Edward Haas  wrote:
>
>>
>> Thank you Nir.
>> I added an assert message to this last one.
>> It should not happen at all, it is very strange.
>>
>> https://gerrit.ovirt.org/#/c/96849/
>>
>> Thanks,
>> Edy.
>>
>> On Sun, Jan 13, 2019 at 9:21 AM Nir Soffer  wrote:
>>
>>> Another network test that did not fail for long time, failed again today.
>>>
>>> Build:
>>>
>>> https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_standard-check-patch/runs/1484/nodes/127/steps/407/log/?start=0
>>>
>>> ==
>>> FAIL: test_local_auto_with_static_address_without_ra_server 
>>> (network.netinfo_test.TestIPv6Addresses)
>>> --
>>> Traceback (most recent call last):
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
>>>  line 333, in wrapper
>>> return f(*args, **kwargs)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
>>>  line 194, in wrapper
>>> return f(*args, **kwargs)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/netinfo_test.py",
>>>  line 399, in test_local_auto_with_static_address_without_ra_server
>>> self.assertEqual(2, len(ip_addrs))
>>> AssertionError: 2 != 4
>>>  >> begin captured logging << 
>>> 2019-01-13 07:08:43,598 DEBUG (MainThread) [root] /sbin/ip link add name 
>>> dummy_PU7TA type dummy (cwd None) (cmdutils:133)
>>> 2019-01-13 07:08:43,619 DEBUG (MainThread) [root] SUCCESS:  = '';  
>>> = 0 (cmdutils:141)
>>> 2019-01-13 07:08:43,624 DEBUG (netlink/events) [root] START thread 
>>>  (func=>> method Monitor._scan of >> 0x7f0817ca1610>>, args=(), kwargs={}) (concurrent:193)
>>> 2019-01-13 07:08:43,627 DEBUG (MainThread) [root] /sbin/ip link set dev 
>>> dummy_PU7TA up (cwd None) (cmdutils:133)
>>> 2019-01-13 07:08:43,647 DEBUG (MainThread) [root] SUCCESS:  = '';  
>>> = 0 (cmdutils:141)
>>> 2019-01-13 07:08:43,653 DEBUG (netlink/events) [root] FINISH thread 
>>>  (concurrent:196)
>>> 2019-01-13 07:08:43,655 DEBUG (MainThread) [root] /sbin/ip -6 addr add dev 
>>> dummy_PU7TA 2001::88/64 (cwd None) (cmdutils:133)
>>> 2019-01-13 07:08:43,669 DEBUG (MainThread) [root] SUCCESS:  = '';  
>>> = 0 (cmdutils:141)
>>> 2019-01-13 07:08:43,677 DEBUG (MainThread) [root] /sbin/ip link del dev 
>>> dummy_PU7TA (cwd None) (cmdutils:133)
>>> 2019-01-13 07:08:43,696 DEBUG (MainThread) [root] SUCCESS:  = '';  
>>> = 0 (cmdutils:141)
>>> - >> end captured logging << -
>>>
>>>
>>>
>>> On Fri, Jan 4, 2019 at 7:30 PM Nir Soffer  wrote:
>>>
 We had this failure a lot in the past and it seems to be resolve, but I
 see it again today:

 ==
 FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest)
 --
 Traceback (most recent call last):
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
  line 333, in wrapper
 return f(*args, **kwargs)
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
  line 226, in test_add_delete_ipv6
 self._test_add_delete(IPV6_A_WITH_PREFIXLEN, IPV6_B_WITH_PREFIXLEN)
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
  line 247, in _test_add_delete
 self._assert_has_no_address(nic, ip_b)
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
  line 344, in _assert_has_no_address
 self._assert_address_not_in(address_with_prefixlen, addresses)
   File 
 "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
  line 352, in _assert_address_not_in
 self.assertNotIn(address_with_prefixlen, addresses_list)
 AssertionError: '2002:99::1/64' unexpectedly found in ['2002:99::1/64', 
 '2001:99::1/64', 'fe80::6:23ff:fead:ed34/64']
  >> begin captured logging << 
 2019-01-04 16:01:53,543 DEBUG (MainThread) [root] /sbin/ip link add name 
 dummy_NKzY1 type dummy (cwd None) (cmdutils:133)
 2019-01-04 16:01:53,559 DEBUG (MainThread) [root] SUCCESS:  = ''; 
  = 0 (cmdutils:141)
 2019-01-04 16:01:53,563 DEBUG (netlink/events) [root] START thread 
  (func=>>> method Monitor._scan of >>> 0x7f271d654cd0>>, args=(), kwargs={}) (concurrent:193)
 2019-01-04 16:01:53,567 DEBUG (MainThread) [root] /sbin/ip link set dev 
 dummy_NKzY1 up (cwd None) (cmdutils:133)
 2019-01-04 16:01:53,586 DEBUG (MainThread)

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

2019-01-15 Thread Martin Perina 
There is way how to replace directory from previous package version with a
symlink in new version, we are already using this in other roles. Ondro,
could you please share the details about this hack?


On Tue, 15 Jan 2019, 13:24 Simone Tiraboschi 
>
> On Tue, Jan 15, 2019 at 11:15 AM Yedidyah Bar David 
> wrote:
>
>> On Tue, Jan 15, 2019 at 11:38 AM Dafna Ron  wrote:
>> >
>> > The last ovirt-engine package ran on Jan 11th and this failure happened
>> on the 14th so the appliance package is suppose to be newer then the engine
>> and should be running fine.
>> > if this is not the case, then I suggest that the maintainers of the
>> project see what is needed to be updated and trigger a new package build
>> (which is why I was alerting to the failure)
>> >
>> > Thanks,
>> > Dafna
>> >
>> >
>> > On Tue, Jan 15, 2019 at 6:51 AM Yedidyah Bar David 
>> wrote:
>> >>
>> >> On Mon, Jan 14, 2019 at 2:15 PM Dafna Ron  wrote:
>> >> >
>> >> > Hi,
>> >> >
>> >> > we are failing test 001_upgrade_engine.test_initialize_engine on
>> ovirt 4.2 for project ovirt-ansible-hosted-engine-setup.
>> >> >
>> >> > Patch reported by CQ:
>> >> >
>> >> >
>> https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d38719de663cb8ade13eb8bdff2d1e6f
>> - Rename the role - replacing '-' with '_'
>> >> >
>> >> > Ido, can you please check this issue?
>> >> >
>> >> > failed build:
>> >> >
>> >> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/
>>
>> This build has a single failure:
>>
>>
>> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/testReport/junit/(root)/001_upgrade_engine/running_tests___upgrade_from_release_suite_el7_x86_64___test_initialize_engine/
>>
>> which is in the upgrade_from_release suite, not hosted-engine.
>>
>> However, I looked at the logs, and the root cause indeed seems to be
>> related to hosted-engine, as the CQ identified (Nice!), which is:
>>
>>
>> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/artifact/upgrade-from-release-suite.el7.x86_64/lago_logs/lago.log/*view*/
>>
>> 2019-01-14 10:38:38,168::ssh.py::ssh::58::lago.ssh::DEBUG::Running
>> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine: yum -y update
>> ovirt-*setup*
>> 2019-01-14 10:38:39,732::ssh.py::ssh::81::lago.ssh::DEBUG::Command
>> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine returned with 1
>> 2019-01-14 10:38:39,733::ssh.py::ssh::89::lago.ssh::DEBUG::Command
>> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine output:
>>  Loaded plugins: fastestmirror, versionlock
>> Determining fastest mirrors
>> Excluding 9 updates due to versionlock (use "yum versionlock status"
>> to show them)
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package ovirt-ansible-engine-setup.noarch 0:1.1.5-1.el7 will be
>> updated
>> ---> Package ovirt-ansible-engine-setup.noarch
>> 0:1.1.7-0.1.master.20181219093302.el7 will be an update
>> ---> Package ovirt-ansible-hosted-engine-setup.noarch 0:1.0.2-1.el7
>> will be updated
>> ---> Package ovirt-ansible-hosted-engine-setup.noarch
>> 0:1.0.6-0.1.master.20190114102323.el7 will be an update
>> ---> Package ovirt-engine-dwh-setup.noarch 0:4.2.4.3-1.el7 will be updated
>> ---> Package ovirt-engine-dwh-setup.noarch
>> 0:4.2.5-0.0.master.20180708055101.el7 will be an update
>> ---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
>> 0:1.3.8-1.el7 will be updated
>> ---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
>> 0:1.3.9-0.0.master.gitc39177c.el7 will be an update
>> --> Processing Dependency: ovirt-engine-extension-aaa-ldap =
>> 1.3.9-0.0.master.gitc39177c.el7 for package:
>>
>> ovirt-engine-extension-aaa-ldap-setup-1.3.9-0.0.master.gitc39177c.el7.noarch
>> ---> Package ovirt-engine-setup.noarch 0:4.2.7.5-1.el7 will be updated
>> ---> Package ovirt-engine-setup.noarch
>> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
>> ---> Package ovirt-engine-setup-base.noarch 0:4.2.7.5-1.el7 will be
>> updated
>> ---> Package ovirt-engine-setup-base.noarch
>> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
>> --> Processing Dependency: ovirt-engine-lib >=
>> 4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 for package:
>>
>> ovirt-engine-setup-base-4.2.8.3-0.0.master.20190111080213.git7965c2e.el7.noarch
>> ---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch
>> 0:4.2.7.5-1.el7 will be updated
>> ---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch
>> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
>> ---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch
>> 0:4.2.7.5-1.el7 will be updated
>> ---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch
>> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
>> ---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
>> 0:4.2.7.5-1.el7 will be updated
>> ---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
>>

[ovirt-devel] [Call for Testing] oVirt 4.3.0

2019-01-15 Thread Sandro Bonazzola 
Hi,
we are planning to release a 4.3.0 RC2 tomorrow morning, January 16th 2019.
We have a scheduled final release for oVirt 4.3.0 on January 29th: this is
the time when testing is most effective to ensure the release will be as
much stable as possible. Please join us testing the RC2 release this week
and reporting issues to
https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
Please remember this is still pre-release material, we recommend not
installing it on production environments yet.

Thanks,
-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VTKSPOIA3XFU6QXF5I7IKZIQYVL2EE6M/

[ovirt-devel] Re: Request for adding ovirt-engine-sdk-go as an incubator project under oVirt

2019-01-15 Thread Ondra Machacek 



On 1/15/19 10:39 AM, Martin Perina wrote:

On Tue, Jan 15, 2019 at 10:35 AM Sandro Bonazzola 
wrote:




Il giorno mar 15 gen 2019 alle ore 10:07 Joey Ma  ha
scritto:




On Tue, Jan 15, 2019 at 4:07 PM Sandro Bonazzola 
wrote:




Il giorno mar 15 gen 2019 alle ore 03:09 Joey Ma 
ha scritto:


Hi fellows,

My name is Joey. Now I'm maintaining the project ovirt-engine-sdk-go[1]
which provides a Golang based sdk for oVirt engine REST API.

During the past year, I was keeping in touch Ondra, Juan and Martin.
It's very appreciated that they helped me a lot to improve the sdk and also
added me into the oVirt developer team[2] in github. Both Ondra and I think
that the project is in great shape and ready for production use. :-)

The original plan is to add the project into oVirt 4.3 official
release. While according to the schedules[3] for 4.3, maybe there's no
enough time to make it done due to some additional CI work.

So if I may ask, is that possible to add the project as an oVirt
incubator project first, by transferring the project from my personal
account to oVirt orgnization in github or gerrit? And then accept it as a
full oVirt project after all the graduation requirements are matched.

Thank you all in advance.

Regards,
Joey



Hi Joey, before submitting the incubation request to the oVirt Board,
I'm reviewing the process:
https://ovirt.org/develop/projects/incubating-an-subproject.html
Your project integrates with oVirt API extending them for Go language
support so on this we are ok.
Are you committing to maintain the project supporting the release
schedule of oVirt project?



Yes, for sure.



License of the project is ASL 2.0 so it's in approved licenses.
Project has 4 releases and 1 maintainer so it classify as project in
developing stage. It's a small project so I believe that the classification
here is not really correct.



Yes, agreed.



Project has 5 contributors so the onboarding requires 3 "+1" votes.
My only concern is that last release is 4.0.6 and dates October 2018. I
would expect a 4.3.0 release aligned with oVirt Engine 4.3 API.



I use 4.0.x to represent that it's not an official release. Current 4.0.6
is keeping in sync with the official Java sdk 4.2.5 release. While maybe I
should have followed the Python sdk instead, which is already in 4.2.9 :-)



I think that if you can release such version, I can give my +1 to
onboarding this project in incubation state and propose it to the Board.



OK. I just released 4.3.0 a couple of minutes ago, which adopted the
metamodel-1.3.0 and model-4.3.20 for sdk generation.



Ok, so, +1 on my side. Ondra? Martin?



Definitely +1 from me.

Joey, thanks a lot for the great work you have done so far on the project
and please continue with your contributions!


+1 Thanks a lot for your contribution!









In any case, thanks for your commitment improving oVirt, very nice job!




That's my pleasure. Great thanks for your help.







[1]: https://github.com/imjoey/ovirt-engine-sdk-go
[2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460
[3]:
https://www.ovirt.org/develop/release-management/releases/4.3/release-management.html
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OCABRD46XI6ADAIBMADJICMSJEXOWQM7/




--

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com






--

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com






___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WYAAC6ENLHPCB4F3CO2ZAGO53EXRMIIX/

[ovirt-devel] vdsm has been tagged (v4.30.6)

2019-01-15 Thread Milan Zamazal 

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/T3AOHKCLKWZ3FX2QZ6HINDVZFTGGP6IY/

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

2019-01-15 Thread Simone Tiraboschi 
On Tue, Jan 15, 2019 at 11:15 AM Yedidyah Bar David  wrote:

> On Tue, Jan 15, 2019 at 11:38 AM Dafna Ron  wrote:
> >
> > The last ovirt-engine package ran on Jan 11th and this failure happened
> on the 14th so the appliance package is suppose to be newer then the engine
> and should be running fine.
> > if this is not the case, then I suggest that the maintainers of the
> project see what is needed to be updated and trigger a new package build
> (which is why I was alerting to the failure)
> >
> > Thanks,
> > Dafna
> >
> >
> > On Tue, Jan 15, 2019 at 6:51 AM Yedidyah Bar David 
> wrote:
> >>
> >> On Mon, Jan 14, 2019 at 2:15 PM Dafna Ron  wrote:
> >> >
> >> > Hi,
> >> >
> >> > we are failing test 001_upgrade_engine.test_initialize_engine on
> ovirt 4.2 for project ovirt-ansible-hosted-engine-setup.
> >> >
> >> > Patch reported by CQ:
> >> >
> >> >
> https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d38719de663cb8ade13eb8bdff2d1e6f
> - Rename the role - replacing '-' with '_'
> >> >
> >> > Ido, can you please check this issue?
> >> >
> >> > failed build:
> >> >
> >> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/
>
> This build has a single failure:
>
>
> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/testReport/junit/(root)/001_upgrade_engine/running_tests___upgrade_from_release_suite_el7_x86_64___test_initialize_engine/
>
> which is in the upgrade_from_release suite, not hosted-engine.
>
> However, I looked at the logs, and the root cause indeed seems to be
> related to hosted-engine, as the CQ identified (Nice!), which is:
>
>
> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/artifact/upgrade-from-release-suite.el7.x86_64/lago_logs/lago.log/*view*/
>
> 2019-01-14 10:38:38,168::ssh.py::ssh::58::lago.ssh::DEBUG::Running
> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine: yum -y update
> ovirt-*setup*
> 2019-01-14 10:38:39,732::ssh.py::ssh::81::lago.ssh::DEBUG::Command
> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine returned with 1
> 2019-01-14 10:38:39,733::ssh.py::ssh::89::lago.ssh::DEBUG::Command
> 8d4833e8 on lago-upgrade-from-release-suite-4-2-engine output:
>  Loaded plugins: fastestmirror, versionlock
> Determining fastest mirrors
> Excluding 9 updates due to versionlock (use "yum versionlock status"
> to show them)
> Resolving Dependencies
> --> Running transaction check
> ---> Package ovirt-ansible-engine-setup.noarch 0:1.1.5-1.el7 will be
> updated
> ---> Package ovirt-ansible-engine-setup.noarch
> 0:1.1.7-0.1.master.20181219093302.el7 will be an update
> ---> Package ovirt-ansible-hosted-engine-setup.noarch 0:1.0.2-1.el7
> will be updated
> ---> Package ovirt-ansible-hosted-engine-setup.noarch
> 0:1.0.6-0.1.master.20190114102323.el7 will be an update
> ---> Package ovirt-engine-dwh-setup.noarch 0:4.2.4.3-1.el7 will be updated
> ---> Package ovirt-engine-dwh-setup.noarch
> 0:4.2.5-0.0.master.20180708055101.el7 will be an update
> ---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
> 0:1.3.8-1.el7 will be updated
> ---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
> 0:1.3.9-0.0.master.gitc39177c.el7 will be an update
> --> Processing Dependency: ovirt-engine-extension-aaa-ldap =
> 1.3.9-0.0.master.gitc39177c.el7 for package:
>
> ovirt-engine-extension-aaa-ldap-setup-1.3.9-0.0.master.gitc39177c.el7.noarch
> ---> Package ovirt-engine-setup.noarch 0:4.2.7.5-1.el7 will be updated
> ---> Package ovirt-engine-setup.noarch
> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
> ---> Package ovirt-engine-setup-base.noarch 0:4.2.7.5-1.el7 will be updated
> ---> Package ovirt-engine-setup-base.noarch
> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
> --> Processing Dependency: ovirt-engine-lib >=
> 4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 for package:
>
> ovirt-engine-setup-base-4.2.8.3-0.0.master.20190111080213.git7965c2e.el7.noarch
> ---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:4.2.7.5-1.el7 will be updated
> ---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
> ---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:4.2.7.5-1.el7 will be updated
> ---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
> ---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:4.2.7.5-1.el7 will be updated
> ---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
> ---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:4.2.7.5-1.el7 will be updated
> ---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
> ---> Package ovirt-imageio-proxy-setup.noarch 0:1.4.5-0.el7 will be updated
> ---> Package

[ovirt-devel] Re: Error while executing action Attach Storage Domain: AcquireHostIdFailure

2019-01-15 Thread Nir Soffer 
On Tue, Jan 15, 2019 at 1:39 PM Fedor Gavrilov  wrote:

> Thanks for the response, Nir!
>
> I will definitely try this installation.
> For the time being, as I found out the issue was indeed with selinux
> https://bugzilla.redhat.com/show_bug.cgi?id=1593853 ; setenforce 0
> workaround helped.
>

Right, this is Fedora 28 issue, mentioning that in your question could help
:-)

David, can we ship this fix in Fedora?


>
> Thanks,
> Fedor
>
> - Исходное сообщение -
> От: "Nir Soffer" 
> Кому: "Fedor Gavrilov" 
> Копия: "devel" 
> Отправленные: Вторник, 15 Январь 2019 г 0:18:15
> Тема: [ovirt-devel] Re: Error while executing action Attach Storage
> Domain: AcquireHostIdFailure
>
> On Mon, Jan 14, 2019 at 4:55 PM Fedor Gavrilov < fgavr...@redhat.com >
> wrote:
>
>
> Hi,
>
> I'm setting up iSCSI domain on freshly installed ovirt and hitting subj
> when I try adding new data domain. After it's added it's in Unattached
> state and can't be removed either.
> I found something in bugzilla about NFS storage and sanlock, could it be
> related?
>
> Maybe, there is no info here to tell :-)
>
>
>
> I allocated iSCSI fileio storage on the same machine where host is (so I'm
> connecting 127.0.0.1:3260 ), was that my mistake?
>
> It should work but not a common setup, so more likely to cause trouble,
> and also less useful for testing
> inaccessible storage. Keeping the storage server on another host (or vm)
> is more useful testing setup.
>
> What I'm using for several years is:
>
> real host running Fedora, with:
> - NFS server
> - LIO, configured with fileio backend and sparse files
> - virt-manager
>
> I have several vms managed by virt manager:
> - engine master vm, built from source, centos 7
> - engine latest release vm (e.g. 4.2), centos 7
> - 2 fedora 28 vms as hosts for fedora cluster
> - 2 centos vms as hosts for centos cluster
>
> Nir
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/P3OREEUEIMZBY3AJJELBN3YKCBS6SW6U/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MOHQUXI5RDMEQT376HNEVYEXELT3GZI3/

[ovirt-devel] Re: Error while executing action Attach Storage Domain: AcquireHostIdFailure

2019-01-15 Thread Fedor Gavrilov 
Thanks for the response, Nir!

I will definitely try this installation.
For the time being, as I found out the issue was indeed with selinux 
https://bugzilla.redhat.com/show_bug.cgi?id=1593853 ; setenforce 0 workaround 
helped.

Thanks,
Fedor

- Исходное сообщение -
От: "Nir Soffer" 
Кому: "Fedor Gavrilov" 
Копия: "devel" 
Отправленные: Вторник, 15 Январь 2019 г 0:18:15
Тема: [ovirt-devel] Re: Error while executing action Attach Storage Domain: 
AcquireHostIdFailure

On Mon, Jan 14, 2019 at 4:55 PM Fedor Gavrilov < fgavr...@redhat.com > wrote: 


Hi, 

I'm setting up iSCSI domain on freshly installed ovirt and hitting subj when I 
try adding new data domain. After it's added it's in Unattached state and can't 
be removed either. 
I found something in bugzilla about NFS storage and sanlock, could it be 
related? 

Maybe, there is no info here to tell :-) 



I allocated iSCSI fileio storage on the same machine where host is (so I'm 
connecting 127.0.0.1:3260 ), was that my mistake? 

It should work but not a common setup, so more likely to cause trouble, and 
also less useful for testing 
inaccessible storage. Keeping the storage server on another host (or vm) is 
more useful testing setup. 

What I'm using for several years is: 

real host running Fedora, with: 
- NFS server 
- LIO, configured with fileio backend and sparse files 
- virt-manager 

I have several vms managed by virt manager: 
- engine master vm, built from source, centos 7 
- engine latest release vm (e.g. 4.2), centos 7 
- 2 fedora 28 vms as hosts for fedora cluster 
- 2 centos vms as hosts for centos cluster 

Nir 

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/P3OREEUEIMZBY3AJJELBN3YKCBS6SW6U/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/RXSU5ZIKR3CZ46ERKXOZ6GXLTR2RDK32/

[ovirt-devel] Re: SSO with lightdm

2019-01-15 Thread Tomáš Golembiovský 
Hi,

On Mon, 17 Dec 2018 14:40:22 +0100
Sandro Bonazzola  wrote:

> Il giorno lun 17 dic 2018 alle ore 07:09  ha scritto:
> 
> > I knows there are the GDM plugin and KDM plugin of ovirt-guest-agent that
> > makes SSO in linux is possible.
> >
> > I want to make SSO with lightdm is possble. To add lightdm plugin to
> > ovirt-guest-agent is enough? or something more is needed?
> >
> > I don't know how to develop SSO with lightdm.
> >  
> 
> Adding Tomas. I would suggest to open a bug tracking this RFE and explain
> the use case to motivate the request.
> 

Actually we are in the process of sun-setting the oVirt Guest Agent and
we don't add new features. We have moved the most important features
into QEMU Guest Agent. However, SSO is not one of them and we don't have
a plan how or even if we're going to do that. There is minimal demand
for this.

Of course, if you're brave enough to implement the feature in oVirt
Guest Agent I can include that.

Tomas

> 
> 
> >
> >
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WZ5BH5MRWZYNQCJRUJ6LDXUSFFBUKOFB/
> >  
> 
> 
> -- 
> 
> SANDRO BONAZZOLA
> 
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> 
> Red Hat EMEA 
> 
> sbona...@redhat.com
> 


-- 
Tomáš Golembiovský 
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QB2FKHRWHBU3WJFK6D6Z4IR2GR7KW7PK/

[ovirt-devel] Re: [VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again

2019-01-15 Thread Nir Soffer 
On Sun, Jan 13, 2019 at 10:34 AM Edward Haas  wrote:

>
> Thank you Nir.
> I added an assert message to this last one.
> It should not happen at all, it is very strange.
>
> https://gerrit.ovirt.org/#/c/96849/
>
> Thanks,
> Edy.
>
> On Sun, Jan 13, 2019 at 9:21 AM Nir Soffer  wrote:
>
>> Another network test that did not fail for long time, failed again today.
>>
>> Build:
>>
>> https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_standard-check-patch/runs/1484/nodes/127/steps/407/log/?start=0
>>
>> ==
>> FAIL: test_local_auto_with_static_address_without_ra_server 
>> (network.netinfo_test.TestIPv6Addresses)
>> --
>> Traceback (most recent call last):
>>   File 
>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
>>  line 333, in wrapper
>> return f(*args, **kwargs)
>>   File 
>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
>>  line 194, in wrapper
>> return f(*args, **kwargs)
>>   File 
>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/netinfo_test.py",
>>  line 399, in test_local_auto_with_static_address_without_ra_server
>> self.assertEqual(2, len(ip_addrs))
>> AssertionError: 2 != 4
>>  >> begin captured logging << 
>> 2019-01-13 07:08:43,598 DEBUG (MainThread) [root] /sbin/ip link add name 
>> dummy_PU7TA type dummy (cwd None) (cmdutils:133)
>> 2019-01-13 07:08:43,619 DEBUG (MainThread) [root] SUCCESS:  = '';  
>> = 0 (cmdutils:141)
>> 2019-01-13 07:08:43,624 DEBUG (netlink/events) [root] START thread 
>>  (func=> Monitor._scan of > 0x7f0817ca1610>>, args=(), kwargs={}) (concurrent:193)
>> 2019-01-13 07:08:43,627 DEBUG (MainThread) [root] /sbin/ip link set dev 
>> dummy_PU7TA up (cwd None) (cmdutils:133)
>> 2019-01-13 07:08:43,647 DEBUG (MainThread) [root] SUCCESS:  = '';  
>> = 0 (cmdutils:141)
>> 2019-01-13 07:08:43,653 DEBUG (netlink/events) [root] FINISH thread 
>>  (concurrent:196)
>> 2019-01-13 07:08:43,655 DEBUG (MainThread) [root] /sbin/ip -6 addr add dev 
>> dummy_PU7TA 2001::88/64 (cwd None) (cmdutils:133)
>> 2019-01-13 07:08:43,669 DEBUG (MainThread) [root] SUCCESS:  = '';  
>> = 0 (cmdutils:141)
>> 2019-01-13 07:08:43,677 DEBUG (MainThread) [root] /sbin/ip link del dev 
>> dummy_PU7TA (cwd None) (cmdutils:133)
>> 2019-01-13 07:08:43,696 DEBUG (MainThread) [root] SUCCESS:  = '';  
>> = 0 (cmdutils:141)
>> - >> end captured logging << -
>>
>>
>>
>> On Fri, Jan 4, 2019 at 7:30 PM Nir Soffer  wrote:
>>
>>> We had this failure a lot in the past and it seems to be resolve, but I
>>> see it again today:
>>>
>>> ==
>>> FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest)
>>> --
>>> Traceback (most recent call last):
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
>>>  line 333, in wrapper
>>> return f(*args, **kwargs)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>>>  line 226, in test_add_delete_ipv6
>>> self._test_add_delete(IPV6_A_WITH_PREFIXLEN, IPV6_B_WITH_PREFIXLEN)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>>>  line 247, in _test_add_delete
>>> self._assert_has_no_address(nic, ip_b)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>>>  line 344, in _assert_has_no_address
>>> self._assert_address_not_in(address_with_prefixlen, addresses)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py",
>>>  line 352, in _assert_address_not_in
>>> self.assertNotIn(address_with_prefixlen, addresses_list)
>>> AssertionError: '2002:99::1/64' unexpectedly found in ['2002:99::1/64', 
>>> '2001:99::1/64', 'fe80::6:23ff:fead:ed34/64']
>>>  >> begin captured logging << 
>>> 2019-01-04 16:01:53,543 DEBUG (MainThread) [root] /sbin/ip link add name 
>>> dummy_NKzY1 type dummy (cwd None) (cmdutils:133)
>>> 2019-01-04 16:01:53,559 DEBUG (MainThread) [root] SUCCESS:  = '';  
>>> = 0 (cmdutils:141)
>>> 2019-01-04 16:01:53,563 DEBUG (netlink/events) [root] START thread 
>>>  (func=>> method Monitor._scan of >> 0x7f271d654cd0>>, args=(), kwargs={}) (concurrent:193)
>>> 2019-01-04 16:01:53,567 DEBUG (MainThread) [root] /sbin/ip link set dev 
>>> dummy_NKzY1 up (cwd None) (cmdutils:133)
>>> 2019-01-04 16:01:53,586 DEBUG (MainThread) [root] SUCCESS:  = '';  
>>> = 0 (cmdutils:141)
>>> 2019-01-04 16:01:53,593 DEBUG (netlink/events) [root] FINISH thread 
>>>  (concurrent:196)
>>> 2019-01-04 16:01:53,597

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

2019-01-15 Thread Yedidyah Bar David 
On Tue, Jan 15, 2019 at 11:38 AM Dafna Ron  wrote:
>
> The last ovirt-engine package ran on Jan 11th and this failure happened on 
> the 14th so the appliance package is suppose to be newer then the engine and 
> should be running fine.
> if this is not the case, then I suggest that the maintainers of the project 
> see what is needed to be updated and trigger a new package build (which is 
> why I was alerting to the failure)
>
> Thanks,
> Dafna
>
>
> On Tue, Jan 15, 2019 at 6:51 AM Yedidyah Bar David  wrote:
>>
>> On Mon, Jan 14, 2019 at 2:15 PM Dafna Ron  wrote:
>> >
>> > Hi,
>> >
>> > we are failing test 001_upgrade_engine.test_initialize_engine on ovirt 4.2 
>> > for project ovirt-ansible-hosted-engine-setup.
>> >
>> > Patch reported by CQ:
>> >
>> > https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d38719de663cb8ade13eb8bdff2d1e6f
>> >  - Rename the role - replacing '-' with '_'
>> >
>> > Ido, can you please check this issue?
>> >
>> > failed build:
>> >
>> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/

This build has a single failure:

https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/testReport/junit/(root)/001_upgrade_engine/running_tests___upgrade_from_release_suite_el7_x86_64___test_initialize_engine/

which is in the upgrade_from_release suite, not hosted-engine.

However, I looked at the logs, and the root cause indeed seems to be
related to hosted-engine, as the CQ identified (Nice!), which is:

https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/artifact/upgrade-from-release-suite.el7.x86_64/lago_logs/lago.log/*view*/

2019-01-14 10:38:38,168::ssh.py::ssh::58::lago.ssh::DEBUG::Running
8d4833e8 on lago-upgrade-from-release-suite-4-2-engine: yum -y update
ovirt-*setup*
2019-01-14 10:38:39,732::ssh.py::ssh::81::lago.ssh::DEBUG::Command
8d4833e8 on lago-upgrade-from-release-suite-4-2-engine returned with 1
2019-01-14 10:38:39,733::ssh.py::ssh::89::lago.ssh::DEBUG::Command
8d4833e8 on lago-upgrade-from-release-suite-4-2-engine output:
 Loaded plugins: fastestmirror, versionlock
Determining fastest mirrors
Excluding 9 updates due to versionlock (use "yum versionlock status"
to show them)
Resolving Dependencies
--> Running transaction check
---> Package ovirt-ansible-engine-setup.noarch 0:1.1.5-1.el7 will be updated
---> Package ovirt-ansible-engine-setup.noarch
0:1.1.7-0.1.master.20181219093302.el7 will be an update
---> Package ovirt-ansible-hosted-engine-setup.noarch 0:1.0.2-1.el7
will be updated
---> Package ovirt-ansible-hosted-engine-setup.noarch
0:1.0.6-0.1.master.20190114102323.el7 will be an update
---> Package ovirt-engine-dwh-setup.noarch 0:4.2.4.3-1.el7 will be updated
---> Package ovirt-engine-dwh-setup.noarch
0:4.2.5-0.0.master.20180708055101.el7 will be an update
---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
0:1.3.8-1.el7 will be updated
---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
0:1.3.9-0.0.master.gitc39177c.el7 will be an update
--> Processing Dependency: ovirt-engine-extension-aaa-ldap =
1.3.9-0.0.master.gitc39177c.el7 for package:
ovirt-engine-extension-aaa-ldap-setup-1.3.9-0.0.master.gitc39177c.el7.noarch
---> Package ovirt-engine-setup.noarch 0:4.2.7.5-1.el7 will be updated
---> Package ovirt-engine-setup.noarch
0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
---> Package ovirt-engine-setup-base.noarch 0:4.2.7.5-1.el7 will be updated
---> Package ovirt-engine-setup-base.noarch
0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
--> Processing Dependency: ovirt-engine-lib >=
4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 for package:
ovirt-engine-setup-base-4.2.8.3-0.0.master.20190111080213.git7965c2e.el7.noarch
---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.2.7.5-1.el7 will be updated
---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.2.7.5-1.el7 will be updated
---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.2.7.5-1.el7 will be updated
---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.2.7.5-1.el7 will be updated
---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.2.8.3-0.0.master.20190111080213.git7965c2e.el7 will be an update
---> Package ovirt-imageio-proxy-setup.noarch 0:1.4.5-0.el7 will be updated
---> Package ovirt-imageio-proxy-setup.noarch 0:1.4.6-1.el7 will be an update
---> Package ovirt-setup-lib.noarch 0:1.1.5-1.el7 will be updated
---> Package ovirt-setup-lib.noarch
0:1.1.6-0.0.master.20180921125403.git90612e6.el7 will be an update
--> Running

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

2019-01-15 Thread Dafna Ron 
The last ovirt-engine package ran on Jan 11th and this failure happened on
the 14th so the appliance package is suppose to be newer then the engine
and should be running fine.
if this is not the case, then I suggest that the maintainers of the project
see what is needed to be updated and trigger a new package build (which is
why I was alerting to the failure)

Thanks,
Dafna


On Tue, Jan 15, 2019 at 6:51 AM Yedidyah Bar David  wrote:

> On Mon, Jan 14, 2019 at 2:15 PM Dafna Ron  wrote:
> >
> > Hi,
> >
> > we are failing test 001_upgrade_engine.test_initialize_engine on ovirt
> 4.2 for project ovirt-ansible-hosted-engine-setup.
> >
> > Patch reported by CQ:
> >
> >
> https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d38719de663cb8ade13eb8bdff2d1e6f
> - Rename the role - replacing '-' with '_'
> >
> > Ido, can you please check this issue?
> >
> > failed build:
> >
> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/
> >
> > error:
> >
> > [ INFO  ] Checking for an update for Setup...
> >   An update for the Setup packages ovirt-engine-setup
> ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup was found.
> Please update that package by running:
> >   "yum update ovirt-engine-setup
> ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup"
> >   and then execute Setup again.
> > [ ERROR ] Failed to execute stage 'Environment customization': Please
> update the Setup packages
> > [ INFO  ] Stage: Clean up
> >   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-setup-20190114053840-4ysu6y.log
> > [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20190114053855-setup.conf'
> > [ INFO  ] Stage: Pre-termination
> > [ INFO  ] Stage: Termination
> > [ ERROR ] Execution of setup failed
> > ('FATAL Internal error (main): Please update the Setup packages',)
> >
> > lago.ssh: DEBUG: Command 8e6b18d0 on
> lago-upgrade-from-release-suite-4-2-engine  errors:
> >  Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in
> main
> > installer.execute()
> >   File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in
> execute
> > self.context.runSequence()
> >   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 771, in
> runSequence
> > util.raiseExceptionInformation(infos[0])
> >   File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in
> raiseExceptionInformation
> > exec('raise info[1], None, info[2]')
> >   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in
> _executeMethod
> > method['method']()
> >   File
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py",
> line 410, in _customization
> > raise RuntimeError(_('Please update the Setup packages'))
> > RuntimeError: Please update the Setup packages
>
> I think this is self-explanatory, no?
>
> Most likely this happens because we have a new engine and the appliance
> is not updated. If it's just a timing issue, should be solved without
> intervention on next appliance build. You (CI) might consider, though,
> forcing an appliance build and using it in each CQ batch that updates
> the engine.
>
> If it's something else, need to check appliance build status.
>
> Best regards,
> --
> Didi
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/KTBPK7GH6UV244RYRBRTFMP5GQVHULXB/

[ovirt-devel] Re: Request for adding ovirt-engine-sdk-go as an incubator project under oVirt

2019-01-15 Thread Sandro Bonazzola 
Il giorno mar 15 gen 2019 alle ore 10:07 Joey Ma  ha
scritto:

>
>
> On Tue, Jan 15, 2019 at 4:07 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno mar 15 gen 2019 alle ore 03:09 Joey Ma 
>> ha scritto:
>>
>>> Hi fellows,
>>>
>>> My name is Joey. Now I'm maintaining the project ovirt-engine-sdk-go[1]
>>> which provides a Golang based sdk for oVirt engine REST API.
>>>
>>> During the past year, I was keeping in touch Ondra, Juan and Martin.
>>> It's very appreciated that they helped me a lot to improve the sdk and also
>>> added me into the oVirt developer team[2] in github. Both Ondra and I think
>>> that the project is in great shape and ready for production use. :-)
>>>
>>> The original plan is to add the project into oVirt 4.3 official release.
>>> While according to the schedules[3] for 4.3, maybe there's no enough time
>>> to make it done due to some additional CI work.
>>>
>>> So if I may ask, is that possible to add the project as an oVirt
>>> incubator project first, by transferring the project from my personal
>>> account to oVirt orgnization in github or gerrit? And then accept it as a
>>> full oVirt project after all the graduation requirements are matched.
>>>
>>> Thank you all in advance.
>>>
>>> Regards,
>>> Joey
>>>
>>>
>> Hi Joey, before submitting the incubation request to the oVirt Board, I'm
>> reviewing the process:
>> https://ovirt.org/develop/projects/incubating-an-subproject.html
>> Your project integrates with oVirt API extending them for Go language
>> support so on this we are ok.
>> Are you committing to maintain the project supporting the release
>> schedule of oVirt project?
>>
>
> Yes, for sure.
>
>
>> License of the project is ASL 2.0 so it's in approved licenses.
>> Project has 4 releases and 1 maintainer so it classify as project in
>> developing stage. It's a small project so I believe that the classification
>> here is not really correct.
>>
>
> Yes, agreed.
>
>
>> Project has 5 contributors so the onboarding requires 3 "+1" votes.
>> My only concern is that last release is 4.0.6 and dates October 2018. I
>> would expect a 4.3.0 release aligned with oVirt Engine 4.3 API.
>>
>
> I use 4.0.x to represent that it's not an official release. Current 4.0.6
> is keeping in sync with the official Java sdk 4.2.5 release. While maybe I
> should have followed the Python sdk instead, which is already in 4.2.9 :-)
>
>
>> I think that if you can release such version, I can give my +1 to
>> onboarding this project in incubation state and propose it to the Board.
>>
>
> OK. I just released 4.3.0 a couple of minutes ago, which adopted the
> metamodel-1.3.0 and model-4.3.20 for sdk generation.
>

Ok, so, +1 on my side. Ondra? Martin?



>
> In any case, thanks for your commitment improving oVirt, very nice job!
>>
>
> That's my pleasure. Great thanks for your help.
>
>
>>
>>
>>
>>> [1]: https://github.com/imjoey/ovirt-engine-sdk-go
>>> [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460
>>> [3]:
>>> https://www.ovirt.org/develop/release-management/releases/4.3/release-management.html
>>> ___
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OCABRD46XI6ADAIBMADJICMSJEXOWQM7/
>>>
>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>>
>

-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HUW5CCETMDYYCHTJEXQPOCBF4QP2HZNI/

[ovirt-devel] Re: Request for adding ovirt-engine-sdk-go as an incubator project under oVirt

2019-01-15 Thread Joey Ma 
On Tue, Jan 15, 2019 at 4:07 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno mar 15 gen 2019 alle ore 03:09 Joey Ma  ha
> scritto:
>
>> Hi fellows,
>>
>> My name is Joey. Now I'm maintaining the project ovirt-engine-sdk-go[1]
>> which provides a Golang based sdk for oVirt engine REST API.
>>
>> During the past year, I was keeping in touch Ondra, Juan and Martin. It's
>> very appreciated that they helped me a lot to improve the sdk and also
>> added me into the oVirt developer team[2] in github. Both Ondra and I think
>> that the project is in great shape and ready for production use. :-)
>>
>> The original plan is to add the project into oVirt 4.3 official release.
>> While according to the schedules[3] for 4.3, maybe there's no enough time
>> to make it done due to some additional CI work.
>>
>> So if I may ask, is that possible to add the project as an oVirt
>> incubator project first, by transferring the project from my personal
>> account to oVirt orgnization in github or gerrit? And then accept it as a
>> full oVirt project after all the graduation requirements are matched.
>>
>> Thank you all in advance.
>>
>> Regards,
>> Joey
>>
>>
> Hi Joey, before submitting the incubation request to the oVirt Board, I'm
> reviewing the process:
> https://ovirt.org/develop/projects/incubating-an-subproject.html
> Your project integrates with oVirt API extending them for Go language
> support so on this we are ok.
> Are you committing to maintain the project supporting the release schedule
> of oVirt project?
>

Yes, for sure.


> License of the project is ASL 2.0 so it's in approved licenses.
> Project has 4 releases and 1 maintainer so it classify as project in
> developing stage. It's a small project so I believe that the classification
> here is not really correct.
>

Yes, agreed.


> Project has 5 contributors so the onboarding requires 3 "+1" votes.
> My only concern is that last release is 4.0.6 and dates October 2018. I
> would expect a 4.3.0 release aligned with oVirt Engine 4.3 API.
>

I use 4.0.x to represent that it's not an official release. Current 4.0.6
is keeping in sync with the official Java sdk 4.2.5 release. While maybe I
should have followed the Python sdk instead, which is already in 4.2.9 :-)


> I think that if you can release such version, I can give my +1 to
> onboarding this project in incubation state and propose it to the Board.
>

OK. I just released 4.3.0 a couple of minutes ago, which adopted the
metamodel-1.3.0 and model-4.3.20 for sdk generation.

In any case, thanks for your commitment improving oVirt, very nice job!
>

That's my pleasure. Great thanks for your help.


>
>
>
>> [1]: https://github.com/imjoey/ovirt-engine-sdk-go
>> [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460
>> [3]:
>> https://www.ovirt.org/develop/release-management/releases/4.3/release-management.html
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OCABRD46XI6ADAIBMADJICMSJEXOWQM7/
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/XHG6FQGG5JFQ6CJEUV3BYAYZYVV74U6Y/

[ovirt-devel] Re: Request for adding ovirt-engine-sdk-go as an incubator project under oVirt

2019-01-15 Thread Sandro Bonazzola 
Il giorno mar 15 gen 2019 alle ore 03:09 Joey Ma  ha
scritto:

> Hi fellows,
>
> My name is Joey. Now I'm maintaining the project ovirt-engine-sdk-go[1]
> which provides a Golang based sdk for oVirt engine REST API.
>
> During the past year, I was keeping in touch Ondra, Juan and Martin. It's
> very appreciated that they helped me a lot to improve the sdk and also
> added me into the oVirt developer team[2] in github. Both Ondra and I think
> that the project is in great shape and ready for production use. :-)
>
> The original plan is to add the project into oVirt 4.3 official release.
> While according to the schedules[3] for 4.3, maybe there's no enough time
> to make it done due to some additional CI work.
>
> So if I may ask, is that possible to add the project as an oVirt incubator
> project first, by transferring the project from my personal account to
> oVirt orgnization in github or gerrit? And then accept it as a full oVirt
> project after all the graduation requirements are matched.
>
> Thank you all in advance.
>
> Regards,
> Joey
>
>
Hi Joey, before submitting the incubation request to the oVirt Board, I'm
reviewing the process:
https://ovirt.org/develop/projects/incubating-an-subproject.html
Your project integrates with oVirt API extending them for Go language
support so on this we are ok.
Are you committing to maintain the project supporting the release schedule
of oVirt project?
License of the project is ASL 2.0 so it's in approved licenses.
Project has 4 releases and 1 maintainer so it classify as project in
developing stage. It's a small project so I believe that the classification
here is not really correct.
Project has 5 contributors so the onboarding requires 3 "+1" votes.
My only concern is that last release is 4.0.6 and dates October 2018. I
would expect a 4.3.0 release aligned with oVirt Engine 4.3 API.
I think that if you can release such version, I can give my +1 to
onboarding this project in incubation state and propose it to the Board.
In any case, thanks for your commitment improving oVirt, very nice job!



> [1]: https://github.com/imjoey/ovirt-engine-sdk-go
> [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460
> [3]:
> https://www.ovirt.org/develop/release-management/releases/4.3/release-management.html
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OCABRD46XI6ADAIBMADJICMSJEXOWQM7/
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MLF5DBWIFXVP6RZJIO2LH5B2DIT5H5G5/