AW: Next Meetup / Hackathon
Hey, Thanks for posting the doodle. I would leave location open. Cc in Frankfurt had the better location when we are more people :) Julian Von meinem Mobiltelefon gesendet Ursprüngliche Nachricht Betreff: RE: Next Meetup / Hackathon Von: "Strljic, Matthias Milan" An: dev@plc4x.apache.org Cc: Hi all, so some anonymous PMC forced me to setup some doodle . So I just throw in some dates where I had time over the next weeks to visit the pragmatic minds HQ and to invite some friends . https://doodle.com/poll/rf3ibkv5cwa7izrd Best regards Matthias Strljic, M.Sc. Universität Stuttgart Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) Seidenstraße 36 70174 Stuttgart GERMANY Tel: +49 711 685-84530 Fax: +49 711 685-74530 E-Mail: matthias.strl...@isw.uni-stuttgart.de Web: http://www.isw.uni-stuttgart.de -Original Message- From: Julian Feinauer Sent: Monday, July 29, 2019 5:50 PM To: dev@plc4x.apache.org Subject: AW: Next Meetup / Hackathon Hey Matthias, As you are out official doodle expert... Start it :) J Von meinem Mobiltelefon gesendet Ursprüngliche Nachricht Betreff: RE: Next Meetup / Hackathon Von: "Strljic, Matthias Milan" An: dev@plc4x.apache.org Cc: + 1 The location is not so important for me as long as we have Pizza + Internet. Something in August? I am very interested in the current code generation and it would be great to get in touch with it at a hackathon, to allocate some time for PLC4X and ofc to see you all again Best regards Matthias Strljic, M.Sc. Universität Stuttgart Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) Seidenstraße 36 70174 Stuttgart GERMANY Tel: +49 711 685-84530 Fax: +49 711 685-74530 E-Mail: matthias.strl...@isw.uni-stuttgart.de Web: http://www.isw.uni-stuttgart.de -Original Message- From: Julian Feinauer Sent: Monday, July 29, 2019 11:46 AM To: dev@plc4x.apache.org Subject: Next Meetup / Hackathon Hi folks, after our last TLP Party meetup I think it would be cool to have another meetup with a more technical focus. First, we have new people on the list and contributors in jira (Kai, Volker, Mirko and Bjoern) and second we have big changes coming with the next release 0.5 like the code generation. And as I also stated, it would be good to discuss some API Extensions that I want to do. Whats your opinion on that? We would of course provide our location here but are also free to come to somewhere else. Julian PS.: And on a final note I already start to be “unterhopft” (I checked, there is no nice counterpart in English) and we have a new PMC member coming up which is eager to spend us some beer, I hope : )
RE: Next Meetup / Hackathon
Hi all, so some anonymous PMC forced me to setup some doodle . So I just throw in some dates where I had time over the next weeks to visit the pragmatic minds HQ and to invite some friends . https://doodle.com/poll/rf3ibkv5cwa7izrd Best regards Matthias Strljic, M.Sc. Universität Stuttgart Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) Seidenstraße 36 70174 Stuttgart GERMANY Tel: +49 711 685-84530 Fax: +49 711 685-74530 E-Mail: matthias.strl...@isw.uni-stuttgart.de Web: http://www.isw.uni-stuttgart.de -Original Message- From: Julian Feinauer Sent: Monday, July 29, 2019 5:50 PM To: dev@plc4x.apache.org Subject: AW: Next Meetup / Hackathon Hey Matthias, As you are out official doodle expert... Start it :) J Von meinem Mobiltelefon gesendet Ursprüngliche Nachricht Betreff: RE: Next Meetup / Hackathon Von: "Strljic, Matthias Milan" An: dev@plc4x.apache.org Cc: + 1 The location is not so important for me as long as we have Pizza + Internet. Something in August? I am very interested in the current code generation and it would be great to get in touch with it at a hackathon, to allocate some time for PLC4X and ofc to see you all again Best regards Matthias Strljic, M.Sc. Universität Stuttgart Institut für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) Seidenstraße 36 70174 Stuttgart GERMANY Tel: +49 711 685-84530 Fax: +49 711 685-74530 E-Mail: matthias.strl...@isw.uni-stuttgart.de Web: http://www.isw.uni-stuttgart.de -Original Message- From: Julian Feinauer Sent: Monday, July 29, 2019 11:46 AM To: dev@plc4x.apache.org Subject: Next Meetup / Hackathon Hi folks, after our last TLP Party meetup I think it would be cool to have another meetup with a more technical focus. First, we have new people on the list and contributors in jira (Kai, Volker, Mirko and Bjoern) and second we have big changes coming with the next release 0.5 like the code generation. And as I also stated, it would be good to discuss some API Extensions that I want to do. Whats your opinion on that? We would of course provide our location here but are also free to come to somewhere else. Julian PS.: And on a final note I already start to be “unterhopft” (I checked, there is no nice counterpart in English) and we have a new PMC member coming up which is eager to spend us some beer, I hope : )
Re: [KAFKA] Refactoring the Kafka Connect plugin?
Hi Kai, that document is exactly the one I'm currently using. What I'm currently working on is updating the current plugin to not schedule and handle the connection stuff manually, but use the scraper component of PLC4X. Also is the current configuration not production ready and I'll be working on to make it more easily usable. But it will definitely not hurt to have some Kafka Pro have a look at what we did and propose improvements. After all we want the thing to be rock-solid :-) Chris Am 31.07.19, 17:03 schrieb "Kai Wähner" : Hi Chris, great that you will work on the connector. I am not deep technical, but if you need guidance from Kafka Connect experts, I can connect you to a Confluent colleague to can help with best practices for building the connector. For example, we have implemented a wildcard option into our MQTT Connector to map MQTT Topics to Kafka Topics in a more flexible way (e.g. 1000s of cars from different MQTT Topics can be routed into 1 Kafka Topic). This might also be interesting for this connector as you expect to various PLCs. This guide might also help: https://www.confluent.io/wp-content/uploads/Verification-Guide-Confluent-Platform-Connectors-Integrations.pdf On Wed, Jul 31, 2019 at 4:39 PM Christofer Dutz wrote: > Hi all, > > I am currently planning on cleaning up the Kafka Connect adapter a little > as this was implemented as part of a proof of concept and is still I a > state I wouldn’t use in production ;-) > But a lot has happened since then and I’m planning on making it a really > usable tool in the next few days. > > A lot has changed since we created the integration module QT3 2018 and I > would like to refactor it to use the Scraper for the heavy lifting. > > Currently a user has to provide a parameter “query” which contains a > comma-separated list of connection-strings with appended address. This is > purely unmanageable. > > I would like to make it configurable via JSON or Yaml file. > > I think it would make sense to define groups of fields that are collected > on one device at an equal rate. So it’s pretty similar to the scraper > example, however I would like to not specify the source in the job, but the > other way around. > When specifying the “sources” I would also provide which jobs should run > on a given collection. > As the connector was initially showcased in a scenario where data had to > be collected on a big number of PLCs with equal specs, > I think this is the probably most important use-case and in this it is > also probably more common to add new devices to collect standard data on > than the other way around. > > Also should we provide the means to also set per connection to which > kafka-topic the data should be sent to. > We could provide the means to set a default and make it optional however. > When posting to a topic we also need to provide means for partitioning, so > I would provide sources with an optional “name”. > Each message would not only have the data requested, but also the > source-url, source-name and the job-name with a timestamp. > > So I guess it would look something like this: > > # > > # Licensed to the Apache Software Foundation (ASF) under one > # or more contributor license agreements. See the NOTICE file > # distributed with this work for additional information > # regarding copyright ownership. The ASF licenses this file > # to you under the Apache License, Version 2.0 (the > # "License"); you may not use this file except in compliance > # with the License. You may obtain a copy of the License at > # > #http://www.apache.org/licenses/LICENSE-2.0 > # > # Unless required by applicable law or agreed to in writing, > # software distributed under the License is distributed on an > # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > # KIND, either express or implied. See the License for the > # specific language governing permissions and limitations > # under the License. > # > > --- > # Defaults used throughout all collections > defaults: > # If not specified, all data goes to this topic (optional) > default-topic: some/default > > # Defines connections to PLCs > sources: > # Connection to a S7 device > - name: machineA > # PLC4X connection URL > url: s7://1.2.3.4/1/1 > jobs: > # Just references the job "s7-dashboard". All data will be published > to the default topic > - name: s7-dashboard > # References the job
