On Mon, Mar 9, 2015 at 10:08 PM, John Garbutt j...@johngarbutt.com wrote:
Hi,
I think I agree with Jay here, but let me explain...
On 8 March 2015 at 12:10, Alex Xu sou...@gmail.com wrote:
Thanks for Jay point this out! If we have agreement on this and document
it,
that will be great
On Mon, Mar 9, 2015 at 10:08 PM, John Garbutt j...@johngarbutt.com wrote:
+1
Please could you submit a dev ref for this?
We can argue on the review, a bit like this one:
https://github.com/openstack/nova/blob/master/doc/source/devref/policy_enforcement.rst
I think it'd also be a good
Hi fellow developers,
It'd be nice to achieve a 1.0 release for tooz, as some projects are
already using it, and more are going to adopt it.
I think we should collect features and potential bugs/limitations we'd
like to have and fix before that. Ideas, thoughts?
Cheers,
--
Julien Danjou
;;
The Oslo team is glad to announce the release of:
oslo.config 1.9.1: Oslo Configuration API
For more details, please see the git log history below and:
http://launchpad.net/oslo.config/+milestone/1.9.1
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.config
hi,
I have a standalone swift cluster with swauth as the auth module. By
standalone, I mean the cluster is not in the context of OpenStack, or
keystone server.
Now I have moved ACL logic to application level and decided to have all
data in swift under one user account. I have a few questions on
On 03/09/2015 01:59 PM, Michael Krotscheck wrote:
On Sun, Mar 8, 2015 at 3:21 PM Thomas Goirand z...@debian.org
mailto:z...@debian.org wrote:
Anyway, you understood me: please *never* use this Expat/MIT license
with the The Software shall be used for Good, not Evil. additional
The Oslo team is excited to announce the release of:
oslo.log 1.0.0: oslo.log library
For more details, please see the git log history below and:
http://launchpad.net/oslo.log/+milestone/1.0.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.log
Notable changes
On Mon, Mar 9, 2015 at 9:35 PM, Sean Dague s...@dague.net wrote:
On 03/07/2015 07:31 PM, Jay Pipes wrote:
Hi Stackers,
Now that microversions have been introduced to the Nova API (meaning we
can now have novaclient request, say, version 2.3 of the Nova API using
the special
On Sun, Mar 8, 2015 at 3:21 PM Thomas Goirand z...@debian.org wrote:
Anyway, you understood me: please *never* use this Expat/MIT license
with the The Software shall be used for Good, not Evil. additional
clause. This is non-free software, which I will *never* be able to
upload to Debian
hi there
In murano when deploy environment useEnvironmentNerwork=true is default.
How can I deploy with useEnvironmentNerwork=true?
I'm currently using sample Apache web server package
--
Choe, Cheng-Dae
Blog: http://blog.woosum.net http://www.woosum.net
The Oslo team is chuffed to announce the release of:
cliff 1.10.1: Command Line Interface Formulation Framework
For more details, please see the git log history below and:
https://launchpad.net/python-cliff/+milestone/1.10.1
Please report issues through launchpad:
The Oslo team is gleeful to announce the release of:
oslo.i18n 1.5.0: oslo.i18n library
For more details, please see the git log history below and:
http://launchpad.net/oslo.i18n/+milestone/1.5.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.i18n
Notable
Hi,
Apologies for the slow reply, long weekend because of a public holiday over
here. I'm probably going to end up repeating part of what
Alex has mentioned as well.
So the first thing I think we want to distinguish between plugins being a
REST API user or operator concept and it being
a tool
Dear All,
I have a openstack HA environment deployed using fuel 5.1. Fuel master node
collects all the node logs under /var/log/docker-logs/remote/ directory.
I have installed Logstash on fuel master node. Here is Logstash.conf:
http://paste.openstack.org/show/190985/
Here is rsyslog Template
- Original Message -
From: Christopher Yeoh cbky...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, March 9, 2015 1:04:15 PM
Subject: Re: [openstack-dev] [nova][api] Microversions. And why do we need
API
- Original Message -
From: Mike Bayer mba...@redhat.com
To: Attila Fazekas afaze...@redhat.com
Cc: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Friday, March 6, 2015 2:20:45 AM
Subject: Re: [openstack-dev] [all] SQLAlchemy
Hi,
I think I agree with Jay here, but let me explain...
On 8 March 2015 at 12:10, Alex Xu sou...@gmail.com wrote:
Thanks for Jay point this out! If we have agreement on this and document it,
that will be great for guiding developer how to add new API.
+1
Please could you submit a dev ref
Greetings!
Neutron is adding a new concept of subnet pool. To put it simply, it is a
collection of IP prefixes from which subnets can be allocated. In this way
a user does not have to specify a full CIDR, but simply a desired prefix
length, and then let the pool generate a CIDR from its prefixes.
Boris,
1. Suppose a project say Nova wants to enable this Rally Integration
for its functional tests, what does that project have to do? (other
than the existing well defined tox targets)
2. Is there a test project with Gabbi based tests that you know of?
3. What changes if any are needed in
The Oslo team is pleased to announce the release of:
oslo.concurrency 1.7.0: oslo.concurrency library
For more details, please see the git log history below and:
http://launchpad.net/oslo.concurrency/+milestone/1.7.0
Please report issues through launchpad:
On 03/07/2015 07:31 PM, Jay Pipes wrote:
Hi Stackers,
Now that microversions have been introduced to the Nova API (meaning we
can now have novaclient request, say, version 2.3 of the Nova API using
the special X-OpenStack-Nova-API-Version HTTP header), is there any good
reason to require
Since test_server_cfn_init was recently moved from tempest to the heat
functional tests, there are no subclasses of OrchestrationScenarioTest.
If there is no plan to add any more heat scenario tests to tempest I
would like to remove that class. So I want to confirm that future
scenario tests
On Sun, Mar 08, 2015 at 11:19:10PM +0100, Thomas Goirand wrote:
On 03/08/2015 06:34 PM, Mike Bayer wrote:
Ian Wells ijw.ubu...@cack.org.uk wrote:
With apologies for derailing the question, but would you care to tell us
what evil you're planning on doing? I find it's always best
The Oslo team is thrilled to announce the release of:
oslo.db 1.6.0: oslo.db library
For more details, please see the git log history below and:
http://launchpad.net/oslo.db/+milestone/1.6.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.db
Notable changes
- Original Message -
The L3 agent uses ARP and static routes like a normal router would. The L2
agent is where there might be differences depending on the network type
used. If it's a tunnel overlay, the L2 agent may perform an ARP offload from
information it has learned via the L2
The Oslo team is gleeful to announce the release of:
oslo.middleware 1.0.0: Oslo Middleware library
For more details, please see the git log history below and:
http://launchpad.net/oslo.middleware/+milestone/1.0.0
Please report issues through launchpad:
The Oslo team is gleeful to announce the release of:
oslo.utils 1.4.0: Oslo Utility library
For more details, please see the git log history below and:
http://launchpad.net/oslo.utils/+milestone/1.4.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.utils
The Oslo team is excited to announce the release of:
stevedore 1.3.0: Manage dynamic plugins for Python applications
For more details, please see the git log history below and:
https://launchpad.net/python-stevedore/+milestone/1.3.0
Please report issues through launchpad:
The Oslo team is pumped to announce the release of:
tooz 0.13.0: Coordination library for distributed systems.
For more details, please see the git log history below and:
http://launchpad.net/python-tooz/+milestone/0.13.0
Please report issues through launchpad:
On Mon, Mar 09, 2015 at 10:47:21AM -0400, Attila Fazekas wrote:
Hi All,
This is follow up on [1].
Running the full tempest test-suite in parallel without the
allow_tenant_isolation=True settings, can cause random not too obvious
failures, which caused lot of issue to tempest newcomers.
The Oslo team is happy to announce the release of:
oslotest 1.5.1: OpenStack test framework
For more details, please see the git log history below and:
http://launchpad.net/oslotest/+milestone/1.5.1
Please report issues through launchpad:
http://bugs.launchpad.net/oslotest
Notable
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Mon, Mar 9, 2015, at 08:52 AM, Radomir Dopieralski wrote:
On 03/09/2015 01:59 PM, Michael Krotscheck wrote:
On Sun, Mar 8, 2015 at 3:21 PM Thomas Goirand z...@debian.org
mailto:z...@debian.org wrote:
Anyway, you understood me: please *never* use this Expat/MIT license
On Mon, Mar 09, 2015 at 09:52:54AM -0400, David Kranz wrote:
Since test_server_cfn_init was recently moved from tempest to the heat
functional tests, there are no subclasses of OrchestrationScenarioTest.
If there is no plan to add any more heat scenario tests to tempest I would
like to remove
The Oslo team is overjoyed to announce the release of:
oslo.messaging 1.8.0: Oslo Messaging API
For more details, please see the git log history below and:
http://launchpad.net/oslo.messaging/+milestone/1.8.0
Please report issues through launchpad:
The Oslo team is chuffed to announce the release of:
oslo.serialization 1.4.0: oslo.serialization library
For more details, please see the git log history below and:
http://launchpad.net/oslo.serialization/+milestone/1.4.0
Please report issues through launchpad:
Hi Everyone,
I just wanted to mention that in the past couple of weeks we've started an
effort to write some documentation to explain common aspects of tempest
configuration. The current version of the doc can be found here:
http://docs.openstack.org/developer/tempest/configuration.html
Right
Another idea; provide some way for tooz to handle the heartbeating
(instead of clients having to do this); perhaps tooz coordinator should
take ownership of the thread that heartbeats (instead of clients having
to do this on there own)? This avoids having each client create there
own thread
The Oslo team is chuffed to announce the release of:
oslo.rootwrap 1.6.0: Oslo Rootwrap
For more details, please see the git log history below and:
http://launchpad.net/oslo.rootwrap/+milestone/1.6.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.rootwrap
Davanum,
1. Suppose a project say Nova wants to enable this Rally Integration
for its functional tests, what does that project have to do? (other
than the existing well defined tox targets)
Actually project by it self shouldn't do anything.
The whole work regarding to integration belongs to
On Mon, 9 Mar 2015, Davanum Srinivas wrote:
2. Is there a test project with Gabbi based tests that you know of?
In addition to the ceilometer tests that Boris pointed out gnocchi
is using it as well:
https://github.com/stackforge/gnocchi/tree/master/gnocchi/tests/gabbi
3. What changes
- Original Message -
Thank you. I am looking to read this state and compare it with neutron DB. If
there are agents that do it already, I would like only to learn if I can
change the polling period. Can you advise about the most efficient way to
learn which agent does it and which
I've been chipping away at what it would take to upgrade our Fedora CI
jobs to Fedora 21. The motivation was primarily that Fedora 21 has more
recent packages which would simplify some of the package requirements in
Delorean. Besides this Fedora 21 has been out for months now so we
really should
Apologies to the tooz team, auto-correct ate the Z in the name in the
subject line. - Doug
On Mon, Mar 9, 2015, at 09:44 AM, Doug Hellmann wrote:
The Oslo team is pumped to announce the release of:
tooz 0.13.0: Coordination library for distributed systems.
For more details, please see the
Hi All,
This is follow up on [1].
Running the full tempest test-suite in parallel without the
allow_tenant_isolation=True settings, can cause random not too obvious
failures, which caused lot of issue to tempest newcomers.
There are special uses case when you might want to disable it,
for
On Mar 9, 2015, at 9:46 AM, Weidong Shao weidongs...@gmail.com wrote:
hi,
I have a standalone swift cluster with swauth as the auth module. By
standalone, I mean the cluster is not in the context of OpenStack, or
keystone server.
That's completely fine (and not uncommon at all).
Let's do it,
One that I can think of off the top of my head would be to have
`join_group` and associated functions have the ability to automatically
create the group if it does not exist already (instead of raising a
error and then having the user deal with the failure themselves).
I'm also
ok, no problem, will take a look it tomorrow.
2015-03-09 20:18 GMT+08:00 Christopher Yeoh cbky...@gmail.com:
On Mon, Mar 9, 2015 at 10:08 PM, John Garbutt j...@johngarbutt.com
wrote:
+1
Please could you submit a dev ref for this?
We can argue on the review, a bit like this one:
On 03/08/2015 02:28 PM, Morgan Fainberg wrote:
On March 8, 2015 at 11:24:37 AM, David Stanek (dsta...@dstanek.com
mailto:dsta...@dstanek.com) wrote:
On Sun, Mar 8, 2015 at 1:37 PM, Mike Bayermba...@redhat.com
mailto:mba...@redhat.comwrote:
can you elaborate on your reasoning that FK
On 02/25/2015 07:07 AM, Daniel P. Berrange wrote:
On Wed, Feb 25, 2015 at 11:46:05AM +, Neil Jerram wrote:
Although we are past the non-priority deadline, I have been encouraged
to request this late exception for Project Calico's spec and code adding
VIF_TYPE_TAP to Nova.
I'm afraid
Clint Byrum cl...@fewbar.com wrote:
Excerpts from David Stanek's message of 2015-03-08 11:18:05 -0700:
On Sun, Mar 8, 2015 at 1:37 PM, Mike Bayer mba...@redhat.com wrote:
can you elaborate on your reasoning that FK constraints should be used less
overall? or do you just mean that the
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday March 10th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone
Excerpts from David Stanek's message of 2015-03-08 11:18:05 -0700:
On Sun, Mar 8, 2015 at 1:37 PM, Mike Bayer mba...@redhat.com wrote:
can you elaborate on your reasoning that FK constraints should be used less
overall? or do you just mean that the client side should be mirroring the
On 03/05/2015 09:34 AM, Andy McCrae wrote:
Sorry to resurrect this almost a year later! I've recently run into this
issue, and it does make logging into Windows instances, via the console,
quite challenging.
On Fri, Jun 6, 2014 at 3:46 PM, Ben Nemec openst...@nemebean.com wrote:
This
On Sun, Mar 8, 2015 at 10:28 PM, Chen, Wei D wei.d.c...@intel.com wrote:
+1,
I am fan of checking the constraints in the controller level instead of
relying on FK constraints itself, thanks.
The Keystone controllers shouldn't do any business logic. This should be in
the managers. The
Hi All,
I've noticed a few times recently where reviews have been abandoned by
people who were not the original authors. These reviews were only days old
and there was no prior notice or discussion. This is both rude and
discouraging to contributors. Reasons for abandoning should be discussed on
Hi all,
I would like to invite you to review the guidelines for metadata and
tagging that I proposed to the API-WG. Links:
https://review.openstack.org/#/c/141229/
https://review.openstack.org/#/c/155620/
The idea with these guidelines is to come up with a set of recommendations
to be used
Julien Danjou wrote:
On Mon, Mar 09 2015, Joshua Harlow wrote:
Another idea; provide some way for tooz to handle the heartbeating (instead of
clients having to do this); perhaps tooz coordinator should take ownership of
the thread that heartbeats (instead of clients having to do this on there
On Mon, Mar 09 2015, Joshua Harlow wrote:
Another idea; provide some way for tooz to handle the heartbeating (instead of
clients having to do this); perhaps tooz coordinator should take ownership of
the thread that heartbeats (instead of clients having to do this on there
own)?
This avoids
On Mon, Mar 09 2015, Joshua Harlow wrote:
One that I can think of off the top of my head would be to have `join_group`
and associated functions have the ability to automatically create the group if
it does not exist already (instead of raising a error and then having the user
deal with the
Julien Danjou wrote:
On Mon, Mar 09 2015, Joshua Harlow wrote:
One that I can think of off the top of my head would be to have `join_group`
and associated functions have the ability to automatically create the group if
it does not exist already (instead of raising a error and then having the
Wei D wei.d.c...@intel.com wrote:
+1,
I am fan of checking the constraints in the controller level instead of
relying on FK constraints itself, thanks.
Why shouldn’t the storage backends, be they relational or not, be tasked
with verifying integrity of data manipulations? If data
The Oslo team is glad to announce the release of:
debtcollector 0.3.0: A collection of Python deprecation patterns and
strategies that help you collect your technical debt in a non-
destructive manner.
For more details, please see the git log history below and:
Hi all,
I'd like to propose adding Ramakrishnan (rameshg87) to ironic-core.
He's been consistently providing good code reviews, and been in the top
five active reviewers for the last 90 days and top 10 for the last 180
days. Two cores have recently approached me to let me know that they, too,
On Mar 9, 2015, at 13:14, Sean Dague s...@dague.net wrote:
So possibly another way to think about this is our prior signaling of
what was supported by Nova was signaled by the extension list. Our code
was refactored into a way that supported optional loading by that unit.
As we're making
On Mon, Mar 09, 2015 at 09:52:54AM -0400, David Kranz wrote:
Since test_server_cfn_init was recently moved from tempest to the heat
functional tests, there are no subclasses of OrchestrationScenarioTest.
If there is no plan to add any more heat scenario tests to tempest I would
like to remove
Hello,
Answears below
Dnia niedziela, 8 marca 2015 13:53:51 Ian Wells pisze:
On 6 March 2015 at 13:16, Sławek Kapłoński sla...@kaplonski.pl wrote:
Hello,
Today I found bug https://bugs.launchpad.net/neutron/+bug/1314614 because
I
have such problem on my infra.
(For reference, if
We are getting issues running barbican functional tests - seems to have started
sometime between Thursday last week (3/5) and today (3/9)
Seems that oslo config giving us DuplicateOptErrors now. Our functional tests
use oslo config (via tempest) as well as barbican server code. Looking into
Morgan Fainberg morgan.fainb...@gmail.com wrote:
On Monday, March 9, 2015, Mike Bayer mba...@redhat.com wrote:
Wei D wei.d.c...@intel.com wrote:
+1,
I am fan of checking the constraints in the controller level instead of
relying on FK constraints itself, thanks.
Why
On 03/08/2015 08:10 AM, Alex Xu wrote:
Thanks for Jay point this out! If we have agreement on this and document
it, that will be great for guiding developer how to add new API.
I know we didn't want extension for API. But I think we still
need modularity. I don't think we should put everything
On 03/07/2015 04:34 AM, Dan Prince wrote:
On Tue, 2015-03-03 at 17:30 -0500, James Slagle wrote:
Hi,
Don't let the subject throw you off :)
I wasn't sure how to phrase what I wanted to capture in this mail, and
that seemed reasonable enough. I wanted to kick off a discussion about
what gaps
Sorry, pulling this from the archives [1] because I seem to have lost the
original in my mailbox...
1) (this is more for neutron people) Is there a real use case for
requesting specific gateway IPs and allocation pools when allocating from
a
pool? If not, maybe we should let the pool set a
On Mon, Mar 9, 2015 at 2:32 PM, Matthew Farina m...@mattfarina.com wrote:
David,
FYI, the last time I chatted with John Dickinson I learned there are
numerous API elements not documented. Not meant to be private but the docs
have not kept up. How should we handle that?
I've read through
Hi,
it would make sense to have a library for the code shared by Tuskar UI
and CLI (I mean TripleO CLI - whatever it will be, not tuskarclient
which is just a thing wrapper for Tuskar API). There are various actions
which consist from more that a single API call to an openstack
service, to
On 10/03/15 03:23, Matthew Treinish wrote:
On Mon, Mar 09, 2015 at 09:52:54AM -0400, David Kranz wrote:
Since test_server_cfn_init was recently moved from tempest to the heat
functional tests, there are no subclasses of OrchestrationScenarioTest.
If there is no plan to add any more heat
I guess I'll vote for (D), so that there is the possibility of early (1400
UTC) and late (2100) on alternating weeks, given we don't have much to
discuss lately and then changing to (C), if things pick up.
Let's discuss at Tuesday's meeting (note DST change for US folks), at 1500
UTC.
PCM
On Monday, March 9, 2015, Mike Bayer mba...@redhat.com wrote:
Wei D wei.d.c...@intel.com javascript:; wrote:
+1,
I am fan of checking the constraints in the controller level instead of
relying on FK constraints itself, thanks.
Why shouldn’t the storage backends, be they
+1 on both points, Ryan.
On 03/09/2015 01:21 PM, Ryan Moe wrote:
Hi All,
I've noticed a few times recently where reviews have been abandoned by
people who were not the original authors. These reviews were only days
old and there was no prior notice or discussion. This is both rude and
Richard, thanks for sharing this. I hope we can move to bower sooner rather
than later.
On Sat, Mar 7, 2015 at 5:26 PM, Richard Jones r1chardj0...@gmail.com
wrote:
On Sun, 8 Mar 2015 at 04:59 Michael Krotscheck krotsch...@gmail.com
wrote:
Anyone wanna hack on a bower mirror puppet module
On 03/09/2015 07:32 AM, Christopher Yeoh wrote:
snip
So the first thing I think we want to distinguish between plugins
being a REST API user or operator concept and it being a tool
developers use as a framework to support the Nova REST API. As I've
mentioned before I've no problem with the
On Mon, Mar 9, 2015, at 09:09 AM, Doug Hellmann wrote:
The Oslo team is glad to announce the release of:
oslo.config 1.9.1: Oslo Configuration API
For more details, please see the git log history below and:
http://launchpad.net/oslo.config/+milestone/1.9.1
Please report issues
Hi Devananda,
Thanks for bringing this up. I've seen some recent discussions about
changing our python-client so that it supports a range of versions of the
server. I think that makes sense and that's how/where we can fix the client
so that it supports requests/responses that are particular to a
So another idea.
I know kazoo has/had the following:
https://github.com/python-zk/kazoo/pull/141
Add shared locks and revocable shared lock support
It might be nice if tooz had support for that (the kazoo PR was rejected
since there just wasn't enough maintainers in the kazoo project to
Hi everyone,
The virtual sprint[1] has been going really well. Last Thursday in the virtual
sprint we got 3 patches reviewed and merged! (156810, 157128, 160093) We also
had good discussion on the transfer tables and and spinner. With the transfer
tables, we decided to make them a parent
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
(As of Mon, 09 Mar 17:00 UTC)
Open: 133 (+4)
3 new (0), 32 in progress (0), 0 critical, 18 high and 8 incomplete
Drivers
==
IPA
On 09/03/15 13:56, Julien Danjou wrote:
Hi fellow developers,
It'd be nice to achieve a 1.0 release for tooz, as some projects are
already using it, and more are going to adopt it.
I think we should collect features and potential bugs/limitations we'd
like to have and fix before that.
David,
FYI, the last time I chatted with John Dickinson I learned there are
numerous API elements not documented. Not meant to be private but the docs
have not kept up. How should we handle that?
Thanks,
Matt Farina
On Sat, Mar 7, 2015 at 5:25 PM, David Lyle dkly...@gmail.com wrote:
I agree
John,
thanks for the reply. See questions inline.
thanks,
Weidong
On Mon, Mar 9, 2015 at 8:23 AM John Dickinson m...@not.mn wrote:
On Mar 9, 2015, at 9:46 AM, Weidong Shao weidongs...@gmail.com wrote:
hi,
I have a standalone swift cluster with swauth as the auth module. By
On 03/09/2015 03:37 PM, Jay Pipes wrote:
On 03/08/2015 08:10 AM, Alex Xu wrote:
Thanks for Jay point this out! If we have agreement on this and document
it, that will be great for guiding developer how to add new API.
I know we didn't want extension for API. But I think we still
need
On Mon, Mar 9, 2015, at 09:21 AM, Doug Hellmann wrote:
The Oslo team is excited to announce the release of:
oslo.log 1.0.0: oslo.log library
For more details, please see the git log history below and:
http://launchpad.net/oslo.log/+milestone/1.0.0
Please report issues through
Thank you all! The nominations and the consolidation has been implemented.
Cheers
-Nikhil
From: Nikhil Komawar nikhil.koma...@rackspace.com
Sent: Sunday, March 8, 2015 2:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
Excerpts from Mike Bayer's message of 2015-03-09 10:26:37 -0700:
Clint Byrum cl...@fewbar.com wrote:
Excerpts from David Stanek's message of 2015-03-08 11:18:05 -0700:
On Sun, Mar 8, 2015 at 1:37 PM, Mike Bayer mba...@redhat.com wrote:
can you elaborate on your reasoning that FK
I've just finished[1] an arc of development adding showing frame local
variables in tracebacks to our testing stack[2]. Its off by default
since its new and doesn't have the depth of polish that e.g. the
py.test equivalent does.
Turning it on is easy - bump the subunit library version to get the
2015-03-09 20:36 GMT+09:00 Christopher Yeoh cbky...@gmail.com:
On Mon, Mar 9, 2015 at 9:35 PM, Sean Dague s...@dague.net wrote:
On 03/07/2015 07:31 PM, Jay Pipes wrote:
Hi Stackers,
Now that microversions have been introduced to the Nova API (meaning we
can now have novaclient
Thanks Salvatore. Here are my thoughts, hopefully there’s some merit to them:
With implicit allocations, the thinking is that this is where a subnet is
created in a backward-compatible way with no subnetpool_id and the subnets
API’s continue to work as they always have.
In the case of a
Hi,
2015-03-09 20:38 GMT+09:00 John Garbutt j...@johngarbutt.com:
On 8 March 2015 at 12:10, Alex Xu sou...@gmail.com wrote:
Thanks for Jay point this out! If we have agreement on this and document it,
that will be great for guiding developer how to add new API.
+1
Please could you submit a
And I forgot my references. Doh.
On 10 March 2015 at 12:57, Robert Collins robe...@robertcollins.net wrote:
I've just finished[1] an arc of development adding showing frame local
variables in tracebacks to our testing stack[2]. Its off by default
since its new and doesn't have the depth of
As the title says, I've gone ahead and written up our core review team
policies, and posted it here:
https://wiki.openstack.org/wiki/Ironic/CoreTeam
Why now, you may ask?
In the interests of full disclosure, we (the current ironic-core team) had
a private discussion recently about adding a new
I was wrong. Ignore me on the https thing.
On Mon, Mar 9, 2015 at 4:05 PM Michael Krotscheck krotsch...@gmail.com
wrote:
Turns out that the bower registry doesn't actually support https. Git does
- so we can prove authenticity of the code - but the address lookup that
tells us which git url
Clint Byrum cl...@fewbar.com wrote:
So I think I didn't speak clearly enough here. The benchmarks are of
course needed, but there's a tipping point when write activity gets to
a certain level where it's cheaper to let it get a little skewed and
correct asynchronously. This is not unique
1 - 100 of 122 matches
Mail list logo
