461393 - New website, Community Store

Status: VERIFIED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[matthew zeier [:mrz]]

tracking bug for deployment

Comment 1

[Alex Buchanan [:abuchanan]]

created SVN spot at

https://svn.mozilla.org/projects/community_store

Comment 2

[Mark Smith [:xb95]]

Staged the code on mrapp-stage02.

Deployment is going to require a shared NFS mount.  Alex, can you estimate how much space the site is going to need?  On the order of megabytes, hundreds of megabytes, gigabytes, more?

Comment 3

[matthew zeier [:mrz]]

Switching IT lead to Aravind.  Mark, please get Aravind up to speed.

Comment 4

[Aravind Gottipati [:aravind]]

Please re-open when this is actually ready to go to production.

Comment 5

[Ryan Doherty (:rdoherty)]

Re-opening as we are launching 12/2 and need to put together a plan.

The most significant issue is we have to pre-seed the database with designs. We can do this 2 ways:

1) Upload them on stage and copy the database over to production. We will also have to copy over the /uploads directory with the uploaded images. This will also mean no more dumping/reloading the database. We don't forsee any database changes before launch, so this is not a large issue.

2) Setup the production site early behind LDAP and we can upload the images ahead of time before we launch. We would need the site up by the 24th to give us a few days to upload, edit and verify the designs.

Comment 6

[Tara (musingt)]

Hi guys.  Sorry for the late chime-in.  All the images are zipped up and ready to go. Just let me know when you need them.  

I prefer #2 simply because it seems to allow a bit more flexibility in terms of editing the image pool if need be.  But I'll let you guys decide which option works best from your end.

Comment 7

[Aravind Gottipati [:aravind]]

I think the first option is the way to go, since that's the whole point of having a staging server - that we stage it there and make sure its ready to be pushed to production.

However, if you guys strongly prefer option 2, I need more time than the 24'th to set it up.

Also, from the staging environment, the site had an admin section under https, but the rest of it was under http.  Is that going to be similar for the production site?  If so, do we need to order certs and stuff for it?

Comment 8

[Ryan Doherty (:rdoherty)]

(In reply to comment #7)
> Also, from the staging environment, the site had an admin section under https,
> but the rest of it was under http.  Is that going to be similar for the
> production site?  If so, do we need to order certs and stuff for it?

Yes, we'll need https for the admin section to allow for LDAP. So we will need certs.

Regarding Tara's comment in comment #6, we can still edit/update/upload images on stage. I don't see how it offers us any different level of flexibility to do this on production if it's the same site, just a different url.

I'm fine with option #1 as long as IT is ok with it.

Comment 9

[Tara (musingt)]

Sounds good.  Sorry my misunderstanding - I thought we couldn't make edits with option #1.

Comment 10

[Aravind Gottipati [:aravind]]

Since the url for this site is going to be communitystore.mozilla.org, we can just use our wildcard certs.  I don't think we need to order new ssl certs for this.

Comment 11

[Ryan Doherty (:rdoherty)]

Also, the launch time is slated for 12:00pm.

Comment 12

[Ryan Doherty (:rdoherty)]

Update: 

New launch time is Wednesday, Dec 3, 10:00am PST, pending bug 466175 and bug 466921 are resolved.

Comment 13

[Aravind Gottipati [:aravind]]

All good.

Comment 14

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified; we're live.