#9 Migrate to Fedora Communishift
Closed: not possible 2 years ago by jflory7. Opened 4 years ago by jflory7.

Eventually, the Fedora OpenStack servers where TeleIRC currently lives will go away. Eventually, we should migrate to the Fedora community OpenShift, "Communishift", hosted by Fedora Infrastructure:

https://fedoraproject.org/wiki/Infrastructure/Communishift

This will likely require us to switch to a container-based method of deploying TeleIRC.


Is there a timeline that we need to get this done by?

As a note on resource limits, it seems there is a base limit of 10 pods. SInce there are currently 21 groups using TeleIRC (in Fedora), we may need to ask for more resources.

As a first step for whenever we do this implementation, we should do a test run with a few groups before doing a full switch.

Is there a timeline that we need to get this done by?

Good question. I asked for clarification in #fedora-admin on IRC.

As a note on resource limits, it seems there is a base limit of 10 pods. SInce there are currently 21 groups using TeleIRC (in Fedora), we may need to ask for more resources.

Good catch. You're right, we will need to request more. Hopefully since these are very very lightweight processes, it will not be a blocker.

As a first step for whenever we do this implementation, we should do a test run with a few groups before doing a full switch.

+1. Do you have some experience with migrating apps to OpenShift? We could get face-time in September to try out TeleIRC in a container and work on porting it into a Minishift VM locally.

Great, thanks for asking in #fedora-admin ^>^
I don't see requesting more resources as being a blocker, hopefully, since each instance is pretty lightweight and used pretty heavily throughout the groups.

In terms of OpenShift, I have some experience with app migration. I spent my last week at work learning about the OpenShift model as we prepare our own migration process from OpenStack to OpenShift. Once we see each other in person and start up TeleIRC developer meetings again, we can start this process of figuring out the new OpenShift implementation. Minishift may be a good initial step to work towards.

Do you have much experience with OpenShift? We may be able to catch each other up on pieces we're missing out on.

@jflory7 did you ever find a timeline that we need to get this done by?

We had some offline conversations about this. tl;dr, there is not a strict timeline to move to the Communishift. Before tackling this one, we will probably wait for TeleIRC upstream to make more progress on a Go port by the end of 2019.

Metadata Update from @jflory7:
- Issue untagged with: help wanted
- Issue priority set to: waiting on external (was: needs review)
- Issue tagged with: blocked

4 years ago

Update

We have been given a deadline of March 1st, 2020 to shut down our OpenStack instances.

We are currently working to get an extension until June. This may result in a temporary AWS deployment.

Furthermore, we need to come up with a list of requirements that we need in order to successfully transition to OpenShift. These may include:

  • Pushing TeleIRC to an image registry (docker hub, quay)
  • Adding configuration methods for adding new TeleIRC groups
    • May include creating teleirc.yaml files
    • Use new credentials system to replace ansible vault for TeleIRC secrets

We should add to this issue, or create a new one, to track our specific timeline for what we need to do in order to complete this transition.

Yes. This is not happening. Thanks for pointing it out @t0xic0der. Closing as not possible.

Metadata Update from @jflory7:
- Issue close_status updated to: not possible
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata