* Dan Wendlandt (d...@nicira.com) wrote:
> We still have an unresolved discussion around having project-specific dev
> lists, raised by Chris Wright. My gut says that the right long-term
> approach is to have project specific *-dev lists, with a single "openstack"
> list for users questions and co
Hi David,
I'll leave the list operational for a bit (as I suspect some people will
have missed the announcement), but will redirect all discussions to the
main openstack list. I think having Quantum in the title of the email will
help us pick out relevant emails.
We still have an unresolved disc
Hi Gary,
quantum.common is actually part of quantumclient at present, so installing
python-quantumclient will resolve the problem you are seeing. There is a bug
and associated changes to remove this dependency:
https://bugs.launchpad.net/quantum/+bug/977711
Thanks,
Maru
On 2012-04-23, at
Hi Mandar,
If a question is quantum-specific, best to associated it with the "quantum"
project, not the "nova" project. Associating it with the Quantum project
will make sure that Quantum developers are notified. Most quantum
developers are not notified for each question asked about nova.
I've
On 04/22/2012 12:29 AM, Dan Wendlandt wrote:
Great Gary, thanks for finding and (soon) fixing these issues! Making
sure the open source plugins get more love in terms of system and
failure testing is very important.
Thanks. I am in the process of fixing the issues. I have updated the
following
5 matches
Mail list logo
