Re: [onap-tsc] [it-infrastructure-alerts] ONAP environment maintenance 2018-03-08 Now

[Jessica Wagantall]

Correction,

All services are still up and we don't get affected by this.

thanks!
Jess

On Thu, Mar 8, 2018 at 4:34 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> What: The Linux Foundation will be performing a Nexus reboot
>
> When: Now, March 8th
>
> Why: AWS that ap-southeast-1-nexus-1 is going to be rebooted at 22:00 UTC
> on the 22nd March
> We need to perform this reboot before then.
>
> Impact: Jenkins and Nexus will be unavailable for 30 mins.
>
> Notices will be posted to the mailing lists at the start and end of the
> maintenance.
>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] [it-infrastructure-alerts] ONAP environment maintenance 2018-03-08 Now

[Jessica Wagantall]

What: The Linux Foundation will be performing a Nexus reboot

When: Now, March 8th

Why: AWS that ap-southeast-1-nexus-1 is going to be rebooted at 22:00 UTC
on the 22nd March
We need to perform this reboot before then.

Impact: Jenkins and Nexus will be unavailable for 30 mins.

Notices will be posted to the mailing lists at the start and end of the
maintenance.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Invitation: TSC Meeting (updated Mar. 8, 2018) @ Weekly from 7am to 8:30am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 (PDT) (onap-tsc@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180315T14Z
DTEND:20180315T153000Z
RRULE:FREQ=WEEKLY;UNTIL=20190221T153000Z;INTERVAL=1;BYDAY=TH
DTSTAMP:20180308T235734Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:u1agdle6gtl9cqn9a9ud36q...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-tsc@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-...@lists.onap.o
 rg
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jwagant...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:jwagantall@lin
 uxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Andrew Grimberg;X-NUM-GUESTS=0:mailto:agrimb...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jphe...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:jphelps@linuxfoun
 dation.org
CREATED:20180308T235503Z
DESCRIPTION:Hi there\, \n\nONAPmeet1 is inviting you to a scheduled Zoom me
 eting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/6
 61303200\n\nOr iPhone one-tap :\nUS: +16465588656\,\,661303200#  or +16
 699006833\,\,661303200# \nOr Telephone:\nDial(for higher quality\, dial
  a number based on your current location): \nUS: +1 646 558 8656  o
 r +1 669 900 6833  or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll 
 Free)\nMeeting ID: 661 303 200\nInternational numbers available: ht
 tps://zoom.us/zoomconference?m=FHWF11_wwIutwd1PAi_vsotA5bQ6kCLh\n\n\n\n-::~
 :~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 ::~:~::-\nPlease do not edit this section of the description.\n\nView your 
 event at https://www.google.com/calendar/event?action=VIEW=dTFhZ2RsZTZn
 dGw5Y3FuOWE5dWQzNnE4cGMgb25hcC10c2NAbGlzdHMub25hcC5vcmc=NzIjbGludXhmb3V
 uZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb2
 9nbGUuY29tNWEwZTBmZTY0ZjA1ODAwYWM1NjliMmUxNDRiYTMwMzRlYzEwMmE2MQ=Americ
 a/Los_Angeles=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180308T235734Z
