mass staging
Dutch translation: grootschalige staging naar productie; overbrengen van alle apparatuur naar de productieomgeving
| GLOSSARY ENTRY (DERIVED FROM QUESTION BELOW) | ||||||
|---|---|---|---|---|---|---|
|
| 07:22 Sep 16, 2016 |
| English to Dutch translations [PRO] Tech/Engineering - IT (Information Technology) | |||||||
|---|---|---|---|---|---|---|---|
|
| ||||||
|  Selected response from: Kitty Brussaard Netherlands Local time: 11:55 | ||||||
Grading comment
| |||||||
| Summary of answers provided | ||||
|---|---|---|---|---|
| 3 | grootschalige staging naar productie(omgeving) |
|
| Summary of reference entries provided | |||
|---|---|---|---|
| Staging naar productie |
|
| Discussion entries: 1 | |
|---|---|
Answers
4 hrs confidence: 
grootschalige staging naar productie(omgeving) Explanation: Een poging :-). De term 'staging' op zichzelf is mij wel bekend (zie ook mijn opmerking in de D-box en de zojuist geplaatste verwijzing), maar ik durf niet met zekerheid te zeggen wat 'mass staging' hier precies inhoudt. Het lijkt hier in ieder geval te gaan om staging/verplaatsing van de apparatuur/installatie naar de productie-omgeving. Wellicht dat de verdere context hier nog verdere verduidelijking kan bieden. -------------------------------------------------- Note added at 6 days (2016-09-22 09:52:11 GMT) -------------------------------------------------- @Joop: graag gedaan :-) |
| ||
Notes to answerer
| |||
| Login to enter a peer comment (or grade) | |||
Reference comments
4 hrs |
| Reference: Staging naar productie Reference information: Zie mijn opmerking in de D-box en onderstaand voorbeeld, dat specifiek betrekking heeft op staging naar productie van portaloplossingen. Staging naar productie Tijdens ontwikkeling van portaloplossingen wordt de oplossing oorspronkelijk ontwikkeld, getest en verfijnd op één server of op een beperkt aantal servers. De oplossing wordt later geïmplementeerd op actieve systemen, die de productieomgeving worden genoemd. Het verplaatsen van de oplossing van de ontwikkelomgeving naar de productieomgeving wordt staging genoemd. Tijdens de ontwikkelingscyclus van een oplossing is er verschillende keren staging vereist. Elke release van de oplossing wordt op een bepaald systeem gebouwd en vervolgens verplaatst naar het productiesysteem. Tijdens deze hele cyclus worden er meerdere oplossingen gemaakt en in productie genomen. Er worden meerdere releases met oplossingen gebouwd op de vorige productrelease. Staging is alleen mogelijk bij dezelfde productrelease. Bijwerken van een release naar een nieuwere release wordt migratie genoemd. http://www.ibm.com/support/knowledgecenter/nl/SSHRKX_8.5.0/m... -------------------------------------------------- Note added at 8 hrs (2016-09-16 16:20:14 GMT) -------------------------------------------------- Staging Alle ontwikkelingen en deelopleveringen zetten we in een voor u gemaakte proefomgeving, in deze omgeving kunt u alle deeloplossingen testen op functionaliteit en werking. Pas bij akkoord brengen we deze over naar de live omgeving zodat iedereen er gebruik van kan maken. http://www.panaxae.com/ Deployment architectures vary significantly, but broadly, the tiers are bookended by starting at development (DEV) and ending at production (PROD). A common 4-tier architecture is development, testing, staging, production (DEV, TEST, STAGE, PROD), with software being deployed to each in order. (...) Another common architecture is development, testing, acceptance and production (DTAP), consisting of dev/test/qa/prod. Staging (STAGE) is a pre-production environment, for final testing immediately prior to deploying to production. It seeks to mirror the actual production environment as closely as possible, and may connect to other production services and data, such as databases. For example, servers will be run on remote machines, rather than locally (as on a developer's workstation during dev, or on a single test machine during test), which tests the effect of networking on the system. The primary use of a staging environment is to test all installation/configuration/migration scripts and procedures, before they are applied to production environment. This ensures that all major and minor upgrades to the production environment will be completed reliably without errors, in minimum time. Another important use of staging is for performance testing, particularly load testing, as this often depends sensitively on the environment. Production The production environment is also known as live, particularly for servers, as it is the environment that users directly interact with. Deploying to production is the most sensitive step; it may be done by deploying new code directly (overwriting old code, so only one copy is present at a time), or by deploying a configuration change. This can take various forms: deploying a parallel installation of a new version of code, and switching between them with a configuration change; deploying a new version of code with the old behavior and a feature flag, and switching to the new behavior with a configuration change that performs a flag flip; or by deploying separate servers (one running the old code, one the new) and redirecting traffic from old to new with a configuration change at the traffic routing level. These in turn may be done all at once or gradually, in phases. Deploying a new release generally requires a restart, unless hot swapping is possible, and thus requires either an interruption in service (usual for user software, where applications are restarted), or redundancy – either restarting instances slowly behind a load balancer, or starting up new servers ahead of time and then simply redirecting traffic to the new servers. When deploying a new release to production, rather than immediately deploying to all instances or users, it may be deployed to a single instance or fraction of users first, and then either deployed to all or gradually deployed in phases, in order to catch any last-minute problems. This is similar to staging, except actually done in production, and is referred to as a canary release, by analogy with coalmining. This adds complexity due to multiple releases being run simultaneously, and is thus usually over quickly, to avoid compatibility problems. https://en.wikipedia.org/wiki/Deployment_environment#Develop... |
| |
| Login to enter a peer comment (or grade) | ||
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.
KudoZ™ translation help
The KudoZ network provides a framework for translators and others to assist each other with translations or explanations of terms and short phrases.
See also:
Search millions of term translations