Hi, stackers,
When submit code review in gerrit, i have been recommended put Fixes-Bug:
#bug-id/Implement-Blueprint: #bp-desc before chang-id. However, when first
run git commit in a seperate patch branch, the change-id will generate
before bug/bp, it is automatically, so i have to use git commit
Hi stackers,
I notice that there are some exceptions defined in neutron.extension, and
many exceptions are defined in neutron.common.exception. Why they are
defined seperately?
In my opinion:
1) extension will define exception which is only releated to this extension
and is intended to exposed t
+3
Sent from my really tiny device...
On Aug 17, 2013, at 8:33 AM, "Dolph Mathews"
mailto:dolph.math...@gmail.com>> wrote:
On Sat, Aug 17, 2013 at 4:18 AM, Julien Danjou
mailto:jul...@danjou.info>> wrote:
On Fri, Aug 16 2013, Doug Hellmann wrote:
> If you're saying that you want to registe
Hello,
I have 2 different openstack clusters. They share glance and keystone. I am
trying to configure them to share quantum service as well. For that I am
running a common network node that is running all the agents
(quantum-dhcp/quantum-l3/quantum-metadata/quantum-openvswitch agents) with
On 2013-08-16 11:04:14 -0400 (-0400), Doug Hellmann wrote:
> I'd like to propose Alex Gaynor for core status on the
> requirements project.
[...]
Agreed, I for one welcome his continued assistance.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
Hi -
After discussion with Jay Pipes about this bug
(https://bugs.launchpad.net/ceilometer/+bug/1211015), I'd like to split
out a new TraitType table in the storage layer, and remove the UniqueName
table. A TraitType is the name of the trait and the data type (i.e.,
string, int, float). I'd like
On Sat, Aug 17, 2013 at 4:18 AM, Julien Danjou wrote:
> On Fri, Aug 16 2013, Doug Hellmann wrote:
>
> > If you're saying that you want to register URLs without version info
> > embedded in them, and let the client work that part out by talking to the
> > service in question (or getting a version
Hi Rudra,
In this blueprint what would be the plan for Neutron?
>From the specification it seems the scope is not limited to nova-network,
but includes Neutron as well, so you probably have a plan to forward the
VPC calls to Neutron.
The question here is whether you've considered implementing the
On Fri, Aug 16, at 10:34 pm, Dean Troyer wrote:
> On Fri, Aug 16, 2013 at 8:26 PM, Henry Gessau wrote:
>
> I asked on #openstack-infra and clarkb immediately identified it as a
> problem with cliff, and saw that the cliff folks have apparently already
> fixed it in cliff 1.4.3, whic
On 17 August 2013 23:49, Salvatore Orlando wrote:
> I tend to agree that when the gate for a project is broken, nothing should
> be merged for that project until the gate jobs are green again.
> In the case of Neutron, making the job non voting only caused more bugs to
> slip through, and that mea
On Fri, Aug 16, 2013 at 11:42:52AM -0400, Steve Martinelli wrote:
>
> Hi Steven,
>
> You can look at the unit tests being run.
> https://github.com/openstack/keystone/blob/master/keystone/tests/test_v3_auth.py#L1782
>
> It looks like you need to provide the trustee uname/password and the trust
>
On Aug 17, 2013 7:52 AM, "Salvatore Orlando" wrote:
>
> I tend to agree that when the gate for a project is broken, nothing
should be merged for that project until the gate jobs are green again.
> In the case of Neutron, making the job non voting only caused more bugs
to slip through, and that mea
I tend to agree that when the gate for a project is broken, nothing should
be merged for that project until the gate jobs are green again.
In the case of Neutron, making the job non voting only caused more bugs to
slip through, and that meant more works for the developer themselves, and
more headac
On Fri, Aug 16 2013, Doug Hellmann wrote:
> If you're saying that you want to register URLs without version info
> embedded in them, and let the client work that part out by talking to the
> service in question (or getting a version number from the caller), then
> "yes, please."
Yes yes yes. I al
On Fri, Aug 16 2013, Jay Pipes wrote:
> Actually, that's the opposite of what I'm suggesting :) I'm suggesting
> getting rid of the resource_metadata column in the meter table and using the
> resource table in joins...
I think there's a lot of scenario where this would fail, like for
example inst
15 matches
Mail list logo
