702596 - rename balrog's "client" web portion to something different

Status: RESOLVED FIXED

(Release Engineering :: General, enhancement, P3)

Description

[[e-mail] (:bhearsum)]

Currently, the part of Balrog that Firefox and other applications talk to is called "client" (eg, auslib/client, client.wsgi, client.ini-dist). We've also started to talk about a "Balrog client" being a client to the administrative API. This is starting to get confusing; we should find a new name for the application facing part.

Comment 1

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

found in triage; not sure of urgency on this, so marking as p5 for now. bhearsum, is that ok, or you need it sooner?

Comment 2

[[e-mail] (:bhearsum)]

Going to try to get to this soon.

Comment 3

[[e-mail] (:bhearsum)]

I'm having trouble coming up with any better names for this. My best idea is to skirt the issue and do the following
- Move the existing 'web' directory to 'admin'.
- Move the existing 'client' directory to 'web'.
- Rename client.wsgi/client.ini-dist to balrog.wsgi/balrog.ini-dist.

Anyone have strong feelings about that either way?

Comment 4

[[e-mail] (:bhearsum)]

Attachment: do the renaming from comment #3

Passes unit tests and I ran both apps against a database dump locally. I also found a bug in auslib/admin/base.py where 'log' wasn't set, so I fixed that.

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 630641 [details] [diff] [review]
do the renaming from comment #3

Looks fine to me.

Comment 6

[[e-mail] (:bhearsum)]

Comment on attachment 630641 [details] [diff] [review]
do the renaming from comment #3

https://jenkins.mozilla.org/job/Balrog/93/

Comment 7

[[e-mail] (:bhearsum)]

Landed cleanly, and relatively in sync with the IT changes from bug 763874.