[Geoserver-devel] GSIP 145 Back-up and Restore Extension for GeoServer Configuration

jive · May 31, 2016, 8:31pm

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

···

–
Jody Garnett

Alessio_Fabiani · June 1, 2016, 8:06am

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish few tasks, especially on the GeoServer Configuration workflow).

···

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

jive · June 1, 2016, 6:43pm

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the use of “variables” in resolution of connection parameters. So this GSIP could of been done as a small API / GUI change for variables — and a community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some clarifications:

a) where do the variables come from?

Introductionn: “on a file external to the data directory”
design the solution “The location where this file is placed will be configurable also via an env variable similarly to how the GeoServer data dir is setup (env variable, system variable, servlet context parameter).”

b) is their a GUI for these variables? REST API?

I expect that if this is a file it will just be reported via status extension / status page.
Not sure if you want additional details listed or logged (showing the variables).

c) Can these variables be configured on a node by node basis?

I guess the idea would be to fill in this file as part of node provisioning.

My previous feedback still applies:

Are we working too hard - introducing complexity that is already covered by Servlet API? These variables could be provided by JNDI (configured as part of the application server).

Your specific example is already covered by JNDI connection pool use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

Jetty: http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

rasters

/mnt/team_data/rasters

true

The background (/rest/br/backup/) REST API for backup/restore stuff is very cool - both technically and functionally. As mentioned it is similar to the async importer workflow and I would like see if we can combine forces - rather than have more and more async activity implementations added to GeoServer at time.

One option is to ignore this while you are working on a community module, and consider it again when you are interested making this an extension.

The second option is to think ahead to “/rest/activity” end-point would look like, define backup and restore as initial operations, and long term migrate importer, catalog reload, coveagestore statistics, bounds calculations as activities.

I apologize that the above feedback is a bit off topic for your direct need, I would be happy to work with you on an “rest activity” proposal if this is a strategic direction you agree with (or one that the PSC likes). The advantage of taking this into account now is that your customer’s REST API endpoint would not need to be migrated.

···

On 1 June 2016 at 01:06, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish few tasks, especially on the GeoServer Configuration workflow).

–
Jody Garnett

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

Alessio_Fabiani · June 3, 2016, 10:19am

Hi Jody,
thanks for your reviews and the time you spent on taking a look deeply both at the code and the proposal.

Let me try to reply to your questions.

First of all, currently I focused my energies to complete the backup & restore tool (which is almost ready, except for further feedbacks and reviews). For that reasons I still have to start the work on the configuration migration through the environment variables. This is something I’m going to face starting from the next week, so I’m open to review the technical analysis.

Since the proposal is more oriented to the backup & restore stuff, I wanted to maintain the core variable API / GUI changes less invasive as possible.
So the idea here is to put just the basis for further improvements of the configuration workflow.
I didn’t envisage any REST / GUI interfaces, but only the possibility of (optionally) use placeholders as part of the resources connection parameters in order to take the advantage of using external GeoServer environment variables to make it portable through different systems. My idea would be to create a more specific and detailed GSIP only for the configuration workflow in the future.

I’ll take a look at the serlvet API you are proposing and come back with more questions before start coding.

About the “/rest/activity” idea, I abosolutely agree with you. We need to move towards a unified platform. Lets start talking about on how to proceed and put down some ideas and directions.
We can work on this once the community module has been deeply tested, refactored if/where needed and we are it is stable. Before converting it into an official extension we can work on this common REST endpoint and then start moving the importer too.

···

On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the use of “variables” in resolution of connection parameters. So this GSIP could of been done as a small API / GUI change for variables — and a community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some clarifications:

a) where do the variables come from?

Introductionn: “on a file external to the data directory”
design the solution “The location where this file is placed will be configurable also via an env variable similarly to how the GeoServer data dir is setup (env variable, system variable, servlet context parameter).”

b) is their a GUI for these variables? REST API?

I expect that if this is a file it will just be reported via status extension / status page.
Not sure if you want additional details listed or logged (showing the variables).

c) Can these variables be configured on a node by node basis?

I guess the idea would be to fill in this file as part of node provisioning.

My previous feedback still applies:

Are we working too hard - introducing complexity that is already covered by Servlet API? These variables could be provided by JNDI (configured as part of the application server).

Your specific example is already covered by JNDI connection pool use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

Jetty: http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

rasters

/mnt/team_data/rasters

true

The background (/rest/br/backup/) REST API for backup/restore stuff is very cool - both technically and functionally. As mentioned it is similar to the async importer workflow and I would like see if we can combine forces - rather than have more and more async activity implementations added to GeoServer at time.

One option is to ignore this while you are working on a community module, and consider it again when you are interested making this an extension.

The second option is to think ahead to “/rest/activity” end-point would look like, define backup and restore as initial operations, and long term migrate importer, catalog reload, coveagestore statistics, bounds calculations as activities.

I apologize that the above feedback is a bit off topic for your direct need, I would be happy to work with you on an “rest activity” proposal if this is a strategic direction you agree with (or one that the PSC likes). The advantage of taking this into account now is that your customer’s REST API endpoint would not need to be migrated.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

–
Jody Garnett

On 1 June 2016 at 01:06, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish few tasks, especially on the GeoServer Configuration workflow).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

Alessio_Fabiani · July 5, 2016, 9:22am

Dear all,
JIRAs and PRs have been created regarding this GSIP.

The specific PR is https://github.com/geoserver/geoserver/pull/1668 but, as stated in the comments, this strictly depends on the other related Jiras.

Therefore in order to fully compile the following Jiras must be merged first:

GEOS-7611
GEOS-7613
GEOS-7614 depends-on GeoWebCache Issue #400
GEOS-7616
GEOS-7619

Nevertheless the code is there for your review.

Thank you all for your help in advance.

-A.

···

On Fri, Jun 3, 2016 at 12:19 PM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hi Jody,
thanks for your reviews and the time you spent on taking a look deeply both at the code and the proposal.

Let me try to reply to your questions.

