Re: [onap-discuss] Building blocks for multicloud k8s plugin, RE: [coe] Team meeting Agenda

[Tal Liron]

Hi everyone,

I've been following the conversation silently for a while, but it might be
time to jump in --

I am working on a training tutorial for Go, for my own team, and would be
happy to pass it on to anyone involved in ONAP. It's meant for veterans
like you who just need some pointers for the main stumbling blocks of this
productive language.

In Beijing next week I will be giving two talks related to the technologies
discussed. In one, I will present a tool to deploy directly to Kubernetes
from TOSCA models. In the second, I will introduce "operators" as a way to
create domain-specific clustering in Kubernetes, which I think we'll be
seeing more and more of in the Kubernetes space. All of this work is in Go.

(For what it's worth -- despite finding Go extremely useful, I'm actually
not sure that Go is the best choice specifically for writing operators.
I'll discuss the issue in my talk.)

I can probably contribute more significantly to the COE project, but I must
be honest and say that I have serious concerns about its overall approach.
I am not convinced that it's fruitful to treat Kubernetes as a VIM. This is
especially apparent as we see more and more truly cloud-native services
that manage their own lifecycles. Not only do they know best, but the
custom code to self-manage (operators) is embedded within the service.
(That's why it's "cloud native".) There's just so much more to Kubernetes
then deploying replicated pods. As a small example, on topic: I can't see
having the ObjectMeta.Name as having meaning externally in all but the most
trivial Kubernetes applications.

I see that the COE project is moving forward confidently, so I hope we can
talk more and perhaps find ways in which I can work with you
constructively. I'm sure that despite disagreement we can find some overlap
in our goals and help make ONAP better.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Beijing Community Awards - VOTE NOW! POLLS CLOSE, 23:59 China Time, Tuesday, June 19th

[Kenny Paul]

I have finished compiling the results of the nominations and the polls are now 
open. 

We received 59 Nominations across 6 categories, which represents 33 uniquely 
names individuals and 11 uniquely named projects. 

 
Nominations officially closed last night at 6 PM local time.  I have continued 
to receive nominations (vie email) today. Anything that came in after the 
deadline has been discarded.
 
One nomination that came in before the deadline was disqualified because the 
justification cited work an individual was specifically doing for Casablanca 
rather than citing any accomplishments attributed to the Beijing release
 
As with the Amsterdam awards, if one person was nominated multiple times in the 
same category, I selected the justification that I felt best captured the 
spirit of the combined feedback, or provided composite feedback from a couple 
of sources.
 
While the wiki page lists people/projects alphabetically, the order in which 
nominee names are actually presented to the voter are randomized
 
Please honor the spirit of 1 Community Member == 1 vote.  
 
If some individual or project wins in more than one category, they will only 
receive the award for the "higher" category and the first runner-up will be 
awarded in the "lower" category
 
Individual vote counts will not be shared with the Community
 
VOTE for the Beijing Release Awards
 
 

 

Thanks!

-kenny

 

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [it-infrastructure-alerts] JIRA security maintainance. Saturday June 16 at 8am Pacific (3pm UTC)

[Jessica Wagantall]

Dear team,

This is just a small reminder of this upcoming maintenance.

Thanks!
Jess

On Wed, Jun 13, 2018 at 2:42 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> What: The Linux Foundation will be performing a JIRA security upgrade
>
> When: Saturday June 16 at 8am Pacific (3pm UTC)
>
> Why:The bundled Atlassian OAuth plugin allows arbitrary HTTP requests to
> be proxied
> CVE-2017-9506 (https://jira.atlassian.com/browse/JRASERVER-65862)
>
> Impact: Jira will be unavailable for 1 hour
>
> Notices will be posted to the mailing lists at the start and end of the
> maintenance.
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [modeling] Call for approval on the “obsolete legacy attributes/datatypes” proposal for the resource IM

[jessie jewitt]

 Here is our (ARM/OAM Technologies) feedback on this proposal:

1. Format - We're glad to see that ONAP is using the "Applied Stereotypes"
column in their tables, even though this is only defined in IFA015 output
and not IFA011. However, since you are choosing to use it, we'd like to
recommend that it be used properly. The column is intended to show the
applied stereotypes that they use in Papyrus, which are based on the IISOMI
Open Model Profile. See Stereotype Usage
   for an explanation of how
these stereotypes are used.  "Obsolete" is a stereotype itself and not a
valid enum for "support".  The proper format per IISOMI would be:

OpenModelAttribute   (this is the applied stereotype)
isInvariant: false
support: MANDATORY
Obsolete  (this is the applied stereotype, note there is no "d" on the end)

2. Artifact lifecycle:  The proposal to put an artifact in an "Obsolete"
lifecycle state implies that we have agreed to implement artifact
lifecycles in accordance with the IISOMI Guidelines
 . As far as
we know, this is under discussion, but has not been accepted by the team.
It seems a bit pre-mature, therefore, to jump straight to a proposal where
we implement the "Obsolete" stereotype without having first accepted
general use of the the lifecycle stereotypes.

3. Recommendation for moving forward on this proposal:
 a. Implementing an artifact lifecycle, per this proposal, implies
"agreement" that we will use artifact lifecycles in the model. If people
   agree to this proposal, then we have implicit agreement on
using lifecycle stereotypes. No need for discussion. If this is not the
case,
 then we need to discuss and agree on usage of the lifecycle
stereotypes before marking any artifact as "Obsolete".
 b. Assuming it is agreed to use lifecycle stereotypes, all artifacts
in the model should have a lifecycle phase associated to them, and not
 just the proposed "Obsolete" lifecycle.
 c.  The proposal to go from "nothing" to "Obsolete" is not in
accordance with the
lifecycle
state machine

 that
proposes an artifact go from  "Mature"-> "Deprecated"->
"Obsolete". Assuming, had we implemented lifecycles, and that these
attributes would be in a "Mature"   phase, the next logical step would
be then to transition them to "Deprecated" and not "Obsolete", as proposed.
We are not in agreement
 that they directly be marked as "Obsolete".


On Wed, Jun 13, 2018 at 11:38 PM, yangxu (H)  wrote:

> Hi Jessie,
>
>
>
> Maybe I can help clarify this. Per the discussion of the resource IM
> interest group, the “obsolete” is intended to follow the definitions of the
> IISOMI modeling guidelines as you stated below for the time being.
>
> I think the intention of the proposal is to mark those
> attributes/datatypes as “obsolete” but not removed for R3, and perhaps
> remove them in R4, which fits the definition. Alex, you can confirm whether
> I interpreted it correctly.
>
>
>
> For others who haven’t attend the resource IM call, please noted that the
> “lifecycle” stereotype of the model is still under discussion. The interest
> group just agrees that the IISOMI definition of “obsolete” fits the current
> intention of the proposal and decides to use the term.
>
>
>
> BR,
>
> Xu
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *jessie jewitt
> *Sent:* Thursday, June 14, 2018 12:05 AM
> *To:* denghui (L) 
> *Cc:* onap-discuss@lists.onap.org; onap-tsc 
> *Subject:* Re: [onap-discuss] [modeling] Call for approval on the
> “obsolete legacy attributes/datatypes” proposal for the resource IM
>
>
>
> Hello Deng Hui-
>
>  Could you please clarify something for me. The ETSI "applied
> stereotype", on which this column in the wiki table is based, has
> "obsolete" as an artifact lifecycle option, with its definition supplied in
> the IISOMI Modeling Guidelines. This is the definition of "obsolete" in
> those guidelines. Is this what we should interpret this to mean? Will the
> entity be kept in the model for at least one further release?
>
> Thanks for your guidance,
>
> Jessie
>
> · *Obsolete*
> This stereotype indicates that the entity should not be used in new
> implementation and that attempts should be made to remove it from existing
> implementation. The entity should be kept in the model for at least one
> further release. The team has to decide on a case by case basis when to
> remove it from the model.
>
>
>
>
>
> On Wed, Jun 13, 2018 at 8:23 AM, denghui (L)  wrote:
>
> Hello all,
>
>
>
> This is 1 week’s call for approval on the “obsolete legacy
> attributes/datatypes” proposal for the resource IM.
>
> The intention is to mark several 

Re: [onap-discuss] Casablanca Requirements

[Alla Goldner]

Gildas,

All endorsed use cases and requirements are included now.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image002.png@01D404CC.3DE22FA0]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Gildas Lanilis
Sent: Friday, June 15, 2018 12:04 AM
To: onap-tsc ; onap-discuss@lists.onap.org; 
onap-rele...@lists.onap.org
Subject: [onap-tsc] Casablanca Requirements
Importance: High

Hi All,

This is to follow up on June 14, TSC Meeting regarding gathering the 
Requirements for Casablanca Release.

To meet that goal, I have created a wiki page 
listing in 3 
big categories:

1.   Use Cases

2.   Functional Requirements

3.   Non Functional Requirements

with an identified owner and the projects impacted.

Note this is NOT the Casablanca Release Scope, but the gathering of all 
requirements we have to consider and prioritize while we meet at Beijing.

I have done the first cut (some have already added complementary info, +1), 
however there are some empty cells and the community would be grateful if you 
could fill out the missing part by:

* Adding missing owners

* Identifying impacted projects

* Adding link to complementary set of information

Let me know if you have any questions, I will be glad to help.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
gildas.lani...@huawei.com
Mobile: 1 415 238 6287

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ONAP Casablanca Developer Forum- Final Event Details

[Pasi Vaananen]

The "full schedule" link below is for Dec2017 event, it should be:
https://onapcasablanca2018.sched.com/

Pasi

On 06/15/2018 01:27 AM, ONAP Events Team wrote:
> Untitled Document
>
> If you are having trouble viewing this email, try viewing it in a
> browser
> .
>
>
>  
>   ONAP Casablanca Release Developer Forum
>
> Dear Pasi,
>
> We look forward to seeing you next week at the ONAP Casablanca Release
> Developer Forum hosted by China Telecom and co-hosted by Huawei at
> the China Telecom Beijing Research Institute  (CTBRI). Below you will
> find all the logistical details needed to prepare you for your arrival.
>
> EVENT VENUE China Telecom Beijing Research Institute  (CTBRI)
> Address: China Telecom,
> Southern Zone of Future Science & Technology
> Beiqijia, Changping
> Beijing, China
> Tel <+86-10> 50902000 
>
>
>
> AGENDA
>
> View the full schedule  for the
> ONAP Casablanca Release Developer Forum or visit the ONAP wiki
> .
> You may also view and save the schedule to your mobile device
> .
>
>
> PARKING
>
> Parking is available at the CTBRI. *VERY IMPORTANT:* You *MUST PRINT*
> the parking permit below *prior* to arriving and present it at the
> gate to the CTBRI.
>
>
>
> *TRANSPORTATION *
>
> *FROM THE BEIJING AIRPORT
> *Taxis are available from the airport and will cost approximately $20
> USD to downtown Beijing and is 22 km. We recommend you have the
> address of your hotel in Chinese to show the driver.
>
> *AROUND BEIJING
> *Taxis are available anywhere on the street of Beijing. The first 3KM
> are 13 Yuan ($2 USD) and every 1KM extra costs 2.3 Yuan ($0.4 USD,
> tipping is not required.  It is best to show the driver the address of
> your destination in Chinese.
>
> You may also download Didi App (Chinese Uber) on your mobile phone.
> Register for a Didi account using your mobile phone number, then enter
> the destination that you want to go, confirm the type of car you would
> like, and request the vehicle
>
> *GETTING TO CTBRI*
>
> *Shuttles
> *China Telecom is providing shuttle buses each morning and evening
> from Shaoyaoju station (a railway station on line 10) to and from
> CTBRI. The pickup location is 200 meters east of  Exit at ShaoYaoJu
> station and there will be staff directing you to the F exit. The Bus
> stop is about a 5-minute walk from the Crowne Plaza Sun Palace. The
> bus ride is approximately 20 minutes to CTBRI.
>
>
>
> Below is the schedule for the shuttle each day
>
>
>   From Shaoyaoju to CTBRI (Morning): 8:00am and 8:15am
>
>
>   From CTBRI to Shaoyaoju (Evening)
>
>
>   June 19
>
>   
>
>
>   June 20
>
>   
>
>
>   June 21
>
>   
>
>
>   June 22
>
>
>   6:00pm
>
>   
>
>
>   5:30pm
>
>
>   (To Reception and Shaoyaoju)
>
>   
>
>
>   6:00pm
>
>   
>
>
>   12:30pm
>
>
>   6:30pm
>
>   
>
>
>   8:00pm
>
>
>   (from Tixiangyuan)
>
>   
>
>
>   6:30pm
>
>   
>
>
>   1:00pm
>
>
>   8:30pm
>
>
>   (from Tixiangyuan)
>
>
> **
>
> *Taxi*
>
> From Shaoyaoju station to CTBRI a taxi is approximately $15 USD
>
> *Didi App*
>
> CTBRI may not show on the map in the app but you can try Lutuan
> Jiayuan located east to CTBRI, see the image for the Chinese Address.
>
> *
> *
>
> BADGE PICK-UP
>
> On your first arrival day to the CTBRI you will check-in with the
> security desk and receive a name bade. This badge will be used for
> access to the event space, parking, hotel shuttle and meals (where
> appropriate). 
> The opposite side of the badge will provide helpful information
> including:
>
>   * CTBRI address
>   * Wifi information
>   * Lunch & Coffee Bar Location
>   * Tuesday Reception Information
>   * Meeting agenda QR code
>
>
> *MEALS *Lunch will be hosted each day in the Dining Hall from
> 12:30pm-1:30pm and will include both Chinese and western food. The
> dining hall is located south of the overpass, on the 2nd
> floor. Morning and afternoon tea break is also hosted. There is a
> coffee bar on the 1st floor and complimentary coffee will be hosted
> each day from 1:00-2:00pm. *Evening Event* Huawei is hosting an
> evening event on Wednesday, June 20 at the Tixiangyuan Restaurant.
> Shuttles will be available from the main entrance beginning at 5:30-pm.
>
> *Contact information  * 
> Emergency call: 110 (Police)   120(Ambulance)   
> CTBRI Helpdesk:  Yue Liu 13661318157  Helen Lu 15300087071 
>
>
>   Cancellation/No-Show Fee
>
> There is no cost to participate in the ONAP Developer Event. You will
> only be charged a cancellation/no-show fee of $50.00 USD if you do not
> cancel by 08:00 PST on Monday, June 18 or do not attend the 

[onap-discuss] Updated invitation: [usecase] Subcommittee (updated Jan. 30, 2018) @ Weekly from 7am to 8am on Monday (PST) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20180212T07
DTEND;TZID=America/Los_Angeles:20180212T08
RRULE:FREQ=WEEKLY;BYDAY=MO
DTSTAMP:20180615T060457Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:5bbivu18169mds1kt2g8kkl...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=alla.gold...@amdocs.com;X-NUM-GUESTS=0:mailto:alla.goldner@amdocs.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20180131T011058Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 2 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/655429955\n\nOr iPhone one-tap :\nUS: +16699006833\,\,655429955#  o
 r +16465588656\,\,655429955# \nOr Telephone:\nDial(for higher quality\,
  dial a number based on your current location): \nUS: +1 669 900 68
 33  or +1 646 558 8656  or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (
 Toll Free)\nMeeting ID: 655 429 955\nInternational numbers availabl
 e: https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86\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=NWJiaXZ
 1MTgxNjltZHMxa3QyZzhra2x0M2Mgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjb
 GludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxl
 bmRhci5nb29nbGUuY29tNTVmYjAzZWZjNWNiZTk3Zjk4MWIzZWM0YzYxNDNjOTQxMzBlMmM3Nw&
 ctz=America%2FLos_Angeles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180615T060457Z
LOCATION:https://zoom.us/j/655429955
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:[usecase] Subcommittee (updated Jan. 30\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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

[onap-discuss] Updated invitation: [dcaegen2] Weekly (updated Mar. 13, 2018) @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20180315T09
DTEND;TZID=America/New_York:20180315T10
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20180615T060310Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:v72pcvbopuooo4mtp91ue24...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=l...@research.att.com;X-NUM-GUESTS=0:mailto:l...@research.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20180314T003251Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 4 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/824147956\n\nOr iPhone one-tap :\nUS: +16465588656\,\,824147956#  o
 r +16699006833\,\,824147956# \nOr Telephone:\nDial(for higher quality\,
  dial a number based on your current location): \nUS: +1 646 558 86
 56  or +1 669 900 6833  or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (
 Toll Free)\nMeeting ID: 824 147 956\nInternational numbers availabl
 e: https://zoom.us/zoomconference?m=HN2MIJkxqxYgu8EjDmekdG0WHlAnv3Zp\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=djcycGN
 2Ym9wdW9vbzRtdHA5MXVlMjRsMWsgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjb
 GludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxl
 bmRhci5nb29nbGUuY29tNjQ3YjliZmVjNWYzMDY1YjlmOTE5Yjk2NGZkOTlmZTAwNDEyYmI5YQ&
 ctz=America%2FLos_Angeles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180615T060310Z
LOCATION:https://zoom.us/j/824147956
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:[dcaegen2] Weekly (updated Mar. 13\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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

[onap-discuss] Updated invitation: [aai] weekly (updated Mar. 13, 2018) @ Weekly from 6am to 7am on Wednesday (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180314T13Z
DTEND:20180314T14Z
RRULE:FREQ=WEEKLY;BYDAY=WE
DTSTAMP:20180615T060134Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:t0nun6n7vi95ccujf4uloco...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jf2...@att.com;X-NUM-GUESTS=0:mailto:jf2...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20180314T011644Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 10 is inviting you to a scheduled Z
 oom meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.
 us/j/935396994\n\nOr iPhone one-tap :\nUS: +16465588656\,\,935396994#  
 or +16699006833\,\,935396994# \nOr Telephone:\nDial(for higher quality\
 , dial a number based on your current location): \nUS: +1 646 558 8
 656  or +1 669 900 6833  or +1 855 880 1246 (Toll Free) or +1 877 369 0926 
 (Toll Free)\nMeeting ID: 935 396 994\nInternational numbers availab
 le: https://zoom.us/zoomconference?m=K-nxZ7a390DVt0RwGLpkrB6gzd_9L9W7\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=dDBudW
 42bjd2aTk1Y2N1amY0dWxvY29sbm8gb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIj
 bGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWx
 lbmRhci5nb29nbGUuY29tZTY0ZjhhNWE1ZGNiNDQ0ODA4NzdlMGNmNzQ2NmU2YTQxMjA2MjgwNQ
 =America%2FLos_Angeles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180615T060134Z
LOCATION:https://zoom.us/j/935396994
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:[aai] weekly (updated Mar. 13\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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