Name of the project: joystick One line description of the project: control the plume binary to upload cloud images Contact person for this / admin for the project: sayanchowdhury URL to the sources of the project: https://pagure.io/joystick
@bstinson can you take a look?
Metadata Update from @kevin: - Issue assigned to bstinson - Issue priority set to: Waiting on Assignee (was: Needs Review)
@bstinson or @siddharthvipul1 any thoughts here?
Or is this even still needed? @dustymabe @jdoss might have more insight?
I'd imagine this would be something good to run in openshift. I'll see if @jdoss wants to chime in about moving forward.
I can take a crack at getting it going on Openshift. I just need to be pointed in the right direction for getting access.
Hey @jdoss. As far as design I would look at coreos-koji-tagger. I think we should probably set it up so that it listens for fedora messages that way.
For testing out the design I would test inside communishift for now. Once you have it working in communishift we can get it over into Fedora's main openshift instance (staging and prod).
For deploying an app to staging an prod openshift we use ansible. Some of that is detailed in the coreos-koji-tagger README.
@kevin, can we get @jdoss access to communishift ?
Sure, done.
So, this ticket was for adding a jenkins project for joystick. I assume that was either done long ago, or no longer needed.
Please re-open if thats not the case... or file a new ticket if you need anything different. :)
Metadata Update from @kevin: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)
unfortunately still needed.
@jdoss - where do we stand here?
Metadata Update from @dustymabe: - Issue status updated to: Open (was: Closed)
@jdoss did you see @dustymabe 's question?
Metadata Update from @pingou: - Issue tagged with: ci
unfortunately still needed. @jdoss - where do we stand here?
Sorry @dustymabe I didn't see this. Is it okay if I create this project in fedora-infra namespace (https://jenkins-fedora-infra.apps.ci.centos.org/) ? I would also need a +1 from one of the admins of the namespace (or someone from sysadmin-jenkins) Also, do let me know what type of job that will be. If you are not sure, just let me know a similar project on the namespace and I will create the same.
otoh, if you were expecting a separate namespace (like joystick-apps-ci.centos.org) that will have to wait on bstinson
Metadata Update from @cverna: - Assignee reset
You can wait until we need this to create anything. We don't have our story completely fleshed out right now.
@dustymabe is there anything new for this ticket?
Should we close it and re-open when we can progress on it or should we move forward now?
@dustymabe just an FYI, I can create a separate namespace if it's still needed (on new CI OCP cluster)
we can close this. I think we are tracking new efforts in this space over in https://pagure.io/cloud-sig/issue/301
Metadata Update from @dustymabe: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.