February 2020 - nmstate-devel - Fedora mailing-lists

[ANNOUNCE] Master branch is tacking nmstate-0.3.0
by Fernando Fernandez Mancera 25 Feb '20

25 Feb '20

Hi! The git master branch is now tracking nmstate-0.3.0. In addition, nmstate-0.2.x is now being tracked by nmstate-0.2 git branch. Please, find below the new Copr repository tracking the nmstate-0.2 HEAD. * Copr nmstate-0.2-git: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.2-git/ * Copr nmstate-0.2: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.2/ * Github nmstate-0.2 branch: https://github.com/nmstate/nmstate/tree/nmstate-0.2 Happy Networking!

1 0

[ANNOUNCE] nmstate 0.2.6 release
by Fernando Fernandez Mancera 25 Feb '20

25 Feb '20

Hi! The Nmstate project proudly presents: nmstate 0.2.6 This release contains fixes and new features. => Bug Fixes * Linux Bonding: Fix "fail_over_mac" support with active backup bond mode. * Linux Bonding: Fix "arp_ip_target" bond option support. * OVS Bridge VLAN: Use "unknown" value for unsupported modes. * Fix partial editting for DNS configuration. * Report only non-default bonding option values. * Fix switching from static IP to DHCP/Autoconf. => New Features * Linux Bonding: Support numeric values for options. => Known issues when using NetworkManager 1.22.8 * All changes to bridges might disrupt their connectivity. * Cannot detach a system port from an OVS bridge. * Sometimes, NetworkManager may throw a "Failed to find a compatible device for this connection" error. * Cannot set bond option with updelay=0,miimon=0. * Cannot set bond option with miimon=100,arp_interval=0. Please note that the packages are already available. * Fedora 32: https://koji.fedoraproject.org/koji/buildinfo?buildID=1470063 * Fedora rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1470051 * Copr nmstate-0.2: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.2/packages/ * Copr nmstate-0.2-git: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.2-git/packages/ * Copr nmstate: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate/packages/ * PyPi: https://pypi.org/project/nmstate/0.2.6/ Happy networking!

1 0

Hi everyone!
by Elvira G. 20 Feb '20

20 Feb '20

Hello there, My name is Elvira García Ruiz (AKA "elvgarrui" on Github), and I've recently started contributing to nmstate. I've been wanting to learn how to contribute to a libre software project for a while, and I'm also interested on improving my skills in Python, so when ffmancera talked to me about this project I decided I wanted to get involved. Currently, I'm finishing my master's degree on Logics, Computation and AI, and prior to that I studied a computer science degree. I don't really have a deep knowledge about networking, but I'm in for learning about it! If all goes well, I would also be interested on participating at the Google Summer of Code with this project. Lastly, I wanted to thank all of you for your patience when reviewing my PRs!! =) Kind regards, Elvira

1 0

Copr will be without ppc64le support, soon
by Till Maas 20 Feb '20

20 Feb '20

