Switch staging sites to RelStorage

Bug #793187 reported by Paul Everitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KARL3
Fix Released
Low
Chris Rossi

Bug Description

After pgtextindex goes out the door, let's switch branch1-5 to use RelStorage. This makes us dogfood it, perhaps to go into production in July.

Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

Note that all of the staging sites currently use both zeo and relstorage:

https://karlstaging.gocept.com/branch1/osf
https://karlstaging.gocept.com/branch1/osf-relstorage

The only real missing piece is the bit of staging machinery to copy production data over to the relstorage instances.

Revision history for this message
Paul Everitt (paul-agendaless) wrote : Re: [Bug 793187] Re: Switch staging sites to RelStorage

Hmm, I bet that VM is a bit tightly constrained on RAM. :)

--Paul

On Jun 6, 2011, at 8:56 AM, Chris Rossi wrote:

> Note that all of the staging sites currently use both zeo and
> relstorage:
>
> https://karlstaging.gocept.com/branch1/osf
> https://karlstaging.gocept.com/branch1/osf-relstorage
>
> The only real missing piece is the bit of staging machinery to copy
> production data over to the relstorage instances.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/793187
>
> Title:
> Switch staging sites to RelStorage
>
> Status in KARL3:
> New
>
> Bug description:
> After pgtextindex goes out the door, let's switch branch1-5 to use
> RelStorage. This makes us dogfood it, perhaps to go into production
> in July.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/karl3/+bug/793187/+subscribe

Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

Not so much actually:

crossi@osfkarltest10 ~ $ free
             total used free shared buffers cached
Mem: 2072484 1308052 764432 0 430792 157068
-/+ buffers/cache: 720192 1352292
Swap: 2097148 174040 1923108

Chris

On Mon, Jun 6, 2011 at 9:09 AM, Paul Everitt <email address hidden> wrote:

> Hmm, I bet that VM is a bit tightly constrained on RAM. :)
>
> --Paul
>
> On Jun 6, 2011, at 8:56 AM, Chris Rossi wrote:
>
> > Note that all of the staging sites currently use both zeo and
> > relstorage:
> >
> > https://karlstaging.gocept.com/branch1/osf
> > https://karlstaging.gocept.com/branch1/osf-relstorage
> >
> > The only real missing piece is the bit of staging machinery to copy
> > production data over to the relstorage instances.
> >
> > --
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> > https://bugs.launchpad.net/bugs/793187
> >
> > Title:
> > Switch staging sites to RelStorage
> >
> > Status in KARL3:
> > New
> >
> > Bug description:
> > After pgtextindex goes out the door, let's switch branch1-5 to use
> > RelStorage. This makes us dogfood it, perhaps to go into production
> > in July.
> >
> > To unsubscribe from this bug, go to:
> > https://bugs.launchpad.net/karl3/+bug/793187/+subscribe
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/793187
>
> Title:
> Switch staging sites to RelStorage
>
> Status in KARL3:
> New
>
> Bug description:
> After pgtextindex goes out the door, let's switch branch1-5 to use
> RelStorage. This makes us dogfood it, perhaps to go into production
> in July.
>

Changed in karl3:
status: New → In Progress
Changed in karl3:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.