This commit is contained in:
Correl Roush 2021-09-28 13:23:48 -04:00
parent 54a9cc5d6a
commit 9bf93596e7
10 changed files with 124 additions and 7 deletions

View file

@ -2,6 +2,9 @@
:ID: 9cfd85fd-998e-4f21-b82e-c7963576c202
:END:
#+title: Deploying S4 to Kubernetes
Tasks for deploying [[id:c7322400-c6e6-4595-87e2-7db6e57b6a2b][S4]] to Kubernetes.
* DONE Deploying the service
* Migrating the Redis database
* Deploying the workers

View file

@ -2,3 +2,18 @@
:ID: 6413d680-ee2e-43e6-b7c7-10f14e0873c2
:END:
#+title: Deploying Bulk Tagging to Kubernetes
#+filetags: project
* DONE Deploy to kubernetes in production
* Update services to use the new consul hostname
** DONE Subscriber Proxy
Configured in consul
** DONE Bulk Tagging Consumers
Configured in consul
** TODO AWSubscribers
https://gitlab.aweber.io/CP/Services/awsubscribers
** TODO Bulk Tagging Acceptance Tests
[[https://gitlab.aweber.io/CP/automation/bulk-tagging-acceptance/]]
** TODO QA Regression Tests
- https://gitlab.aweber.io/BoFs/QA/QAWeber

View file

@ -33,13 +33,6 @@ Added: [2019-08-06 Tue 10:34]
- Distinct from a materialized search-optimized db
- Deal with =subscriber_tags= table bloat in AppDB
#+end_quote
* Concerns
** Performance
** Fitness to Purpose
This service will need to fulfill the needs of both end-user subscriber searches
and segment emailing.
* Interim Solution
** Component Diagram
#+BEGIN_SRC plantuml :file search-components.svg
database Analytics {
@ -67,6 +60,44 @@ and segment emailing.
#+RESULTS:
[[file:search-components.svg]]
* Concerns
** Performance
** Fitness to Purpose
This service will need to fulfill the needs of both end-user subscriber searches
and segment emailing.
* Plan
** Search Centralization
*** Expose search inputs backed with the existing database
- Include IDs required to build existing POST format
*** Enable dblink on the search master database
[[jira:CCPANEL-7147][CCPANEL-7147]]
*** Create new unlogged search results table
https://jira.aweber.io/browse/CCPANEL-7077
*** Define the search result format
https://xd.adobe.com/view/ae8fb2b2-c039-4e88-8ade-ff2562a8c8cf-fbdc/screen/c03f09c7-187e-4a6f-8b8c-571d131daee1/ (ignore engagement column)
- name
- email
- source
- status
- date added
- last updated
*** Perform search using new search DSL
*** Perform search using legacy segment ID
- Include flags for broadcast segment-required filtering?
*** Manage segments using the existing database
- Translate a DSL search into a legacy stored segment
** Migrate to an updated schema
** Migrate to new search service
*** Create new subscriber management React application
*** Update broadcast-segment to use new search service
** Milestone 3: Add new search features
* Resources
- [[https://confluence.aweber.io/display/AR/PostgreSQL+Backed+Search][PostgreSQL Backed Search]] (Rejected ACP)
- [[https://confluence.aweber.io/display/AR/Search+Proxy+Service][Search Proxy Service]]

View file

@ -0,0 +1,5 @@
:PROPERTIES:
:ID: c7322400-c6e6-4595-87e2-7db6e57b6a2b
:ROAM_ALIASES: S4
:END:
#+title: Suspicious Submission Spam Service

View file

@ -0,0 +1,4 @@
:PROPERTIES:
:ID: 321075e7-db53-4676-b785-7c77ed9d1150
:END:
#+title: Bulk Tagging Service

View file

@ -0,0 +1,4 @@
:PROPERTIES:
:ID: 0d24c57a-fd56-43b0-8209-497320bf79f7
:END:
#+title: Dashboard

14
daily/2021-09-20.org Normal file
View file

@ -0,0 +1,14 @@
:PROPERTIES:
:ID: dbc56c34-1081-493a-9700-284542312a7f
:END:
#+title: 2021-09-20
* Ops Workshop
** Discussing remaining Chef VMs
https://docs.google.com/spreadsheets/d/1k3WK5OqqGgEPeVaFb9uJhjomLoI76ufYfQeDN-zfA-c/edit#gid=0
- [ ] Removing [[id:c7322400-c6e6-4595-87e2-7db6e57b6a2b][Suspicious Submission Spam Service]] nodes
- [ ] Removing Search Proxy nodes (last activity on <2021-07-15 Thu>)
- [ ] Removing Subscriber Proxy nodes (last activity on <2021-05-21 Fri>)
- [ ] Removing Tagging Proxy nodes (last activity on <2021-09-10 Fri>)
- [ ] Removing Search Recipient Service nodes
- [ ] Removing Segment Recipient Service nodes

16
daily/2021-09-21.org Normal file
View file

@ -0,0 +1,16 @@
:PROPERTIES:
:ID: d7651d76-1ec6-48ea-a621-15b7fcc405b1
:END:
y:PROPERTIES:
:ID: 8ee0cd4e-32f0-467a-8bb3-44ef5b5fc0a0
:END:
#+title: 2021-09-21
* Tech Initiatives Sync-Up
- [X] Fix [[id:c7322400-c6e6-4595-87e2-7db6e57b6a2b][S4]] metrics failing to publish
- [ ] Update [[id:c7322400-c6e6-4595-87e2-7db6e57b6a2b][S4]] Dashboard
- [ ] Fix [[id:321075e7-db53-4676-b785-7c77ed9d1150][Bulk Tagging Service]] metrics failing to publish
- [ ] Update [[id:321075e7-db53-4676-b785-7c77ed9d1150][Bulk Tagging Service]] Dashboard
- [ ] Updating [[id:321075e7-db53-4676-b785-7c77ed9d1150][Bulk Tagging Service]] client hostnames
+ [ ] AWSubscribers
- [ ] Decommission [[id:c7322400-c6e6-4595-87e2-7db6e57b6a2b][S4]] VM nodes

20
daily/2021-09-24.org Normal file
View file

@ -0,0 +1,20 @@
:PROPERTIES:
:ID: c47f2faa-09f9-4307-8a5b-5a130ecacb76
:END:
#+title: 2021-09-24
* Reviewing dashboard prototype
https://xd.adobe.com/view/d5897e51-82ed-4a17-9d7e-57412a391c03-80da/
A discussion about potential future updates to the [[id:57ee2f00-9bcd-4e0f-8a77-ae1f2d4cda89][Control Panel]] [[id:0d24c57a-fd56-43b0-8209-497320bf79f7][Dashboard]].
There is a desire to display the most recent subscribers added. I don't believe
we have a way to fetch those from our current public APIs, but the planned
[[id:11edd6c9-b976-403b-a419-b5542ddedaae][Subscriber Search Service]] should provide that functionality once it's ready.
How would we define subscriber engagement?
Recent sales would have to be provided by the [[id:3ddc4e32-932f-4748-bfe9-7025d4d6b352][Report API Controller]] or the
future [[id:c45881de-46f2-4f76-9579-063626c5956c][Analytics View Service]].
Recent edits?

5
daily/2021-09-27.org Normal file
View file

@ -0,0 +1,5 @@
:PROPERTIES:
:ID: d1d47a85-ce22-4e31-ac33-83600d833c6e
:END:
#+title: 2021-09-27
* Calling about the new apartment lease