? https://review.openstack.org/#/c/98640/
Thanks,
Stephen
On Thu, Jun 19, 2014 at 6:23 AM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Hi Samuel,
Yes, it's more friendly to extract this information on behalf of the user,
but does occasionally break use cases we've seen. It should be possible
of
LBaaS in the last few months who are also interested in contributing to the
Octavia project.
Who would you like to see as PTL and core developers in this project?
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, Inc.
(800)613-4305 x807
___
OpenStack
and Doug Wiegley as core members.
On Thu, Jun 19, 2014 at 6:18 PM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Howdy y'all!
Among other things that happened at the Neutron LBaaS mid-cycle
hackathon,
we have now put together process around, and established Octavia as a
stackforge
contributing
to Neutron LBaaS related code or specs, people I recognize being active in
the IRC meetings, etc. I come up with the following list. Apologies in
advance for anyone I've forgotten here; errors are entirely my fault:
Avishay Balderman
Susanne Balle
Stephen Balukoff
Samuel Bercovici
Vijay
mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
multiple matches, the 1st one will be used
3. If no match was found than try to use subjectAltName to match. If
you have multiple matches, the 1st one will be used
4. If no match than use default certificate
-Sam.
*From:* Stephen Balukoff [mailto:sbaluk...@bluebox.net
of
complexity for what is gained.
doug
From: Stephen Balukoff sbaluk...@bluebox.net
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Tuesday, June 10, 2014 at 1:47 PM
To: OpenStack Development Mailing List (not for usage questions
/pointer to
certificate?
Thanks,
Vijay V.
From: Stephen Balukoff [mailto:sbaluk...@bluebox.net]
Sent: Tuesday, June 10, 2014 7:43 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS
Integration Ideas
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
topics.
I shall try to make sure I have time to review the document later today or
tomorrow.
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack
of
complexity for what is gained.
doug
From: Stephen Balukoff sbaluk...@bluebox.net
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Tuesday, June 10, 2014 at 1:47 PM
To: OpenStack Development Mailing List (not for usage
a fair bit of
complexity for what is gained.
doug
From: Stephen Balukoff sbaluk...@bluebox.net
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Tuesday, June 10, 2014 at 1:47 PM
To: OpenStack Development Mailing List
will not result in lbaas breaking, I think. The
shadow copy would only get used if the lb had to be re-provisioned for some
reason before it was given a new key id, which seems a fair bit of
complexity for what is gained.
doug
From: Stephen Balukoff sbaluk...@bluebox.net
Reply-To: OpenStack
working on the API revision but I
wanted to take a step back and look at the goal we are trying to solve and
weigh the perceived need for complexity (i.e flexibility in the API) vs
a simpler solution.
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
make the haproxy logs available. Which
contain connection information like from, to, duration, protocol, status
(though
we frequently have been told that this is not really useful for
debuggingŠ) and of course having that more gui-fied would be neat
German
From: Stephen Balukoff
of depended entities is called
Heat.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
a bit but relationship conversations has
stalled that some. I think if we can go with this route it will make
the code much more clear.
Thanks,
Brandon
Yep, knowing this is going to be key to where we need to put engineering
time into this, eh.
Stephen
--
Stephen Balukoff
Blue Box Group
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
)?
· Deletion of shared objects
o Do we support deletion of shared objects that will cascade delete?
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
is suggesting we try to make the old
schema work for the new API.
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
users asking for or
accustomed to seeing?
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
would
be appreciated!)
Thanks,
Stephen
On Mon, May 19, 2014 at 4:45 PM, Stephen Balukoff sbaluk...@bluebox.netwrote:
Hi folks,
Ok, I've attached a newly-updated object diagram (and its source) which is
hopefully both a little bit clearer than the monstrosity I created for the
summit, and also
more productive with less crosstalk.
Thoughts?
Best,
Craig
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613
, etc.
Best,
Craig
On Wed, May 14, 2014 at 1:32 PM, Stephen Balukoff
sbaluk...@bluebox.netwrote:
Aah-- and here's a small error correction. :)
Please also note:
* We're not yet in consensus on the L7 or SSL related objects, but the
Loadbalancer, Listener, Pool, and Member should
Hi Eugene,
A couple notes of clarification:
On Sat, May 10, 2014 at 2:30 AM, Eugene Nikanorov
enikano...@mirantis.comwrote:
On Fri, May 9, 2014 at 10:25 PM, Stephen Balukoff
sbaluk...@bluebox.netwrote:
Hi Eugene,
This assumes that 'VIP' is an entity that can contain both an IPv4
@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
features.
I can publish the results in time for the 2nd LBaaS meeting (so deadline
would be end of 15th May “summit time”)
Is this acceptable?
-Sam.
*From:* Stephen Balukoff [mailto:sbaluk...@bluebox.netsbaluk...@bluebox.net]
*Sent:* Thursday, May 08, 2014 2:17 AM
*To:* OpenStack
with very basic load balancing needs: No (mostly, though
to many it's still yes)
* To larger customers with advanced load balancing needs: Yes.
* To operators of any size: Yes.
I've outlined my reasoning for thinking so in the other discussion thread.
Thanks,
Stephen
--
Stephen Balukoff
Blue Box
.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack
if this is acceptable.
Regards,
-Sam.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
:
Lets go over the Rackspace portion of the API comparison tomorrow
then, and we can cover Stephen's on the ML when it's complete.
On Wed, May 7, 2014 at 4:55 AM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Howdy, y'all!
I just wanted to give you a quick update: It looks like the Rackspace
for manipulating their objects, what do
we care if those who are going to use single-call would rather do this
through the listener / load balancer object?
And... that's about it. Sorry for the length of this e-mail, y'all!
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
agreement. :)
Does anyone actually *oppose* this arrangement?
--Adam
*From: *Stephen Balukoff sbaluk...@bluebox.net
*Reply-To: *OpenStack Development Mailing List (not for usage
questions) openstack-dev@lists.openstack.org
*Date: *Friday, May 2, 2014 7:53 PM
*To: *OpenStack Development
a list of capabilities.
-Sam.
*From:* Stephen Balukoff [mailto:sbaluk...@bluebox.net]
*Sent:* Saturday, May 03, 2014 1:33 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Neutron][LBaaS]L7 conent switching APIs
Hi Adam and Samuel
think this is too strange an edge case to be covered by the LBaaS. In
any case I am wondering if there is a valid use case if we can add it to
the user stories.
German
*From:* Stephen Balukoff [mailto:sbaluk...@bluebox.net]
*Sent:* Monday, May 05, 2014 4:05 PM
*To:* OpenStack Development
confusing thing to do for the user? What are
others' thoughts on this?
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
route to use to access such
member(s).
On many cases the needed static routes could also be computed
automatically.
Regards,
-Sam.
On 2 במאי 2014, at 03:50, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Hi Trevor,
I was the one who wrote that use case based
/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev
-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
Jorge,
In looking over your API proposal linked above, have things significantly
changed there since you sent it out two weeks ago? (And if so, which parts
should I take a look at again?)
Thanks,
Stephen
On Wed, Apr 30, 2014 at 5:07 PM, Stephen Balukoff sbaluk...@bluebox.netwrote:
Hi Jorge
: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
On Mon, Apr 28, 2014 at 6:23 PM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Hi guys,
Sorry for all the drama on the list lately.
Not a problem. Like I said, the passion from all sides is great, and I'm
especially happy to see
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to make iterative
progress and also to work on items in parallel.
Thanks again for the great document!
Right.
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
as a web application available via a single IP.
-Trevor Vardeman
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305
discussion about this going on in another mailing list thread-- and now
that I'm not neck deep in API documentation I'll probably jump back onto
this in the next couple of days.)
And... I think that's about it. Please have fun ripping this draft to
shreds!
Thanks,
Stephen
--
Stephen
...
which is of course not the same one we've been discussing here. XD)
What did you have in mind, as far as a POC is concerned?
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev
cases.
Please add additional use cases based on your experience.
Regards,
-Sam.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen
be chained. So in our case we might want to chain a firewall to a load
balancer to a VPN to get the functionality we want.
Thoughts?
German
*From:* Stephen Balukoff [mailto:sbaluk...@bluebox.net]
*Sent:* Friday, April 18, 2014 9:07 PM
*To:* OpenStack Development Mailing List
a few ask
about it, usually because they didn't understand what a load balancer is
supposed to do-- and with a bit of explanation they went either with SSL
termination on the load balancer + clear text on the back-end, or just
straight TCP load balancing.)
Thanks,
Stephen
--
Stephen Balukoff
is not completely private and the
sensitive information needs to be again transmitted encrypted. This is
admittedly an edge case but we had to implement a similar scheme for HP
Cloud’s swift storage.
German
*From:* Stephen Balukoff [mailto:sbaluk...@bluebox.net]
*Sent:* Friday, April 18, 2014 8:22
users using
inconsistently-signed or per-node self-signed certs in a single pool?
Thanks,
Stephen
On Fri, Apr 18, 2014 at 5:56 PM, Carlos Garza carlos.ga...@rackspace.comwrote:
On Apr 18, 2014, at 12:36 PM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Dang. I was hoping this wasn't
.)
What do y'all think of the above idea?
Thanks,
Stephen
On Fri, Apr 18, 2014 at 2:35 PM, Carlos Garza carlos.ga...@rackspace.comwrote:
On Apr 17, 2014, at 8:39 PM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Hello German and Brandon!
Responses in-line:
On Thu, Apr 17, 2014
to manipulating primitives?
Thanks!
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-call-API-discussion-tp38533p38542.html
Sent from the Developer mailing list archive at Nabble.com.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen
Oh! One other question:
5. Should single-call stuff work for the lifecycle of a load balancing
service? That is to say, should delete functionality also clean up all
primitives associated with the service?
On Thu, Apr 17, 2014 at 11:44 AM, Stephen Balukoff sbaluk...@bluebox.netwrote:
Hi Sri
things more friendly for the OpenStack environment,
which we understand probably isn't ready for layer-3 routing just yet).
8. I wrote this survey, so none come to mind for me. :)
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
(redudant, I know). In the case of HaProxy it would
just add the second port to the same config that the first load balancer
was using. In other drivers it might be different.
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
Hello German and Brandon!
Responses in-line:
On Thu, Apr 17, 2014 at 3:46 PM, Brandon Logan
brandon.lo...@rackspace.comwrote:
Stephen,
I have responded to your questions below.
On 04/17/2014 01:02 PM, Stephen Balukoff wrote:
Howdy folks!
Based on this morning's IRC meeting
, Stephen Balukoff wrote:
Hi Brandon!
Per the meeting this morning, I seem to recall you were looking to have
me elaborate on why the term 'load balancer' as used in your API proposal
is significantly different from the term 'load balancer' as used in the
glossary at: https
@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron][LBaaS] Requirements and API
revision progress
Hi Stephen,
Thanks for a good summary. Some comments inline.
On Tue, Apr 15, 2014 at 5:20 AM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
So! On this front:
1. Does is make
...@gmail.com
wrote:
More additions to the use cases (
https://wiki.openstack.org/wiki/Neutron/LBaaS/Usecases).
I have updated some of the features we are interested in.
Thanks,
Prashanth
On Wed, Apr 2, 2014 at 8:12 PM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
Hi y'all
/openstack-network/2.0/content/ch_preface.html
but this seems like it might be a little heavy for an API draft that
is
likely to get altered significantly, especially given how this discussion
has gone thus far. :/ )
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
having this functionality now.
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
such a thing still being sold in 2014? ;)
Also, Jorge-- thanks for creating that page! I've made a few additions to
it as well that I'd love to see prioritized.
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openst...@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
:
On Feb 25, 2014, at 10:10 AM, Stephen Balukoff sbaluk...@bluebox.net
wrote:
On Feb 25, 2014 at 3:39 AM, enikano...@mirantis.com wrote:
Agree, however actual hardware is beyond logical LBaaS API but could
be a part of admin LBaaS API.
Aah yes-- In my opinion, users should almost
-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
among our largest clients, we rarely see them re-using
pools, or having pools associated with multiple listeners. So, this might
be a moot point for the 90% use case anyway.
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
of them is the
default.
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
not remove this as a choice.
+1
-Sam.
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev
Oh! One thing I forgot to mention below:
On Sat, Feb 15, 2014 at 11:55 PM, Avishay Balderman avish...@radware.comwrote:
Entity: L7Rule
Field : compare_type
Description: The way we compare the value against a given value
Possible values: REG_EXP, EQ, GT, LT,EQ_IGNORE_CASE,(?)
*Note*:
-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
is not a floating ip,
but an ip on the internal tenant network with a neutron port. So ip
uniqueness is enforced at port level and not at VIP level. We need to allow
VIPs to share the port, that is a part of multiple-vips-per-pool blueprint.
Thanks,
Eugene.
--
Stephen Balukoff
Blue Box Group
balancer API which is already addressed:
· Multiple pools per VIP (ie. “layer 7” support) -
https://blueprints.launchpad.net/neutron/+spec/lbaas-l7-rules.
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev
rules and associations, we're inherently going
to have an haproxy bias. :)
And again, I'm OK with this. :)
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
enikano...@mirantis.comwrote:
Hi folks,
Lets gather as usual on #openstack-meeting on Thursday, 13 at 14-00 UTC
The updated agenda for our regular meeting is here:
https://wiki.openstack.org/wiki/Network/LBaaS
In addition to that I'd like to discuss some ideas that Stephen Balukoff
has proposed
case going to be confusing for new comers
expecting it to be one thing when it's actually another.
Thanks,
Stephen
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
that generally out of scope of Neutron project
and more in the scope of Heat project.
Automated provisioning of load balancer devices as was said is what
'service vm framework' is trying to address.
--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
101 - 193 of 193 matches
Mail list logo
