[onap-discuss] SO Weekly Meeting Schedule... (New DST effect)

2018-11-19 Thread seshu kumar m 
[so] Weekly Meeting...

https://zoom.us/j/309416964

NOTE: I’m sending out this meeting notice (on 20-Nov-2018) as a convenience to 
those like me whose calendar appointment was scheduled at the wrong time due 
the changes in the DST.  If you already have the correct appointment on your 
calendar, you can ignore this one.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/309416964
Or
iPhone one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964#
Or
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free)
Meeting ID: 309 416 964
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT



Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
---

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13874): https://lists.onap.org/g/onap-discuss/message/13874
Mute This Topic: https://lists.onap.org/mt/28250974/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

--- Begin Message ---
BEGIN:VCALENDAR
METHOD:PUBLISH
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Seshu m:MAILTO:seshu.kuma...@huawei.com
DESCRIPTION;LANGUAGE=en-US:Description:\n\n\n[so] Weekly Meeting...\n\n\nht
 tps://zoom.us/j/309416964\n\nNOTE: I’m sending out this meeting no
 tice (on 20-Nov-2018) as a convenience to those like me whose calendar app
 ointment was scheduled at the wrong time due the changes in the DST.  If y
 ou already have the correct appointment on your calendar\, you can ignore 
 this one.\n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/
 j/309416964\nOr\niPhone one-tap (US Toll): +14086380968\,\,309416964
 # or +16465588656\,\,309416964#\nOr\nTelephone: Dial: +1 408 638 0968 (US 
 Toll) or +1 646 558 8656 (US Toll) +1 855 880 1246 (US Toll Free) +1 877 3
 69 0926 (US Toll Free)\nMeeting ID: 309 416 964\nInternational numbers ava
 ilable: https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT<
 https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_zoomconferenc
 e-3Fm-3D30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT=DwMFoQ=LFYZ-o9_HUMeMTSQicvjIg
 =1avnrliG2ZNIjGQV4rWQZg=9i_b101x-TPTtN9bB0Cj4NoV2nAWslXcob1JoKdi-rI=
 m3tFPxbLVXl0jvk-CTZ9SF8kLmaer24OvaPSXdBQjPs=>\n\n\n\n
SUMMARY;LANGUAGE=en-US:SO Weekly Meeting Schedule... (New DST effect)
DTSTART;TZID=China Standard Time:20181121T223000
DTEND;TZID=China Standard Time:20190430T233000
UID:04008200E00074C5B7101A82E008F5EC17E97C80D401000

[onap-discuss] SO weekly Meeting is cancelled - On the occasion of Diwai

2018-11-06 Thread seshu kumar m 
Dear All,

We would not be having our SO weekly meeting this week on the occasion of 
Diwali.



Subject: SO weekly meeting
When: Wednesday, November 07, 2018 8:00 PM-9:00 PM (UTC+05:30) Sri 
Jayawardenepura.
Where: https://zoom.us/j/309416964


[so] Weekly Meeting
https://zoom.us/j/309416964
NOTE: I'm sending out this meeting notice (on 20-Feb-2018) as a convenience to 
those like me whose calendar appointment was scheduled at the wrong time.  If 
you already have the correct appointment on your calendar, you can ignore this 
one.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/309416964
Or
iPhone one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964#
Or
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free)
Meeting ID: 309 416 964
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT

Thanks and Regards,
M Seshu Kumar
Senior System Architect
Single OSS India Branch Department. S/W BU.
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
[Company_logo]
___
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
---


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13524): https://lists.onap.org/g/onap-discuss/message/13524
Mute This Topic: https://lists.onap.org/mt/27868617/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [SO] Weekly Meeting Minutes

2018-08-22 Thread Marcus G K Williams 
https://wiki.onap.org/display/DW/SO+Weekly+Meeting+8-22-2018

Thanks,

Marcus Williams
IRC, Twitter, etc. @ mgkwill
Intel Corp.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12005): https://lists.onap.org/g/onap-discuss/message/12005
Mute This Topic: https://lists.onap.org/mt/24920301/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [so] Weekly Meeting CANCELLED 15 Aug 2018 in the event of National Holiday

2018-08-14 Thread seshu kumar m 
[so] Weekly Meeting CANCELLED on 15th August 2018 in the event of National 
Holiday

https://zoom.us/j/309416964
NOTE: I'm sending out this meeting notice (on 20-Feb-2018) as a convenience to 
those like me whose calendar appointment was scheduled at the wrong time.  If 
you already have the correct appointment on your calendar, you can ignore this 
one.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/309416964
Or
iPhone one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964#
Or
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free)
Meeting ID: 309 416 964
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT


Thanks and Regards,
M Seshu Kumar
Senior System Architect
Single OSS India Branch Department. S/W BU.
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
[Company_logo]
___
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
---


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11872): https://lists.onap.org/g/onap-discuss/message/11872
Mute This Topic: https://lists.onap.org/mt/24523963/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [E] Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-27 Thread Tal Liron 
rk completely in TOSCA mode even for
>>>workflows and then share the same in standard format for future purposes.
>>>- Having HEAT / TOSCA backend : I second Tal's view on this one.
>>>IMHO SO shouldn't be coupled with controller logic and SO's core logic
>>>should be based on BPMN. It is the BPMN engine which is at the heart of 
>>> SO,
>>>    which is making SO as a SO. Addition of new controller logic ( HEAT / any
>>>other format ) should follow existing adapter logic in SO, thereby it is
>>>extendable & scalable. This idea / PoC is actually providing a "friendly"
>>>wrapper on top of BPMN. that's it.
>>>
>>> Hope this sets the stage for future discussions on this topic.
>>>
>>> @Tal Liron  : It was a great show !
>>>
>>> BR,
>>> Viswa
>>>
>>> <http://www.verizon.com>
>>>
>>> Viswanath Kumar Skand Priya
>>> Senior Architect
>>> Technology, Architecture & Planning
>>>
>>>
>>>
>>> On Thu, Jul 26, 2018 at 6:39 PM Steve Smokowski  wrote:
>>>
>>>> Thank you for the readme
>>>>
>>>>
>>>>
>>>> -Steve
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From: * on behalf of Tal Liron <
>>>> tli...@redhat.com>
>>>> *Reply-To: *"onap-discuss@lists.onap.org" ,
>>>> "tli...@redhat.com" 
>>>> *Date: *Thursday, July 26, 2018 at 9:07 AM
>>>> *To: *onap-discuss 
>>>> *Subject: *Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018
>>>>
>>>>
>>>>
>>>> Hi Steve,
>>>>
>>>>
>>>>
>>>> At your request I wrote a detailed README describing the solution and
>>>> the example: https://github.com/tliron/puccini-bpmn/
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=wl1FD1fND7cuPeOEzE0FYxXfWxXz4hQcW_2AWtLRQdA=>
>>>>
>>>>
>>>>
>>>> For convenience, I will reproduce it here:
>>>> Features
>>>>
>>>> The imports directory has everything needed to generate BPMN from
>>>> TOSCA. Specifically there is bpmn.yaml
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.yaml=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=dNdhlhIFjwpk0aq_f8qmQwtK36nT7UKlnz8_Buf8VCU=>,
>>>> which has the type information and in turn imports bpmn.js
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.js=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=VdPzf1BX7bl-4ZxS7AMZr4PzzMsiuH0fg6bg8tJg31o=>,
>>>> which is the JavaScript code to generate BPMN.
>>>>
>>>> Two TOSCA features (introduced in TOSCA 1.1) are supported:
>>>> Workflows
>>>>
>>>> TOSCA declarative workflows are translated into BPMN processes. Because
>>>> a TOSCA workflow is essentially a graph of steps with sequential and
>>>> parallel sections, in BPMN we must represent the graph using parallel
>>>> gateways, diverging or converging as the case may be, as well as
>>>> conditional gateways to represent step success or failure. The JavaScript
>>>> analyzes the graph and inserts the appropriate gateways between the steps.
>>>>
>>>> Each step in TOSCA comprises zero or more activities that should happen
>>>> in sequence. In BPMN, all the activities in the step become a single
>>>> scriptTask entity. For now, we create a script made of pseudo-code
>>>> that calls these activities. A complete solution would require a BPM
>>>> orchestration environment and real code that would actually call node
>>>> instances deployed in a cloud.
>>>>
>>>> Once the BPMN process is imported into BPM software, you may include
>>>> this process as a sub-process within other BPM processes. The workflow may
>>>> or may not hand control back to another sub-process, so that it may or may
>>>> not be a continuation of a control loop.
>>>> Policies and Policy Triggers
>>>>
>>>> Policy triggers are also trans

Re: [E] Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-27 Thread Viswanath Kumar Skand Priya via Lists.Onap.Org 
ase, SO and the rest of ONAP. :)
>
> On Fri, Jul 27, 2018 at 6:28 AM Viswanath V Kumar Skand Priya <
> viswanath.kumarskandpr...@verizon.com> wrote:
>
>> Dear All / SO team,
>>
>> During last SO call, I was caught inbetween 2 calls and wan't able to
>> participate in SO call, was largely in hearing mode. I would like to add
>> few points esp on the perspectives raised by Seshu ( reuse existing BPMN
>> and do something about it ) & Alex ( adding HEAT / TOSCA backend for
>> puccini ).
>>
>> One of the motivation behind this PoC ( atleast for me ) is to bridge gap
>> between BPMN driven orchestration ( imperative style ) Vs TOSCA driven
>> orchestration ( declarative style ). It is also important to note that,
>> both styles has its own merits / demerits and both are suitable for
>> specific set of use-cases. However in a typical service provider landscape,
>> esp with the advent of NFV, the boundary between network orchestration & IT
>> orchestration is becoming more fuzzy. We would normally need the
>> flexibility of doing both styles.
>>
>> IMHO TOSCA is well suited for "expressing" what you want to do and what
>> steps you want to take in doing that thing. However BPMN is really suited
>> to actually "do" that orchestration. In current ONAP story ( where we don't
>> have E2E TOSCA ), if I want to create a network service with a specific
>> work flow, I have to "design a BPMN" for my case and then tie it with the
>> engine. Though one can argue that, BPMNs are resuable, they are already
>> abstract , they can be tied / chained with each other etc, practically it
>> is still a complex process. TOSCA on other hands helps us to define what we
>> want in more flexible & extendable way. So the idea here is to express what
>> you want to do in TOSCA and execute it via BPMN. Thereby we get best of
>> both worlds, with minimal impact to existing architecture.
>>
>> Now coming to the perspectives :
>>
>>- Re-use existing BPMN : Like I quoted above, the idea is to generate
>>a BPMN flow dynamically from input TOSCA. This can be further refined to
>>hook up with existing BPMN if it makes sense. The crux of this idea is to
>>let the designer work completely in TOSCA mode even for workflows and then
>>share the same in standard format for future purposes.
>>- Having HEAT / TOSCA backend : I second Tal's view on this one. IMHO
>>SO shouldn't be coupled with controller logic and SO's core logic should 
>> be
>>based on BPMN. It is the BPMN engine which is at the heart of SO, which is
>>making SO as a SO. Addition of new controller logic ( HEAT / any other
>>format ) should follow existing adapter logic in SO, thereby it is
>>extendable & scalable. This idea / PoC is actually providing a "friendly"
>>wrapper on top of BPMN. that's it.
>>
>> Hope this sets the stage for future discussions on this topic.
>>
>> @Tal Liron  : It was a great show !
>>
>> BR,
>> Viswa
>>
>> <http://www.verizon.com>
>>
>> Viswanath Kumar Skand Priya
>> Senior Architect
>> Technology, Architecture & Planning
>>
>>
>>
>> On Thu, Jul 26, 2018 at 6:39 PM Steve Smokowski  wrote:
>>
>>> Thank you for the readme
>>>
>>>
>>>
>>> -Steve
>>>
>>>
>>>
>>>
>>>
>>> *From: * on behalf of Tal Liron <
>>> tli...@redhat.com>
>>> *Reply-To: *"onap-discuss@lists.onap.org" ,
>>> "tli...@redhat.com" 
>>> *Date: *Thursday, July 26, 2018 at 9:07 AM
>>> *To: *onap-discuss 
>>> *Subject: *Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018
>>>
>>>
>>>
>>> Hi Steve,
>>>
>>>
>>>
>>> At your request I wrote a detailed README describing the solution and
>>> the example: https://github.com/tliron/puccini-bpmn/
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=wl1FD1fND7cuPeOEzE0FYxXfWxXz4hQcW_2AWtLRQdA=>
>>>
>>>
>>>
>>> For convenience, I will reproduce it here:
>>> Features
>>>
>>> The imports directory has everything needed to generate BPMN from
>>> TOSCA. Specifically there is bpmn.yaml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_b

