Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose port 9997 #14

Open
4 tasks
frgomes opened this issue Sep 10, 2018 · 5 comments
Open
4 tasks

Expose port 9997 #14

frgomes opened this issue Sep 10, 2018 · 5 comments

Comments

@frgomes
Copy link

frgomes commented Sep 10, 2018

I'm a complete newbie on geomesa, so please pardon me for my language full of uncertainties and suppositions.

Background

I'm trying to run the accumulo tutorial which apparently needs port 9997.
In order to do that, apparently I have to expose port 9997 and rebuild the Docker image.
I had troubles building this image, mainly because bigtop repository version 1.1.0 apparently vanished.

About this ticket

This ticket is intended to tag the experiments I'm doing on the docker build process.
This is a list of modifications:

  • expose port 9997
  • parameterize BIGTOP_VERSION so that next time it becomes far easier;
  • parameterize HADOOP_VERSION so that the same version is employed by all containers;
  • automate the build of the tarball, so that the build is repeatable, not requiring the developer to build the tarball beforehand.

My changes are being done at:
https://github.com/frgomes/geodocker-geomesa/tree/0014-expose_port_9997

@frgomes
Copy link
Author

frgomes commented Sep 10, 2018

Known issues

  • build geodocker-geomesa-jupyter, which I've commented out for the time being, since it's failing at the moment;
  • port 9997 is not exposed, apparently because accumulo is not running.

@elahrvivaz
Copy link
Collaborator

thanks for working on this - for 'automate the build of the tarball', it would be good to check to see if it already exists in the user's .m2 - I believe people use this to run custom builds of geomesa so they may want a particular working branch to get deployed

@frgomes
Copy link
Author

frgomes commented Sep 10, 2018

@elahrvivaz

https://raw.githubusercontent.com/frgomes/geodocker-geomesa/0014-expose_port_9997/geodocker-accumulo-geomesa/Makefile

I suppose that this definition

BUILD_TARBALL := ${HOME}/.m2/repository/org/locationtech/geomesa/geomesa-accumulo-dist_2.11/${GEOMESA_VERSION}/geomesa-accumulo-dist_2.11-${GEOMESA_VERSION}-bin.tar.gz

and this dependency

${DIST_TARBALL}: ${BUILD_TARBALL}

.. they together guarantee that the tarball is only built if necessary, correct?

@elahrvivaz
Copy link
Collaborator

Ah, I'm not sure - isn't BUILD_TARBALL a prerequisite for DIST_TARBALL then? I feel like there is another check required

@frgomes
Copy link
Author

frgomes commented Sep 11, 2018

@elahrvivaz : No worries. I will test what happens when the artifact is already there, and when it is not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants