FUCK OFF
From: dava...@gmail.commailto:dava...@gmail.com
dava...@gmail.commailto:dava...@gmail.com
Reply-To:
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, August 3, 2015 at
Just starting this discussion…
This is in reference to
https://blueprints.launchpad.net/python-neutronclient/+spec/pluggable-neutronclient-auth
Originally the blueprint was for python-neutronclient only, but pluggable auth
is a wide-reaching issue. With OSC/SDK on the horizon (however far), we
I have uploaded it using the given link but I can't seem to find where people
can find it.
Thanks.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
are still meeting at 11:30.
From: Justin Hammond
justin.hamm...@rackspace.commailto:justin.hamm...@rackspace.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thu, 15 May 2014 03:16:13 +
I also intend on advertising this during the core-refactoring session in
the etherpad. Please pay attention to that if you're there!
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
John Voss and I believe Thursday (May 15) would be the best time to do
this. I will write it on the board.
On 5/14/14 11:59 AM, Justin Hammond justin.hamm...@rackspace.com wrote:
I also intend on advertising this during the core-refactoring session in
the etherpad. Please pay attention
Signed up for 11:30 AM, May 14 at the neutron POD.
On 5/14/14 12:29 PM, Justin Hammond justin.hamm...@rackspace.com wrote:
John Voss and I believe Thursday (May 15) would be the best time to do
this. I will write it on the board.
On 5/14/14 11:59 AM, Justin Hammond justin.hamm...@rackspace.com
) 665 14 28
Skype: max_lobur
38, Lenina ave. Kharkov, Ukraine
www.mirantis.comhttp://www.mirantis.com
www.mirantis.ruhttp://www.mirantis.ru
On Wed, May 14, 2014 at 8:06 PM, Justin Hammond
justin.hamm...@rackspace.commailto:justin.hamm...@rackspace.com wrote:
Signed up for 11:30 AM, May 14
I'm not sure if it was said, but which httplib using being used (urllib3
maybe?). Also I noticed many people were talking about supporting auth
properly, but are there any intentions to properly support 'noauth'
(python-neutronclient, for instance, doesn't support it properly as of
this writing)?
in 'trusted
environment'
It saves quite a few calls to identity in this way and scales a lot better.
On 1/16/14 11:06 AM, Dean Troyer dtro...@gmail.com wrote:
On Thu, Jan 16, 2014 at 9:37 AM, Jesse Noller
jesse.nol...@rackspace.com wrote:
On Jan 16, 2014, at 9:26 AM, Justin Hammond
justin.hamm
I am a developer who is currently having troubles keeping up with the
mailing list due to volume, and my inability to organize it in my client.
I am nearly forced to use Outlook 2011 for Mac and I have read and
attempted to implement
https://wiki.openstack.org/wiki/MailingListEtiquette but it is
We have been considering this and have some notes on our concept, but we
haven't made a blueprint for it. I will speak amongst my group and find
out what they think of making it more public.
On 10/29/13 12:26 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi Neutron devs,
Are there any plans to
I agree. +1. Mark has been nothing but helpful to me and I have enjoyed all the
chances I have had to work with him. Not sure if I can vote though.
From: Dan Wendlandt d...@nicira.commailto:d...@nicira.com
Reply-To: OpenStack Development Mailing List
The blueprint,
https://blueprints.launchpad.net/neutron/+spec/configurable-ip-allocation, was
started by Isaku Yamahata but was abandoned due to inactivity. We have
contacted Yamahata and he has agreed to partner with us on the development of
this blueprint. A majority of the preexisting
As it seems the review is no longer the place for this discussion, I will
copy/paste my inline comments here:
I dislike the idea of passing magical numbers around to define protocols
(defined or otherwise). I believe there should be a common set of
protocols with their numbers mapped (such as
I agree with you. Plugin was a mere example and it does make sense to
allow the provider to define custom protocols.
+1
On 9/11/13 12:46 PM, Akihiro Motoki amot...@gmail.com wrote:
Hi Justin,
My point is what
On Thu, Sep 12, 2013 at 12:46 AM, Justin Hammond
justin.hamm...@rackspace.com wrote
I am currently working this bug and I have a question about the scope of
the changes. The original description of the bug deals with constants
defined as TYPE_FLAT in multiple locations with the same value. It is
desired to have said constant put into common/constants.py and shared for
DRY-sake. I
you for your time,
Justin Hammond
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
18 matches
Mail list logo
