Re: [onap-tsc] Migration to *.onap.org

[SPATSCHECK, OLIVER (OLIVER)]

Also not sure if it is entirely black and white. There might be some projects 
we can move in the R1 timeframe if we allow for one project at a time 
migration. Then the PTL can make that choice based on there workload and 
project complexity.

Oliver

> On Aug 4, 2017, at 2:44 AM  EDT, LEFEVRE, CATHERINE <cl6...@intl.att.com> 
> wrote:
> 
> ***Security Advisory: This Message Originated Outside of AT ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> 
> Good morning Stephen,
>  
> Thank you for your feedback.
>  
> I will definitively finalize the high level plan as requested and will 
> organize a call accordingly in the coming days.
> I will also consider Gildas’ feedback based on the discussions we had with 
> the LF Council.
>  
> Best regards
> Catherine
>  
> From: Stephen Terrill [mailto:stephen.terr...@ericsson.com] 
> Sent: Thursday, August 03, 2017 8:22 PM
> To: Lefevre, Catherine <cl6...@intl.att.com>; onap-tsc@lists.onap.org
> Subject: RE: Migration to *.onap.org
>  
> Hi Catherine,
>  
> I can understand the complexities (and this was confirmed internally for me).
>  
> I think that there are some basic things we need to cover, already mentioned 
> by Gildas, such as removing commented references to what is considered 
> proprietary, or owned,  code etc, even if that is not what you are addressing 
> below.
>  
> What could be good to resolve the discussion is to at a high level, like you 
> have, state down the high level options that we have with the associated 
> risks.  E.g.
> -Initial big bang migration 
> o   Start now: 
> §  Move all projects at once 
> ·Advantage: Clean slate for R1
> ·Risk: several weeks to sort out, release 1 delay unmitigated risk.
> §  Move projects one at a time 
> ·Advantage: 
> o   Controlled migration
> ·Disadvantage 
> o   Implication for each project to reference old and new dependancies
> o   Time to migration (could it be done by R1 Release)
> o   Risk delay to R1 due to stablising after migration
> §  Move projects after xxx (code freeze, …?) 
> ·….
> BR,
>  
> Steve
>  
> From: onap-tsc-boun...@lists.onap.org 
> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine
> Sent: 01 August 2017 14:07
> To: onap-tsc@lists.onap.org
> Subject: [onap-tsc] Migration to *.onap.org
>  
> Dear ONAP TSC,
>  
> I fully understand the request about the seed code to be migrated to 
> *.onap.org.
> Nevertheless I want to bring to your attention that this request will require 
> significant effort (development, testing and infrastructure changes)
>   • Coordinate and update Maven dependencies and links
>   • Update namespaces as required
>   • Change the source code in order to align with *.onap.org for each 
> impacted project
>   • Change the development scripts
>   • Review and update automated test cases
>   • Re-adjust the LF infrastructure accordingly, keeping the 
> org.openecomp version in place until the end of migration
> That way each project can control the pace of migration from org.openecomp -> 
> org.onap : especially for the projects that are already based on the previous 
> naming.  
>   • Review and re-adjust build jobs to be approved by CI-Management 
> project
>   • Create a temporary environment to perform the necessary code changes
>   • Plan the migration in order to avoid any drastic impact on the ONAP 
> community
>   • Recreate new docker images and stabilize the complete ONAP Environment
>   • Etc.
>  
> Based on past experience (moving from *.att.com to *.openecomp.org), this 
> effort can take up to several weeks until the ONAP release is completely 
> stabilized
> If we pursue in this direction then it is a major risk for our Amsterdam 
> release to be completed on time.
> We will need to review the scope of ONAP R1 based on our resource capacity.
>  
> Or we can develop a complete migration plan as part of our ONAP R1 commitments
> And implement this migration in October as part of ONAP R2 preparation.
>  
> Is it something we can discuss during our next TSC meeting?
>  
> Thanks in advance for your consideration.
>  
> Many thanks & regards
> Catherine
>  
> Catherine Lefèvre
> AT Network and Shared Services
> D2 Platform & Systems Development
> AVP Software Development & Engineering
> ECOMP/ONAP/RUBY/SPP
>  
>  
> Phone: +32 2 418 49 22
> Mobile: +32 475 77 36 73
> catherine.lefe...@intl.att.com
>  
> TEXTING and DRIVING… It Can Wait
> AT
> BUROGEST OFFICE PARK SA
> Avenue des Dessus-de-Lives, 2
> 5101 Loyers (Namur)
> Belgiu

Re: [onap-tsc] Migration to *.onap.org

[Lefevre, Catherine]

Good morning Stephen,

Thank you for your feedback.

I will definitively finalize the high level plan as requested and will organize 
a call accordingly in the coming days.
I will also consider Gildas' feedback based on the discussions we had with the 
LF Council.

Best regards
Catherine

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Thursday, August 03, 2017 8:22 PM
To: Lefevre, Catherine <cl6...@intl.att.com>; onap-tsc@lists.onap.org
Subject: RE: Migration to *.onap.org