First of all, currently I focused my energies to complete the backup & restore tool (which is almost ready, except for further feedbacks and reviews). For that reasons I still have to start the work on the configuration migration through the environment variables. This is something I’m going to face starting from the next week, so I’m open to review the technical analysis.

Since the proposal is more oriented to the backup & restore stuff, I wanted to maintain the core variable API / GUI changes less invasive as possible.
So the idea here is to put just the basis for further improvements of the configuration workflow.
I didn’t envisage any REST / GUI interfaces, but only the possibility of (optionally) use placeholders as part of the resources connection parameters in order to take the advantage of using external GeoServer environment variables to make it portable through different systems. My idea would be to create a more specific and detailed GSIP only for the configuration workflow in the future.

I’ll take a look at the serlvet API you are proposing and come back with more questions before start coding.

About the “/rest/activity” idea, I abosolutely agree with you. We need to move towards a unified platform. Lets start talking about on how to proceed and put down some ideas and directions.
We can work on this once the community module has been deeply tested, refactored if/where needed and we are it is stable. Before converting it into an official extension we can work on this common REST endpoint and then start moving the importer too.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the use of “variables” in resolution of connection parameters. So this GSIP could of been done as a small API / GUI change for variables — and a community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some clarifications:

a) where do the variables come from?

Introductionn: “on a file external to the data directory”
design the solution “The location where this file is placed will be configurable also via an env variable similarly to how the GeoServer data dir is setup (env variable, system variable, servlet context parameter).”

b) is their a GUI for these variables? REST API?

I expect that if this is a file it will just be reported via status extension / status page.
Not sure if you want additional details listed or logged (showing the variables).

c) Can these variables be configured on a node by node basis?

I guess the idea would be to fill in this file as part of node provisioning.

My previous feedback still applies:

Are we working too hard - introducing complexity that is already covered by Servlet API? These variables could be provided by JNDI (configured as part of the application server).

Your specific example is already covered by JNDI connection pool use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

Jetty: http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

rasters

/mnt/team_data/rasters

true

The background (/rest/br/backup/) REST API for backup/restore stuff is very cool - both technically and functionally. As mentioned it is similar to the async importer workflow and I would like see if we can combine forces - rather than have more and more async activity implementations added to GeoServer at time.

One option is to ignore this while you are working on a community module, and consider it again when you are interested making this an extension.

The second option is to think ahead to “/rest/activity” end-point would look like, define backup and restore as initial operations, and long term migrate importer, catalog reload, coveagestore statistics, bounds calculations as activities.

I apologize that the above feedback is a bit off topic for your direct need, I would be happy to work with you on an “rest activity” proposal if this is a strategic direction you agree with (or one that the PSC likes). The advantage of taking this into account now is that your customer’s REST API endpoint would not need to be migrated.

–
Jody Garnett

On 1 June 2016 at 01:06, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish few tasks, especially on the GeoServer Configuration workflow).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

jive · July 6, 2016, 7:28pm

Here is a link for GeoWebCache pull request 400 https://github.com/geowebcache/geowebcache/issues/400 is this what you intended?

Checking GSIP-145 we have not collected enough votes to proceed … can we kick this discussion up a notch? Thus far it has just been the two of us I would like to hear from other PSC members.

···

On 5 July 2016 at 02:22, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Dear all,
JIRAs and PRs have been created regarding this GSIP.

The specific PR is https://github.com/geoserver/geoserver/pull/1668 but, as stated in the comments, this strictly depends on the other related Jiras.

Therefore in order to fully compile the following Jiras must be merged first:

GEOS-7611

GEOS-7613

GEOS-7614 depends-on GeoWebCache Issue #400

GEOS-7616

GEOS-7619

Nevertheless the code is there for your review.

Thank you all for your help in advance.

-A.

–
Jody Garnett

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Fri, Jun 3, 2016 at 12:19 PM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hi Jody,
thanks for your reviews and the time you spent on taking a look deeply both at the code and the proposal.

Let me try to reply to your questions.

First of all, currently I focused my energies to complete the backup & restore tool (which is almost ready, except for further feedbacks and reviews). For that reasons I still have to start the work on the configuration migration through the environment variables. This is something I’m going to face starting from the next week, so I’m open to review the technical analysis.

Since the proposal is more oriented to the backup & restore stuff, I wanted to maintain the core variable API / GUI changes less invasive as possible.
So the idea here is to put just the basis for further improvements of the configuration workflow.
I didn’t envisage any REST / GUI interfaces, but only the possibility of (optionally) use placeholders as part of the resources connection parameters in order to take the advantage of using external GeoServer environment variables to make it portable through different systems. My idea would be to create a more specific and detailed GSIP only for the configuration workflow in the future.

I’ll take a look at the serlvet API you are proposing and come back with more questions before start coding.

About the “/rest/activity” idea, I abosolutely agree with you. We need to move towards a unified platform. Lets start talking about on how to proceed and put down some ideas and directions.
We can work on this once the community module has been deeply tested, refactored if/where needed and we are it is stable. Before converting it into an official extension we can work on this common REST endpoint and then start moving the importer too.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the use of “variables” in resolution of connection parameters. So this GSIP could of been done as a small API / GUI change for variables — and a community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some clarifications:

a) where do the variables come from?

Introductionn: “on a file external to the data directory”
design the solution “The location where this file is placed will be configurable also via an env variable similarly to how the GeoServer data dir is setup (env variable, system variable, servlet context parameter).”

b) is their a GUI for these variables? REST API?

I expect that if this is a file it will just be reported via status extension / status page.
Not sure if you want additional details listed or logged (showing the variables).

c) Can these variables be configured on a node by node basis?

I guess the idea would be to fill in this file as part of node provisioning.

My previous feedback still applies:

Are we working too hard - introducing complexity that is already covered by Servlet API? These variables could be provided by JNDI (configured as part of the application server).

Your specific example is already covered by JNDI connection pool use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

Jetty: http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

rasters

/mnt/team_data/rasters

true

The background (/rest/br/backup/) REST API for backup/restore stuff is very cool - both technically and functionally. As mentioned it is similar to the async importer workflow and I would like see if we can combine forces - rather than have more and more async activity implementations added to GeoServer at time.

