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

2018-06-14 Thread HU, BIN
While it might be the overall concern on ONAP, we are discussing implementation 
of K8S Plugin ☺.

So if we can address the concern here, it will certainly contribute to the 
future discussion of overall concern ☺

Bin
From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Thursday, June 14, 2018 8:38 AM
To: HU, BIN ; HEKMAT, ARASH ; Yang, 
Bin (Wind River) ; Morales, Victor 
; onap-discuss@lists.onap.org
Cc: Zhang, Xiaohua (Wind River) ; Huang, Yun (Wind 
River) 
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

Hi Bin,

I think you are raising a concern across ONAP.

Today, following languages are used in ONAP (Even not considering K8S plugin) – 
From dec 17th presentation by Jason (Software Architecture 11 December)


-  Java

-  Python

-  Java script

-  C

-  Go

-  Perl

-  Erlang

-  NodeJS

-  Clojure

-  Shell

-  Lua

You are suggesting that ONAP should recommend few languages so that we have 
skillset that can support ONAP in future.
So far, this discussion did not come up except in this list ☺

It would be good to raise at ONAP TSC/Architecture level?

Thanks
Srini


From: HU, BIN [mailto:bh5...@att.com]
Sent: Thursday, June 14, 2018 7:39 AM
To: HEKMAT, ARASH mailto:arash.hek...@amdocs.com>>; 
Addepalli, Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
Yang, Bin (Wind River) mailto:bin.y...@windriver.com>>; 
Morales, Victor mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Zhang, Xiaohua (Wind River) 
mailto:xiaohua.zh...@windriver.com>>; Huang, Yun 
(Wind River) mailto:yun.hu...@windriver.com>>
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

I think all of the arguments now focus on the technology side, its merit and 
how to implement it.

From user experience perspective, my interest is more related to how I can get 
continuous community support to maintain and evolve it in the future. When I 
invest in using something, current technology and implementation is certainly 
important (i.e. CapEx). But more importantly, after using it in operation, 
getting the continuous support from community is vital to the success of 
operation (i.e. OpEx).

Of course, we can expect people to learn, but that is the best wish. Currently, 
I don’t see a convincing plan of growing the support of a particular language 
(Go) except the best wish. Thus I have the concern of sustainable support (e.g. 
OpEx) from user perspective.

Hope my point can be really understood, which has nothing to do technology 
itself (e.g. micro-service, performance etc.)

Thanks
Bin

From: HEKMAT, ARASH
Sent: Thursday, June 14, 2018 6:57 AM
To: Addepalli, Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; HU, 
BIN mailto:bh5...@att.com>>; Yang, Bin (Wind River) 
mailto:bin.y...@windriver.com>>; Morales, Victor 
mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Zhang, Xiaohua (Wind River) 
mailto:xiaohua.zh...@windriver.com>>; Huang, Yun 
(Wind River) mailto:yun.hu...@windriver.com>>
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

In my view, the whole idea of micro-services is isolation of technologies and 
communications only through well-defined APIs.

So the arguments both for and against a specific language for a micro-service 
based on the language having been used or not used in other micro-services are 
contrary to the idea of micro-services design.

So I believe:

  1.  As long as a micro-service is self-contained, both in code and at run 
time, and has well-defined APIs for all communications with other parts of the 
system then the choice of technology for the micro-service should only be based 
on what best suits the requirements of the micro-service.
  2.  To me ultimately the decision on what technology to use for a 
micro-service should be with the PTL and the team that commits to implementing 
the micro-service (committed implementers can vote).

Regards,
Arash

From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Wednesday, June 13, 2018 6:07 PM
To: HU, BIN mailto:bh5...@att.com>>; Arash Hekmat 
mailto:arash.hek...@amdocs.com>>; Yang, Bin (Wind 
River) mailto:bin.y...@windriver.com>>; Morales, Victor 
mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Zhang, Xiaohua (Wind River) 
mailto:xiaohua.zh...@windriver.com>>; Huang, Yun 
(Wind River) mailto:yun.hu...@windriver.com>>
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

Hi Bin,

I think you answered questions  yourself ☺. It 

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

2018-06-14 Thread HU, BIN
I think all of the arguments now focus on the technology side, its merit and 
how to implement it.

From user experience perspective, my interest is more related to how I can get 
continuous community support to maintain and evolve it in the future. When I 
invest in using something, current technology and implementation is certainly 
important (i.e. CapEx). But more importantly, after using it in operation, 
getting the continuous support from community is vital to the success of 
operation (i.e. OpEx).

Of course, we can expect people to learn, but that is the best wish. Currently, 
I don’t see a convincing plan of growing the support of a particular language 
(Go) except the best wish. Thus I have the concern of sustainable support (e.g. 
OpEx) from user perspective.

Hope my point can be really understood, which has nothing to do technology 
itself (e.g. micro-service, performance etc.)

Thanks
Bin

From: HEKMAT, ARASH
Sent: Thursday, June 14, 2018 6:57 AM
To: Addepalli, Srinivasa R ; HU, BIN 
; Yang, Bin (Wind River) ; Morales, 
Victor ; onap-discuss@lists.onap.org
Cc: Zhang, Xiaohua (Wind River) ; Huang, Yun (Wind 
River) 
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

In my view, the whole idea of micro-services is isolation of technologies and 
communications only through well-defined APIs.

So the arguments both for and against a specific language for a micro-service 
based on the language having been used or not used in other micro-services are 
contrary to the idea of micro-services design.

So I believe:

  1.  As long as a micro-service is self-contained, both in code and at run 
time, and has well-defined APIs for all communications with other parts of the 
system then the choice of technology for the micro-service should only be based 
on what best suits the requirements of the micro-service.
  2.  To me ultimately the decision on what technology to use for a 
micro-service should be with the PTL and the team that commits to implementing 
the micro-service (committed implementers can vote).

Regards,
Arash

From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Wednesday, June 13, 2018 6:07 PM
To: HU, BIN mailto:bh5...@att.com>>; Arash Hekmat 
mailto:arash.hek...@amdocs.com>>; Yang, Bin (Wind 
River) mailto:bin.y...@windriver.com>>; Morales, Victor 
mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Zhang, Xiaohua (Wind River) 
mailto:xiaohua.zh...@windriver.com>>; Huang, Yun 
(Wind River) mailto:yun.hu...@windriver.com>>
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

Hi Bin,

I think you answered questions  yourself ☺. It is easy to learn, secure 
language, performant and many are eager to learn.  There are some good number 
of people with Golang experience (thanks to some of the work that was done in 
Beijing) already in ONAP community.  Also,

-  we see the need for using Prometheus (or similar) for 
event/statistics aggregation micro service to satisfy the MVP of 
Edge-automation use case. Since Prometheus is developed in golang, any 
ancillary packages/glues are also expected to be developed in golang.
-  ISTIO service mesh technology is being seriously looked at to 
replace existing MSB and simplify security.  If this is adopted, any 
enhancements related to service mesh would normally happen in golang as ISTIO 
is developed in golang.

With above two, I have a confidence that we will have more developers in golang.

Thanks
Srini


From: HU, BIN [mailto:bh5...@att.com]
Sent: Wednesday, June 13, 2018 12:26 PM
To: Addepalli, Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
HEKMAT, ARASH mailto:arash.hek...@amdocs.com>>; Yang, 
Bin (Wind River) mailto:bin.y...@windriver.com>>; 
Morales, Victor mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Zhang, Xiaohua (Wind River) 
mailto:xiaohua.zh...@windriver.com>>; Huang, Yun 
(Wind River) mailto:yun.hu...@windriver.com>>
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

Hi Srini and Arash,

Thank you for the great information. I am truly with you, and there is no doubt 
that K8S can be implemented with Go language, and I do see the merit of Go 
language that will provide great value in implementation.

The concern here is not related to technology of Go language, as I mentioned 
earlier. Please understand that I do believe that Go language is easy to learn, 
and savvy developers all eager to learn new technologies. GoLang client is also 
well maintained by Kubernetes community as Victor mentioned in a different 
email.