Hi, I just saw that Copr will not be able to support ppc64le, soon. Vdsm requested support for it in the past. Since Nmstate is noarch, it should be possible to just use the x86_64 repo on ppc64le hosts. A bigger problem might be that we cannot provide new NetworkManager builds for ppc64le, too. Is this going to be a problem? What are the exact requirements regarding ppc64le support? Kind regards Till ---------- Forwarded message ---------- From: "Miroslav Suchý" <msuchy(a)redhat.com> To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org> Cc: Bcc: Date: Thu, 20 Feb 2020 10:27:40 +0100 Subject: Copr outage - details tl;dr: On Sunday 23rd February, there will be Copr outage. It will last the whole day. PPC64LE builder and chroots will be deactivated. The PPC64LE builders should be back in a matter of weeks. Hi. As previously announced, Fedora's infrastructure is moving to a different datacenter. For some servers, the move is trivial. Copr servers are different. Copr build system consists of four servers, plus four staging servers. Eight TB of repos, four TB of dist-git, and several small volumes. The original plan was to move to Washington D.C. to IAD2 datacenter by June. Copr is running in Fedora OpenStack, and this cloud has to be evacuated by the beginning of March to free an IP range. The plan was to move Copr to new hardware (thanks to Red Hat) and later move this HW to the new datacenter. That would mean two outages, where the second one lasted at least 15 days (!). We were looking for another option and we found it. We are going to move Copr to Amazon AWS, shutdown old VM on Fedora Cloud. Move the new HW to IAD2 datacenter and then move Copr from AWS to new HW in IAD2 - FYI, the final destination is still subject to change. This still means two outages, but they should be just a few hours. And web server with DNF repositories should be available all the time. The second outage, will happen in May or June. Here is a detailed schedule. We are going to update this table during migration. You can watch the progress during migration: https://docs.google.com/spreadsheets/d/1jrCgdhseZwi91CTRlo9Y5DNwfl9VHoZfjHP… Here is a short abstract: * we are doing constant rsync to the new location * we spin up staging and production instances in the new location * on Sunday morning we stop frontend and therefore accepting new jobs. The backend with DNF repos will still be operational. * we do final rsync (~6 hours) * around 13:00 UTC we switch DNS to the new location * we then enable all services * once we confirm that everything is operational, the outage will be over There are several caveats: * After we enable services on Sunday 13:00 UTC you may see some failures. Be asured that we will swiftly address them. * Once we get out of Fedora Cloud, we lost access to PPC64LE builders. We are going to deactivate those chroots just before the migration. After a few weeks, we should get it back. ETA is unknown. The worst-case scenario is in June 2020. We will be aiming to bring it back as soon as possible. * Any small issue can easily change the schedule by hours. E.g., just simple 'chown -R' on backend runs ~4 hours. There are going to be three Copr engineers and one fedora-infrastructure member available whole Sunday. If you experienced a problem, do not hesitate to contact us. We are on #fedora-buildsys on Freenode. The link to the outage ticket is: https://pagure.io/fedora-infrastructure/issue/8668 -- Miroslav Suchy, RHCARed Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

1 0

[ANNOUNCE] nmstate 0.2.5 release
by Fernando Fernandez Mancera 20 Feb '20

20 Feb '20

Hi! The Nmstate project proudly presents: nmstate 0.2.5 This release contains fixes, new features and breaking changes. => Breaking changes * Deprecate specifying keyword arguments as positional arguments in the public methods. This will become a hard failure in Nmstate-0.3.0 and later and it affects the following functions: - "libnmstate.apply()" - "libnmstate.commit()" - "libnmstate.rollback()" - "libmstate.show()" * NetworkManager 1.22.8 or later is now required. => Bug Fixes * Fix "AtributeError" when editing an existing OVS interface. * Do not remove slaves implicitly when removing the master interface. * Fix team interface port support. * Prevent virtual interface removal after DHCP or IPV6-RA timeout. * Get Linux Bonding options from kernel instead of reading the NetworkManager configuration. => New Features * Report missing NetworkManager plugin during validation. * Support OVS Link Aggregation (Bonding). => Known issues when using NetworkManager 1.22.8 * All changes to bridges might disrupt their connectivity. * Cannot set Linux Bond option to "fail_over_mac=1". * Cannot detach a system port from an OVS bridge. * Sometimes, NetworkManager may throw a "Failed to find a compatible device for this connection" error. Please note that the packages are already available. * Fedora 32: https://koji.fedoraproject.org/koji/buildinfo?buildID=1466446 * Fedora rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1466444 * Copr nmstate-0.2: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.2/packages/ * Copr nmstate: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate/packages/ * PyPi: https://pypi.org/project/nmstate/0.2.5/ Happy networking!

1 0

Checkpoint logic error for integration test tear-up phase
by Till Maas 14 Feb '20

14 Feb '20

