Skip to content

Commit

Permalink
Update docs. (Netflix#186)
Browse files Browse the repository at this point in the history
* Replace Wasabi with ATC in docs.

* Update dev.md

replace wasabi with atc in dev handbook
  • Loading branch information
bgres authored and GitHub Enterprise committed May 10, 2021
1 parent 0ddcced commit 11cbd16
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion docs/dev.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ If you didn't have python 3.7, you might need the `libffi(-dev)` package before
Clone the repository and initialize the submodule `public-lemur` which points
to the [public fork of Netflix/lemur in our Github spotify org](https://github.com/spotify/lemur):
```bash
git clone [email protected]:wasabi/spotify-lemur.git
git clone [email protected]:atc/spotify-lemur.git
cd spotify-lemur
git submodule update --init --recursive
```
Expand Down
10 changes: 5 additions & 5 deletions docs/ops.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@

* public upstream [Netflix/lemur](https://github.com/Netflix/lemur/)
* public fork [spotify/lemur](https://github.com/spotify/lemur/) (pulled in as submodule in internal lemur-frontend and spotify-lemur)
* internal [lemur-frontend](https://ghe.spotify.net/wasabi/lemur-frontend/) (static frontend code, used as base-image for spotify-lemur)
* internal [spotify-lemur](https://ghe.spotify.net/wasabi/spotify-lemur/) (main internal repository, including build pipeline, GKE deployment definitions and docs) 📍 you are here
* internal [spotify-lemur-redis](https://ghe.spotify.net/wasabi/spotify-lemur-redis/) (plain redis instance for celery)
* internal [lemur-frontend](https://ghe.spotify.net/atc/lemur-frontend/) (static frontend code, used as base-image for spotify-lemur)
* internal [spotify-lemur](https://ghe.spotify.net/atc/spotify-lemur/) (main internal repository, including build pipeline, GKE deployment definitions and docs) 📍 you are here
* internal [spotify-lemur-redis](https://ghe.spotify.net/atc/spotify-lemur-redis/) (plain redis instance for celery)

## Architecture and components

Expand Down Expand Up @@ -90,13 +90,13 @@ Note that the `domains` table might still have entries with the domains the cert

## Celery Tasks

The [Celery Beat schedule is defined in lemur.conf.py](https://ghe.spotify.net/wasabi/spotify-lemur/blob/master/lemur.conf.py#L221).
The [Celery Beat schedule is defined in lemur.conf.py](https://ghe.spotify.net/atc/spotify-lemur/blob/master/lemur.conf.py#L221).

Tasks can be inpsected with celery-flower on https://certs.spotify.net/celery-flower.

### Manually triggering a celery task

1. Use `kubectx` to make sure you're in the `gke_gke-xpn-1_europe-west1_europe-west1-j1b3` context.
1. Run `kubectl config use-context gke_gke-xpn-1_europe-west1_europe-west1-j1b3` to switch to the correct context.
1. Run `kubectl get pods --namespace cert-management` to find out the name of the currently running celery beat pod name.
1. Run `kubectl exec $LEMUR_CELERY_BEAT_POD_NAME celery -- celery -A lemur.common.celery call lemur.common.celery.$TASK_NAME` to run the task $TASK_NAME, so for example `kubectl exec lemur-celery-beat-7cc6d47c4f-qqbkh celery -- celery -A lemur.common.celery call lemur.common.celery.fetch_all_pending_certs`

Expand Down

0 comments on commit 11cbd16

Please sign in to comment.