Opened 4 years ago

Closed 3 years ago

#19922 closed defect (fixed)

server set up for giant rabit

Reported by: isabela Owned by: tpa
Priority: High Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: qbi, weasel, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Dear admins, could you please create the servers for Giant Rabit? About the account they will need, should they add them to this ticket as comments or email (encrypted?) is better?

What Tor needs to provide:

The TOR Project will provide two Debian servers that accommodate the following specifications:

Server A (Drupal-hosted CiviCRM and the REST API interface)

  • PHP 5.6
  • User setup for Giant Rabbit staff
  • MySQL or MariaDB
  • Redis
  • 3 websites
    • Production, Staging and Test environments for Drupal-hosted CiviCRM
      • Besides the normal Drupal authentication mechanism, this site will also have HTTP Basic Authentication required with separate accounts for each user.
      • The TOR Project will handle the HTTP Basic Authentication user management.
  • Monit (or some equivalent) to run Resque Worker

Server B (the public donation site)
PHP 5.6

  • User setup for Giant Rabbit staff
  • 3 websites:
    • Production, Staging and Test environments for the public donation site
  • autossh tunnel to Redis on Server A
  • Monit (or maybe just an init script) to start/stop the autossh tunnel

Giant Rabbit will provide a list of Giant Rabbit staff users and private ssh keys that will need access to these servers.

Child Tickets

TicketStatusOwnerSummaryComponent
#20281closedtpaPlease make the following user accounts for GiantRabbitInternal Services/Tor Sysadmin Team

Change History (9)

comment:1 Changed 3 years ago by weasel

Do we know anything about disk and memory requirements?

comment:2 Changed 3 years ago by weasel

we have two hosts, geyeri for the externally reachable things, and gillii for the internal stuff.

both run apache, gillii has mariadb, php, and a redis. the redis is reachable from geyeri (as localhost:6379).

comment:3 Changed 3 years ago by weasel

We need:

  • site names for the apache vhosts on geyeri.
  • site names for the apache vhosts on gillii.
  • database and username for mariaDB on gillii.
  • user account tickets filed.

comment:4 Changed 3 years ago by isabela

Server A:
crm.torproject.org
staging.crm.torproject.org
test.crm.torproject.org

Server B:
donate.torproject.org
staging.donate.torproject.org
test.donate.torproject.org

  • database and username for mariaDB on gillii.

We'll need 3 databases:
tor_prod
tor_stag
tor_test
Username:
www-data

Tickets for accounts:

Version 0, edited 3 years ago by isabela (next)

comment:5 Changed 3 years ago by weasel

dns names created.

Last edited 3 years ago by weasel (previous) (diff)

comment:6 Changed 3 years ago by weasel

I have also created 3 databases, torcrm_{prod,staging,test}. I'm unsure if the user really needs to be www-data or whether it could and should be something dedicated to this crm purpose.

comment:7 Changed 3 years ago by weasel

and we have a user too.

comment:8 Changed 3 years ago by weasel

Status: newneeds_review

comment:9 Changed 3 years ago by weasel

Resolution: fixed
Status: needs_reviewclosed
Note: See TracTickets for help on using tickets.