Re: [onap-discuss] [onap-tsc] [modeling] Please vote for chairperson of Modeling Subcommittee

[xiexj...@chinatelecom.cn]

+1

Best Regards，

Xiaojun


From: Xinhui Li
Date: 2017-07-07 14:39
To: denghui (L); onap-...@lists.onap.org; onap-discuss@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] [modeling] Please vote for chairperson 
of Modeling Subcommittee
+1
 
From:  on behalf of "denghui (L)" 

Date: Friday, 7 July 2017 at 11:56 AM
To: "onap-...@lists.onap.org" , 
"onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [modeling] Please vote for chairperson of Modeling 
Subcommittee
 
Hello, Modelling members,
 
There is only one candidate for modeling subcommittee: Hui Deng
 
If you support Please help to vote “+1”, 
If you are neutral, please vote “0”,
If you don’t please respond  “-1” 
 
Members are listed here: https://wiki.onap.org/display/DW/Members
 
Thanks a lot
 
DENG Hui
 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] is docker pull breaking

[xiexj...@chinatelecom.cn]

Thanks，Marco，

I'll try it again.

Xiaojun

From: PLATANIA, MARCO (MARCO)
Date: 2017-05-08 01:42
To: xiexj...@chinatelecom.cn
CC: onap-discuss
Subject: Re: [onap-discuss] is docker pull breaking
Hello Xiaojun,
 
I just manually ran the commands that you also ran, that is:
 
docker login -u docker -p docker nexus3.onap.org:10001
docker search nexus3.onap.org:10001/openecomp/sdc
docker pull nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest
 
and it worked as expected. Please try again. If the error still persists, 
please try to see whether your docker engine installation follows the one in 
the heat template. As you see in your docker search, the container is there, so 
it should be downloaded.
 
Thanks,
Marco  
 
From: "xiexj...@chinatelecom.cn" 
Date: Saturday, May 6, 2017 at 3:42 AM
To: "PLATANIA, MARCO (MARCO)" 
Cc: onap-discuss 
Subject: Re: [onap-discuss] is docker pull breaking
 
Hi, Marco,
 
Following the operations in this mail, 'docker pull' is still failing with the 
error:
 
$ sudo docker login -u docker -p docker nexus3.onap.org:10001
WARNING: login credentials saved in /home/xiexj/.dockercfg.
Login Succeeded
$ sudo docker search nexus3.onap.org:10001/openecomp/sdc
NAME  
DESCRIPTION   STARS OFFICIAL   AUTOMATED
nexus3.onap.org/openecomp/sdc-backend:1.0-STAGING-latest
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0 
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170316T0739   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170316T1240   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170317T1241   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170322T2208   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-20170406T1135  
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-20170405T1442 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-20170406T0859 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-latest
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-latest 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170406T1256   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170407T1318   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170409T1253   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170411T1257   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170412T1302   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170413T1305   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170414T1446   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170415T1326   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170416T1407   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170420T1255   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170421T1518   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170425T1858   
0
$ sudo docker pull 
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/sdc-backend
FATA[0043] Error: image openecomp/sdc-backend:1.0-STAGING-latest not found
 
Is there anything else missing? 
Thanks in advance.


Best Regards,


Xiaojun Xie
 
From: Kanagaraj Manickam
Date: 2017-05-03 02:31
To: PLATANIA, MARCO (MARCO)
CC: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] is docker pull breaking
Hello Marco, 
 
Awesome !. It works now.
 
Thank you
Kanagaraj M
 
On Tue, May 2, 2017 at 9:59 AM, PLATANIA, MARCO (MARCO) 
 wrote:
Hello Kanagaraj,
 
The reason why is failing is that there’s something missing in your docker pull 
instruction. The repository is missing, so it can’t find any container

Re: [onap-discuss] 回复: is docker pull breaking

[xiexj...@chinatelecom.cn]

Thanks, Hulong,

My OS is Ubuntu 14.04.4 LTS (GNU/Linux 4.2.0-27-generic x86_64)

$ sudo docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.2.1
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.2.1
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64

