Hi,
I would like to propose to run Tempest at the end of the beaker jobs, for
testing purpose now.
As a start, we would accept 0 1 as return code, because this is really
experimental.
Though I think it will be interesting to see how it behaves, specially when
we implement new configurations or
Hello everyone,
Who can help me decide the importance of the bug?
https://bugs.launchpad.net/keystone/+bug/1473639
By the way, help me review the bug:
https://review.openstack.org/#/c/200512/__
OpenStack Development Mailing
This includes for client libraries too?
--John
On Jul 12, 2015, at 6:29 PM, Robert Collins robe...@robertcollins.net wrote:
So, we've got constraints support for tox coming together nicely.
The rollout for that will be per project (because tox.ini needs to change).
However, we're not
We used Tempest for a time against our production environment. It was a
pain to clean up but ephemeral test jobs solves that for you. A few
questions:
What version of tempest will be using?
Will we maintain a blacklist if there are known failures? (although this is
a pain to keep updated)
On
We had discussed this (see subj) interesting idea, during our latest meeting in
IRC
(http://eavesdrop.openstack.org/meetings/murano/2015/murano.2015-07-07-17.01.html)
The idea was borrowed from nova, who froze their specs shortly after L1
release. The reasoning behind this is rather simple, as
You can mark the network as shared and have it exposed to all of your
tenants.
- Original Message -
Hi,
I'm running openstack ( IceHouse ) configured for provider networks.
For a tenant i've created the network/ subnet using the below commands and
everything works as expected.
Hey,
Yes, sorry, I only discovered this yesterday. I should have updated the
wiki page sooner but I've placed some details there now:
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo+topic:fix-th,n,z
Basically the removal of migrate-flavor-data from master
Hi,
I'm running openstack (IceHouse) configured for provider networks.
For a tenant i've created the network/ subnet using the below commands and
everything works as expected.
neutron net-create --tenant-id f557a3f5303d4e7c9218c5539456eb37
--provider:physical_network=physnet2
Kirill,
Here's the latest on the Nova freeze concept:
http://lists.openstack.org/pipermail/openstack-dev/2015-June/068079.html
-- dims
On Sun, Jul 12, 2015 at 5:29 PM, Kirill Zaitsev kzait...@mirantis.com wrote:
We had discussed this (see subj) interesting idea, during our latest meeting
in
Has anyone else seen this error with the new mock?
'self' parameter lacking default value
My function under test runs correctly, but then Mock throws this TypeError
when comparing the parameters in assert_calls_with().
I'm seeing this in Barbican. More info below [1][2].
--Dave
[1]
So, we've got constraints support for tox coming together nicely.
The rollout for that will be per project (because tox.ini needs to change).
However, we're not compiling, nor are we easily able to do so, a
constraints set for Python 2.6. (We compile one unified file with all
our constraints,
Hi Andrew,
Thanks for the reply.
Are you mean :
1. admin user is used by transient cluster is mainly to make it work.
2. The proxy user is the more secure way to do the same thing.
Should we use proxy user at all situation then ? Should this be a bp or just a
bug ?
Thanks.
I just ran into this issue because I was installing a package that was
bringing in keystonemiddleware 1.5.x which was downgrading pbr to 1.0.
I fixed this problem by upgrading keystonemiddleware to 2.x.x with:
pip install -U keystonemiddleware
After that, devstack worked fine again.
This break
Hi,
Forgot to mention, indeed we configured extra_specs: volume_backend_name.
The problem is that a volume of this type can get scheduled on a node where
c-vol is not configured with this backend.
F.e.: I have 3 storage nodes (c-vol) and two have the driver configured,
the third one doesn't have
Hi,
Tried these in requirements.txt:
Routes!=2.0,!=2.1,=1.12.3;python_version=='2.7'
Routes!=2.0,=1.12.3;python_version!='2.7'
The gate still complains:
Requirement set([Requirement(package=u'Routes', location='',
specifiers='!=2.0,!=2.1,=1.12.3', markers=upython_version=='2.7',
comment=''),
+1 Welcome!!
--
OTSUKA, Motohiro
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Friday, July 10, 2015 at 21:50, Hongbin Lu wrote:
+1 Welcome Tom!
-Original Message-
From: Adrian Otto [mailto:adrian.o...@rackspace.com]
Sent: July-09-15 10:21 PM
To: OpenStack
Meeting on #openstack-meeting at 1400 UTC (8:00AM MDT)
1) Liberty specs -
https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
2) Mid-cycle meetup
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
It sounds like the extra specs you configured are not selective enough. Can
you post up your 3 cinder.conf files from the c-vol nodes, and the commands
used to create the volume type, please?
On 13 Jul 2015 08:00, Eduard Matei eduard.ma...@cloudfounders.com wrote:
Hi,
Forgot to mention, indeed
Right - all changes to requirements.txt in a project must be already
in global-requirements. So propose it there, get that merged, then
propose into your local project.
-Rob
On 13 July 2015 at 17:08, Qiming Teng teng...@linux.vnet.ibm.com wrote:
Hi,
Tried these in requirements.txt:
+1 for this
2015-07-10 18:19 GMT+09:00 Thierry Carrez thie...@openstack.org:
Adam Lawson wrote:
The alternative of course is to just number the releases since names
ultimately don't mean anything but it seems there are problems with that
level of simplicity. I personally prefer Tristan's
On Fri, Jul 10, 2015 at 1:57 AM, Mark Kirkwood
mark.kirkw...@catalyst.net.nz wrote:
Hi,
I'm deploying a swift 1.13 cluster on Ubuntu 14.04 and enabling ceilometer
in the proxy pipeline results in it not working.
The cause appears to be the log directory perms (note I am running the
proxy
21 matches
Mail list logo