Re: [E] Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-27 Thread Tal Liron 
mpletely in TOSCA mode even for workflows and then
>share the same in standard format for future purposes.
>- Having HEAT / TOSCA backend : I second Tal's view on this one. IMHO
>SO shouldn't be coupled with controller logic and SO's core logic should be
>based on BPMN. It is the BPMN engine which is at the heart of SO, which is
>making SO as a SO. Addition of new controller logic ( HEAT / any other
>format ) should follow existing adapter logic in SO, thereby it is
>extendable & scalable. This idea / PoC is actually providing a "friendly"
>wrapper on top of BPMN. that's it.
>
> Hope this sets the stage for future discussions on this topic.
>
> @Tal Liron  : It was a great show !
>
> BR,
> Viswa
>
> <http://www.verizon.com>
>
> Viswanath Kumar Skand Priya
> Senior Architect
> Technology, Architecture & Planning
>
>
>
> On Thu, Jul 26, 2018 at 6:39 PM Steve Smokowski  wrote:
>
>> Thank you for the readme
>>
>>
>>
>> -Steve
>>
>>
>>
>>
>>
>> *From: * on behalf of Tal Liron <
>> tli...@redhat.com>
>> *Reply-To: *"onap-discuss@lists.onap.org" ,
>> "tli...@redhat.com" 
>> *Date: *Thursday, July 26, 2018 at 9:07 AM
>> *To: *onap-discuss 
>> *Subject: *Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018
>>
>>
>>
>> Hi Steve,
>>
>>
>>
>> At your request I wrote a detailed README describing the solution and the
>> example: https://github.com/tliron/puccini-bpmn/
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=wl1FD1fND7cuPeOEzE0FYxXfWxXz4hQcW_2AWtLRQdA=>
>>
>>
>>
>> For convenience, I will reproduce it here:
>> Features
>>
>> The imports directory has everything needed to generate BPMN from TOSCA.
>> Specifically there is bpmn.yaml
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.yaml=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=dNdhlhIFjwpk0aq_f8qmQwtK36nT7UKlnz8_Buf8VCU=>,
>> which has the type information and in turn imports bpmn.js
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.js=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=VdPzf1BX7bl-4ZxS7AMZr4PzzMsiuH0fg6bg8tJg31o=>,
>> which is the JavaScript code to generate BPMN.
>>
>> Two TOSCA features (introduced in TOSCA 1.1) are supported:
>> Workflows
>>
>> TOSCA declarative workflows are translated into BPMN processes. Because a
>> TOSCA workflow is essentially a graph of steps with sequential and parallel
>> sections, in BPMN we must represent the graph using parallel gateways,
>> diverging or converging as the case may be, as well as conditional gateways
>> to represent step success or failure. The JavaScript analyzes the graph and
>> inserts the appropriate gateways between the steps.
>>
>> Each step in TOSCA comprises zero or more activities that should happen
>> in sequence. In BPMN, all the activities in the step become a single
>> scriptTask entity. For now, we create a script made of pseudo-code that
>> calls these activities. A complete solution would require a BPM
>> orchestration environment and real code that would actually call node
>> instances deployed in a cloud.
>>
>> Once the BPMN process is imported into BPM software, you may include this
>> process as a sub-process within other BPM processes. The workflow may or
>> may not hand control back to another sub-process, so that it may or may not
>> be a continuation of a control loop.
>> Policies and Policy Triggers
>>
>> Policy triggers are also translated into BPMN processes. Because the
>> trigger must be executed from within an orchestrator on node instances
>> deployed in a cloud, within configurable time intervals or schedules, this
>> BPM process essentially hands over control of the loop to the orchestrator.
>> By launching a new sub-process when triggered, control is handed back to
>> the business process: an open loop.
>>
>> A single scriptTask entity is created for each target node of the
>> policy, and all are executed in parallel using diverging/converging
>> parallel gateways. A conditional gateway at the convergence is used to
>> launch a new sub-process if any of the tasks succeed. Again, the

Re: [E] Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-27 Thread Steve Smokowski 
Next week I would like to cover the newer BB refactor we did in BPMN, and give 
some thoughts on how that would integrate into the solution that you have 
presented here.  Essentially delegating that top layer entirely to TOSCA to 
orchestrate the E2E flow.  I think we are not all that far off from re-using 
being able to re-use our BPMN artifacts, and still hand off the end to end flow 
to TOSCA entirely.
On Jul 27, 2018, at 7:28 AM, Viswanath V Kumar Skand Priya 
mailto:viswanath.kumarskandpr...@verizon.com>>
 wrote:

Dear All / SO team,

During last SO call, I was caught inbetween 2 calls and wan't able to 
participate in SO call, was largely in hearing mode. I would like to add few 
points esp on the perspectives raised by Seshu ( reuse existing BPMN and do 
something about it ) & Alex ( adding HEAT / TOSCA backend for puccini ).

One of the motivation behind this PoC ( atleast for me ) is to bridge gap 
between BPMN driven orchestration ( imperative style ) Vs TOSCA driven 
orchestration ( declarative style ). It is also important to note that, both 
styles has its own merits / demerits and both are suitable for specific set of 
use-cases. However in a typical service provider landscape, esp with the advent 
of NFV, the boundary between network orchestration & IT orchestration is 
becoming more fuzzy. We would normally need the flexibility of doing both 
styles.

