Bxp Release 10 - Revision history

Philip Lacey: /* Replication */

2017-10-03T14:37:34Z

‎Replication

Philip Lacey: /* Physical Servers */

2017-10-03T14:36:04Z

‎Physical Servers

Philip Lacey: /* Schedule notes */

2017-10-03T14:33:26Z

‎Schedule notes

Philip Lacey at 14:29, 3 October 2017

2017-10-03T14:29:47Z

Show changes

Philip Lacey: Created page with "= Overview = bxp Release 10 went live on Sunday 26th of March 2017. The primary focus was to * change the infrastructure's physical servers, * server operating systems an..."

2017-10-03T13:38:31Z

Created page with "= Overview = bxp Release 10 went live on Sunday 26th of March 2017. The primary focus was to * change the infrastructure's physical servers, * server operating systems an..."

New page

= Overview =

bxp Release 10 went live on Sunday 26th of March 2017. The primary focus was to
* change the infrastructure's physical servers,
* server operating systems and
* to perform a database engine upgrade.

= Physical Servers =

= Server Operating Systems =

= Database engine upgrade =

[[Category:Topic:About bxp]]

@@ Line 44: / Line 44: @@
-When chatting with Denis Creighton and the technical team in FEXCO (who also MySQL inhouse as well as bxp) we discovered that MySQL 5.7 had some distinct advantages over 5.6.
+When chatting with Denis Creighton and the technical team in FEXCO (who also use MySQL inhouse as well as bxp) we discovered that MySQL 5.7 had some distinct advantages over 5.6.
@@ Line 55: / Line 55: @@
 The master / slave functionality now means that in real time Db2 can serve as a database server.  It is also now capable of responding to queries, thus allowing it to become operational rather than just a backup server waiting in the wings.
 == Operational challenges ==

@@ Line 195: / Line 195: @@
 Key Notes
 * Db2, will become an active server, rather than a passive backup server.
 * The hard drives in the Db servers are being changed from 7200 rpm drives to Solid State Drives, which will see throughput increase over 10 fold.
@@ Line 202: / Line 204: @@
 * Previously if we’d used Db1, the tables would lock and the tills still would have been unusable.  Instead, we’re able to allow W3 to chat to Db2, which is being kept up to date in real time.  This means the tills aren’t affected and yet we can do very memory intensive operations.
 * This change addresses KeyStats generation speed issues, as they will be created on W3.
 = Server Operating Systems =

@@ Line 265: / Line 265: @@
 | 2017-02-11 || Live setup of new infrastructure
 |-
-| 2017-02-18 || Migration of services from current infrastructure to new infrastructure
+| 2017-02-18 || Migration of services from current infrastructure to new infrastructure (Actually moved 26th March 2017 due to staff availability)
 |-
 | 2017-02-25 || KeyStat generation and all scheduled processes to be migrated to Web3