One option is to ignore this while you are working on a community module, and consider it again when you are interested making this an extension.

The second option is to think ahead to “/rest/activity” end-point would look like, define backup and restore as initial operations, and long term migrate importer, catalog reload, coveagestore statistics, bounds calculations as activities.

I apologize that the above feedback is a bit off topic for your direct need, I would be happy to work with you on an “rest activity” proposal if this is a strategic direction you agree with (or one that the PSC likes). The advantage of taking this into account now is that your customer’s REST API endpoint would not need to be migrated.

–
Jody Garnett

On 1 June 2016 at 01:06, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish few tasks, especially on the GeoServer Configuration workflow).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

Alessio_Fabiani · July 7, 2016, 8:28am

Yep,

I understand that is a lot of stuff to digest … hopefully the others can find some time to take a look at the proposal and provide some feedbacks.

I tried to split the PRs in order to keep them as much simple and separate as possible. Also the backup&resotre stuff for the moment (as we already discussed with Jody) is a community module with the idea to merge also the importer stuff under a unique REST contest in the future (please read the previous emails in the thread).

···

On Wed, Jul 6, 2016 at 9:28 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Here is a link for GeoWebCache pull request 400 https://github.com/geowebcache/geowebcache/issues/400 is this what you intended?

Checking GSIP-145 we have not collected enough votes to proceed … can we kick this discussion up a notch? Thus far it has just been the two of us I would like to hear from other PSC members.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

–
Jody Garnett

On 5 July 2016 at 02:22, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Dear all,
JIRAs and PRs have been created regarding this GSIP.

The specific PR is https://github.com/geoserver/geoserver/pull/1668 but, as stated in the comments, this strictly depends on the other related Jiras.

Therefore in order to fully compile the following Jiras must be merged first:

GEOS-7611

GEOS-7613

GEOS-7614 depends-on GeoWebCache Issue #400

GEOS-7616

GEOS-7619

Nevertheless the code is there for your review.

Thank you all for your help in advance.

-A.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Fri, Jun 3, 2016 at 12:19 PM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hi Jody,
thanks for your reviews and the time you spent on taking a look deeply both at the code and the proposal.

Let me try to reply to your questions.

First of all, currently I focused my energies to complete the backup & restore tool (which is almost ready, except for further feedbacks and reviews). For that reasons I still have to start the work on the configuration migration through the environment variables. This is something I’m going to face starting from the next week, so I’m open to review the technical analysis.

Since the proposal is more oriented to the backup & restore stuff, I wanted to maintain the core variable API / GUI changes less invasive as possible.
So the idea here is to put just the basis for further improvements of the configuration workflow.
I didn’t envisage any REST / GUI interfaces, but only the possibility of (optionally) use placeholders as part of the resources connection parameters in order to take the advantage of using external GeoServer environment variables to make it portable through different systems. My idea would be to create a more specific and detailed GSIP only for the configuration workflow in the future.

I’ll take a look at the serlvet API you are proposing and come back with more questions before start coding.

About the “/rest/activity” idea, I abosolutely agree with you. We need to move towards a unified platform. Lets start talking about on how to proceed and put down some ideas and directions.
We can work on this once the community module has been deeply tested, refactored if/where needed and we are it is stable. Before converting it into an official extension we can work on this common REST endpoint and then start moving the importer too.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the use of “variables” in resolution of connection parameters. So this GSIP could of been done as a small API / GUI change for variables — and a community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some clarifications:

a) where do the variables come from?

Introductionn: “on a file external to the data directory”
design the solution “The location where this file is placed will be configurable also via an env variable similarly to how the GeoServer data dir is setup (env variable, system variable, servlet context parameter).”

b) is their a GUI for these variables? REST API?

I expect that if this is a file it will just be reported via status extension / status page.
Not sure if you want additional details listed or logged (showing the variables).

c) Can these variables be configured on a node by node basis?

I guess the idea would be to fill in this file as part of node provisioning.

My previous feedback still applies:

Are we working too hard - introducing complexity that is already covered by Servlet API? These variables could be provided by JNDI (configured as part of the application server).

Your specific example is already covered by JNDI connection pool use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

Jetty: http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

rasters

/mnt/team_data/rasters

true

The background (/rest/br/backup/) REST API for backup/restore stuff is very cool - both technically and functionally. As mentioned it is similar to the async importer workflow and I would like see if we can combine forces - rather than have more and more async activity implementations added to GeoServer at time.

One option is to ignore this while you are working on a community module, and consider it again when you are interested making this an extension.

The second option is to think ahead to “/rest/activity” end-point would look like, define backup and restore as initial operations, and long term migrate importer, catalog reload, coveagestore statistics, bounds calculations as activities.

I apologize that the above feedback is a bit off topic for your direct need, I would be happy to work with you on an “rest activity” proposal if this is a strategic direction you agree with (or one that the PSC likes). The advantage of taking this into account now is that your customer’s REST API endpoint would not need to be migrated.

–
Jody Garnett

On 1 June 2016 at 01:06, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish few tasks, especially on the GeoServer Configuration workflow).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

jive · July 26, 2016, 4:24pm

This work is done https://github.com/geoserver/geoserver/wiki/GSIP-145

It has one +1 from Ian, I am waiting on resolving tasks before voting myself.

···

On 7 July 2016 at 01:28, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Yep,

I understand that is a lot of stuff to digest … hopefully the others can find some time to take a look at the proposal and provide some feedbacks.

I tried to split the PRs in order to keep them as much simple and separate as possible. Also the backup&resotre stuff for the moment (as we already discussed with Jody) is a community module with the idea to merge also the importer stuff under a unique REST contest in the future (please read the previous emails in the thread).

–
Jody Garnett

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Wed, Jul 6, 2016 at 9:28 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Here is a link for GeoWebCache pull request 400 https://github.com/geowebcache/geowebcache/issues/400 is this what you intended?

Checking GSIP-145 we have not collected enough votes to proceed … can we kick this discussion up a notch? Thus far it has just been the two of us I would like to hear from other PSC members.

