I think we should focus on using the existing modularity mechanisms inside this project, at least in terms of the dashboard integration. The Rackspace Cloudbuilders team has been improving some of the extensibility mechanisms and have provided some examples. I've added Jake Dahn to this thread so he can go into some more detail about how it works.
With respect to using quantum separately, I think that the project structure is strongly coupled enough to say that there isn't much value here. To be clear, a general python API around quantum is of course valuable, but trying to generalize the django components around quantum is probably going to cause more problems than it solves. To that end I for one would much prefer to see the quantum support refactored as a submodule instead of a top level django-quantum project. Happy to help or answer any questions about this. I saw the updated screenshots today and things are looking great! Best, Devin On Aug 8, 2011, at 2:22 PM, Arvind Somya wrote: > Hey Devin > > The integration is nearly complete, I'm just working on the final bits to > attach/detach ports from nova instances. > > I did start out similar to the swift container code in the dashboard with my > views and controllers within the django_openstack module but halfway through > I changed my mind and moved them to a separate module. > > I thought since Quantum is a project that can also be used outside openstack, > it might be nice to have a separate module that provides all the basic views > and operations without depending on nova. The templates are also contained > within django-quantum so publishing a django-quantum egg should enable any > other nova/non-nova clients to reuse the views. > > I'm fairly new to Django/Buildout and I could be totally wrong on the > approach. Should I roll up everything into django-openstack? Please let me > know the potential pitfalls/ shortcomings of my approach. > > Thanks > Arvind > > On 08/08/2011 04:45 PM, Devin Carlen wrote: >> >> Hey Dan, >> >> Thanks for the link! I'm excited to see that support for Quantum is being >> added to Dashboard. I did notice that a new module called django-quantum is >> added, but there is a slightly cleaner way to accomplish this without having >> to create a new top level module. I recommend looking at how we integrated >> Swift support recently. >> >> Let me know if you guys have any questions about the integration. I'm >> available to help! >> >> >> Best, >> >> Devin >> >> On Aug 8, 2011, at 11:39 AM, Dan Wendlandt wrote: >> >>> Hi Devin, >>> >>> Here's the pointer to the existing Quantum dashboard blueprint: >>> https://blueprints.launchpad.net/quantum/+spec/quantum-client-gui >>> >>> Mark Voelker's team at Cisco has been taking the lead on this and can >>> provide you with more details. Its currently targeted for Diablo-4. >>> >>> CC'ing the netstack list in case an impromptu design discussion ensures :) >>> >>> Dan >>> >>> >>> -- >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Dan Wendlandt >>> Nicira Networks, Inc. >>> www.nicira.com | www.openvswitch.org >>> Sr. Product Manager >>> cell: 650-906-2650 >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> >> >
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
