February 2020 - Uyuni Users - openSUSE Mailing Lists

[uyuni-users] New wiki page with Uyuni presentations

by Pau Garcia Quiles

Hello I have added a new page to the Uyuni wiki with links to past presentations about Uyuni, how to get started developing, etc: https://github.com/uyuni-project/uyuni/wiki/Presentations If there is any other presentation you would like to be linked, please tell me. Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 year, 5 months

1
0
0 0

[uyuni-users] Uyuni accepted in Google Summer of Code 2020

by Pau Garcia Quiles

Hello We have been accepted in Google Summer of Code (look for the openSUSE organization, we are participating as an openSUSE project) This is the initial list of ideas we submitted: * Convert Virtual Systems page to ReactJS https://github.com/openSUSE/mentoring/issues/124 * Breakdown Uyuni into plugins architecture https://github.com/openSUSE/mentoring/issues/126 * Enhance Debian support https://github.com/openSUSE/mentoring/issues/127 * Add KDE support (co-mentored with KDE) https://github.com/openSUSE/mentoring/issues/128 * Improve Uyuni Documentation Publishing Theme https://github.com/openSUSE/mentoring/issues/125 We are still on time to add more ideas, please tell me (or add directly to the openSUSE mentoring GH repository) if you have something in mind. If you are a student and are interested in taking one of them, or have some other proposal, speak up! Also if you want to be a mentor. Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 year, 5 months

1
0
0 0

[uyuni-users] SUSE Manager to Uyuni?

by Alisia Prince

My customer is in the process of moving away from Micro Focus products to Microsoft ones. Unfortunately, their current SUMA license is expired. They're running version 3.2 of SUMA and their primary supported systems are OES15.1, SLES12.x and SLES11.x (yes, I know it's not supported, see previous comment). They've got about 200 systems that are all virtual on 25 VM hosts running VMware. The issue with the license is partly that the state makes it difficult to purchase since SUSE is not on the state contract and partly that SUSE sales folks were not lined up properly to help get quotes and such. As a result, we don't know how long it will take to get the license renewed. They've been using Icinga for monitoring but the latest patches have caused conflicts with nagios and are breaking the plugins. Also, we've done the patch channels manually but would like to get them setup with the built in versions of SUMA 4 and now they're also looking into the new monitoring solution. Would they better off, given their move away from OES, to use Uyuni instead? And, if they do, can we use the migration wizard in Uyuni to go from SUMA to Uyuni? Thanks! A -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 year, 5 months

1
0
0 0

[uyuni-users] Trouble making macros in configuration files work

by Kristijan Savic - ratiokontakt GmbH

Version of Uyuni: 2020.01 In short, macros in configuration files get deployed literally instead of being replaced with custom system information. Longer explanation: The configuration file is as follows: /root/.bashrc <snip> export PS1="({| rhn.system.custom_info(contract_number) |} {| rhn.system.custom_info(bash_name) |}) $PS1" </snip> The delimiters are set to {| and |} for beginning and end. Accordingly I have also configured two custom system information key named "contract_number" and "bash_name" After a system gets bootstraped the two keys are filled with values unter "Custom info". For example "12345" and "backup server". Afterwards the configuration files are deployed, but the macros are taken literally e.g. {| rhn.system.custom_info(contract_number) |} instead of being replaced with 12345. I am not sure if I am doing something wrong or may this be a bug? -------------------------------------------------------- ratiokontakt GmbH Biegenhofstr. 13 96103 Hallstadt Telefon: +49 (0) 951 9 35 35 - 0 Telefax: +49 (0) 951 9 35 35 - 902 Internet: www.ratiokontakt.de Geschäftsführer: Stefan Kraft Amtsgericht Bamberg - HRB 3757 -------------------------------------------------------- ratiokontakt ist zertifiziert nach DIN ISO/IEC 27001 -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 year, 5 months

1
0
0 0

[uyuni-users] RHEL8/Centos8 as uyuni server?

by Stefan Wiederoder

Hello list, the new uyuni release has initial support for RHEL8/Centos8 clients, but is also planned to support RHEL8/Centos8 on the server side? thanks , Stefan Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>. -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 year, 5 months

3
2
0 0

2021

2020

2019

2018

Uyuni Users February 2020