–
Jody Garnett

On 5 July 2016 at 02:22, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Dear all,
JIRAs and PRs have been created regarding this GSIP.

The specific PR is https://github.com/geoserver/geoserver/pull/1668 but, as stated in the comments, this strictly depends on the other related Jiras.

Therefore in order to fully compile the following Jiras must be merged first:

GEOS-7611

GEOS-7613

GEOS-7614 depends-on GeoWebCache Issue #400

GEOS-7616

GEOS-7619

Nevertheless the code is there for your review.

Thank you all for your help in advance.

-A.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Fri, Jun 3, 2016 at 12:19 PM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hi Jody,
thanks for your reviews and the time you spent on taking a look deeply both at the code and the proposal.

Let me try to reply to your questions.

First of all, currently I focused my energies to complete the backup & restore tool (which is almost ready, except for further feedbacks and reviews). For that reasons I still have to start the work on the configuration migration through the environment variables. This is something I’m going to face starting from the next week, so I’m open to review the technical analysis.

Since the proposal is more oriented to the backup & restore stuff, I wanted to maintain the core variable API / GUI changes less invasive as possible.
So the idea here is to put just the basis for further improvements of the configuration workflow.
I didn’t envisage any REST / GUI interfaces, but only the possibility of (optionally) use placeholders as part of the resources connection parameters in order to take the advantage of using external GeoServer environment variables to make it portable through different systems. My idea would be to create a more specific and detailed GSIP only for the configuration workflow in the future.

I’ll take a look at the serlvet API you are proposing and come back with more questions before start coding.

About the “/rest/activity” idea, I abosolutely agree with you. We need to move towards a unified platform. Lets start talking about on how to proceed and put down some ideas and directions.
We can work on this once the community module has been deeply tested, refactored if/where needed and we are it is stable. Before converting it into an official extension we can work on this common REST endpoint and then start moving the importer too.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the use of “variables” in resolution of connection parameters. So this GSIP could of been done as a small API / GUI change for variables — and a community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some clarifications:

a) where do the variables come from?

Introductionn: “on a file external to the data directory”
design the solution “The location where this file is placed will be configurable also via an env variable similarly to how the GeoServer data dir is setup (env variable, system variable, servlet context parameter).”

b) is their a GUI for these variables? REST API?

I expect that if this is a file it will just be reported via status extension / status page.
Not sure if you want additional details listed or logged (showing the variables).

c) Can these variables be configured on a node by node basis?

I guess the idea would be to fill in this file as part of node provisioning.

My previous feedback still applies:

Are we working too hard - introducing complexity that is already covered by Servlet API? These variables could be provided by JNDI (configured as part of the application server).

Your specific example is already covered by JNDI connection pool use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

Jetty: http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

rasters

/mnt/team_data/rasters

true

The background (/rest/br/backup/) REST API for backup/restore stuff is very cool - both technically and functionally. As mentioned it is similar to the async importer workflow and I would like see if we can combine forces - rather than have more and more async activity implementations added to GeoServer at time.

One option is to ignore this while you are working on a community module, and consider it again when you are interested making this an extension.

The second option is to think ahead to “/rest/activity” end-point would look like, define backup and restore as initial operations, and long term migrate importer, catalog reload, coveagestore statistics, bounds calculations as activities.

I apologize that the above feedback is a bit off topic for your direct need, I would be happy to work with you on an “rest activity” proposal if this is a strategic direction you agree with (or one that the PSC likes). The advantage of taking this into account now is that your customer’s REST API endpoint would not need to be migrated.

–
Jody Garnett

On 1 June 2016 at 01:06, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish few tasks, especially on the GeoServer Configuration workflow).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

Simone_Giannecchini3 · July 26, 2016, 4:45pm

Ciao Jody,
I have not understood what you mean by "I am waiting on resolving
tasks before voting myself".

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

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.

On Tue, Jul 26, 2016 at 6:24 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This work is done https://github.com/geoserver/geoserver/wiki/GSIP-145

It has one +1 from Ian, I am waiting on resolving tasks before voting
myself.

--
Jody Garnett

On 7 July 2016 at 01:28, Alessio Fabiani <alessio.fabiani@anonymised.com>
wrote:

Yep,

I understand that is a lot of stuff to digest ... hopefully the others can
find some time to take a look at the proposal and provide some feedbacks.

I tried to split the PRs in order to keep them as much simple and separate
as possible. Also the backup&resotre stuff for the moment (as we already
discussed with Jody) is a community module with the idea to merge also the
importer stuff under a unique REST contest in the future (please read the
previous emails in the thread).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

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

On Wed, Jul 6, 2016 at 9:28 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Here is a link for GeoWebCache pull request 400
https://github.com/geowebcache/geowebcache/issues/400 is this what you
intended?

Checking GSIP-145 we have not collected enough votes to proceed ... can
we kick this discussion up a notch? Thus far it has just been the two of us
I would like to hear from other PSC members.

--
Jody Garnett

On 5 July 2016 at 02:22, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Dear all,
JIRAs and PRs have been created regarding this GSIP.

The specific PR is https://github.com/geoserver/geoserver/pull/1668 but,
as stated in the comments, this strictly depends on the other related Jiras.

Therefore in order to fully compile the following Jiras must be merged
first:

GEOS-7611
GEOS-7613
GEOS-7614 depends-on GeoWebCache Issue #400
GEOS-7616
GEOS-7619

Nevertheless the code is there for your review.

Thank you all for your help in advance.

-A.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

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

On Fri, Jun 3, 2016 at 12:19 PM, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Hi Jody,
thanks for your reviews and the time you spent on taking a look deeply
both at the code and the proposal.

Let me try to reply to your questions.

First of all, currently I focused my energies to complete the backup &
restore tool (which is almost ready, except for further feedbacks and
reviews). For that reasons I still have to start the work on the
configuration migration through the environment variables. This is something
I'm going to face starting from the next week, so I'm open to review the
technical analysis.