The situation is that K8S Plugin will be implemented and maintained in ONAP 
community. So for the long-term sustainability, a rea

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

2018-06-13 Thread HU, BIN
Hi Srini and Arash,

Thank you for the great information. I am truly with you, and there is no doubt 
that K8S can be implemented with Go language, and I do see the merit of Go 
language that will provide great value in implementation.

The concern here is not related to technology of Go language, as I mentioned 
earlier. Please understand that I do believe that Go language is easy to learn, 
and savvy developers all eager to learn new technologies. GoLang client is also 
well maintained by Kubernetes community as Victor mentioned in a different 
email.

The situation is that K8S Plugin will be implemented and maintained in ONAP 
community. So for the long-term sustainability, a reasonable size of developer 
pool in ONAP community is needed to continuously maintain our own K8S Plugin 
code base in ONAP.

I just want to know: do you have a plan to grow a reasonable size of developer 
pool in ONAP community so that K8S Plugin implementation with Go can be 
continuously maintained and evolved in ONAP?

Thanks
Bin

From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Wednesday, June 13, 2018 7:36 AM
To: HEKMAT, ARASH ; HU, BIN ; Yang, 
Bin (Wind River) ; Morales, Victor 
; onap-discuss@lists.onap.org
Cc: Zhang, Xiaohua (Wind River) ; Huang, Yun (Wind 
River) 
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

Yes Arash.  K8S plugin has its own repo and will be set (currently one) micro 
service run as container.  We don’t intend to call Python calls from Go 
programs.  So, answer is Yes for all three points you have mentioned in your 
email.

Hi Bin,

I don’t mean to be pedantic here.  Sorry if it appears so.


1.   (Can be argumentative and may become philosophical discussion)It is 
very easy to learn go-lang.  I don’t see it as big issue either maintaining it 
or even developing.  Engineers who contributed to SMS, Distributed KV Store 
(done as part of R2) were new to go and could learn in matter of days/weeks.

2.   Code size is very small – Hence easy to adopt in Edge locations (if 
there is a need in future).

3.   Static type checking – Less error prone.

4.   Performance of golang based system is higher. (Bring up is very fast 
and it is just 10-20% lower performance than C/C++)

5.   K8S Client in go-lang always little bit ahead of other language 
bindings.  Go-client is maintained as part of Kubernetes project.

6.   GoCrypto has a way to talk to HSMs. If there is a need to secure keys, 
password, secrets,  then the support is already available. Java Crypto has 
similar support, but python does not have it (yet).

7.   Many micro service projects are developed in golang. It is quite 
mature. Many CNCF projects are developed in golang.

https://hackernoon.com/5-reasons-why-we-switched-from-python-to-go-4414d5f42690<https://urldefense.proofpoint.com/v2/url?u=https-3A__hackernoon.com_5-2Dreasons-2Dwhy-2Dwe-2Dswitched-2Dfrom-2Dpython-2Dto-2Dgo-2D4414d5f42690=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=kKJpI7d4BvGzsfgElthwPCjo7-CR9Z7D0x-r3mXt0KE=TJX91uvzwLwPtQBNruqU6B98r2WHw7rjpEjc9diS2OU=>

Since ONAP is micro-service based, language choice for a given micro-service 
should not matter.  And you will find more and more Engineers with go skillset 
with increasing popularity Kubernetes and micro-service architecture

Thanks
Srini


From: Arash Hekmat [mailto:arash.hek...@amdocs.com]
Sent: Wednesday, June 13, 2018 7:04 AM
To: HU, BIN mailto:bh5...@att.com>>; Yang, Bin (Wind River) 
mailto:bin.y...@windriver.com>>; Addepalli, Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
Morales, Victor mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Zhang, Xiaohua (Wind River) 
mailto:xiaohua.zh...@windriver.com>>; Huang, Yun 
(Wind River) mailto:yun.hu...@windriver.com>>
Subject: RE: [onap-discuss] Building blocks for multicloud k8s plugin, RE: 
[coe] Team meeting Agenda

Hi MultiCloud Team,

My 2 cents here.

I believe if below conditions are true, the K8S plugin can be implemented in Go 
or any other language. But if they are not true, it should probably match 
MultiCould’s core and use Python, for all the maintainability and integration 
concerns already raised.

The K8S plugin can use Go or any other language if:

(1)   It has its own separate git repo
(2)   It runs in its own separate docker container
(3)   It does not directly call or share MultiCould’s Python framework

Arash

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HU, BIN
Sent: Wednesday, June 13, 2018 2:02 AM
To: Yang, Bin mailto:bin.y...@windriver.com>>; 
ADDEPALLI, SRINIVASA 
mailto:srinivasa.r.addepa...@intel.com>>; 
MORALES RUVALCABA, VICTOR 
mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org&l

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

2018-06-13 Thread HU, BIN
If I understand correctly, there are 2 types of concerns regarding Go language 
(v.s. Python) here:

-  Implementation, integration and testing: e.g. CI/CD integration, 
reuse of shared services etc.

-  Long-term community support with the appropriate expertise in Go 
language.

The 2nd one, i.e long-term community support is actually the biggest concern. 
For example, after K8S plugin is developed with Go language, but the original 
Go developer no longer works in ONAP, do we have a pool of Go developers in 
ONAP community that can comfortably take over the work of maintenance and 
further evolving K8S Plugin? Or will then-current developers have to re-develop 
K8S Plugin with Python or Java because most of ONAP developers are Python or 
Java developers?

If there are very few Go developers in ONAP community, using Go language 
certainly brings huge risk of continuous support, maintenance and evolution in 
the future.

My 2 cents
Thanks
Bin

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Tuesday, June 12, 2018 8:27 PM
To: ADDEPALLI, SRINIVASA ; MORALES RUVALCABA, 
VICTOR ; onap-discuss@lists.onap.org; HU, BIN 

Cc: Huang, Yun ; HUANG, HAIBIN 
; Zhang, Xiaohua 
Subject: Building blocks for multicloud k8s plugin, RE: [coe] Team meeting 
Agenda

Hi Victor, Srini and all,

In addition to the agenda you listed, could you also add one more to touch the 
topic of building blocks (e.g. “language binding” with golang instead of 
python) for multicloud k8s plugin?

I do understand that from the architecture perspective it is irrelevant w.r.t. 
how to implement the plugin service, hence up to developers/contributors’ 
choice. However, it is worth to think again for following reasons:

1, Leverage and Scale
   Aligning to existing practice of multicloud plugin 
implementation enables developers focus on the core value of the plugin, e.g. 
mediate ONAP orchestration to k8s cluster in case of multicloud k8s plugin. As 
part of ONAP projects it is required that the multicloud k8s plugin be 
integrated with CI/CD process and other shared services (e.g. AAF, centralized 
logging, etc.)  Right now CI/CD support projects with python binding very well, 
and the logging AOP facility for Python is well supported, I don’t know if 
there is off-the-shelf utility for golang available yet. If multicloud k8s 
plugin align to the existing practice of openstack plugin and vio plugin, then 
you don’t have to invest further time/cost on those effort.


2, Facilitate more participation from current multicloud committers/contributors
   multicloud committers/contributors has been working on python 
already for a long time , and it is not surprising that many of them are 
willing to participate/contribute to this multicloud k8s plugin development. 
Assuming that Golang is not as widely adopted as Python so most of them is not 
that familiar with Golang compared to Python, it would lower the barrier for 
them to contribute if multicloud k8s plugin could adopt the same language and 
framework.

3, Decrease the maintenance cost from either community and the Service 
Providers who will productize ONAP
   By align to the same practice and share the same building blocks 
across multicloud plugins, one committer/contributor support/maintain one 
plugin could also be possible to support another one with low cost to 
learn/understand it. This will decrease the TCO which is always a pain of open 
source product compared to those commercialized close source product.

4, facilitate pairwise/integration testing for fast release cadence
   It might not concern those architect, but it is really a pain 
for developers who support the pairwise/integration testing. Fortunately, 
python make our life better since it is possible to fix the bug on runtime and 
test it immediately, which reduce the cycle of debugging. I can share you some 
feedback from several PTLs whom I had supported during Pairwise/integration 
test if you are interested to know.

