Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@syncope.apache.org
Date: Tue, 29 Mar 2016 14:33:25 +0000 (UTC)
From: =?utf-8?Q?Francesco_Chicchiricc=C3=B2_=28JIRA=29?= <jira@apache.org>
To: dev@syncope.apache.org
Message-ID: <JIRA.12924358.1451143886000.76615.1459262005551@Atlassian.JIRA>
In-Reply-To: <JIRA.12924358.1451143886000@Atlassian.JIRA>
References: <JIRA.12924358.1451143886000@Atlassian.JIRA>
 <JIRA.12924358.1451143886310@arcas>
Subject: [jira] [Updated] (SYNCOPE-753) Settle how to migrate from 1.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/SYNCOPE-753?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiricc=C3=B2 updated SYNCOPE-753:
-------------------------------------------
    Description:=20
Discuss and define a procedure for migrating Syncope 1.2 deployments to 2.0=
, and build helping tools for the purpose.

Essentially, we need:

 # a tool generating (mostly) valid {{*Content.xml}} in 2.0 format, taking =
a 1.2 {{content.xml}} (ideally exported from a 1.2 deployment)
 # a "Syncope" ConnId connector which can be used to pull users and groups =
from an existing 1.2 deployment
 # a reference migration procedure to follow

The idea is that, given an existing 1.2 deployment, one will:

 # generate a new 2.0 project
 # export {{content.xml}} from 1.2 deployment
 # run the migration tool to convert most of {{content.xml}} into some {{Ma=
sterContent.xml}} - there are some items which cannot be directly migrated,=
 as virtual schemas and related mappings
 # put the generated {{MasterContent.xml}} under {{core/src/test/resources/=
domains}} in the new 2.0 project
 # run the new 2.0 project in embedded mode while watching all logs - if er=
rors are found, make appropriate corrections into {{core/src/test/resources=
/domains/MasterContent.xml}} - this might involve migrate 1.2 customized cl=
asses into their respective 2.0 counterparts
 # once errors are gone, access the admin console in embedded mode and look=
 if every configuration item is at its place (schema, connectors, resources=
, mappings, notifications, ...)
 # manually add the items that cannot be automatically migrated
 # if using delegated administration, reconstruct roles and entitlements un=
der the [new security model|https://cwiki.apache.org/confluence/display/SYN=
COPE/[DISCUSS]+Realms#id-[DISCUSS]Realms-Newsecuritymodel]
 # verify that all operations (CRUD / propagate / synchronize / push) about=
 users and roles in 1.2 are now working (CRUD / propagate / pull / push) wi=
th users and groups in 2.0

  was:Discuss and define a procedure for migrating Syncope 1.2 deployments =
to 2.0, and build helping tools for the purpose.


> Settle how to migrate from 1.2
> ------------------------------
>
>                 Key: SYNCOPE-753
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-753
>             Project: Syncope
>          Issue Type: Task
>            Reporter: Francesco Chicchiricc=C3=B2
>            Assignee: Francesco Chicchiricc=C3=B2
>             Fix For: 2.0.0
>
>
> Discuss and define a procedure for migrating Syncope 1.2 deployments to 2=
.0, and build helping tools for the purpose.
> Essentially, we need:
>  # a tool generating (mostly) valid {{*Content.xml}} in 2.0 format, takin=
g a 1.2 {{content.xml}} (ideally exported from a 1.2 deployment)
>  # a "Syncope" ConnId connector which can be used to pull users and group=
s from an existing 1.2 deployment
>  # a reference migration procedure to follow
> The idea is that, given an existing 1.2 deployment, one will:
>  # generate a new 2.0 project
>  # export {{content.xml}} from 1.2 deployment
>  # run the migration tool to convert most of {{content.xml}} into some {{=
MasterContent.xml}} - there are some items which cannot be directly migrate=
d, as virtual schemas and related mappings
>  # put the generated {{MasterContent.xml}} under {{core/src/test/resource=
s/domains}} in the new 2.0 project
>  # run the new 2.0 project in embedded mode while watching all logs - if =
errors are found, make appropriate corrections into {{core/src/test/resourc=
es/domains/MasterContent.xml}} - this might involve migrate 1.2 customized =
classes into their respective 2.0 counterparts
>  # once errors are gone, access the admin console in embedded mode and lo=
ok if every configuration item is at its place (schema, connectors, resourc=
es, mappings, notifications, ...)
>  # manually add the items that cannot be automatically migrated
>  # if using delegated administration, reconstruct roles and entitlements =
under the [new security model|https://cwiki.apache.org/confluence/display/S=
YNCOPE/[DISCUSS]+Realms#id-[DISCUSS]Realms-Newsecuritymodel]
>  # verify that all operations (CRUD / propagate / synchronize / push) abo=
ut users and roles in 1.2 are now working (CRUD / propagate / pull / push) =
with users and groups in 2.0


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)