On Mon, Mar 26, 2012 at 2:48 AM, Deepak Garg <deepakgarg.i...@gmail.com>wrote:
> Thanks, I will keep this in mind. > > a. when this is well thought out, you may include it in Community Projects > b. Here's CLI auth bp sent to Netstack list in case you are catching > up with emails: http://wiki.openstack.org/QuantumCliAuth Great to see this BP. A few quick comments: - I suspect that if I specify a value (e.g., username) both with the flag (e.g., --username) and the environment, the flag takes precedence? - I've noticed devstack's stack.sh has a catalog entry for Quantum that have incorrect URLs. I think the URLs should include both the version and the tenant_id, just like nova and other services. - currently, all CLI commands take the tenant-id as the first ordered parameter. Now we get the tenant-name specified in the " OS_TENANT_NAME" environment variable or with the --os_tenant_name flag. Tenant-name is different from tenant-id though, so we need to use the tenant-name along with the username and password and pass that to keystone, which returns the service catalog which will include the tenant-id. This tenant-id can then be used in the Quantum URL. This should make it easier to type CLI commands :) Dan > > > > Cheers, > Deepak > > On Mon, Mar 26, 2012 at 2:52 PM, Dan Wendlandt <d...@nicira.com> wrote: > > There is a plan, currently files as one of the community projects. The > > trick is that there is a "quantum.common" namespace that is currently > used > > by both the client and the server. Thus, for now, they must share the > same > > namespace, as quantum.common needs to be useable by both. One of my > > suggested projects is splitting all code in quantum.common to be either > in > > the client or server repo. I think that is possible without much (or > any?) > > duplication. Once we do that, we can choose to have different namespaces > > for client and server. We will also get rid of the very confusing fact > that > > the server has to depend on the client for common code. > > > > dan > > > > > > On Mon, Mar 26, 2012 at 1:54 AM, Deepak Garg <deepakgarg.i...@gmail.com> > > wrote: > >> > >> HI Dan, > >> > >> In both the Quantum and Quantum client repos, the package is named as > >> 'quantum'. Its been a little confusing when importing modules. e.g. > >> > >> >>> from quantum.common import config > >> /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py:8: > >> UserWarning: Module quantum was already imported from > >> /opt/stack/quantum/quantum/__init__.pyc, but > >> /opt/stack/python-quantumclient is being added to sys.path > >> import pkg_resources > >> >>> from quantum import service > >> >>> from quantum import wsgi > >> >>> from quantum.common import serializer > >> >>> from quantum.openstack import common > >> > >> Modules get imported from both packages. Is there a reason for this > naming > >> ? > >> > >> e.g. find_config_file should really be in the quantum server repo and > >> not in the client repo. > >> > >> Nova uses 'nova' and 'novaclient' for package names. I understand > >> that changing the package name could be really painful but is there a > >> plan for this ? > >> > >> Thanks, > >> > >> Deepak Garg, > >> Data Center and Cloud Div. > >> Citrix R&D, India > >> Skype-id: deepakgarg.iit > > > > > > > > > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Dan Wendlandt > > Nicira Networks: www.nicira.com > > twitter: danwendlandt > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > -- > > Deepak Garg, > Data Center and Cloud Div. > Citrix R&D, India > Skype-id: deepakgarg.iit > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
