fedora-infrastructure

Clone
Source Code
GIT

#3898 system for cloud image upload service
Closed: Fixed None Opened 10 years ago by mattdm.

Closed: Fixed
Reopen Issue

Background from https://fedoraproject.org/wiki/Features/FirstClassCloudImages/KojiPlan

[[Image(https://fedoraproject.org/w/uploads/f/f1/Kojiplan.jpg)]]

This ticket is about the bit labeled "AMI upload service" on the image above. Dennis had suggested that this could run on an existing releng machine, but I think there's some advantage in it being isolated unto itself. I'll let you all make that decision, though.

This system will

  1. Contain and run code from https://git.fedorahosted.org/cgit/cloud-image-service.git (either deployed by Andrew Thomas, me, or by infrastructure team; whatever is best). This code is still in development and hasn't been tested yet due to other blockers, but will be ready soon.
  2. Contain high-risk security credentials for uploading to the official fedora cloud account
  3. Have write access to alt.fedoraproject.org -- ideally, I think, just to http://alt.fedoraproject.org/pub/alt/cloud and nowhere else

A virtual machine in the fedora cloud infrastructure group would be fine if that's stable enough to run this kind of service at this point.

I said that we should use releng03 which is a machine that doesn't exist today. everything for this needs to be setup in ansible.

the credentials are no more high risk than other bits we have in infra today, they should be in ansible-private

it is not any more special than anything else we have today.

the code needs to be packaged so that it can be deployed.

Replying to [comment:1 ausil]:

I said that we should use releng03 which is a machine that doesn't exist today. everything for this needs to be setup in ansible.

Okay, that's perfect. So this becomes a request for that machine to exist. (It would have been nice to know that that's what you meant, though, because I would have filed this sooner.)

the credentials are no more high risk than other bits we have in infra today, they should be in ansible-private

Sure.

it is not any more special than anything else we have today.

I just wanted to highlight that it ''is'' special, not necessarily more special.

the code needs to be packaged so that it can be deployed.

Does that mean in RPM? Can we deploy from git via puppet?

it needs to be packaged as a rpm. That is how infrastructure deploys things.

I'm willing to help package and maintain it in EPEL if you'd like.

Thanks Sam! Can you talk to Andrew?

We have now fedimg01 to do this. ;)

Oddshocks is working on the setup...

I think we can close this out now, unless there's something here that needs to be specificially addressed as part of deploying fedimg?

Login to comment on this ticket.

Metadata
None
None
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.