[ovirt-devel] Re: Publishing oVirt Go modules under ovirt.org namespace

2021-10-27 Thread Nir Soffer
On Wed, Oct 27, 2021 at 10:03 PM Yedidyah Bar David  wrote:
>
> On Wed, Oct 27, 2021 at 6:19 PM Nir Soffer  wrote:
>>
>> Currently we have 3 go modules:
>>
>> - github.com/ovirt/go-ovirt
>>   https://github.com/oVirt/go-ovirt/
>>   seems that this repo generated by 
>> https://github.com/oVirt/ovirt-engine-sdk-go
>>
>> - github.com/ovirt/go-ovirt-client
>>https://github.com/oVirt/go-ovirt-client
>>
>> - github.com/ovirt/go-ovirt-client-log
>>https://github.com/oVirt/go-ovirt-client-log
>>
>> These modules share the issue of depending on the hosting service
>> and the repo the code is located.
>>
>> I started to work on the imageio go module here:
>> https://gerrit.ovirt.org/c/ovirt-imageio/+/117277
>>
>> And I'm trying to avoid the issues above by naming the module:
>>
>> ovirt.org/imageio
>>
>> The module name does not depend on the hosting service, or on the
>> actual repo or the location in the repo.
>>
>> To make this work, the web server at ovirt.org should serve this resource:
>>
>> https://ovirt.org/imageio
>>
>> returning an HTML document that contains a magic  tag in
>> the page header
>>
>> https://github.com/ovirt/ovirt-imageio/imageio-go"/>
>>
>> Is this possible with our current infrastructure?
>
>
> If that's all you want, I guess you should simply open an infra ticket, no?

I want to discuss the issue and possible solutions

>> Should we rename all the go modules to fit this scheme?
>
>
> Perhaps do something slightly different: Use a subdir, or a subdomain,
> such as go.ovirt.org/imageio or ovirt.org/go/imageio, and ask for this
> place to be managed using a git repo somewhere (in gerrit or elsewhere), so
> that when you merge there stuff, something updates the namespace
> automatically. This way you do not need to ping infra per each project.

This is nicer since using "ovirt.org/name" for a go module prevents
using this name for something else.

But hopefully we can do this using the current ovirt site
infrastructure, for example
adding a wiki page with a special metadata key, or syntax that will generate
the  tag like:

   ---
   title: oVirt ... Go module
   meta: name=... content=...
   ---
   Page text...

This way the same page can also contain useful content about the resource.

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


[ovirt-devel] Re: Publishing oVirt Go modules under ovirt.org namespace

2021-10-27 Thread Yedidyah Bar David
On Wed, Oct 27, 2021 at 6:19 PM Nir Soffer  wrote:

> Currently we have 3 go modules:
>
> - github.com/ovirt/go-ovirt
>   https://github.com/oVirt/go-ovirt/
>   seems that this repo generated by
> https://github.com/oVirt/ovirt-engine-sdk-go
>
> - github.com/ovirt/go-ovirt-client
>https://github.com/oVirt/go-ovirt-client
>
> - github.com/ovirt/go-ovirt-client-log
>https://github.com/oVirt/go-ovirt-client-log
>
> These modules share the issue of depending on the hosting service
> and the repo the code is located.
>
> I started to work on the imageio go module here:
> https://gerrit.ovirt.org/c/ovirt-imageio/+/117277
>
> And I'm trying to avoid the issues above by naming the module:
>
> ovirt.org/imageio
>
> The module name does not depend on the hosting service, or on the
> actual repo or the location in the repo.
>
> To make this work, the web server at ovirt.org should serve this resource:
>
> https://ovirt.org/imageio
>
> returning an HTML document that contains a magic  tag in
> the page header
>
> https://github.com/ovirt/ovirt-imageio/imageio-go"/>
>
> Is this possible with our current infrastructure?
>

If that's all you want, I guess you should simply open an infra ticket, no?


> Should we rename all the go modules to fit this scheme?
>

Perhaps do something slightly different: Use a subdir, or a subdomain,
such as go.ovirt.org/imageio or ovirt.org/go/imageio, and ask for this
place to be managed using a git repo somewhere (in gerrit or elsewhere), so
that when you merge there stuff, something updates the namespace
automatically. This way you do not need to ping infra per each project.

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/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YW2LM73CUAM3BZ6OQ7W5OGTWVQ6TIMPK/


[ovirt-devel] ovirt-engine has been tagged (ovirt-engine-4.4.9.4)

2021-10-27 Thread Martin Perina
ovirt-engine has been tagged (ovirt-engine-4.4.9.4)

-- 
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/5H4OTIGRMAN3HPV6OTGYSH5WC6YEPMDK/


[ovirt-devel] Publishing oVirt Go modules under ovirt.org namespace

2021-10-27 Thread Nir Soffer
Currently we have 3 go modules:

- github.com/ovirt/go-ovirt
  https://github.com/oVirt/go-ovirt/
  seems that this repo generated by https://github.com/oVirt/ovirt-engine-sdk-go

- github.com/ovirt/go-ovirt-client
   https://github.com/oVirt/go-ovirt-client

- github.com/ovirt/go-ovirt-client-log
   https://github.com/oVirt/go-ovirt-client-log

These modules share the issue of depending on the hosting service
and the repo the code is located.

I started to work on the imageio go module here:
https://gerrit.ovirt.org/c/ovirt-imageio/+/117277

And I'm trying to avoid the issues above by naming the module:

ovirt.org/imageio

The module name does not depend on the hosting service, or on the
actual repo or the location in the repo.

To make this work, the web server at ovirt.org should serve this resource:

https://ovirt.org/imageio

returning an HTML document that contains a magic  tag in
the page header

https://github.com/ovirt/ovirt-imageio/imageio-go"/>

