Project

General

Profile

Actions
Copy link

communication #61862

closed

2020-02-04 19:00 UTC: openSUSE Heroes meeting February 2020

Added by cboltz over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
opensuse-admin
Category:
Event
Target version:
-
Start date:
2020-01-07
Due date:
% Done:

0%

Estimated time:

Description

Where: irc://irc.freenode.net/#openSUSE-admin IRC channel
When: 2020-02-04 19:00 UTC / 20:00 CET
Who: The openSUSE Heroes team and everybody else!

Topics
see/use checklist

Files

2020-02-04-heroes-meeting.txt (26.6 KB) 2020-02-04-heroes-meeting.txt IRC meeting log cboltz, 2020-02-05 21:39
Hide closed

Checklist

  • Questions and answers from the community
  • status reports about everything
  • review old tickets
  • RFC: SSH-key management via salt
  • Email setup on anna/elsa
Actions
Copy link
 #1

Updated by cboltz over 4 years ago

  • Private changed from Yes to No
Actions
Copy link
 #2

Updated by lrupp about 4 years ago

  • Checklist item changed from [ ] Questions and answers from the community, [ ] status reports about everything, [ ] review old tickets to [ ] Questions and answers from the community, [ ] status reports about everything, [ ] review old tickets, [ ] RFC: SSH-key management via salt

SSH-key management via Salt

At the moment, we expect all users to login on the machines with their username from FreeIPA and become root via sudo.
This will break access to all machines if the single FreeIPA instance is down. It's also a bit uncommon on (open)SUSE to work via sudo if you could work as root ;-)

=> therefor I like to request/discuss if we could add our SSH-Keys to Salt and deploy them to the machines, where the user is marked as admin.

Actions
Copy link
 #3

Updated by lrupp about 4 years ago

  • Checklist item changed from [ ] Questions and answers from the community, [ ] status reports about everything, [ ] review old tickets, [ ] RFC: SSH-key management via salt to [ ] Questions and answers from the community, [ ] status reports about everything, [ ] review old tickets, [ ] RFC: SSH-key management via salt, [ ] Email setup on anna/elsa

Email setup on anna/elsa

Christian opened #61638 early in January, noting down that t-online's Email servers do not like Email sent by elsa (one of the HAProxy servers, which are used as mail relays for the machines in the internal network).

My current analysis points to a wrong 'myhostname' and reverse-DNS setup on anna and elsa.

The ticket contains my short analysis and a suggestion how to fix this. But maybe we have other Mailserver admins here with better ideas?

Actions
Copy link
 #4

Updated by cboltz about 4 years ago

Actions
Copy link

Also available in: Atom PDF