search

cloud-native-toolkit / automation-solutions

A collection of Bills of Materials that address solution/use-case scenarios.
https://cloud-native-toolkit.github.io/automation-solutions/
Apache License 2.0
3 stars 9 forks source link

Maximo BOMs should be collapsed into one #45

Open seansund opened 2 years ago

seansund commented 2 years ago

We shouldn't create different BOMs between AWS, Azure, and IBM Cloud just to change the values of the storage class variables. That goes against the whole point of the BOMs.

https://github.com/cloud-native-toolkit/iascable/issues/122 has been created to provide a mechanism within one BOM to define different default values. In the meantime we should have 1 BOM with the structural definition of the MAS core deployment. In the files folder we can provide different auto.tfvars files and can manually add them to the published terraform repo

tcskill commented 2 years ago

@seansund Can we wait on this one until we collect a little more usage / deployment data from the various platforms? Right now it’s storage, but I could see use cases from discussions so far where we may default azure or AWS deployments to a native service more often. Then we don’t have to recreate the boms again for the platform. @mjperrins

seansund commented 2 years ago

@tcskill I would rather keep it simple now and create a platform-specific BOM if/when there is differentiation in the structure of the BOM (not just the variables). For example, we will have an Azure BOM at some point that uses Azure-centric services (like SQL server instead of DB2) but that will come later

tcskill commented 2 years ago

@seansund agreed - after further review and discussions on client approaches let's create multi-platform then platform specific for use cases as required