This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
admin:admin:applications:staging [2011/01/10 17:08] 127.0.0.1 external edit |
admin:admin:applications:staging [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Omnidex Administration ====== | + | |
| + | ====== Administration: Administration Basics ====== | ||
| ===== Building Omnidex Applications ===== | ===== Building Omnidex Applications ===== | ||
| - | [[admin:admin:applications:design|Design]] -> [[admin:admin:applications:prototype|Prototype]] -> [[admin:admin:applications:development|Development]] -> [[admin:admin:applications:testing|Testing]] -> **[[admin:admin:applications:staging|Staging]]** -> [[admin:admin:applications:production|Production]] -> [[admin:admin:applications:optimization|Optimization]] | + | [[admin:admin:applications:design|Design]] | [[admin:admin:applications:prototype|Prototype]] | [[admin:admin:applications:development|Development]] | [[admin:admin:applications:testing|Testing]] | **[[admin:admin:applications:staging|Staging]]** | [[admin:admin:applications:production|Production]] | [[admin:admin:applications:optimization|Optimization]] |
| ---- | ---- | ||
| - | |||
| ==== Staging ==== | ==== Staging ==== | ||
| Line 30: | Line 32: | ||
| Some administrators prefer to have a staging server. A staging server is a separate server that is used to assemble and index the data. Assembling and indexing the data can consume a great deal of system resources and it is beneficial to keep this load away from the production servers. Administrators assemble and index the new data, test to insure the new data is ready for deployment, and then copy the data and index files to the production server. | Some administrators prefer to have a staging server. A staging server is a separate server that is used to assemble and index the data. Assembling and indexing the data can consume a great deal of system resources and it is beneficial to keep this load away from the production servers. Administrators assemble and index the new data, test to insure the new data is ready for deployment, and then copy the data and index files to the production server. | ||
| - | For large applications, such as Omnidex Grids, staging servers should be high-performance servers with multiple cores, plenty of memory and extra diskspace. For smaller applications, staging servers can be simpler machines, with just a few cores, a standard amount of memory and sufficient diskspace. The choice of server should also be based on how quickly the new data must be assembled, indexed and deployed. | + | For large applications, such as Omnidex Grids, staging servers should be high-performance servers with multiple cores, plenty of memory and extra diskspace. For smaller applications, staging servers can be simpler machines, with just a few cores, a standard amount of memory, and sufficient diskspace. The choice of server should also be based on how quickly the new data must be assembled, indexed, and deployed. |
| Line 37: | Line 39: | ||
| Some administrators maintain two production servers, alternating which server is currently in use. While that server processes the production queries, the other server acts as a staging server. Once the new data is assembled and indexed on the staging server, the roles reverse and the staging server becomes the new production server. Meanwhile, the old production server begins the process of assembling and indexing the next batch of data. | Some administrators maintain two production servers, alternating which server is currently in use. While that server processes the production queries, the other server acts as a staging server. Once the new data is assembled and indexed on the staging server, the roles reverse and the staging server becomes the new production server. Meanwhile, the old production server begins the process of assembling and indexing the next batch of data. | ||
| - | This strategy allows faster deployment since the data and indexes do not need to be copied between servers. This strategy is commonly used for Omnidex Grids as well since Omnidex Grids benefit from a lot of parallel processing. | + | This strategy allows faster deployment since the data and indexes do not need to be copied between servers. This strategy is commonly used for Omnidex Grids as well, since Omnidex Grids benefit from a lot of parallel processing. |
| === Rotating Nodes on an Omnidex Grid === | === Rotating Nodes on an Omnidex Grid === | ||
| Line 46: | Line 48: | ||
| - | ====== ====== | + | ===== ===== |
| - | \\ | + | **[[admin:admin:applications:testing|Prev]]** | **[[admin:admin:applications:production|Next]]** |
| - | ---- | + | |
| - | \\ | + | |
| - | The next stage in building Omnidex applications is [[admin:admin:applications:production|Production]]. | + | ====== Additional Resources ====== |
| - | **[[admin:admin:applications:testing|Prev]]** | **[[admin:admin:applications:production|Next]]** | + | See also: |
| + | {{page>:admin:admin:see_also&nofooter&noeditbtn}} | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||