server January 2023

server@lists.fedoraproject.org

6 participants
11 discussions

Federa 35 Server default editor
by Peter Boy 14 Mar '23

14 Mar '23

In Fedora 34 the default editor was nano, for Workstation and also for Server. In my latest default F35 Server installation I noticed vim-default-editor was installed. Did some good soul take pity and bring vim back to us or did something go wrong with my installation? Best Peter

8 25

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 31 Jan '23

31 Jan '23

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2023-02-01 from 18:00:00 to 19:00:00 UTC At fedora-meeting(a)irc.libera.chat The meeting will be about: Standing meeting of the Fedora Server Working Group More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… Source: https://calendar.fedoraproject.org//meeting/10247/

1 0

Cockpit 284, cockpit-machines 282, cockpit-podman 62 released
by Martin Pitt 25 Jan '23

25 Jan '23

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes: https://cockpit-project.org/blog/cockpit-284.html - Services: Show logs for user units - Storage: Set up NBDE - Machines: Option to forcefully revert a snapshot - Podman: Use container image’s default command You can get Cockpit here: http://cockpit-project.org/running.html Take care, Martin Pitt

1 0

Are There Platforms or Companies Publicly Using Fedora Server
by mowest 20 Jan '23

20 Jan '23

For the Fedora Website design each of the editions has a section referring to "Platforms / Business" where the edition can be run or is supported or is used. I am not aware of any companies/non-profits/governments that publicly have spoken about their use of Fedora Server. Does anyone in the WG know of such entities that we could list their logo and point out that Fedora Server is running in some real world use cases? mowest ---------> discoverfoss.com

1 0

Fedora Server Website Refresh
by mowest＠vivaldi.net 19 Jan '23

19 Jan '23

I just wanted to encourage everyone in Server WG to take a look at the issue Peter Boy created. I was contacted yesterday, 1/18/23, by the website design team, and have begun working with them on a mock up for our page. I have updated the issue below with the current status and relevant links. I will post to that issue in Pagure the mock up for Fedora Server landing page once the design team has created the first version (perhaps by Monday, 1/23/23). Nothing is set in stone, so now is the time to let your ideas flow for how you would like Fedora Server Edition to be viewed by those coming to the Fedora site. On Thursday, January 19, 2023 11:06:34 AM (-05:00), Peter Boy wrote: The issue: `Fedora Website Revamp` of project: `fedora-server` has been assigned to `mowest` by pboy. https://pagure.io/fedora-server/issue/66 --------- mowest --------- discoverfoss.com

1 0

Short info about this week's IRC meeting (2023-01-18)
by Peter Boy 19 Jan '23

19 Jan '23

Again, for everyone's convenience, a brief summary of our IRC meeting right here. For greater details see meetbot == Summary: == https://meetbot.fedoraproject.org/fedora-meeting/2023-01-18/fedora-server.2… == Full log: == https://meetbot.fedoraproject.org/fedora-meeting/2023-01-18/fedora-server.2… == Highlights == ==== F38: Shorter Shutdown Timer ==== We will first review the Core Services of our current "Technical Specification" to see what configuration is implemented for a shutdown. Furthermore, we will consider conducting a test tag on this point, although implementation is likely to be difficult. Depending on the findings, we will decide on the further handling of the magnitude of the default timeout. We found contradictions resp. ambiguities about the exact configuration of the current timeout configuration in Server. Nirik will clarify this. Actions: * nirik will look up the services in our technical specification and check for time out value See pagure issue: https://pagure.io/fedora-server/issue/96 ==== Fedora Server web site revamp ==== Mowest made contact with the revamp team and introduced himself as Server contact. We are now in the flow to work on it. The next step is to collect content for our pages. Mowest asks to contribute key ideas, messages, mission statements for the content of the page. We prefer professional, meaningful texts, not rather content-less marketing phrases, which can be found partly on some newly designed pages. Actions: * pboy to create a ticket to collect our central messages for the new web site. See pagure issue: https://pagure.io/fedora-server/issue/66 ==== Possible agenda items next meeting ==== * F38: Shorter Shutdown Timer * Using Ansible to install and configure Wildfly * Fedora Server web site revamp

1 0

Call for agenda Items on 2023-01-18 18:00 ==UTC== meeting (today)
by Peter Boy 18 Jan '23

18 Jan '23

The meeting date ========================================================= Fedora Server IRC meeting Wednesday, Jan. 18 18:00 ==UTC== irc.libera.chat #fedora-meeting ========================================================= Please, check your local time using date -d ‘2023-01-18 18:00UTC’ fort Unfortunately, there is a lot to read beforehand, today. == Agenda == 1. = Follow up actions = 2. = Shorter Shutdown Timer = Fesco meeting log: https://meetbot.fedoraproject.org/fedora-meeting/2023-01-17/fesco.2023-01-1… Systemwide change proposal: https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer Mailing list discussion: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… see specifically Colin Wolters (CoreOS) post 3. = Using Ansible to install and configure Wildfly= #link https://pagure.io/fedora-server/issue/60 Mailing List: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… (step through the posts using „newer“ and „older“, I can’t manage to get a link to the complete thread) Goal: We want to discuss how to proceed 4. = Server WG work program for upcomming year = #link https://pagure.io/fedora-server/boards/Works%20in%20progress 5. = Open floor = For any additions or changes, please reply to this email. For an overview about current tasks look at: https://pagure.io/fedora-server/boards/Works%20in%20progress -- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast

