Query: All Stories

Prepare the ground for several flavours

	Include stories about projects I am a member of.

Allow spaces in command name

Allow php-http/discovery plugin to run

Add the actual script

Solved at Nasqueron by upgrading from 3.11.8 to 3.11.11.

One another occurence of this issue exists at https://ask.csdn.net/questions/7791019

Provision orange-rabbit for integration Notifications Center

All provisioned correctly, but RabbitMQ management plugin now returns a 500 when we visit the exchange notifications.

Set vhost permissions for RabbitMQ administrator account

Restore blank line before touch

Complector

$ salt dwellers state.sls roles/paas-docker/containers/rabbitmq
[…]
----------
          ID: rabbitmq_orange-rabbit_root_password
    Function: cmd.script
      Result: True
     Comment: Command 'rabbitmq_orange-rabbit_root_password' run
     Started: 23:10:16.479077
    Duration: 26894.14 ms
     Changes:
              ----------
              pid:
                  3451250
              retcode:
                  0
              stderr:
              stdout:
                  Deleting user "guest" ...
                  Adding user "root" ...
                  Done. Don't forget to grant the user permissions to some virtual hosts! See 'rabbitmqctl help set_permissions' to learn more.
                  Setting tags for user "root" to [administrator] ...
                  Setting permissions for user "root" in vhost "/" ...
[…]

Rebased. We tested deployment, we've a 401 error.

Create Laravel framework directories

OK for notifications, and also for auth-grove.

Not sure at one moment the issue was solved, with opcache it's not easy to know, but just restart the server after creating the directories wasn't enough.

Provision Notifications center integration environment

Sentry works like a charm: T1821

deploy and correct bug

Update ports information, switch from frontend container to directly use our nginx (let's avoid nginx to nginx), rebase

Add SSH key on fauve@windriver.nasqueron.org

everything is okey fauve have normally access on windriver

salt windriver state.apply roles/core/users

backend and exporter are OK

Use nasqueron/postgres-sentry image

This deployment created the incident:

Allow to use _default.conf for PaaS Docker nginx vhost

Works like a charm for Hound:

Update environment for the concept of feature flags. See https://help.penpot.app/technical-guide/configuration/. Bump PostgreSQL and Redis versions. Add Exim container so we can send mail.

A Kafka offset reset was needed:

Correct typo in sentry_post_process_forwarder_transactions

If one of the two topics lag, we'd have:

$ notification-push --project Nasqueron --group ops --service monitoring --type autoheal.kafka_offset.start --text "Containers sentry_post_process_forwarder_ have an issue. Identified as Kafka offet issue. Starting automatic healing procedure."
$ notification-push --project Nasqueron --group ops --service monitoring --type autoheal.kafka_offset.done --text "Containers sentry_post_process_forwarder_ automatic healing one. Containers should be alive."

We don't use uptime anymore.

All Stories
Use Results
Edit Query
Hide Query

Apr 6 2023

Apr 5 2023

Apr 4 2023

Apr 3 2023

Apr 2 2023