LOCATION:https://zoom.us/j/661303200
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:TSC Meeting  (updated Mar. 8\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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

Re: [onap-tsc] Agenda for our meeting on 12/3/2018

[Ievgen Zhukov]

Hi, Dear Alla

Could you tell please, what is a plan for Use Cases Release2 implementation?
They are in implementation plans for ONAP Beijing or Cassandra Release?

Thanks,
---

Evgeniy Zhukov, Business Analysis
Netcracker Technology

+38 (044) 238-8727 | ext. 26927| office
+38 (093) 210-4266 | mobile

We are Netcracker, and we are focused forward

From: onap-usecasesub-boun...@lists.onap.org 
 On Behalf Of Alla Goldner
Sent: Thursday, March 8, 2018 5:35 PM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc 
Subject: [Onap-usecasesub] Agenda for our meeting on 12/3/2018

Hi all,

Here is the agenda for the upcoming meeting:


  1.  Status of Beijing functional requirements
  2.  5G task force update for all of the requirements they are currently 
working on
  3.  Any additional request? (please approach me, if you wish to present 
something additional on Monday)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3B73D.6A81B5D0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer




The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Confirming Context of TSC Structure Vote

[Kenny Paul]

Following up from today’s TSC Meeting on the TSC Composition discussion. 
Section 2 of the ONAP Technical Charter reads as follows:

b. TSC Voting Members 

i. “Startup Period”: From date of creation of the ONAP Project a Series 
of LF Projects, LLC (“Project Launch”) until June 30, 2018 (such period the 
“Startup Period”), the TSC voting members will consist of one appointee from 
each organization listed as having TSC appointees on ONAP.org. All TSC voting 
members will be listed on ONAP.org. 

ii. “Steady State”: After the Startup Period, the size, makeup and 
procedure for determining voting members of the TSC will be as determined by 
the TSC and documented on the ONAP web site. 

A couple things of note here directly relevant to this morning’s discussion:
- First at the TSC’s request the original “Steady State” cutover to a 
meritocratic based TSC was previously changed from the end of this month to 
June 30 to avoid disrupting the Beijing release.  Changing this again would 
require amending the ONAP Technical Charter.

- Second, limitations were established to maintain the TSC membership at its 
current level until the “Steady State” structure and elections. Opening this up 
to all include TSC membership from any LFN Platinum member that is not already 
represented on the ONAP TSC in advance of the “Steady State” elections will 
require an amendment to the ONAP Technical Charter.  My personal recommendation 
is to keep the status quo on this item. 

- Finally although we had 19 Platinum Member reps appointed to the TSC, there 
were only 18 TSC members ever listed on the web page 
  - our requests to the remaining Platinum 
member for a pic/bio info from were never answered and therefore nothing was 
ever posted. (Also there has been little to no participation since the 1st or 
2nd meeting for what it is worth.)

So in summary, the current size of the TSC based upon the ONAP Technical 
Charter (effective Jan. 1st) is 18 members and will remain so until the TSC 
sets the Steady State structure by June 30th, or amends the Technical Charter 
to do something different.

Having provided that background my understanding of today’s proposal is for the 
TSC to stay “as-is” until after Casablanca.  

THIS IS TO ENSURE CLARIFICATION OF THE INTENT AND LANGUAGE, NOT THE VOTE 
ITSELF.  The formal vote will occur on the onap-tsc-vote alias, not here. A 
plus-one here on this issue is null and void.

The TSC approves modifying the “Steady State” definition in Section 2,b,i of 
the ONAP Technical Charter to be _DATE_.

I am looking to the TSC to verify the above sentence reflects the correct vote 
on this issue and to provide _DATE_.


Thanks!

Best Regards, 
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone

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

Re: [onap-tsc] [onap-discuss] [modeling] ONAP R2 IM to DM design

[jessie jewitt]

Hello-
I don't remember this being an action out of the modelling committee
meeting yesterday. How does it compare to the action item from another
meeting that Alex, Thinh, Anatoly and myself took to work on the IM to DM
model mapping, and the mappings that have already been proposed (and
commented on) here:

https://wiki.onap.org/pages/viewpage.action?pageId=25436710

Could you please clarify.
Thank you,
Jessie

On Thu, Mar 8, 2018 at 4:46 AM, denghui (L)  wrote:

> Hello all
>
>
>
> As agreed in modeling subcommittee meeting, we need to update the onap
> types of the data model to reflect the agreements reached in information
> model.
>
>
>
> It’s huge work to achieve the goal, in order to accelerate, 7 separate
> tasks have been created based on the current IM. We encourage interested
> people to volunteer to take the lead for particular task.
>
>
>
> The tasks including:
>
> 1. VDU: https://jira.onap.org/browse/MODELING-67
>
> 2. HPA: https://jira.onap.org/browse/MODELING-68
>
> 3. CP: https://jira.onap.org/browse/MODELING-69
>
> 4. DeploymentFlavor: https://jira.onap.org/browse/MODELING-70
>
> 5. VL: https://jira.onap.org/browse/MODELING-71
>
> 6. VNFD: https://jira.onap.org/browse/MODELING-72
>
> 7. monitor: https://jira.onap.org/browse/MODELING-73
>
>
>
> It’s expected that the lead would help provide tosca definitions on the
> contribution page (https://wiki.onap.org/display/DW/Data+Model+align+
> with+TOSCA+NFV+Profile) and
>
> help implement related logic in SDC, APPC/VFC projects.
>
>
>
> Thanks a lot
>
>
>
> DENG Hui
>
> ___
> onap-discuss mailing list
> onap-disc...@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
>
>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Re-introduction from Red Hat

[Tal Liron]

Hello ONAP community,

I've been assigned to be Red Hat's engineering point of contact for ONAP. I 
work as a principal engineer in our NFV Partner Engineering team, together with 
Pasi Vaananen and Frank Zdarsky.

Under the broader goal of our commitment to ONAP's success, we are focused on 
ensuring that ONAP can be productized on top of open-source software stacks 
supported by multiple vendors: from the bare-metal operating system, through 
virtual machines and container deployment, up to enterprise middleware and SDN. 
Right now ONAP's reference implementations per project tend to be those with 
which the developers are most comfortable, so we hope to loosen that coupling 
by testing and documenting alternatives, as well as participating 
constructively in the architecture process.

Red Hat, as you may know, is heavily invested in many of ONAP's upstream 
projects and communities. We'd like to extend this activity to encompass ONAP, 
too. For the present in particular we'll do our best to assist ONAP projects in 
our team's areas of expertise:

• Production-grade Kubernetes, especially advanced networking and CI 
integrations
• OpenStack, Ansible, OpenDaylight
• RPM-based Linuxes
• Atomic Host (lightweight transactional Linux optimized for containers)

We're especially excited to see ONAP push these technologies to their limits 
and catalyze upstream improvements for NFV.

Please contact me if you'd like to cooperate with us on these or other 
technologies. Also, I and many other Red Hat folk will be at ONS North America 
and would be happy to meet you there.

If my name is familiar to some of you, it's because I've been involved in 
OPEN-O and ONAP for a long time as an employee of GigaSpaces/Cloudify. I'm one 
of the core developers of ARIA and am a recipient of the coveted "TOSCA All 
Star" award in OPEN-O, which I still display proudly on my bookcase. In my new 
role at Red Hat I will be more narrowly focused on NFV, but do broader 
technological work in virtualization, containers, networking, and 
orchestration. I'm looking forward to continue working with all of you in my 
new role!
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] LFN Compliant Charter