Hi Catherine,

I can understand the complexities (and this was confirmed internally for me).

I think that there are some basic things we need to cover, already mentioned by 
Gildas, such as removing commented references to what is considered 
proprietary, or owned,  code etc, even if that is not what you are addressing 
below.

What could be good to resolve the discussion is to at a high level, like you 
have, state down the high level options that we have with the associated risks. 
 E.g.
-Initial big bang migration
o   Start now:
§  Move all projects at once
·Advantage: Clean slate for R1
·Risk: several weeks to sort out, release 1 delay unmitigated risk.
§  Move projects one at a time
·Advantage:
o   Controlled migration
·Disadvantage
o   Implication for each project to reference old and new dependancies
o   Time to migration (could it be done by R1 Release)
o   Risk delay to R1 due to stablising after migration
§  Move projects after xxx (code freeze, ...?)
·
BR,

Steve

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine
Sent: 01 August 2017 14:07
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Migration to *.onap.org

Dear ONAP TSC,

I fully understand the request about the seed code to be migrated to *.onap.org.
Nevertheless I want to bring to your attention that this request will require 
significant effort (development, testing and infrastructure changes)

  *   Coordinate and update Maven dependencies and links
  *   Update namespaces as required
  *   Change the source code in order to align with *.onap.org for each 
impacted project
  *   Change the development scripts
  *   Review and update automated test cases
  *   Re-adjust the LF infrastructure accordingly, keeping the org.openecomp 
version in place until the end of migration
That way each project can control the pace of migration from org.openecomp -> 
org.onap : especially for the projects that are already based on the previous 
naming.

  *   Review and re-adjust build jobs to be approved by CI-Management project
  *   Create a temporary environment to perform the necessary code changes
  *   Plan the migration in order to avoid any drastic impact on the ONAP 
community
  *   Recreate new docker images and stabilize the complete ONAP Environment
  *   Etc.

Based on past experience (moving from *.att.com to *.openecomp.org), this 
effort can take up to several weeks until the ONAP release is completely 
stabilized
If we pursue in this direction then it is a major risk for our Amsterdam 
release to be completed on time.
We will need to review the scope of ONAP R1 based on our resource capacity.

Or we can develop a complete migration plan as part of our ONAP R1 commitments
And implement this migration in October as part of ONAP R2 preparation.

Is it something we can discuss during our next TSC meeting?

Thanks in advance for your consideration.

Many thanks & regards
Catherine

Catherine Lefèvre
AT Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>

TEXTING and DRIVING... It Can Wait

AT
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Migration to *.onap.org

[Kenny Paul]

Adding this to the Aug 3 agenda.

Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

> On Aug 1, 2017, at 5:07 AM, Lefevre, Catherine  wrote:
> 
> Dear ONAP TSC,
>  
> I fully understand the request about the seed code to be migrated to 
> *.onap.org .
> Nevertheless I want to bring to your attention that this request will require 
> significant effort (development, testing and infrastructure changes)
> ·Coordinate and update Maven dependencies and links
> ·Update namespaces as required
> ·Change the source code in order to align with *.onap.org 
>  for each impacted project
> ·Change the development scripts
> ·Review and update automated test cases
> ·Re-adjust the LF infrastructure accordingly, keeping the 
> org.openecomp version in place until the end of migration
> That way each project can control the pace of migration from org.openecomp -> 
> org.onap : especially for the projects that are already based on the previous 
> naming.  
> ·Review and re-adjust build jobs to be approved by CI-Management 
> project
> ·Create a temporary environment to perform the necessary code changes
> ·Plan the migration in order to avoid any drastic impact on the ONAP 
> community
> ·Recreate new docker images and stabilize the complete ONAP 
> Environment
> ·Etc.
>  
> Based on past experience (moving from *.att.com  to 
> *.openecomp.org ), this effort can take up to several 
> weeks until the ONAP release is completely stabilized
> If we pursue in this direction then it is a major risk for our Amsterdam 
> release to be completed on time.
> We will need to review the scope of ONAP R1 based on our resource capacity.
>  
> Or we can develop a complete migration plan as part of our ONAP R1 commitments
> And implement this migration in October as part of ONAP R2 preparation.
>  
> Is it something we can discuss during our next TSC meeting?
>  
> Thanks in advance for your consideration.
>  
> Many thanks & regards
> Catherine
>  
> Catherine Lefèvre
> AT Network and Shared Services
> D2 Platform & Systems Development
> AVP Software Development & Engineering
> ECOMP/ONAP/RUBY/SPP
>  
>  
> Phone: +32 2 418 49 22
> Mobile: +32 475 77 36 73
> catherine.lefe...@intl.att.com 
>  <> 
> TEXTING and DRIVING… It Can Wait
> AT
> BUROGEST OFFICE PARK SA
> Avenue des Dessus-de-Lives, 2
> 5101 Loyers (Namur)
> Belgium
>  
>  
> NOTE: This email (or its attachments) contains information belonging to the 
> sender, which may be confidential. proprietary and/or legally privileged. The 
> information is intended only for the use of the individual(s) or entity(ies) 
> named above. If you are not the intended recipient, you are hereby notified 
> that any disclosure, distribution or taking of any action in reliance on the 
> content of this is strictly forbidden. If you have received this e-mail in 
> error please immediately notify the sender identified above
>  
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org 
> https://lists.onap.org/mailman/listinfo/onap-tsc 
> 
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Migration to *.onap.org

