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

[zhang.maopeng1]

Hello


   


   6. VNFD: https://jira.onap.org/browse/MODELING-72


According to the time limited, CMCC and ZTE as volunteers will corperate to 
take the classes for R2 needed.






BR


Maopeng



原始邮件



发件人：denghui(L) 
收件人：onap-discuss@lists.onap.org onap-tsc 

抄送人：Rittwik Jana 
日 期 ：2018年03月10日 09:51
主 题 ：Re: [onap-tsc] [modeling] ONAP R2 IM to DM design


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

  

Hello all


 


Currently, only 1,2,3,5 have been take, many thanks to Ericsson/Intel/Huawei


we still missing contributor for 4,6,7, R2 DM spec aligned with IM need to be 
finalized before next Tuesday modeling call.


 


Please help to volunteer


 


Thanks a lot


 


DENG Hui


 



From: denghui (L) 
 Sent: Thursday, March 8, 2018 8:46 PM
 To: onap-discuss@lists.onap.org; 'onap-tsc' 
 Cc: Rittwik Jana ; 'Lingli Deng' 

 Subject: [modeling] ONAP R2 IM to DM design




 


Hello all


 


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


 


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


 


The tasks including:


1. VDU: https://jira.onap.org/browse/MODELING-67


2. HPA: https://jira.onap.org/browse/MODELING-68


3. CP: https://jira.onap.org/browse/MODELING-69


4. DeploymentFlavor: https://jira.onap.org/browse/MODELING-70


5. VL: https://jira.onap.org/browse/MODELING-71


6. VNFD: https://jira.onap.org/browse/MODELING-72


7. monitor: https://jira.onap.org/browse/MODELING-73


 


It’s expected that the lead would help provide tosca definitions on the 
contribution page 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile) and


help implement related logic in SDC, APPC/VFC projects.


 


Thanks a lot


 


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

Re: [onap-discuss] [multvim] MultiVIM broker does not support multipart/form-request

[Yang, Bin]

Hi Avdhut Kholkar

I would suggest you create a jira ticket for this issue and we will take care 
of it.

B.R.

Bin

> 在 2018年3月10日，01:04，Avdhut Kholkar  写道：
> 
> Avdhut Kholkar
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

[denghui (L)]

Hello all

Currently, only 1,2,3,5 have been take, many thanks to Ericsson/Intel/Huawei
we still missing contributor for 4,6,7, R2 DM spec aligned with IM need to be 
finalized before next Tuesday modeling call.

Please help to volunteer

Thanks a lot

DENG Hui

From: denghui (L)
Sent: Thursday, March 8, 2018 8:46 PM
To: onap-discuss@lists.onap.org; 'onap-tsc' 
Cc: Rittwik Jana ; 'Lingli Deng' 

Subject: [modeling] ONAP R2 IM to DM design

Hello all

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

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

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

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

Thanks a lot

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

Re: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs adjustment

