On 1/10/2018 1:15 AM, Alec Hothan (ahothan) wrote:
+1 on the “no valid host found”, this one should be at the very top of
the to-be-fixed list.
Very difficult to troubleshoot filters in lab testing (let alone in
production) as there can be many of them. This will get worst with more
NFV optim
Matt,
Thanks for clarifying the logs, the older release I was using did not have much
information in the scheduler log. I’ll double check on the Newton release to
see how they look like.
As you mention, a simple pass/fail result may not always explain why it fails
but it is definitely good to
On 1/10/2018 1:49 PM, Alec Hothan (ahothan) wrote:
The main problem is that the nova API does not return sufficient detail
on the reason for a NoValidHostFound and perhaps that should be fixed at
that level. Extending the API to return a reason field which is a json
dict that is returned by the
Dear Operators,
I have a mix of Mitaka and Pike clusters, all for private clouds, and with
multiple tenants. I am very interested in having the ability to have
per-network (really, per-tenant) dns_domain. You would think that this
works, based on the documentation here:
https://docs.openstack.or
As you’re using a L2 network topology and until all of your project use a
different network you can do:
domain=domain1,10.10.10.0/24
domain=domain2,20.20.20.0/24
Within the dnsmasq-neutron.conf file.
Of course, restart the neutron-server service once done.
Le mer. 10 janv. 2018 à 22:40, Jonathan
Thanks, Flint WALRUS. I will certainly try that.
On Wed, Jan 10, 2018 at 4:57 PM, Flint WALRUS
wrote:
> As you’re using a L2 network topology and until all of your project use a
> different network you can do:
>
> domain=domain1,10.10.10.0/24
> domain=domain2,20.20.20.0/24
>
> Within the dnsmas
That does, indeed, appear to be a solution to the problem. Albeit, not an
ideal solution. I really hope that this will be resolved in Neutron
eventually.
On Wed, Jan 10, 2018 at 5:00 PM, Jonathan Mills wrote:
> Thanks, Flint WALRUS. I will certainly try that.
>
> On Wed, Jan 10, 2018 at 4:57
Hi everyone,
I wanted to point out that the nova API patch for volume mulitattach
support is available for review:
https://review.openstack.org/#/c/271047/
It's actually a series of changes, but that is the last one that enables
the feature in nova. It relies on the 2.59 compute API microver
Hi Folks,
Today we are gonna continue to comb through the public cloud feature
list[0] as we did yesterday. Please join the discussion at
#openstack-publiccloud starting from UTC1400.
[0]https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-
XSycSkOjqCyMTIedkA/edit?usp=sharing
--
Zhi
Hi,
We currently have a private cloud running old instances using the virtio-blk
driver and new instances using the virtio-scsi driver. We would like to convert
all our existing instances to virtio-scsi but there doesn’t appear to be an
official way to do this. Can I modify this in the openstac
10 matches
Mail list logo