1 0

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 17 Jan '23

17 Jan '23

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2023-01-18 from 18:00:00 to 19:00:00 UTC At fedora-meeting(a)irc.libera.chat The meeting will be about: Standing meeting of the Fedora Server Working Group More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… Source: https://calendar.fedoraproject.org//meeting/10247/

1 0

Cockpit 283, cockpit-machines 281 and cockpit-podman 60
by Katerina Koukiou 12 Jan '23

12 Jan '23

Happy new year! I am happy to announce the first Cockpit release in 2023! Here are the release notes from Cockpit version 283 and cockpit-machines version 281: https://cockpit-project.org/blog/cockpit-283.html Users can now create on the Services page timers to run every minute! And Cockpit Machines now has support for adding a virtual software-based watchdog device to a VM. Cockpit 283 is available for download here: - Cockpit Source Tarball <https://github.com/cockpit-project/cockpit/releases/tag/283> - Cockpit Fedora 37 <https://bodhi.fedoraproject.org/updates/FEDORA-2023-74586bb92c> - Cockpit Fedora 36 <https://bodhi.fedoraproject.org/updates/FEDORA-2023-8bc12f90dd> Cockpit Machines 281: - cockpit-machines Source Tarball <https://github.com/cockpit-project/cockpit-machines/releases/tag/281> - cockpit-machines Fedora 37 <https://bodhi.fedoraproject.org/updates/FEDORA-2023-49b3964047> - cockpit-machines Fedora 36 <https://bodhi.fedoraproject.org/updates/FEDORA-2023-3b424a9b80> Cockpit podman 60: - cockpit-podman Source Tarball <https://github.com/cockpit-project/cockpit-podman/releases/tag/60> - cockpit-podman Fedora 37 <https://bodhi.fedoraproject.org/updates/FEDORA-2023-e680d8b5cb> - cockpit-podman Fedora 36 <https://bodhi.fedoraproject.org/updates/FEDORA-2023-c0a825e37f> Cheers, Katerina Koukiou

1 0

Re: WildFly
by John W. Himpel 06 Jan '23

06 Jan '23

