1223995 - Migrate reps, moderator and moderator-dev off of Stackato

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Eric Ziegenhorn :ericz]

Following up from IRC, the Stackato apps reps, moderator and moderator-dev will be migrated off of Stackato.  This is a tracker bug for that work.

Comment 1

[Eric Ziegenhorn :ericz]

Hi, I just wanted to see if we're on track for this to be migrated before the
end of the year given there are a lot of holidays and Mozlando between now and
then.

Comment 3

[Pierros Papadeas [:pierros]]

Hello,

Reps app can be shutdown as it is.

As the current technical owners of moderator (and its dev instance) we (partincipation infrastructure) would like to know the status of this migration, and details around it (where would it go? who will maintain it? etc.)

Thanks!

Comment 4

[Eric Ziegenhorn :ericz]

Reps app is shut down now, thanks.

These are all self-service apps on Stackato and we're recommending Heroku as the replacement platform as it is also self-service, just better.  John Giannelos was already looking at AWS as a replacement platform last I checked.  John is there any update on the moderator migration?

Comment 5

[Pierros Papadeas [:pierros]]

Moving forward, moderator is not considered as a participation team tool. It is though an internal communications tool, thus under IT team responsibility (including operation and migration)

I am cc'ing the programmatic owner for more input.

Comment 6

[:Atoll]

Let's just decommission moderator then, since it has no developer/owner/champion. :fox2mike, can you ask around and see if anyone's left that wishes to claim it as their own?

Comment 7

[Pierros Papadeas [:pierros]]

Decomission a tool that has 1691 users over its lifetime, is used on every all moco meetings and has Mozlando events on it?

If that sounds OK to you it is fine by me. I would also let Mardi chime in here too.

Comment 8

[:Atoll]

No, that doesn't sound fine to me *at all*. I just thought that since it had been unilaterally disowned by participation team, that it was no longer important. I am glad to see that I was mistaken.

So, we need to find a web developer to maintain this. IT is more than happy to continue running it, but we don't have *any* web developers who can actually repair code issues, or respond to security events that require patches and deploys, and so on.

As it happens, there's an issue right now that isn't immediately apparent how to fix, and it's preventing someone from using the app, and we have no web developers assigned to it, which means they're locked out until we find someone.

Clearly it's unacceptable for Moderator to have *no* maintainer - "a tool that has 1691 users over its lifetime, is used on every all moco meetings and has Mozlando events on it" has no place being unowned. I just wish I could understand why the previous owner let it become unowned, rather than handing off development responsibilities to a new team. (I don't even know who used to own it, annoyingly.)

Shyam will pick up this baton moving forward, as it's both high SLA and currently abandoned. Thank you for correcting my misguided intentions above.

Comment 9

[Pierros Papadeas [:pierros]]

(In reply to Richard Soderberg [:atoll] from comment #8)
 
> So, we need to find a web developer to maintain this. IT is more than happy
> to continue running it, but we don't have *any* web developers who can
> actually repair code issues, or respond to security events that require
> patches and deploys, and so on.

Moderator currently does not need a web developer to maintain it. The code is solid and has been getting all the fixes it needs. The issue is the current deployment. Most (if not all) the errors and troubles we are getting in moderator are deployment and infrastructure related.

> 
> As it happens, there's an issue right now that isn't immediately apparent
> how to fix, and it's preventing someone from using the app, and we have no
> web developers assigned to it, which means they're locked out until we find
> someone.

See above :) No need for a developer. (at least, no need for coding)

Comment 10

[Eric Ziegenhorn :ericz]

Moderator was migrated to the python cluster successfully.  Thanks for the team effort everyone!