Ying, I can provide some insight since I am in the current timezone. Comments below. Perhaps Santhosh or are team can provide some additional thoughts later.
Troy On Jun 9, 2011, at 4:10 PM, Ying Liu (yinliu2) wrote: Hi all, Thanks Santhosh for the great work about Quantum_Framework. I looked at the code and have some questions. 1. Extension standard. In the netstack meeting, we agreed to adopt Openstack's extension standard. Jorge is still working on the standard draft. I'm not sure whether this work followed old extension mechanism or Jorge's presentation on the summit. One extension could be added is "attribute extension" to existing resources. In our use case, we need to create Portprofile and later refer it as a port's attribute. With current framework, we can create "Portprofile" as a resource through "ResourceExtension". But how does the plug-in know about this extension and refer the portprofile when the port is created? This initial Quantum extensions merge prop essentially ports the current extension code that is in Nova and puts it into Quantum. I'm not completely sure how the current Nova extension code maps to Jorge's summit presentation but I think it should be pretty close. Perhaps Jorge or someone form Team Titan can answer that. 2. Relationship between extension and plug-in. Extension seems be separated from the plug-in. If we want to extend existing plug-in, can we do it through extensions' api? How is extension made aware of plug-in’s existence? And how does the plug-in know the new resources created by extensions? Since Nova doesn't have plug-ins in the same way as Quantum, I don't know that we've considered that relationship fully. It is a good topic for discussion. Best, Ying _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated.
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
