infra/tickets

Please create loopabull_ociimage automation user created for automation tasks related to oc image management/syncing actions #5943

New issue

Closed

opened 2017-03-30 17:47:39 +00:00 by maxamillion · 9 comments

maxamillion commented

2017-03-30 17:47:39 +00:00

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'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

kevin commented

2018-04-20 20:07:43 +00:00

Owner

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?

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?

kevin commented

2018-04-20 20:07:44 +00:00

Owner

Metadata Update from @kevin:

Issue priority set to: Waiting on Asignee

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

pingou commented

2018-08-16 14:53:58 +00:00

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 :)

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 :)

mohanboddu commented

2018-08-16 14:58:05 +00:00

@pingou I am interested in understanding the new setup.

Lets get together sometime and go over it.

@pingou I am interested in understanding the new setup. Lets get together sometime and go over it.

pingou commented

2018-08-16 14:59:34 +00:00

Sure :)

Sure :)

smooge commented

2018-09-20 14:42:52 +00:00

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

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

pingou commented

2018-09-21 07:34:47 +00:00

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

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

kevin commented

2019-03-25 22:30:09 +00:00

Owner

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

🕣

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

kevin commented

2019-03-25 22:30:09 +00:00

Owner

Metadata Update from @kevin:

Issue close_status updated to: Fixed
Issue status updated to: Closed (was: Open)

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

Sign in to join this conversation.

No labels

forgejo_migration

Needs investigation

packager_workflow_blocker

🔥 URGENT 🔥

Waiting on Assignee

Waiting on External

Waiting on Reporter

release-monitoring

request-for-resources

websites-general

No milestone

No project

No assignees

5 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

infra/tickets#5943

No description provided.