diff options
author | Sridhar K. N. Rao <sridhar.rao@spirent.com> | 2019-10-18 14:35:14 +0530 |
---|---|---|
committer | Kaspars Skels <kaspars.skels@att.com> | 2019-10-28 17:44:13 -0500 |
commit | 799182f0c40730e41253dc5c861857d219291c3b (patch) | |
tree | 5138ae74cbbffb8aaf47929d063254c0043773d5 /site/intel-pod10/software/charts/osh/openstack-compute-kit/neutron.yaml | |
parent | c053e71f295dc91ee60bbdcbcf99d909923af3b0 (diff) |
Site definition for Intel Pod-10
This patch adds site definition for Intel Pod-10.
Updated publickeys of luc and trevor
Updated site-definition
Updated divingbell
Modifying common parts - FOR TESTING ONLY - Will be removed
Trying with only 1 disk (bootdisk)
Trying with 2 disks - /dev/sda as bootdisk, /dev/sdb as datadisk
Change ceph config from directory to /dev/sdb (OSD-data only)
Change ceph config from directory to /dev/sdb (OSD-Journl too)
Reduce footprint of osh-infra (reduce disk pressure)
Move ceph to site specific manifests
Fix pod10 host/hardware profiles to be site local
Fix Nova/Neutron parts to be site local
Fix glance cirros image pull
Fix type to site layer names for moved files
Rename pod10 hardware/host profiles
Move ceph fully to /dev/sdb
Disable SR-IOV configuration
Optimize disk storage for Nova VMs (use root disk or 3T)
Signed-off-by: Sridhar K. N. Rao <sridhar.rao@spirent.com>
Change-Id: I2160e56744917510d4627cefca32031904188f77
Diffstat (limited to 'site/intel-pod10/software/charts/osh/openstack-compute-kit/neutron.yaml')
-rw-r--r-- | site/intel-pod10/software/charts/osh/openstack-compute-kit/neutron.yaml | 72 |
1 files changed, 72 insertions, 0 deletions
diff --git a/site/intel-pod10/software/charts/osh/openstack-compute-kit/neutron.yaml b/site/intel-pod10/software/charts/osh/openstack-compute-kit/neutron.yaml new file mode 100644 index 0000000..38e3cd3 --- /dev/null +++ b/site/intel-pod10/software/charts/osh/openstack-compute-kit/neutron.yaml @@ -0,0 +1,72 @@ +--- +# This file defines hardware-specific settings for neutron. If you use the same +# hardware profile as this environment, you should not need to change this file. +# Otherwise, you should review the settings here and adjust for your hardware. +# In particular: +# 1. logical network interface names +# 2. physical device mappigns +# TODO: Should move to global layer and become tied to the hardware profile +schema: armada/Chart/v1 +metadata: + schema: metadata/Document/v1 + replacement: true + name: neutron + layeringDefinition: + abstract: false + layer: site + parentSelector: + name: neutron-global + actions: + - method: merge + path: . + storagePolicy: cleartext +data: + wait: + timeout: 1800 + test: + timeout: 900 + # values: + # labels: + # sriov: + # node_selector_key: sriov + # node_selector_value: enabled + # pod: + # security_context: + # neutron_sriov_agent: + # pod: + # runAsUser: 42424 + # container: + # neutron_sriov_agent_init: + # privileged: true + # runAsUser: 0 + # readOnlyRootFilesystem: false + # neutron_sriov_agent: + # readOnlyRootFilesystem: true + # privileged: true + # network: + # interface: + # sriov: + # - device: eno4 + # num_vfs: 32 + # promisc: false + # backend: + # - openvswitch + # - sriov + # conf: + # plugins: + # ml2_conf: + # ml2: + # mechanism_drivers: l2population,openvswitch,sriovnicswitch + # ml2_type_vlan: + # ## NOTE: Must have at least 1 sriov network defined + # network_vlan_ranges: external,sriovnet1:100:4000 + # sriov_agent: + # securitygroup: + # firewall_driver: neutron.agent.firewall.NoopFirewallDriver + # sriov_nic: + # ## NOTE: Must have at least 1 sriov network to physical device + # ## mapping, otherwise sriov agent readiness check + # ## will fail. + # physical_device_mappings: sriovnet1:eno4 + # exclude_devices: "" +... |