Hi, while looking at Nmstate logs after failures I noticed that Nmstate uses checkpoints in the tear-up phase of integration tests. Therefore, if something fails inside the mainloopo in the tear-up phase, all tear-up progress is reverted instead of keeping at least the removed bits removed. Am I missing something? My idea for the easiest/cleanest solution would be to just issue "nmcli c d $interface; nmclid d $interface (if it is not eth1/eth2)" and ignoring the returncode for all interfaces that are touched in a test as the tear-up code. Since Nmstate also stores routes and DNS information in the respective profiles, this should properly clean it up with the better working nmcli code. What do you think? Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

2 2

[ANNOUNCE] nmstate 0.2.4 release
by Fernando Fernandez Mancera 12 Feb '20

12 Feb '20

Hi! The Nmstate project proudly presents: nmstate 0.2.4 This release contains fixes and new features. => Bug Fixes * Reduce minimal required MAC address length to 4 octets * Warn early when the same interface name is mentioned multiple times => New Features * Raise NmstateTimeoutError on mainloop timeout Please note that the Fedora packages are already available. * Fedora 32: https://koji.fedoraproject.org/koji/taskinfo?taskID=41469394 * Fedora rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=41469345 * Copr nmstate-0.2: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.2/packages/ * Copr nmstate: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate/packages/ Happy networking!

1 0

Copr GIT builds broken because of regression in Copr
by Till Maas 11 Feb '20

11 Feb '20

Hi, https://pagure.io/copr/copr/issue/1258 breaks our Copr Git builds currently. A possible workaround might be diff --git a/.copr/Makefile b/.copr/Makefile index b5d5c22..47dae83 100644 --- a/.copr/Makefile +++ b/.copr/Makefile @@ -3,4 +3,5 @@ SRPM_DEPENDENCIES=python$(python_major_version)-setuptools git srpm: rpm -q --whatprovides $(SRPM_DEPENDENCIES) || dnf -y install $(SRPM_DEPENDENCIES) - $(dir $(realpath $(firstword $(MAKEFILE_LIST))))../packaging/make_srpm.sh + # su needed as a workaround for https://pagure.io/copr/copr/issue/1258 + su -c '$(dir $(realpath $(firstword $(MAKEFILE_LIST))))../packaging/make_srpm.sh' - mockbuild In case anyone needs the repo urgently, we can try this. Otherwise we can wait for a hotfix in Copr. Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

2 2

Intent to remove nmstate-0.1 branch/packages (Copr) and Fedora 31 and earlier Copr repos
by Till Maas 07 Feb '20

07 Feb '20

Hi, it appears that we do not need to support nmstate-0.1/Fedora 31 anymore. Therefore, to clean up and free ressources, we plan to - remove the nmstate-0.1 branch from Github - remove the nmstate-0.1 related Copr repositories - Remove Fedora 31 and earlier chroots (build targets) from Copr repositories If there are no objections, we will start to implement these changes after a week (on 17 February or later). If you have any need for any of these items, please add a comment to the issue: https://github.com/nmstate/nmstate/issues/758 Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

3 3

2020-02-06 meeting minutes
by Till Maas 06 Feb '20

06 Feb '20

Hi, Here are my notes. Please correct me if I am wrong or missed anything. Gris will mark integration tests as tier1 for NM QE, tier2 optional or maybe not that important, tier3 with random failures -> more discussion in PR Testers reported problems with plugins being removed with rpm/reinstalling them with DNF because the test systems might not have any repos configured, it would help them to just remove the .so file temporarily. Important would be to use proper temporary directories created with mkdtemp or renaming the plugin in the same directory instead of moving it to a temporary directory. GSoC: Prioritize varlink, stretch goals Ansible and maybe remote API based on varlink Fernando will be the primary Mentor, the others will be help as fallback nmstate-0.1 branch does not seem to be needed anymore. Request feedback from the community and delete it if there are no objections. -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

1 0

2024

2023

2022

2021

2020

2019

nmstate-devel February 2020