So it is my 2 cents, please let me know if you have other concerns/opinions and 
I am willing to learn them, thanks.


Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yang, Bin
Sent: Wednesday, June 13, 2018 9:21 AM
To: ADDEPALLI, SRINIVASA; MORALES RUVALCABA, VICTOR; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [coe] Team meeting Agenda

Hi Srini, and all,

   With regarding to the “each deployment instance needs to be 
uniquely identified”,  what is the intention for this “uniquely identified”? I 
mean, who will care about/consume this unique ID?

IMHO, from multicloud NBI consumers’ perspective, I don’t g

Re: [onap-discuss] [coe] Team meeting Agenda

2018-06-12 Thread HU, BIN
Victor,

The endpoint is the one (URL) in “Auth Url” when using ESR portal, or the 
“service-url” property in “esr-system-info” when using curl.

The endpoint is the base URL of K8S API (as a microservice), which we should 
define.

Thanks
Bin

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Tuesday, June 12, 2018 4:02 PM
To: HU, BIN ; Addepalli, Srinivasa R 
; onap-discuss@lists.onap.org
Subject: Re: [coe] Team meeting Agenda

Hey there,

@Bin, I have a question about using the ESR VIM registration portal. According 
to the wiki using this method will trigger a discovery process. I’m wondering 
if we have to create an endpoint for this, maybe it’s something that we can 
include into the API definition and implement it later.

@Srini regarding your questions, for this PoC we have only considered the 
scenario for consuming the ./kube/config[1] file. In the other hand, I noticed 
that’s possible to configure Kubernetes to use Basic Authentication method [2] 
which can do something similar than OpenStack.  Lastly, regarding the 
concatenation I have the impression that what Kubernetes is doing internally is 
quite enough to guarantee its uniqueness, but we can include it as a functional 
test to cover that scenario.

Regards,
Victor Morales

[1] 
https://github.com/electrocucaracha/krd/blob/master/installer#L97<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_electrocucaracha_krd_blob_master_installer-23L97=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=mUqO87YaHbvd2KhWUk8wU9exCXbw55_C51kOXstd5v0=KbTxB3n67E9D_DFXlvyRMqxyFkbPOryzjzK4OQKtgas=>
[2] 
https://github.com/electrocucaracha/krd/blob/master/inventory/group_vars/k8s-cluster.yml#L69<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_electrocucaracha_krd_blob_master_inventory_group-5Fvars_k8s-2Dcluster.yml-23L69=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=mUqO87YaHbvd2KhWUk8wU9exCXbw55_C51kOXstd5v0=WcizN3AiygURz2qLat-04JuC4xoNfammUq6gthb7_t8=>


From: "HU, BIN" mailto:bh5...@att.com>>
Date: Tuesday, June 12, 2018 at 1:04 PM
To: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>, 
Victor Morales mailto:victor.mora...@intel.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Subject: RE: [coe] Team meeting Agenda

Refer to the wiki page: 
https://wiki.onap.org/pages/viewpage.action?pageId=25431491<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D25431491=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=mUqO87YaHbvd2KhWUk8wU9exCXbw55_C51kOXstd5v0=XFW3LbHznpsmGs_ePqATpmv__DS1Uj8sSkfb9nJcmG8=>
 (How-To: Register a VIM/Cloud Instance to 
ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D25431491=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=mUqO87YaHbvd2KhWUk8wU9exCXbw55_C51kOXstd5v0=XFW3LbHznpsmGs_ePqATpmv__DS1Uj8sSkfb9nJcmG8=>).

In this guide, when registering a new VIM, we need to:

-  Create Complex object in A

-  Register VIM/Cloud instance in A

-  And some other steps

When registering VIM/Cloud instance in A, one can use curl command to create 
a cloud region object in A This Cloud Region Object contains a 
“esr-system-info-list” which includes “username” and “password” for keystone 
authentication.

Because this schema is OpenStack-centric, we may have 2 options:

-  Reuse “password” property, and store kubeconfig information within 
this “password” property

-  Or expand the “esr-system-info-list” with a new property for 
kubeconfig information.

Hope it helps
Thanks
Bin

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Addepalli, Srinivasa R
Sent: Tuesday, June 12, 2018 12:29 PM
To: Morales, Victor 
mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [coe] Team meeting Agenda

Hi Victor and Shashank,

There were few questions from Multi-Cloud meeting yesterday (Shankar and 
others).  It would be good if we could cover following also today


-  K8S plugin needs to have access to information that connect to K8S 
masters in the remote edge-clouds/sites.  Normal practice for K8S client is to 
read kubeconfig file  that has connectivity information for each cluster and 
certificate/private key to be used to communicate with remote site K8S master.  
In ONAP, we have ESR. Are we going to use ESR or K8S plugin provides its own 
way to upload kubeconfig information.  If so, how does get stored in A Is 
there any schema change required?

-  K8S plugin at the run time will use same deployment template files 
multiple times.  But, each deployment instance needs to be uniquely identified

Re: [onap-discuss] [modeling][cloud infrastructure]

2018-06-04 Thread HU, BIN
Howard,

Thank you for your questions and concerns.

Would you mind proposing an improvement proposal to address your concerns? For 
example,

-  A model representing a relationship of abstraction rather than 
aggregation (to address your first concern)?

-  More specifically, a model to improve RCGC (or alternative of RCGC) 
to address your exemplary concern?

-  An improvement model (or an alternative model) of resource slices to 
address your second concern?

Look forward to your proposal of improvement.
Thanks

Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Zhipeng Huang
Sent: Monday, June 04, 2018 1:10 AM
To: denghui (L) 
Cc: onap-discuss@lists.onap.org; onap-tsc ; GUPTA, 
ARUN 
Subject: Re: [onap-discuss] [modeling][cloud infrastructure]

Hi Arun and all,

Sorry for the late response, I just want to re-state my concern during the conf 
call earlier on the mailing-list.

My first concern is that for the data modeling, we should adopt a common 
denominator of different VIM implementations. This means each concept defined 
in the data model here should be able to correctly mapped to various VIM 
implementations within scope. Moreover, a good data model should represent a 
relationship of abstraction rather than aggregation.

Take Resource Cluster Group Class for example, it merely represents an 
arbitrary aggregation of the Resource Cluster Group which means this concept 
does not provide any abstraction over underlying resource concept. Another 
problem is that only VMware implementation has a nicely mapped corresponding 
concept to RCGC, whereas in OpenStack it is just obscurely mapped to "a set of 
host-aggregates".

And if you remove the RCG point in the diagram provided in [0], you can see 
that no major connection will be disrupted, which also proves as a leaf node it 
is not a necessary one.

RCGC is something I would recommend we avoid for the data modeling of 
multicloud.

Secondly, I'm concerned with the concept of resource slice. Again it seems very 
arbitrarily crafted as a subset of resource (which again I fail to see an 
abstraction relationship but an aggregation one). It would be great if this 
concept is necessary then we have a very good detailed explanation of why we 
need it.

[0]https://wiki.onap.org/display/DW/Cloud+Infrastructure+Aggregate+Representation+Classes



On Wed, May 23, 2018 at 10:26 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hello modelers,

We are hoping that  people could raise the discussion point before next Tuesday 
modeling call in this list or wiki page, we will limit one point discussion 
time during our next call.

Thanks a lot

DENG Hui

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org]
 On Behalf Of GUPTA, ARUN
Sent: Tuesday, May 22, 2018 11:20 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [modeling][cloud infrastructure]



The Wiki pages for Cloud Infrastructure Modeling in general:
https://wiki.onap.org/pages/viewpage.action?pageId=33065694
and for Cloud Aggregation Classes:
https://wiki.onap.org/display/DW/Cloud+Infrastructure+Aggregate+Representation+Classes

The presentation used in today’s (Tuesday May 22) Modeling Committee call is on 
the second page.


-Arun


Arun Gupta
Lead Member of Technical Staff
Domain 2 Architecture and Planning
200 S Laurel Ave – Bldg B, B5-3Z09
Middletown, NJ 07748
P: 732 420 6597
arungu...@att.com





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



