Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Discussion on whether or not to backport OVN exporter 'locally' #22

Closed
Tracked by #23
, #24
...
fkr opened this issue Apr 11, 2022 · 3 comments
Closed
Tracked by #23
, #24
...

Discussion on whether or not to backport OVN exporter 'locally' #22

fkr opened this issue Apr 11, 2022 · 3 comments
Assignees
@fkr
Labels
Ops Issues or pull requests relevant for Team 3: Ops Tooling question Further information is requested

Comments

@fkr
Copy link
Member

fkr commented Apr 11, 2022

Once the OVN exporter has been merged upstream, we need to discuss on whether or not to backport it locally (for example, within OSIMS) to have it available, until it comes with the OpenStack release where it has been merged.

See: #21
@fkr fkr added question Further information is requested Ops Issues or pull requests relevant for Team 3: Ops Tooling labels Apr 11, 2022
@fkr fkr added this to the v4.0.0 milestone Apr 11, 2022
This was referenced Apr 11, 2022
Open
Open
@fkr
Copy link
Member Author

fkr commented Apr 14, 2022

  1. it must be merged upstream onto main
  2. only if upstream will not accept a backport, a local backport is adviseable
  3. is the feature a blocking requirement?
  4. is a local backport simple enough - if not this is a strong argument against a local backport

a) where do we document this decision? -> contributor guide (open issue)
b) present in weekly as well as scs-tech@

@fkr fkr self-assigned this Apr 14, 2022
@fkr fkr mentioned this issue Apr 14, 2022
Closed
fkr added a commit to SovereignCloudStack/standards that referenced this issue Apr 19, 2022
@fkr
document the backports policy
02de886 
Instead of the contributor guide, the Release-Policy document was chosen,
since there other (similar) items are being defined.
The backports policy was discussed in Team 3 meeting on April 14th as part
of the OVN exporter backport discussion:

SovereignCloudStack/issues#22

Addresses: #60

Signed-off-by: Felix Kronlage-Dammers <fkr@hazardous.org>
@fkr fkr mentioned this issue Apr 19, 2022
Merged
@fkr
Copy link
Member Author

fkr commented Apr 28, 2022

We will postpone the discussion of a local backport of the OVN exporter until #67 is done.

@garloff
Copy link
Member

garloff commented Aug 18, 2022

Plan is to not use a locally built image in production, but we can build images for development, test, ... purposes of course.

@fkr fkr modified the milestones: R3 (v4.0.0), R4 (v5.0.0) Oct 4, 2022
@tibeer tibeer mentioned this issue Mar 29, 2023
Closed
@fkr fkr removed this from the R4 (v5.0.0) milestone Apr 27, 2023
@fkr fkr closed this as completed Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fkr fkr

Labels
Ops Issues or pull requests relevant for Team 3: Ops Tooling question Further information is requested
Projects
Sovereign Cloud Stack
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fkr @garloff