Opened 12 years ago
Closed 12 years ago
#118 closed (fixed)
push all submission-related changes to gmoc-db
| Reported by: | chaos@bbn.com | Owned by: | mrmccrac@grnoc.iu.edu |
|---|---|---|---|
| Priority: | major | Milestone: | gmoc.py data submission debugging |
| Component: | Infrastructure | Version: | |
| Keywords: | Cc: | ||
| Dependencies: |
Description
The changes we have made to gmoc-db2 (database schema and scripts) in order to get gmoc.py relational submission working should be pushed to gmoc-db.
Change History (3)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
| Owner: | changed from somebody to mrmccrac@grnoc.iu.edu |
|---|
We will do this cutover at 13:00 today. We have notified gmoc about the outage, and asked them to notify response-team. Mitch is going to do the actual cutover.
comment:3 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
In addition to the changes Mitch identified in advance, we needed to do:
- Add a column
primary_contactto some table (not sure which, i think probably slice) on gmoc-db - Install the grandfathered sliver URN:
urn:publicid:IDN+gmoc.geni.net+contact+user-not-known
on gmoc-db.
I think this is done now.
Note: See
TracTickets for help on using
tickets.
This is another dependency to get live aggregates reporting data using gmoc.py.