On 10/7/14 6:36 PM, Ivar Lazzaro wrote:
I posted a patch that implements the Different DB Different Chain
approach [0].
That does not mean that this approach is the chosen one! It's just to
have a grasp of what the change looks like.
The Same DB different chain solution is much simpler to
It seems to me that deployment tools such as puppet scripts would also be
simpler if the GBP service plugin used the neutron DB, as there would be no
need to create a separate DB, set its permissions, put its URL into
neutron's config file, etc.. All that would be needed at deployment time is
I posted a patch that implements the Different DB Different Chain
approach [0].
That does not mean that this approach is the chosen one! It's just to have
a grasp of what the change looks like.
The Same DB different chain solution is much simpler to implement
(basically you just specify a
I believe Group-based Policy (which this thread is about) will use the
Neutron
database configuration for its dependent database.
If Neutron is configured for:
connection = mysql://user:pass@locationX:3306/neutron
then GBP would use:
connection =
On Oct 4, 2014, at 1:10 AM, Kevin Benton blak...@gmail.com wrote:
Does sqlalchemy have good support for cross-database foreign keys? I was
under the impression that they cannot be implemented with the normal syntax
and semantics of an intra-database foreign-key constraint.
cross
Excerpts from Mike Bayer's message of 2014-10-04 08:10:38 -0700:
On Oct 4, 2014, at 1:10 AM, Kevin Benton blak...@gmail.com wrote:
Does sqlalchemy have good support for cross-database foreign keys? I was
under the impression that they cannot be implemented with the normal syntax
and
Clint Byrum cl...@fewbar.com wrote:
Excerpts from Mike Bayer's message of 2014-10-04 08:10:38 -0700:
On Oct 4, 2014, at 1:10 AM, Kevin Benton blak...@gmail.com wrote:
Does sqlalchemy have good support for cross-database foreign keys? I was
under the impression that they cannot be
On Oct 4, 2014, at 11:24 AM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Mike Bayer's message of 2014-10-04 08:10:38 -0700:
On Oct 4, 2014, at 1:10 AM, Kevin Benton blak...@gmail.com wrote:
Does sqlalchemy have good support for cross-database foreign keys? I was
under the
Hi,
Following up the latest GBP team meeting [0][1]:
As we keep going with our Juno stackforge implementation [2], although the
service is effectively a Neutron extension, we should avoid breaking
Neutron's migration chain by adding our model on top of it (and
subsequently changing Neutron's
Does sqlalchemy have good support for cross-database foreign keys? I was
under the impression that they cannot be implemented with the normal syntax
and semantics of an intra-database foreign-key constraint.
On Fri, Oct 3, 2014 at 5:25 PM, Ivar Lazzaro ivarlazz...@gmail.com wrote:
Hi,
10 matches
Mail list logo