Since the proposal is more oriented to the backup & restore stuff, I
wanted to maintain the core variable API / GUI changes less invasive as
possible.
So the idea here is to put just the basis for further improvements of
the configuration workflow.
I didn't envisage any REST / GUI interfaces, but only the possibility
of (optionally) use placeholders as part of the resources connection
parameters in order to take the advantage of using external GeoServer
environment variables to make it portable through different systems. My idea
would be to create a more specific and detailed GSIP only for the
configuration workflow in the future.

I'll take a look at the serlvet API you are proposing and come back
with more questions before start coding.

About the "/rest/activity" idea, I abosolutely agree with you. We need
to move towards a unified platform. Lets start talking about on how to
proceed and put down some ideas and directions.
We can work on this once the community module has been deeply tested,
refactored if/where needed and we are it is stable. Before converting it
into an official extension we can work on this common REST endpoint and then
start moving the importer too.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

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

On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the
use of "variables" in resolution of connection parameters. So this GSIP
could of been done as a small API / GUI change for variables --- and a
community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some
clarifications:

a) where do the variables come from?

   Introductionn: "on a file external to the data directory"
   design the solution "The location where this file is placed will be
configurable also via an env variable similarly to how the GeoServer data
dir is setup (env variable, system variable, servlet context parameter)."

b) is their a GUI for these variables? REST API?

    I expect that if this is a file it will just be reported via
status extension / status page.
    Not sure if you want additional details listed or logged (showing
the variables).

c) Can these variables be configured on a node by node basis?

    I guess the idea would be to fill in this file as part of node
provisioning.

My previous feedback still applies:

- Are we working too hard - introducing complexity that is already
covered by Servlet API? These variables could be provided by JNDI
(configured as part of the application server).

  Your specific example is already covered by JNDI connection pool
use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

  However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

  Jetty:
http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

<New class="org.eclipse.jetty.plus.jndi.EnvEntry">

  <Arg></Arg>

  <Arg>rasters</Arg>

  <Arg type="java.lang.String">/mnt/team_data/rasters</Arg>

  <Arg type="boolean">true</Arg> 

</New>

- The background (/rest/br/backup/) REST API for backup/restore stuff
is very cool - both technically and functionally. As mentioned it is similar
to the async importer workflow and I would like see if we can combine forces
- rather than have more and more async activity implementations added to
GeoServer at time.

  One option is to ignore this while you are working on a community
module, and consider it again when you are interested making this an
extension.

  The second option is to think ahead to "/rest/activity" end-point
would look like, define backup and restore as initial operations, and long
term migrate importer, catalog reload, coveagestore statistics, bounds
calculations as activities.

  I apologize that the above feedback is a bit off topic for your
direct need, I would be happy to work with you on an "rest activity"
proposal if this is a strategic direction you agree with (or one that the
PSC likes). The advantage of taking this into account now is that your
customer's REST API endpoint would not need to be migrated.

--
Jody Garnett

On 1 June 2016 at 01:06, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish
few tasks, especially on the GeoServer Configuration workflow).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

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

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett
<jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we
could get through in todays meeting:

- https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?
--
Jody Garnett

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

jive · July 26, 2016, 4:53pm

I was interested in hearing about the “/rest/activity” idea. Andrea’s feedback in today’s meeting has resolved by question - it is not a good idea as it goes against how rest is expected to be organized.

With that in mind I have added my +1 to the proposal.

···

On 26 July 2016 at 09:45, Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Ciao Jody,
I have not understood what you mean by “I am waiting on resolving
tasks before voting myself”.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

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.

On Tue, Jul 26, 2016 at 6:24 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

This work is done https://github.com/geoserver/geoserver/wiki/GSIP-145

It has one +1 from Ian, I am waiting on resolving tasks before voting
myself.

–
Jody Garnett

On 7 July 2016 at 01:28, Alessio Fabiani <alessio.fabiani@anonymised.com>
wrote:

Yep,

I understand that is a lot of stuff to digest … hopefully the others can
find some time to take a look at the proposal and provide some feedbacks.

I tried to split the PRs in order to keep them as much simple and separate
as possible. Also the backup&resotre stuff for the moment (as we already
discussed with Jody) is a community module with the idea to merge also the
importer stuff under a unique REST contest in the future (please read the
previous emails in the thread).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Wed, Jul 6, 2016 at 9:28 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Here is a link for GeoWebCache pull request 400
https://github.com/geowebcache/geowebcache/issues/400 is this what you
intended?

Checking GSIP-145 we have not collected enough votes to proceed … can
we kick this discussion up a notch? Thus far it has just been the two of us
I would like to hear from other PSC members.

–
Jody Garnett

On 5 July 2016 at 02:22, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Dear all,
JIRAs and PRs have been created regarding this GSIP.

The specific PR is https://github.com/geoserver/geoserver/pull/1668 but,
as stated in the comments, this strictly depends on the other related Jiras.

Therefore in order to fully compile the following Jiras must be merged
first:

GEOS-7611
GEOS-7613
GEOS-7614 depends-on GeoWebCache Issue #400
GEOS-7616
GEOS-7619

Nevertheless the code is there for your review.

Thank you all for your help in advance.

-A.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Fri, Jun 3, 2016 at 12:19 PM, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Hi Jody,
thanks for your reviews and the time you spent on taking a look deeply
both at the code and the proposal.

Let me try to reply to your questions.

First of all, currently I focused my energies to complete the backup &
restore tool (which is almost ready, except for further feedbacks and
reviews). For that reasons I still have to start the work on the
configuration migration through the environment variables. This is something
I’m going to face starting from the next week, so I’m open to review the
technical analysis.

Since the proposal is more oriented to the backup & restore stuff, I
wanted to maintain the core variable API / GUI changes less invasive as
possible.
So the idea here is to put just the basis for further improvements of
the configuration workflow.
I didn’t envisage any REST / GUI interfaces, but only the possibility
of (optionally) use placeholders as part of the resources connection
parameters in order to take the advantage of using external GeoServer
environment variables to make it portable through different systems. My idea
would be to create a more specific and detailed GSIP only for the
configuration workflow in the future.

