Status

P1
normal
RESOLVED WONTFIX
4 years ago
3 years ago

People

(Reporter: yousef, Assigned: yousef)

Tracking

Details

(Whiteboard: Up and functional. Need to move media to own server.)

A new server will need to be put up for badg.us, I have the db dump for it.
(Assignee)

Updated

4 years ago
Blocks: 1039722
(Assignee)

Updated

4 years ago
Assignee: nobody → jan

Updated

4 years ago
Priority: -- → P1

Updated

4 years ago
Due Date: 2014-07-24
Jan and myself have got the server running but there's two issues to far:

ewong, where were the uploads stored on the original server? If they were stored in an Object store on HP then we may be able to retrieve them otherwise I think they're gone.

The other issue is that logging in via persona leads the brower to constantly refresh. ewong, if you came across it, did you find a solution?

Moving forwards, the app server will need to be put behind nginx and I will ensure uploads are served through S3 which will have scheduled backups enabled.
Flags: needinfo?(ewong)
One more thing before I forget, did the original site use SSL? That would need to be re-issued also.

Comment 3

4 years ago
(In reply to Yousef Alam [:yalam96] from comment #1)
> Jan and myself have got the server running but there's two issues to far:
> 
> ewong, where were the uploads stored on the original server? If they were
> stored in an Object store on HP then we may be able to retrieve them
> otherwise I think they're gone.
> 
If you're talking about the images, they were stored on the server itself,
unfortunately.

> The other issue is that logging in via persona leads the brower to
> constantly refresh. ewong, if you came across it, did you find a solution?
> 
No, I don't recall encountering that problem.
Flags: needinfo?(ewong)

Comment 4

4 years ago
(In reply to Yousef Alam [:yalam96] from comment #2)
> One more thing before I forget, did the original site use SSL? That would
> need to be re-issued also.

No.
Server is up at http://54.88.56.79/ but I'm still running into issues with persona causing the page to refresh.

Updated

4 years ago
Blocks: 1044491

Comment 6

4 years ago
(In reply to Yousef Alam [:yalam96] from comment #5)
> Server is up at http://54.88.56.79/ but I'm still running into issues with
> persona causing the page to refresh.

I'm getting a 502 for that URL. What is the status on this?
Flags: needinfo?(yousef)
I haven't done anything on it in a while, I spent a couple of hours trying to get persona to work with no luck.
Flags: needinfo?(yousef)

Comment 8

4 years ago
As an update, I was able to resolve the Persona issue by fixing a config settings for not having SSL, so it's up and running again at the IP above (54.88.56.79).

Edmund, could you please see if this looks good to you? Can we point badg.us to this?
Flags: needinfo?(ewong)

Comment 9

4 years ago
(In reply to Logan Rosen [:Logan] from comment #8)
> As an update, I was able to resolve the Persona issue by fixing a config
> settings for not having SSL, so it's up and running again at the IP above
> (54.88.56.79).
> 
> Edmund, could you please see if this looks good to you? Can we point badg.us
> to this?

Heck yeah!  Awesome job dudes!
Flags: needinfo?(ewong)
This needs to be moved into the new VPC, then it should be ready.
Assignee: jan → yousef
(Assignee)

Updated

4 years ago
Depends on: 1062502
(Assignee)

Updated

4 years ago
Depends on: 1062509
Things that need to be done:

- Set up the NFS share from bug 1062509 so that all media is stored on it
- Move the db to the RDS instance inside our VPC (bug 1062502)
- Set up the auto-scaling group
- Point the domain name to the lb
Tagging for team discussion. Need to formulate a plan to address.
Whiteboard: [DISCUSS]
Yousef - it seems the site is up, was this fixed or is it just by chance that it is working right now?
Flags: needinfo?(yousef)
Need:

* documentation wiki
* runbook (how to fix common issues when it breaks)
* Pingdom monitoring
* Dashboard integration

@yalam - when do you think you can wrap that up?
Whiteboard: [DISCUSS]
It's up to the same level as before, but media would still be stored on the same server which is what lead to the loss of the data from before. I'd like to get it using S3 or similar before calling it production-ready.
Flags: needinfo?(yousef)
Whiteboard: [Discuss] Up and functional. Need to move media to own server.
Depends on: 1088136
Whiteboard: [Discuss] Up and functional. Need to move media to own server. → Up and functional. Need to move media to own server.
(In reply to Edmund Wong (:ewong) from comment #9)
> (In reply to Logan Rosen [:Logan] from comment #8)
> > As an update, I was able to resolve the Persona issue by fixing a config
> > settings for not having SSL, so it's up and running again at the IP above
> > (54.88.56.79).
> > 
> > Edmund, could you please see if this looks good to you? Can we point badg.us
> > to this?
> 
> Heck yeah!  Awesome job dudes!

I tried to connect to bad.us using my persona account (same address as bugzilla) and I get the constant refresh bug...
Are you sure this is fixed? I got the same issue a while ago with mozilians.org (bug 908342), maybe linked to the mixed case address bug.

Updated

4 years ago
Whiteboard: Up and functional. Need to move media to own server. → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2505] Up and functional. Need to move media to own server.
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2505] Up and functional. Need to move media to own server. → Up and functional. Need to move media to own server.
We have a potential new contributor who has experience with django apps, I'll see if he can help us with this.
Fixed the constant refreshing bug again.
Given that we're sunsetting badg.us, I think it's safe to close this.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.