Skip to content

Commit

Permalink
DEVO-174 master to main
Browse files Browse the repository at this point in the history
- Updates references to master in README and circleci config files
  • Loading branch information
sensei100 committed Jul 1, 2020
1 parent ace8cfc commit 468f3c1
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .circleci/setup_solr.sh
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
#!/usr/bin/env bash
set -e
cd ..
git clone --single-branch --branch master [email protected]:tulibraries/ansible-playbook-solrcloud.git
git clone --single-branch --branch main [email protected]:tulibraries/ansible-playbook-solrcloud.git
mkdir -p ansible-playbook-solrcloud/data/tmp/collections
cp -r ~/project ansible-playbook-solrcloud/data/tmp/collections/tul_cob-az
cd ansible-playbook-solrcloud
Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,18 +47,18 @@ $ curl "http://localhost:8090/solr/admin/collections?action=CREATEALIAS&name=tul

## SolrCloud Deployment

All PRs merged into the `master` branch are _not_ deployed anywhere. Only releases are deployed.
All PRs merged into the `main` branch are _not_ deployed anywhere. Only releases are deployed.

### Production

Once the master branch has been adequately tested and reviewed, a release is cut. Upon creating the release tag (generally just an integer), the following occurs:
Once the main branch has been adequately tested and reviewed, a release is cut. Upon creating the release tag (generally just an integer), the following occurs:
1. new ConfigSet of `tul_cob-az-{release-tag}` is created in [Production SolrCloud](https://solrcloud.tul-infra.page);
2. new Collection of `tul_cob-az-{release-tag}-init` is created in [Production SolrCloud](https://solrcloud.tul-infra.page) w/the requisite ConfigSet (this Collection is largely ignored);
3. a new QA alias of `tul_cob-az-{release-tag}-qa` is created in [Production SolrCloud](https://solrcloud.tul-infra.page), pointing to the init Collection;
3. a new Stage alias of `tul_cob-az-{release-tag}-stage` is created in [Production SolrCloud](https://solrcloud.tul-infra.page), pointing to the init Collection;
3. a new Production alias of `tul_cob-az-{release-tag}-prod` is created in [Production SolrCloud](https://solrcloud.tul-infra.page), pointing to the init Collection;
4. and, manually, a full reindex DAG is kicked off from Airflow Production to this new tul_cob-az alias. Upon completion of the reindex, relevant clients are redeployed pointing at their new alias, and *then QA & UAT review occur*.

See the process outlined here: https://github.com/tulibraries/grittyOps/blob/master/services/solrcloud.md
See the process outlined here: https://github.com/tulibraries/docs/blob/main/services/solrcloud.md

After some time (1-4 days, as needed), the older tul_cob-az collections are manually removed from Prod SolrCloud.

0 comments on commit 468f3c1

Please sign in to comment.