[openstack-dev] [lbaas] [octavia] Proposing Lubosz Kosnik (diltram) as Octavia Core

2016-10-12 Thread Phillip Toohill
+1 good choice! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

2016-02-29 Thread Phillip Toohill
ST /v1/containers/d96dccd5-0d39-4f67-ba3a-366a84cfd371/consumers/ => generated 111 bytes in 63 msecs (HTTP/1.1 404) 4 headers in 179 bytes (1 switches on core 0) On Mon, Feb 29, 2016 at 1:40 PM, Phillip Toohill mailto:phillip.tooh...@rackspace.com>> wrote: To further my thoughts, as Ada

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

2016-02-29 Thread Phillip Toohill
-8d3014ab8e4d12d3346853d589a26319.r53.cf1.rackcdn.com/signatures/images/rackspace_logo.png] phone: 210-312-4366 mobile: 210-440-8374 From: Phillip Toohill Sent: Monday, February 29, 2016 3:33 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

2016-02-29 Thread Phillip Toohill
We could use some more information. Phillip V. Toohill III Software Developer [http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d589a26319.r53.cf1.rackcdn.com/signatures/images/rackspace_logo.png] phone: 210-312-4366 mobile: 210-440-8374 From: Madhusudhan Kand

Re: [openstack-dev] [Neutron][LBaaS] Regarding v2 LoadBalancer's status(es)

2015-12-14 Thread Phillip Toohill
>Yeah this needs to be better documented. I would say all of those >statuses in the docs pertain to provisioning_status, except for >INACTIVE, which I'm actually not sure where that is being used. ... There is this patch to utilize the INACTIVE status: https://review.openstack.org/#/c/255875/

Re: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for neutron-lbaas core team

2015-09-16 Thread Phillip Toohill
+1 Phillip V. Toohill III Software Developer phone: 210-312-4366 mobile: 210-440-8374 From: Eichberger, German [german.eichber...@hpe.com] Sent: Wednesday, September 16, 2015 5:44 PM To: OpenStack Development Mailing List (not for usage questions) Subjec

Re: [openstack-dev] [neutron][lbaas] questions about scenario tests

2015-07-27 Thread Phillip Toohill
?Wonder if this is the same behavior as the TLS scenario? I have some higher priorities but I am attempting to debug the TLS test in between doing other things. Ill let you know if I come across anything. Phillip V. Toohill III Software Developer [http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346

Re: [openstack-dev] [neutron][lbaas] Proposing Al Miller for neutron-lbaas core team

2015-07-02 Thread Phillip Toohill
) Subject: Re: [openstack-dev] [neutron][lbaas] Proposing Al Miller for neutron-lbaas core team +1 for me. Phil your message did not come through. On 7/2/15, 6:32 PM, "Phillip Toohill" wrote: > > >Phillip V. Toohill III >Software Developer > >phone: 210-31

Re: [openstack-dev] [neutron][lbaas] Proposing Al Miller for neutron-lbaas core team

