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=
GLOBAL_INJECTED_KEYSTONE = "{{ .Values.openStackKeyStoneUrl }}"

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

  enabled: true
  demoArtifactsVersion: "1.2.0-SNAPSHOT"
  openStackPrivateNetCidr: ""
  openStackFlavourMedium: "m1.medium"
  openStackKeyStoneUrl: "";
  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 is coming from.

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


From: <> on behalf of "FREEMAN, BRIAN D" 
Date: Thursday, April 12, 2018 at 4:39 PM
To: "''" <>
Subject: [onap-discuss] [OOM] - correct vm_properties in SB06 in SB06 arent right. Openstack is pointing to 

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

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

you may review at 
onap-discuss mailing list

Reply via email to