Is this possible with our current infrastructure?

Should we rename all the go modules to fit this scheme?

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


[ovirt-devel] Re: [External] : Re: Java Xmx limit building ovirt-engine package

2021-10-27 Thread Marcos Sungaila
Thank you Artur, it make sense.
oVirt itself recommend a small set of supported browsers.
I will try this approach on building the ovirt-engine rpm package.

Regards,
Marcos

From: Artur Socha 
Sent: quarta-feira, 27 de outubro de 2021 05:20
To: Sandro Bonazzola 
Cc: Marcos Sungaila ; Martin Perina 
; oVirt development list 
Subject: [External] : Re: [ovirt-devel] Java Xmx limit building ovirt-engine 
package

Hi Marcos,
I believe you hit the issue because of gwt 'compiler' which by default tries to 
prepare gwt distro for all defined browsers(user agents). It will literally eat 
all the memory that is available :/.
If you need it for development purposes then you can use "ovirt_build_minimal 
1" make the build much faster and not that memory hungry:
$ rm ovirt-engine-*_master.tar.gz ; make clean && make dist && time rpmbuild 
-D"ovirt_build_minimal 1" -tb ovirt-engine-*_master.tar.gz

If you want more user agents supported you can define them as [1]:
-D"ovirt_build_user_agent "

[1] 
https://github.com/oVirt/ovirt-engine/blob/master/README.adoc

I hope that helps.
Artur



On Tue, Oct 26, 2021 at 7:14 PM Sandro Bonazzola 
mailto:sbona...@redhat.com>> wrote:
+Martin Perina , +Artur 
Socha ?

Il giorno mar 26 ott 2021 alle ore 17:01 Marcos Sungaila 
mailto:marcos.sunga...@oracle.com>> ha scritto:
Hello,

I’m facing a weird behave when rebuilding the ovirt-engine rpm package.
When I run a rpmbuild -ba ovirt-engine.spec, it fails with the following error:

[ERROR] Out of memory; to increase the amount of memory
Also, it indicates the option -Xmx8192M in the pom.xml file.
The weird part is that building the application in the command line works fine 
but not in the rpmbuild, neither using a mock build system.
I checked this page 
https://github.com/oVirt/ovirt-engine
 from GitHub and tested those variables with no success.

Can anyone point me where I can find how to use those variables when building 
the package or have experience building this package/application to explain it?

Thank you in advance for any help.

Regards,
Marcos

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


--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat 
EMEA

sbona...@redhat.com
[https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]
Red Hat respects your work life balance. Therefore there is no need to answer 
this email out of your office hours.



--
Artur Socha
Senior Software Engineer, RHV
Red Hat
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HVUXEUEVEVCWDTKRKE47E6GVAUPMEPMI/


[ovirt-devel] Re: Java Xmx limit building ovirt-engine package

2021-10-27 Thread Artur Socha
Hi Marcos,
I believe you hit the issue because of gwt 'compiler' which by default
tries to prepare gwt distro for all defined browsers(user agents). It will
literally eat all the memory that is available :/.
If you need it for development purposes then you can use
"ovirt_build_minimal 1" make the build much faster and not that memory
hungry:
$ rm ovirt-engine-*_master.tar.gz ; make clean && make dist && time
rpmbuild -D"ovirt_build_minimal 1" -tb ovirt-engine-*_master.tar.gz

If you want more user agents supported you can define them as [1]:
-D"ovirt_build_user_agent "

[1] https://github.com/oVirt/ovirt-engine/blob/master/README.adoc

I hope that helps.
Artur



On Tue, Oct 26, 2021 at 7:14 PM Sandro Bonazzola 
wrote:

> +Martin Perina  , +Artur Socha  ?
>
> Il giorno mar 26 ott 2021 alle ore 17:01 Marcos Sungaila <
> marcos.sunga...@oracle.com> ha scritto:
>
>> Hello,
>>
>>
>>
>> I’m facing a weird behave when rebuilding the ovirt-engine rpm package.
>>
>> When I run a rpmbuild -ba ovirt-engine.spec, it fails with the following
>> error:
>>
>>
>>
>> [ERROR] Out of memory; to increase the amount of memory
>>
>> Also, it indicates the option -Xmx8192M in the pom.xml file.
>>
>> The weird part is that building the application in the command line works
>> fine but not in the rpmbuild, neither using a mock build system.
>>
>> I checked this page https://github.com/oVirt/ovirt-engine from GitHub
>> and tested those variables with no success.
>>
>>
>>
>> Can anyone point me where I can find how to use those variables when
>> building the package or have experience building this package/application
>> to explain it?
>>
>>
>>
>> Thank you in advance for any help.
>>
>>
>>
>> Regards,
>>
>> Marcos
>>
>>
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DNRP3JCD6VEETCRGFIILOOUDO2LBQFTQ/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>

-- 
Artur Socha
Senior Software Engineer, RHV
Red Hat
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EUBSKMWXASCTEJJRT2THXBWLYMBGPXNW/


[ovirt-devel] Help needed enabling copr builds for ovirt-ansible-collection

2021-10-27 Thread Sandro Bonazzola
Hi,
I was looking at ovirt-ansible-collection build scripts and I need help
preparing a Makefile as
https://github.com/oVirt/ovirt-host/blob/master/.copr/Makefile for this
package.
It will be executed on a Fedora 34 host and then the resulting SRPM is
going to be rebuilt with mock for el8 / el9 as needed.
This package seems to do weird stuff with pip to get ansible / ansible-core
in the build root and we need to streamline the build to avoid this
workaround.
@Martin Necas  , @Martin Perina  can
you help?

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/X6CTIUHHJX2AJ7IT2KE7WIVLBH6SINYZ/