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.

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

R24.03 Managed Service Orchestrator - Release Checks #493

Closed
20 tasks done
kelaja opened this issue Jan 30, 2024 · 32 comments
Closed
20 tasks done

R24.03 Managed Service Orchestrator - Release Checks #493

kelaja opened this issue Jan 30, 2024 · 32 comments
Assignees
Labels
compliance RM compliance documentation RM documentation managed service orchestrator Feature/Bug for Managed Service Orchestrator component
Milestone

Comments

@kelaja
Copy link
Contributor

kelaja commented Jan 30, 2024

Release Info

Please provide information on what you want to be included in the Eclipse Tractus-X release.
If you are not owner of this issue, please provide the information as comment to the issue.

Version to be included in Eclipse Tractus-X release: version placeholder

Leading product repository: repository link

Compliance Verifications

This issue tracks all compliance related checks, that need to be performed for a product release in Eclipse Tractus-X.

  • Gaia-X compliance confirmed
  • GDPR compliance confirmed (personal data, data protection + privacy DPP)
  • Interoperability checks performed
  • Data Sovereignty checks performed
  • Compliant with relevant published CX Standards (see the Catena-X standard library)

Documentation

  • Arc24 documentation up-to-date
  • Administrators Guide up-to-date
  • End-User manual up-to-date
  • Interface documentation up-to-date

Security Checks

  • Thread Modelling Analysis passed
  • Static Application Security Testing (SAST) scans passed
  • Dynamic Application Security Testing (DAST) tests passed
  • Secret Scans passed
  • Software Composition Analysis (SCA) passed
  • Container Scans passed
  • Infrastructure as Code (IaC) scans passed

General Checks

Test Results

  • E2E Integration Test passed
  • User Journey approved

Helpful Links

@kelaja kelaja added documentation RM documentation compliance RM compliance managed service orchestrator Feature/Bug for Managed Service Orchestrator component labels Jan 30, 2024
@kelaja kelaja added this to the 24.03 milestone Jan 30, 2024
@ciprianherciu
Copy link

Compliance Verifications
Data Sovereignty: There are no changes from last release regarding the data Sovereignty for managed service Orchestrator.
Approval of Standards: There is no changes since R3.2. Managed Service Orchastror does not define any standard. It is only using the existing standard. The tests show that we are compatible with the current standards.
GPDR and Gaia-X: there are no changes regarding GPDR and Gaia-X
Data Interoperability check: Not applicable

Test Results
Internal Integration tests: A1IDSES-1536
Managed Service Orchestrator - Integration Testing with Portal: A1IDSES-1534

@sharathshivprasad
Copy link

Security Checks

Threat modelling Document:
https://confluence.catena-x.net/display/cxsecurity/Security+Assessment+-+Auto+Setup+API
Static Application Security Testing (SAST): Latest Veracode report: https://analysiscenter.veracode.com/auth/index.jsp#ViewReportsResultSummary:47240:1550110:33047817:33017393:33033043:4910813
DetailedReport_DFT_AutoSetup_18_Feb_2024.pdf

Dynamic Application Security Testing: Latest Invicti report : https://www.netsparkercloud.com/scans/report/a47fc6c147074d7e1dedb11b01aaf696/
Secret scanning and SCA: Latest veracode report uploaded above, please check git guardian from your side and approve.
Container Scan conducted: Latest Trivy Scan Report: https://github.com/eclipse-tractusx/managed-service-orchestrator/actions/workflows/trivy.yml
Infrastructure as Code: Latest KICS report: https://github.com/eclipse-tractusx/managed-service-orchestrator/actions/workflows/kics.yml

@galyshann
Copy link

@RoKrish14
Security scans looks good from our side (check previous comment),
Could you please review and approve?

@DnlZF
Copy link

DnlZF commented Feb 20, 2024

Secret Scans: Approved

@szymonkowalczykzf
Copy link

Security Assessment Process (Threat Modeling Analysis) approved.

No significant changes detected since last release.
No open critical & high finding remaining for this release.

Documentation of the assessment will be moved out to the GitHub repositories of the Products before the next release.

@ciprianherciu
Copy link

ciprianherciu commented Feb 21, 2024

@vialkoje Please approve the Data Sovereignty and documentation

@ciprianherciu
Copy link

ciprianherciu commented Feb 21, 2024

@HiHenrik please approve interoperability.
Last time it was agreed with @RolaH1t we do not need the interoperability check:
#81

@ciprianherciu
Copy link

@RoKrish14 please approve the security Checks

@RoKrish14
Copy link

SAST: Approved
SCA: Approved
DAST: Approved
IAC: Approved

Pending-
Container scans

@RolaH1t
Copy link
Contributor

RolaH1t commented Feb 21, 2024

QG review comments:
InterOP ok; StyleGuide not applicable
@DirkBTSI pls confirm E2E test approval
additional completed items will be documented by @RolaH1t 21-Feb

