12 jun 2013 kl. 09:25 skrev Andre Pech:
As promised at the ml2 kickoff meeting last week, attached is our basic
proposal for the ml2 mechanism driver API.
Great, that is fast work!
After getting more familiar with the ml2 plugin code and looking at some of
the other blueprints that are
Chmouel,
Yes, it's possible to set up excluded directories in several ways. My question
was why not make those directories excluded by default?
- Roman
On Jun 18, 2013, at 11:14 , Chmouel Boudjnah chmo...@enovance.com wrote:
On Tue, Jun 18, 2013 at 9:50 AM, Roman Prykhodchenko
The gate has been terribly broken of the last couple of weeks, and right
now people running 'recheck no bug' aren't helping, as it keeps papering
over *real* issues. There was a glance one, which is fixed.
However the current biggest issue is probably this one -
On 13-06-18 04:59 AM, Thierry Carrez wrote:
Personally I would introduce a TESTING file that would describe all
available methods for running tests, and rename/move run_tests.sh to
something less discoverable... so that people looking for ways to run
tests would find TESTING first. Then if
I don't have any objections to this being exposed - but the question was should
we expose it, and I don't see any benefit to the user for this particular key.
Of course, as you say, a provider may want to expose many specific metadata
keys. Perhaps we should look at how to do this
Excerpts from Robert Collins's message of 2013-06-18 03:06:40 -0700:
On 18 June 2013 17:57, Mark McLoughlin mar...@redhat.com wrote:
On Tue, 2013-06-18 at 13:17 +1200, Robert Collins wrote:
So, I've been pretty happy with reviews from Chris Jones and Clint
Byrum - would like to propose them
Excerpts from Thierry Carrez's message of 2013-06-18 01:59:57 -0700:
Joe Gordon wrote:
Reasons to keep run_tests.sh:
* there is no possibility to run tests with testtools instead of testr.
This feature allows us to use the debugger.
* in some projects tox doesn't use a testr wrapper to
Hi,
I'm trying to configure an Openstack installation with only 2 hosts:
Controller-Network node and Compute node.
My problems came when I tried to configure the quantum-dhcp-agent. In my
dhcp.agent.log I have the following error:
RROR [quantum.agent.dhcp_agent] Failed reporting state!
On 19 June 2013 03:56, Clark Boylan clark.boy...@gmail.com wrote:
I finally got around to looking into this today. I ran `tox -epy27`
locally a couple times and noticed that test numbers did vary (but not
as wildly as reported earlier). My next step was to source the tox
py27 virtualenv then
On 06/18/2013 12:43 PM, Martina Kollarova wrote:
Jenkins keeps running all the tests, even if the basic pep8 test fails,
and runs all of the (very slow) Tempest Quantum tests, even though
almost all of them are failing.
I propose that it should fail and stop all of the other tests once there
is
On 06/18/2013 12:43 PM, Martina Kollarova wrote:
Jenkins keeps running all the tests, even if the basic pep8 test fails,
and runs all of the (very slow) Tempest Quantum tests, even though
almost all of them are failing.
I propose that it should fail and stop all of the other tests once there
is
Bob,
If the user is cognizant of the extension, they may want to do post-build
activities based on the value. I think that's the use for this particular case.
As for exposing them in a more general fashion, I agree with both of your
points: there can be use to expose them, and also reasons to
On 06/18/2013 09:13 PM, Kant, Arun wrote:
The issue with having un-managed number of tokens for same credential
is that it can be easily exploited. Getting a token is one of initial
step (gateway) to get access to services. A rogue client can keep
creating unlimited number of tokens and
Angus,
I'm glad you are asking good questions. I have additional input for you to
consider below.
On Jun 18, 2013, at 6:09 PM, Angus Salkeld asalk...@redhat.com wrote:
On 18/06/13 23:32 +, Adrian Otto wrote:
Yes. I think having a POST method in the API makes perfect sense. Assuming
we
On Tue, Jun 18, 2013 at 11:01 PM, Adrian Otto adrian.o...@rackspace.comwrote:
On Jun 18, 2013, at 6:09 PM, Angus Salkeld asalk...@redhat.com wrote:
To me one of the most powerful and apealing things of Heat is the
ability to reproducibly re-create a stack from a template. This
new public
15 matches
Mail list logo
