#2797 Define how we want to use *.dev and its relation to pt* and *.stg
Closed: Fixed None Opened 12 years ago by toshio.

= background analysis =
Currently we have three environments that are used for things not yet in production:

  • publictest (pt)
  • *.dev
  • *.stg

Although we seem to agree that pt is more experimental than .dev than .stg than production, we haven't really nailed down what the expectations from our side or from the user's of these systems sides are. This ticket is so we start discussing and figuring this out a bit.

= implementation recommendation =
||'''topic'''|| '''pt''' || '''dev''' || '''stg''' ||
|| '''Purpose''' || Experimentation with new apps for potential deployment in infrastructure (Currently: also used for testing new features for existing apps) || Testing new features for existing apps (Possible future: also, testing long term apps?) || Integration testing and sanity check before deploying changes (Currently: also used to test new features that are almost done; recreate and fix bugs that are reported in production)||
|| '''Timeframe''' || We agree that pt should have a short timeframe between refreshes (1 month?) || One idea for dev is that it's longer time frame. Perhaps semi-permanent (ie: boxes may be reinstalled from scratch but the apps being worked on on them would be reinstalled ) || apps live here semi-permanently as the environment simulates production ||
|| '''users''' || currently: sysadmin-test. Possible future: individual boxes have one service with a distinct set of users (ie: calendar testing would have a group that is different from bcfg testing) || currently: sysadmin-test and sysadmin-web. Possible future: one group/box per service like publictest||sysadmin-web which mirrors production||


I think we have basically moved to this model now. ;)

The dev boxes I have made recently have followed the 'per group' setup.

Should we codify this? where? The RFR docs? somewhere else?

We should codify it. RFR docs probably work for publictest but not really for the others. Maybe a new document and link to it from RFR docs etc.

Going to add this link in here:
http://fedoraproject.org/wiki/Infrastructure/Rethinking_staging_and_development

More thoughts on changing how this is all setup.

We may be revising this soon to handle containers and cloud and other things... but I don't think this is the place to discuss that. Will close this for now, but once we have decided something on list or in meetings we can open a new one to codify that.

Login to comment on this ticket.

Metadata