[SPATSCHECK, OLIVER (OLIVER)]

Could we put that on the TSC agenda on Thu?

Thx

Oliver

> On Aug 1, 2017, at 8:07 AM  EDT, LEFEVRE, CATHERINE  
> wrote:
> 
> ***Security Advisory: This Message Originated Outside of AT ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> 
> Dear ONAP TSC,
>  
> I fully understand the request about the seed code to be migrated to 
> *.onap.org.
> Nevertheless I want to bring to your attention that this request will require 
> significant effort (development, testing and infrastructure changes)
> ·Coordinate and update Maven dependencies and links
> ·Update namespaces as required
> ·Change the source code in order to align with *.onap.org for each 
> impacted project
> ·Change the development scripts
> ·Review and update automated test cases
> ·Re-adjust the LF infrastructure accordingly, keeping the 
> org.openecomp version in place until the end of migration
> That way each project can control the pace of migration from org.openecomp -> 
> org.onap : especially for the projects that are already based on the previous 
> naming.  
> ·Review and re-adjust build jobs to be approved by CI-Management 
> project
> ·Create a temporary environment to perform the necessary code changes
> ·Plan the migration in order to avoid any drastic impact on the ONAP 
> community
> ·Recreate new docker images and stabilize the complete ONAP 
> Environment
> ·Etc.
>  
> Based on past experience (moving from *.att.com to *.openecomp.org), this 
> effort can take up to several weeks until the ONAP release is completely 
> stabilized
> If we pursue in this direction then it is a major risk for our Amsterdam 
> release to be completed on time.
> We will need to review the scope of ONAP R1 based on our resource capacity.
>  
> Or we can develop a complete migration plan as part of our ONAP R1 commitments
> And implement this migration in October as part of ONAP R2 preparation.
>  
> Is it something we can discuss during our next TSC meeting?
>  
> Thanks in advance for your consideration.
>  
> Many thanks & regards
> Catherine
>  
> Catherine Lefèvre
> AT Network and Shared Services
> D2 Platform & Systems Development
> AVP Software Development & Engineering
> ECOMP/ONAP/RUBY/SPP
>  
>  
> Phone: +32 2 418 49 22
> Mobile: +32 475 77 36 73
> catherine.lefe...@intl.att.com
>  
> TEXTING and DRIVING… It Can Wait
> AT
> BUROGEST OFFICE PARK SA
> Avenue des Dessus-de-Lives, 2
> 5101 Loyers (Namur)
> Belgium
>  
>  
> NOTE: This email (or its attachments) contains information belonging to the 
> sender, which may be confidential. proprietary and/or legally privileged. The 
> information is intended only for the use of the individual(s) or entity(ies) 
> named above. If you are not the intended recipient, you are hereby notified 
> that any disclosure, distribution or taking of any action in reliance on the 
> content of this is strictly forbidden. If you have received this e-mail in 
> error please immediately notify the sender identified above
>  
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=3qNBXK1AEoL6zxuaVrLo3UBFVSNq0OaszyDvfaLoUQE=vK70kqm-zpxVa5UZRJs-RxEUPokb6jDG4kR-XCz9hGY=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Migration to *.onap.org

[Lefevre, Catherine]

Dear ONAP TSC,

I fully understand the request about the seed code to be migrated to *.onap.org.
Nevertheless I want to bring to your attention that this request will require 
significant effort (development, testing and infrastructure changes)

·Coordinate and update Maven dependencies and links

·Update namespaces as required

·Change the source code in order to align with *.onap.org for each 
impacted project

·Change the development scripts

·Review and update automated test cases

·Re-adjust the LF infrastructure accordingly, keeping the org.openecomp 
version in place until the end of migration
That way each project can control the pace of migration from org.openecomp -> 
org.onap : especially for the projects that are already based on the previous 
naming.

·Review and re-adjust build jobs to be approved by CI-Management project

·Create a temporary environment to perform the necessary code changes

·Plan the migration in order to avoid any drastic impact on the ONAP 
community

·Recreate new docker images and stabilize the complete ONAP Environment

·Etc.

Based on past experience (moving from *.att.com to *.openecomp.org), this 
effort can take up to several weeks until the ONAP release is completely 
stabilized
If we pursue in this direction then it is a major risk for our Amsterdam 
release to be completed on time.
We will need to review the scope of ONAP R1 based on our resource capacity.

Or we can develop a complete migration plan as part of our ONAP R1 commitments
And implement this migration in October as part of ONAP R2 preparation.

Is it something we can discuss during our next TSC meeting?

Thanks in advance for your consideration.

Many thanks & regards
Catherine

Catherine Lefèvre
AT Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc