Hi All,
Following the Flavors discussion that was held on last Thursday, as promised,
here is a description of use cases and CLI commands to demonstrate Flavor usage.
I would appreciate your feedback and thoughts about it.
I prefer to do it on a mailing list first, since if we agree on this, it
Hi Ahana,
Neutron Flavors, as it is now, is just an initial implementation with no
scheduling or meta templating implemented.
The flavor actually has its identifiers ena/dis, and service type it belongs to.
The flavor profile has identifiers, driver FQN, ena/dis and metainfo (which has
no implem
Hi Ahana,
Neutron Flavors, as it is now, is just an initial implementation with no
scheduling or meta templating implemented.
The flavor actually has its identifiers ena/dis, and service type it belongs to.
The flavor profile has identifiers, driver FQN, ena/dis and metainfo (which has
no implem
0 at 18:36 +, Jain, Vivek wrote:
>> Hi Evgeny,
>> Did you add “loadbalancerv2" dir next to “loadbalancer” under
>> openstack_dashboard/dashboards/project/ ?
>>
>>
>> Thanks,
>> Vivek
>>
>>
>> From: Evgeny Fedoruk
>> Rep
will greatly speedup our horizon integration.
>>
>> Thanks,
>> Vivek
>>
>> From: Phillip Toohill
>> mailto:phillip.tooh...@rackspace.com><mailto:phillip.tooh...@rackspace.com<mailto:phillip.tooh...@rackspace.com>>>
>> Reply-To: "OpenStack
Hi All,
Here is L7 work tasks etherpad
https://etherpad.openstack.org/p/Neutron_LBaaS_v2_-_L7_work_tasks
Please review and comment
Evg
-Original Message-
From: Evgeny Fedoruk [mailto:evge...@radware.com]
Sent: Wednesday, August 26, 2015 8:45 PM
To: Samuel Bercovici; OpenStack
/204957
Evg
-Original Message-
From: Samuel Bercovici
Sent: Wednesday, August 26, 2015 4:22 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Evgeny Fedoruk
Subject: RE: [openstack-dev] [neutron][lbaas] L7 - Tasks
Hi,
I think that Evgeny is trying to complete
Hello
I would like to know if there is a plan for L7 extension work for Liberty
There is an extension patch-set here https://review.openstack.org/#/c/148232/
We will also need to do a CLI work which I started to do and will commit
initial patch-set soon
Reference implementation was started by Ste
Brandon, thank you.
I’ve pushed a fix for this issue https://review.openstack.org/#/c/201044
Evg
From: Brandon Logan [mailto:brandon.lo...@rackspace.com]
Sent: Friday, July 10, 2015 7:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [neutron][lbaas
Hi All,
Does anyone know on which IRC channel the GSLB API meeting is happening?
Thanks,
Evg
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
ing actively worked on. I would
reach out to him to get better timelines if concerned.
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
___
Hi guys,
LBaaS v2 has no horizon support as for now and I want to know if this work is
planned to be done and , if yes, in what time frame.
Is there a plan to develop it for Kilo or for L release?
Thanks,
Evg
__
OpenStack De
until the Neutron WSGI Refactor is
completed so it's easier for them to test all extensions and that nothing
breaks. I do believe the plan is to move the extensions into the service repos
once this is completed.
Thanks,
Brandon
On Sun, 2014-12-21 at 10:14 +0000, Evgeny Fedoruk wrote:
>
Hi Doug,
How are you?
I have a question regarding https://review.openstack.org/#/c/141247/ change set
Extension changes are not part of this change. I also see the whole extension
mechanism is out of the new repository.
I may be missed something. Are we replacing the mechanism with something els
Hi Doug,
Thanks for a reminder,
Res-submitted following three for kilo:
LBaaS Layer 7 rules - https://review.openstack.org/#/c/139853/
Neutron LBaaS TLS - https://review.openstack.org/#/c/139852
Radware LBaaS Driver - https://review.openstack.org/#/c/139854/
Thanks,
Evg
-
gt; >
> > > On Nov 10, 2014, at 10:33 AM, Evgeny Fedoruk
> wrote:
> > >
> > > Thanks,
> > > Evg
> > >
> > >
Hi Doug,
On which channel?
Thanks,
Evg
-Original Message-
From: Doug Wiegley [mailto:do...@a10networks.com]
Sent: Friday, November 07, 2014 9:04 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [neutron][lbaas] meeting day/time change
Hi all,
Neutron LBaaS meetings ar
Hi folks,
Since pyasn1_modules is needed by our new common Barbican interactions module,
The package was added to the neutron requirements file by the
https://review.openstack.org/#/c/109849/ change set.
Gate checks are failing now because this new pyasn1_modules requirement should
be added to t
endent commit setup
> 4. Create your topic branch
> 5. Cherry-pick your commit from gerrit into your new topic branch
> 6. Use "git log -n5 --decorate --pretty=oneline”, and verify that
> your dependency commit hashes match what’s in gerrit.
> 7. Git r
Hi folks,
I'm working on a change for neutron LBaaS service.
Since there is a massive work done for LBaaS these days, my change depends on
other changes being reviewed in parallel in gerrit.
I don't have a big git knowledge and I'm failing in figuring out the right
procedure that should be follo
1:06 AM, Carlos Garza
wrote:
> I'Just park a module with a stub call that I can populate with pyasn1.
> On Jul 24, 2014, at 10:38 AM, Evgeny Fedoruk
> wrote:
>
>> Hi,
>>
>> Following our talk on TLS work items split, We need to decide how
>> will we validat
Hi,
Following our talk on TLS work items split,
We need to decide how will we validate/extract certificates Barbican TLS
containers.
As we agreed on IRC, the first priority should be certificates fetching.
TLS RST describes a new common module that will be used by LBaaS API and LBaaS
drivers.
I
error for non-TLS
> v2 drivers? Or must all v2 drivers support TLS?
>
> doug
>
>
>
> On 7/23/14, 10:54 AM, "Evgeny Fedoruk" wrote:
>
> >My code is here:
> >https://review.openstack.org/#/c/109035/1
> >
> >
> >
> >-Or
My code is here:
https://review.openstack.org/#/c/109035/1
-Original Message-
From: Evgeny Fedoruk
Sent: Wednesday, July 23, 2014 6:54 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [Neutron][LBaaS] TLS capability - work division
Hi
Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] TLS capability - work division
Do you have any idea as to how we can split up the work?
On Jul 23, 2014, at 6:01 AM, Evgeny Fedoruk
wrote:
> Hi,
>
> I'm working on TLS integration with l
Hi,
I'm working on TLS integration with loadbalancer v2 extension and db.
Basing on Brandon's patches https://review.openstack.org/#/c/105609 ,
https://review.openstack.org/#/c/105331/ ,
https://review.openstack.org/#/c/105610/
I will abandon previous 2 patches for TLS which are
https://revie
Hi folks,
In a current version of TLS capabilities RST certificate SubjectCommonName and
SubjectAltName information is cached in a database.
This may be not necessary and here is why:
1. TLS containers are immutable, meaning once a container was associated
to a listener and was validated
i,
> >
> > My impression was that the frontend would extract the names and hand them
> > to the driver. This has the following advantages:
> >
> > · We can be sure all drivers can extract the same names
> > · No duplicate code to maintain
> >
o duplicate code to maintain
> · If we ever allow the user to specify the names on UI rather in the
> certificate the driver doesn’t need to change.
>
> I think I saw Adam say something similar in a comment to the code.
>
> Thanks,
> German
>
> From: Evgeny Fedoruk [
Hi All,
Since this issue came up from TLS capabilities RST doc review, I opened a ML
thread for it to make the decision.
Currently, the document says:
"
For SNI functionality, tenant will supply list of TLS containers in specific
Order.
In case when specific back-end is not able to support SNI c
he invalidation
> * Naming things
> * Off-by-one errors
>
>
> And far be it from me to pick nits about a name (OK, I guess it's
> isn't that far fetched for me to pick nits. :P ), but it's hard for me
> to imagine a worse name than 'listenersniassocaitions&
settings for listener
be set through separate API/model?
>>SNI list is managed by separate entity
What is this entity?
From: Evgeny Fedoruk [mailto:evge...@radware.com]
Sent: Tuesday, June 24, 2014 12:25 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [opensta
+1 for option 1. SNI list is managed by separate entity, default TLS container
is part of a listener object. It will have None value when listener does not
offloads TLS.
Managing another entity for 1:0-1 relationship just for future use seems not
right to me. Breaking TLS settings apart from lis
and will change the document accordingly.
Thanks,
Evg
-Original Message-
From: Evgeny Fedoruk
Sent: Sunday, June 15, 2014 1:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] TLS support RST document on Gerrit
Hi All
allow adding meta data on the
>>container so that
>>> the user will be aware which listeners use this container. This is
>>optional. It
>>> can also be optional for LBaaS to implement adding the listeners ID
>>> automatically into this metadata just for information.
>>> >
t;registration" will be removed when VIP listener stops using the
certificate?
Please comment on these points and review the document on gerrit
(https://review.openstack.org/#/c/98640)
I will update the document with decisions on above topics.
Thank you!
Evgeny
From: Evgeny Fedoruk
Sent: M
-
From: Samuel Bercovici
Sent: Monday, June 09, 2014 9:49 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Samuel Bercovici; Evgeny Fedoruk
Subject: RE: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS
Integration Ideas
Hi,
I think that option 2 should be preferred
Hi All,
A Spec. RST document for LBaaS TLS support was added to Gerrit for review
https://review.openstack.org/#/c/98640
You are welcome to start commenting it for any open discussions.
I tried to address each aspect being discussed, please add comments about
missing things.
Thanks,
E
Hi All,
LBaaS SSL support wiki page was updated with up-to-date design decisions:
1. SSL offload is a core LBaaS feature
2. Certificate's private key is always transient until secure storage is
available
https://wiki.openstack.org/wiki/Neutron/LBaaS/
Eugene, you might want to add
Hi All,
I just cloned master devstack and stacked.
Nova-compute fails while trying to load libvirt driver
Log:
Loading compute driver 'libvirt.LibvirtDriver'^[[00m
2014-01-13 08:20:01.228 ^[[01;31mERROR nova.virt.driver [^[[00;36m-^[[01;31m]
^[[01;35m^[[01;31mUnable to load the virtualization
ggestion is to call the property as certificate
Thanks,
Vijay V.
> -----Original Message-
> From: Evgeny Fedoruk [mailto:evge...@radware.com]
> Sent: Sunday, December 08, 2013 10:24 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [N
(not for usage questions)
Cc: Evgeny Fedoruk; Samuel Bercovici
Subject: RE: [openstack-dev] [Neutron][LBaaS] Vote required for certificate as
first-class citizen - SSL Termination (Revised)
Correct.
Evgeny will update the WIKI accordingly.
We will add a flag in the SSL Certificate to allow
Hello All,
Extending quota mechanism to support vips, pools, members and health-monitors
Blueprint is not approved yet.
Changes are ready for review
Blueprint:
https://blueprints.launchpad.net/neutron/+spec/neutron-quota-extension
Related changes for review:
neutron - https://review.opensta
Hi,
I've updated the wiki page
Please see and comment
https://wiki.openstack.org/wiki/Neutron/LBaaS/SSL
Thanks,
Evg
-Original Message-
From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com]
Sent: Wednesday, November 20, 2013 4:17 PM
To: Samuel Bercovici; OpenStack Development
44 matches
Mail list logo
