prabhastechie opened a new issue #221: Unable to create trigger from openwhisk 
kafka feed that listens to a Generic Kafka instance in a Local ubuntu 
installation
URL: https://github.com/apache/incubator-openwhisk-package-kafka/issues/221
 
 
   I have openwhisk _local_ installation on Ubuntu 16.04 desktop. Actions, 
triggers, rules and alarm triggers are working.
   
   I cloned the git repository 
https://github.com/apache/incubator-openwhisk-package-kafka and ran the 
following in sequence: installCatalog.sh , gradlew :distDocker, installKafka.sh
   
   Then I tried to create a trigger:
   
   ```
   bin/wsk trigger create MyKafkaTrigger -f /messaging/kafkaFeed -p brokers "
   [\"localhost:9092\", \"localhost:9093\"]" -p topic test -p isJSONData true -
   -insecure
   ```
   I am following this section of the README: "Creating a Trigger that listens 
to a Generic Kafka instance"
   
   I am re-using the Kafka instance created as part of Openwhisk installation, 
and created a topic named 'test' - I am able to publish / consume to this topic 
using kafka command line tools.
   
   The trigger creation fails (it deletes the trigger, saying resource does not 
exist).
   
   One thing I observed is that the following packages were created under 
/guest:
   
   ```
   bin/wsk package list /guest --insecurepackages
   /guest/messagingWeb                                                    
                        private
   /guest/messaging                      
   ```
   I did change the feed name to /guest/messaging/kafkFeed, only kafkaFeed, 
etc., but the results are slightly different:
   
   bin/wsk trigger create MyKafkaTrigger -f /guest/messaging/kafkaFeed -p 
   brokers "[\"localhost:9092\", \"localhost:9093\"]" -p topic test -p 
   isJSONData true --insecure
   GIVES a JSON output saying "error": "The requested resource does not exist."
   
   bin/wsk trigger create MyKafkaTrigger -f /messaging/kafkaFeed -p brokers "
   [\"localhost:9092\", \"localhost:9093\"]" -p topic test -p isJSONData true -
   -insecure
   GIVES
   
   `ok: deleted trigger MyKafkaTrigger`
   ```
   error: Unable to create trigger 'MyKafkaTrigger': Unable to invoke trigger 
   'MyKafkaTrigger' feed action '/messaging/kafkaFeed'; feed is not configured: 
   Unable to invoke action 'kafkaFeed': The supplied authentication is not 
   authorized to access this resource. (code 186)
   ```
   
   Note that I am just planning to use a Generic Kafka instance without SASL . 
username / password / kafka admin (REST) url.
   
   Later, I was advised to follow the document:
   
https://github.com/apache/incubator-openwhisk-package-kafka/blob/master/devGuide.md#install-actions
   I created a docker build and create steps there too. But the trigger still 
cannot be created.
   
   I do get expected results with the following commands:
   ```
   bin/wsk -i package list /guest
   
   packages
   /guest/messagingWeb                                                    
private
   /guest/messaging
   ```
   
   and 
   
   ```
   bin/wsk -i package get --summary /guest/messaging
   
   package /guest/messaging: Returns a result based on parameter endpoint
      (parameters: *endpoint)
    action /guest/messaging/kafkaProduce: Produce a message to a Kafka cluster
      (parameters: base64DecodeKey, base64DecodeValue, brokers, key, topic, 
value)
    feed   /guest/messaging/kafkaFeed: Feed to listen to Kafka messages
      (parameters: brokers, endpoint, isBinaryKey, isBinaryValue, isJSONData, 
topic)
   ```
   
   Also, I tried:
   ```
   bin/wsk -i property get --namespace 
   whisk namespace
   ```
   
   Then I tried unsetting the namespace: 
   `bin/wsk -i property unset --namespace`
   
   and
   
   run `trigger create` again
   
   But same error remains.
   
   _On a related note, I am not sure how the docker creation in the devGuide 
will work, since the port mapping 80:5000 will conflict with port 80 used by 
nginx. Note that this is a local installation - all in the same machine.  If we 
map it to a different port, how will the trigger know which (non-standard) port 
to connect to?_
   
   But creating the trigger should work even if the docker is not running, so 
the more fundamental question is how to create the trigger.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to