- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Tue, Aug 4
Improve comment
Actually rewrite the file too
Avoid too many blank lines in Markdown rendering
Improve description
Mon, Aug 3
Wed, Jul 29
Revert to the cnf.sls context-variable version per dereckson: easier to see which values are configurable/pillar-dependant in roles/*.sls than in configuration templates.
Tue, Jul 28
No please revert back to the version with innodb_buffer_pool_size = {{ innodb_buffer_pool_size }}.
Address dereckson feedback: drop the innodb_buffer_pool_size context var in cnf.sls and access pillar["dbserver_mysql"]["server"]["innodb_buffer_pool_size"] directly in server.cnf instead, so it fails loudly if the server pillar block is missing rather than silently falling back via pillar.get.
Sun, Jul 26
That will be useful to implement a bunch of values for T2337
I confirm we probably don't need it on WindRiver right now.
Tested, works fine.
Thu, Jul 23
Wed, Jul 22
Tue, Jul 21
Merge the three exact-match redirect blocks (/cd, /cd/, /cd/dashboard) into a single regex location, as suggested.
Merge the three exact-match redirect blocks (/cd, /cd/, /cd/dashboard) into a single regex location, as suggested: location ~ ^/cd(?:/|/dashboard)?$ { ... }
Computed on db-B-001, got 1 Gb using POWER(1024,3) but only 139 Mb using POWER(1024,2), so we're good with the default value there for now.
Drop the redundant pillar/top.sls entry per dereckson's comment: pillar/tower.sls already auto-loads dbserver/{{ minion_id }}.sls for every minion via salt-tower, so pillar/dbserver/ysul.sls alone is enough.
I see 3 blocks with the same 302 redirect.
Mon, Jul 20
COMFIRM
Sun, Jul 19
Document HTTP/HTTPS pitfall when pulling from the local Docker registry is closed
Document HTTP/HTTPS pitfall when pulling from the local Docker registry is closed
Simplify wording per dereckson's feedback: switch to callout primary, keep only the pull URL and a brief note that localhost:5000 no longer provides a certificate.
Sat, Jul 18
Instead of documenting the error in a warning block, I'd suggest we keep a primary callout block with directly the good instructions you wrote.
Works like a charm.
To help edit vhosts, I've used the following sed expressions:
We can live with that, as there is work in progress to:
- at Nasqueron, migrate certificates to acme.sh
- on FreeBSD ports, prepare Salt for Python 3.12
It could be solved upstream with 3006.26.
@yousra It seems better with last Salt versions on 3006 LTS branch.
Fix: the pull failure was reported on docker-002, not docker-001.