[Geoserver-devel] GeoMesa community module

GeoServer GeoServer Developer
1

Hi all,

I'm seeking approval to submit a GeoServer community module supporting GeoMesa's datastore (http://www.geomesa.org/). The purpose is to provide some additional data about the Hadoop ecosystem to the GeoServer user. Concretely, some of this would let users see the size of their GeoMesa tables and visualize ingest rates, etc.

Thanks,

Jim

2

Hi,

As someone that will be integrating GeoMesa, Accumulo and GeoServer into our product very soon, I give this a hearty
+1

Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.

-----Original Message-----
From: Jim Hughes [mailto:jnh5y@anonymised.com]
Sent: Friday, February 13, 2015 8:20 AM
To: geoserver-devel@lists.sourceforge.net
Subject: [Geoserver-devel] GeoMesa community module

Hi all,

I'm seeking approval to submit a GeoServer community module supporting GeoMesa's datastore (http://www.geomesa.org/). The purpose is to provide some additional data about the Hadoop ecosystem to the GeoServer user. Concretely, some of this would let users see the size of their GeoMesa tables and visualize ingest rates, etc.

Thanks,

Jim

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

3

Thanks Jim,

+1 and welcome to GeoServer :slight_smile:

One technical question - for this community module … is it able to fetch the geomesa datastore from a public repository?

As per the developers guide the next step is to send in contributor agreeements to OSGeo (see committing). When that is done send me your github ID we can set you up.

There are some notes on playing nice with others (don’t break the build) and hooking a community module into maven here. Community modules an optional profile initially, and are only included with the build/release when subject to QA/IP review.

···

On 13 February 2015 at 10:19, Jim Hughes <jnh5y@anonymised.com> wrote:

Hi all,

I’m seeking approval to submit a GeoServer community module supporting
GeoMesa’s datastore (http://www.geomesa.org/). The purpose is to
provide some additional data about the Hadoop ecosystem to the GeoServer
user. Concretely, some of this would let users see the size of their
GeoMesa tables and visualize ingest rates, etc.

Thanks,

Jim

Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett

4

On Fri, Feb 13, 2015 at 4:52 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Thanks Jim,

+1 and welcome to GeoServer :slight_smile:

One technical question - for this community module ... is it able to fetch
the geomesa datastore from a public repository?

As per the developers guide the next step is to send in contributor
agreeements to OSGeo (see committing
<http://docs.geoserver.org/latest/en/developer/policies/committing.html#comitting&gt;\).
When that is done send me your github ID we can set you up.

There are some notes on playing nice with others (don't break the build)
and hooking a community module into maven here
<http://docs.geoserver.org/latest/en/developer/policies/community-modules.html&gt;\.
Community modules an optional profile initially, and are only included with
the build/release when subject to QA/IP review.

Just a clarification here, once your module compiles in a stable way you
can add it to the nightly build profile
to have it show up here:
http://ares.boundlessgeo.com/geoserver/master/community-latest/

The community modules are only built once a day afaik, and do not build
with test
The latter, continous build with tests, is a privilege for core/extension
modules, in order to incentivize
you to satisfy the graduation requirements, which are not that scary after
all, basic things really for a module that
wants to be included in a release: tests, docs, users, and a maintainer.
More info here:
http://docs.geoserver.org/2.5.x/en/developer/policies/community-modules.html#promoting-a-community-module

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

5

Thanks Jody,

Apologies for the long, I've submitted my OSGeo paperwork and my github id is jnh5y.

I'd like to provide documentation for the module. How can I submit that info?

As for fetching the GeoMesa datastore from a public repo, the answer is yes. GeoMesa artifacts are available from LocationTech's Nexus repo. There is a subtle issue with some versions of Maven and that server at the minute.

On the other hand, the GeoMesa GeoServer module is intended to be the home for code which provides additional functionality to GeoServer related to GeoMesa GeoTools datatores.

Thanks in advance,

Jim

On 02/13/2015 10:52 AM, Jody Garnett wrote:

Thanks Jim,

+1 and welcome to GeoServer :slight_smile:

One technical question - for this community module ... is it able to fetch the geomesa datastore from a public repository?

As per the developers guide the next step is to send in contributor agreeements to OSGeo (see committing <http://docs.geoserver.org/latest/en/developer/policies/committing.html#comitting&gt;\). When that is done send me your github ID we can set you up.

There are some notes on playing nice with others (don't break the build) and hooking a community module into maven here <http://docs.geoserver.org/latest/en/developer/policies/community-modules.html&gt;\. Community modules an optional profile initially, and are only included with the build/release when subject to QA/IP review.
--
Jody

--
Jody Garnett

On 13 February 2015 at 10:19, Jim Hughes <jnh5y@anonymised.com <mailto:jnh5y@anonymised.com>> wrote:

    Hi all,

    I'm seeking approval to submit a GeoServer community module supporting
    GeoMesa's datastore (http://www.geomesa.org/). The purpose is to
    provide some additional data about the Hadoop ecosystem to the
    GeoServer
    user. Concretely, some of this would let users see the size of their
    GeoMesa tables and visualize ingest rates, etc.

    Thanks,

    Jim

    ------------------------------------------------------------------------------
    Dive into the World of Parallel Programming. The Go Parallel Website,
    sponsored by Intel and developed in partnership with Slashdot
    Media, is your
    hub for all things parallel software development, from weekly thought
    leadership blogs to news, videos, case studies, tutorials and
    more. Take a
    look and join the conversation now. http://goparallel.sourceforge.net/
    _______________________________________________
    Geoserver-devel mailing list
    Geoserver-devel@lists.sourceforge.net
    <mailto:Geoserver-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geoserver-devel

6

Thanks Jim, sent you a github invite.

Sounds like you know what is needed to add geomesa as a community module. You can copy one of the other modules as an example of how to hook a -Pgeomesa profile into community/pom.xml

For adding the location tech nexus repo you will need to update the src/pom.xml - it would be good to do that one as a pull request.

For docs have a look at http://docs.geoserver.org/latest/en/docguide/ for instructions on RST and sphinx. You can add docs for community modules here https://github.com/geoserver/geoserver/tree/master/doc/en/user/source/community

···

On 1 March 2015 at 15:53, Jim Hughes <jnh5y@…1612…> wrote:

Thanks Jody,

Apologies for the long, I’ve submitted my OSGeo paperwork and my github id is jnh5y.

I’d like to provide documentation for the module. How can I submit that info?

As for fetching the GeoMesa datastore from a public repo, the answer is yes. GeoMesa artifacts are available from LocationTech’s Nexus repo. There is a subtle issue with some versions of Maven and that server at the minute.

On the other hand, the GeoMesa GeoServer module is intended to be the home for code which provides additional functionality to GeoServer related to GeoMesa GeoTools datatores.

Thanks in advance,

Jim

On 02/13/2015 10:52 AM, Jody Garnett wrote:

Thanks Jim,

+1 and welcome to GeoServer :slight_smile:

One technical question - for this community module … is it able to fetch the geomesa datastore from a public repository?

As per the developers guide the next step is to send in contributor agreeements to OSGeo (see committing). When that is done send me your github ID we can set you up.

There are some notes on playing nice with others (don’t break the build) and hooking a community module into maven here. Community modules an optional profile initially, and are only included with the build/release when subject to QA/IP review.

–
Jody

–
Jody Garnett

–
Jody Garnett

On 13 February 2015 at 10:19, Jim Hughes <jnh5y@anonymised.com> wrote:

Hi all,

I’m seeking approval to submit a GeoServer community module supporting
GeoMesa’s datastore (http://www.geomesa.org/). The purpose is to
provide some additional data about the Hadoop ecosystem to the GeoServer
user. Concretely, some of this would let users see the size of their
GeoMesa tables and visualize ingest rates, etc.

Thanks,

Jim

Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

7

Hi Jody,

Thanks. For community module additions, should I be submitting PRs or just updating my little slice of the community directory?

Initially, I don’t think we’ll be pulling in the GeoMesa datastore from LocationTech. Once I have code and documentation up, it may become more clear what I’m doing. If you aren’t worried, maybe we can check back in at that point to make sure that I’m following the rules.

Thanks,

Jim

···

On 03/02/2015 02:00 PM, Jody Garnett wrote:

Thanks Jim, sent you a github invite.

Sounds like you know what is needed to add geomesa as a community module. You can copy one of the other modules as an example of how to hook a -Pgeomesa profile into community/pom.xml

For adding the location tech nexus repo you will need to update the src/pom.xml - it would be good to do that one as a pull request.

For docs have a look at http://docs.geoserver.org/latest/en/docguide/ for instructions on RST and sphinx. You can add docs for community modules here https://github.com/geoserver/geoserver/tree/master/doc/en/user/source/community

–
Jody Garnett

On 1 March 2015 at 15:53, Jim Hughes <jnh5y@anonymised.com> wrote:

Thanks Jody,

Apologies for the long, I’ve submitted my OSGeo paperwork and my github id is jnh5y.

I’d like to provide documentation for the module. How can I submit that info?

As for fetching the GeoMesa datastore from a public repo, the answer is yes. GeoMesa artifacts are available from LocationTech’s Nexus repo. There is a subtle issue with some versions of Maven and that server at the minute.

On the other hand, the GeoMesa GeoServer module is intended to be the home for code which provides additional functionality to GeoServer related to GeoMesa GeoTools datatores.

Thanks in advance,

Jim

On 02/13/2015 10:52 AM, Jody Garnett wrote:

Thanks Jim,

+1 and welcome to GeoServer :slight_smile:

One technical question - for this community module … is it able to fetch the geomesa datastore from a public repository?

As per the developers guide the next step is to send in contributor agreeements to OSGeo (see committing). When that is done send me your github ID we can set you up.

There are some notes on playing nice with others (don’t break the build) and hooking a community module into maven here. Community modules an optional profile initially, and are only included with the build/release when subject to QA/IP review.

–
Jody

–
Jody Garnett

On 13 February 2015 at 10:19, Jim Hughes <jnh5y@anonymised.com> wrote:

Hi all,

I’m seeking approval to submit a GeoServer community module supporting
GeoMesa’s datastore (http://www.geomesa.org/). The purpose is to
provide some additional data about the Hadoop ecosystem to the GeoServer
user. Concretely, some of this would let users see the size of their
GeoMesa tables and visualize ingest rates, etc.

Thanks,

Jim

Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

8

On Mon, Mar 2, 2015 at 9:37 PM, Jim Hughes <jnh5y@anonymised.com> wrote:

Hi Jody,

Thanks. For community module additions, should I be submitting PRs or
just updating my little slice of the community directory?

Normally the first contribution is done as a PR, if it's fine, and you
have read the developer guide and say so,
and so on, you normally get commit access in order to maintain your
community module.

If instead the PR is a long back and forth and/or you start questioning the
way the project does things
before even having commit access... uh... things might get long :wink:
(mind, not saying you are going to do that, or that you have done anything
like that so far, because
you did not, just exemplifying for the readers what might give us doubts
about giving out commit access)

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

9

We went over the basic “this way is up” overview during the OSGeo code sprint :slight_smile:

Jim I am on Skype or IRC if you need a hand getting going…

···

On 2 March 2015 at 12:56, Andrea Aime <andrea.aime@anonymised.com> wrote:

–
Jody Garnett

On Mon, Mar 2, 2015 at 9:37 PM, Jim Hughes <jnh5y@anonymised.com…> wrote:

Hi Jody,

Thanks. For community module additions, should I be submitting PRs or just updating my little slice of the community directory?

Normally the first contribution is done as a PR, if it’s fine, and you have read the developer guide and say so,
and so on, you normally get commit access in order to maintain your community module.

If instead the PR is a long back and forth and/or you start questioning the way the project does things
before even having commit access… uh… things might get long :wink:
(mind, not saying you are going to do that, or that you have done anything like that so far, because
you did not, just exemplifying for the readers what might give us doubts about giving out commit access)

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

10

Thanks Jody, Andrea,

Awesome, I’ll write back when I have a PR for the GeoMesa code which needs to move over.

Cheers,

Jim

···

On 03/02/2015 03:58 PM, Jody Garnett wrote:

We went over the basic “this way is up” overview during the OSGeo code sprint :slight_smile:

Jim I am on Skype or IRC if you need a hand getting going…

Jody

–
Jody Garnett

On 2 March 2015 at 12:56, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Mon, Mar 2, 2015 at 9:37 PM, Jim Hughes <jnh5y@anonymised.com> wrote:

Hi Jody,

Thanks. For community module additions, should I be submitting PRs or just updating my little slice of the community directory?

Normally the first contribution is done as a PR, if it’s fine, and you have read the developer guide and say so,
and so on, you normally get commit access in order to maintain your community module.

If instead the PR is a long back and forth and/or you start questioning the way the project does things
before even having commit access… uh… things might get long :wink:
(mind, not saying you are going to do that, or that you have done anything like that so far, because
you did not, just exemplifying for the readers what might give us doubts about giving out commit access)

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.