openlmis-deployment

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OLMIS-5914 - Added installion Postgres extensions during RDS database setup using Terraform
OLMIS-5914 - Added installion Postgres extensions during RDS database setup using Terraform
There probably is a more robust way; I just did this as an incremental improvement.

There probably is a more robust way; I just did this as an incremental improvement.

This statement was necessary to go from 9.5.x to 9.6.x (https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion)...

This statement was necessary to go from 9.5.x to 9.6.x (https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion) It shouldn't upgrade to 10 or 11, since we specify engine version as 9.6.14. But if we did specify the engine version as 10 or 11, it might, based on the matrix in the link I posted. We do have PostGIS installed, so that would also affect what it gets upgraded to.

There may be a way to look up the group ID automatically? For instance the default_security_group_id attribute of aws_vpc?

There may be a way to look up the group ID automatically? For instance the default_security_group_id attribute of aws_vpc?

Will OpenLMIS work with the latest version of postgres? Will this cause us to go up to that latest version?

Will OpenLMIS work with the latest version of postgres? Will this cause us to go up to that latest version?

OLMIS-6425 Various provisioning and build changes
OLMIS-6425 Various provisioning and build changes
Thanks, I added the repo, and made a couple of comments.

Thanks, I added the repo, and made a couple of comments.

This stage is what I would prefer to be for the build jenkins job. Additionally, that way, if we wanted to deploy with a custom pg dump and eLMIS WAR file, we can do that instead of just using some...

This stage is what I would prefer to be for the build jenkins job. Additionally, that way, if we wanted to deploy with a custom pg dump and eLMIS WAR file, we can do that instead of just using something from the eLMIS git repo.

Can we change this so that we build the docker images in one jenkins job, and do the deployment in another jenkins job? Since it's not that important to see the latest eLMIS code when demonstrating...

Can we change this so that we build the docker images in one jenkins job, and do the deployment in another jenkins job? Since it's not that important to see the latest eLMIS code when demonstrating the pipeline, I would prefer to have a build process with a different cadence from the deployment process. This way, we're not also waiting for a whole eLMIS build when we redeploy the eLMIS server as well.

Since openlmis-deployment just has new files, here's what's different between the casper-elmis config and the casper v3 config: https://github.com/OpenLMIS/openlmis-deployment/compare/7600a6d...4a0...

Since openlmis-deployment just has new files, here's what's different between the casper-elmis config and the casper v3 config: https://github.com/OpenLMIS/openlmis-deployment/compare/7600a6d...4a0d226

And here's the diff for the casper-elmis repo: https://gitlab.com/openlmis/casper-elmis/compare/master...OLMIS-6425

OLMIS-6425 Create eLMIS deployment process for a Casper v2 demo server
OLMIS-6425 Create eLMIS deployment process for a Casper v2 demo server
The server is here: https://casper-elmis.a.openlmis.org Build & deployment config is here https://gitlab.com/openlmis/casper-elmis/tree/OLMIS-6425 (I don't think I have permissions to add a new re...

The server is here: https://casper-elmis.a.openlmis.org

Build & deployment config is here https://gitlab.com/openlmis/casper-elmis/tree/OLMIS-6425 (I don't think I have permissions to add a new repository)

Jenkins job is eLMIS-2.x-deploy-casper: currently running with eLMIS source branch `tanzania-elmis` (to get the casper demo data) and casper-elmis branch `OLMIS-6425` pending completion of this review and merge into master.

OLMIS-6413: Use orderable versioning in requisition line items
OLMIS-6413: Use orderable versioning in requisition line items
OLMIS-6351: Dropped reference to orderable version from FTAP
OLMIS-6351: Dropped reference to orderable version from FTAP
OLMIS-5549: Updated restart.sh to remove all containers and images
OLMIS-5549: Updated restart.sh to remove all containers and images