Open RafyMehany opened 5 months ago
matthewrossi
commented
5 months ago Today I watched the recording of the platform integration call, and there I have seen used the concept of components and sub-component. So, just to make sure I am understanding the requirements to meet Milestone 5.7, with "neighbor services" are we referring to the sub-components of a component, other components, or both?
RafyMehany
commented
5 months ago Dear Mathew,
If your component is sufficiently large, it can be divided into sub-components. Essentially, these sub-components are parts of your original component, allowing you to break them down into more manageable pieces to carry out your tasks effectively.
Neighboring services refer to the services or components that your component will interact with. When your component is deployed in the cluster, it's crucial to ensure it functions correctly through smoke tests. Subsequently, you conduct tests on neighboring services to validate that your component can seamlessly integrate with its dependencies.
If you have further questions, please reach out to us. Thanks in advance
Rafy Mehany HIRO-MicroDataCenters
From: Matthew Rossi @.> Sent: Friday, April 19, 2024 4:40 PM To: glaciation-heu/IceStream @.> Cc: Rafy Benjamin @.>; Author @.> Subject: Re: [glaciation-heu/IceStream] [Policy Decision Point (PDP)] Component Neighbor Integration tests (Issue #175)
Today I watched the recording of the platform integration call, and there I have seen used the concept of components and sub-component. So, just to make sure I am understanding the requirements to meet Milestone 5.7, with "neighbor services" are we referring to the sub-components of a component, other components, or both?
— Reply to this email directly, view it on GitHubhttps://github.com/glaciation-heu/IceStream/issues/175#issuecomment-2066725911, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFLD6L6ASARTRLY7J2EEUKLY6EUE5AVCNFSM6AAAAABGLJUSUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRWG4ZDKOJRGE. You are receiving this because you authored the thread.Message ID: @.***>
Task
Specify and run neighbor integration tests for your deployed service/component, ensuring compatibility and smooth operation alongside neighboring services. The goal is to make sure that your service is compatible with the services it interacts with.
1- Neighbor Service Testing Specification
Test Specification: Specify tests to verify the interaction and compatibility of your service with neighboring services. To accomplish this task effectively, it's crucial to establish communication channels with your neighbors and gain insights into their service functionalities and dependencies.
2- Document Neighbor Service Tests
Update Documentation: Update your documentation to include neighbor service tests, facilitating reference for both yourself and your neighbors. Later, when automation is implemented, these tests will be documented to save time and ensure consistency. Example: API calls or simulated interactions to ensure seamless integration with neighbor services.
3- Run neighbor Tests
Run your neighbor integration tests on the integration cluster to make sure that the service is working as expected and can integrate with the neighboring services.
Example:
4- Integration with Deployment Workflow (Optional for Now):
Integration with Deployment Workflow: Integrate neighbor service testing into the deployment workflow to automate the process, ensuring continuous compatibility and smooth operation with neighboring services. You can explore tools like Argo Rollouts for streamlined integration for more information check this docs.
Acceptance Criteria:
Note: