Guess the only advantage would be to minimize the chance of someone missing the
security related messages in the noise of a heavy traffic mailing list.
Even if there were a specialized list, I'd think you'd want to cross post
security issues to all lists, depending on severity (and with
In addition to looking at blueprints in launchpad, you might want to (start by)
view(ing) the following slide decks produced by some of the principal engineers
behind quantum. They were helpful to me in getting my arms around the
motivations behind quantum and openstack in general. As they say,
I'm I correct in believing that the Quantum L3 Abstractions and API Framework
(https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api) is the current
plan of record for bringing L2toL3 functionality (e.g., VXLAN/NVGRE) into
Quantum?
Is anyone signed up to do this or has this blueprint
from the blueprint both
would be plugin instances) is still a bit of a mystery to me, so I look forward
to whatever documentation appears.
Thanks,
syd
-Original Message-
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Friday, September 07, 2012 11:11 AM
To: Syd (Sydney) Logan
Cc
Backporting *would* duplicate work, by definition.
This is nothing new in the industry, the need to innovate and move forward is
always at odds with the need to support legacy deployments.
Seems to me quantum is a bit of an inflection point in the life of this rather
young platform, and
29, 2012 at 12:53 AM, Syd (Sydney) Logan
slo...@broadcom.commailto:slo...@broadcom.com wrote:
I played around with horizon a bit more and discovered that the demo project
page does have a Create Instance button, but when I try and do so I get an
error message saying that horizon is unable to get
Hi,
Is there a recommended procedure for upgrading nodes that were configured
pre-Folsom 3 to use quantum V1/OVS that were deployed with devstack? I probably
should have asked this question before trying, but I went ahead and tried. I
had a multi-node setup that I was driving with Horizon that
-cauth,horizon,mysql,rabbit,openstackx,q-svc,quantum,q-agt
Q_PLUGIN=openvswitch
Q_AUTH_STRATEGY=noauth
NOVA_USE_QUANTUM_API=v2
syd
From: Syd (Sydney) Logan
Sent: Tuesday, August 28, 2012 2:19 PM
To: 'openstack@lists.launchpad.net'
Subject: Upgrading from devstack pre-F3/quantum v1/OVS to latest
Hi,
I just posted the following at
http://forums.openstack.org/viewtopic.php?f=15t=1435, then realized this
mailing list might be a better place to ask the question.
In summary, I've cobbled together devstack-based nodes to exercise
quantum/openvswitch (when I say cobbled, I mean my result is
9 matches
Mail list logo