I’ll take a look at the serlvet API you are proposing and come back
with more questions before start coding.

About the “/rest/activity” idea, I abosolutely agree with you. We need
to move towards a unified platform. Lets start talking about on how to
proceed and put down some ideas and directions.
We can work on this once the community module has been deeply tested,
refactored if/where needed and we are it is stable. Before converting it
into an official extension we can work on this common REST endpoint and then
start moving the importer too.

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Thanks Alessio:

Careful reading of the proposal shows one key addition to core - the
use of “variables” in resolution of connection parameters. So this GSIP
could of been done as a small API / GUI change for variables — and a
community module request. But the larger context is very helpful.

For the core variable API / GUI change I would like to ask for some
clarifications:

a) where do the variables come from?

Introductionn: “on a file external to the data directory”
design the solution “The location where this file is placed will be
configurable also via an env variable similarly to how the GeoServer data
dir is setup (env variable, system variable, servlet context parameter).”

b) is their a GUI for these variables? REST API?

I expect that if this is a file it will just be reported via
status extension / status page.
Not sure if you want additional details listed or logged (showing
the variables).

c) Can these variables be configured on a node by node basis?

I guess the idea would be to fill in this file as part of node
provisioning.

My previous feedback still applies:

Are we working too hard - introducing complexity that is already
covered by Servlet API? These variables could be provided by JNDI
(configured as part of the application server).

Your specific example is already covered by JNDI connection pool
use:

jdbc.driverClassName = “my_value”

jdbc.connectUrl = “my_value”

However we can take that to a directory value:

rasters = “/mnt/team_data/rasters”

Jetty:
http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html

rasters

/mnt/team_data/rasters

true

The background (/rest/br/backup/) REST API for backup/restore stuff
is very cool - both technically and functionally. As mentioned it is similar
to the async importer workflow and I would like see if we can combine forces

rather than have more and more async activity implementations added to
GeoServer at time.

One option is to ignore this while you are working on a community
module, and consider it again when you are interested making this an
extension.

The second option is to think ahead to “/rest/activity” end-point
would look like, define backup and restore as initial operations, and long
term migrate importer, catalog reload, coveagestore statistics, bounds
calculations as activities.

I apologize that the above feedback is a bit off topic for your
direct need, I would be happy to work with you on an “rest activity”
proposal if this is a strategic direction you agree with (or one that the
PSC likes). The advantage of taking this into account now is that your
customer’s REST API endpoint would not need to be migrated.

–
Jody Garnett

On 1 June 2016 at 01:06, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:

Hello Jody,

yes of course. Lets just have an agreement on the time schedule

By the way the development branch is available here

https://github.com/geosolutions-it/geoserver/tree/backup_restore

based on GeoServer master.

Is still under review/development (need to add more tests and finish
few tasks, especially on the GeoServer Configuration workflow).

Best Regards,
Alessio Fabiani.

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

Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

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.

On Tue, May 31, 2016 at 10:31 PM, Jody Garnett
<jody.garnett@anonymised.com> wrote:

This proposal has a lot of far reaching ideas, much more than we
could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

Jody Garnett

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev

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

–
Jody Garnett

Simone_Giannecchini3 · July 26, 2016, 4:56pm

Ciao Jody,
thanks for the quick turnaround on this.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

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.

On Tue, Jul 26, 2016 at 6:53 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

I was interested in hearing about the "/rest/activity" idea. Andrea's
feedback in today's meeting has resolved by question - it is not a good idea
as it goes against how rest is expected to be organized.

With that in mind I have added my +1 to the proposal.

--
Jody Garnett

On 26 July 2016 at 09:45, Simone Giannecchini
<simone.giannecchini@anonymised.com> wrote:

Ciao Jody,
I have not understood what you mean by "I am waiting on resolving
tasks before voting myself".

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

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.