2015-07-02 Thread Phillip Toohill
Phillip V. Toohill III Software Developer phone: 210-312-4366 mobile: 210-440-8374 From: Eichberger, German [german.eichber...@hp.com] Sent: Thursday, July 2, 2015 5:24 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [op

Re: [openstack-dev] [neutron][lbaas]Error at listener's barbican container validation

2015-06-04 Thread Phillip Toohill
I think there may just be some non-updated docstrings here. We should take only the 'ref'. If we get a UUID we wont know how to build it or what to do with it. The naming of this does need to change, but I dont' believe we need to convert UUID to ref. Is 'self.get_cert_ref_url(cert_ref)​' some

Re: [openstack-dev] [neutron][lbaas] adding lbaas core

2015-04-21 Thread Phillip Toohill
Thank you! Phillip V. Toohill III Software Developer phone: 210-312-4366 mobile: 210-440-8374 From: Brandon Logan Sent: Tuesday, April 21, 2015 11:57 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutr

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

2015-04-07 Thread Phillip Toohill
?Hey Evgeny, I believe Vivek is working on Horizon lbaasv2 support. We werent given a timeline or anything but sounds like its being actively worked on. I would reach out to him to get better timelines if concerned. Phillip V. Toohill III Software Developer [http://600a2794aa4ab5bae6bd-8d3014

Re: [openstack-dev] [neutron][lbaas] Can entity calls be made to driver when entities get associated/disassociated with root entity?

2015-02-04 Thread Phillip Toohill
Sharing/reusing pools is a planned future feature. We are currently trying to work towards getting something released and having shared pools would extend that timeline to not meet our expectations. From: Vijay Venkatachalam mailto:vijay.venkatacha...@citrix.com>> Reply-To: "OpenStack Developme

Re: [openstack-dev] [neutron] [lbaas] LBaaS Haproxy performance benchmarking

2015-02-04 Thread Phillip Toohill
+1 for Tsung! From: Adam Harwell mailto:adam.harw...@rackspace.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, February 4, 2015 9:25 AM To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [Octavia] Questions about the Octavia project

2015-01-06 Thread Phillip Toohill
Ill answer inline what I can, others can chime in to clear up anything and answer the rest. On 1/6/15 10:38 AM, "Andrew Hutchings" wrote: >Hi, > >I¹m looking into the Octavia project in relation to something my team are >working on inside HP and I have a bunch of questions. I realise it is >ea

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management

2014-10-15 Thread Phillip Toohill
ch a case, the VIP/Virtual Server with FLIP can be configured in the LB appliance. Meaning, LB appliance is now the “owner” of the FLIP and will be responding to ARPs. Thanks, Vijay V. From: Phillip Toohill [mailto:phillip.tooh...@rackspace.com] Sent: 15 October 2014 23:16 To: OpenStack Development

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management

2014-10-15 Thread Phillip Toohill
Thanks. Susanne On Mon, Oct 13, 2014 at 4:18 PM, Phillip Toohill mailto:phillip.tooh...@rackspace.com>> wrote: Diagrams in jpeg format.. On 10/12/14 10:06 PM, "Phillip Toohill" mailto:phillip.tooh...@rackspace.com>> wrote: >Hello all, > >Heres some additional di

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management

2014-10-15 Thread Phillip Toohill
always override the default plugin and driver layers and write our own and do whatever we want in them :) This allows vendors to rewrite implementations if they need to. Hopefully we’ll get the design well enough that they don’t have to do that in more than a few modules. Hope this helps! Please do

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management

2014-10-12 Thread Phillip Toohill
ure branch and not merged into Neutron master, so we can >change it pretty easily. Phil and I will bring this up in the meeting >tomorrow, which may lead to a meeting topic in the neutron lbaas >meeting. > >Thanks, >Brandon > > >On Mon, 2014-10-06 at 17:40 +, P

[openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management

2014-10-06 Thread Phillip Toohill
Hello All, I wanted to start a discussion on floating IP management and ultimately decide how the LBaaS group wants to handle the association. There is a need to utilize floating IPs(FLIP) and its API calls to associate a FLIP to the neutron port that we currently spin up. See DOCS here: > h

Re: [openstack-dev] [Neutron] Auth token in context

2014-07-18 Thread Phillip Toohill
n] Auth token in context What are you trying to use the token to do? On Fri, Jul 18, 2014 at 9:16 AM, Phillip Toohill mailto:phillip.tooh...@rackspace.com>> wrote: Excellent! Thank you for the response, I figured it was possible, just concerned me to why everything else made it to context

Re: [openstack-dev] [Neutron] Auth token in context

2014-07-18 Thread Phillip Toohill
request_id=req_id) >req.environ['neutron.context'] = ctx > >I think I'd better to report a bug for your case. > >Best Regards >Chaoyi Huang ( Joe Huang ) >-邮件原件- >发件人: Phillip Toohill [mailto:phillip.tooh...@rackspace.com] &

[openstack-dev] [Neutron] Auth token in context

2014-07-17 Thread Phillip Toohill
Hello all, I am wondering how to get the auth token from a user request passed down to the context so it can potentially be used by the plugin or driver? Thank you ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack

Re: [openstack-dev] [Neutron][LBaaS] Status of entities that do not exist in a driver backend

2014-07-03 Thread Phillip Toohill
If the objects remain in 'PENDING_CREATE' until provisioned it would seem that the process got stuck in that status and may be in a bad state from user perspective. I like the idea of QUEUED or similar to reference that the object has been accepted but not provisioned. Phil On 7/3/14 10:28 AM, "B

Re: [openstack-dev] [Neutron][LBaaS] and [Octavia] haproxy-1.5.0 is out

2014-06-20 Thread Phillip Toohill
Alright!!! I'll get to reworking the TLS support bp that didn't get too much attention. This is fantastic news, thanks for sharing! From: Stephen Balukoff [sbaluk...@bluebox.net] Sent: Friday, June 20, 2014 8:01 AM To: OpenStack Development Mailing List (no

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Mid Cycle Sprint

2014-06-17 Thread Phillip Toohill
Everyone is migrating to the new channel #openstack-lbaas From: Dustin Lundquist mailto:dus...@null-ptr.net>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, June 17, 2014 10:10 AM To: "OpenStack Development Mailin

Re: [openstack-dev] [Neutron][LBaaS] SSL re-encryption scenario question

2014-04-18 Thread Phillip Toohill
Hello Stephen, One use case we have, which was actually a highly requested feature for our service, was to ensure that traffic within the internal cloud network was not passed in the clear. I believe this mainly stems from the customers security requirements. I understand this reasoning to allo