<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you Paolo,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
it seems a tricky procedure for my knowledge, but worth to be tested.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Unfortunately I'm not so used with the dev environement,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
could I test it on a mirrored test instance, and in case of positive migration, do the migration on the production instance?</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Or do you suggest me to practice with the virt env?</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I hope to have understood each step, in case I recontact you.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Cheers,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Eugenio</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Da:</b> Paolo Corti <pcorti@gmail.com><br>
<b>Inviato:</b> venerdì 25 ottobre 2019 20:19<br>
<b>A:</b> Alessio Fabiani <alessio.fabiani@geo-solutions.it><br>
<b>Cc:</b> Eugenio Trumpy <frippe12573@hotmail.com>; geonode-users@lists.osgeo.org <geonode-users@lists.osgeo.org><br>
<b>Oggetto:</b> Re: [GeoNode-users] migration suggestions</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Hi Alessio and Eugenio<br>
<br>
I could recently update a GeoNode instance from 2.4 to master (2.10.1)<br>
with not too much effort. Here are few notes I created at the time:<br>
<br>
<a href="https://gist.github.com/capooti/32071c67fb2b40b7715256d287000155">https://gist.github.com/capooti/32071c67fb2b40b7715256d287000155</a><br>
<br>
Try this method on a dev instance before applying it on production.<br>
Obviously, backup everything before doing it ;)<br>
<br>
ciao<br>
Paolo<br>
<br>
On Fri, Oct 25, 2019 at 11:26 AM Alessio Fabiani<br>
<alessio.fabiani@geo-solutions.it> wrote:<br>
><br>
> Hi Eugenio,<br>
> so, the thing is that GeoNode 2.4 and 2.10 are barely compatible. Upgrading the old version, even the look and feel, basically will require you to redo almost everything.<br>
><br>
> My suggestion was to basically update only GeoServer and the GeoServer db, start a GeoNode 2.10.x from scratch and apply the l&f customizations, then run the updatelayers command.<br>
><br>
> The updatelayers command will configure the layers into GeoNode and basically will update:<br>
><br>
> - title and abstract<br>
> - keywords<br>
> - style<br>
><br>
> All the other metadata fields must be set manually.<br>
><br>
> Trying to restore the databases is feasible, but requires a deep knowledge of Django, GeoNode model and how migration works.<br>
> In this latter case, you will need not only to patch the model, but also to update manually the "django_contentypes" in order to fixup the guardians rules, due to the model polymorphism implementation of GeoNode.<br>
><br>
><br>
> Il giorno ven 25 ott 2019 alle ore 16:58 Eugenio Trumpy <frippe12573@hotmail.com> ha scritto:<br>
>><br>
>> Hi Alessio,<br>
>><br>
>> thank you for your prompt answer. However, I have a doubts(I apologise if it is stupid) about your hints:<br>
>><br>
>> for metadata do you mean the postgresql db? in case of yes, what do you mean with 'no much', I have 42 layers in 'geonode_data' and 20 maps 116 layers and a couple of users in 'geonode' pgsql dbs. So can I dump and restore both databases? or the db structure
is changed, so that I need a special procedure?<br>
>> If I port the data only by geoserver, what I have after the updatelayers in the pgsql dbs? no metadata I presume, or only basic info taken from the old geoserver?<br>
>> What about the porting of the look and feel of the sites I have? just copy the codes?<br>
>><br>
>> Thanks a lot,<br>
>><br>
>> Eugenio<br>
>> ________________________________<br>
>> Da: Alessio Fabiani <alessio.fabiani@geo-solutions.it><br>
>> Inviato: venerdì 25 ottobre 2019 16:27<br>
>> A: Eugenio Trumpy <frippe12573@hotmail.com><br>
>> Cc: geonode-users@lists.osgeo.org <geonode-users@lists.osgeo.org><br>
>> Oggetto: Re: [GeoNode-users] migration suggestions<br>
>><br>
>> Hello Eugenio,<br>
>> in the case you have no much metadata to configure and few users, my *hot* suggestion is to pass through GeoServer in order to port your datasets.<br>
>><br>
>> So the steps would be the following ones:<br>
>><br>
>> 1. Setup a new GeoServer 2.15.2 ( <a href="https://build.geo-solutions.it/geonode/geoserver/latest/geoserver-2.15.2.war">
https://build.geo-solutions.it/geonode/geoserver/latest/geoserver-2.15.2.war</a> )<br>
>> 2. Transfer the Data Dir from the old GeoServer to the new one (I strongly suggest to backport **only** the workspace, datasets and styles, not the security subsystem)<br>
>> 3. Setup the new GeoNode instance<br>
>> 4. Run the "updatelayers" management command (see <a href="http://docs.geonode.org/en/master/admin/mgmt_commands/index.html#management-command-updatelayers">
http://docs.geonode.org/en/master/admin/mgmt_commands/index.html#management-command-updatelayers</a> )<br>
>> 5. Update manually the missing permissions and metadata<br>
>><br>
>><br>
>> Il giorno ven 25 ott 2019 alle ore 16:08 Eugenio Trumpy <frippe12573@hotmail.com> ha scritto:<br>
>><br>
>> Dear all,<br>
>><br>
>> I have a running geonode at version 2.4 dev20160525015826 configured as multisite in a ubuntu server 16.04.6 LTS.<br>
>> The system administrator suggested me to update the server OS to 18.04.3 LTS for many reasons that are not the topic of this email.<br>
>><br>
>> I would like to know if there are suggested procedures to migrate my multisite project, data, ... to a newer version of geonode<br>
>> (the most update seems to be the vs.2.10).<br>
>> Just to let you know, for the previous installation I followed the custom installation,<br>
>> because in the server were already running postgresql, tomcat, and so on...<br>
>> Moreover, as said, I set the project to be used as multi-sites.<br>
>><br>
>> So I need:<br>
>><br>
>> to install a fresh geonode version<br>
>> set-up the multi-sites<br>
>> dump the data from version 2.4<br>
>> load the data in the new version<br>
>><br>
>> Any hints or recommendations?<br>
>><br>
>> Thanks,<br>
>><br>
>> Eugenio<br>
>> _______________________________________________<br>
>> geonode-users mailing list<br>
>> geonode-users@lists.osgeo.org<br>
>> <a href="https://lists.osgeo.org/mailman/listinfo/geonode-users">https://lists.osgeo.org/mailman/listinfo/geonode-users</a><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> ==<br>
>><br>
>> GeoServer Professional Services from the experts! Visit <a href="http://goo.gl/it488V">
http://goo.gl/it488V</a> for more information.<br>
>> ==<br>
>> Ing. Alessio Fabiani<br>
>><br>
>> @alfa7691<br>
>> Founder/Technical Lead<br>
>><br>
>><br>
>> GeoSolutions S.A.S.<br>
>> Via di Montramito 3/A - 55054 Massarosa (LU) - Italy<br>
>> phone: +39 0584 962313<br>
>> fax: +39 0584 1660272<br>
>> mob: +39 331 6233686<br>
>><br>
>><br>
>> <a href="http://www.geo-solutions.it">http://www.geo-solutions.it</a><br>
>> <a href="http://twitter.com/geosolutions_it">http://twitter.com/geosolutions_it</a><br>
>> -------------------------------------------------------<br>
>><br>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è
un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.<br>
>><br>
>><br>
>> This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying,
dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.<br>
><br>
><br>
><br>
> --<br>
><br>
> ==<br>
><br>
> GeoServer Professional Services from the experts! Visit <a href="http://goo.gl/it488V">
http://goo.gl/it488V</a> for more information.<br>
> ==<br>
> Ing. Alessio Fabiani<br>
><br>
> @alfa7691<br>
> Founder/Technical Lead<br>
><br>
><br>
> GeoSolutions S.A.S.<br>
> Via di Montramito 3/A - 55054 Massarosa (LU) - Italy<br>
> phone: +39 0584 962313<br>
> fax: +39 0584 1660272<br>
> mob: +39 331 6233686<br>
><br>
><br>
> <a href="http://www.geo-solutions.it">http://www.geo-solutions.it</a><br>
> <a href="http://twitter.com/geosolutions_it">http://twitter.com/geosolutions_it</a><br>
> -------------------------------------------------------<br>
><br>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un
dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.<br>
><br>
><br>
> This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying,
dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.<br>
><br>
> _______________________________________________<br>
> geonode-users mailing list<br>
> geonode-users@lists.osgeo.org<br>
> <a href="https://lists.osgeo.org/mailman/listinfo/geonode-users">https://lists.osgeo.org/mailman/listinfo/geonode-users</a><br>
<br>
<br>
<br>
-- <br>
Paolo Corti<br>
Geospatial software developer<br>
web: <a href="http://www.paolocorti.net">http://www.paolocorti.net</a><br>
twitter: @capooti<br>
skype: capooti<br>
#drt3jc1<br>
</div>
</span></font></div>
</div>
</body>
</html>