#6147 Request for resources: Greenwave
Closed: Fixed 6 years ago Opened 6 years ago by dcallagh.

We would like to request resources for a new service, Greenwave.

Greenwave is one of the services we are developing for the Factory 2 effort. Its job is to decide if some software artefact is "good enough" to pass certain gating points, based on configurable policies. For example we would like to have Bodhi query Greenwave to decide if an update has passed all the required tests before it can be pushed stable. More background about Greenwave is in this focus doc:
https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/Greenwave

Greenwave is still in its early stages, we are continuing to flesh out its design and it is not packaged in Fedora (nor built as a container) just yet. But it will be soon. And we would like to get it running as soon as we can, at least in staging, so that we can begin experimenting with hooking Bodhi up to it.

We are targetting deployment in OpenShift (same as WaiverDB #6043) rather than a traditional VM-with-Ansible approach. So this is dependent on Fedora's OpenShift deployment being in place.

As with WaiverDB, @mjia and I can be the development contacts, and I think @rbean is going to be our infra sponsor once again. :-)


Oh and I forgot the most important part, the actual resources. :-)

Greenwave will be lighter than WaiverDB, the design is currently totally stateless. Eventually it may grow some caching but for the time being, there are no requirements for storage or database. It is just a Python web app, which will be listening/sending on fedmsg and also querying the ResultsDB and WaiverDB services. Memory requirements should also be quite light, at least until the hypothetical future when we may start forming lots of detailed per-package policies or something along those lines.

I think @ralph is going to be our infra sponsor once again. :-)

It's true!

Metadata Update from @ralph:
- Issue tagged with: request-for-resources, security

6 years ago

On the audit, there are two outstanding bugs that I filed:
- https://pagure.io/greenwave/issue/38: nice-to-have
- https://pagure.io/greenwave/issue/37: very hard nice-to-have

Those two are the final bugs resulting from the audit. So Greenwave is acked.

Metadata Update from @puiterwijk:
- Issue untagged with: security

6 years ago

Thanks @puiterwijk . I will make sure we cut a new release of Greenwave with both those addressed before it gets to prod.

Just an update - @mjia is working on putting out a new release that should resolve this.

Once done and in place, the (maybe?) last thing left will be monitoring, just like in #6423 .

For the record, @puiterwijk has asked us to fill out the details here a bit more formally... so I'm going to use his template from infra-docs#64

Phase I

  • Software: greenwave
  • Advantage for Fedora: Enable flexible gating at different points in our pipeline.
  • Sponsor: @ralph

Phase II

Phase III

Phase IV

I think we can close this now since we are in production.

Please re-open if there's anything further to do.

:dragon:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata