Hello,
As announced by the Release Engineering team last week~[1], Trebuchet is being officially deprecated in favour of Scap3 as the preferred deployment mechanism. In order to ease the transition for Node.JS services running in WMF production, I have written a guide that will help service owners switch to the new method~[2]. I invite all service owners to take a look at it and migrate to Scap3 as soon as possible (but not before April, 25th as there are no deploys next week).
We have already filed the necessary tasks in Phabricator for: * Kartotherian~[3] * Mobile Content Service~[4] * Tilerator~[5] * OCG~[6] * CXServer~[7] * Mathoid~[8] * Graphoid~[9] * Parsoid~[10]
If you cannot find your service on the Scap3 board~[11], file a task for it.
Let me know if you need any help or assistance in the process.
Cheers, Marko
[1] https://lists.wikimedia.org/pipermail/wikitech-l/2016-April/085248.html [2] https://wikitech.wikimedia.org/wiki/Services/Scap_Migration [3] https://phabricator.wikimedia.org/T129150 [4] https://phabricator.wikimedia.org/T129147 [5] https://phabricator.wikimedia.org/T129146 [6] https://phabricator.wikimedia.org/T129142 [7] https://phabricator.wikimedia.org/T120104 [8] https://phabricator.wikimedia.org/T116338 [9] https://phabricator.wikimedia.org/T120102 [10] https://phabricator.wikimedia.org/T120103 [11] https://phabricator.wikimedia.org/project/view/1824/
Oo also! Mukunda and Tyler and I did some work over the last couple of weeks to make bootstrapping new repos on deployment servers easier and decoupled from trebuchet. You don’t need to do this now if your repo is already cloned on tin, but you might want to anyway. snap deployed repos should be added the list of sources in hieradata/common/scap/server.yaml (in prod)[1]. For deploy-service repos, you don’t need to add any new keyholder_agents, but adding an entry in sources will ensure that your repo is cloned on a newly provisioned deploy server. To do so, add:
<service-name>/deploy: ~
to the list of snap::server::sources there. (The tilde just makes scap::source use default params.) See scap::source docs for more info[2].
I’ve updated Marko’s Services/Scap_Migration page with this step.
-Ao
[1] In labs deployment-prep, use hieradata/labs/deployment-prep/common.yaml [2] https://github.com/wikimedia/operations-puppet/blob/production/modules/scap/...
I must note that ORES service in beta [1] uses scap3 deployment instead of fabric. I think that's the only python based service deployed via scap3, I'll be around at IRC if you have questions about migrating python-based services.
[1]: https://ores-beta.wmflabs.org Best
On Thu, Apr 14, 2016 at 6:27 PM Andrew Otto otto@wikimedia.org wrote:
Oo also! Mukunda and Tyler and I did some work over the last couple of weeks to make bootstrapping new repos on deployment servers easier and decoupled from trebuchet. You don’t need to do this now if your repo is already cloned on tin, but you might want to anyway. snap deployed repos should be added the list of sources in hieradata/common/scap/server.yaml (in prod)[1]. For deploy-service repos, you don’t need to add any new keyholder_agents, but adding an entry in sources will ensure that your repo is cloned on a newly provisioned deploy server. To do so, add:
<service-name>/deploy: ~
to the list of snap::server::sources there. (The tilde just makes scap::source use default params.) See scap::source docs for more info[2].
I’ve updated Marko’s Services/Scap_Migration page with this step.
-Ao
[1] In labs deployment-prep, use hieradata/labs/deployment-prep/common.yaml [2]
https://github.com/wikimedia/operations-puppet/blob/production/modules/scap/... _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Awesome \o/
On Thu, Apr 14, 2016 at 6:55 PM Andrew Otto otto@wikimedia.org wrote:
I think that’s the only python based service deployed via scap3
EventLogging is python and deployed with scap3. _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org