#9760 Request for EC2 VM
Closed: Fixed by mobrien. Opened by richardgreg.

Describe what you would like us to do:


Hi, I'm an Outreachy intern working on enabling CI/CD for the Fedora documentation website. I have written a script that accomplishes the task and I need an EC2 VM to run it.

When do you need this to be done by? (As soon as possible)


Thank you.


Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

siddharthvipul1 commented

@kevin @mobrien
I would like to help with this
From what I understand, this is a low trouble task and I can take these as we get it every once in a while
What kind of permission would I need?

Metadata Update from @siddharthvipul1:
- Issue untagged with: low-gain, low-trouble, ops
- Issue priority set to: Needs Review (was: Waiting on Assignee)

Metadata Update from @humaton:
- Issue tagged with: low-gain, low-trouble, ops

@richardgreg some questions for you:

  • Does this need to be a vm? Can it run in openshift instead?
  • If it's a vm, you realize that YOU will be responsible for keeping it updated and secure.
  • will this be in the critical path of publishing docs?
  • what os/cpu/memory/disk do you need?

@siddharthvipul1 we can add you to the aws-infra group, which will allow you access to the fedora infra stuff in aws. From there you should be able to spin up a vm for this. However, I would really prefer this to live in openshift if possible. :)

siddharthvipul1 commented

@richardgreg some questions for you:

Let me answer some of these to the extent I understand, @richardgreg and @pingou, if I get anything wrong, please do correct

  • Does this need to be a vm? Can it run in openshift instead?

That was the initial and ideal solution, but because of complexity and outreachy period ending soon, we had to cut that out of the scope and just get something working. Once we have something working in a vm, we can look at putting this all in a container in near future

  • If it's a vm, you realize that YOU will be responsible for keeping it updated and secure.

As this should not fall on anyone from Infrastructure team, +1 and no other way

  • will this be in the critical path of publishing docs?

No, the goal is to comment a rendered - link of PR (as a preview) but the PR can be merged regardless

  • what os/cpu/memory/disk do you need?

@richardgreg Leaving this to you

@siddharthvipul1 we can add you to the aws-infra group, which will allow you access to the fedora infra stuff in aws. From there you should be able to spin up a vm for this.

Great, I can take this and bother others (after AAA things settle down) in case I need any help.

However, I would really prefer this to live in openshift if possible. :)

I agree.. will see if this can be done after outreachy period or a general task open for community members to tackle. Can also be a good help us task

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

Fedora OS/2CPU/4GB/10-15 GB

ok. If this is just a pilot thing and we are going from there thats ok.

@nb @mobrien can one or both of you work with @siddharthvipul1 sometime and go over processing this? He should be in the right group for access. :)

Thanks!

siddharthvipul1 commented

Thank you @mobrien for guiding me the process
This is done and can be closed

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

Metadata