Blueprints are typically used for specific features, but you can also
have supertask blueprints that serve as a way to group related
blueprints together. Each blueprint can have zero or more
dependencies, which allow you to construct dependency graphs. For an
example of this, see here:
https://blueprints.launchpad.net/drizzle/+spec/replication-message-transform-library
See the Dependency tree at the bottom.
Cheers,
jay
On Wed, May 4, 2011 at 1:25 AM, Ram Durairaj (radurair)
radur...@cisco.com wrote:
Hello All:
As per our discussions in Design summit, created 4 Blueprint (BP)
placeholder for Donabe…and also see 6 BPs for Quantum …wondering about need
for so many # of BPs…
Could we just have two BPs one for Quantum and another for Donabe? That way
most of the discussions and the subsequent dev may be all inter related wrt
one of these BP…
Sorry, new to this BP/Launchpad process…So not clear on why / how to
breakdown into Multiple BPs…I see a benefit if its all self contained.
Thoughts?
Ram
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