On Tue, Jul 26, 2016 at 6:24 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:
> This work is done https://github.com/geoserver/geoserver/wiki/GSIP-145
>
> It has one +1 from Ian, I am waiting on resolving tasks before voting
> myself.
>
> --
> Jody Garnett
>
> On 7 July 2016 at 01:28, Alessio Fabiani
> <alessio.fabiani@anonymised.com>
> wrote:
>>
>> Yep,
>>
>> I understand that is a lot of stuff to digest ... hopefully the others
>> can
>> find some time to take a look at the proposal and provide some
>> feedbacks.
>>
>> I tried to split the PRs in order to keep them as much simple and
>> separate
>> as possible. Also the backup&resotre stuff for the moment (as we
>> already
>> discussed with Jody) is a community module with the idea to merge also
>> the
>> importer stuff under a unique REST contest in the future (please read
>> the
>> previous emails in the thread).
>>
>>
>>
>> Best Regards,
>> Alessio Fabiani.
>>
>> ==
>> GeoServer Professional Services from the experts!
>> Visit http://goo.gl/it488V for more information.
>> ==
>>
>> Ing. Alessio Fabiani
>> @alfa7691
>> Founder/Technical Lead
>>
>> GeoSolutions S.A.S.
>> Via di Montramito 3/A
>> 55054 Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax: +39 0584 1660272
>> mob: +39 331 6233686
>>
>> 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.
>>
>> ---------------------------------------------------------------------
>>
>>
>> On Wed, Jul 6, 2016 at 9:28 PM, Jody Garnett <jody.garnett@anonymised.com>
>> wrote:
>>>
>>> Here is a link for GeoWebCache pull request 400
>>> https://github.com/geowebcache/geowebcache/issues/400 is this what you
>>> intended?
>>>
>>> Checking GSIP-145 we have not collected enough votes to proceed ...
>>> can
>>> we kick this discussion up a notch? Thus far it has just been the two
>>> of us
>>> I would like to hear from other PSC members.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Jody Garnett
>>>
>>> On 5 July 2016 at 02:22, Alessio Fabiani
>>> <alessio.fabiani@anonymised.com> wrote:
>>>>
>>>> Dear all,
>>>> JIRAs and PRs have been created regarding this GSIP.
>>>>
>>>> The specific PR is https://github.com/geoserver/geoserver/pull/1668
>>>> but,
>>>> as stated in the comments, this strictly depends on the other related
>>>> Jiras.
>>>>
>>>> Therefore in order to fully compile the following Jiras must be
>>>> merged
>>>> first:
>>>>
>>>> GEOS-7611
>>>> GEOS-7613
>>>> GEOS-7614 depends-on GeoWebCache Issue #400
>>>> GEOS-7616
>>>> GEOS-7619
>>>>
>>>>
>>>> Nevertheless the code is there for your review.
>>>>
>>>> Thank you all for your help in advance.
>>>>
>>>> -A.
>>>>
>>>>
>>>>
>>>> Best Regards,
>>>> Alessio Fabiani.
>>>>
>>>> ==
>>>> GeoServer Professional Services from the experts!
>>>> Visit http://goo.gl/it488V for more information.
>>>> ==
>>>>
>>>> Ing. Alessio Fabiani
>>>> @alfa7691
>>>> Founder/Technical Lead
>>>>
>>>> GeoSolutions S.A.S.
>>>> Via di Montramito 3/A
>>>> 55054 Massarosa (LU)
>>>> Italy
>>>> phone: +39 0584 962313
>>>> fax: +39 0584 1660272
>>>> mob: +39 331 6233686
>>>>
>>>> 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.
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>
>>>> On Fri, Jun 3, 2016 at 12:19 PM, Alessio Fabiani
>>>> <alessio.fabiani@anonymised.com> wrote:
>>>>>
>>>>> Hi Jody,
>>>>> thanks for your reviews and the time you spent on taking a look
>>>>> deeply
>>>>> both at the code and the proposal.
>>>>>
>>>>> Let me try to reply to your questions.
>>>>>
>>>>> First of all, currently I focused my energies to complete the backup
>>>>> &
>>>>> restore tool (which is almost ready, except for further feedbacks
>>>>> and
>>>>> reviews). For that reasons I still have to start the work on the
>>>>> configuration migration through the environment variables. This is
>>>>> something
>>>>> I'm going to face starting from the next week, so I'm open to review
>>>>> the
>>>>> technical analysis.
>>>>>
>>>>> Since the proposal is more oriented to the backup & restore stuff, I
>>>>> wanted to maintain the core variable API / GUI changes less invasive
>>>>> as
>>>>> possible.
>>>>> So the idea here is to put just the basis for further improvements
>>>>> of
>>>>> the configuration workflow.
>>>>> I didn't envisage any REST / GUI interfaces, but only the
>>>>> possibility
>>>>> of (optionally) use placeholders as part of the resources connection
>>>>> parameters in order to take the advantage of using external
>>>>> GeoServer
>>>>> environment variables to make it portable through different systems.
>>>>> My idea
>>>>> would be to create a more specific and detailed GSIP only for the
>>>>> configuration workflow in the future.
>>>>>
>>>>> I'll take a look at the serlvet API you are proposing and come back
>>>>> with more questions before start coding.
>>>>>
>>>>> About the "/rest/activity" idea, I abosolutely agree with you. We
>>>>> need
>>>>> to move towards a unified platform. Lets start talking about on how
>>>>> to
>>>>> proceed and put down some ideas and directions.
>>>>> We can work on this once the community module has been deeply
>>>>> tested,
>>>>> refactored if/where needed and we are it is stable. Before
>>>>> converting it
>>>>> into an official extension we can work on this common REST endpoint
>>>>> and then
>>>>> start moving the importer too.
>>>>>
>>>>>
>>>>> Best Regards,
>>>>> Alessio Fabiani.
>>>>>
>>>>> ==
>>>>> GeoServer Professional Services from the experts!
>>>>> Visit http://goo.gl/it488V for more information.
>>>>> ==
>>>>>
>>>>> Ing. Alessio Fabiani
>>>>> @alfa7691
>>>>> Founder/Technical Lead
>>>>>
>>>>> GeoSolutions S.A.S.
>>>>> Via di Montramito 3/A
>>>>> 55054 Massarosa (LU)
>>>>> Italy
>>>>> phone: +39 0584 962313
>>>>> fax: +39 0584 1660272
>>>>> mob: +39 331 6233686
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>
>>>>> On Wed, Jun 1, 2016 at 8:43 PM, Jody Garnett
>>>>> <jody.garnett@anonymised.com>
>>>>> wrote:
>>>>>>
>>>>>> Thanks Alessio:
>>>>>>
>>>>>> Careful reading of the proposal shows one key addition to core -
>>>>>> the
>>>>>> use of "variables" in resolution of connection parameters. So this
>>>>>> GSIP
>>>>>> could of been done as a small API / GUI change for variables ---
>>>>>> and a
>>>>>> community module request. But the larger context is very helpful.
>>>>>>
>>>>>> For the core variable API / GUI change I would like to ask for some
>>>>>> clarifications:
>>>>>>
>>>>>> a) where do the variables come from?
>>>>>>
>>>>>> Introductionn: "on a file external to the data directory"
>>>>>> design the solution "The location where this file is placed will
>>>>>> be
>>>>>> configurable also via an env variable similarly to how the
>>>>>> GeoServer data
>>>>>> dir is setup (env variable, system variable, servlet context
>>>>>> parameter)."
>>>>>>
>>>>>> b) is their a GUI for these variables? REST API?
>>>>>>
>>>>>> I expect that if this is a file it will just be reported via
>>>>>> status extension / status page.
>>>>>> Not sure if you want additional details listed or logged
>>>>>> (showing
>>>>>> the variables).
>>>>>>
>>>>>> c) Can these variables be configured on a node by node basis?
>>>>>>
>>>>>> I guess the idea would be to fill in this file as part of node
>>>>>> provisioning.
>>>>>>
>>>>>> My previous feedback still applies:
>>>>>>
>>>>>> - Are we working too hard - introducing complexity that is already
>>>>>> covered by Servlet API? These variables could be provided by JNDI
>>>>>> (configured as part of the application server).
>>>>>>
>>>>>> Your specific example is already covered by JNDI connection pool
>>>>>> use:
>>>>>>
>>>>>> jdbc.driverClassName = “my_value”
>>>>>>
>>>>>> jdbc.connectUrl = “my_value”
>>>>>>
>>>>>>
>>>>>> However we can take that to a directory value:
>>>>>>
>>>>>> rasters = “/mnt/team_data/rasters”
>>>>>>
>>>>>>
>>>>>> Jetty:
>>>>>>
>>>>>> http://www.eclipse.org/jetty/documentation/9.3.x/jndi-configuration.html
>>>>>>
>>>>>> <New class="org.eclipse.jetty.plus.jndi.EnvEntry">
>>>>>>
>>>>>> <Arg></Arg>
>>>>>>
>>>>>> <Arg>rasters</Arg>
>>>>>>
>>>>>> <Arg type="java.lang.String">/mnt/team_data/rasters</Arg>
>>>>>>
>>>>>> <Arg type="boolean">true</Arg> 
>>>>>>
>>>>>> </New>
>>>>>>
>>>>>> - The background (/rest/br/backup/) REST API for backup/restore
>>>>>> stuff
>>>>>> is very cool - both technically and functionally. As mentioned it
>>>>>> is similar
>>>>>> to the async importer workflow and I would like see if we can
>>>>>> combine forces
>>>>>> - rather than have more and more async activity implementations
>>>>>> added to
>>>>>> GeoServer at time.
>>>>>>
>>>>>> One option is to ignore this while you are working on a community
>>>>>> module, and consider it again when you are interested making this
>>>>>> an
>>>>>> extension.
>>>>>>
>>>>>> The second option is to think ahead to "/rest/activity" end-point
>>>>>> would look like, define backup and restore as initial operations,
>>>>>> and long
>>>>>> term migrate importer, catalog reload, coveagestore statistics,
>>>>>> bounds
>>>>>> calculations as activities.
>>>>>>
>>>>>> I apologize that the above feedback is a bit off topic for your
>>>>>> direct need, I would be happy to work with you on an "rest
>>>>>> activity"
>>>>>> proposal if this is a strategic direction you agree with (or one
>>>>>> that the
>>>>>> PSC likes). The advantage of taking this into account now is that
>>>>>> your
>>>>>> customer's REST API endpoint would not need to be migrated.
>>>>>>
>>>>>> --
>>>>>> Jody Garnett
>>>>>>
>>>>>> On 1 June 2016 at 01:06, Alessio Fabiani
>>>>>> <alessio.fabiani@anonymised.com> wrote:
>>>>>>>
>>>>>>> Hello Jody,
>>>>>>>
>>>>>>> yes of course. Lets just have an agreement on the time schedule
>>>>>>>
>>>>>>> By the way the development branch is available here
>>>>>>>
>>>>>>> https://github.com/geosolutions-it/geoserver/tree/backup_restore
>>>>>>>
>>>>>>> based on GeoServer master.
>>>>>>>
>>>>>>> Is still under review/development (need to add more tests and
>>>>>>> finish
>>>>>>> few tasks, especially on the GeoServer Configuration workflow).
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Alessio Fabiani.
>>>>>>>
>>>>>>> ==
>>>>>>> GeoServer Professional Services from the experts!
>>>>>>> Visit http://goo.gl/it488V for more information.
>>>>>>> ==
>>>>>>>
>>>>>>> Ing. Alessio Fabiani
>>>>>>> @alfa7691
>>>>>>> Founder/Technical Lead
>>>>>>>
>>>>>>> GeoSolutions S.A.S.
>>>>>>> Via di Montramito 3/A
>>>>>>> 55054 Massarosa (LU)
>>>>>>> Italy
>>>>>>> phone: +39 0584 962313
>>>>>>> fax: +39 0584 1660272
>>>>>>> mob: +39 331 6233686
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 31, 2016 at 10:31 PM, Jody Garnett
>>>>>>> <jody.garnett@anonymised.com> wrote:
>>>>>>>>
>>>>>>>> This proposal has a lot of far reaching ideas, much more than we
>>>>>>>> could get through in todays meeting:
>>>>>>>>
>>>>>>>> - https://github.com/geoserver/geoserver/wiki/GSIP-145
>>>>>>>>
>>>>>>>> Alessio are you available for a breakout meeting to
>>>>>>>> discuss/review?
>>>>>>>> --
>>>>>>>> Jody Garnett
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Kevin_Smith1 · July 26, 2016, 7:39pm