IMHO TOSCA is well suited for "expressing" what you want to do and what steps 
you want to take in doing that thing. However BPMN is really suited to actually 
"do" that orchestration. In current ONAP story ( where we don't have E2E TOSCA 
), if I want to create a network service with a specific work flow, I have to 
"design a BPMN" for my case and then tie it with the engine. Though one can 
argue that, BPMNs are resuable, they are already abstract , they can be tied / 
chained with each other etc, practically it is still a complex process. TOSCA 
on other hands helps us to define what we want in more flexible & extendable 
way. So the idea here is to express what you want to do in TOSCA and execute it 
via BPMN. Thereby we get best of both worlds, with minimal impact to existing 
architecture.

Now coming to the perspectives :

  *   Re-use existing BPMN : Like I quoted above, the idea is to generate a 
BPMN flow dynamically from input TOSCA. This can be further refined to hook up 
with existing BPMN if it makes sense. The crux of this idea is to let the 
designer work completely in TOSCA mode even for workflows and then share the 
same in standard format for future purposes.
  *   Having HEAT / TOSCA backend : I second Tal's view on this one. IMHO SO 
shouldn't be coupled with controller logic and SO's core logic should be based 
on BPMN. It is the BPMN engine which is at the heart of SO, which is making SO 
as a SO. Addition of new controller logic ( HEAT / any other format ) should 
follow existing adapter logic in SO, thereby it is extendable & scalable. This 
idea / PoC is actually providing a "friendly" wrapper on top of BPMN. that's it.

Hope this sets the stage for future discussions on this topic.

@Tal Liron<mailto:tli...@redhat.com> : It was a great show !

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.verizon.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=_7HB2lj9Jl-oIgvmXgZiChFxXitstQ0ypVnHFgkjJwE=aiTojQmzLbgvSchz3l5WyGigijkg5mzUJWrGWnE98d4=>

Viswanath Kumar Skand Priya
Senior Architect
Technology, Architecture & Planning



On Thu, Jul 26, 2018 at 6:39 PM Steve Smokowski 
mailto:ss8...@att.com>> wrote:
Thank you for the readme

-Steve


From: mailto:onap-discuss@lists.onap.org>> on 
behalf of Tal Liron mailto:tli...@redhat.com>>
Reply-To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, 
"tli...@redhat.com<mailto:tli...@redhat.com>" 
mailto:tli...@redhat.com>>
Date: Thursday, July 26, 2018 at 9:07 AM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

Hi Steve,

At your request I wrote a detailed README describing the solution and the 
example: 
https://github.com/tliron/puccini-bpmn/<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=wl1FD1fND7cuPeOEzE0FYxXfWxXz4hQcW_2AWtLRQdA=>

For convenience, I will reproduce it here:
Features

The imports directory has everything needed to generate BPMN from TOSCA. 
Specifically there is 
bpmn.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.yaml=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=Jz

Re: [E] Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-27 Thread Viswanath Kumar Skand Priya via Lists.Onap.Org 
Dear All / SO team,

During last SO call, I was caught inbetween 2 calls and wan't able to
participate in SO call, was largely in hearing mode. I would like to add
few points esp on the perspectives raised by Seshu ( reuse existing BPMN
and do something about it ) & Alex ( adding HEAT / TOSCA backend for
puccini ).

One of the motivation behind this PoC ( atleast for me ) is to bridge gap
between BPMN driven orchestration ( imperative style ) Vs TOSCA driven
orchestration ( declarative style ). It is also important to note that,
both styles has its own merits / demerits and both are suitable for
specific set of use-cases. However in a typical service provider landscape,
esp with the advent of NFV, the boundary between network orchestration & IT
orchestration is becoming more fuzzy. We would normally need the
flexibility of doing both styles.

IMHO TOSCA is well suited for "expressing" what you want to do and what
steps you want to take in doing that thing. However BPMN is really suited
to actually "do" that orchestration. In current ONAP story ( where we don't
have E2E TOSCA ), if I want to create a network service with a specific
work flow, I have to "design a BPMN" for my case and then tie it with the
engine. Though one can argue that, BPMNs are resuable, they are already
abstract , they can be tied / chained with each other etc, practically it
is still a complex process. TOSCA on other hands helps us to define what we
want in more flexible & extendable way. So the idea here is to express what
you want to do in TOSCA and execute it via BPMN. Thereby we get best of
both worlds, with minimal impact to existing architecture.

Now coming to the perspectives :

   - Re-use existing BPMN : Like I quoted above, the idea is to generate a
   BPMN flow dynamically from input TOSCA. This can be further refined to hook
   up with existing BPMN if it makes sense. The crux of this idea is to let
   the designer work completely in TOSCA mode even for workflows and then
   share the same in standard format for future purposes.
   - Having HEAT / TOSCA backend : I second Tal's view on this one. IMHO SO
   shouldn't be coupled with controller logic and SO's core logic should be
   based on BPMN. It is the BPMN engine which is at the heart of SO, which is
   making SO as a SO. Addition of new controller logic ( HEAT / any other
   format ) should follow existing adapter logic in SO, thereby it is
   extendable & scalable. This idea / PoC is actually providing a "friendly"
   wrapper on top of BPMN. that's it.

Hope this sets the stage for future discussions on this topic.

@Tal Liron  : It was a great show !

BR,
Viswa

<http://www.verizon.com>

Viswanath Kumar Skand Priya
Senior Architect
Technology, Architecture & Planning



On Thu, Jul 26, 2018 at 6:39 PM Steve Smokowski  wrote:

> Thank you for the readme
>
>
>
> -Steve
>
>
>
>
>
> *From: * on behalf of Tal Liron <
> tli...@redhat.com>
> *Reply-To: *"onap-discuss@lists.onap.org" , "
> tli...@redhat.com" 
> *Date: *Thursday, July 26, 2018 at 9:07 AM
> *To: *onap-discuss 
> *Subject: *Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018
>
>
>
> Hi Steve,
>
>
>
> At your request I wrote a detailed README describing the solution and the
> example: https://github.com/tliron/puccini-bpmn/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=wl1FD1fND7cuPeOEzE0FYxXfWxXz4hQcW_2AWtLRQdA=>
>
>
>
> For convenience, I will reproduce it here:
> Features
>
> The imports directory has everything needed to generate BPMN from TOSCA.
> Specifically there is bpmn.yaml
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.yaml=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=dNdhlhIFjwpk0aq_f8qmQwtK36nT7UKlnz8_Buf8VCU=>,
> which has the type information and in turn imports bpmn.js
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.js=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=VdPzf1BX7bl-4ZxS7AMZr4PzzMsiuH0fg6bg8tJg31o=>,
> which is the JavaScript code to generate BPMN.
>
> Two TOSCA features (introduced in TOSCA 1.1) are supported:
> Workflows
>
> TOSCA declarative workflows are translated into BPMN processes. Because a
> TOSCA workflow is essentially a graph of steps with sequential and parallel
> sections, in BPMN we must represent the graph using parallel gateways,
> diverging or converging as the case may be, as well as conditional gateways
> to represent step succ

Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-26 Thread Steve Smokowski 
Thank you for the readme

-Steve


From:  on behalf of Tal Liron 
Reply-To: "onap-discuss@lists.onap.org" , 
"tli...@redhat.com" 
Date: Thursday, July 26, 2018 at 9:07 AM
To: onap-discuss 
Subject: Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

Hi Steve,

At your request I wrote a detailed README describing the solution and the 
example: 
https://github.com/tliron/puccini-bpmn/<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=wl1FD1fND7cuPeOEzE0FYxXfWxXz4hQcW_2AWtLRQdA=>

For convenience, I will reproduce it here:
Features

The imports directory has everything needed to generate BPMN from TOSCA. 
Specifically there is 
bpmn.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.yaml=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=dNdhlhIFjwpk0aq_f8qmQwtK36nT7UKlnz8_Buf8VCU=>,
 which has the type information and in turn imports 
bpmn.js<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_imports_bpmn.js=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=VdPzf1BX7bl-4ZxS7AMZr4PzzMsiuH0fg6bg8tJg31o=>,
 which is the JavaScript code to generate BPMN.

Two TOSCA features (introduced in TOSCA 1.1) are supported:

Workflows

TOSCA declarative workflows are translated into BPMN processes. Because a TOSCA 
workflow is essentially a graph of steps with sequential and parallel sections, 
in BPMN we must represent the graph using parallel gateways, diverging or 
converging as the case may be, as well as conditional gateways to represent 
step success or failure. The JavaScript analyzes the graph and inserts the 
appropriate gateways between the steps.

Each step in TOSCA comprises zero or more activities that should happen in 
sequence. In BPMN, all the activities in the step become a single scriptTask 
entity. For now, we create a script made of pseudo-code that calls these 
activities. A complete solution would require a BPM orchestration environment 
and real code that would actually call node instances deployed in a cloud.

Once the BPMN process is imported into BPM software, you may include this 
process as a sub-process within other BPM processes. The workflow may or may 
not hand control back to another sub-process, so that it may or may not be a 
continuation of a control loop.

Policies and Policy Triggers

Policy triggers are also translated into BPMN processes. Because the trigger 
must be executed from within an orchestrator on node instances deployed in a 
cloud, within configurable time intervals or schedules, this BPM process 
essentially hands over control of the loop to the orchestrator. By launching a 
new sub-process when triggered, control is handed back to the business process: 
an open loop.

A single scriptTask entity is created for each target node of the policy, and 
all are executed in parallel using diverging/converging parallel gateways. A 
conditional gateway at the convergence is used to launch a new sub-process if 
any of the tasks succeed. Again, the script is made of pseudo-code that would 
call these operations within a BPM orchestration environment.

Example

Included is an example TOSCA service template, 
open-loop.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_open-2Dloop.yaml=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=iFiYk9ow9wzmmdlb6vlHRxxebiWlYuh81k74D7Y7JJo=>.
 This example demonstrates an open loop policy, notify_on_high_load, which has 
a trigger that runs an operation to get the CPU load on Compute nodes. If this 
operation returns true then a BPM process named NotifyUser would be launched.

Also included is a TOSCA workflow named backup, which comprises a step graph 
that calls an operation on an interface while making sure to set node states, 
notify on failure, etc. This generated BPMN process can be executed on its own, 
or included as a sub-process within larger business processes. Because it does 
not hand control back to any other process when done, it represents an end 
event within a control loop.

We've already included sample output of this example in 
open-loop.bpmn2<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tliron_puccini-2Dbpmn_blob_master_open-2Dloop.bpmn2=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=JzO-UjYTbJGUMdAp-GBJsvFFs6ShpUxOx1OcnoUcxyA=NrBOWJ3QNr7UKdyvZrEe3PCrzZBRve65REH0-SnF72A=>.

To recreate the output, run this command (tested with Puccini 0.2):

puccini-tosca compile open-loop.yaml | puccini-js exec bpmn -o open-loop.bpmn2

Also included is 
open-loop-design.bpmn2<https://urldefense.proofpoint.com/v2/url?u=https-

Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-26 Thread Tal Liron 
Hi Steve,

At your request I wrote a detailed README describing the solution and the
example: https://github.com/tliron/puccini-bpmn/

For convenience, I will reproduce it here:
Features

The imports directory has everything needed to generate BPMN from TOSCA.
Specifically there is bpmn.yaml
,
which has the type information and in turn imports bpmn.js
, which
is the JavaScript code to generate BPMN.

Two TOSCA features (introduced in TOSCA 1.1) are supported:
Workflows

TOSCA declarative workflows are translated into BPMN processes. Because a
TOSCA workflow is essentially a graph of steps with sequential and parallel
sections, in BPMN we must represent the graph using parallel gateways,
diverging or converging as the case may be, as well as conditional gateways
to represent step success or failure. The JavaScript analyzes the graph and
inserts the appropriate gateways between the steps.

Each step in TOSCA comprises zero or more activities that should happen in
sequence. In BPMN, all the activities in the step become a single scriptTask
entity. For now, we create a script made of pseudo-code that calls these
activities. A complete solution would require a BPM orchestration
environment and real code that would actually call node instances deployed
in a cloud.

