[#145612229] add session state caching support for geode - #437
[#145612229] add session state caching support for geode#437Jammy-Louie wants to merge 5 commits into
Conversation
|
Hey pivotal-Jammy-Louie! Thanks for submitting this pull request! All pull request submitters and commit authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate). When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization. If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions. Once you've publicized your membership, one of the owners of this repository can close and reopen this pull request, and dreddbot will take another look. |
nebhale
left a comment
There was a problem hiding this comment.
Before I even do a review of the code, this needs to be updated so as not to remove the contents of .idea/ and not exclude them. This information is intentionally kept under source control as it is a good indicator that your system is not setup in an authoritative way when it changes.
|
Updated the branch not to ignore .idea/ and include the infrastructural files |
| addressable (2.5.1) | ||
| public_suffix (~> 2.0, >= 2.0.2) | ||
| ast (2.3.0) | ||
| coderay (1.1.1) |
There was a problem hiding this comment.
This file should not be modified.
| connection_pool_size: 2 | ||
| geode_store: | ||
| version: 0.+ | ||
| repository_root: "https://tomcat-javabuildpack-spike.s3.amazonaws.com/geode-store" No newline at end of file |
There was a problem hiding this comment.
This doesn't seem like a production version of this bucket URI. Also, for performance reasons, buckets hosted on S3 should probably exposed via CloudFront.
There was a problem hiding this comment.
in the process of find out where i can place the tar
There was a problem hiding this comment.
If the code really is Geode, and is all backed by an ASL repository, we could host it for you.
There was a problem hiding this comment.
all but one jar is from Geode
There was a problem hiding this comment.
Where is that one file from? Is it GemFire branded?
There was a problem hiding this comment.
the jar is called pcc-client-auth
There was a problem hiding this comment.
Yeah, it'll need to be a public repository with a permissive license for us to host it. This goes back to the fact that the CFF needs to take a special exception for US export compliance that can only be satisfied by 100% open source code.
| app_dir = Pathname.new(File.expand_path(app_dir)) | ||
| Logging::LoggerFactory.instance.setup app_dir | ||
| application = Component::Application.new(app_dir) | ||
|
|
There was a problem hiding this comment.
This line should not be removed.
| TomcatLoggingSupport.new(sub_configuration_context(context, 'logging_support')), | ||
| TomcatAccessLoggingSupport.new(sub_configuration_context(context, 'access_logging_support')), | ||
| TomcatRedisStore.new(sub_configuration_context(context, 'redis_store')), | ||
| TomcatGeodeStore.new(sub_configuration_context(context, 'geode_store')), |
There was a problem hiding this comment.
This should be sorted alphabetically.
| require 'java_buildpack/container' | ||
| require 'java_buildpack/container/tomcat/tomcat_insight_support' | ||
| require 'java_buildpack/container/tomcat/tomcat_instance' | ||
| require 'java_buildpack/container/tomcat/tomcat_geode_store' |
There was a problem hiding this comment.
This should be sorted alphabetically.
| context 'when there is a session-replication service' do | ||
| before do | ||
| allow(services).to receive(:one_service?).with(/session-replication/, 'locators', 'users') | ||
| .and_return(true) |
There was a problem hiding this comment.
You'll want to run bundle exec rake to ensure that your code meets all formatting requirements. The Rubocop task will give you pointers on where the code needs to change.
| require 'java_buildpack/container/tomcat' | ||
| require 'java_buildpack/container/tomcat/tomcat_insight_support' | ||
| require 'java_buildpack/container/tomcat/tomcat_instance' | ||
| require 'java_buildpack/container/tomcat/tomcat_geode_store' |
| let(:configuration) do | ||
| { 'tomcat' => tomcat_configuration, | ||
| 'lifecycle_support' => lifecycle_support_configuration, | ||
| 'geode_store' => geode_store_configuration, |
| .to receive(:new).with(sub_configuration_context(tomcat_configuration)) | ||
| allow(JavaBuildpack::Container::TomcatLifecycleSupport) | ||
| .to receive(:new).with(sub_configuration_context(lifecycle_support_configuration)) | ||
| allow(JavaBuildpack::Container::TomcatGeodeStore) |
|
|
||
| let(:logging_support_configuration) { instance_double('logging-support-configuration') } | ||
|
|
||
| let(:geode_store_configuration) { instance_double('geode_store_configuration') } |
|
@pivotal-Jammy-Louie Also noticed that you need to take care of publicizing your CLA compliance. |
|
OK, looks like just the repository outstanding and then we can merge. Let's chat Monday morning about what the options are there. |
|
Hey pivotal-Jammy-Louie! Thanks for submitting this pull request! All pull request submitters and commit authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate). When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization. If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions. Once you've publicized your membership, one of the owners of this repository can close and reopen this pull request, and dreddbot will take another look. |
|
@pivotal-Jammy-Louie Can you please publicize your org so that the CLA is satisfied? |
|
@pivotal-Jammy-Louie We're still waiting on you to publicize your GitHub org membership to identify that you've signed the CLA. |
Signed-off-by: Emily Casey <ecasey@pivotal.io>
…lease and compile
|
Hey pivotal-Jammy-Louie! Thanks for submitting this pull request! All pull request submitters and commit authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate). When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization. If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions. Once you've publicized your membership, one of the owners of this repository can close and reopen this pull request, and dreddbot will take another look. |
|
I have my Org. I apologize for the delay |
|
Hey pivotal-Jammy-Louie! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA. |
|
Great. The PR is more or less ready to go now, after we determine the hosting thing. |
|
I think this PR is ready to be merged, please let us know @nebhale if you have more feedback on it. |
This change adds support for the Pivotal Cloud Cache as a Tomcat Session Manager. Binding to a Pivotal Cloud Cache service instance will cause Tomcat to use it as a session store. [resolves cloudfoundry#437]
|
@pivotal-Jammy-Louie I am an IBM employee working in legal team and my goal is to analyze with some software tools the source code and the license of all open sources and their dependencies to check if they can be included in our products without legal issues (in .cc a colleague working with me). Currently I'm analyzing the java buildpack 3.19 code to verify if we can include it in our code without legal problems; to do that I've to analyze it and all its dependencies chain. Now, the java buildpack 3.19 calls as dependency - with the name Apache Geode Tomcat Session Store - the zip file at:https://java-buildpack.cloudfoundry.org/geode-store/geode-store-0.0.2.tar.gz, that in turn include some jar files that seems to be NOT open source, but commercial code, Pivotal proprietary: Could you please confirm me if they are commercial code or opensource? If they are opensource could you please point me to the download location of their source. Feel free to ask us other details if you need. Thanks for your support. |
This change adds support for the Pivotal Cloud Cache as a Tomcat Session Manager. Binding to a Pivotal Cloud Cache service instance will cause Tomcat to use it as a session store. [resolves #437]
Pull request to Support Session State Caching for Pivotal Cloud Cache (Gemfire)