You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rya.apache.org by Puja Valiyil <pu...@gmail.com> on 2016/08/09 14:20:19 UTC
Rya Working Group tomorrow
Hi everyone,
Tomorrow is the next Rya Working Group meeting. When we last met (a month
ago), we had discussed having a discussion about the new DynamoDB backend
for Rya. I'm fine with leading that discussion, but I was wondering if
anyone would rather we talk about something else. Perhaps a status on the
impending release?
Let me know what everyone would like to discuss -- I can prepare something
about the Dynamodb pull request if there isn't something else everyone
would like to discuss.
Thanks,
Puja
On Tue, Aug 9, 2016 at 9:57 AM, Adina Crainiceanu <ad...@usna.edu> wrote:
> FYI: Since the Java labels on the Apache Jenkins were changed, I changed
> our build incubator-rya-develop to use "JDK 1.8 (latest)" instead of
> "latest 1.8". Last build completed without problems.
>
> Adina
>
>
>
> ---------- Forwarded message ----------
> From: Gav <gm...@apache.org>
> Date: Thu, Aug 4, 2016 at 9:03 PM
> Subject: Re: Jenkins JDK Matrix - and consolidating of versions.
> To: builds <bu...@apache.org>, "infrastructure@apache.org
> Infrastructure" <
> infrastructure@apache.org>
>
>
> Hi all,
>
> Please note that today is the day 7 days have past since the 7 days notice
> that I said I was removing some
> jenkins JDK drop down options.
>
> Unfortunately a fair few projects have failed to move their builds to
> another option.
>
> Therefore I have extended by another 3 days only.
>
> I have informed all PMCs just in case the rare scenario where a PMC has no
> subscribers here.
>
> Below you will find a list of all Jenkins Jobs still using the deprecated
> drop down options.
>
> Carefully check to see if your jobs are on the list and if so please take
> action to change it.
>
> Any jobs still on the old options after this time I WILL MIGRATE THEM
> MYSELF !!!
>
> HTH
>
> Gav...
>
> Project Jobs still using :-
>
> 'latest1.8'
> =======
>
> Accumulo-master-IT
> ACE-trunk
> ActiveMQ-Artemis-Deploy
> ActiveMQ-Artemis-Master
> ActiveMQ-Artemis-Nightly-Regression-Test
> ActiveMQ-Artemis-PR-Build
> Airavata
> Ant_BuildFromPOMs
> Ant_Nightly
> Aries-rsa
> Aries-rsa
> Aries-Tx-Control-Deploy
> Aries-Tx-Control-Trunk-JDK8
> Calcite-Avatica-Master-JDK-1.8
> Calcite-Master-JDK-1.8
> Camel.trunk.fulltest.java8
> Camel.trunk.itest.karaf
> Camel.trunk.itest.osgi
> Camel.trunk.notest
> cayenne-31
> Chemistry
> cloudstack-marvin
> cloudstack-pr-analysis
> ctakes-trunk-compiletest
> ctakes-trunk-package
> CXF-trunk-deploy
> CXF-Trunk-JDK18
> CXF-Trunk-PR
> DeltaSpike-PR-Builder
> DeltaSpike_Wildfly_10.1
> DeltaSpike_Wildfly_10
> Derby-10.11-suites.All
> Derby-10.12-suites.All
> Derby-JaCoCo
> Derby-trunk
> Derby-trunk-JaCoCo
> Derby-trunk-suites.All
> Geode-nightly
> Geode-nightly-copy
> Geode-release
> Geode-spark-connector
> Groovy
> hadoop-qbt-osx-java8
> Hadoop-trunk-Commit
> hadoop-trunk-osx-java8
> hadoop-trunk-win-java8
> HBase-1.1-JDK8
> HBase-1.2
> HBase-1.2-IT
> HBase-1.3
> HBase-1.3-IT
> HBase-1.4
> HBase-Trunk-IT
> HBase-Trunk_matrix
> incubator-eagle-develop
> incubator-eagle-test
> incubator-rya-develop
> Jena_Development_Deploy
> Jena_Development_Test
> Jena_Development_Test_Windows
> johnzon-multi
> joshua_master
> karaf-pr
> Lucene-Artifacts-6.x
> Lucene-Artifacts-master
> Lucene-Solr-Clover-6.x
> Lucene-Solr-Clover-master
> Lucene-Solr-Maven-6.x
> Lucene-Solr-Maven-master
> Lucene-Solr-NightlyTests-6.x
> Lucene-Solr-NightlyTests-master
> Lucene-Solr-SmokeRelease-6.0
> Lucene-Solr-SmokeRelease-6.1
> Lucene-Solr-SmokeRelease-6.x
> Lucene-Solr-SmokeRelease-master
> Lucene-Solr-Tests-5.5-Java8
> Lucene-Solr-Tests-6.x
> Lucene-Solr-Tests-master
> Lucene-Tests-MMAP-master
> maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8_windows
> MINA-trunk-jdk1.8-ubuntu
> MINA-trunk-jdk1.8-windows
> olingo-odata4-all-profiles
> olingo-odata4-cobertura
> olingo-odata4
> Precommit-HADOOP-OSX
> PreCommit-TAJO-Build
> River-dev-jdk8
> river-JoinManagerTests
> river-JRMPactivationTests
> river-LeaseTests
> river-LookupServiceTests
> river-PolicySecurityLoaderUrlTests
> river-ReliabilityThreadTests
> river-ServiceDiscoveryManagerTests
> river-StartConfigIoIdExport
> river-TransactionTests
> ServiceMix-6.x
> ServiceMix-master
> ServiceMix-pr
> Solr-Artifacts-6.x
> Solr-Artifacts-master
> Struts-JDK8-master
> Struts-JDK9-master
> Tajo-master-nightly
> tinkerpop-master
> Tobago
> UIMAJ-SDK_java8
> ZooKeeper_branch35_jdk8
>
> 'latest1.7'
> =======
>
> Ambari-branch-1.7.0
> Ambari-branch-2.0.0
> Ambari-branch-2.1
> Ambari-branch-2.2
> Ambari-trunk-Commit
> Ambari-trunk-Commit-debug
> Ambari-trunk-test-patch
> Ambari-view
> brooklyn-master-windows
> Camel.2.15.x.fulltest
> Curator-3.0
> CXF-3.1.x
> DeltaSpike
> Empire-db
> Empire-db
> Felix-Connect
> Felix-FileInstall
> flex-falcon-w2012-test
> Geode-trunk-test-patch
> Geronimo
> Giraph-trunk-Commit
> Groovy
> Groovy
> HADOOP2_Release_Artifacts_Builder
> HBase-0.98-matrix
> HBase-1.2
> HBase-1.2-IT
> HBase-1.3
> HBase-1.3-IT
> HBase-1.4
> HBase-Trunk-IT
> HBase-Trunk_matrix
> incubator-eagle-main
> JMeter-trunk
> JMeter-Windows
> johnzon-multi
> Lucene-Solr-Tests-5.5-Java7
> maven-plugins
> maven-plugins-ITs-m3.0.4
> olingo-odata2
> PreCommit-SQOOP-Build
> PreCommit-ZOOKEEPER-Build
> Qpid-Java-Cpp-Test
> Qpid-JMS-Deploy
> Qpid-proton-c
> Reef-pull-request-ubuntu
> samza-freestyle-build
> Sqoop2-cobertura
> Sqoop2
> Sqoop-hadoop100
> Sqoop-hadoop200
> Sqoop-hadoop20
> Sqoop-hadoop23
> Struts-archetypes-JDK7-master
> Struts-JDK7-master
> Tamaya-Javadoc-Master
> Tamaya-Master-branch
> Tamaya-Site-Master
> UIMA-AS
> UIMA-SDK
> UIMA-uimaFIT
> ZooKeeper_branch34_jdk7
> ZooKeeper_branch35_jdk7
> ZooKeeper-trunk
> ZooKeeper-trunk-solaris
>
> 'latest1.6'
> =======
>
> Groovy**
> HBase-0.98-matrix
> johnzon-multi
> PreCommit-PIG-Build
>
> '1.8.0_05'
> =======
>
> ActiveMQ-Java8
> archiva-master-jdk-1.8
> PreCommit-Lens-Build
> PreCommit-Lens-Build
>
> '1.8.0_11'
> =======
>
> Apache**
> Geronimo-Specs-trunk
>
> '1.8.0_66'
> =======
>
> AuroraBot
> Aurora
> Axis2
> beam_PostCommit_MavenVerify
> beam_PostCommit_PythonVerify
> beam_PostCommit_RunnableOnService_FlinkLocal
> beam_PostCommit_RunnableOnService_GearpumpLocal
> beam_PostCommit_RunnableOnService_GoogleCloudDataflow
> beam_PostCommit_RunnableOnService_SparkLocal
> beam_PreCommit_MavenVerify
> beam_Release_NightlySnapshot
> bookkeeper-master
> build-incubator-atlas*
> CarbonData-master
> Cassandra-artifacts
> Cassandra-test-all
> Cassandra-test-burn
> Cassandra-test-cdc
> Cassandra-test-compression
> Cassandra-test
> Chukwa-master
> Commons-CRYPTO-JDK1.7
> Commons-CRYPTO-JDK1.8
> Commons-CRYPTO-JDK1.8
> distributedlog-nightly-build
> flink-github-ci
> flink-snapshot-deployment
> Fluo**
> incubator-eagle-pr-reviewer
> karaf-4.0.x
> karaf-master
> Nutch-nutchgora
> Nutch-nutchgora
> PreCommit-Lens-Build
> samza-build-post-commit
> sis-dev
> Struts-examples-JDK8-master
> tika-2.x-windows
> Tobago**
> wss4j-trunk
>
> --end list
>
>
>
>
> On Fri, Jul 29, 2016 at 9:03 PM, Gav <gm...@apache.org> wrote:
>
> > Hi All,
> >
> > So 99% of our Jenkins build machines are now puppetised with our configs
> > in our Git repos.
> > Going forward this should make things easier to maintain the software
> (and
> > versions of) on the nodes.
> >
> > I went through all the JDK drop down options available in the Jenkins UI
> > when
> > creating a build.The Confluence wiki page at :-
> >
> > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> Installation+Matrix
> >
> > lists all them all. When choosing a version to use I hope that this
> > information will
> > prove useful - any changes made we will keep this page upto date.
> > However, some are not currently installed on the new puppetised
> > slaves (on purpose) and others we intend to consolidate down to fewer
> > versions.
> >
> > In contrast, we will be able to make newer release versions available
> > quicker.
> >
> > Once we are done with the JDKs, we'll move on to Maven, and then the
> rest.
> >
> > Ok to specifics,
> >
> > First major change to get out of the way is the removal of the 'auto
> > install' JDK
> > versions. They overlap with installed versions and going forward we would
> > rather
> > manage installation via Puppet and roll them out to all slaves in one
> hit.
> >
> > Looking at the table in the linked wiki page above, this means we'll be
> > removing
> > eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> > To avoid confusion we'll also be removing the auto install 'latest1.6'
> > 'latest1.7' and 'latest1.8' options.
> >
> > The best options for 'latest' versions is the ones at the top of the
> table
> > 'JDK 1.x (Latest)'
> > which are all installed on all nodes and managed via puppet.
> >
> > I'll point out also that we have installed 'unlimited security' versions
> > of 1.6,1.7,1.8 jdks.
> >
> > Very recent addition is also that of the JDK 9 b128 Early Access Build.
> We
> > hope you enjoy
> > this addition and please do give feedback on this version to the builds@
> > mailing list so we can pass it on - but certainly do not plan to base
> your
> > releases on these 'ea' builds. I'll try my best to add new ea builds as
> > they come through.
> >
> > Last ones to mention are the IBM and Harmony versions. I'm not sure how
> > much in use
> > these are so I'm holding off on installing these for now. Please do ask
> > for a specific version
> > if needed. I'll drop the from the UI in time.
> >
> > I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> > 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from
> now,
> > along with the auto install latest links. Please plan
> > on migrating your builds away from these versions before then.
> >
> > Any follow questions, please do concentrate your email responses to the
> > builds@ mailing list.
> >
> > Thanks!
> >
> > Gav... (On behalf of the Infrastructure Team)
> >
> >
>
>
>
> --
> Dr. Adina Crainiceanu
> Associate Professor, Computer Science Department
> United States Naval Academy
> 410-293-6822
> adina@usna.edu
> http://www.usna.edu/Users/cs/adina/
>
Re: Rya Working Group tomorrow
Posted by "Ly, Kiet" <Ki...@finra.org>.
Can we talk about the Architecture roadmap?
Also can we focus our integration backend with other open source projects, HBase, Cassandra rather than commercial product like DynamoDB given this is an open source project?
I would also like to see more Spark integration and convert exist MR to use Spark processing. MR is now consider legacy framework.
On 8/9/16, 11:00 AM, "Adina Crainiceanu" <ad...@usna.edu> wrote:
Puja, thank you so much for offering to talk about DynamoDB. I'm interested
in that, but I think it would be good if we can talk about the release
tomorrow. Maybe we can figure out what needs to be done and see how
everyone can help with the release.
Thanks,
Adina
On Tue, Aug 9, 2016 at 10:20 AM, Puja Valiyil <pu...@gmail.com> wrote:
> Hi everyone,
> Tomorrow is the next Rya Working Group meeting. When we last met (a month
> ago), we had discussed having a discussion about the new DynamoDB backend
> for Rya. I'm fine with leading that discussion, but I was wondering if
> anyone would rather we talk about something else. Perhaps a status on the
> impending release?
>
> Let me know what everyone would like to discuss -- I can prepare something
> about the Dynamodb pull request if there isn't something else everyone
> would like to discuss.
>
> Thanks,
> Puja
>
>
--
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department
United States Naval Academy
410-293-6822
adina@usna.edu
http://www.usna.edu/Users/cs/adina/
Confidentiality Notice:: This email, including attachments, may include non-public, proprietary, confidential or legally privileged information. If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.
Re: Rya Working Group tomorrow
Posted by Adina Crainiceanu <ad...@usna.edu>.
Puja, thank you so much for offering to talk about DynamoDB. I'm interested
in that, but I think it would be good if we can talk about the release
tomorrow. Maybe we can figure out what needs to be done and see how
everyone can help with the release.
Thanks,
Adina
On Tue, Aug 9, 2016 at 10:20 AM, Puja Valiyil <pu...@gmail.com> wrote:
> Hi everyone,
> Tomorrow is the next Rya Working Group meeting. When we last met (a month
> ago), we had discussed having a discussion about the new DynamoDB backend
> for Rya. I'm fine with leading that discussion, but I was wondering if
> anyone would rather we talk about something else. Perhaps a status on the
> impending release?
>
> Let me know what everyone would like to discuss -- I can prepare something
> about the Dynamodb pull request if there isn't something else everyone
> would like to discuss.
>
> Thanks,
> Puja
>
>
--
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department
United States Naval Academy
410-293-6822
adina@usna.edu
http://www.usna.edu/Users/cs/adina/