@ciprianherciu
Copy link

For User Journey, no changes from last releases

@DirkBTSI
Copy link

INT test performed/documented.
E2E test performed/documented.
No high defect.
TM approved
@kelaja : please approve for "E2E Integration Test passed"

@RoKrish14
Copy link

SAST: Approved
SCA: Approved
DAST: Approved
Container scan: Approved
IAC: Approved

@ciprianherciu
Copy link

ciprianherciu commented Feb 22, 2024

@RolaH1t Container scans are passed.
Open Topics:

  • - Documentation
  • - Data Sov
  • - Tractus-X Release Guidelines

@SebastianBezold SebastianBezold self-assigned this Feb 23, 2024
@SebastianBezold
Copy link
Contributor

HI @ciprianherciu,

just to make sure: i did not find any version information in this issue. Are you planning to use the latest release in your repo to be included in the Tractus-X release? This would be 1.5.3 as App and Chart version. If this is the correct one, I would ask you @kelaja to add that to the initial issue description

@ciprianherciu
Copy link

@SebastianBezold yes, the version 1.5.3 should be reviewed

@ciprianherciu
Copy link

@vialkoje Please approve the Data Sovereignty and documentation

@SebastianBezold
Copy link
Contributor

Hi @ciprianherciu,

the TRG checks are done, but there was one issue already open, asking for better guidance on installation and quick-start.
See eclipse-tractusx/managed-service-orchestrator#98
I think "outside" feedback is better than what I could ever provide on this topic, so I think it's highly valuable and would ask your team to address that, before I set the TRG checks to closed

@vialkoje
Copy link

Links for documentation are defective and do not work ! Please correct and make sure you provide appropriate links everywhere pointing to documentations.

Nevertheless the Documents exist after trying to find them manually. content is looking appropriate - Expert approval granted.

Requirements for data sovereignty unchanged. Expert approval granted.
please consider the data sovereignty QG-requirements for 24.05.

@ciprianherciu
Copy link

Hi @SebastianBezold,
the PR in regards with the installation guide and quick-start is open.
In order to be able to close the QG ticket, could You please review it and let us know if there is something else that we need to do?

Thank You,
Best regards,
Ciprian Herciu

@SebastianBezold
Copy link
Contributor

Hi @ciprianherciu,

since the missing install docs was actually mentioned by someone else, I would wait for feedback, if the new instructions do help. Otherwise I would leave it to release management @kelaja and @RolaH1t, if we will close the QG and work on this docs later on

@ciprianherciu
Copy link

Hi @SebastianBezold @kelaja @RolaH1t ,
In order to close the QG 4 for MSO, we need the TRG to be approved.
In Order to get it approved, the condition was to update the installation guide and the quick start as requested here: eclipse-tractusx/managed-service-orchestrator#98.

The updates were made, we have added a comment to @awellnitz-materna, to get it approved but no answer yet.

Since the QG is almost at the end, please let us know how can we get this ticket approved.

Thank You,
Ciprian Herciu

@SebastianBezold
Copy link
Contributor

Installation guide has been improved further, so the last open release guideline issue has been resolved.

@ciprianherciu
Copy link

@kelaja and @RolaH1t TRG approved. QG Ticket can be closed

@RolaH1t
Copy link
Contributor

RolaH1t commented Mar 5, 2024

Congrats: all pre-conditions now fulfilled.
QG approval granted!

@Siegfriedk
Copy link
Contributor

@ciprianherciu i can't find the helm chart for 1.5.3/1.5.3 only 1.5.3/1.5.2:

tractusx-dev/managed-service-orchestrator 1.5.3 1.5.2

I also would like to highlight the postgresql issue: its 14 and not 15

@RolaH1t FYI

@RolaH1t
Copy link
Contributor

RolaH1t commented Mar 8, 2024

final conclusion: TRG 5.07 violated (postgresql DB version 14.x) but successfully tested.
this is covered in overall release note 24.03
QG closed with these conditions.

@Siegfriedk
Copy link
Contributor

@RolaH1t i'm still missing the helm chart version
@ciprianherciu !

@ciprianherciu
Copy link

@Siegfriedk
The release version for 1.5.3 can be found here:

The changes which were done in regards with the documentation were release in the version 1.5.4 yesterday and this version will be deployed for 24.03

@Siegfriedk
Copy link
Contributor

@ciprianherciu is it now 1.5.3 or 1.5.4?

I do see a helm chart with 1.5.4/1.5.4 ich kan reference that one

@ciprianherciu
Copy link

@Siegfriedk it is 1.5.4 since it was requested to change a documentation in order to get the TRG approval.

Please reference that

@kelaja kelaja moved this from Inbox to Done in Release Planning Mar 13, 2024
@kelaja kelaja closed this as completed Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compliance RM compliance documentation RM documentation managed service orchestrator Feature/Bug for Managed Service Orchestrator component
Projects
Status: Done
Development

No branches or pull requests