New repo for os-net-config?
The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub repo doesn't have the same level of CI that we have now on OpenStack Jenkins.
Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of.
If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly?
Thank you very much for any suggestions,
-Dan Sneddon
On Wed, Jun 7, 2023, at 7:29 AM, Dan Sneddon wrote:
The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub repo doesn't have the same level of CI that we have now on OpenStack Jenkins.
Note we haven't run Jenkins since ~2017.
Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of.
Is there some reason the existing repository won't work?
If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly?
Thank you very much for any suggestions,
-Dan Sneddon
-- Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
On Wed, Jun 7, 2023 at 9:00 AM Clark Boylan cboylan@sapwetik.org wrote:
On Wed, Jun 7, 2023, at 7:29 AM, Dan Sneddon wrote:
The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub repo doesn't have the same level of CI that we have now on OpenStack Jenkins.
Note we haven't run Jenkins since ~2017.
I misspoke, I meant to say Gerrit. GitHub is workable, but the review/merge interface is not as good, IMHO.
Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of.
Is there some reason the existing repository won't work?
Currently os-net-config is a part of the TripleO project. Since TripleO is retiring and being replaced by something hosted on GitHub, we are no longer maintaining the Master/Zed branches.
If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly?
Thank you very much for any suggestions,
-Dan Sneddon
-- Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
--
Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
On Wed, Jun 7, 2023 at 12:13 PM Dan Sneddon dsneddon@redhat.com wrote:
On Wed, Jun 7, 2023 at 9:00 AM Clark Boylan cboylan@sapwetik.org wrote:
On Wed, Jun 7, 2023, at 7:29 AM, Dan Sneddon wrote:
The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub
repo
doesn't have the same level of CI that we have now on OpenStack Jenkins.
Note we haven't run Jenkins since ~2017.
I misspoke, I meant to say Gerrit. GitHub is workable, but the review/merge interface is not as good, IMHO.
Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of.
Is there some reason the existing repository won't work?
Currently os-net-config is a part of the TripleO project. Since TripleO is retiring and being replaced by something hosted on GitHub, we are no longer maintaining the Master/Zed branches.
Its governance could be moved and the repo stay as-is, that is if a project wishes to adopt it to keep it in OpenStack governance.
If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly?
Thank you very much for any suggestions,
-Dan Sneddon
-- Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
--
Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
On 2023-06-07 12:07:59 -0700 (-0700), Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 9:00 AM Clark Boylan cboylan@sapwetik.org wrote:
[...]
Is there some reason the existing repository won't work?
Currently os-net-config is a part of the TripleO project. Since TripleO is retiring and being replaced by something hosted on GitHub, we are no longer maintaining the Master/Zed branches.
[...]
Maybe you misunderstood. To restate: Is there any reason the people who want to use and maintain the openstack/os-net-config master and stable/zed (or other) branches can't just adopt the project? It's well within the TC's power to grant control of that repository to another project team who isn't TripleO.
Which use cases specifically (outside of Red Hat's lingering interest in the stable/wallaby branches of TripleO repositories) are you referring to?
On Wed, Jun 7, 2023 at 12:49 PM Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-06-07 12:07:59 -0700 (-0700), Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 9:00 AM Clark Boylan cboylan@sapwetik.org
wrote: [...]
Is there some reason the existing repository won't work?
Currently os-net-config is a part of the TripleO project. Since TripleO is retiring and being replaced by something hosted on GitHub, we are no longer maintaining the Master/Zed branches.
[...]
Maybe you misunderstood. To restate: Is there any reason the people who want to use and maintain the openstack/os-net-config master and stable/zed (or other) branches can't just adopt the project? It's well within the TC's power to grant control of that repository to another project team who isn't TripleO.
Which use cases specifically (outside of Red Hat's lingering interest in the stable/wallaby branches of TripleO repositories) are you referring to? -- Jeremy Stanley
The people who want to continue to use os-net-config are developing the replacement for TripleO, but they have moved to GutHub. That’s an option for os-net-config, but not my first preference. I have over the years heard of companies using os-net-config for various use cases. It’s possible that posting to openstack-discuss won’t reach any of those users, but it doesn’t hurt to ask here.
-Dan
On Wed, 2023-06-07 at 15:44 -0700, Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 12:49 PM Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-06-07 12:07:59 -0700 (-0700), Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 9:00 AM Clark Boylan cboylan@sapwetik.org
wrote: [...]
Is there some reason the existing repository won't work?
Currently os-net-config is a part of the TripleO project. Since TripleO is retiring and being replaced by something hosted on GitHub, we are no longer maintaining the Master/Zed branches.
[...]
Maybe you misunderstood. To restate: Is there any reason the people who want to use and maintain the openstack/os-net-config master and stable/zed (or other) branches can't just adopt the project? It's well within the TC's power to grant control of that repository to another project team who isn't TripleO.
Which use cases specifically (outside of Red Hat's lingering interest in the stable/wallaby branches of TripleO repositories) are you referring to? -- Jeremy Stanley
The people who want to continue to use os-net-config are developing the replacement for TripleO, but they have moved to GutHub. That’s an option for os-net-config, but not my first preference. I have over the years heard of companies using os-net-config for various use cases. It’s possible that posting to openstack-discuss won’t reach any of those users, but it doesn’t hurt to ask here.
i will need to reread the thread but i thought that there was reference to baremetal use cases i had assumed that meant ironic?
just because we are using GitHub for the replacement for tripleo is not a reason to move things to github by default. movign to github for the code review as im sure you are aware is a much worse code review interface. we would be loosing the release tooling and ablity to publish to pypi. the ci would need to be ported amoung other things.
There is also an open question of if/how much of os-net-config will continue to be used for the operator based installer. alternatives are being considered although we have known gaps. no desicssion has been made on if we will continue with os-net-config or replace it with nmstate or a hybird of the two.
a quick search https://codesearch.opendev.org/?q=os-net-config&i=nope&literal=nope&... seams to indicate that os-net-config is used by: - openstack-virtual-baremetal - networking-bigswitch - possibly starlingx
so i would suggest moving it to ironic governance and keeping the repo as is to suppot the virtual baremetal usecase.
-Dan
On 6/8/23 12:53, smooney@redhat.com wrote:
On Wed, 2023-06-07 at 15:44 -0700, Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 12:49 PM Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-06-07 12:07:59 -0700 (-0700), Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 9:00 AM Clark Boylan cboylan@sapwetik.org
wrote: [...]
Is there some reason the existing repository won't work?
Currently os-net-config is a part of the TripleO project. Since TripleO is retiring and being replaced by something hosted on GitHub, we are no longer maintaining the Master/Zed branches.
[...]
Maybe you misunderstood. To restate: Is there any reason the people who want to use and maintain the openstack/os-net-config master and stable/zed (or other) branches can't just adopt the project? It's well within the TC's power to grant control of that repository to another project team who isn't TripleO.
Which use cases specifically (outside of Red Hat's lingering interest in the stable/wallaby branches of TripleO repositories) are you referring to? -- Jeremy Stanley
The people who want to continue to use os-net-config are developing the replacement for TripleO, but they have moved to GutHub. That’s an option for os-net-config, but not my first preference. I have over the years heard of companies using os-net-config for various use cases. It’s possible that posting to openstack-discuss won’t reach any of those users, but it doesn’t hurt to ask here.
i will need to reread the thread but i thought that there was reference to baremetal use cases i had assumed that meant ironic?
just because we are using GitHub for the replacement for tripleo is not a reason to move things to github by default. movign to github for the code review as im sure you are aware is a much worse code review interface. we would be loosing the release tooling and ablity to publish to pypi. the ci would need to be ported amoung other things.
There is also an open question of if/how much of os-net-config will continue to be used for the operator based installer. alternatives are being considered although we have known gaps. no desicssion has been made on if we will continue with os-net-config or replace it with nmstate or a hybird of the two.
a quick search https://codesearch.opendev.org/?q=os-net-config&i=nope&literal=nope&... seams to indicate that os-net-config is used by:
- openstack-virtual-baremetal
- networking-bigswitch
- possibly starlingx
so i would suggest moving it to ironic governance and keeping the repo as is to suppot the virtual baremetal usecase.
None of these repos are part of the baremetal project. I cannot speak for the PTL or for the team, but I highly doubt we'll be in a position to adopt os-net-config.
Dmitry
-Dan
On Mon, Jun 12, 2023 at 3:51 AM Dmitry Tantsur dtantsur@protonmail.com wrote:
On 6/8/23 12:53, smooney@redhat.com wrote:
On Wed, 2023-06-07 at 15:44 -0700, Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 12:49 PM Jeremy Stanley fungi@yuggoth.org
wrote:
On 2023-06-07 12:07:59 -0700 (-0700), Dan Sneddon wrote:
On Wed, Jun 7, 2023 at 9:00 AM Clark Boylan cboylan@sapwetik.org
wrote: [...]
Is there some reason the existing repository won't work?
Currently os-net-config is a part of the TripleO project. Since TripleO is retiring and being replaced by something hosted on GitHub, we are no longer maintaining the Master/Zed branches.
[...]
Maybe you misunderstood. To restate: Is there any reason the people who want to use and maintain the openstack/os-net-config master and stable/zed (or other) branches can't just adopt the project? It's well within the TC's power to grant control of that repository to another project team who isn't TripleO.
Which use cases specifically (outside of Red Hat's lingering interest in the stable/wallaby branches of TripleO repositories) are you referring to? -- Jeremy Stanley
The people who want to continue to use os-net-config are developing the replacement for TripleO, but they have moved to GutHub. That’s an option for os-net-config, but not my first preference. I have over the years heard of companies using os-net-config for various use cases. It’s possible that posting to openstack-discuss won’t reach
any
of those users, but it doesn’t hurt to ask here.
i will need to reread the thread but i thought that there was reference
to baremetal
use cases i had assumed that meant ironic?
just because we are using GitHub for the replacement for tripleo is not
a reason to move
things to github by default. movign to github for the code review as im
sure you are aware
is a much worse code review interface. we would be loosing the release
tooling and ablity to
publish to pypi. the ci would need to be ported amoung other things.
There is also an open question of if/how much of os-net-config will
continue to be used for the
operator based installer. alternatives are being considered although we
have known gaps.
no desicssion has been made on if we will continue with os-net-config or
replace it with nmstate
or a hybird of the two.
a quick search
https://codesearch.opendev.org/?q=os-net-config&i=nope&literal=nope&...
seams to indicate that os-net-config is used by:
- openstack-virtual-baremetal
- networking-bigswitch
- possibly starlingx
so i would suggest moving it to ironic governance and keeping the repo
as is to suppot the virtual baremetal usecase.
None of these repos are part of the baremetal project. I cannot speak for the PTL or for the team, but I highly doubt we'll be in a position to adopt os-net-config.
Dmitry
+1
I don't think any Ironic documentation refers to using os-net-config -- it's a single option for how to configure your images post-boot out of a large number (many of which remain supported). I agree with Dmitry that it's hard to see this fitting well in the baremetal program.
Thanks, Jay Faulkner Ironic PTL TC Vice-Chair
On Wed, 7 Jun 2023 at 09:36, Dan Sneddon dsneddon@redhat.com wrote:
The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub repo doesn't have the same level of CI that we have now on OpenStack Jenkins.
s/Jenkins/Zuul/ :p
Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of.
What exactly is the problem with the repo as is? I guess if needed it could be adopted by a team that is actively using it?
If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly?
I don't see anyone:
$ beagle --server-url https://codesearch.openstack.org search --format=grep --file '.*requirements.*' os-net-config openstack/requirements:global-requirements.txt:171:os-net-config # Apache-2.0 openstack/tripleo-ansible:molecule-requirements.txt:22:os-net-config # Apache-2.0 openstack/tripleo-validations:requirements.txt:13:os-net-config>=7.1.0 # Apache-2.0 starlingx/root:build-tools/build-wheels/debian/openstack-requirements/ussuri/global-requirements.txt:210:os-net-config # Apache-2.0 starlingx/root:build-tools/build-wheels/debian/openstack-requirements/ussuri/upper-constraints.txt:351:os-net-config===12.3.5 starlingx/root:build-tools/build-wheels/debian/openstack-requirements/ussuri/upstream/36a2c2677e56afe0ece61cc0ade0f89285440ea0/global-requirements.txt:210:os-net-config # Apache-2.0 starlingx/root:build-tools/build-wheels/debian/openstack-requirements/ussuri/upstream/36a2c2677e56afe0ece61cc0ade0f89285440ea0/upper-constraints.txt:309:os-net-config===12.3.5
Thank you very much for any suggestions,
-Dan Sneddon
-- Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
Hey Dan,
There are a couple other projects which are maintained, and might be able to take the role of os-net-config in your environment. Both of these are based on reading out information from a config drive and configuring a host: - https://docs.openstack.org/infra/glean/ - https://cloudinit.readthedocs.io/en/latest/
Neither of these may fit your use case exactly, but they continue to exist and are supported, whereas right now (other than you) there's been no interest in keeping some of these tripleo deliverables alive.
Good luck, Jay Faulkner Ironic PTL
On Wed, Jun 7, 2023 at 7:46 AM Dan Sneddon dsneddon@redhat.com wrote:
The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub repo doesn't have the same level of CI that we have now on OpenStack Jenkins.
Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of.
If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly?
Thank you very much for any suggestions,
-Dan Sneddon
-- Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
I want to add to this that we also do maintain an ansible role [1], that performs network configuration of hosts using systemd-networkd. Role is tested against Ubuntu 20.04 and 22.04, CentOS Stream 9, Rocky 9 and Debian 11.
[1] https://opendev.org/openstack/ansible-role-systemd_networkd
ср, 7 июн. 2023 г. в 18:51, Jay Faulkner jay@gr-oss.io:
Hey Dan,
There are a couple other projects which are maintained, and might be able to take the role of os-net-config in your environment. Both of these are based on reading out information from a config drive and configuring a host:
Neither of these may fit your use case exactly, but they continue to exist and are supported, whereas right now (other than you) there's been no interest in keeping some of these tripleo deliverables alive.
Good luck, Jay Faulkner Ironic PTL
On Wed, Jun 7, 2023 at 7:46 AM Dan Sneddon dsneddon@redhat.com wrote:
The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub repo doesn't have the same level of CI that we have now on OpenStack Jenkins.
Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of.
If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly?
Thank you very much for any suggestions,
-Dan Sneddon
-- Dan Sneddon | Senior Principal Software Engineer dsneddon@redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter
participants (9)
-
Clark Boylan
-
Dan Sneddon
-
Dmitriy Rabotyagov
-
Dmitry Tantsur
-
Jay Faulkner
-
Jeremy Stanley
-
Julia Kreger
-
smooney＠redhat.com
-
Tony Breeds