Page MenuHomePhabricator

Deploy ocg with scap3
Closed, DeclinedPublic

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 7 2016, 9:07 PM

The plan is to sunset OCG, so it's doesn't make sense to put effort in migrating it T150871

The plan is to sunset OCG, so it's doesn't make sense to put effort in migrating it T150871

How soon, by end of quarter? That's the deadline for trebuchet removals.

Pchelolo added a subscriber: GWicke.

That idea was around for quite a while, but since there's no clear owner of OCG it was just dragging. I think @GWicke can provide more details as he was following that closer then I did

See T150871: [EPIC] (Proposal) Replicate core OCG features and sunset OCG service. Original timeline / agreement with Reading was to sunset OCG this month. This has not happened yet, but there is some movement. Both ops & services clearly want this to happen ASAP, so that we can stop spending time on it for things like the Node security upgrade or Scap migration.

There is a working group (that I am on, that we just made on Monday, of tech-mgt people) to work through what it means and how to sunset things here. I hope we have something useful in this case by the end of the month-ish so $whoever_is_tasked_with_it can have time to migrate or remove by the end of Sept. That all depends on what the sunsetting process looks like (it might take longer than a month in some cases, is my guess).

Ah, useful, thanks @GWicke ! I'll follow that task.

How soon, by end of quarter? That's the deadline for trebuchet removals.

The original deadline was 2017-08-01, but that hasn't happened yet. Sunsetting it by EOQ is possible, but it's a stretch IMHO.

The migration to Scap3 shouldn't take more than a day and should be straightforward AFAICT, so if you (RelEng) still want to do it, you should coordinate with @cscott and OpsEns.

Thanks @mobrovac, I poked a little over on the sunsetting epic gwicke mentioned.

As already announced in Tech News, OfflineContentGenerator (OCG) will not be used anymore after October 1st, 2017 on Wikimedia sites. OCG will be replaced by Electron. You can read more on mediawiki.org.

Salt (on which Trebuchet is build on) is being removed by end of September. in TechOps we'll need a few days to fully clean out Salt from production.

Is the plan to still move ocg to scap3 despite it's remaining two weeks of lifetime or is it acceptable to dismantle the deployment basis of ocg starting the week of the 25th? If no further ocg deployments are planned, we could just as well rsync the fix manually in case of an unexpected ocg emergency deployment, the ocg* cluster only consists of three hosts.

Change 378240 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[mediawiki/services/ocg-collection@master] Add scap3 config

https://gerrit.wikimedia.org/r/378240

Change 378241 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[operations/puppet@production] Deploy ocg with scap3

https://gerrit.wikimedia.org/r/378241

thcipriani closed this task as Declined.Sep 15 2017, 12:54 PM

Is the plan to still move ocg to scap3 despite it's remaining two weeks of lifetime or is it acceptable to dismantle the deployment basis of ocg starting the week of the 25th?

I'm declining this task as ocg is meant to be replaced by the end of the quarter and (afaik) no further deployments are scheduled. I've created patches to migrate ocg should the need arise to do a deploy, but I don't think this should block the removal of salt.

Change 378241 abandoned by Thcipriani:
Deploy ocg with scap3

https://gerrit.wikimedia.org/r/378241

Change 378240 abandoned by Thcipriani:
Add scap3 config

https://gerrit.wikimedia.org/r/378240