[Michael O'Brien]

Not that I know of - I don't know the plans of the DCAEGEN2 team right now - 
but I understand that the Beijing implementation of DCAEGEN2 is very different 
from amsterdam

For myself I can only run DCAE on openlab via amsterdam.
We will know when it is ported - by watching for changes in onap-parameters.yaml
The one in master is still bare-bones.
https://git.onap.org/oom/tree/kubernetes/config/onap-parameters.yaml
https://git.onap.org/oom/tree/kubernetes/config/onap-parameters.yaml?h=amsterdam

I know of 3 or 4 options - don't know which one will be the final

Port amsterdam heatbridge (Alexis D.T.'s) over to master - either as is or 
reduced VM's - I hear the 7 cdap nodes are getting reduced in number
Finish the containerization of cloudify manager - I hear it is almost complete
Run openstack on kubernetes
Fully containerize cloudify and dcae

Q) is the Beijing job running Beijing or amsterdam - it looks like amsterdam 
but without DCAE running - I periodically get questions about it.
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/

I am trying to figure out why the 2 systems run differently since 2 March.

From: Gary Wu [mailto:gary.i...@huawei.com]
Sent: Friday, March 9, 2018 16:27
To: Michael O'Brien ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes 
healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs 
adjustment

Hi Michael,

Thanks for the heads up.  Does this also mean that DCAE is now enabled in OOM 
master branch?

Thanks,
Gary

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Friday, March 09, 2018 12:46 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo 
parameters modified 20180302 - 1 of 2 CD systems needs adjustment

Team,
   A heads up that a change went in last Friday under OOM-722 that merged all 
the namespaces into one.
   One of the effects of this change was to add a parameter to the healthcheck 
and vFW demo scripts - that require the namespace name (usually "onap")

./ete-k8s.sh health
./ete-k8s.sh $ENVIRONMENT health
See
https://git.onap.org/oom/tree/kubernetes/robot/demo-k8s.sh
https://gerrit.onap.org/r/#/c/32093/21/kubernetes/robot/ete-k8s.sh
https://jira.onap.org/browse/OOM-722

   For developers you will notice this right away when healthcheck commands 
fail.  For automated systems the logs or the build should pick it up.

Therefore all automated CD systems broke last Friday.
The following CD system is fixed - I also had another issue with a stuck 
nodejs install - increased build freq to 2h
http://jenkins.onap.info/job/oom-cd/
Corresponding 1-click entrypoint.sh script(and oom_rancher_install.sh, 
cd.sh) is updated as of yesterday.
https://jira.onap.org/browse/OOM-710

Friendly information sharing between E2E teams
The official CD system is still running without a fix - I would expect it 
to fail on the missing namespace - this means it is actually testing daily 
amsterdam builds (not Beijing) - unless I am missing a preset of the onap 
namespace
Integration team - you will want to either rename the Jenkins jobs to 
"amsterdam" or change the OOM deployment script to clone -b master instead.
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/
https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-oom-deploy/

for example
this needs a "onap" parameter
17:41:47 + timeout 2m ssh -o StrictHostKeychecking=no -i 
/var/lib/jenkins/.ssh/onap_key 
ubuntu@192.168.31.129 'sudo su -l root -c 
"/root/oom/kubernetes/robot/ete-k8s.sh health"'
This is also an issue when running demo commands for the vFW (the part that is 
automated)

./demo-k8s.sh onap init
Or we would see

04:14:50 Usage: demo.sh namespace  []

04:14:50demo.sh  init

04:14:50- Execute both init_customer + distribute

Raised https://jira.onap.org/browse/INT-439 as a tracking taks

 Known issues:
 SDNC rarely comes up since mid Jan 2018 because of increased docker images 
size - usually a restart fixes it (done after all other dependent pods are up)
 ONAP components take 15-40 min to come up now instead of 15-20 - adjust 
your wait states.



Thank you

Michael O'Brien
Amdocs Technology
16135955268
55268
[amdocs-a]

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
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 

Re: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs adjustment

[Gary Wu]

Hi Michael,

Thanks for the heads up.  Does this also mean that DCAE is now enabled in OOM 
master branch?

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Friday, March 09, 2018 12:46 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo 
parameters modified 20180302 - 1 of 2 CD systems needs adjustment

Team,
   A heads up that a change went in last Friday under OOM-722 that merged all 
the namespaces into one.
   One of the effects of this change was to add a parameter to the healthcheck 
and vFW demo scripts - that require the namespace name (usually "onap")

./ete-k8s.sh health
./ete-k8s.sh $ENVIRONMENT health
See
https://git.onap.org/oom/tree/kubernetes/robot/demo-k8s.sh
https://gerrit.onap.org/r/#/c/32093/21/kubernetes/robot/ete-k8s.sh
https://jira.onap.org/browse/OOM-722

   For developers you will notice this right away when healthcheck commands 
fail.  For automated systems the logs or the build should pick it up.

Therefore all automated CD systems broke last Friday.
The following CD system is fixed - I also had another issue with a stuck 
nodejs install - increased build freq to 2h
http://jenkins.onap.info/job/oom-cd/
Corresponding 1-click entrypoint.sh script(and oom_rancher_install.sh, 
cd.sh) is updated as of yesterday.
https://jira.onap.org/browse/OOM-710

Friendly information sharing between E2E teams
The official CD system is still running without a fix - I would expect it 
to fail on the missing namespace - this means it is actually testing daily 
amsterdam builds (not Beijing) - unless I am missing a preset of the onap 
namespace
Integration team - you will want to either rename the Jenkins jobs to 
"amsterdam" or change the OOM deployment script to clone -b master instead.
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/
https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-oom-deploy/

for example
this needs a "onap" parameter
17:41:47 + timeout 2m ssh -o StrictHostKeychecking=no -i 
/var/lib/jenkins/.ssh/onap_key 
ubuntu@192.168.31.129 'sudo su -l root -c 
"/root/oom/kubernetes/robot/ete-k8s.sh health"'
This is also an issue when running demo commands for the vFW (the part that is 
automated)

./demo-k8s.sh onap init
Or we would see

04:14:50 Usage: demo.sh namespace  []

04:14:50demo.sh  init

04:14:50- Execute both init_customer + distribute

Raised https://jira.onap.org/browse/INT-439 as a tracking taks

 Known issues:
 SDNC rarely comes up since mid Jan 2018 because of increased docker images 
size - usually a restart fixes it (done after all other dependent pods are up)
 ONAP components take 15-40 min to come up now instead of 15-20 - adjust 
your wait states.



Thank you

Michael O'Brien
Amdocs Technology
16135955268
55268
[amdocs-a]

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

[onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs adjustment

[Michael O'Brien]

Team,
   A heads up that a change went in last Friday under OOM-722 that merged all 
the namespaces into one.
   One of the effects of this change was to add a parameter to the healthcheck 
and vFW demo scripts - that require the namespace name (usually "onap")

./ete-k8s.sh health
./ete-k8s.sh $ENVIRONMENT health
See
https://git.onap.org/oom/tree/kubernetes/robot/demo-k8s.sh
https://gerrit.onap.org/r/#/c/32093/21/kubernetes/robot/ete-k8s.sh
https://jira.onap.org/browse/OOM-722

   For developers you will notice this right away when healthcheck commands 
fail.  For automated systems the logs or the build should pick it up.

Therefore all automated CD systems broke last Friday.
The following CD system is fixed - I also had another issue with a stuck 
nodejs install - increased build freq to 2h
http://jenkins.onap.info/job/oom-cd/
Corresponding 1-click entrypoint.sh script(and oom_rancher_install.sh, 
cd.sh) is updated as of yesterday.
https://jira.onap.org/browse/OOM-710

Friendly information sharing between E2E teams
The official CD system is still running without a fix - I would expect it 
to fail on the missing namespace - this means it is actually testing daily 
amsterdam builds (not Beijing) - unless I am missing a preset of the onap 
namespace
Integration team - you will want to either rename the Jenkins jobs to 
"amsterdam" or change the OOM deployment script to clone -b master instead.
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/
https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-oom-deploy/

for example
this needs a "onap" parameter
17:41:47 + timeout 2m ssh -o StrictHostKeychecking=no -i 
/var/lib/jenkins/.ssh/onap_key ubuntu@192.168.31.129 'sudo su -l root -c 
"/root/oom/kubernetes/robot/ete-k8s.sh health"'
This is also an issue when running demo commands for the vFW (the part that is 
automated)

./demo-k8s.sh onap init
Or we would see

04:14:50 Usage: demo.sh namespace  []

04:14:50demo.sh  init

04:14:50- Execute both init_customer + distribute

Raised https://jira.onap.org/browse/INT-439 as a tracking taks

 Known issues:
 SDNC rarely comes up since mid Jan 2018 because of increased docker images 
size - usually a restart fixes it (done after all other dependent pods are up)
 ONAP components take 15-40 min to come up now instead of 15-20 - adjust 
your wait states.



Thank you

Michael O'Brien
Amdocs Technology
16135955268
55268
[amdocs-a]

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

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

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

[onap-discuss] [OOM] Heads up: ONAP Kubernetes master has crossed the 64G VM barrier

[Michael O'Brien]

Team,
   ONAP Beijing is currently crossing the 64G boundary as of a couple weeks ago.
   If you run the system on a 128G VM then heaps will expand past 64G within 24 
hours.
   If you stay on 64G (which you can) - reduce the optional pods or you will be 
getting OOME's
   Use the ongoing POC JIRA as a guide - we need a full set of 
deploytime/runtime dependency trees to be able to know what to shutdown.
https://jira.onap.org/browse/OOM-511

   The recommended VM size (1 or a cluster) is now 80 to 128G - for Beijing 
(without the upcoming DCAE port)
   For Amsterdam the OOM side still fits in a 64G vm (you can shutdown 
vCPE/vVOLTE required pods like vfc) - heatbridge works there to DCAE which 
bring you up to 150G when the full heat side is up.

https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-HardwareRequirements
ONAP startup now reaches a peak of 60 cores so the more vCores you have the 
less CPU bound you will be.

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

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

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

[onap-discuss] [multvim] MultiVIM broker does not support multipart/form-request

[Avdhut Kholkar]

Hi MultiVIM team,

We are developing a azure plugin that accepts a TOSCA csar file and its related 
input as a json. However, we are facing an issue in the MultiVIM broker which 
does not seem to accept multipart/form-data request.
The broker  is not able to forward this request to the plugin.  We are getting 
a Unicode error given below.
Does Multivim broker support multipart/form-data content in request?


Below is the error trace:

2018-03-09 05:00:39,952:[multivimbroker.pub.utils.restcall]:[restcall.py]-[63]
   [DEBUG]:request=https://aai-service.onap-aai:8443/aai/v11/cloud-infra
structure/cloud-regions/cloud-region/azure/azure)
2018-03-09 12:32:02,874:[multivimbroker.forwarder.views]:[views.py]-[123]
  [DEBUG]:forward request
2018-03-09 12:32:02,875:[multivimbroker.pub.utils.restcall]:[restcall.py]-[63]
   [DEBUG]:request=https://aai-service.onap-aai:8443/aai/v11/cloud-infra
structure/cloud-regions/cloud-region/azure/azure)
2018-03-09 12:32:02,949:[multivimbroker.pub.utils.restcall]:[restcall.py]-[63]
   [DEBUG]:request=http://10.244.2.71:80/api/multicloud-azure/v0/azure_a
zure/createStack/servicestest2)
2018-03-09 12:32:02,952:[multivimbroker.pub.utils.restcall]:[restcall.py]-[85]
   [ERROR]:Traceback (most recent call last):
  File "/opt/multivimbroker/multivimbroker/pub/utils/restcall.py", line 81, in c
all_req
raise ex
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 178: ordina
l not in range(128)



Regards,
Avdhut Kholkar



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 


Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Schedule Update for ONS

[Kenny Paul]

Hi Alla,

the M4 Code Freeze review is on the 29th and was scheduled to align with the 
TSC meeting.
Release Planning 

There has always been a strong emphasis from the dev community to adhere to the 
published schedules. I don’t believe that there would be an issue with a room 
change, but both the TSC and the PLS would need to agree to any change.

I set up a doodle poll for Wednesday, Thursday, or Monday at the PTL meeting. 
ONLY VOTE IF YOU ARE A PTL OR TSC MEMBERI will close this poll @ 5pm 
Pacific on Monday the 12th.
https://doodle.com/poll/dcwm23ev8vi2v22s 


Any change will require both a majority of PTLs (17 of 32) and TSC (10 of 18) 
members agreeing.

Best Regards, 
-kenny

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

> On Mar 8, 2018, at 9:45 PM, Alla Goldner  wrote:
> 
> Kenny,
>  
> As for the TSC meeting: as Passover holidays start on Friday, Israeli 
> participants will leave on Thursday morning (this is the latest we can do to 
> be at home by the time the holiday starts, though without appropriate 
> holidays preparations due to ONS L).
> Is here any possibility to move TSC meeting to Wednesday?
>  
> Best regards,
>  
> Alla Goldner
>  
> Open Network Division
> Amdocs Technology
>  
>  
> 
>  
> From: onap-discuss-boun...@lists.onap.org 
>  
> [mailto:onap-discuss-boun...@lists.onap.org 
> ] On Behalf Of Kenny Paul
> Sent: Friday, March 09, 2018 1:35 AM
> To: onap-discuss  >
> Subject: [onap-discuss] Schedule Update for ONS
>  
> Just a quick update about the LFN Developer Forum schedule at ONS- 
>  
> The plenary sessions have been chosen and the Events team is currently 
> notifying speakers.  The Developer Forum schedule should be published on the 
> LFN wiki by tomorrow. LFN Developer Forum Plenary Session Proposals 
> 
>  
> If you submitted a proposal what was not selected for the plenary sessions 
> that you believe would be an equally good topic for an ONAP specific breakout 
> session, please add it to the ONAP Breakout Page  as soon as possible so the 
> that Program Committee can work on the scheduling. ONAP Project Specific 
> Breakouts 
> 
>  
> The TSC meeting itself will still occur on Thursday morning as usual. Please 
> add TSC meeting topics to the upcoming agenda page just the same as always. 
> TSC 2018-03-29 Meeting Agenda (ONS) 
> 
>  
>  
>  
> Best Regards, 
> -kenny
> 
> Kenny Paul, Technical Program Manager, The Linux Foundation
> kp...@linuxfoundation.org , 510.766.5945
> San Francisco Bay Area, Pacific Time Zone
>  
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Light installation

[Michael O'Brien]

Santiago,
   Hi, good question.  You have several options.
   In HEAT you can comment out VM's you require before running the openstack 
template
   In OOM we have the same sort of thing via the HELM_APPS config variable - in 
the near future helm commands will bring up different ecosystems or partial 
onaps

   There is a dependency tree depending on your use case vFW, vCPE, vVOLTE
   I ran through an exercise for a particular scenario focused for example on 
running policy (no open/closed loop - no SO in this case) detailed below.  Feel 
free to comment on the jira and wiki page with your specific requirements.
   Ideally we have a full list of dependency subtrees for every component.
   For example you can just run aai by itself in a 11G VM on a laptop via 
./createAll.bash -n onap -a aai

https://jira.onap.org/browse/OOM-511
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes 

HELM_APPS=('message-router' 'vid' 'portal' 'policy' 'aai' 'sdc' )

root@ip-172-31-86-138:~/oom/kubernetes/oneclick# kubectl get pods 
--all-namespaces -a
NAMESPACE NAME   READY STATUS   
 RESTARTS   AGE
onap-aai  aai-resources-2398553481-0jr3g 2/2   Running  
 0  45m
onap-aai  aai-service-749944520-dr2h81/1   Running  
 0  45m
onap-aai  aai-traversal-2677319478-ttbp6 2/2   Running  
 0  45m
onap-aai  data-router-3700447603-v0g2w   1/1   Running  
 0  45m
onap-aai  elasticsearch-622738319-xmt5m  1/1   Running  
 0  45m
onap-aai  hbase-3471984843-3plfk 1/1   Running  
 0  45m
onap-aai  model-loader-service-911950978-0tg28   2/2   Running  
 0  45m
onap-aai  search-data-service-2471976899-181pg   2/2   Running  
 0  45m
onap-aai  sparky-be-1779663793-rkm9f 2/2   Running  
 0  45m
onap-message-router   dmaap-3126594942-slbwm 1/1   Running  
 0  2m
onap-message-router   global-kafka-3848542622-bxwrb  1/1   Running  
 0  2m
onap-message-router   zookeeper-624700062-hkp6k  1/1   Running  
 0  2m
onap-policy   brmsgw-2284221413-dd8mt1/1   Running  
 0  45m
onap-policy   drools-534015681-b8xp0 2/2   Running  
 0  45m
onap-policy   mariadb-559003789-5mv1g1/1   Running  
 0  45m
onap-policy   nexus-687566637-z6dt3  1/1   Running  
 0  45m
onap-policy   pap-4181215123-j2bcc   2/2   Running  
 0  45m
onap-policy   pdp-2622241204-h8ttg   2/2   Running  
 0  45m
onap-portal   portalapps-1783099045-8m7mj2/2   Running  
 0  4m
onap-portal   portaldb-1451233177-t5wfg  1/1   Running  
 0  4m
onap-portal   portalwidgets-2060058548-2gjd1 1/1   Running  
 0  4m
onap-portal   vnc-portal-1252894321-g9lbf1/1   Running  
 0  4m
onap-sdc  sdc-be-2336519847-m28d22/2   Running  
 0  11m
onap-sdc  sdc-cs-1151560586-t4bz61/1   Running  
 0  11m
onap-sdc  sdc-es-3319302712-kj4b81/1   Running  
 0  11m
onap-sdc  sdc-fe-2862673798-gqdt52/2   Running  
 0  11m
onap-sdc  sdc-kb-1258596734-3j00r1/1   Running  
 0  11m
onap-vid  vid-mariadb-3318685446-c4djt   1/1   Running  
 0  19m
onap-vid  vid-server-421936131-rm199 2/2   Running  
 0  19m
root@ip-172-31-86-138:~/oom/kubernetes/oneclick# free
  totalusedfree  shared  buff/cache   available
Mem:   628801363130330416300900   318201527593230767432
Swap: 0   0   0
root@ip-172-31-86-138:~/oom/kubernetes/oneclick# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev314321000  31432100   0% /dev
tmpfs628801621772   6266244   1% /run
/dev/xvda1 101584140 55738232  45829524  55% /

other scenarios
HELM_APPS=('mso' 'message-router' 'vid' 'portal' 'policy' 'aai' 'sdc' )
HELM_APPS=('mso' 'message-router' 'vid' 'portal' 'policy' 'aai' 'sdc' 'clamp' )
HELM_APPS=('mso' 'message-router' 'sdnc' 'vid' 'robot' 'portal' 'policy' 'appc' 
'aai' 'sdc' 'log' 'clamp' )
HELM_APPS=('consul' 'msb' 'mso' 'message-router' 'sdnc' 'vid' 'robot' 'portal' 
'policy' 'appc' 'aai' 'sdc' 'log' 'cli' 'multicloud' 'clamp' 'kube2msb')
HELM_APPS=('consul' 'msb' 'mso' 'message-router' 'sdnc' 'vid' 'robot' 'portal' 

Re: [onap-discuss] Light installation

[Mars Toktonaliev (Nokia - US/Irving)]

Hi,

The best chance you have is probably OOM installation:
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes

It still requires at least 1 VM with 64GB of RAM and a whole lot more
resources if you want to have DCAE deployed too. 

BR
Mars

On Fri, 2018-03-09 at 09:22 +0100, Santi Rodríguez wrote:
> Hi all,
> 
> sorry if this is not the best forum to make this question but I
> deeply searched in the wiki and I didn't find a better option.
> 
> Is there a way to install/deploy an ONAP reduced resources or light
> version?
> 
> I'm trying to install the platform in my company local environment
> but i don't have the hughe amount of resources required by the full
> installation, and the component by component installation is not
> always well documented or uses references to not existing/deprecated
> code.
> 
> I saw that Beijing release will have a "light" version but I don't
> know if it's available to test.
> 
> Thanks,
> Santiago
> 
> Santiago Rodríguez García | Senior Analyst
> T/ + 34 986 410 091 (ext) 227
> www.optaresolutions.com
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss

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

Re: [onap-discuss] Cross Orgin Pre-flight Rest call to AAI

[abdelmuhaimen.seaudi]

Hi,

I was able to resolve this issue by updating the HAPROXY configuration in the 
AAI VM, as you can see below, and now the AAI supports Cross Origin CORS.


OPTIONS /aai/v11/business/customers/ HTTP/1.1
Host: aai.api.simpledemo.onap.org:8443
Connection: keep-alive
Access-Control-Request-Method: GET
Origin: https://www.w3schools.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, 
like Gecko) Chrome/64.0.3282.186 Safari/537.36
Access-Control-Request-Headers: 
authorization,content-type,x-fromappid,x-transactionid
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9,ar;q=0.8


HTTP/1.1 200 OK
Date: Fri, 09 Mar 2018 07:42:28 GMT
Allow: GET,HEAD,POST,PUT,DELETE,TRACE,OPTIONS,CONNECT,PATCH
Connection: close
Server: Jetty(9.2.z-SNAPSHOT)
Strict-Transport-Security: max-age=1600; includeSubDomains; preload;
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, HEAD, OPTIONS, POST, PUT
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Origin, Accept, X-Requested-With, 
X-TransactionId, X-FromAppId, Content-Type, Access-Control-Request-Method, 
Access-Control-Request-Headers, Authorization




Thanks

Abdelmuhaimen Seaudi
Orange Labs Egypt
Email: abdelmuhaimen.sea...@orange.com
Mobile: +2012 84644 733

From: SEAUDI Abdelmuhaimen OBS/CSO
Sent: Thursday, March 8, 2018 7:07 PM
To: onap-discuss@lists.onap.org
Cc: SEAUDI Abdelmuhaimen OBS/CSO
Subject: Cross Orgin Pre-flight Rest call to AAI

Hi

We are developing an Angular 4 web application based on ONAP Portal SDK.

When the webapp page javascript send Rest call to AAI, the browser sends a 
aross origin pre-flight OPTION request, without username/password.

This pre-flight OPTION request is rejected by AAI as 401 unauthorized.

How can we communicate properly with AAI ?


Sent from Samsung tablet.

_

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

[onap-discuss] CII Badging

[Stephen Terrill]

Hi All,

I had a short update regarding the CII Badging to present at the TSC, however 
time didn't allow and I wanted to anyway get the information out to the PTLs so 
I am sending the link to the presentation instead of waiting a week as every 
week counts now: 
https://wiki.onap.org/download/attachments/25434810/2018-03-08%20CII%20Badging%20program.pptx?version=2=1520435345000=v2

Basically I am encouraged to see the progress and the projects addressing it.  
The value in the CII badging is achieving the clarity and practices in the 
projects to have a way of working that avoids the introduction of 
vulnerabilities.  Please keep in mind when filling it out to follow the 
guidelines described here for the project naming in the CII badging (it needs 
to have ONAP in the name).  https://wiki.onap.org/display/DW/CII+Badging+Program

Some of the projects do not have the correct link listed to their Repo, please 
correct that (can be found in the presentation).

Please also pay attention to "There MUST be no unpatched vulnerabilities of 
medium or high severity that have been publicly known for more than 60 days." 
When answering.

Best Regards,

Steve



[Ericsson]

STEPHEN TERRILL
Technology Specialist
POA Architecture and Solutions
Business Unit Digital Services

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[http://www.ericsson.com/current_campaign]

Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer

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

[onap-discuss] Light installation

[Santi Rodríguez]

Hi all,

sorry if this is not the best forum to make this question but I deeply
searched in the wiki and I didn't find a better option.

Is there a way to install/deploy an ONAP reduced resources or light version?

I'm trying to install the platform in my company local environment but i
don't have the hughe amount of resources required by the full installation,
and the component by component installation is not always well documented
or uses references to not existing/deprecated code.

I saw that Beijing release will have a "light" version but I don't know if
it's available to test.

Thanks,
Santiago

*Santiago Rodríguez García* | Senior Analyst
T/ + 34 986 410 091 (ext) 227
www.optaresolutions.com
[image: Optare Solutions] 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss