DHCP is working again so instances are getting their addresses. For some reason
cloud-init isn't working correctly. Hostnames aren't getting set, and SSH key
pair isn't getting set. The neutron-metadata service is in control of this?
neutron-metadata-agent.log:
2018-07-10 08:01:42.046 5518 INFO
What is the proper way to use NetConfigDataLookup? I tried the following:
(undercloud) [stack@oscloud5 ~]$ cat << '__EOF__' >
~/templates/mapping-info.yaml
parameter_defaults:
NetConfigDataLookup:
control1:
nic1: '5c:f3:fc:36:dd:68'
nic2: '5c:f3:fc:36:dd:6c'
nic3:
Data retained after deletion of a ScaleIO volume
---
### Summary ###
Certain storage volume configurations allow newly created volumes to
contain previous data. This could lead to leakage of sensitive
information between tenants.
### Affected Services / Software ###
Cinder releases up to and incl
There has been some work on this [2], but it didn't make it into the
Kilo release (abandoned), and I don't see it either in later releases.
[2]
https://blueprints.launchpad.net/nova/+spec/selecting-subnet-when-creating-vm
Zitat von Hang Yang :
Hi there,
I have one question about choosin
Hi,
depending on your workflow there would be a way with scripting [0],
not sure if this would be a suitable approach for you.
There also has been a blueprint [1] for the selection of subnets
during instance creation since Juno, but I can't find anything about
an implementation.
Regards,
