Blueprint-flagged-module-loading - Revision history

Fifieldt at 08:08, 26 March 2014

2014-03-26T08:08:20Z

Ryan Lane: Text replace - "SwiftSpec" to "SwiftSpec"

2013-02-17T23:31:54Z

Text replace - "SwiftSpec" to "SwiftSpec"

Ryan Lane: Text replace - "NovaSpec" to "NovaSpec"

2013-02-17T23:31:05Z

Text replace - "NovaSpec" to "NovaSpec"

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:29:49Z

Text replace - "__NOTOC__" to ""

ToddWilley: load -> import for function names

2010-11-01T18:20:41Z

load -> import for function names

VishvanandaIshaya at 18:19, 1 November 2010

2010-11-01T18:19:10Z

VishvanandaIshaya at 05:48, 1 November 2010

2010-11-01T05:48:49Z

VishvanandaIshaya at 05:48, 1 November 2010

2010-11-01T05:48:17Z

VishvanandaIshaya at 05:47, 1 November 2010

2010-11-01T05:47:53Z

ToddWilley at 17:57, 30 October 2010

2010-10-30T17:57:39Z

New page

__NOTOC__
We currently use utils.[[LazyPluggable]] and utils.import_class to load classes. We should use a single method. I suggest we use the techniques of [[LazyPluggable]], but modify it so we don't need to specify a list of backends, but can give a class reference like those used in import_class. This way we get the lazy-loading of the backend, so that we can be less concerned with order of operations such as loading flags, and we don't need to maintain a list of possible values and can even reverence classes in other packages and allow drivers to be written outside of the main nova source tree.

← Older revision		Revision as of 08:08, 26 March 2014
Line 1:		Line 1:
−		+	{{OldDesignPage}}
	We currently use utils.[[LazyPluggable]] and utils.import_class to load classes. We should use a single method. I suggest we use the techniques of [[LazyPluggable]], but modify it so we don't need to specify a list of backends, but can give a class reference like those used in import_class. This way we get the lazy-loading of the backend, so that we can be less concerned with order of operations such as loading flags, and we don't need to maintain a list of possible values and can even reverence classes in other packages and allow drivers to be written outside of the main nova source tree.		We currently use utils.[[LazyPluggable]] and utils.import_class to load classes. We should use a single method. I suggest we use the techniques of [[LazyPluggable]], but modify it so we don't need to specify a list of backends, but can give a class reference like those used in import_class. This way we get the lazy-loading of the backend, so that we can be less concerned with order of operations such as loading flags, and we don't need to maintain a list of possible values and can even reverence classes in other packages and allow drivers to be written outside of the main nova source tree.

@@ Line 11: / Line 11: @@
 All of them start with a flag. There is no reason to have four different ways of delayed object loading.
-* '''Launchpad Entry''': NovaSpec:foo or [[SwiftSpec]]:foo
+* '''Launchpad Entry''': NovaSpec:foo or SwiftSpec:foo
 * '''Created''':
 * '''Contributors''':

@@ Line 11: / Line 11: @@
 All of them start with a flag. There is no reason to have four different ways of delayed object loading.
-* '''Launchpad Entry''': [[NovaSpec]]:foo or [[SwiftSpec]]:foo
+* '''Launchpad Entry''': NovaSpec:foo or [[SwiftSpec]]:foo
 * '''Created''':
 * '''Contributors''':

← Older revision		Revision as of 23:29, 17 February 2013
Line 1:		Line 1:
−	~~__NOTOC__~~	+
	We currently use utils.[[LazyPluggable]] and utils.import_class to load classes. We should use a single method. I suggest we use the techniques of [[LazyPluggable]], but modify it so we don't need to specify a list of backends, but can give a class reference like those used in import_class. This way we get the lazy-loading of the backend, so that we can be less concerned with order of operations such as loading flags, and we don't need to maintain a list of possible values and can even reverence classes in other packages and allow drivers to be written outside of the main nova source tree.		We currently use utils.[[LazyPluggable]] and utils.import_class to load classes. We should use a single method. I suggest we use the techniques of [[LazyPluggable]], but modify it so we don't need to specify a list of backends, but can give a class reference like those used in import_class. This way we get the lazy-loading of the backend, so that we can be less concerned with order of operations such as loading flags, and we don't need to maintain a list of possible values and can even reverence classes in other packages and allow drivers to be written outside of the main nova source tree.

