Hi!
For most openstack parts (e.g. Aodh, Cinder, Glance, Heat, Ironic, Keystone,
Neutron, Nova) it was easy to get logs to syslog.
For example for Heat something similar to this (into file
templates/heat.conf.j2):
# Syslog usage
{% if heat_syslog_enabled %}
use_syslog = True
syslog_log_facilit
Hi!
There was a new 'domain' property added to OS::Keystone::Role
(https://storyboard.openstack.org/#!/story/1684558,
https://review.openstack.org/#/c/459033/).
With "openstack role create" CLI command it is still possible to create roles
with no associated domains; but it seems that the same
Hi!
I refer here to my question sent earlier to AskOpenstack:
https://ask.openstack.org/en/question/97425/why-it-is-not-possible-to-rebuild-an-instance-from-a-bootable-volume/
Are there some (architectural, performance, security etc.) reasons why
rebuilding instances from (bootable) volumes is
e.com]
> Sent: Thursday, September 24, 2015 4:56 PM
> To: Kosonen, Juha (Nokia - FI/Espoo); Tikkanen, Viktor (Nokia - FI/Espoo)
> Cc: Jose Lausuch
> Subject: [OPNFV] [Functest] Tempest & Rally
>
> Hi,
>
> I was wondering whether you could have a look at Rally/Tempest t
Hi!
We have a scenario tempest test case (test_cross_tenant_traffic) which
assumes that an instance should be able to receive icmp echo responses
even when no ingress security rules are defined for that instance.
I don't take a stand on iptables-based security group implementation
details (this w
Thank you for the references!
> -Original Message-
> From: ext Ken'ichi Ohmichi [mailto:ken1ohmi...@gmail.com]
> Sent: Wednesday, August 19, 2015 2:48 AM
...
> Is it difficult to make these properties upstream?
> Vendor specific properties will make API different between clouds, and
> that
Hi!
I have I question regarding validating responses during API tests.
Has it been decided some time ago that no additional properties
are allowed when verifying response schemas during API tests?
I have an OpenStack based product that contains few additional
properties in it's compute API an
; So I need to point out that the openstack-qa list isn't used anymore. We
> only
> keep it around so we have a place to send for periodic test results. In
> the
> future you should just send things to the openstack-dev ML with a [QA] tag
> in the subject.
>
> On Tue, Jun 16,