--
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei 

Re: [onap-discuss] [coe] Today's meeting

2018-05-22 Thread HU, BIN
Isaku used to be the organizer. I am glad to see that Victor is going to 
organize it down the road.

Either 10am or 1pm Pacific Time works for me in general.

Can Srini or Victor formally announce it and make the update of the calendar 
invite if needed? Current calendar invite is 10am Pacific Time.

Thank you
Bin

From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Tuesday, May 22, 2018 10:31 AM
To: Munish Agarwal <munish.agar...@ericsson.com>; Morales, Victor 
<victor.mora...@intel.com>; onap-discuss@lists.onap.org; Shankar, Shashank 
Kumar <shashank.kumar.shan...@intel.com>
Cc: HU, BIN <bh5...@att.com>; Ramki Krishnan <ram...@vmware.com>; Seshu m 
<seshu.kuma...@huawei.com>
Subject: RE: [coe] Today's meeting

If it is 10:00AM PST, Can we make it at 1:00PM PST?

I have a conflict at 10:00AM on regular basis.

Thanks
Srini


From: Munish Agarwal [mailto:munish.agar...@ericsson.com]
Sent: Tuesday, May 22, 2018 10:24 AM
To: Morales, Victor 
<victor.mora...@intel.com<mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: HU, BIN <bh5...@att.com<mailto:bh5...@att.com>>; Addepalli, Srinivasa R 
<srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>>; 
Ramki Krishnan <ram...@vmware.com<mailto:ram...@vmware.com>>; Seshu m 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>
Subject: RE: [coe] Today's meeting

Hi,

The wiki says 10:00 AM PST which is 1:00 AM EST.  Which is the correct one?

Regards,
Munish

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Tuesday, May 22, 2018 12:09 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: HU, BIN <bh5...@att.com<mailto:bh5...@att.com>>; Addepalli, Srinivasa R 
<srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>>; 
Munish Agarwal 
<munish.agar...@ericsson.com<mailto:munish.agar...@ericsson.com>>; Ramki 
Krishnan <ram...@vmware.com<mailto:ram...@vmware.com>>; Seshu m 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>
Subject: [coe] Today's meeting

Hey there,

According to the wiki [1], it’s scheduled the Container Orchestration Engine 
Weekly Meeting today at 1:00pm PST.  I’d be glad to hear and discuss ideas 
about this project.

Regards,
Victor Morales

[1] 
https://wiki.onap.org/pages/viewpage.action?pageId=16009184<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D16009184=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=VUZkX6wyj-FurrT5YrUc_jGjui-oTJS3gZnL4vxxzxQ=hTDlb0Pv0CWuUv6GWPwHqmnSKgPu0tgSyx5Rp5gtOds=>

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


Re: [onap-discuss] [multicloud] cancel the meeting on May.21 5:00 PST and update of project status

2018-05-21 Thread HU, BIN
Dear Xinhui,

On Friday, May 11th, 2018, VES team (Alok Gupta) has sent VES 6.0 draft with 
recommended changes for comments from ONAP teams. If possible, would you please 
put it on the agenda of the next available MultiVIM team meeting to discuss the 
changes in VES 6.0 draft?

Please let us know the date/time of the meeting so that we can make sure Alok 
Gupta will join.

Thanks
Bin

From: Xinhui Li [mailto:lxin...@vmware.com]
Sent: Sunday, May 20, 2018 10:50 PM
To: Addepalli, Srinivasa R <srinivasa.r.addepa...@intel.com>; Yang, Bin (Wind 
River) <bin.y...@windriver.com>; Hellmann, Gil (Wind River) 
<gil.hellm...@windriver.com>; HU, BIN <bh5...@att.com>; Ramki Krishnan 
<ram...@vmware.com>; Sumit Verdi <sve...@vmware.com>; Ethan Lynn 
<ethanly...@vmware.com>; Hong Hui Xiao <hongh...@vmware.com>; Ke Liang 
<lia...@vmware.com>; Bin Sun <b...@vmware.com>; Ramesh Tammana 
<rame...@vmware.com>; Morales, Victor <victor.mora...@intel.com>; Yang Xu 
(Yang, Fixed Network) <yang@huawei.com>; Anil Vishnoi 
<vishnoia...@gmail.com>; TOFIGH, TOM <mt3...@att.com>; 
isaku.yamah...@gmail.com; Huang, Haibin <haibin.hu...@intel.com>; Kanagaraj 
Manickam <kanagaraj.manic...@huawei.com>; Kenny Paul 
<kp...@linuxfoundation.org>; Vul, Alex <alex@intel.com>; 
zhang.maope...@zte.com.cn; fu.jin...@zte.com.cn; Ramu n <ram...@huawei.com>; 
huang.zhuo...@zte.com.cn; OBRIEN, FRANK MICHAEL <frank.obr...@amdocs.com>; 
HEKMAT, ARASH <arash.hek...@amdocs.com>; BLANDFORD, SCOTT <cb1...@att.com>; 
LEWIS, LAUREN A <ll7...@att.com>; HALLAHAN, RYAN <rh1...@att.com>; Harwani, 
Robin <harwa...@amazon.com>; Parviz Yegani <parviz.yeg...@huawei.com>; Mohamed 
El-Serngawy <mohamed.elserng...@kontron.com>; Potter, Nathaniel 
<nathaniel.pot...@intel.com>; Ran Pollak <ran.pol...@amdocs.com>; Liyan Li 
<liy...@vmware.com>; Sachin Thakkar <sthak...@vmware.com>; Brian Hedstrom 
<brian.hedst...@oamtechnologies.com>; Adolfo Perez-Duran 
<adolfo.perez-du...@oamtechnologies.com>; Tina Tsou <tina.t...@arm.com>; 
SULLIVAN, BRYAN L <bryan.sulli...@research.att.com>; GUPTA, ARUN 
<ag7...@att.com>; NELSON, CAROL A <cn1...@att.com>; Avdhut Kholkar 
<avdhut.khol...@amdocs.com>; Beejal Shah <beejal.s...@amdocs.com>; Alka 
Choudhary <al...@amdocs.com>; Robin George <robi...@amdocs.com>; SINASAC, 
DANIEL <craig.sina...@amdocs.com>; Manoj Kapre <mano...@amdocs.com>; Casem Majd 
(Cas Majd) <cas.m...@huawei.com>; TABEDZKI, RICHARD <rt0...@att.com>; Bou 
Hanana Mohamed <mohamed.bouhan...@aalto.fi>; Karin Arnold 
<karin.arn...@de.ibm.com>; pierre.ly...@keysight.com; Ramkumar Venketaramani 
<rvenketar...@vmware.com>; thomas.ku...@telekom.de; Jason Hunt 
<djh...@us.ibm.com>; Huang, Yun (Wind River) <yun.hu...@windriver.com>; 
NOSHPITZ, CLAUDE <cn5...@att.com>; GUPTA, ALOK <ag1...@att.com>; CHEN, CHI-MING 
<cc5...@att.com>; Avula, Niranjan B <niranjan.av...@verizonwireless.com>; 
fernando.olive...@verizon.com; Draznin, Sagiv 
<sagiv.draz...@verizonwireless.com>; Margaret Chiosi (A) 
<margaret.chio...@huawei.com>; Gaoweitao (Victor, MANO) 
<victor@huawei.com>; zhanganb...@chinamobile.com; Lingli Deng 
<denglin...@chinamobile.com>; Gadiyar, Rajesh <rajesh.gadi...@intel.com>; HAY, 
AARON <ah4...@att.com>; simer.si...@us.fujitsu.com; 
david.perezcapar...@swisscom.com; meng.zhaoxi...@zte.com.cn; 
denghu...@huawei.com; shang.xiaod...@zte.com.cn; CHAPNICK, AVI 
<avi.chap...@amdocs.com>; FREEMAN, BRIAN D <bf1...@att.com>; HILTUNEN, MATTI 
<hiltu...@research.att.com>; Beaudet, Eric <eric.beaud...@bell.ca>; Iurcovich, 
Hector (Nokia - US/Naperville) <hector.iurcov...@nokia.com>; Alex Daltrini 
(adaltrin) <adalt...@cisco.com>; Jorge Salazar <jorge.sala...@amdocs.com>; Eli 
Williams (eliwill) <eliw...@cisco.com>; Fatih Degirmenci 
<fatih.degirme...@ericsson.com>; huangzhipeng <huangzhip...@huawei.com>; Ramki 
Krishnan <ram...@vmware.com>; Morales, Victor <victor.mora...@intel.com>; HU, 
BIN <bh5...@att.com>; Tal Liron <tli...@redhat.com>; Stephen Terrill 
<stephen.terr...@ericsson.com>; Beejal Shah <beejal.s...@amdocs.com>; CHAPNICK, 
AVI <avi.chap...@amdocs.com>; Robin George <robi...@amdocs.com>; Munish Agarwal 
<munish.agar...@ericsson.com>; Avdhut Kholkar <avdhut.khol...@amdocs.com>; 
Yang, Bin (Wind River) <bin.y...@windriver.com>; denghui (L) 
<denghu...@huawei.com>; FREEMAN, BRIAN D <bf1...@att.com>; Ke Liang 
<lia...@vmware.com>; Lingli Deng <denglin...@chinamobile.com>; Gaoweitao 
(Victor, MANO) <victor@huawei.com>; huang.zhuo...@zte.com.cn; HILTU

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

