bodhi2 plans

[Kevin Fenzi]

Greetings. 

So, in the releng meeting last week we discussed about landing bodhi2
before the alpha freeze started, however there were just too many
things still up in the air to do that, so we held off. 

However, I'd like to propose a concrete date to enable it and try and
make sure we have everything we need lined up for making that work. :) 

My understanding of the current status: 
(Luke: please correct me if anything is wrong or unclear here)

* We have bodhi2 web frontend up and running fine in staging: 
https://admin.stg.fedoraproject.org/updates/
(well, right now it's down as Luke is working on a update id bug there
and is repopulating the db, but it was and will be up again soon). 

* We have a bodhi2 backend up in staging and it's successfully mashed
  updates pushes. 

* bodhi2 isn't yet packaged in Fedora (it and it's deps are in a copr): 
http://copr.fedoraproject.org/coprs/lmacken/bodhi2/

So, to get that last bit we need: 

* API users. I thought we had a list somewhere, but I cannot seem to
  find it. At least fedora-easy-karma and fedora-gooey-karma use it.
  Are all of these using python-fedora for the api? Do we need to
  update that and bodhi-client? 

* We need bodhi2 in fedora/epel. Were we going to do it as a seperate
  package, or just an update to the existing 'bodhi' package. I assume
  maintainers would need the new client to do 'fedpkg update' ?

* Do we need any fedpkg changes? Or anything else? How do we want to
  handle the switchover?

* Is taskotron all ready to go with bodhi2? or more changes there?

* We will need an outage to switch over. I assume the bodhi1->bodhi2 db
  conversion shouldn't take too long? But once we convert and make live
  we are commmited. 

* Anything else I missed?

I'd like to propose we schedule the switchover/outage for 2015-08-19. 
(Provided alpha doesn't slip). This will allow us a few days to recover
from flock and get anything lined up we need to. 

Thoughts? additions? 

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150803/5db1c65a/attachment.sig>