Hi all,
we are considering using sg-core in our stack, and I am trying to understand which is the more 'authoritative' source - this repo here, or the infrawatch/sg-core ?
From what I gather, this repo here was forked somewhere around late 2024 from infrawatch, and they already diverged, use rather different release cadence and even versioned tags.
openstack-k8s-operators/sg-core - has put more effort into devstack plugin, has some patches for ceilo-specific metadata handling, and AFAICT OpenStack upstream testing uses this one everywhere sg-core is used.infrawatch/sg-core - had more effort on code coverage, testing and golang updates, and also has some non-testing-related patches that are missing from openstack-k8s-operators but look quite useful.
I also see same people keep contributing to both projects still, so what's the difference?
Should all non-trivial/non-ci patches be also ported here from infrawatch repo?
Hi all,
we are considering using sg-core in our stack, and I am trying to understand which is the more 'authoritative' source - this repo here, or the
infrawatch/sg-core?From what I gather, this repo here was forked somewhere around late 2024 from infrawatch, and they already diverged, use rather different release cadence and even versioned tags.
openstack-k8s-operators/sg-core- has put more effort into devstack plugin, has some patches for ceilo-specific metadata handling, and AFAICT OpenStack upstream testing uses this one everywhere sg-core is used.infrawatch/sg-core- had more effort on code coverage, testing and golang updates, and also has some non-testing-related patches that are missing from openstack-k8s-operators but look quite useful.I also see same people keep contributing to both projects still, so what's the difference?
Should all non-trivial/non-ci patches be also ported here from infrawatch repo?