Ticket #2673 (closed RFR: wontfix)

Opened 3 years ago

Last modified 15 months ago

Hosting space for nitrate project

Reported by: jlaska Owned by: kevin
Priority: major Milestone: Fedora 15
Component: General Version:
Severity: Normal Keywords:
Cc: rhe, kevin Blocked By:
Blocking: Sensitive: no

Description

Project Sponsor


Project Team (FAS Names): rhe, vchen, jlaska
Infrastructure Sponsor: ???

Project Info


Project Name: nitrate server
Target Audience: Fedora QA
Expiration/Delivery? Date (required): After Fedora 15 is released (eta 2011-05-17)
Description/Summary:

The Fedora QA team is interested in exploring nitrate to replace our use of wiki for managing test results from community test events (e.g. test days, release validation etc...)

A virtual guest where we can create+manage a mysql database, and host a Django-based application should be sufficient.


Project plan (Detailed):

The nitrate project (see https://fedorahosted.org/nitrate) is a test case management system created by Red Hat associates. The nitrate project uses the testopia database schema, but relies on a Django-based front-end to work around several issues with upstream testopia. The most notable issue being incompatible licensing of the Testopia front-end.

The Fedora QA team is interested in exploring nitrate to replace our use of wiki for managing test results from community test events (e.g. test days, release validation etc...). Hurry (Fedora QA) has been developing a list of requirements. However, in order to complete requirements, it will be helpful to have a proof-of-concept server available to use for several upcoming test runs.


Goals:

  • experiment with managing several community test events using nitrate
  • identify additional missing features or workflows

Change History

comment:1 follow-up: ↓ 2 Changed 3 years ago by kevin

  • Owner changed from sysadmin-members to kevin
  • Cc kevin added

I'll help you guys out with this one.

Next steps:

  1. Get nitrate packaged
  2. Test on a publictest instance.
  3. Decide some things:

a) does it need it's own local db, or can it use one of our existing db servers? b) does it need to be load balanced or just a direct instance.

Likely there are many other decisions to make along the way, but we can do so as we come to them. ;)

comment:2 in reply to: ↑ 1 ; follow-ups: ↓ 3 ↓ 4 Changed 3 years ago by jlaska

Replying to kevin:

  1. Get nitrate packaged

Can the packaging work proceed in parallel, or does it need to be completed before moving to the next step?

  1. Test on a publictest instance.

Looking forward to this step! :)

  1. Decide some things:

a) does it need it's own local db, or can it use one of our existing db servers? b) does it need to be load balanced or just a direct instance.

I'll ask for guidance from rhe (or nitrate-devel) for this.

comment:3 in reply to: ↑ 2 Changed 3 years ago by jlaska

Replying to jlaska:

a) does it need it's own local db, or can it use one of our existing db servers? b) does it need to be load balanced or just a direct instance.

I'll ask for guidance from rhe (or nitrate-devel) for this.

A MySQL database on a separate host is preferred.

comment:4 in reply to: ↑ 2 ; follow-up: ↓ 5 Changed 3 years ago by kevin

Can the packaging work proceed in parallel, or does it need to be completed before moving to the next step?

I'd really prefer the packaging is all worked out first. That way we can install and test that package and know what we are getting, can upgrade easily, etc.

A MySQL database on a separate host is preferred.

ok. We could do a local db on the same publictest for that stage of things, then when we move to staging we can move the db to a db host from there.

comment:5 in reply to: ↑ 4 Changed 3 years ago by jlaska

Replying to kevin:

Can the packaging work proceed in parallel, or does it need to be completed before moving to the next step?

I'd really prefer the packaging is all worked out first. That way we can install and test that package and know what we are getting, can upgrade easily, etc.

Certainly understood! Will stay tuned to bug#690728 for updates.

comment:6 Changed 15 months ago by kevin

  • Sensitive unset
  • Resolution set to wontfix
  • Status changed from new to closed

I'm going to close this for now.

We can reopen it when/if we get closer to implementing anything.

Note: See TracTickets for help on using tickets.