We really dont want them to be local to the person installing.

We should put them in a known place on the rancher VM at least since that is 
the bootstrap and would be the best place to upgrade if we need to change 
something like I dont know change from pointing to Horizon to pointing to 
MultiVIM for different test scenarios.

Brian


From: Mandeep Khinda [mailto:mandeep.khi...@amdocs.com]
Sent: Thursday, April 12, 2018 5:25 PM
To: FREEMAN, BRIAN D <bf1...@att.com>; 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [OOM] - correct vm_properties in SB06

If the file ended up with defaults then that means no tuning was done at all.
It is a good question.  Perhaps we should start a library of these for the 
environments in the windriver lab in the integration git repo.
Right now each person who is responsible for installing/upgrading the 
environment has config parameters stored locally.
We have some sample files here that can be used as a base in the oom git repo:
oom/kubernetes/onap/resources/environments/disable-allcharts.yaml

If you want to unblock yourself you can do this to tweak robot now:

helm upgrade dev local/onap --namespace onap --set 
robot.openStackKeyStoneUrl=http://4.5.6.7:9998<https://urldefense.proofpoint.com/v2/url?u=http-3A__4.5.6.7-3A9998&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=2XIeOfjBBe17ND0l68a8U3gyqfqzzc1arEDEz5ZXSBc&s=2CI-LoW1LZv6miQz0awPJXJQhgg36M2tt5ey8gcjJhU&e=>,

helm upgrade dev local/onap --namespace onap --set 
robot.openStackKeyStoneUrl=http://4.5.6.7:9998,robot.openStackUserName=brian,robot.foo=bar<https://urldefense.proofpoint.com/v2/url?u=http-3A__4.5.6.7-3A9998-2Crobot.openStackUserName-3Dbrian-2Crobot.foo-3Dbar&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=2XIeOfjBBe17ND0l68a8U3gyqfqzzc1arEDEz5ZXSBc&s=UiN-KwCNXdeCwa4AFt9mrpfSm_rvgj5u7hFVFladsMM&e=>

Or create a file with the params like in my robot example for SB06 and just use 
the same command above except for the --set you would use a -f SB06-values.yaml

The vm_properties file will be updated without a container restart.

From: "FREEMAN, BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>>
Date: Thursday, April 12, 2018 at 5:03 PM
To: Mandeep Khinda 
<mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>, 
"'onap-discuss@lists.onap.org'" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: RE: [onap-discuss] [OOM] - correct vm_properties in SB06

So.... what file was used when Michael et al created SB06 ? Seems like I should 
edit that file and do a helm upgrade in SB06 ?

Where should these be stored in environment so we can edit the file in one 
place for corrections like this that would span re-installs ?

Brian


From: Mandeep Khinda [mailto:mandeep.khi...@amdocs.com]
Sent: Thursday, April 12, 2018 4:47 PM
To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; 
'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [OOM] - correct vm_properties in SB06

Brian,
It is a currently a configmap in the robot chart and isn’t visible on an 
external mount anymore – it is injected into the container only.
The values can be set dynamically at helm install/upgrade through -f 
values.yaml or --set 
openStackKeyStoneUrl=http://4.5.6.7:5000<https://urldefense.proofpoint.com/v2/url?u=http-3A__4.5.6.7-3A5000&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=2WL9pKqMgDC93z23aIUKveTD1Fd_5lYghragfYaJMd4&s=Y6OI0Brm8rHYZNyi6UGFoaS7HJYA8gpHkZc8Z4uGbYE&e=>
GLOBAL_INJECTED_KEYSTONE = "{{ .Values.openStackKeyStoneUrl }}"

For example, I have a file called dev-env.yaml with this content for my own 
environment:

robot:
  enabled: true
  demoArtifactsVersion: "1.2.0-SNAPSHOT"
  openStackPrivateNetCidr: "192.168.2.0"
  openStackFlavourMedium: "m1.medium"
  openStackKeyStoneUrl: 
"http://10.53.202.10:5000";<https://urldefense.proofpoint.com/v2/url?u=http-3A__10.53.202.10-3A5000-2522&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=2WL9pKqMgDC93z23aIUKveTD1Fd_5lYghragfYaJMd4&s=GAVGEkD_gfKJWjxo8QCeay-4m1EXi40Bmf6mnqychR4&e=>
  openStackPublicNetId: "5a88ca9c-7fbb-4232-8d8e-46b53e492de9"
  openStackPrivateNetId: "e8f51956-00dd-4425-af36-045716781ffc"
  openStackOamNetworkCidrPrefix: "10.10.10"
  openStackEncryptedPassword: "2fa2266344b4caaca1eba8264d277831"
  openStackRegion: "RegionOne"
  openStackPrivateSubnetId: "5a3602a5-d708-4096-942d-db741031ade1"
  openStackTenantId: "47899782ed714295b1151681fdfd51f5"
  openStackUserName: "dev"
  ubuntuImage: "Ubuntu_14.04.5_LTS"

This will override the defaults found in the robot chart’s values.yaml which is 
where your 1.2.3.4:5000 is coming from.

We can spend some time on this in the integration meeting tomorrow if you like.

Mandeep

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "FREEMAN, BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>>
Date: Thursday, April 12, 2018 at 4:39 PM
To: "'onap-discuss@lists.onap.org'" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [OOM] - correct vm_properties in SB06

Vm_properties.py in SB06 arent right. Openstack is pointing to 
http:1.2.3.4:5000<https://urldefense.proofpoint.com/v2/url?u=http-3A1.2.3.4-3A5000&d=DwQGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=2WL9pKqMgDC93z23aIUKveTD1Fd_5lYghragfYaJMd4&s=Sto5ykyijGuRXX1_zHvXOnPrG0GXNvJpIXWt7Nc9c80&e=>.

I cant find where the mounted file is – it doesnt seem to be under dockernfs ?

Brian
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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=2WL9pKqMgDC93z23aIUKveTD1Fd_5lYghragfYaJMd4&s=TGJQ_W_lNM94nrmZLEQqnEubaCjm14CL_EUHHE-f9pg&e=>
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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=2XIeOfjBBe17ND0l68a8U3gyqfqzzc1arEDEz5ZXSBc&s=xxyIELuT4TbsS0oV0vEHpMeMjsXDbXJ2CHgw21KfYbw&e=>
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to