Best Regards,

Xiaojun


发件人： hulon...@mcsue.com
发送时间： 2017-05-06 16:02
收件人： xiexj.gd; PLATANIA, MARCO (MARCO)
抄送： onap-discuss
主题： 回复: [onap-discuss] is docker pull breaking
supposed you have blocked by same issues which i got few weeks ago，may i ask 
you what kind operation system you are running docker? seems CentOS and redhat 
AS is not a good choice.


Regards！
Hulong


 原始邮件 
主题：Re: [onap-discuss] is docker pull breaking
发件人：xiexj...@chinatelecom.cn
收件人："PLATANIA, MARCO (MARCO)" 
抄送：onap-discuss 


Hi, Marco,

Following the operations in this mail, 'docker pull' is still failing with the 
error:

$ sudo docker login -u docker -p docker nexus3.onap.org:10001
WARNING: login credentials saved in /home/xiexj/.dockercfg.
Login Succeeded
$ sudo docker search nexus3.onap.org:10001/openecomp/sdc
NAME  
DESCRIPTION   STARS OFFICIAL   AUTOMATED
nexus3.onap.org/openecomp/sdc-backend:1.0-STAGING-latest
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0 
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170316T0739   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170316T1240   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170317T1241   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170322T2208   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-20170406T1135  
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-20170405T1442 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-20170406T0859 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-latest
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-latest 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170406T1256   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170407T1318   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170409T1253   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170411T1257   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170412T1302   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170413T1305   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170414T1446   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170415T1326   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170416T1407   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170420T1255   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170421T1518   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170425T1858   
0
$ sudo docker pull 
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/sdc-backend
FATA[0043] Error: image openecomp/sdc-backend:1.0-STAGING-latest not found

Is there anything else missing? 
Thanks in advance.

Best Regards,

Xiaojun Xie

From: Kanagaraj Manickam
Date: 2017-05-03 02:31
To: PLATANIA, MARCO (MARCO)
CC: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] is docker pull breaking
Hello Marco,

Awesome !. It works now.

Thank you
Kanagaraj M

On Tue, May 2, 2017 at 9:59 AM, PLATANIA, MARCO (MARCO) 
 wrote:
Hello Kanagaraj,
 
The reason why is failing is that there’s something missing in your docker pull 
instruction. The repository is missing, so it can’t find any container. These 
are the correct operations:
 
do

Re: [onap-discuss] is docker pull breaking

[xiexj...@chinatelecom.cn]

Hi, Marco,

Following the operations in this mail, 'docker pull' is still failing with the 
error:

$ sudo docker login -u docker -p docker nexus3.onap.org:10001
WARNING: login credentials saved in /home/xiexj/.dockercfg.
Login Succeeded
$ sudo docker search nexus3.onap.org:10001/openecomp/sdc
NAME  
DESCRIPTION   STARS OFFICIAL   AUTOMATED
nexus3.onap.org/openecomp/sdc-backend:1.0-STAGING-latest
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0 
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170316T0739   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170316T1240   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170317T1241   
0
nexus3.onap.org/openecomp/sdc-backend:1.0.0-STAGING-20170322T2208   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-20170406T1135  
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-20170405T1442 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-20170406T0859 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-SNAPSHOT-latest
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-SNAPSHOT-latest 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING 
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170406T1256   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170407T1318   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170409T1253   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170411T1257   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170412T1302   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170413T1305   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170414T1446   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170415T1326   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170416T1407   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170420T1255   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170421T1518   
0
nexus3.onap.org/openecomp/sdc-backend:1.1.0-STAGING-20170425T1858   
0
$ sudo docker pull 
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/sdc-backend
FATA[0043] Error: image openecomp/sdc-backend:1.0-STAGING-latest not found

Is there anything else missing? 
Thanks in advance.

Best Regards,

Xiaojun Xie

From: Kanagaraj Manickam
Date: 2017-05-03 02:31
To: PLATANIA, MARCO (MARCO)
CC: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] is docker pull breaking
Hello Marco,

Awesome !. It works now.

