AMQP 1.0 plugin in RabbitMQ - rabbitmq

Is it possibile for RabbitMQ with amqp1.0 plugin, queues act like topics?
In this docs -19th slide- I saw, Queue-s acting like topics, with non-destructive links. I just don't see is it able to(?), if yes >> where and how can configure RabbitMQ to get this behaviour.

Information provided in the documentation is well enough to add plugins
In case if you are looking for adding a AMQP1.0 plugin to the existing rabbitmq docker image
Dockerfile:
FROM rabbitmq:3-management
RUN echo '[rabbitmq_management,rabbitmq_management_visualiser,rabbitmq_amqp1_0].' > enabled_plugins
RUN rabbitmq-plugins enable rabbitmq_amqp1_0
Hope this helps.

You can activate the aqmp 1.0 plugin using rabbitmq-plugins enable rabbitmq_amqp1_0 command.
Create a config file named "rabbitmq.conf" in this path $RABBITMQ_HOME/etc/rabbitmq/
Add this content to the "rabbitmq.conf" file which you have created following the above instruction.
amqp1_0.default_user = guest
amqp1_0.default_vhost = /
amqp1_0.protocol_strict_mode = false
I followed these steps to configure my RabbitMQ to work with aqmp 1.0 version.
Documentation for reference :
https://github.com/rabbitmq/rabbitmq-amqp1.0
https://www.rabbitmq.com/configure.html#config-file
I hope this helps.

Related

How can I configure ckanext-archiver plugin for CKAN (dockerized) to make it work?

I'm using the Docker approach from here and I can't find a way to make the archiver with report and qa plugins fully working.
Apparently, the archiver plugin is not executed (the tasks for archiver update are launched and listed in the queue but not executed - don't see any archive created).
The configs for celery in production.ini are as follow:
# Before [app:main]
[app:celery]
BROKER_URL = redis://redis:6379
RESULT_BACKEND = redis://redis:6379
BROKER_BACKEND = redis
BROKER_HOST = redis://redis/1
CELERY_RESULT_BACKEND = redis
REDIS_HOST = redis
REDIS_PORT = 6379
REDIS_DB = 0
REDIS_CONNECT_RETRY = True
and the configs for Archiver
# Archiver Settings
ckanext-archiver.archive_dir=/var/lib/ckan/storage/resource_cache
ckanext-archiver.cache_url_root=http://ckan:5000/resource_cache
ckanext-archiver.max_content_length=50000000
For all 3 plugins the db schema is initiated.
Another issue, the report info in the dataset detail page is not visible
Any suggestion for the right way to configure the archiver plugin will be appreciated.
Firstly, did you included the archiver plugin in the Docker setup? If not follow this Docker as an example.
Next, the archiver can be triggered by adding a dataset with a resource or updating a resource URL using ckanext-archiver command. Please check using archiver docs.
You can also check these sh scripts, to run as cron jobs that are executing the archiver and then generate reports:
archiver.sh
report.sh

Drone Repo Add throwing error - No help topic for 'add'

Getting the following error when using drone cli to add/activate repo
No help topic for 'add'
I can confirm I am successfully login and I am an admin.
{"id":1,"login":"XXXXX","email":"","machine":false,"admin":true,"active":true,"avatar":"https://bitbucket.org/account/XXXX/avatar/32/","syncing":false,"synced":1578888217,"created":1578431775,"updated":1578891320,"last_login":1578891344}
I can also list my repo using 'drone repo ls'
My guess, if you are using the add option is that you are still interacting with drone 0.8 or below, in this case the docs have been archived to an alternate location in favor of the latest version (v1.x). The old docs are still available under the following URL and help for the add option is present there:
https://0-8-0.docs.drone.io/cli-repository-add/
If you are not using 0.8 and are indeed trying to use 1.x, perhaps you are referencing improper documentation, as this cli option shifted in v1 to enable
$ drone repo enable <repo/name>
Regardless of the versions however, you will want to ensure you both have admin access to the repository (so that drone is able to add the appropriate webhooks) and also refresh or sync your repo listing in if it is something brand new:
$ drone repo sync
username/hello-world
organization/minio
...
NOTE: This might take a bit depending on how many repos you have access to

Spinnaker:There is no stage type to be selected

After I deploy the Spinnaker with the command './InstallSpinnaker.sh' on https://github.com/spinnaker/spinnaker, but when I create the Pipeline and add stage ,I found there is no stage type to be selected, would you help on it ? thanks!
Remember this was the option for spinnaker as a dev deployment option on localdebian
Please install in a Kubernetes cluster or get easily started with Minnaker
thanks

Cannot deploy smart contract with Eris / Monax

I'm following the Getting Started Tutorial, using eris version 0.12.0
I stuck at the point where to deploy the smart contract ~/.eris/apps/idi/idi.sol
eris pkgs do --chain simplechain --address $addr
By random I get either of following two errors:
Performing action. This can sometimes take a wee while
Could not perform pkg action service: Could not perform pkg action: Docker: {"m
ssage":"Cannot link to a non running container: /simplechain-a49e7fc2-45d4-44df
83bf-1dfab6246c13 AS /interactive-67fff395-600b-4161-912b-df11dc6b2807/chain"}
or:
Performing action. This can sometimes take a wee while
Could not perform pkg action service: Docker: {"message":"Invalid container name
(.eris_tmp_-798bc8a1-70bb-45fd-ac23-8468503cdbad), only [a-zA-Z0-9][a-zA-Z0-9_.
-] are allowed"}
When I install eris version 0.11.4 the error looks like this:
Performing action. This can sometimes take a wee while
Sorry, the marmots were unable to load the eris-pm jobs file. Please check your
path.
ERROR => Unsupported Config Type ""
Container interactive-39ac3a49-52fa-4f1d-953e-1662b1af7f21 exited with status 1
I restarted Docker Quickstart Terminal several times and also deleted the default VM in VirtualBox.
What I'm doing wrong? Thanks for help!
In addition to David's answer, you also should run
eval $(docker-machine env eris) to activate the docker-image.
I had been missing the eris docker-machine running. You can check this with
docker-machine ls
And you can recreate it with:
docker-machine create -d virtualbox eris
Thanks to quick help from Monax / Eris team.

unable to install activemq-web-console in Fuse service mix

"Error executing command: URL [mvn:org.apache.activemq/activemq-web-console/5.4.0/war] could not be resolved."
is thrown up when i do features:install activemq-web-console
i am using fuse 4.3
removed the old Url for activemq from features:removeUrl and added the new one
mvn:org.apache.activemq/activemq-karaf/5.4.0/xml/features
and re-installed activemq features . if u are unable to install mvn url's then,u must add the fuse repo's to your maven settings xml.
apart from this there is a well known bug
Add the following lines to etc/system.properties
webconsole.type=properties
webconsole.jms.url=tcp://localhost:61616
webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root
webconsole.jmx.user=smx
webconsole.jmx.password=smx
this would make ur console work
For newbie follow these steps:
1. list all features using following command:
karaf#root> features:listurl
2. you can remove url using following command:
features:removeurl
you can find the url to remove in the above removeurl command from the step 1 where you list urls.
add url that you want to using following command:
features:addurl <>
and then follow steps that are mentioned by sanre6 above.