[libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python

[Jim Fehlig]

On 9/13/19 9:28 AM, Andrea Bolognani wrote:
> On Fri, 2019-09-13 at 13:58 +0000, Jim Fehlig wrote:
>> On 9/13/19 2:56 AM, Andrea Bolognani wrote:
>>> Jim, does SLES 12 have
>>> Python 3?
>>
>> Yes, python 3.4.6. And python 2.7.13.
> 
> That's *amazing* news! \o/
> 
>>> And, as a side note: do you think you could find the time to add
>>> OpenSUSE support to the libvirt-jenkins-ci project? That'd be very
>>> useful, because it makes grepping for this kind of information
>>> trivial, and also would open the door to running actual CI jobs on
>>> the OS :)
>>
>> I have internal jobs but agreed it would be nice to have openSUSE included in
>> upstream CI on vanilla upstream :-). Any pointers on how to do that?
> 
> Good to hear you're willing to help with this effort! I've been
> wanting to introduce OpenSUSE support myself for a very long time,
> but unfortunately I've never quite managed to scrap together the
> necessary time.

Thanks for the detailed info! I have a busy month ahead, including traveling the 
next two weeks, so I likely wont get to it until Oct. But I will get to it :-).

Regards,
Jim

> 
> The repository is
> 
>    https://libvirt.org/git/?p=libvirt-jenkins-ci.git
> 
> and most of the stuff you'd have to touch is inside the guests/
> subdirectory; more specifically, you're definitely going to have to:
> 
>    * add OpenSUSE 12 and 15 to inventory and host_vars/;
> 
>    * write an AutoYaST configuration file that can be used to install
>      a minimal OpenSUSE guest without user interaction and add it to
>      the configs/ directory along with the existing preseed and
>      kickstart configurations;
> 
>    * add mappings from abstract package names, such as 'dtrace', to
>      the corresponding OpenSUSE concrete package names, such as
>      'systemtap-sdt-devel', to vars/mappings.yml;
> 
>    * test installation and see what breaks, fix it, rinse and
>      repeat :D
> 
> There are more steps necessary to reach full integration after the
> above, such as ensuring Dockerfiles can be generated, figuring out
> which projects can be build on the new target platforms and tweaking
> the Jenkins / Ansible configuration, but the above is a good start
> and also the part that I'm less comfortable doing myself since I'm
> not at all familiar with SUSE, so if you could take care of the
> above that'd be a big help indeed!
> 
> The guests/README.md file provides some more information, and the
> lcitool script is hopefully not too difficult to understand. Last
> but not least, if you have any questions you already know how to
> get in touch with me ;)
>