2018-03-23 Thread HU, BIN
Hi Lingli,

Thank you for your review and questions.

VES team (led by Alok Gupta) has been working with Modeling team (Andrew Mayer 
etc), and VES model is already aligned with the ONAP Telemetry model. So the 
team is specifically looking for the feedback of specific metrics applicable to 
MultiVIM.

The team got feedback from VMWare and Intel, and has been working on the high 
level metrics we would need to support MultiVIM project. We are in the process 
of finalizing the details of metrics. The plan is to finalize the requirements 
by end of the month and send them out for review.

The current ask was to include MultiVIM metrics within the defined block of 
measurementForVfscaling and the team is in the process of finalizing it.

Hope this helps.
Thanks
Bin

From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Thursday, March 22, 2018 9:16 PM
To: HU, BIN <bh5...@att.com>; onap-discuss@lists.onap.org
Cc: 'zhang ab' <zhanganb...@chinamobile.com>; 'Ke Liang' <lia...@vmware.com>; 
'Hellmann, Gil' <gil.hellm...@windriver.com>; 'Andrew Philip' 
<aphi...@microsoft.com>; denghu...@huawei.com; 'Rittwik Jana' 
<rittwik.j...@gmail.com>
Subject: RE: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM 
Metrics for VES Requirement

Hi Bin,

Sorry for the late response on this thread.

I have the following questions and would appreciate your clarifications if 
possible:
1, Is it intended for R2 implementation?
2, Is it calling for feedback on metrics or feedback on data/information model?

From the content you shared, although it is entitled as “Multi-Cloud Data 
Model”, the “Next Steps”listed on Page 12 as follows, which confuses me with 
the intention of the last call, are we evaluating the VES metrics from Pages 
5-10 or a data model/schema which I cannot find from the current slides deck? 
Is there anything else I could refer to for clarification?

In either case, I suppose it would be great to sync it to modeling group before 
committing any changes that might impact ONAP Data/Information Model.

[cid:image001.jpg@01D3C277.9916A050]

Thanks,
Lingli


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of HU, BIN
Sent: 2018年3月15日 3:15
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: zhang ab <zhanganb...@chinamobile.com<mailto:zhanganb...@chinamobile.com>>; 
Ke Liang <lia...@vmware.com<mailto:lia...@vmware.com>>; Hellmann, Gil 
<gil.hellm...@windriver.com<mailto:gil.hellm...@windriver.com>>; Andrew Philip 
<aphi...@microsoft.com<mailto:aphi...@microsoft.com>>
Subject: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics 
for VES Requirement

Hello my fellow colleagues in MultiVIM project,

Following our great discussion on February 26th, and follow up email on Feb 
27th for feedback of MultiVIM metrics in VES requirement, this is the last call 
for feedback.

Please provide any feedback in terms of MultiVIM metrics for VES Requirement. 
VES team intends to publish official requirement next week.

Because this is the last call for feedback, and prior communication has been 
made for reasonable times. Lacking of feedback means that MultiVIM project team 
agrees to official VES requirement that will be published next week.

Thank you everyone.
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of GUPTA, ALOK
Sent: Tuesday, February 27, 2018 10:07 AM
To: aasm...@redhat.com<mailto:aasm...@redhat.com>; 
bj@intel.com<mailto:bj@intel.com>; 
tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>; 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; 
scott.mansfi...@ericsson.com<mailto:scott.mansfi...@ericsson.com>; 
mario.rodrig...@arm.com<mailto:mario.rodrig...@arm.com>; 
aput...@redhat.com<mailto:aput...@redhat.com>; 
calin.gher...@intel.com<mailto:calin.gher...@intel.com>; SULLIVAN, BRYAN L 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>; 
romanx.korynkev...@intel.com<mailto:romanx.korynkev...@intel.com>; 
manish.ja...@cavium.com<mailto:manish.ja...@cavium.com>; 
pavan.gu...@calsoftinc.com<mailto:pavan.gu...@calsoftinc.com>; 
damien.po...@intel.com<mailto:damien.po...@intel.com>; 
kand...@us.ibm.com<mailto:kand...@us.ibm.com>; 
wesley.campb...@intel.com<mailto:wesley.campb...@intel.com>; Javier Arauz 
<j.javier.ar...@gmail.com<mailto:j.javier.ar...@gmail.com>>; 
ning@intel.com<mailto:ning@intel.com>; 
ab...@redhat.com<mailto:ab...@redhat.com>; 
tarasx.chor...@intel.com<mailto:tarasx.chor...@intel.com>; 
ola.liljed...@arm.com&l

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

2018-03-15 Thread HU, BIN
Jessie,

Thank you for your interest. Please refer to this 
link<https://wiki.onap.org/download/attachments/8227952/Multi%20VIM%20Data%20Model.pptx?version=1=1521138254534=v2>
 for the document.

Look forward to your feedback.

Thanks
Bin

From: jessie jewitt [mailto:jessie.jew...@oamtechnologies.com]
Sent: Thursday, March 15, 2018 10:18 AM
To: HU, BIN <bh5...@att.com>
Cc: onap-discuss@lists.onap.org; zhang ab <zhanganb...@chinamobile.com>; Ke 
Liang <lia...@vmware.com>; Hellmann, Gil <gil.hellm...@windriver.com>; Andrew 
Philip <aphi...@microsoft.com>
Subject: Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM 
Metrics for VES Requirement

This is a long email chain. Could you please provide a link to the document 
that is supposed to be reviewed and for which we should provide feedback?
Thank you,
Jessie

On Wed, Mar 14, 2018 at 12:14 PM, HU, BIN 
<bh5...@att.com<mailto:bh5...@att.com>> wrote:
Hello my fellow colleagues in MultiVIM project,

Following our great discussion on February 26th, and follow up email on Feb 
27th for feedback of MultiVIM metrics in VES requirement, this is the last call 
for feedback.

Please provide any feedback in terms of MultiVIM metrics for VES Requirement. 
VES team intends to publish official requirement next week.

Because this is the last call for feedback, and prior communication has been 
made for reasonable times. Lacking of feedback means that MultiVIM project team 
agrees to official VES requirement that will be published next week.