Once the BPMN process is imported into BPM software, you may include this
process as a sub-process within other BPM processes. The workflow may or
may not hand control back to another sub-process, so that it may or may not
be a continuation of a control loop.
Policies
and Policy Triggers

Policy triggers are also translated into BPMN processes. Because the
trigger must be executed from within an orchestrator on node instances
deployed in a cloud, within configurable time intervals or schedules, this
BPM process essentially hands over control of the loop to the orchestrator.
By launching a new sub-process when triggered, control is handed back to
the business process: an open loop.

A single scriptTask entity is created for each target node of the policy,
and all are executed in parallel using diverging/converging parallel
gateways. A conditional gateway at the convergence is used to launch a new
sub-process if any of the tasks succeed. Again, the script is made of
pseudo-code that would call these operations within a BPM orchestration
environment.
Example

Included is an example TOSCA service template, open-loop.yaml
. This
example demonstrates an open loop policy, notify_on_high_load, which has a
trigger that runs an operation to get the CPU load on Compute nodes. If
this operation returns true then a BPM process named NotifyUser would be
launched.

Also included is a TOSCA workflow named backup, which comprises a step
graph that calls an operation on an interface while making sure to set node
states, notify on failure, etc. This generated BPMN process can be executed
on its own, or included as a sub-process within larger business processes.
Because it does not hand control back to any other process when done, it
represents an end event within a control loop.

We've already included sample output of this example in open-loop.bpmn2
.

To recreate the output, run this command (tested with Puccini 0.2):

puccini-tosca compile open-loop.yaml | puccini-js exec bpmn -o open-loop.bpmn2

Also included is open-loop-design.bpmn2
,
which is the same file with added diagram information so that it would
appear more nicely in a BPMN GUI. We used the Eclipse BPMN2 modeler
 to edit the diagram.

You can import either file into your BPM software. Tested with jBPM
 7.8.0.

On Thu, Jul 26, 2018 at 6:51 AM Steve Smokowski  wrote:

> Is there a readme or walkthrough of how we can reproduce the demo shown?
> Or can you share the command used to take Puccini and have it output the
> bpmn?
>
>
>
> It appears to be something like
>
>
>
> -Parse CSAR using Puccini
>
> -Output to Clout
>
> -Utilize Clout output to the javascript file to transform to bpmn
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11444): https://lists.onap.org/g/onap-discuss/message/11444
Mute This Topic: https://lists.onap.org/mt/23813337/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-26 Thread Steve Smokowski 
Is there a readme or walkthrough of how we can reproduce the demo shown?  Or 
can you share the command used to take Puccini and have it output the bpmn?

It appears to be something like

-Parse CSAR using Puccini
-Output to Clout
-Utilize Clout output to the javascript file to transform to bpmn

Thanks

-Steve


From:  on behalf of Tal Liron 
Reply-To: "onap-discuss@lists.onap.org" , 
"tli...@redhat.com" 
Date: Wednesday, July 25, 2018 at 12:55 PM
To: onap-discuss , Seshu m 

Subject: Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

Hi Seshu,

I'm getting numerous private requests for a recording of the meeting. Did you 
end up recording?

On Wed, Jul 25, 2018 at 11:01 AM Tal Liron 
mailto:tli...@redhat.com>> wrote:
Thank you all for participating in my TOSCA/BPMN demonstration.

We can continue brainstorming ideas here on the mailing list rather than 
waiting for next week's meeting. In general it's a good idea to use email more 
for discussion, as it encourages more visibility and participation.

On Wed, Jul 25, 2018 at 9:37 AM Marcus G K Williams 
mailto:marcus.willi...@intel.com>> wrote:
https://wiki.onap.org/display/DW/SO+Weekly+Meeting+7-25-2018<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_SO-2BWeekly-2BMeeting-2B7-2D25-2D2018=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=shs6nPzThSiGJml9VXN0Eg=n5v6m61-xl-pff6EuQeZvxTNeaQ0jiBKUj1qNRlthMg=SdPqMr5J44n8G5K8JCxjVY6RH_d-3x18mAV7Cep_XjQ=>

Thanks,

Marcus Williams
IRC, Twitter, etc. @ mgkwill
Intel Corp.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11441): https://lists.onap.org/g/onap-discuss/message/11441
Mute This Topic: https://lists.onap.org/mt/23813337/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-25 Thread Tal Liron 
Hi Seshu,

I'm getting numerous private requests for a recording of the meeting. Did
you end up recording?

On Wed, Jul 25, 2018 at 11:01 AM Tal Liron  wrote:

> Thank you all for participating in my TOSCA/BPMN demonstration.
>
> We can continue brainstorming ideas here on the mailing list rather than
> waiting for next week's meeting. In general it's a good idea to use email
> more for discussion, as it encourages more visibility and participation.
>
> On Wed, Jul 25, 2018 at 9:37 AM Marcus G K Williams <
> marcus.willi...@intel.com> wrote:
>
>> https://wiki.onap.org/display/DW/SO+Weekly+Meeting+7-25-2018
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Marcus Williams
>>
>> IRC, Twitter, etc. @ mgkwill
>>
>> Intel Corp.
>>
>>
>> 
>>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11427): https://lists.onap.org/g/onap-discuss/message/11427
Mute This Topic: https://lists.onap.org/mt/23813337/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-25 Thread Tal Liron 
Thank you all for participating in my TOSCA/BPMN demonstration.

We can continue brainstorming ideas here on the mailing list rather than
waiting for next week's meeting. In general it's a good idea to use email
more for discussion, as it encourages more visibility and participation.

On Wed, Jul 25, 2018 at 9:37 AM Marcus G K Williams <
marcus.willi...@intel.com> wrote:

> https://wiki.onap.org/display/DW/SO+Weekly+Meeting+7-25-2018
>
>
>
> Thanks,
>
>
>
> Marcus Williams
>
> IRC, Twitter, etc. @ mgkwill
>
> Intel Corp.
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11426): https://lists.onap.org/g/onap-discuss/message/11426
Mute This Topic: https://lists.onap.org/mt/23813337/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [SO] Weekly Meeting Minutes 7-25-2018

2018-07-25 Thread Marcus G K Williams 
https://wiki.onap.org/display/DW/SO+Weekly+Meeting+7-25-2018

Thanks,

Marcus Williams
IRC, Twitter, etc. @ mgkwill
Intel Corp.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11419): https://lists.onap.org/g/onap-discuss/message/11419
Mute This Topic: https://lists.onap.org/mt/23813337/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss][SO] Weekly MEETING CANCELLED due to July 4th holiday in USA

2018-07-04 Thread seshu kumar m 
Dear All

The SO weekly meeting has been cancelled due to the July 4th holiday in USA.

Thanks and Regards,
M Seshu Kumar
Senior System Architect
Single OSS India Branch Department. S/W BU.
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
[Company_logo]
___
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
---

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Mike Elliott
Sent: Wednesday, July 04, 2018 8:39 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss][oom] MEETING CANCELLED due to July 4th holiday in USA

more details 
»
[oom] Weekly Meeing
Hi there,
ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/118908904
Or iPhone one-tap (US Toll): +14086380968,,118908904# or 
+16465588656,,118908904#
Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 118 908 904
International numbers available: 
https://zoom.us/zoomconference?m=RjcDSzvXlwMWG5gaHA7q936bD1fmNWjr





When

Weekly from 7am to 8am on Wednesday Pacific Time

Where

https://zoom.us/j/118908904 
(map)

Calendar

onap-discuss@lists.onap.org

Who

•

kp...@linuxfoundation.org - creator

•

david.sauvag...@bell.ca

•

onap-discuss@lists.onap.org



Going?   All events in this series:   
Yes
 - 
Maybe
 - 
No
more options 
»


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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10837): https://lists.onap.org/g/onap-discuss/message/10837
Mute This Topic: https://lists.onap.org/mt/23038629/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] SO weekly meeting change as per DST

2018-03-12 Thread Seshu m 
Dear Fellow SO ONAPers,

In due to the DST change in US and Europe, the SO weekly meeting tomorrow would 
be held @ Wed UTC 13:30 / China 21:30 / Eastern 09:30 / Pacific 06:30
one hour earlier in other parts (Non Daylight following nations).


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.


本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SO weekly meeting

2017-11-22 Thread DAUGHERTY, ROBERT E 
Seshu is on a business trip and will not be available for this meeting.

I propose that we meet 1 hour later than this scheduled time (i.e. at the old 
time: 9:30 US ET).   Since Seshu is the organizer, I don't think I can change 
the calendar appointment.  The main thing I want to discuss is creating an 
Amsterdam branch for SO, which shouldn't take long.

Rob

-Original Appointment-
From: Seshu m [mailto:seshu.kuma...@huawei.com]
Sent: Wednesday, August 16, 2017 12:06 AM
To: Seshu m; Xinhui Li; Danny Lin; Jinxin (Saw); Zengjianguo (OSS Design); 
Andrew Philip; Yang, Bin; zhanganb...@chinamobile.com; Ethan Lynn; CHOMA, JOHN 
S; DeWayne Filppi; Byung-Woo Jun; wangchen...@chinamobile.com; 
zhonghe...@boco.com.cn; zhang.zh...@zte.com.cn; Chenchuanyu; 
yangyan...@chinamobile.com; DAUGHERTY, ROBERT E; Lingli Deng; 
wu.li...@zte.com.cn; yangyuan...@boco.com.cn; denghui (L); Christopher Donley 
(Chris); alex@intel.com; Vijaykumar S; onap-discuss@lists.onap.org; Praveen 
Krishnamurthy P; SOMASUNDARAM, PRABHURAM; BULLARD, GIL
Subject: FW: SO weekly meeting
When: Wednesday, November 22, 2017 7:00 PM-8:00 PM (UTC+05:30) Chennai, 
Kolkata, Mumbai, New Delhi.
Where:


When: Occurs every Wednesday effective 8/16/2017 from 7:00 PM to 8:00 PM 
(UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi.

Note: The GMT offset above does not reflect daylight saving time adjustments.

*~*~*~*~*~*~*~*~*~*

[so] Weekly Meeting
https://zoom.us/j/309416964

Hi there, ONAP Meeting 8 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/309416964
Or
iPhone one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964#
Or
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free)
Meeting ID: 309 416 964
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [so] Weekly Meeting

2017-08-16 Thread Manoj K Nair 
Hi Seshu,

In today’s SO meeting you mentioned about the bifurcation to Imperative BPMN 
flow and Existing MSO BPMN flow . Can you please clarify how this bifurcation 
is carried out. I just checked the implementation of API handler – 
ServiceInstances.java and found that - String requestJSON, Action action, 
HashMap instanceIdMap, String version parameters are passed for 
Service instantiation . Further  getServiceInstanceOrchestrationURI is used to 
look up the Recipe from Catalog DB.

Can you please confirm if the BPMN URL is selected based on 
msoRequest.getModelInfo().getModelType() ?  Can you please clarify what logic 
is applied for selection of BPMN flow and delegation.

Additionally , is this going to change, because 
here
 there is a proposal to have a generic workflow engine with Camunda and WSO2 
plugins.

Thanks

Manoj

