#5943 Please create loopabull_ociimage automation user created for automation tasks related to oc image management/syncing actions
Closed: Fixed 5 years ago by kevin. Opened 6 years ago by maxamillion.

I'm open to other names for the automation user account, but I'll use the one in the title through out the ticket for now.

I would like to request the loopabull_ociimage user be created such that it can ssh from loopabull01.stg to composer.stg in order to perform skopeo actions to manage docker and other oci compliant images (in the future this will likely include flatpaks).

Sudo permissions:
- skopeo copy
- skopeo delete
- skopeo inspect

This is for use with RelEng Automation[0].

[0] - https://pagure.io/releng-automation


I guess this is going to taken over by @puiterwijk now.

I'd say we should create these users in the playbook locally, but we also need to blacklist them in fas so they could never exist there. Or should we just allow loopabull to run these things as root?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Asignee

5 years ago

Since loopabull is no longer pointed to that git repo I think we can close this ticket and re-consider this if someone wants to take back this work

@cverna @mohanboddu this may be something that interest you, if so feel free to ping me, I'll help you get familiar with the new setup :)

@pingou I am interested in understanding the new setup.

Lets get together sometime and go over it.

Is this still being worked on by @mohanboddu and @pingou or can we close this?

I am not working on it, happy to help if someone wants some insight in our loopabull deployment though :)

I'm going to just close this for now, please file a new ticket if there's something we need to do.

:clock830:

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

5 years ago

Login to comment on this ticket.

Metadata