Thank you everyone.
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of GUPTA, ALOK
Sent: Tuesday, February 27, 2018 10:07 AM
To: aasm...@redhat.com<mailto:aasm...@redhat.com>; 
bj@intel.com<mailto:bj@intel.com>; 
tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>; 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; 
scott.mansfi...@ericsson.com<mailto:scott.mansfi...@ericsson.com>; 
mario.rodrig...@arm.com<mailto:mario.rodrig...@arm.com>; 
aput...@redhat.com<mailto:aput...@redhat.com>; 
calin.gher...@intel.com<mailto:calin.gher...@intel.com>; SULLIVAN, BRYAN L 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>; 
romanx.korynkev...@intel.com<mailto:romanx.korynkev...@intel.com>; 
manish.ja...@cavium.com<mailto:manish.ja...@cavium.com>; 
pavan.gu...@calsoftinc.com<mailto:pavan.gu...@calsoftinc.com>; 
damien.po...@intel.com<mailto:damien.po...@intel.com>; 
kand...@us.ibm.com<mailto:kand...@us.ibm.com>; 
wesley.campb...@intel.com<mailto:wesley.campb...@intel.com>; Javier Arauz 
<j.javier.ar...@gmail.com<mailto:j.javier.ar...@gmail.com>>; 
ning@intel.com<mailto:ning@intel.com>; 
ab...@redhat.com<mailto:ab...@redhat.com>; 
tarasx.chor...@intel.com<mailto:tarasx.chor...@intel.com>; 
ola.liljed...@arm.com<mailto:ola.liljed...@arm.com>; 
raghuveer.re...@intel.com<mailto:raghuveer.re...@intel.com>; 
yangya...@chinamobile.com<mailto:yangya...@chinamobile.com>; 
serkant.ulude...@argela.com.tr<mailto:serkant.ulude...@argela.com.tr>; 
krishna.j.mur...@intel.com<mailto:krishna.j.mur...@intel.com>; 
opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>; 
andrew.duig...@intel.com<mailto:andrew.duig...@intel.com>; Srinivas Chaganti 
<schaga...@versa-networks.com<mailto:schaga...@versa-networks.com>>; MORTON 
JR., AL <acmor...@att.com<mailto:acmor...@att.com>>
Subject: Re: [opnfv-tech-discuss] Updated invitation: [barometer] Weekly Call @ 
Weekly from 12pm to 1pm on Tuesday (EDT) 
(opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>)

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Team:

Please find enclosed a presentation from ONAP mulit-vim project requesting 
feedback on the metrics we should include in the main body. Please help provide 
feedback on following:

-  Please see chart 5 with metrics categories currently in VES shown on 
the Left column. The list from Right column includes metrics that could be 
included with VES frame work. Please provide feedback, the ones that you would 
like me to include in VES mfvs domain.

-  ON pages 7 thru 10 we define metrics that is VES and delta metrics 
detail that is currently not in VES. Please review the embedded excel file on 
pg 5 and the pg 7 thru 10 and advice if you would like me to expand the metrics 
category.
Please send me feedback soon, so I can update VES Requirements and provide you 
a draft copy for approval.

Regards,

Alok Gupta
732-420-7007&l

[onap-discuss] [COE] Today's Meeting is Cancelled

2018-02-27 Thread HU, BIN
Hello community,

Isaku is on OpenStack PTG this week. There is no outstanding agenda item today. 
Thus our COE weekly meeting is canceled today.

Quick update of where we are:

-  K8s Plugin Spec:

o   It is being reviewed at Gerrit. Current patchset is #13.

-  Repo for k8s Plugin:

o   Isaku has sent request to Gilda some time ago.

o   Gilda is waiting for MultiVIM PTL's acknowledgement in order to create the 
new repo for k8s Plugin.

Thank you, and let us re-convene after Isaku is back next week.

Bin

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


[onap-discuss] Inaugural Meetup 02/09/2018 - Open Source Networking Bay Area User Group

2018-02-01 Thread HU, BIN
Hello communities of LFN,

We are very excited to announce our Open Source Networking Bay Area User 
Group's Inaugural Meetup of the 2018 New Year, which will be held on Friday, 
02/09/2018 and hosted by Lumina Networks.

-  Date/Time: 12:30pm-4:00pm, Friday February 9th.

-  Venue: Lumina Networks, 2055 Gateway Place, 1st Floor Training Room, 
San Jose, CA.

We will start with a special guest presentation, in which you will receive 
insights from Verizon, who recently joined ONAP, on building a programmable 
network infrastructure using open source SDN technology. We will also talk 
about OpenDaylight (ODL) and its new offerings on Oxygen and upcoming Flourine 
release, how ONAP can orchestrate workloads into multiple clouds, container 
networking for Kubernetes (K8s), and learn about a new tool from OPNFV 
Lab-as-a-Service.

For more details, please visit and RSVP at 
https://www.meetup.com/Open-Source-Networking-User-Group-Bay-Area/events/246581633/.

Come. Connect. Enjoy. FREE FOOD AND DRINKS.

Thank you

Bin Hu
Co-Organizer, Open Source Networking Bay Area User Group

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


[onap-discuss] [multicloud] Planned use of repo "multicloud/azure"

2018-01-16 Thread HU, BIN
Hello community,

MultiVIM/Cloud R2 (Beijing) Release will include support of Azure as a stretch 
goal. Thus we are planning to develop Azure Plugin in the repo 
"multicloud/azure".

This is a courtesy notice to the community regarding the planned use of repo 
"multicloud/azure", which is currently empty. If there is any concern or other 
plan from the community regarding this planned usage, please share your 
thoughts, concerns and/or other plans.

Thank you
Bin

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


Re: [onap-discuss] [ONAP container] ONAP event follow up: next steps and logistics(doodle poll)

2017-12-18 Thread HU, BIN
Thank you Isaku, and I have uploaded my presentation.

Happy holidays
Bin
-Original Message-
From: Isaku Yamahata [mailto:yamah...@private.email.ne.jp] 
Sent: Thursday, December 14, 2017 2:54 PM
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org; HU, BIN 
<bh5...@att.com>; ram...@vmware.com; gil.hellm...@windriver.com; 
munish.agar...@ericsson.com; fzdar...@redhat.com; quinton.ho...@huawei.com; 
Bhatia, Manjeet S <manjeet.s.bha...@intel.com>
Cc: yamah...@private.email.ne.jp; isaku.yamah...@gmail.com; 
isaku.yamah...@intel.com
Subject: [ONAP container] ONAP event follow up: next steps and logistics(doodle 
poll)

Hello ONAP kubernetes folks.
This week we had good discussions and got feedback from TSC.
In order to follow to the feedback and make the next step, I'd like to arrange 
weekly zoom meeting.


* doodle poll for timeslot for zoom meeting I've created a doodle poll for 
meeting. Please vote for timeslot.
https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_hkas87yba5bcyfs9=DwIBAg=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=r0eqbkeKLviJwSu6gx3ugv4mEdBvvEK7UlV2A8EXocA=FuK-e0HD_c03qT6i6j4wyJjBxvu58Ua2SiK2suPG54Y=
We can start meeting from the week of Jan 1 or 8, 2018.
If we're agressive, we can also have a meeting on the week of Dec 18, 2017.


* wiki page
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D16007890=DwIBAg=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=r0eqbkeKLviJwSu6gx3ugv4mEdBvvEK7UlV2A8EXocA=bSDB9oigIy7p2oA3xkNuIS04UDOHJ6zvicf_FyfS75E=
 
I've created this wiki page to collect/accumulate information.

Bin, Can you please up load your presentations and create link?
Frank, Can you please please create your proposal and upload it?
Hopefully your proposal can on the table for discussion.


There are several discussion points.
- how to deploy VNF
  So far we have two proposals. Bin's proposal and Munish proposal(3 options).
  - use ARIA or not
  - use Helm or not
  - relationship to TOSCA

- Life Cycle Management(LCM)
  There are several aspects of LCM and the how to architect
  generic VNF controller in the contest of k8s.
  - configuration
  - auto scaling
  - rolling upgrade

- relationship to other ONAP component
  especially multicloud, SO, OOF and modeling would have a deep relationship.


- any other discussion points?

Thanks,
-- 
Isaku Yamahata <isaku.yamah...@gmail.com>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

2017-11-30 Thread HU, BIN
Michael,

Looks very cool, and information shown are very helpful.

Thank you very much
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of OBRIEN, FRANK MICHAEL
Sent: Thursday, November 30, 2017 8:53 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

