Discussed the need to provide separate isolated accounts for each building block provider to address their requests for additional resources and ensure the security and stability of the system. The Sandbox team emphasized that this approach was chosen to address the requests for additional resources and to avoid conflicts and complexities in a shared environment.
Need to restrict resource usage and strive for a lighter version of building blocks to reduce costs due to the budgetary constraints and the importance of finding a balance between resource requirements and cost-efficiency.
The GovStack architecture specification emphasized the need to containerize everything being deployed. This requirement was highlighted as a necessary aspect of the building blocks' deployment and was not expected to change. There is thus the requirement to containerize everything and find ways to strive for the lightest version of the building blocks to minimize expenses.
Discussed the challenges and conflicts of interests that arise when multiple building block providers share a common environment. It was recognized that having separate environments for each provider would reduce complexity and improve the management and monitoring of resources.
Concerns around estimating the space and resource requirements for each building block provider. Discussed the importance of having an approximate estimate to plan for future needs and understand the potential impact on costs and efforts.
Circle CI as the preferred CI/CD pipeline for deploying container images and helm charts. The sandbox team mentioned the availability of examples and resources related to Circle CI pipeline and emphasized the need to adhere to the agreed-upon approach.
Discussed whether the isolated instances would affect testing and interworking between building blocks. Initially, the testing and integration would occur within the separate environments, and once validated, the setup would be transferred to the sandbox environment for further interoperability testing.
It was impressed upon the Sandbox (Gofore) team about the need to stabilize the deployment approach and ensure the long-term viability of the system. The decision to provide separate environments for building block providers was seen as a step toward finding a sustainable solution and reducing complexity.
Highlighted the need to consider both financial and technical implications of the proposed changes to the Sandbox deployment strategy. The cost implications of providing separate environments were discussed, and it was acknowledged that there might be an increase in hosting costs.
Emphasized the importance of communicating these implications to the technical committee and addressing any concerns.
The time required to set up the new environments for building block providers - it was estimated that it would take at least a few days, with a potential completion date by the end of the week.