[Kenny Paul]

As voted upon by the original ONAP Governing Board, on Jan. 1st ONAP became 
part of Linux Foundation Networking (LFN). It is now the ONAP Project a Series 
of LF Projects, LLC.  As part of this transition the management responsibility 
for the Project transferred from the Board to the TSC.

This change in governance required modifications to the both original Project 
Charter and the TSC Charter, resulting from the elimination of the previous 
ONAP Governing Board and the transfer of responsibilities to the TSC. I had 
neglected to link these documents in to the wiki and have now done so.  My 
sincere apologies for failing to do so until now. 

The original Project Charter has been replaced with the ONAP Project a Series 
of LF Projects, LLC Technical Charter 

The original TSC Charter has been renamed to the ONAP Technical Community 
Document 

 
( a redlined version of the Technical Community Document is attached to the TSC 
page for reference)

As has been previously discussed, the TSC continues to operate as it did 
before. The Technical Community Document retains the same fundamental 
operational provisions of the original TSC Charter wherever appropriate.  
Amendments to either the Project Technical Charter or the Technical Community 
Document can be made by the TSC.

Currently the Technical Community Document it is in PDF form only. I will 
provide an indexed version when time permits.

Again, my apologies for failing to post those back in January. It was an 
unacceptable oversight on my part.

Best Regards, 
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone

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

[onap-tsc] Agenda for our meeting on 12/3/2018

[Alla Goldner]

Hi all,

Here is the agenda for the upcoming meeting:


1.   Status of Beijing functional requirements

2.   5G task force update for all of the requirements they are currently 
working on

3.   Any additional request? (please approach me, if you wish to present 
something additional on Monday)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3B703.CD4E6C10]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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

Re: [onap-tsc] [modeling] ONAP R2 IM to DM design

[denghui (L)]

Hello Andrei,

It's really hard to keep the synchronization between SDO and OSS, they have 
different paces,
ONAP is working for Release time frame restriction.

Thanks a lot

DENG Hui

From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com]
Sent: Thursday, March 8, 2018 8:59 PM
To: denghui (L) ; onap-disc...@lists.onap.org; onap-tsc 

Cc: Rittwik Jana ; Lishitao ; 
MAYER, ANDREW J 
Subject: RE: [modeling] ONAP R2 IM to DM design

Hello Deng Hui, Andy,

