Before we deploy anything beyond a dev environment, these deployments need to be automated and repeatable. The best way to make this happen for us is to package everything appropriate as RPM.
Package resultsdb and resultsdb_frontend as RPM so that they can be hosted in a repository. This doesn't mean that getting the packages into fedora is required at this point, just working spec files in git.
Here are specfiles for aniso8601 and python-flask-restful that are needed for resultsdb.
{F25}
{F26}
https://bugzilla.redhat.com/show_bug.cgi?id=1061732 https://bugzilla.redhat.com/show_bug.cgi?id=1059659
and now resultsdb.
resultsdb rpms are available on http://jsedlak.fedorapeople.org/
shouldn't the spec files be in the resultsdb and resultsdb_frontend repos?
I'm not sure if resultsdb and resultdb_fronted repos are integrated with phabricator, so I will send pull request on bitbucket.
This has been resolved for our current purposes, even though the package review request has yet to be resolved. Will keep this ticket open for tracking purposes but am removing it from 0.1
AFAIK this is already resolved, or isn't it @jsedlak? Please close the ticket, if possible, otherwise update with current state.
python-flask-restful and python-aniso8601 are in repos. There are specfiles for resultsdb and resultsdb_api, but I haven't submitted review request for them. I will do it.
python-flask-restful
python-aniso8601
resultsdb
resultsdb_api
! In #43#4338, @jsedlak wrote: python-flask-restful and python-aniso8601 are in repos. There are specfiles for resultsdb and resultsdb_api, but I haven't submitted review request for them. I will do it.
It looks like the review for python-flask-restful is still open and I'm not seeing anything in pkgdb. From what I'm seeing, the review is waiting for input from you.
As for resultsdb*, let's hold off on that for now. I do want to see them in the fedora repos but I'd rather not do it piecemeal and I also think that libtaskotron is more important to have in the repos first.
libtaskotron
python-flask-restful is in repos and all of resultsdb, resultsdb_frontend and resultsdb_api have their specfiles in git, so closing this as "Resolved".