+1

···

On 16-05-31 01:31 PM, Jody Garnett wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. [https://ad.doubleclick.net/ddm/clk/305295220;132659582;e](https://ad.doubleclick.net/ddm/clk/305295220;132659582;e)

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@anonymised.comsourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)

-- 
Kevin Michael Smith
[<smithkm@anonymised.com>](mailto:smithkm@anonymised.com)

Jukka_Rahkonen · July 26, 2016, 7:52pm

+1

-Jukka Rahkonen-

···

On 16-05-31 01:31 PM, Jody Garnett wrote:

This proposal has a lot of far reaching ideas, much more than we could get through in todays meeting:

https://github.com/geoserver/geoserver/wiki/GSIP-145

Alessio are you available for a breakout meeting to discuss/review?

–
Jody Garnett

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. [https://ad.doubleclick.net/ddm/clk/305295220;132659582;e](https://ad.doubleclick.net/ddm/clk/305295220;132659582;e)

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)

-- 
Kevin Michael Smith
[<smithkm@...3859...>](mailto:smithkm@...3859...)

[Geoserver-devel] GSIP 145 Back-up and Restore Extension for GeoServer Configuration

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Regards, Simone Giannecchini

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

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

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

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

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

Regards, Simone Giannecchini

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

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

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

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

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

Alessio are you available for a breakout meeting to discuss/review?

Regards, Simone Giannecchini

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

Regards, Simone Giannecchini

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Regards,
Simone Giannecchini

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

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

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

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

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

Regards,
Simone Giannecchini

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

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

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

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

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

Regards,
Simone Giannecchini

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

Regards,
Simone Giannecchini

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