Bin,
 For reference, there is an unprotected continuous deployment server we use 
to verify commits running the OOM master build hourly (No DCAE yet) where you 
can get a view of the runtime configuration of a single node (ONAP R1 currently 
fits in a 64G vm) – the kubernetes UI will show individual docker container 
cpu/ram limits.
 Launch the rancher UI and the Kubernetes console to see resource usage
 The CD server gets cleared/recreated at the top of the hour and is usually 
up within 25-45 min depending on the health check status (which may push 
maximum wait time for pods-up) – it is idle for the last 15 min of the hour.
  Note it is only a 4 core VM – so multiple users may slow the system

  Rancher UI: 
http://dev.onap.info:8880/env/1a7/infra/hosts/1h1/containers<https://urldefense.proofpoint.com/v2/url?u=http-3A__dev.onap.info-3A8880_env_1a7_infra_hosts_1h1_containers=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=qAo8np3_ZClZ5RDeIoAvxkN7lpUTlXkN4vje1s0Ovl8=UONiw6THyl_nd3FwD6v8TMrvurMOdqZ1MEopH4tSDY0=>
 - it may switch back to cd.onap.info in the future
  Kubernetes Console: 
http://dev.onap.info:8880/r/projects/1a7/kubernetes-dashboard:9090/#!/pod?namespace=_all<https://urldefense.proofpoint.com/v2/url?u=http-3A__dev.onap.info-3A8880_r_projects_1a7_kubernetes-2Ddashboard-3A9090_-23-21_pod-3Fnamespace-3D-5Fall=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=qAo8np3_ZClZ5RDeIoAvxkN7lpUTlXkN4vje1s0Ovl8=lR3QasrJVIn41WjjrNnQ6WM2ig-w1nC-8GyJF-yMLdM=>
  Check status at 
http://jenkins.onap.info/job/oom-cd/<https://urldefense.proofpoint.com/v2/url?u=http-3A__jenkins.onap.info_job_oom-2Dcd_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=qAo8np3_ZClZ5RDeIoAvxkN7lpUTlXkN4vje1s0Ovl8=BeYkQkS8dsQ7Q1y7tFDs46pJMWs7u-iiOinqmkSH2yY=>

  Thank you
  /michael


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Thursday, November 30, 2017 14:14
To: HU, BIN <bh5...@att.com<mailto:bh5...@att.com>>; 
eric.deb...@orange.com<mailto:eric.deb...@orange.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

Bin,

Are you talking about the k8s cluster? If so, please look at these best 
practices: 
https://kubernetes.io/docs/tasks/administer-cluster/highly-available-master/<https://urldefense.proofpoint.com/v2/url?u=https-3A__kubernetes.io_docs_tasks_administer-2Dcluster_highly-2Davailable-2Dmaster_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=qAo8np3_ZClZ5RDeIoAvxkN7lpUTlXkN4vje1s0Ovl8=BcqZnUXS6XZvbnx5hV3XQ8O7webcVQQVmhhZl2sw0TE=>

Marco

From: "HU, BIN" <bh5...@att.com<mailto:bh5...@att.com>>
Date: Thursday, November 30, 2017 at 12:54 PM
To: "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com<mailto:plata...@research.att.com>>, 
"eric.deb...@orange.com<mailto:eric.deb...@orange.com>" 
<eric.deb...@orange.com<mailto:eric.deb...@orange.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: RE: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

Is there a typical cluster configuration documented somewhere? such as:

-  Recommended number of master nodes for HA?

-  Recommended number of worker nodes?

-  Recommended capacity of each master node (CPUs, RAM and storage)?

-  Recommended capacity of each worker node (CPUs, RAM and storage)?

Thanks
Bin

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Thursday, November 30, 2017 8:55 AM
To: eric.deb...@orange.com<mailto:eric.deb...@orange.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Eric,