@@ Line 4: / Line 4: @@
 Currently, nova uses at least four different methods for lazy loading components:
-* utils.load_object (managers and drivers)
+* utils.import_object (managers and drivers)
-* utils.load_class (auth manager)
+* utils.import_class (auth manager)
 * utils.[[LazyPluggable]] (db backend)
 * switch statement (virt connections)

← Older revision		Revision as of 18:19, 1 November 2010
Line 10:		Line 10:

	All of them start with a flag. There is no reason to have four different ways of delayed object loading.		All of them start with a flag. There is no reason to have four different ways of delayed object loading.
		+
		+	* '''Launchpad Entry''': [[NovaSpec]]:foo or [[SwiftSpec]]:foo
		+	* '''Created''':
		+	* '''Contributors''':
		+
		+	== Summary ==
		+
		+	== Release Note ==
		+
		+	This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
		+
		+	It is mandatory.
		+
		+	== Rationale ==
		+
		+	== User stories ==
		+
		+	== Assumptions ==
		+
		+	== Design ==
		+
		+	You can have subsections that better describe specific parts of the issue.
		+
		+	== Implementation ==
		+
		+	This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
		+
		+	=== UI Changes ===
		+
		+	Should cover changes required to the UI, or specific UI that is required to implement this
		+
		+	=== Code Changes ===
		+
		+	Code changes should include an overview of what needs to change, and in some cases even the specific details.
		+
		+	=== Migration ===
		+
		+	Include:
		+	* data migration, if any
		+	* redirects from old URLs to new ones, if any
		+	* how users will be pointed to the new way of doing things, if necessary.
		+
		+	== Test/Demo Plan ==
		+
		+	This need not be added or completed until the specification is nearing beta.
		+
		+	== Unresolved issues ==
		+
		+	This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
		+
		+	== BoF agenda and discussion ==
		+
		+	Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
		+
		+	----
		+	[[Category:Spec]]

← Older revision		Revision as of 05:47, 1 November 2010
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	We currently use utils.[[LazyPluggable]] and utils.import_class to load classes. We should use a single method. I suggest we use the techniques of [[LazyPluggable]], but modify it so we don't need to specify a list of backends, but can give a class reference like those used in import_class. This way we get the lazy-loading of the backend, so that we can be less concerned with order of operations such as loading flags, and we don't need to maintain a list of possible values and can even reverence classes in other packages and allow drivers to be written outside of the main nova source tree.		We currently use utils.[[LazyPluggable]] and utils.import_class to load classes. We should use a single method. I suggest we use the techniques of [[LazyPluggable]], but modify it so we don't need to specify a list of backends, but can give a class reference like those used in import_class. This way we get the lazy-loading of the backend, so that we can be less concerned with order of operations such as loading flags, and we don't need to maintain a list of possible values and can even reverence classes in other packages and allow drivers to be written outside of the main nova source tree.
		+
		+	Currently, nova uses at least four different methods for lazy loading components:
		+
		+	utils.load_object (managers and drivers)
		+	utils.load_class (auth manager)
		+	utils.[[LazyPluggable]] (db backend)
		+	switch statement (virt connections)
		+
		+	All of them start with a flag. There is no reason to have four different ways of delayed object loading.

Blueprint-flagged-module-loading - Revision history

Fifieldt at 08:08, 26 March 2014

Ryan Lane: Text replace - "SwiftSpec" to "SwiftSpec"

Ryan Lane: Text replace - "NovaSpec" to "NovaSpec"

Ryan Lane: Text replace - "__NOTOC__" to ""

ToddWilley: load -> import for function names

VishvanandaIshaya at 18:19, 1 November 2010

VishvanandaIshaya at 05:48, 1 November 2010

VishvanandaIshaya at 05:48, 1 November 2010

VishvanandaIshaya at 05:47, 1 November 2010

ToddWilley at 17:57, 30 October 2010

Ryan Lane: Text replace - "NOTOC" to ""