Parts for the 250 Quad
| #!/usr/bin/python | |
| import random | |
| words = ['gamification', 'informal', 'learning', 'individualized', 'E-', 'Differentiated', 'Massive open online course', 'virtual', 'environment'] | |
| choices = [random.choice(words) for _ in range(10)] | |
| print(' '.join(choices)) |
| diff --git a/owncloud.wxs b/owncloud.wxs | |
| index d24d042..2272f33 100644 | |
| --- a/owncloud.wxs | |
| +++ b/thunderbird.wxs | |
| @@ -1,28 +1,25 @@ | |
| <?xml version='1.0'?> | |
| -<?define PrevProductVersion = "1.8.2"?> <!-- Match previous ownCloud Client version --> | |
| -<?define ProductVersion = "1.8.3"?> <!-- Match ownCloud Client version --> | |
| -<?define ExeSourceFile = "ownCloud-1.8.3.5213-setup.exe"?> <!-- Match new .exe : use a relative path --> | |
| +<?define PrevProductVersion = "1.8"?> <!-- Match previous Thunderbird version, can be `ProductVersion-1` if new install --> |
- Document current AWS resources for each plan
- MT vs ODB
- Required vs Optional tags
- Add postgis extention
- IP Subnets from external domains (see Connecting to the Service from external VPC)
- Compliance Profiles
- Document pgAudit settings for each profile
The commands listed in this document use BOSH CLI v2+ and CF CLI version 6.37.0+a40009753.2018-05-25+
In addition to standard PCF service parameters, Our recent releases have included the ability for customers to modify the PostgreSQL configuration parameters while creating or updating service instances.
In Crunchy PCF release version 03.090512.109, users could create a service instance with the pgc_ parameters.
An example of creating a service instance with modifying the max_wal_senders and log_rotation_size PostgreSQL options is as follows:
The commands listed in this document use BOSH CLI v2+.
The current Crunchy PostgreSQL for PCF tile release included high availability features that in the event of a problem on the Primary PostgreSQL server, our configuration would automatically fence the Primary and promote a replica to Primary status. Our recent release of the v04.090513.001 tile version included some additional statistics gathering as part of our health check process.
The high availability functions are based on the status of each server in Consul. On each of the PostgreSQL servers, there exists a script at /var/vcap/store/service/healthcheck.sh. Every service has one, haproxy, pgbackrest, postgresql, etc. in the same location. The Consul application on each VM runs that script, if it exits with a status code of 0, it is in passing state, if it is 1 warning state and anything 2 or above it is marked critical. Our HA configuration is such that if the status of a PostgreSQ
| 86 35 F4 40 93 DF 1A 60 79 84 5E B9 65 C4 81 7F CD 7D 8E 88 61 4A 22 B5 DC 6E C2 E7 EE D2 8F 39 31 D9 A4 0B 8F 79 64 91 E6 BC 4B D3 75 D0 F0 34 AC 21 C3 0E F5 BB C1 A6 0F 79 28 AE 06 50 33 34 34 30 30 32 36 1D 00 00 01 00 00 14 00 00 99 00 07 32 1A 00 00 00 00 E6 96 7E 3F 97 82 9B B8 AA 39 23 30 34 61 7A 2A 68 6C 02 2E 00 02 DE E6 02 81 5B 08 F6 40 07 AB 4B 08 B0 A2 02 2F 00 02 E0 E6 02 17 1E 05 F6 79 04 9C 76 06 00 00 E6 09 00 00 95 0B 7C 1E EB 07 08 D4 01 18 10 8F 15 B5 0D F8 18 91 1D BD 0F FC 07 92 1E 95 14 92 02 B3 05 F9 FF 00 4B FD 7D 59 E3 41 39 01 FF 89 62 8C 1F 72 52 00 E2 60 3E 0F E2 63 FF 43 00 00 00 28 31 00 1C DB 3C 1C B6 26 FF 14 B7 7E 04 B2 B0 00 2B FE 6F 00 96 8D FF 43 05 BF 20 BF 97 00 5A CE C7 17 06 37 00 03 96 5A 16 4B 4F FF AB D5 36 11 67 F0 00 5F F2 D0 07 02 C1 00 00 00 00 00 00 00 00 7D 76 7B 15 CC 6C E1 06 FF 62 AA E3 36 B8 5A 18 4C 05 1D 01 42 03 08 03 11 2A DE 76 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EC C7 96 F9 38 18 B3 49 80 1C 4E A5 D9 8C 19 EC B4 26 BE 1C AA EA 79 5 |