Re: [onap-discuss] [OOM] StatefulSet not removed while Delete/Purge a project

[Mandeep Khinda]

Hi Dileep,
What version of helm & kubernetes are you using?

In Casablanca we have up-revved the recommended helm 2.9.1 and K8s 1.10.x

There are some known issues where dynamic PVC resources are left behind after a 
purge but not statefulsets.


From:  on behalf of Dileep Ranganathan 

Reply-To: "onap-discuss@lists.onap.org" , 
"dileep.ranganat...@intel.com" 
Date: Wednesday, October 10, 2018 at 12:15 AM
To: "onap-discuss@lists.onap.org" , Michael 
O'Brien , "Kamineni, Kiran K" 
, "NELSON JR., THOMAS" , 
"PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN" 
Subject: [onap-discuss] [OOM] StatefulSet not removed while Delete/Purge a 
project

Hi OOM team,

For the OOF project, while deleting/purging a project, there are some dangling 
resources which is affecting redeploy.
OOF has added common music charts in requirements.yaml (WIP) and it is starting 
Cassandra and Zookeeper. The statefulsets and pods related to these two 
services brought up as part of common charts are not deleted while deleting the 
project oof.

These are the steps I am following to redeploy oof in my local system.
helm del dev-oof –purge
helm deploy dev local/onap --namespace onap

And the error I am getting is.
Release "dev-oof" does not exist. Installing it now.
Error: release dev-oof failed: statefulsets.apps "dev-oof-cassandra" already 
exists

Thanks,
Dileep

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

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


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

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

Re: [onap-discuss] [oom] Helm deploy plugin to address configmap limitation

[Mandeep Khinda]

Yes that is exactly it..you can copy paste the onap/values.yaml and make it 
your own and maintain it outside of the oom git repo (in your own repo or home 
directory..somewhere safe and where you can track changes to it).  Here you can 
tweak the liveness/readiness initial delay, resource limits, image tags..pretty 
much everything found in the values for each chart/sub-chart.

And the nice thing that people may not know about is that you can use YAML 
anchors to reduce repetition..for example, I do something like this for Beijing:

global: # global defaults
  pullPolicy: IfNotPresent

openstackCommon: 
  openStackUserName: "dev"
  openStackRegion: "RegionOne"
  openStackKeyStoneUrl: "http://#.#.#.#:5000;

so:
  enabled: false
  config:
<<: *openstackCommon
openStackUserName: "dev"
openStackRegion: "RegionOne"
openStackKeyStoneUrl: "http://#.#.#.#:5000;
openStackServiceTenantName: "services"
openStackEncryptedPasswordHere: "c0d9e4d69a667c67725a9e466e6c3"
  liveness:
initialDelaySeconds: 300
  readiness:
initialDelaySeconds: 300

aai:
  enabled: true

robot:
  <<: *openstackCommon
  enabled: true
  demoArtifactsVersion: "1.2.1-SNAPSHOT"


and so on..

Mandeep



From:  on behalf of George Clapp 

Reply-To: "onap-discuss@lists.onap.org" , 
"georgehcl...@gmail.com" 
Date: Friday, September 21, 2018 at 1:14 PM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [oom] Helm deploy plugin to address configmap 
limitation

Can you share an example of an "override.yaml" file?  I've searched but can't 
find one.  Is it a complete copy of oom/kubernetes/onap/values.yaml with new 
parameter values?  Or something else?

Thanks,
George

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

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


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

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

Re: [onap-discuss] [oom] Helm deploy plugin to address configmap limitation

[Mandeep Khinda]

Hi George,
What many people do including myself is maintain their own values.yaml override 
for their particular environment.

In there you can set whatever charts you want to enabled and then feed them in 
to helm using “-f”

I suspect there is something going on with your local helm repo where it is not 
being updated properly.
Mandeep


From:  on behalf of George Clapp 

Reply-To: "onap-discuss@lists.onap.org" , 
"georgehcl...@gmail.com" 
Date: Thursday, September 20, 2018 at 3:38 PM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [oom] Helm deploy plugin to address configmap 
limitation

It's working, but it's deploying everything.  I had edited 
~/git/oom/kubernetes/onap/values.yaml to set "enabled: false" for the 
components that I didn't want.  Why is that not working?  Is there a sequence?  
Do I enter:
1.cd oom/kubernetes
2.make repo
3.make; make onap
4.helm deploy demo local/onap --namespace onap

after editing the values.yaml file?

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

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


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

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

Re: [onap-discuss] Port number missing for AAI in portal

[Mandeep Khinda]

Hi Manoop,

The steps are captured in Arul's patch: https://gerrit.onap.org/r/#/c/55139

You need to assign a free node port to the portal-sdk chart's service.  this 
can be done in its values.yaml file.  The challenge here is with how things are 
working today, it is challenging to find a free port.
I found one for you: 30234 is currently not being used by any charts.

Once that is done, you take that node port and default it in the portal-mariadb 
values.yaml.  This will then be used to update the mariadb's application URL 
with the node port.  Now it will be able to redirect to your app.

You should deploy the portal chart and test whether you can launch the new app 
as well.

Mandeep



On Thu, 2018-06-21 at 17:33 +, Manoop Talasila wrote:
Hi Arul/Mandeep,
Can you please guide me on which all files to update if I have to open a new 
port 30221 for portal-sdk? – this is related to similar pending item as AAI, 
the jira item is - https://jira.onap.org/browse/OOM-1117

I will update below file. But, are there any other files to update?