You are right saying that full HA deployment will require a lot of resources, 
but that is true for the Heat approach only. If we use K8s, instead of 7 VMs 
for SDNC (SDNC here is just an example, based on numbers that Dan provided

Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

2017-11-30 Thread HU, BIN
Is there a typical cluster configuration documented somewhere? such as:

-  Recommended number of master nodes for HA?

-  Recommended number of worker nodes?

-  Recommended capacity of each master node (CPUs, RAM and storage)?

-  Recommended capacity of each worker node (CPUs, RAM and storage)?

Thanks
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Thursday, November 30, 2017 8:55 AM
To: eric.deb...@orange.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Eric,

You are right saying that full HA deployment will require a lot of resources, 
but that is true for the Heat approach only. If we use K8s, instead of 7 VMs 
for SDNC (SDNC here is just an example, based on numbers that Dan provided) we 
have 3 times (still based on Dan’s numbers) the number of containers that SDNC 
runs in a non-replicated environment.

Then, we need to adjust the size of the cluster accordingly. As I said in a 
previous email, the resource required by each single container depend on what 
that container does. I don’t have number to share, except that, based on OOM 
Team’s experience, 64 GB worked well for non-replicated ONAP (excluding DCAE). 
I expected that number going up when we use HA, but still reasonably, not even 
close to what Heat would require.

Marco

From: 
>
 on behalf of "eric.deb...@orange.com" 
>
Date: Thursday, November 30, 2017 at 11:38 AM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource 
needs

Hello

We first need to define what we want to test on the labs.

We need various platforms to test at least a minimal installation on various 
environments to validate that the installation works fine in different 
environments (ie 3 different platforms) in a daily basis.
I believe that we need around 100~150 GB RAM memory for that (we are working to 
optimize a minimal installation).
We can offer our lab for that.

Each project should test their various modules in standalone and cluster mode 
and that should not require such many resources on a project basis.

Now, do we need to test a full HA mode for all the components ?
If yes, It may require a huge amount of resources according to first answers 
(eg SDNC) running on different platforms.
We need to estimate that.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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


Re: [onap-discuss] [MultiVIM] local sdn controller APIs

2017-09-15 Thread HU, BIN
Hi Serkant,

In MultiVIM project, the long-term goal (R2 and beyond) is to support 
multi-vendor SDN local controllers.

We will be implementing a model-driven framework to support:

-  Standard model of network resources and services (common and custom)

-  Standard NBI (APIs) are auto-generated based on model definition

-  SBI interfaces (e.g. Shim Layer) to interface with vendor-specific 
APIs of 3rd party SDN local controllers

We are working on implementation plan, i.e. what specifically can be 
implemented in R2 and a roadmap of implementation beyond R2, based on resource 
availability.

Hope it helps
Thanks
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Serkant Uluderya
Sent: Friday, September 15, 2017 12:31 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [MultiVIM] local sdn controller APIs

Dear MultiVIM team,

MultiVIM component is responsible for configuring overlay networks via local 
SDN controllers for the cloud infrastructure. Does it mean that MultiVIM will 
be able to talk directly with a 3rd party SDN controller? In Volte UseCase for 
R1, it seems that SDNC would be responsible implementing the APIs from the 
local SDN controller. Do you plan to implement those APIs for the R2 in 
MultiVIM?

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


[onap-discuss] Bay Area User Group Meetup on 08/31/2017 Thursday in Cable Labs, Sunnyvale

2017-08-25 Thread HU, BIN
Hello folks,

Our quarterly meetup of OPNFV Bay Area User Group is less than a week away:

-  4pm-6pm on Thursday 08/31 hosted by Cable Labs in Sunnyvale, CA.

We will start with an events update (Beijing Summit plus 2H Plugfest) by Ray, 
followed by SNAPS-OO introduction by Tetsuya, and focus on exploring the topic 
of OPNFV automating ONAP integration.

If you are in San Francisco Bay Area (a.k.a. Silicon Valley) at that time, 
please join us. We will be delighted to see as many  of you as possible.

For more details of the event, and driving direction and maps, please go to 
https://www.meetup.com/OPNFV-Bay-Area-User-Group/events/242228679/, and 
register there.

FREE PIZZA AND SNACKS, and plus HAPPY HOUR PERKS.

See you there.

Bin Hu
Chair of OPNFV Technical Community Weekly Discussion
Organizer of OPNFV Bay Area User Group
OPNFV Ambassador

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


Re: [onap-discuss] [onap-tsc] Call for Self-Nominations for Multi VIM/Cloud Project PTL

2017-06-26 Thread HU, BIN
Congratulations, Xinhui.

Thanks
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Danny Lin
Sent: Sunday, June 25, 2017 9:44 AM
To: onap-discuss@lists.onap.org; onap-tsc 
Subject: Re: [onap-discuss] [onap-tsc] Call for Self-Nominations for Multi 
VIM/Cloud Project PTL

Dear Multi VIM/Cloud project committers,

Thanks for voting. The poll was closed on June 24th, 11:45 pm PDT. All 
committers have voted.

Xinhui Li has been voted as PTL of Multi VIM/Cloud project.

Details of voting result can be seen at
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_8907a52209a9f72a

Regards,

Danny

From: > 
on behalf of Danny Lin >
Date: Friday, June 23, 2017 at 12:15 AM
To: "onap-discuss@lists.onap.org" 
>, onap-tsc 
>
Subject: [onap-tsc] [onap-discuss] Call for Self-Nominations for Multi 
VIM/Cloud Project PTL

Dear Multi VIM/Cloud committers,

I would like to inform you that the poll has been set up for vote collection.

The poll will be closed on Saturday, June 24th, 11:59 PM, PDT.

Regards,

Danny


From: 
>
 on behalf of Danny Lin >
Date: Wednesday, 21 June 2017 at 2:15 AM
To: "onap-discuss@lists.onap.org" 
>, onap-tsc 
>
Subject: [onap-discuss] Call for Self-Nominations for Multi VIM/Cloud Project 
PTL

Hello all

The Multi VIM/Cloud project is soliciting self nominations for its Project 
Technical Lead. Per TSC instructions, nominees should be from those listed as 
committers on the Multi VIM/Cloud project proposal approved by the ONAP TSC 
(https://wiki.onap.org/pages/viewpage.action?pageId=3247262). The nomination 
period will end on Thursday, June 22, 11:59pm PDT

To nominate, please send an email to the onap-discuss list, stating your 
interest, and a short bio for helping people to know you better. After the 
nomination period is closed, a voting poll will be set up for vote collection.

Thanks,

Danny

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


[onap-discuss] [multicloud] MultiVIM/Cloud PTL Self-Nomination

2017-06-20 Thread HU, BIN
Dear MultiVIM/Cloud Committers,



I would like to nominate myself, Bin Hu, for the role of PTL for MultiVIM/Cloud.



I have been working in the technology sector for over 20 years. My technical 
experience and expertise ranges across multiple disciplines, from network 
infrastructure and networking, cloud computing, NFV and SDN, to mobile device, 
web platform and mobile Internet. My open source experience started from 
Android platform, and extended to OPNFV and OpenStack. I have taken PTL roles 
in both OPNFV (IPv6) and OpenStack (Gluon), bringing not only the excellent 
leadership but also the technology of supporting multiple SDN local controllers 
to MultiVIM/Cloud.



My achievement in technology sector includes Winner of 2015 OPNFV Annual Award, 
and 2012 OMA Contributor and Achievement Award for Outstanding Contribution to 
Cloud Computing and Content Delivery.



I currently work for AT Over the course of my career, I have worked as 
developer, engineer, development manager, and technical product manager for 
Internet startup (Infoseek), content provider (Disney Internet Group), device 
vendor (Motorola), infrastructure vendor (Huawei), as well as operators (NTT 
and AT). My diversified background and experience will make sure that I have 
a broad view of technology excellence and business priority, balance of long 
term goal and short term deliverables, a clear vision and a practical path from 
reality to vision. I will facilitate the collaboration with all stakeholders, 
and strive for excellence and success of our project.



Thank you for consideration and support.



Bin Hu

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


Re: [onap-discuss] [onap-tsc] ONAP Release Naming Framework Election Has Concluded - Global Cities Wins

2017-06-12 Thread HU, BIN
Note sure how “Amsterdam” was there.

For the official record 
https://lists.onap.org/pipermail/onap-tsc/2017-May/000598.html, the original 
proposal was “Anchorage”.

I didn’t see any other proposal on the public mailing list.

The same holds true for “Casablanca”, “Fiji”, “Guiling” , “Juarez” and “Kyoto”. 
All of those have official public record in mailing list. Others don’t.

Thanks
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Monday, June 12, 2017 11:40 AM
To: Lisa Caywood ; Phil Robb 

Cc: onap-discuss@lists.onap.org; onap-tsc 
Subject: Re: [onap-discuss] [onap-tsc] ONAP Release Naming Framework Election 
Has Concluded - Global Cities Wins

Hi Lisa,

I understand the concerns you brought up. However, we need your immediate 
recommendations regarding the naming of our first release “Anchorage” or 
“Amsterdam”.
This is critical as we are using these names while discussing Release plan and 
in our tool chain.

[cid:image001.jpg@01D2E374.CFF977B0]

Thanks,
Gildas

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

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lisa Caywood
Sent: Wednesday, June 07, 2017 10:20 AM
To: Phil Robb
Cc: onap-discuss@lists.onap.org; onap-tsc
Subject: Re: [onap-tsc] ONAP Release Naming Framework Election Has Concluded - 
Global Cities Wins

For the record, Marketing had two concerns with Cities:

1) OpenStack also uses some cities, so we would need to ensure that our names 
do not overlap with theirs.

2) Visual elements (for launch banners and other branding assets) - many cities 
look like other big cities. We would want to ensure that each city picked has a 
widely recognized landmark to anchor on.

Obviously both of these are very manageable, just things to be aware of.

Regards, Lisa

On Wed, Jun 7, 2017 at 3:17 AM, Phil Robb 
> wrote:
Hello All:

The Release Naming Framework election has concluded and the winner is "Global 
Cities".
Result detailsHide details




1

2

3

4

5

1. Global Cities



-

106

117

130

147

2. Scientists



99

-

111

131

132

3. Music Composers



87

82

-

108

131

4. Philosophers



74

51

81

-

116

5. Zodiac Signs



55

62

63

73

-


Before we make it official, we need to run the idea by the Marketing Folks to 
make sure they have no issues with it.

I'll keep you posted.

Thanks to all of those folks that voted.  We had 210 votes all told.

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb

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



--
Lisa Caywood
Director of Ecosystem Development | OpenDaylight Project | 
lcayw...@opendaylight.org | +1 408 857 3642
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] Some questions regarding Controllers in ONAP Architecture

2017-04-18 Thread HU, BIN
Hello community,

Reading current ONAP architecture [1] and tutorial of setting up the base ONAP 
stack [2], I have a few questions regarding those controllers:

-  SDN Agent:

o   What is the role, features and functions of SDN Agent? How is it different 
from Network Controller?

o   I couldn't find any code of SDN Agent in ONAP repo [3]. Does anyone know 
where it is?

-  Infrastructure Controller:

o   Is it OpenStack Nova? Or is it agnostic of any VIM and OpenStack is just 
one of the VIM?

o   If the intention is to be agnostic of VIM, and support other VIMs, where is 
a plugin/adaptor from architecture point of view?

o   I couldn't find code either in ONAP [3]. Does anyone know where it is?

-  Network Controller:

o   Is it OpenStack Neutron or ODL? Or Neutron with ODL as backend?

o   I found the code in [3], but it seems it only installs ODL there (correct 
me if I am wrong).

o   What is the primary role, features and functions of Network Controller 
other than those in ODL?

-  App Controller:

o   Are we using ODL too as App Controller?

o   Or Is it a container orchestrator or something else?

Appreciate if someone can explain some details, or give the pointer to more 
detailed documentation.

Thanks
Bin

[1] https://wiki.onap.org/display/DW/ONAP at 
ONS2017?preview=/3245268/3245303/ONAP%20Architecture%20Overview%20_Final-1.pdf
[2] 
https://wiki.onap.org/display/DW/Tutorial%3A+Configuring+and+Starting+Up+the+Base+ONAP+Stack
[3] https://git.onap.org/

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