[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Seshu m
Sent: Wednesday, August 09, 2017 1:40 PM
To: onap-discuss@lists.onap.org
Cc: onap-...@lists.onap.org
Subject: [onap-tsc] [so] Weekly Meeting


[so] Weekly Meeting
https://zoom.us/j/309416964
Hi there,
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/309416964 Or iPhone 
one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964# Or 
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 309 416 964 
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT
2:00 PM - 3:00 PM

Best Regards,
Seshu
**
 This email and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained here in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*






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

[onap-discuss] [so] Weekly Meeting

2017-08-09 Thread Seshu m 
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Seshu m:MAILTO:seshu.kuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Xinhui Li:
 MAILTO:lxin...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Danny Lin:
 MAILTO:l...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jinxin (Sa
 w):MAILTO:saw@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Zengjiangu
 o (OSS Design):MAILTO:zengjian...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Phi
 lip:MAILTO:aphi...@microsoft.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang, Bin":
 MAILTO:bin.y...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhanganbin
 g...@chinamobile.com:MAILTO:zhanganb...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ethan Lynn
 :MAILTO:ethanly...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="CHOMA, JOH
 N S":MAILTO:jc1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=DeWayne Fi
 lppi:MAILTO:dewa...@gigaspaces.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Byung-Woo 
 Jun:MAILTO:byung-woo@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangchengl
 i...@chinamobile.com:MAILTO:wangchen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhongheliu
 @boco.com.cn:MAILTO:zhonghe...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhang.zhou
 1...@zte.com.cn:MAILTO:zhang.zh...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chenchuany
 u:MAILTO:chenchua...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyanyjy
 @chinamobile.com:MAILTO:yangyan...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DAUGHERTY,
  ROBERT E":MAILTO:rd4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lingli Den
 g:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wu.liang@z
 te.com.cn:MAILTO:wu.li...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyuanwe
 i...@boco.com.cn:MAILTO:yangyuan...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="BULLARD, G
 IL":MAILTO:wb5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=denghui (L
 ):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=alex.vul@i
 ntel.com:MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Vijaykumar
  S:MAILTO:vijaykuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Praveen Kr
 ishnamurthy P:MAILTO:kprav...@huawei.com
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, August 09\, 2017 7:00 PM-8:00 
 PM (UTC+08:00) Perth.\nWhere: Zoom\n\nNote: The GMT offset above does not 
 reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\n\n[so] W
 eekly Meeting\nhttps://zoom.us/j/309416964\nHi there\,\nONAP Meeting 6 is 
 inviting you to a scheduled Zoom meeting.\nJoin from PC\, Mac\, Linux\, iO
 S or Android: https://zoom.us/j/309416964 Or iPhone one-tap (US Toll): +14
 086380968\,\,309416964# or +16465588656\,\,309416964# Or Telephone: Dial: 
 +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 880 1246 (US
  Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 309 416 964 Interna
 tional numbers available: https://zoom.us/zoomconference?m=30xXqK2sdCwPiwK
 QZLwqW5yEWuwQ7QHT\n1:30 PM - 2:30 PM\n\nBest Regards\,\nSeshu\n***
 **
 *\n This email and its attachments contain confidential information fr
 om HUAWEI\, which is intended only for the person or entity whose address 
 is listed above. Any use of the information contained here in any way (inc
 luding\, but not limited to\, total or partial disclosure\, reproduction\,
  or dissemination) by persons other than the intended recipient(s) is proh
 ibited. If you receive this email in error\, please notify the sender by p
 hone or email immediately and delete it!\n ***

[onap-discuss] [so] Weekly Meeting

2017-08-09 Thread Seshu m 
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:India Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Seshu m:MAILTO:seshu.kuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Xinhui Li:
 MAILTO:lxin...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Danny Lin:
 MAILTO:l...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jinxin (Sa
 w):MAILTO:saw@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Zengjiangu
 o (OSS Design):MAILTO:zengjian...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Phi
 lip:MAILTO:aphi...@microsoft.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang, Bin":
 MAILTO:bin.y...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhanganbin
 g...@chinamobile.com:MAILTO:zhanganb...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ethan Lynn
 :MAILTO:ethanly...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="CHOMA, JOH
 N S":MAILTO:jc1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=DeWayne Fi
 lppi:MAILTO:dewa...@gigaspaces.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Byung-Woo 
 Jun:MAILTO:byung-woo@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangchengl
 i...@chinamobile.com:MAILTO:wangchen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhongheliu
 @boco.com.cn:MAILTO:zhonghe...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhang.zhou
 1...@zte.com.cn:MAILTO:zhang.zh...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chenchuany
 u:MAILTO:chenchua...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyanyjy
 @chinamobile.com:MAILTO:yangyan...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DAUGHERTY,
  ROBERT E":MAILTO:rd4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lingli Den
 g:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wu.liang@z
 te.com.cn:MAILTO:wu.li...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyuanwe
 i...@boco.com.cn:MAILTO:yangyuan...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="BULLARD, G
 IL":MAILTO:wb5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=denghui (L
 ):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=alex.vul@i
 ntel.com:MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Vijaykumar
  S:MAILTO:vijaykuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Praveen Kr
 ishnamurthy P:MAILTO:kprav...@huawei.com
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, August 09\, 2017 7:00 PM-8:00 
 PM (UTC+05:30) Chennai\, Kolkata\, Mumbai\, New Delhi.\nWhere: Zoom\n\nNot
 e: The GMT offset above does not reflect daylight saving time adjustments.
 \n\n*~*~*~*~*~*~*~*~*~*\n\n[so] Weekly Meeting\nhttps://zoom.us/j/30941696
 4\nHi there\,\nONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
 \nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/309416964
  Or iPhone one-tap (US Toll): +14086380968\,\,309416964# or +16465588656\,
 \,309416964# Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8
 656 (US Toll) +1 855 880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free
 ) Meeting ID: 309 416 964 International numbers available: https://zoom.us
 /zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT\n1:30 PM - 2:30 PM UTC\
 n\nSorry about the timezone issue in the previous invite.\n\nBest Regards\
 ,\nSeshu\n
 **\n This email and its attachments contain confid
 ential information from HUAWEI\, which is intended only for the person or 
 entity whose address is listed above. Any use of the information contained
  here in any way (including\, but not limited to\, total or partial disclo
 sure\, reproduction\, or dissemination) by persons other than the intended
  recipient(s) is prohibited. If you receive this email in error\, please n
 otify the sender by phone or email immediately and delete

[onap-discuss] [so] Weekly Meeting

2017-08-09 Thread Seshu m 

[so] Weekly Meeting
https://zoom.us/j/309416964
Hi there,
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/309416964 Or iPhone 
one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964# Or 
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 309 416 964 
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT
2:00 PM - 3:00 PM

Best Regards,
Seshu
**
 This email and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained here in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss