Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

note: AMQP configuration change #463

Merged
merged 2 commits into from
Jan 14, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions source/adminguide/events.rst
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,13 @@ in the AMQP server.
Additionally, both an in-memory implementation and an Apache Kafka
implementation are also available.


.. note::
On upgrading from 4.19.x or lower, existing AMQP or Kafka intergration
configurations should be moved from folder
``/etc/cloudstack/management/META-INF/cloudstack/core`` to
``/etc/cloudstack/management/META-INF/cloudstack/event``
Comment on lines +77 to +81
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, but should we add it to the release notes as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DaanHoogland thanks. I've added a note in about.rst as well. Please review


Use Cases
~~~~~~~~~

Expand Down Expand Up @@ -101,7 +108,7 @@ As a CloudStack administrator, perform the following one-time
configuration to enable event notification framework. At run time no
changes can control the behaviour.

#. Create the folder ``/etc/cloudstack/management/META-INF/cloudstack/core``
#. Create the folder ``/etc/cloudstack/management/META-INF/cloudstack/event``

#. Inside that folder, open ``spring-event-bus-context.xml``.

Expand Down Expand Up @@ -216,7 +223,7 @@ changes can control the behaviour.
While ``key.serializer`` and ``value.serializer`` are usually required for a producer to correctly start, they may be omitted and
will default to ``org.apache.kafka.common.serialization.StringSerializer``.

#. Create the folder ``/etc/cloudstack/management/META-INF/cloudstack/core``
#. Create the folder ``/etc/cloudstack/management/META-INF/cloudstack/event``

#. Inside that folder, open ``spring-event-bus-context.xml``.

Expand Down
7 changes: 7 additions & 0 deletions source/releasenotes/about.rst
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,10 @@ Up until 4.19.x.x, the JRE used for ACS was JRE 11. In 4.20.0.0, JRE has been up
This means that Centos7 (EL7) is no longer supported.

.. _official Log4j documentation: https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html

Events Message Bus Change
=========================
On upgrading from 4.19.x or lower, existing AMQP or Kafka intergration
configurations should be moved from folder
``/etc/cloudstack/management/META-INF/cloudstack/core`` to
``/etc/cloudstack/management/META-INF/cloudstack/event``
Loading