As the topics 1 -  6 are more or less covered (or in the process of finalizing) 
by the ETSI GS NFV-SOL001 so it would not be a big deal to re-use the TOSCA 
constructs from there.

However the topic # 7 is not covered (and not planned to be covered) by SOL001 
so to my understanding we really have an issue. I'm aware of existence of TOSCA 
based monitoring definitions done by AT team and I was requested to 
contribute it in ETSI SOL but this contribution may take time.

BR

Andrei

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, March 08, 2018 2:46 PM
To: onap-disc...@lists.onap.org; onap-tsc 
>
Cc: Rittwik Jana >
Subject: [onap-tsc] [modeling] ONAP R2 IM to DM design

Hello all

As agreed in modeling subcommittee meeting, we need to update the onap types of 
the data model to reflect the agreements reached in information model.

It's huge work to achieve the goal, in order to accelerate, 7 separate tasks 
have been created based on the current IM. We encourage interested people to 
volunteer to take the lead for particular task.

The tasks including:
1. VDU: https://jira.onap.org/browse/MODELING-67
2. HPA: https://jira.onap.org/browse/MODELING-68
3. CP: https://jira.onap.org/browse/MODELING-69
4. DeploymentFlavor: https://jira.onap.org/browse/MODELING-70
5. VL: https://jira.onap.org/browse/MODELING-71
6. VNFD: https://jira.onap.org/browse/MODELING-72
7. monitor: https://jira.onap.org/browse/MODELING-73

It's expected that the lead would help provide tosca definitions on the 
contribution page 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile) and
help implement related logic in SDC, APPC/VFC projects.

Thanks a lot

DENG Hui
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [modeling] ONAP R2 IM to DM design

[Andrei Kojukhov]

Hello Deng Hui, Andy,

As the topics 1 -  6 are more or less covered (or in the process of finalizing) 
by the ETSI GS NFV-SOL001 so it would not be a big deal to re-use the TOSCA 
constructs from there.

However the topic # 7 is not covered (and not planned to be covered) by SOL001 
so to my understanding we really have an issue. I'm aware of existence of TOSCA 
based monitoring definitions done by AT team and I was requested to 
contribute it in ETSI SOL but this contribution may take time.

BR

Andrei

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of denghui (L)
Sent: Thursday, March 08, 2018 2:46 PM
To: onap-disc...@lists.onap.org; onap-tsc 
Cc: Rittwik Jana 
Subject: [onap-tsc] [modeling] ONAP R2 IM to DM design

Hello all

As agreed in modeling subcommittee meeting, we need to update the onap types of 
the data model to reflect the agreements reached in information model.

It's huge work to achieve the goal, in order to accelerate, 7 separate tasks 
have been created based on the current IM. We encourage interested people to 
volunteer to take the lead for particular task.

The tasks including:
1. VDU: https://jira.onap.org/browse/MODELING-67
2. HPA: https://jira.onap.org/browse/MODELING-68
3. CP: https://jira.onap.org/browse/MODELING-69
4. DeploymentFlavor: https://jira.onap.org/browse/MODELING-70
5. VL: https://jira.onap.org/browse/MODELING-71
6. VNFD: https://jira.onap.org/browse/MODELING-72
7. monitor: https://jira.onap.org/browse/MODELING-73

It's expected that the lead would help provide tosca definitions on the 
contribution page 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile) and
help implement related logic in SDC, APPC/VFC projects.

Thanks a lot

DENG Hui
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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

[onap-tsc] [modeling] ONAP R2 IM to DM design

[denghui (L)]

Hello all

As agreed in modeling subcommittee meeting, we need to update the onap types of 
the data model to reflect the agreements reached in information model.

It's huge work to achieve the goal, in order to accelerate, 7 separate tasks 
have been created based on the current IM. We encourage interested people to 
volunteer to take the lead for particular task.

The tasks including:
1. VDU: https://jira.onap.org/browse/MODELING-67
2. HPA: https://jira.onap.org/browse/MODELING-68
3. CP: https://jira.onap.org/browse/MODELING-69
4. DeploymentFlavor: https://jira.onap.org/browse/MODELING-70
5. VL: https://jira.onap.org/browse/MODELING-71
6. VNFD: https://jira.onap.org/browse/MODELING-72
7. monitor: https://jira.onap.org/browse/MODELING-73

It's expected that the lead would help provide tosca definitions on the 
contribution page 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile) and
help implement related logic in SDC, APPC/VFC projects.

Thanks a lot

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