Update the new 30xxx port in file: 
https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/portal/charts/portal-mariadb/values.yaml;h=7d9b82a629df5ba0f94b34d20c4234e738e10f4a;hb=789ee4aefe17623b25375b0a17474d12bc79354a
At line: "portalSdkPort: "" # TODO: populate with port"
Manoop

From: "NAMBI, ARUL" mailto:arul.na...@amdocs.com>>
Date: Thursday, June 21, 2018 at 9:52 AM
To: Santi Rodríguez 
mailto:srodrig...@optaresolutions.com>>
Cc: "TALASILA, MANOOP (MANOOP)" 
mailto:talas...@research.att.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, 
"TATTAVARADA, SUNDER (SUNDER)" 
mailto:sta...@research.att.com>>
Subject: RE: [onap-discuss] Port number missing for AAI in portal

Hi Santi,
Thanks sorry I missed that, will get that updated in the patch.
Regards
Arul

From: Santi Rodríguez 
[mailto:srodrig...@optaresolutions.com]
Sent: Thursday, June 21, 2018 6:32 AM
To: Arul Nambi mailto:arul.na...@amdocs.com>>
Cc: TALASILA, MANOOP (MANOOP) 
mailto:talas...@research.att.com>>; 
onap-discuss@lists.onap.org; TATTAVARADA, SUNDER (SUNDER) 

Subject: Re: [onap-discuss] Port number missing for AAI in portal

Hi Arul, all,

I applied the https://gerrit.onap.org/r/#/c/55139 patch in my code and works 
perfectly!!!
I only had to make a minor change:



externalPort: 30220 instead of 9517

Now I can access to AAI from portal:


Thanks,
BR, Santiago

Santiago Rodríguez García | Senior Analyst
T/ + 34 986 410 091 (ext) 227
www.optaresolutions.com


2018-06-20 18:38 GMT+02:00 Arul Nambi 
mailto:arul.na...@amdocs.com>>:
Thanks Manoop that is what I was looking for,
I have patched my commit
https://gerrit.onap.org/r/#/c/55139/
You are one of the reviewers.
Regards
Arul

From: TALASILA, MANOOP (MANOOP) 
[mailto:talas...@research.att.com]
Sent: Wednesday, June 20, 2018 12:18 PM
To: Arul Nambi mailto:arul.na...@amdocs.com>>; 
onap-discuss@lists.onap.org
Cc: TATTAVARADA, SUNDER (SUNDER) 
mailto:sta...@research.att.com>>
Subject: Re: Port number missing for AAI in portal

Hi Arul,

I believe once you update the new 30xxx port in below file then the AAI url 
will be formed with right port number in OOM deployment, so that Portal can 
access it correctly. Along with your other changes, please see if you would 
like to submit change to below file (otherwise, in past Mandeep helped us in 
keeping track of these ports correctly).

o
https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/portal/charts/portal-mariadb/values.yaml;h=7d9b82a629df5ba0f94b34d20c4234e738e10f4a;hb=789ee4aefe17623b25375b0a17474d12bc79354a
oAt line:
  # aai sparky ui assignment for port 8080
  aaiSparkyPort: "" # TODO: populate with
  # application's front end hostname.  Must be resolvable on the client side 
environment
  aaiSparkyHostName: "aai.api.sparky.simpledemo.onap.org"
Manoop
From: "NAMBI, ARUL" mailto:arul.na...@amdocs.com>>
Date: Wednesday, June 20, 2018 at 11:19 AM
To: "TALASILA, MANOOP (MANOOP)" 
mailto:talas...@research.att.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Cc: "TATTAVARADA, SUNDER (SUNDER)" 
mailto:sta...@research.att.com>>
Subject: RE: Port number missing for AAI in portal

Hi Manoop,
You are right I am working on the OOM deployments and assigned the task OOM-347 
that you have pointed out.
The issue is I have opened up a node port(30220) for sparky in the AAI lab(FYI: 
the code is not committed yet). Now even though the port is open and I can 
access the URL from my browser

Here is a screenshot of the AAI running in OOM after I have the port exposed.


The portal is not able to open it because the port number is not a part of the 
App URL. I can change this manually from the portal UI, but I want it to be 
included as a part of the onboarding script. And since the node port in 
OOM(30220) is different from the 

Re: [onap-discuss] How to clear logs

[Mandeep Khinda]

Hi,
It is a good question as I have had my disk filled before too.

I have removed the massive .json log file from /var/lib/docker/containers/*/* 
in the past after stopping the container and docker daemon but I would not 
suggest unless you were okay with having to re-deploy the pod as I have had 
mixed success.

I think we need to add some documentation to the K8s cluster build requirements 
to enable some sort of log rotation for the docker containers.
I found this:
https://kubernetes.io/docs/concepts/cluster-administration/logging/

Kubernetes currently is not responsible for rotating logs, but rather a 
deployment tool should set up a solution to address that. For example, in 
Kubernetes clusters, deployed by the kube-up.sh script, there is a 
logrotate tool configured to run each 
hour

By default, the docker daemon uses json-file as its logging driver and this 
thing comes out of the box with an unlimited size.

https://docs.docker.com/config/containers/logging/json-file/#usage

Try setting “--log-opt max-size=[SIZE]m” in your k8s nodes where docker is 
running to prevent this from happening again.

Thanks,
Mandeep

From:  on behalf of 
"abdelmuhaimen.sea...@orange.com" 
Date: Wednesday, June 13, 2018 at 2:09 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] How to clear logs

Hi,

I was able to resolve an issue with an ONAP OOM Pod that resulted in a log file 
filling up 95% of the disk space.

Now, what if I need to clear the logs of an ONAP OOM pod ? What is the correct 
process ?

Thanks.

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


_



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.
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

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

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

Re: [onap-discuss] ONAP Portal access from outside

[Mandeep Khinda]

Hi,
In ONAP Amsterdam using OOM, supported ONAP portal is access is through the VNC 
utility pod.  Direct access was introduced in OOM Beijing.

I am sure there are ways to get direct access either by a new approach or by 
backporting what was done in Beijing.  It also depends on what you did to get 
direct access in Amsterdam using Kubernetes.

I think the problem you are facing is that the widget applications loaded by 
the portal are not being exposed externally or are not reachable by your client 
that is on the same subnet.  That is configured in the portal database for each 
application.  I believe you can view/edit this in the portal GUI under 
application or widget configuration.
There is a URL and port for backend and frontend widgets that also would need 
to be reachable by your client and not just the main portal front end.  The 
port will need to be a nodePort and in Amsterdam I don’t believe they are 
because within the VNC pod the internal ports are resolvable.

Thanks,
Mandeep

From:  on behalf of Pavithra R13 

Date: Wednesday, June 13, 2018 at 2:49 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] ONAP Portal access from outside

Hi All,

I have installed Kubernetes based ONAP Amsterdam this week on a Ubuntu server. 
I am able to access the Portal and the SDC/VID/Policy components from the ONAP 
Ubuntu server. But when I try to access the portal from a different desktop 
which is in the same subnet of ONAP server , I am able to access only the ONAP 
portal ,the other components are not accessible . Kindly let me know how to 
access the portal components from other servers.

Note: I have made host entry of the portal apps container and other containers 
in ONAP server and portal container . I am accessing the portal directly using 
portal apps container and not through VNC portal.

Please find attached screenshot for the portal pods.

Regards
Pavithra R
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] [oom] [aai] Resources fails to start

[Mandeep Khinda]

Using today’s everything (helm charts, docker images) I am not seeing the same 
problem in my multi-node k8s cluster:

root@aai-resources:/opt/app/aai-resources# ping dev-aai-cassandra-0
PING dev-aai-cassandra-0.rancher.internal (10.42.62.210) 56(84) bytes of data.
64 bytes from 10.42.62.210: icmp_seq=1 ttl=62 time=0.428 ms
64 bytes from 10.42.62.210: icmp_seq=2 ttl=62 time=0.226 ms
^C
--- dev-aai-cassandra-0.rancher.internal ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 0.226/0.327/0.428/0.101 ms
root@aai-resources:/opt/app/aai-resources# ping dev-aai-cassandra-1
PING dev-aai-cassandra-1.rancher.internal (10.42.26.92) 56(84) bytes of data.
64 bytes from 10.42.26.92: icmp_seq=1 ttl=64 time=0.065 ms
^C
--- dev-aai-cassandra-1.rancher.internal ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.065/0.065/0.065/0.000 ms
root@aai-resources:/opt/app/aai-resources# ping dev-aai-cassandra-2
PING dev-aai-cassandra-2.rancher.internal (10.42.57.146) 56(84) bytes of data.
64 bytes from 10.42.57.146: icmp_seq=1 ttl=62 time=0.559 ms
^C
--- dev-aai-cassandra-2.rancher.internal ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.559/0.559/0.559/0.000 ms

Each SS instance is on a different K8s node too.
kubectl get pods -o=wide|grep aai-cass
dev-aai-cassandra-0 1/1   Running   0  
1h10.42.62.210k8s-5
dev-aai-cassandra-1 1/1   Running   0  
1h10.42.26.92 k8s-10
dev-aai-cassandra-2 1/1   Running   0  
1h10.42.57.146k8s-4


From:  on behalf of Borislav Glozman 

Date: Thursday, May 10, 2018 at 12:15 PM
To: Daniel Silverthorn , 
"onap-discuss@lists.onap.org" , Steven Blimkie 
, "jf2...@att.com" 
Subject: Re: [onap-discuss] [oom] [aai] Resources fails to start

Hi,

Same problem here.
Did anyone manage to resolve this?

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of 
ONAP

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Daniel Silverthorn
Sent: Monday, April 23, 2018 5:40 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [oom] [aai] Resources fails to start

Using the latest oom as of Friday, I am able to start aai on a single node k8s 
cluster, but when trying it on a multimode cluster, resources fails to start up 
with the following error:

Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
at 
org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:594)
Caused by: java.lang.ExceptionInInitializerError
at org.onap.aai.dbmap.AAIGraph.getInstance(AAIGraph.java:98)
at org.onap.aai.dbgen.GenTester.main(GenTester.java:118)
... 8 more
Caused by: java.lang.RuntimeException: Failed to instantiate graphs
at org.onap.aai.dbmap.AAIGraph.(AAIGraph.java:83)
at org.onap.aai.dbmap.AAIGraph.(AAIGraph.java:55)
at org.onap.aai.dbmap.AAIGraph$Helper.(AAIGraph.java:88)
... 10 more
Caused by: java.lang.IllegalArgumentException: Could not instantiate 
implementation: 
org.janusgraph.diskstorage.cassandra.astyanax.AstyanaxStoreManager
at 
org.janusgraph.util.system.ConfigurationUtil.instantiate(ConfigurationUtil.java:69)
at 
org.janusgraph.diskstorage.Backend.getImplementationClass(Backend.java:477)
at 
org.janusgraph.diskstorage.Backend.getStorageManager(Backend.java:409)
at 
org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration.(GraphDatabaseConfiguration.java:1376)
at 
org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:164)
at 
org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:133)
at 
org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:113)
at org.onap.aai.dbmap.AAIGraph.loadGraph(AAIGraph.java:110)
at org.onap.aai.dbmap.AAIGraph.(AAIGraph.java:80)
... 12 more
Caused by: 

Re: [onap-discuss] [onap-discuss[[oom[[portal]

[Mandeep Khinda]

Hi Hector,
For the Beijing release on OOM  the VNC pod was obsoleted in favour of direct 
client side access.

I captured some notes on it in the link below after a couple of questions on 
usage have come my way.
https://wiki.onap.org/display/DW/2018/05/09/Accessing+ONAP+Portal+using+OOM+and+a+Kubernetes+Cluster

Let me know if that doesn’t work or if you have any other questions.
Mandeep

From:  on behalf of "ANAPAN-LAVALLE, 
HECTOR A" 
Date: Wednesday, May 9, 2018 at 3:22 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [onap-discuss[[oom[[portal]

Hi,

Trying to deploy an ONAP Portal (Amsterdam release) deployment on a 
Rancher/7-node K8S cluster, and the vnc-console does not start and stays in the 
“CrashLoopBackOff” State.

Exec lifecycle hook ([/bin/sh -c mkdir -p /root/.mozilla/firefox/onap.default; 
cp /root/.init_profile/profiles.ini /root/.mozilla/firefox/; echo 
'user_pref("browser.tabs.remote.autostart.2", false);' > 
/root/.mozilla/firefox/onap.default/prefs.js; cat /ubuntu-init/hosts >> 
/etc/hosts]) for Container "vnc-portal" in Pod 
"vnc-portal-7bd4ddd978-k6v4x_onap-portal(877dede2-53b3-11e8-8933-02cc6f206a12)" 
failed - error: command '/bin/sh -c mkdir -p 
/root/.mozilla/firefox/onap.default; cp /root/.init_profile/profiles.ini 
/root/.mozilla/firefox/; echo 'user_pref("browser.tabs.remote.autostart.2", 
false);' > /root/.mozilla/firefox/onap.default/prefs.js; cat /ubuntu-init/hosts 
>> /etc/hosts' exited with 1: cat: /ubuntu-init/hosts: No such file or 
directory , message: "cat: /ubuntu-init/hosts: No such file or directory\n"

Has anybody come across/know how why this error is happening?

Thanks,
Hector
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] [oom][sdc] SDC-ES pod not reaching running state

[Mandeep Khinda]

I am having the same issue.  I just raised 
https://jira.onap.org/browse/SDC-1259 to track the resolution.

From:  on behalf of bharath thiruveedula 

Date: Tuesday, April 24, 2018 at 1:31 PM
To: Michael O'Brien , "onap-discuss@lists.onap.org" 
, "david.sauvag...@bell.ca" 

Subject: [onap-discuss] [oom][sdc] SDC-ES pod not reaching running state


Hi ,



I am trying to launch ONAP using OOM master branch. I am facing errors to make 
dev-sdc-es pod in running state. I can see the following error in the log

"FATAL: NoMethodError: undefined method 'each' for "dev-sdc-es.onap": String"



Let me know if you need more info from me.



Best Regards

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

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

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

Re: [onap-discuss] [onap-tsc] ONAP-OOM Deployment Error

[Mandeep Khinda]

Hi Pulkit,
The OOM team noticed this and created a defect to track the fix which is 
currently a top priority and has a gerrit review outstanding.  I believe it 
will be wrapped up and merged today.
https://jira.onap.org/browse/OOM-858

The root cause is this: portal has a sql file that is extremely large because 
it contains images (binary data).
This is exhausting the config map space so we have removed it and found an 
alternate way of injecting it in the portals db instantiation.  The fix can 
also be used to reduce other config maps that really do not need to be part of 
the helm package.  This was important to us to ensure that it is not just a 
band-aid fix specific to one app.

Mandeep


Begin forwarded message:

From: Pulkit Walia >
Subject: [onap-tsc] ONAP-OOM Deployment Error
Date: April 6, 2018 at 6:35:06 AM EDT
To: "onap-discuss@lists.onap.org" 
>, 
"onap-...@lists.onap.org" 
>, 
"onap-...@lists.onap.org" 
>

Hi All,

I need some help related to ONAP Deployment.
I am trying to deploy ONAP on VMware Integrated OpenStack 4.0 with Kubernetes 
and I have been facing an error with it.

I am using the following for ONAP deployment:


  *   VMware Integrated OpenStack 4.0 with Kubernetes
  *   Helm v2.7.0
  *   Kubectl v1.7.0
  *   ONAP-OOM Repository http://gerrit.onap.org/r/oom

I enabled all the components as true in the oom/kubernetes/onap/values.yaml 
file except the portal component, it was disabled.
During this configuration, the deployment was successful using Helm.

But the problem arises when I enable portal component as true in the yaml file. 
The deployment is unsuccessful and I get the following error:


[cid:image001.png@01D3CDBD.925D2FD0]

In the above screenshot, after a successful deployment I am upgrading the 
deployment after enabling the portal component in the yaml file. After that, 
“data: Too Long: …” error is triggered always, in all the versions of Helm.
I think the portal components is flooding the Kubernetes ConfigMap with large 
amount of data that it is unable to handle.

The kubectl and helm version screenshot is as follows:


[cid:image002.png@01D3CDBF.0A9B16A0]


I have a few doubts/questions regarding this, they are as follows:


  *   Is this a known issue in ONAP Deployment?
  *   Is the portal component responsible for this error?
  *   Is this an issue related to Helm v2.7.x?
  *   Is this an issue related to Kubectl Version?
  *   Is this caused due to VMware Integrated OpenStack with Kubernetes 4.0?
  *   Is this caused due to lack of RAM in the Master and Worker Node Instances 
? (Right now, each of the instance has 32 vCPUs, 128 GB RAM, 256 GB Size)
  *   If not due to one of the reasons above, then what is the cause of this 
error?

It will be really helpful if someone from the ONAP Community can put some of 
their suggestions on this, or someone who has faced the same issue and knows 
the solutions to this error.

Thank You and Regards,
Pulkit Walia

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


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] [OOM] 20180214: Agenda proposal - weekly OOM meet - discuss AAI cassandra clustering PV on openstack issue

[Mandeep Khinda]

I can speak to the SDN-C work as I have tested it out when it was being done 
(This already might be known information but here it is anyways…)

The way the replica set’s DNS resolution was done is through a k8s service 
called “sdnhost-cluster”
https://gerrit.onap.org/r/#/c/25467/23/kubernetes/sdnc/templates/all-services.yaml

Then any pod running in k8s should be able to reach any of the replicas using a 
well known host name suffixed by the replica number..like this:
{"ip": "sdnc-0.sdnhost-cluster", "port": "8181"},
{"ip": "sdnc-1.sdnhost-cluster", "port": "8181"},
{"ip": "sdnc-2.sdnhost-cluster", "port": "8181"}



Mandeep Khinda
Software Development
Open Network Division

+1.613.595.5132 (office)

[ocs-a]

Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs blog 
network<http://blogs.amdocs.com/> – and follow us on 
Facebook<http://www.facebook.com/Amdocs>, Twitter<http://twitter.com/Amdocs>, 
LinkedIn<http://www.linkedin.com/company/amdocs> and 
YouTube<http://www.youtube.com/amdocs>.


From: <onap-discuss-boun...@lists.onap.org> on behalf of Michael O'Brien 
<frank.obr...@amdocs.com>
Date: Tuesday, February 13, 2018 at 10:32 AM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] [OOM] 20180214: Agenda proposal - weekly OOM meet - 
discuss AAI cassandra clustering PV on openstack issue

Team,
   I have added a proposed agenda item to the OOM meeting
   To continue work with the AAI team to help resolve an openstack specific PV 
issue occurring during Cassandra scale out that is causing issues with DNS.  We 
have been meeting a couple times separately, we will bring this working session 
into half the OOM meet tomorrow to get the opinion of DNS and PV experts and 
developers involved in the SDNC cluster POC – from the onap community and the 
larger OOM team.

https://zoom.us/j/118908904
https://wiki.onap.org/display/DW/OOM+Meeting+Notes+-+2018-02-14

See video prep in the last comment on
https://jira.onap.org/browse/OOM-591
https://jira.onap.org/browse/AAI-539

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
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 
<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] [OOM] restart an entire POD ?

[Mandeep Khinda]

One negative to deleteAll and our helm charts in their current incarnation is 
that it deletes everything in the namespace including services (Pod and cluster 
IPs will change when they come back), database processes etc (not the persisted 
data).  

If you are impatient like I am, I target just the deployment I want to bounce 
by exporting the current running yaml and then following something similar to 
the link Josef had sent.

For example: This is what I would use to bounce just the SO Jboss container:
kubectl -n onap-mso get deployment mso -o=yaml > /tmp/mso.app.yaml
kubectl -n onap-mso delete -f /tmp/mso.app.yaml
kubectl -n onap-mso create -f /tmp/mso.app.yaml


Mandeep Khinda
Software Development
Open Network Division
 
+1.613.595.5132 (office)
 

 
Read the latest on Amdocs.com <http://www.amdocs.com/> and the Amdocs blog 
network <http://blogs.amdocs.com/> – and follow us on Facebook 
<http://www.facebook.com/Amdocs>, Twitter <http://twitter.com/Amdocs>, LinkedIn 
<http://www.linkedin.com/company/amdocs> and YouTube 
<http://www.youtube.com/amdocs>. 
 

On 2018-02-07, 10:00 AM, "onap-discuss-boun...@lists.onap.org on behalf of 
FREEMAN, BRIAN D" <onap-discuss-boun...@lists.onap.org on behalf of 
bf1...@att.com> wrote:

OK

I assume deleteAll.sh does not remove the dockernfs so persistant data 
should not be lost just any "fixes" to the container config.

I can work with that.

Brian


-Original Message-
From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
Sent: Wednesday, February 07, 2018 9:56 AM
To: FREEMAN, BRIAN D <bf1...@att.com>
Cc: onap-discuss@lists.onap.org; Mike Elliott <mike.elli...@amdocs.com>
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

Hi Brian,

Those issues are tracked in JIRA already. Adding Mike that is looking at it 
(I think).

About your question, you cannot do this through K8S UI; at least, not that 
I’m aware of.
But using our scripts, you can delete and create a specific app.

For instance:
./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the 
whole AAI namespace (deployment and services)
./oom/kubernetes/oneclick/createAll.sh -n onap -a aai <— will create the 
whole AAI namespace (deployment and services)

I’m not sure this is what you’re after, but that’s how I do it when I need 
to bounce a whole application (e.g. all the containers of an app).

Alexis

> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote:
> 
> Michael, Alexi,
> 
> I'm having race conditions when I use OOM in Azure where the health check 
passes but distribution fails (MSO and AAI never get notified).
> 
> I restarted the SO front end POD and SO successfully picked up a model 
distribution.
> 
> I tried to restart just the AAI Model loader but that didnt seem to work 
so I need to restart all of AAI
> 
> I suspect that SO and AAI came up before DMaaP was up but cant confirm 
that.
> 
> Is there an easy / safe way to do restart an entire domain through the K8 
portal ?
> 
> Feel free to point me at the right documentation on the wiki if I am just 
missing that guidance.
> 
> Brian
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=-pj2hS0sQHfti5uKrngRGpvwXRLbxAppOnyPro6DGyA=f7jUNSvpSscVwuhbekP_wy4_NKgR99_Iu8pYxQF4-Y0=
 

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


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 
<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] OOM Installation Problem | Unable to bring up Portal Pod

[Mandeep Khinda]

Hi Karthik,
Can you share some more output from your k8s cluster (in a text format if 
possible)

kubectl -n onap-portal get events|grep portalapps

This will show the events that took place and hopefully the reason why it is 
stuck at initializing.  In my experience it is usually image pulling issues 
and/or k8s cluster resource limits are maxed out.


Mandeep Khinda
Software Development
Open Network Division

+1.613.595.5132 (office)

[ocs-a]

Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs blog 
network<http://blogs.amdocs.com/> – and follow us on 
Facebook<http://www.facebook.com/Amdocs>, Twitter<http://twitter.com/Amdocs>, 
LinkedIn<http://www.linkedin.com/company/amdocs> and 
YouTube<http://www.youtube.com/amdocs>.


From: <onap-discuss-boun...@lists.onap.org> on behalf of Karthik 
<sdkarth...@gmail.com>
Date: Tuesday, January 9, 2018 at 10:18 AM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] OOM Installation Problem | Unable to bring up Portal Pod


Hi Team , Good day !

I followed the Quick 
Installation<https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation>
 steps to install ONAP.  All pods are up and running except "Portal".I tried 
multiple times to bring up  "Portal" pod , but  could not able to solve the 
problem . "portalapps", "vnc-portal" are keep on hangs with 
Waiting:PodInitializing status. I have attached the log and status images . 
Please refer it and reply to me if you could help me in this problem.
Environment Details:
Ubuntu 16, RAM 50 GB.

Thanks in Advance.

Regards,
Karthik.

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 
<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] [dcae] dcaegen2 bootstrap help: sanity deployment?

[Mandeep Khinda]

Hi,
I’ve been trying to bootstrap dcaegen2 using OOM on the side in my own 
environment.
After following the Openstack Designate e-mail thread and getting that 
installed locally the bootstrap gets much further – thanks for that info!

I have 1 VM spawned “ onapr1orcl00   CentOS-7-x86_64-GenericCloud” that 
has an interface and a floating IP which seems good but the process fails 
eventually at the “sanity” deployment with the log below.

2017-10-18 15:16:51 CFY  [sanity_388d0] Starting operation 
cloudify.interfaces.lifecycle.start (Operation parameters: {'manager_ip': 
u'10.53.202.107', 'run_sanity': 'true', 'fabric_env': {'key_filename': 
u'/opt/app/installer/cmtmp/cmbootstrap/id_rsa.cfybootstrap', 'host_string': 
u'10.53.202.107', 'user': u'centos'}})
2017-10-18 15:16:52 CFY  [sanity_388d0.start] Sending task 
'fabric_plugin.tasks.run_script'
2017-10-18 15:16:52 CFY  [sanity_388d0.start] Task started 
'fabric_plugin.tasks.run_script'
2017-10-18 15:16:52 LOG  [sanity_388d0.start] INFO: Preparing fabric 
environment...
2017-10-18 15:16:52 LOG  [sanity_388d0.start] INFO: Environment 
prepared successfully
2017-10-18 15:16:52 LOG  [sanity_388d0.start] INFO: Saving sanity 
input configuration to /opt/cloudify/sanity/node_properties/properties.json
2017-10-18 15:16:53 LOG  [sanity_388d0.start] INFO: Starting Manager 
sanity check...
[10.53.202.107] out: Timed out while waiting for deployment sanity_deployment 
to be created
[10.53.202.107] out: Traceback (most recent call last):
[10.53.202.107] out:   File 
"/tmp/cloudify-ctx/scripts/tmp8pKuMU-sanity.py-8O2V1F5M", line 276, in 
[10.53.202.107] out: perform_sanity()
[10.53.202.107] out:   File 
"/tmp/cloudify-ctx/scripts/tmp8pKuMU-sanity.py-8O2V1F5M", line 259, in 
perform_sanity
[10.53.202.107] out: _prepare_sanity_app()
[10.53.202.107] out:   File 
"/tmp/cloudify-ctx/scripts/tmp8pKuMU-sanity.py-8O2V1F5M", line 36, in 
_prepare_sanity_app
[10.53.202.107] out: _deploy_app()
[10.53.202.107] out:   File 
"/tmp/cloudify-ctx/scripts/tmp8pKuMU-sanity.py-8O2V1F5M", line 87, in 
_deploy_app
[10.53.202.107] out: 'deployment {0} to be created'.format(DEPLOYMENT_ID))
[10.53.202.107] out:   File "/tmp/cloudify-ctx/scripts/utils.py", line 725, in 
repetitive
[10.53.202.107] out: ctx.abort_operation(timeout_msg)
[10.53.202.107] out:   File "/tmp/cloudify-ctx/cloudify.py", line 234, in 
abort_operation
[10.53.202.107] out: subprocess.check_call(cmd)
[10.53.202.107] out:   File "/usr/lib64/python2.7/subprocess.py", line 542, in 
check_call
[10.53.202.107] out: raise CalledProcessError(retcode, cmd)
[10.53.202.107] out: subprocess.CalledProcessError: Command '['ctx', 
'abort_operation', 'Timed out while waiting for deployment sanity_deployment to 
be created']' returned non-zero exit status 1
[10.53.202.107] out:

Fatal error: run() received nonzero return code 1 while executing!

Requested: source /tmp/cloudify-ctx/scripts/env-tmp8pKuMU-sanity.py-8O2V1F5M && 
/tmp/cloudify-ctx/scripts/tmp8pKuMU-sanity.py-8O2V1F5M
Executed: /bin/bash -l -c "cd /tmp/cloudify-ctx/work && source 
/tmp/cloudify-ctx/scripts/env-tmp8pKuMU-sanity.py-8O2V1F5M && 
/tmp/cloudify-ctx/scripts/tmp8pKuMU-sanity.py-8O2V1F5M"

Aborting.
2017-10-18 15:17:13 CFY  [sanity_388d0.start] Task failed 
'fabric_plugin.tasks.run_script' -> Timed out while waiting for deployment 
sanity_deployment to be created
2017-10-18 15:17:13 CFY  'execute_operation' workflow execution 
failed: Workflow failed: Task failed 'fabric_plugin.tasks.run_script' -> Timed 
out while waiting for deployment sanity_deployment to be created
Bootstrap failed! (Workflow failed: Task failed 
'fabric_plugin.tasks.run_script' -> Timed out while waiting for deployment 
sanity_deployment to be created)
Executing teardown due to failed bootstrap...
2017-10-18 15:17:13 CFY  Starting 'uninstall' workflow execution


I can connect to the VM that spun up and see some sanity files and directories 
but no logs.

[root@onapr1orcl00 sanity]# pwd
/opt/cloudify/sanity
[root@onapr1orcl00 sanity]# ls
node_properties  resources
[root@onapr1orcl00 sanity]# ls node_properties/
properties.json
[root@onapr1orcl00 sanity]# ls resources/
cloudify-hello-world-example-3.4.tar.gz  __resources.json
[root@onapr1orcl00 sanity]#

Has anyone else gotten past this part of the bootstrap?  Any idea what I can do 
to troubleshoot further?
I can see that it is trying to do an HTTP request to somewhere to startup the 
sanity service but have no idea to where it is going or what the HTTP content 
is.

 61 def _deploy_app():
 62 if _is_sanity_dep_exist(should_fail=True):
 63 return
 64
 65 dep_inputs = {'server_ip': manager_ip,
 66   'agent_user': manager_user,
 67   'agent_private_key_path': manager_remote_key_path}
 68 data = {
 69 'blueprint_id': BLUEPRINT_ID,
 70 'inputs': dep_inputs
 71 }
 72 headers = 

Re: [onap-discuss] ONAP on K8S+Rancher

[Mandeep Khinda]

Hi Srini,
There are 2 ways launch robot in OOM.

1.   One is from your local environment that uses your kubectl 
configuration to route into the K8s env:
oom/kubernetes/config/docker/init/src/config/robot/ete-k8s.sh[demo-k8s.sh]

2.   The other is from wherever your /dockerdata-nfs share mount lands 
which uses the docker daemon directly.  This one is problematic if you have a 
K8s cluster with more than 1 host.  Then you will have to run this from the 
host where the robot pod was scheduled on.
/dockerdata-nfs/onap/robot/ete-docker.sh[demo-docker.sh]

These will work out of the box IF you used “onap” as your namespace prefix (the 
default).  If you set something else then you will unfortunately need to 
locally modify the file temporarily from “--namespace onap-robot” to 
“--namespace [YOUR-NAMESPACE]-robot”

I tend to use the k8s.sh version that uses kubectl as I have a cluster of 3 K8s 
hosts.

Mandeep
--


From:  on behalf of Srinivasa Goda 

Date: Thursday, September 21, 2017 at 10:46 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] ONAP on K8S+Rancher


Hi All,



I've another question on ONAP on K8S+Rancher. For service instantiation, I need 
to run demo.sh in robot container. However, demo.sh script is referring to a 
container named 'openecompete_container'. But I don't see that container in 
only host running ONAP. Am I missing something or is there an issue around it?



Thanks,

Srini


[eta Tester Badge 3]
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] config pod changes

[Mandeep Khinda]

OOM users,
I’ve just pushed a change that requires a re-build of the /dockerdata-nfs/onap/ 
mount on your K8s host.

Basically, what I’ve tried to do is port over the heat stack version of ONAPs 
configuration mechanism.  The heat way of running ONAP writes files to 
/opt/config/ based on the stack’s environment file that has the details related 
to each users environment.  These values are then swapped in to the various VMs 
containers using scripts.

Now that we are using helm for OOM, I was able to do something similar in order 
to start trying to run the vFW/vLB demo use cases.
This story tracks the functionality that was needed: 
https://jira.onap.org/browse/OOM-277

I have also been made aware that this change requires K8s 1.6 as I am making 
use of the “envFrom”  
https://kubernetes.io/docs/api-reference/v1.6/#container-v1-core.  We stated 
earlier that we are setting minimum requirements of K8s 1.7 and rancher 1.6 for 
OOM so hopefully this isn’t a big issue.

It boils down to this:
/oom/kubernetes/config/onap-parameters.yaml is kind of like file 
“onap_openstackRC.env” and you will need to define some required values 
otherwise the config pod deployment will fail.

A sample can be found here:
/oom/kubernetes/config/onap-parameters-sample.yaml
Note: If you don’t care about interacting with openstack to launch VNFs then, 
you can just use the sample file contents.

continue to run createConfig.sh –n onap and it will install the config files 
and swap in your environment specific values before it completes.

createAll.bash –n onap to recreate your ONAP K8s environment and go from there.

Thx,
Mandeep
--

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] [OOM] Kubernetes version to be used as reference

[Mandeep Khinda]

FYI. I just updated my local lab and confirm some versions as of today:

rancher/server:stable = >
Component  Version
Rancher v1.6.7
Cattle v0.183.5
User Interface v1.6.17
Rancher CLI  v0.6.3
Rancher Compose  v0.12.5

The kubernetes stack template that it comes with this version of rancher is: 
1.7.2

Mandeep
--


From:  on behalf of Jerome Doucerain 

Date: Thursday, August 17, 2017 at 5:21 PM
To: Roger Maitland , "onap-discuss@lists.onap.org" 

Subject: Re: [onap-discuss] [OOM] Kubernetes version to be used as reference


Hi Roger

Yes exactly Rancher v1.6.6+ and Kubernetes 1.7.2+
​that's what I had in mind.

Thanks

Jerome


 Original message 
From: Roger Maitland 
Date: 2017-08-17 11:35 AM (GMT-05:00)
To: "Doucerain, Jerome" , onap-discuss@lists.onap.org
Subject: RE: [OOM] Kubernetes version to be used as reference
Hi Jerome,

In general I strongly support going to the latest stable version at the 
beginning of a project like this one.

To refine this a bit, Rancher seems to be a popular choice for management of 
the infrastructure and it is heavily integrated to Kubernetes so we should 
consider it too.  The Rancher v1.6.6 release notes 
  state that Kubernetes 
1.7.2 is supported; are you recommending Rancher v1.6.6+ and Kubernetes 1.7.2+?

Thanks,
Roger

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Doucerain, Jerome
Sent: Wednesday, August 16, 2017 1:19 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [OOM] Kubernetes version to be used as reference


Hi,



as we are using kubernetes to run ONAP containers, we are developing kubernetes 
manifests to describe the resources required by the ONAP components and the 
environment where we are running them on.



Some kubernetes resources we are referring to in the manifests are valid only 
in some kubernetes versions or the way to refer to those resources is specific 
to particular versions, taking into account the evolution as the kubernetes API.



So to keep the valuable material the community is bringing valid as long as 
possible, and as we are at the beginning of the ONAP on kubernetes story, my 
proposal would be to try to start with the most recent stable version of 
kubernetes (i.e. 1.7) and base the kubernetes manifests on the version 1.7 API 
reference.



It will also allow us to use the latest features of kubernetes to operate ONAP.



Could you please give some feedback on that.



Thanks



Jerome


Jerome Doucerain
Sr Consultant - System Architecture
Bell Business Markets
671, LaGauchetière Ouest, 5e
Montréal (Québec) H3B 2M8
Office : 514 870-6392
jerome.doucer...@bell.ca
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 

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

Re: [onap-discuss] [installation] Updated Heat templates for vanilla OpenStack

[Mandeep Khinda]

Hi Marco,
Do these include the openstack-ization of the DCAE VMs?  Last I remember, those 
were a work in progress.
Thx
Mandeep

From:  on behalf of "PLATANIA, MARCO 
(MARCO)" 
Date: Monday, May 8, 2017 at 3:05 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [installation] Updated Heat templates for vanilla 
OpenStack

Hello all,

Gerrit demo repo contains an updated set of Heat templates to install ONAP in 
vanilla OpenStack. Please check here:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/OpenECOMP;h=b191dadd58edbe261c860adb649acdfd8e7c8b0f;hb=refs/heads/master


  1.  onap_openstack.yaml / onap_openstack.env: ONAP VMs created out of this 
template have one vNIC. The vNIC has a private IP towards the Private 
Management Network and a floating IP. The floating IPs addresses are assigned 
during ONAP installation by OpenStack, based on floating IP availability. This 
template can be used when users do not know the set of floating IPs assigned to 
them. Note that this template should be used in OpenStack Kilo and older 
releases, because those releases do not support fixed floating IP association 
via Heat template.
  2.  onap_openstack_float.yaml / onap_openstack_float.env: ONAP VMs created 
out of this template have one vNIC. The vNIC has a private IP towards the 
Private Management Network and a floating IP. The floating IPs addresses are 
specified ahead of time in the environment file. This template can be used when 
users always want to assign the same floating IP to an ONAP VM in different 
ONAP installation. Note that fixed floating IP assignment via Heat template is 
not supported in OpenStack Kilo and older releases.
  3.  onap_openstack_nofloat.yaml / onap_openstack_nofloat.env: ONAP VMs 
created out of this template have two vNICs: one has a private IP towards the 
Private Management Network and the other one has a public IP address towards 
the external network. From a network resource perspective, this template is 
similar to the Heat template used to build ONAP in Rackspace.

Templates at point 2 are the ones previously named onap_openstack_RC.yaml and 
onap_openstack_RC.env, the content is the same.

For a detailed description of ONAP installation in vanilla OpenStack, please 
refer to the wiki page: 
https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack

Thanks,
Marco
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