Thank you
Kanagaraj M

On Tue, May 2, 2017 at 9:59 AM, PLATANIA, MARCO (MARCO) 
 wrote:
Hello Kanagaraj,
 
The reason why is failing is that there’s something missing in your docker pull 
instruction. The repository is missing, so it can’t find any container. These 
are the correct operations:
 
docker login –u docker –p docker nexus3.onap.org:10001
docker pull 
nexus3.onap.org:10001/openecomp/dgbuilder-sdnc-image:1.0-STAGING-latest
 
Note the repo name, nexus3.onap.org:10001, which is missing in your case. Try 
the instruction above, it will work.
 
Thanks,
Marco
 
From: Kanagaraj Manickam 
Date: Tuesday, May 2, 2017 at 9:12 AM
To: "PLATANIA, MARCO (MARCO)" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] is docker pull breaking
 
Hello Marco, 
 
Thank you.
 
It is failing with docker version 1.0-STAGING-latest and error is listed below:
 
root@mrkanag-os:~# docker pull openecomp/dgbuilder-sdnc-image:1.0-STAGING-latest
Pulling repository openecomp/dgbuilder-sdnc-image
FATA[0001] Error: image openecomp/dgbuilder-sdnc-image:1.0-STAGING-latest not 
found
 
Not sure if there are some issue with my docker environment though i could pull 
images from other docker repo for example open docker r

[onap-discuss] [onap-tsc] Modelling discussion on Friday May 5th

[xiexj...@chinatelecom.cn]

I agree with this.

Maybe we could consider the modeling from the perspective of the micro-service 
principle. The orchestrator is responsible for the execution of the workflow 
model(such as BPMN), and the controllers are charge of the execution of the 
configuration model(such as YANG). So in my opinion the modeling languages, 
which are suitable for the implementation of the orchestrator or the 
controllers respectively, are the best for ONAP now. In the future, if there is 
another better modeling language, the orchestrator or the controllers will 
autonomously evolve to a new version which adopt the new workflow or 
configuration modeling languages. The influence of the evolvement will be 
controllable.

Best Regards,

Xiaojun


 Ed Warnicke
? 2017-04-25 07:47
 Michael Brenner
??? onap-discuss
??? Re: [onap-discuss][onap-tsc] ???Re: Modelling discussion on Friday May 5th
I strongly second this.

My experience is that there is a huge service for the good modelers who engage 
with the community to do incredible good... but modeling in a vacuum, away from 
the implementation, and then just expecting the implementers to follow 
directions works poorly.

I'd say that a far better activity for the long term health would be to plug 
good model people into the places in the community where models are in 
progress.  Their wisdom as participants can be huge, but they need to 
*participate*, not work off in a tower of UML.

Ed

On Mon, Apr 24, 2017 at 4:25 PM, Michael Brenner  
wrote:
... on the other hand, what does one do with a smooth cohesive model, if you 
can't easily translate it to a data model? Without any intent to dive into a 
debate about whether the example is right or not ... we have an ETSI NFV VNF 
UML model ... and we cannot translate it into any data model - it takes manual 
work. The other issue is sort of the reverse - i.e. you don't actually KNOW 
that the UML model is right, until you implement it. And it is difficult to 
implement it, when you don't have the automatic translation tools. So you end 
up building an ideal model, but you don't know if it works ... until you have 
the right translation tools. How long is one to wait ... instead of 
implementing and iterating?
Like with any other project, it really comes down to a schedule, and knowing 
what you want to achieve within that schedule.

Best,
Michael

On Mon, Apr 24, 2017 at 6:23 PM, Brian Hedstrom  wrote:
While the tools are maturing and advancing, if we choose to close that door 
now, there's no cohesive UML Common Information Model for ONAP.  Consequently, 
we would lack a protocol agnostic information model and when the next cool data 
modeling language or encoding scheme comes out, we have to start again with 
working backward. Another key benefit is that UML is much easier to comprehend 
due to it's graphical diagram nature, versus needing to understand a data 
modeling language and/or data encoding mechanism. 
Consensus can be made on class diagrams for example, then translation to a data 
modeling language can be easily done by hand or by the emerging tools (see my 
previous email with the links).

On Mon, Apr 24, 2017 at 12:29 PM, Michael Brenner  
wrote:
Hi all,

I actually tend to agree with Ed. While it may be an ideal approach in theory, 
tools for automatic generation from UML to Yang, or other modeling languages 
for that matter are improving, they are still too far from perfect, and require 
a lot of hand-holding so-to-speak, and as a result - too many headaches. We may 
be mired in tool debugging, instead on progressing on ONAP.

Michael

From: Ash Young 
Subject: Re: [onap-discuss] [onap-tsc] ???Re: Modelling discussion on Friday 
May 5th
Date: April 24, 2017 at 10:09:22 AM PDT
To: Ed Warnicke , Brian Hedstrom 
Cc: "JANA, RITTWIK \(RITTWIK\)" , onap-discuss 
, onap-tsc 

I'm actually in agreement with Brian on approach and tool. So much work has 
been going on here that I really don't want to see us go backwards by thinking 
Yang solves everything.

Ash

Sent from my iPhone

On Apr 24, 2017, at 12:01, Ed Warnicke  wrote:

I love UML in a variety of contexts, but for expressing things that are 
destined to be expressed in yang, or for creating things to be rendered to 
yang, in my experience its been a very poor fit.

Ed

On Mon, Apr 24, 2017 at 9:41 AM, Brian Hedstrom  wrote:
The way to put all these different data models under a single umbrella is to 
create a UML Information Model using Eclipse/Papyrus (as an open source tool).  
Unified Modeling Language (UML) is a standard syntax for describing the 
architectural design of a system
Object Management Group (OMG) & ISO standard
Originated from object-oriented software development methods
UML includes many diagrams types to graphically represent parts of a system?s 
model, including
Structural Views: The static nature of the system using objects, attributes and 
relationships (e.g., information or components that must be present in the 
system). This 

[onap-discuss] ONAP: May F2F Visa Letter Procees

[xiexj...@chinatelecom.cn]

Hi, Annie,

Chen Yan will be our point person for the process from China Telecom.
His email is . Thanks.

Regards,



Xiaojun XIE
Technical Director of IT R&D Center,
Guangzhou Research Institute of China Telecom.
(O) 86-20-38639130
(M) 86-13316090153
xiexj.gd at chinatelecom.cn

From: Annie Fisher
Date: 2017-04-04 04:23
To: onap-tsc; onap-discuss
Subject: [onap-discuss] ONAP: May F2F Visa Letter Procees
Greetings all,

I hope this email finds you all well.  As Phil mentioned in his message on 
Friday, we are working on the final logistics and registration now for the ONAP 
TSC F2F in May, but we can begin the processing of the Visa Letters now.

Here is the process:
1.  For each member company, please assign 1 (one) person to be the point 
person for this process.  This will be the person our LF staff will work with 
on the processing of these letters.  
ACTION:  Designate one point person per member company

2.  The point person at each member company should fill out the data needed for 
each person they are requesting a visa letter for, in its entirety on the 
attached spreadsheet.This spreadsheet takes the place of needing the 
on-site registration, so it is imperative all fields are completed.
ACTION: Complete attached spreadsheet for each person you are requesting a visa 
letter.

3. After you've completed the data entry, please return this spreadsheet via 
email to me (Annie Fisher, afisher at linuxfoundation.org) and we will get the 
letter(s) processed as quickly as possible.  NOTE:  Hard copies will be sent to 
the Point Person only.
ACTION: Return the spreadsheet to Annie and processing will start immediately.

Thank you all - and please contact me with any questions about the process.  
Further information regarding these event will be out shortly.

Cheers,
Annie

Annie Fisher, MPA CSM
Program Manager, The Linux Foundation
Location & Time-zone: San Francisco, CA, PST
web: https://www.linuxfoundation.org/
email: afisher at linuxfoundation.org

-- next part --
An HTML attachment was scrubbed...
URL: