Hi team,
Please find an initial draft of our virtual ptg on Thursday at
https://etherpad.openstack.org/p/publiccloud-atlanta-ptg , feel free to add
anything that you want to discuss
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Excerpts from Jeremy Stanley's message of 2017-02-20 20:08:00 +:
> On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote:
> > What exactly is the security concern of the metadata service? Perhaps
> > those concerns can be addressed directly?
> [...]
>
> A few I'm aware of:
>
Thanks!
> 1.
On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote:
> What exactly is the security concern of the metadata service? Perhaps
> those concerns can be addressed directly?
[...]
A few I'm aware of:
1. It's something that runs in the control plane but needs to be
reachable from untrusted server
What exactly is the security concern of the metadata service? Perhaps
those concerns can be addressed directly?
I ask because anything that requires special software on the guest is
a non-starter IMO. virtio is a Linux thing, so what does this do for
users of Windows? FreeBSD? etc.
Excerpts
We've been having a discussion [1] in openstack-dev about how to best
expose dynamic metadata that changes over a server's lifetime to the
server. The specific use case is device role tagging with hotplugged
devices, where a network interface or volume is attached with a role
tag, and the guest
Hey there,
During the PTG, one of the discussions in the OpenStack-Ansible room was around
adding a monitoring component to OSA. I found the 'osops-tools-monitoring'
repository today.
The idea we discussed was around writing plugins using the OpenStack SDK and
then adding a simple library
Expanding on that, you get that binding error usually when Neutron thinks
it can't wire up the ports on the compute nodes. So ensure that you started
the appropriate Neutron agents on the new compute nodes and that they are
alive by running 'neutron agent-list'.
On Mon, Feb 20, 2017 at 8:14 AM,
Hi,
this 'Unexpected vif_type=binding_failed’ is as well fairly-generic, but you
can change focus from Nova to Neutron+virtual switch.
So check:
-Neutron server logs
-Logs of Neutron agent on target Compute Host(s)
-OVS logs and possibly things like /var/log/messages for things related to
