Doug Whitfield dw@datamost.com
Minneapolis, MN, USA
Every Sunday at 1pm US Central, you can find me at https://meet.jit.si/QuarantineMusicChat
2023-03-24T14:50:01Z via datamost.com Web To: Public CC: Followers
Excited to be adding to our team!
Perforce is seeking an Open Source Software (OSS) Support Engineer to join the OpenLogic team. The ideal candidate is expected to be self-motivated, proactive, and results oriented. Our engineers are responsible for facilitating frequent and timely customer interactions via e-mail, web portal, phone, and video conferences. The OSS Support team is the tip of the spear for OpenLogic’s customers, so all candidates must possess excellent written and verbal English communication skills. They also work closely with members of our internal Sales and Professional Services, so we require a team player with a positive attitude and a willingness to listen, learn, and share knowledge. At OpenLogic we do open source right, and our people make it happen. If your skills meet any of the specs below, now is the time to apply to be a part of our passionate team.
Job Responsibilities:
Interact with end users on technical problems.
Tiers 1, 2 and 3 support for open source products.
Drive resolution to problems, which include:
#Opensource software issues
Questions around #opensourcesoftware usage
Questions around use and best practices
Review customer architecture and design implementations
Research, understand, and advocate open source software
Interact with various open source communities
Serve in case assignment rotation
Share knowledge via blogs, brown-bags, and conference session
Competencies:
Strong #Linux background required
Some programming experience required Understanding of networks and networking protocols
Experience with virtualization and containerization at scale
Database administration experience very desirable
Experience working in production environments, especially enterprise/carrier environments
Understanding of #DevOps and automation concepts
Strong troubleshooting and problem solving abilities
Fast and creative thinker, quick on their feet to respond quickly to complex and difficult problems
Proven track record of acquiring strong proficiency in new technologies quickly
Good communication skills and strong customer service orientation.
Ability to work in a 24/7, 365 day a year Support Organization, and be on rotation for critical customer issues during off business hours.
Experience:
Minimum of 3 years of software development and design or systems administration or level 3-4 technical support experience
At least 2 years in a senior position ( senior/lead developer, engineer, or DBA)
Minimum 3 years implementation and troubleshooting experience in Linux, #Java, #Kubernetes, and/or #Hadoop
Preference given to candidates with implementation and troubleshooting experience on other broadly adopted open source technologies (e.g. #Kafka, #Spark, #Solr, #ActiveMQ, #RabbitMQ, #Artemis, #Tomcat, #Wildfly, #CentOS, #DockerCE, #InfluxDB, #Cassandra, etc)
Experience working with a geographically dispersed virtual team.2023-03-22T01:18:34Z via datamost.com Web To: Public CC: Followers
Unclear if this is a change in policy. We've never had anyone tied to an office in the US in OpenLogic. There are some other things that don't make a lot of sense in the listing. I'm following up to make sure those are as the are supposed to be. I'll post in the comments or edit as necessary.
Perforce is seeking an OSS Services Engineer to join the OpenLogic team. Under remote supervision, this engineer will use their knowledge and skills from previous experience and from on-the-job training to contribute to projects that deliver mission critical open-source software solutions to our customers in complex distributed environments.
Interact with end users on technical problems
Deliver professional services and training engagements
Drive resolution to problems, which include:
Open-source software issues
Questions around open-source software usage
Questions around use and best practices
Review customer architecture and design implementations
Research, understand, and advocate open-source software
Interact with various open source communities
Assist the broader OpenLogic team with thorny Tier 4 level open-source problems
Requirements:
10+ years of software development and design, enterprise architecture, or systems administration or level 3-4 technical support experience
At least 2 years in a senior position ( senior/lead developer, engineer, or DBA)
Minimum 3 years implementation and troubleshooting experience in #Linux, #Java, #Kubernetes, and/or #Hadoop
5+ years of hands-on experience working with a combination of SQL and NoSQL database technologies (e.g. Oracle, #MySQL/ #MariaDB, #Postgres, #MongoDB, #Cassandra, Neo4j/ #JanusGraph)
Experience working with a geographically dispersed virtual team
Strong Linux background
Strong SQL and NoSQL background
Some programming experience
Understanding of networks and networking protocols
Experience with virtualization and containerization at scale
Experience working in production environments, especially enterprise/carrier environments
Understanding of DevOps and automation concepts
Strong troubleshooting and problem solving abilities
Fast and creative thinker, quick on their feet to respond quickly to complex and difficult problems
Proven track record of acquiring strong proficiency in new technologies quickly
Effective communication skills and strong customer service orientation
Experience speaking at conferences/comfortable speaking in front of large crowds
Nice-to-have:
Preference given to candidates with implementation and troubleshooting experience on other broadly adopted open-source technologies and CNCF technologies (e.g. #Kafka, #Spark, #Nifi, #Flink, Elasticsearch, #Solr, Vault, Keycloak, #ActiveMQ/RabbitMQ/Artemis, #Redis, Tomcat/Wildfly, CentOS/Rocky/SLES, Docker/Podman, etc.)
Preference given to candidates with experience in DevOps automation tools like #Jenkins, Ansible, #Terraform, Nexus/Artifactory, #GitLab/ #GitHubDatabase administration experience very desirablealright, so the Totalview piece on the actual listing was removed. I had already removed it assuming that was incorrect2023-03-21T21:09:19Z via datamost.com Web To: Public CC: Followers
I would like to set the max message mentioned in https://github.com/apache/activemq/blob/d48cf3758312a25122508854946c399a2e6f6f69/activemq-web/src/ma... -- where exactly do I do that?2023-03-19T23:04:32Z via datamost.com Web To: Public CC: Followers
Next week Sam Austin and I will be hosting the CC Listening Party without Donnie Ozone. This is a huge bummer, but also an opportunity!Are you a musician? Do you release under a Creative Commons license? Do you have videos? More time to share your stuff!Do these things apply to your friends? Share this info with your friends if so!1pm US Central we show up at https://meet.jit.si/quarantinemusicchat -- no account necessaryHere's our most popular show if you want to see how we get down: https://www.youtube.com/watch?v=Mk6CBCrojyA&t=5s2023-03-14T19:43:54Z via datamost.com Web To: Public CC: Followers
I would like to use jlink to create a customized JRE within our own compiled OpenJDK version.
I use this guide to compile my OpenJDK version 17:
https://wiki.openjdk.org/display/OpenJFX/Building+OpenJFX
The used version is: git clone https://github.com/openjdk/jfx17u
Basically the compilation (bash configure, and make images) is successful and I am able to run java.
bash configure –with-boot-jdk=/cygdrive/c/jdk1602
make images
openjdk@debian10-uni:~/Java17/jdk17u/build/linux-x86_64-server-release/jdk/bin$ ./java -version
openjdk version "17.0.7-internal" 2023-04-18
OpenJDK Runtime Environment (build 17.0.7-internal+0-adhoc.openjdk.jdk17u)
OpenJDK 64-Bit Server VM (build 17.0.7-internal+0-adhoc.openjdk.jdk17u, mixed mode)
Now I use jlink to customize the JRE. The command is this one:
openjdk@debian10-uni:~/Java17/jdk17u/build/linux-x86_64-server-release/jdk/bin$ ./jlink —add-modules java.base —module-path ../../images/jmods —output my-jre
The result is this:
Error: java.io.UncheckedIOException: java.nio.channels.ClosedChannelException
If I replace the module java.bases with "—add-modules ALL-MODULE-PATH" then the result is this:
WARNING: Using incubator modules: jdk.incubator.foreign, jdk.incubator.vector
Error: java.io.UncheckedIOException: java.nio.channels.ClosedChannelException
Doing the same with a pre-compiled version https://jdk.java.net/archive ((build 17.0.2+8) then jlink is working fine and it creates my-jre and the command "java -version" runs successfully.
I tried already to use jlink from the downloaded JDK and the jmods from my compiled version. This is working as well. But using jlink from my own compiled version with jmods from the download JDK does not work.
Do you have an idea, what’s wrong there? Does jlink have a bug in 17.0.7? How can I overcome this problem?2022-10-05T18:09:30Z via datamost.com Web To: Public CC: Followers
Anybody got any #ApacheAirflow podcast suggestions?2022-09-20T21:07:32Z via datamost.com Web To: Public CC: Followers
Anybody got any #influxdb podcast suggestions?2022-08-30T22:00:53Z via datamost.com Web To: Public CC: Followers
Is there a #CentOS 7 repo that has #maven 3.1 or greater?McClane shared this.
2022-08-11T16:36:42Z via datamost.com Web To: Public CC: Followers
Any #Telegraf or #TICK-stack related podcast suggestions?2022-06-30T21:11:26Z via datamost.com Web To: Public CC: Followers
Does #apachetomcat have a code review process? I Know there are votes before releases, but I don't see any review athttps://gitbox.apache.org/repos/asf?p=tomcat.git;a=commit;h=76115a2a8681e5951aef9037120fa3babeffd9d3-- It may just be that I don't know much about gitbox though2022-06-29T17:16:18Z via datamost.com Web To: Public CC: Followers
Been a while, mostly because low engagement here, but I've got an intractable issue. No help so far from the JanusGraph gitter.
Anybody got any ideas on the next direction to go after discovery that I have 11 threads waiting on this one?Here’s the offending thread. 0x00007f6ecc104b30 is the problem:"gremlin-server-exec-4" #134 prio=5 os_prio=0 tid=0x00007f6d48004800 nid=0x171a4a runnable [0x00007f6cd05ef000]java.lang.Thread.State: RUNNABLE…Locked ownable synchronizers:- <0x00007f6ecc104b30> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)- <0x00007f6ecee7c9b8> (a java.util.concurrent.ThreadPoolExecutor$Worker)These 11 threads are waiting on gremlin-server-exec-4 to give up that lock:gremlin-server-exec-2, gremlin-server-exec-60, gremlin-server-exec-58, gremlin-server-exec-54, gremlin-server-exec-49, gremlin-server-exec-47, gremlin-server-exec-43, gremlin-server-exec-32, gremlin-server-exec-16, gremlin-server-exec-14, gremlin-server-exec-122022-04-01T00:14:17Z via datamost.com Web To: Public CC: Followers
had no idea this was a thing until today. I guess there's how entrenched in the CC Music scene I am: https://www.youtube.com/watch?v=rId6PKlDXeU
Oh, my life loves Mumford & Sons, so really surprised I never knew about this.2022-03-11T17:42:12Z via datamost.com Web To: Public CC: Followers
Is it possible to get TIME_WAIT status through #jmx? #java #openjdk2022-03-07T21:51:22Z via datamost.com Web To: Public CC: Followers
Anybody got an #ApacheArtemis tutorial they can suggest?2022-02-14T20:07:05Z via datamost.com Web To: Public CC: Followers
2021-12-28T22:37:21Z via datamost.com Web To: Public CC: Followers
I think there is some exciting news coming to the Creative Commons Community Music Awards, possibly as soon as tomorrow.2021-12-14T22:53:55Z via datamost.com Web To: Public CC: Followers
images not on datamost don't seem to be coming through. That's a bummer
Yep, there's an issue with the ProxyURLs.
@Jason Self looked at it but I don't think he found the problem...
2021-12-14T22:51:27Z via datamost.com Web To: Public CC: Followers
If anybody knows keycloak, I would love someone to jump in on this:
https://github.com/keycloak/keycloak/discussions/8874
So you don't have to click through:
I've been supporting a Kerberos-integrated Keycloak use case recently, and I'd like to ask if the premise of the PR we'd like to submit is secure before submitting it. Some background on where we are at: I can use my Kerberos ticket on my browser to log in, and can also, using a forwardable ticket, obtain a JWT with curl, for example: curl -k --negotiate --delegation policy -u : --location --request POST 'https://keycloak.ipa.test/auth/realms/Test/protocol/openid-connect/token' --data-urlencode 'client_id=grafana.ipa.test' --data-urlencode 'client_secret=my-secret-token' -d 'grant_type=password' -d 'scope=openid profile email' -vvvv This gives me gss_delegation_credential in my JWT as I expect. In this case, I'm trying to access an OIDC-integrated grafana instance, and I've got FreeIPA doing Kerberos and LDAP. Everything here works. The trouble we ran into was that we'd like some of our existing software that obtains JWTs from Keycloak through the Java API wasn't integrated with Kerberos. So, for certain rigid deployments at customer sites, we need to provide that gss_delegation_credential to a service that expects GSSAPI. This software is not in a place where we can add Kerberos functionality quickly, so doing things like implementing a keytab and GSSAPI to imitate the success we've had with the above curl command is out of reach for us at the moment. What we'd like to do is ask Keycloak for a password-based grant, have that request get authenticated by Keycloak via Kerberos, and have Keycloak obtain and append the gss_delegation_credential to the JWT for us. We have a PR that we'd like to submit, and we've tested that it achieves the objectives that we've set out to accomplish. However, I'd like to ask the community if this is, prima facie, a supportable flow in Keycloak, or if we're violating some kind of Kerberos prime directive here :) Also in the realm of possibilities is the idea that Keycloak supports this but we're doing it wrong! What should our next steps be? Can Keycloak provide gss_delegation_credential in the returned JWT on behalf of a successful password grant if integrated with Kerberos? If not, does the community believe this could be done securely? If so, do you want us to submit a PR of what we already have? Thanks!2021-10-21T14:49:42Z via datamost.com Web To: Public CC: Followers
Anybody building #linux distros with #jenkins? Seems like the 30 second timeout is a bad match. I'd love to know what type of disks you are using, and particularly if you are using VM or bare metal.2021-09-23T20:41:36Z via datamost.com Web To: Public CC: Followers
Any thoughts from #apachekafka #kafka experts?
1. for a topic with 3 partitions, there is a broker lead for each partition and a single publisher (round-robin) will publish to all three broker leaders. Correct?
2. for a topic with 3 partitions and three publisher instances running, each publisher would use all three broker leaders. The three publisher instances wouldn’t be aligned specifically to one of the three broker leaders. Correct?
3. Rather than developing a model for dividing the work among publishers, wouldn’t the publisher offset internal topic manage that? it is supposed to help the publisher understand where it is in publishing events and where to start looking for the next event to publish. This would only work for a three publisher model if the publishers shared the internal publisher offset topic. I’m assuming that isn’t the case? each publisher instance would have its own internal offset topic?For the curious, here's an answer I got from a colleague:
#1 for a topic with 3 partitions, there is a broker lead for each partition and a single publisher (round-robin) will publish to all three broker leaders. Correct?
For a topic with 3 partitions, there is a broker-leader for each partition and a single publisher, should they configure their ProducerRecord (https://kafka.apache.org/25/javadoc/org/apache/kafka/clients/producer/ProducerRecord.html) to have neither a key nor a partition present then a partition will be assigned in a round-robin fashion. Because the topic partition is the unit of replication (https://kafka.apache.org/documentation/#replication), and each partition in Kafka has a single broker-leader for which all reads and writes go through that leader, it is correct to say that a single publisher will publish to all three broker leaders.
#2 for a topic with 3 partitions and three publisher instances running, each publisher would use all three broker leaders. Correct. The three publisher instances wouldn’t be aligned specifically to one of the three broker leaders. Correct?
If each publisher was configured to create a ProducerRecord<K,V> that went to a specific partition, then this might be the case. However, if the three publishers, totally independently and unaware of each other, were configured to create ProducerRecords that used a specific partition, this might not be the case. Ultimately, it is up to the producer to decide which partition they are writing to, or to trust the hashing or round-robin distribution assigned by the broker.
#3 Rather than developing a model for dividing the work among publishers, wouldn’t the publisher offset internal topic manage that? it is supposed to help the publisher understand where it is in publishing events and where to start looking for the next event to publish. This would only work for a three publisher model if the publishers shared the internal publisher offset topic. I’m assuming that isn’t the case? each publisher instance would have its own internal offset topic?
If you’re referring to the idea that a publisher can store its current offset in a Kafka topic, and coordinate with other publishers working in tandem with it by relying on the committed topic offset, I’d like to clarify some terms first. If a producer is also a consumer, the consumer facet or nature of this worker/thread/app/route is what contains the offset. If you were consuming files from a network share, for example, you might move them to a hidden folder or delete them when you were done consuming them for publication onto a kafka topic, a simple but effective way of marking which files have been consumed and published and which are ready for consumption. In Kafka, the offset refers to the latest available message in the topic. So here, I’m assuming you mean your producer is also a kafka consumer, and is doing some work like enrichment before publishing the completed work to another topic for further processing.
If you want to coordinate between consumer-producers in this way, I would create a single topic with a single message type, but publish messages from each consumer-producer with a header stating which one is which. Then, on startup of the consumer-producer, you can consume a message first from the offset topic, filter for the header to determine which offset message belongs to the individual worker, and then start a stream at the offset it acquires.Just got this from the customer:
"I don’t think I did a good job presenting point 3 to you. This was in the context of a Kafka Connect Publisher (Source).. I didn’t do a lot of homeowrk on this but the idea is that Kafka Connect keeps track of where the publisher is in publishing from a source (database). https://docs.confluent.io/platform/6.2.1/connect/javadocs/javadoc/org/apache/kafka/connect/source/So...
I think the response to point 3 was in regards to the standard Java Publisher API and not considering connect. Can I get an alternative response considering Kafka Connect Publishers?"