Jason, Forgive my tardiness in replying. Sickness has caused the delay. Looking at the template (wildfly.properties.j2), I will make a wild guess as to the issue. There is a ansible_variable (not a user variable) known as inventory_hostname. It is created by ansible when you begin execution of the role. It is created in the Gathering Facts tasks that is auto- generated by ansible to execute as the first task in the execution of a role. I'm unsure if the variable is derived from the hostnamectl command on the target host or if it is derived from the name in the hosts.yml file under the inventories directory. The template having an issue is configure-properties.yml. It is trying to determine which network interface to configure wildfly to use. The computation relies on inventory_hostname being a fqdn. Is the target hostname in your inventory file a fqdn? Another possibility, is my logic may be assuming ipv4 addressing. Perhaps your system is ipv6 addressed? One last possibility is you have defined the target host to be on the same host as the ansible controller. In which case the ansible task will not use any ipv4 or ipv6 to communicate between the target host and the ansible controller. If that is the case, there may not be a SSH connection from which to determine the ipv4 address to use. Hope that one of these ideas bears fruit. Thanks for testing. I appreciate your effort very much. John Himpel (recovering from the flu) The variables that On Thu, 2022-12-29 at 22:55 +0000, J Beard wrote: > John, > > I reworked my inventory to look like yours and same thing. Also, I > think you need to update your github page. What I pulled down isn't > updated to what you posted in this email chain. I'm going to look at > few things later tonight. > > TASK [wildfly_service : configure_properties wf26 - Configure > standalone properties] ********************************************An > exception occurred during task execution. To see the full > traceback, use -vvv. The error was: > ansible.errors.AnsibleUndefinedVariable: {{ > hostvars[inventory_hostname]["ansible_env"].SSH_CONNECTION.split(" > ")[2] }}: 'dict object' has no attribute 'SSH_CONNECTION' > fatal: [f36server1.iapetus.local]: FAILED! => {"changed": false, > "msg": "AnsibleUndefinedVariable: {{ > hostvars[inventory_hostname][\"ansible_env\"].SSH_CONNECTION.split(\" > \")[2] }}: 'dict object' has no attribute 'SSH_CONNECTION'"} > > > inventories├── inventories/test > ├── inventories/test/hosts.yml > └── inventories/test/host_vars > └── inventories/test/host_vars/f36server1.iapetus.local > ├── > inventories/test/host_vars/f36server1.iapetus.local/vars.yml > └── > inventories/test/host_vars/f36server1.iapetus.local/vault.yml > > > > > From: Jason Beard <jas_beard(a)hotmail.com> > Sent: Wednesday, December 28, 2022 5:21 PM > To: server(a)lists.fedoraproject.org <server(a)lists.fedoraproject.org> > Subject: Re: WildFly > I'll check the inventory stuff in a bit. Without looking I'm sure > mine isn't setup like that. I'll have to fix that. > Task where it fails: > TASK [wildfly_service : configure_properties wf26 - Configure > standalone properties] > On 12/28/22 12:46, John W. Himpel wrote: > > On Wed, 2022-12-28 at 11:35 -0600, Jason Beard wrote: > > > Greetings! In regards to Wildfly below is the error I'm getting > > > in the Ansible playbook run. > > > The error is in the jinja2 template. I'm pretty sure I can > > > update it a different way but I wasn't sure that the current > > > setting is a necessity. I'm an Ansible newbie so I tend to ask > > > before I change things. > > > Let me know if you need any other information. > > > Thanks, > > > Jason > > > > > > Error: > > > ~~~ > > > ansible.errors.AnsibleUndefinedVariable: {{ > > > hostvars[inventory_hostname]["ansible_env"].SSH_CONNECTION.split( > > > " ")[2] }}: 'dict object'has no attribute 'SSH_CONNECTION' > > > > > > During handling of the above exception, another exception > > > occurred: > > > > > > Traceback (most recent call last): > > > File "/usr/lib/python3.8/site- > > > packages/ansible/plugins/action/template.py", line 150, in > > > run > > > > > > resultant = templar.do_template(template_data, > > > preserve_trailing_newlines=True, > > > escape_backslashes=False) > > > > > > File "/usr/lib/python3.8/site- > > > packages/ansible/template/__init__.py", line 1176, in > > > do_template > > > > > > raise AnsibleUndefinedVariable(e) > > > ansible.errors.AnsibleUndefinedVariable: {{ > > > hostvars[inventory_hostname]["ansible_env"].SSH_CONNECTION.split( > > > " ")[2] }}: 'dict object' has no attribute 'SSH_CONNECTION' > > > fatal: [f36server1.iapetus.local]: FAILED! => > > > { > > > "changed": false, > > > "msg": "AnsibleUndefinedVariable: {{ > > > hostvars[inventory_hostname][\"ansible_env\"].SSH_CONNECTION.spli > > > t(\" \")[2] }}: 'dict object' has no attribute 'SSH_CONNECTION'" > > > } > > > ~~~ > > > > Jason, > > > > Thanks for the report. There are many tasks in the role that > > attempt to copy a templatized file to the ansible target host. I > > believe I have supplied a name for each task that should display in > > the ansible.log file (if you have one) or on standard out. It > > would be most useful if you could tell me the name on the task that > > is having the issue. > > > > Without the above information, my best guess is your "inventories" > > directory has an issue. Mine looks like this: > > > > ansible/ > > inventories/ > > hosts.yml > > host_vars/ > > testWildfly.jlhimpel.net/ > > vars.yml > > vault.yml > > > > Where hosts.yml contains: > > --- > > all: > > hosts: > > testWildfly.jlhimpel.net: > > children: > > allServersGroup: > > hosts: > > testWildfly.jlhimpel.net: > > wildflyAllRemoveGroup: > > hosts: > > testWildfly.jlhimpel.net: > > wildflyInstanceRemoveGroup: > > hosts: > > testWildfly.jlhimpel.net: > > wildflyServiceGroup: > > hosts: > > testWildfly.jlhimpel.net: > > wildflySslGroup: > > hosts: > > testWildfly.jlhimpel.net: > > wildflyVersionRemoveGroup: > > hosts: > > testWildfly.jlhimpel.net: > > ... > > > > Where vars.yml contains: > > --- > > # python version on this host > > ansible_python_interpreter: /usr/bin/python3 > > > > # non sensitive data > > firewall_mgr: firewalld > > primary_net_interface: enp1s0 > > > > # sensitive data > > ansible_ssh_user: "{{ vault_ansible_ssh_user }}" > > ansible_ssh_pass: "{{ vault_ansible_ssh_pass }}" > > ansible_become_pass: "{{ vault_ansible_become_pass }}" > > ... > > > > Where vault.yml is an encrypted file containing: > > --- > > vault_ansible_ssh_user: XXXXX > > vault_ansible_ssh_pass: XXXXX > > vault_ansible_become_pass: XXXXX > > (Of course, you will need to provide your local values for XXXXX). > > > > Let me know if any of this helps. > > > > John > > ... > > > > > > > > > > > > > _______________________________________________ > > > server mailing list -- server(a)lists.fedoraproject.org > > > To unsubscribe send an email to > > > server-leave(a)lists.fedoraproject.org > > > Fedora Code of Conduct: > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > List Guidelines: > > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > > List Archives: > > > https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org > > > Do not reply to spam, report it: > > > https://pagure.io/fedora-infrastructure/new_issue > > > > > > > > _______________________________________________ > > server mailing list -- server(a)lists.fedoraproject.org > > To unsubscribe send an email to server-leave(a)lists.fedoraproject.org > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue > _______________________________________________ > server mailing list -- server(a)lists.fedoraproject.org > To unsubscribe send an email to server-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server January 2023