Re: [openstack-dev] [neutron][vpnaas] VPNaaS tox api failure

[Madhusudhan Kandadai]

Hi Bharath,

Yes. Did you have this patch https://review.openstack.org/#/c/281493/
before you run "tox -e api" ? There was a change in neutron that removed
vpn and fw tests and its in their tree. However, to make it work for vpn
api tests, we need to figure out a way to implement the changes in vpn
tree. However for time being, patch 281493 needs to be cherry picked until
we get a timeline to implement in vpnaas tree.

If you have cycles, feel free to take on
https://review.openstack.org/#/c/281493 and once that merges,
https://review.openstack.org/#/c/279787/ is the traditional way of running
tempest tests using tempest plugin. Hope this helps.

Regards,
Madhu

On Mon, Apr 25, 2016 at 11:14 AM, Bharath Kumar Gubbala  wrote:

> Hi Henry,
>
>
> Do you have any info on below query in the thread.(is 'tox -e api' working
> in neutron-vpnaas ?)
>
>
>
> Thanks,
>
> bharath
>
>
> --
> *From:* bharath 
> *Sent:* 08 April 2016 01:53
> *To:* OpenStack Development Mailing List (not for usage questions); Alex
> Geevarghese; madhusudhan.openst...@gmail.com; p...@michali.net
> *Subject:* Re: [openstack-dev] [neutron][vpnaas] VPNaaS tox api failure
>
> Thanks Paul for info.
>
> Yes i had run the tests locally under VPN-repo.
>
> My analysis:
>
>- VPN test cases were using the neutron client for VPN
>services (which no longer supported by neutron).
>
>  Thats why its throwing "tempest.lib.exceptions.NotFound:
> Object not found"
>
>- In the case of FW , there were using router client directly
>instead of neutron client.
>
>
>
> I will check with madhusudhan for additional info.
>
>
>
> Madhu,
> Let me know if you have info on "tox api" support.
> If it is an known issue, i can take it up and complete fix
>
> Thanks,
> bharath
>
>
>
>
> On Friday 08 April 2016 01:00 AM, Paul Michali wrote:
>
> Are you running the test locally?
>
> IIRC, the tempest based API tests for VPN have been (are being) moved to
> the VPN repo, but I don't know if a job was ever created for this so that
> the tests actually run. You may want to check with the author who moved the
> tests (madhusudan-kandadai) under commit 3cae934a, to see if the CI job was
> ever created. It is possible that it was never completed.
>
> Likewise, I don't know if support was added to tox.ini for the api test.
> I've never run the test, granted I've been away from VPN for a while and
> only involved intermittently since Liberty, so I may be a bit out of touch.
>
> Regards,
>
> PCM
>
>
> On Thu, Apr 7, 2016 at 2:23 PM bharath  wrote:
>
>>
>> Hi,
>>
>> While running "tox -e api" i hitting " tempest.lib.NotFound" Error.
>>
>> Is it a known issue ? failures expected?
>>
>> https://review.openstack.org/#/c/291949/1
>> 
>> ==> In this commit messages it says it kindof expected failure.
>>
>> Can someone provide some clarification on this
>>
>> Thanks,
>> bharath
>> __
>> 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
>> 
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttps://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=CwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=87NL1fmn9sX2yN6wRmckSjVQpenT6rqPI7fvK0O5yfk&m=9pS9SGHSr62ETR_Qt_kSEpw9f-DjUThD6EYZ90W4cyU&s=ajURyED5NOlDi3x19ZS_layCPNAtjp7vjElGBLVMOtQ&e=
>
>
>
__
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

[Madhusudhan Kandadai]

Okay, Figured out the issue.When debugging, I was trying to create lb and
barbican clients with different users. Thanks guys!

On Mon, Feb 29, 2016 at 2:07 PM, Phillip Toohill <
phillip.tooh...@rackspace.com> wrote:

> Is the create LB happening on a different user than the one that created
> the barbican container? Maybe im not looking at it right, but cant tell
> from this.
>
>
> Phillip V. Toohill III
> Software Developer
> phone: 210-312-4366
> mobile: 210-440-8374
>
>
>
> ------
> *From:* Madhusudhan Kandadai 
> *Sent:* Monday, February 29, 2016 3:47 PM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container
> could not be found
>
> Is what I can see the error logs in barbican svc screen while I create TLS
> listener like this: http://paste.openstack.org/show/xVl9iuJtGW03fCGetDm3/
>
> 2016-02-29 13:42:55.222 INFO barbican.api.middleware.context
> [req-65fd0f08-4c1e-4b2f-9cbd-64f186365077 afaa5d797f3543369d05e370a543ef9d
> c141e106a7424d1a8316cf03a8c91e40] Processed request: 404 Not Found - POST
> http://192.168.109.129:9311/v1/containers/d96dccd5-0d39-4f67-ba3a-366a84cfd371/consumers/
> {address space usage: 220770304 bytes/210MB} {rss usage: 101371904
> bytes/96MB} [pid: 52558|app: 0|req: 75/75] 192.168.109.129 () {34 vars in
> 598 bytes} [Mon Feb 29 13:42:55 2016] POST
> /v1/containers/d96dccd5-0d39-4f67-ba3a-366a84cfd371/consumers/ => generated
> 111 bytes in 214 msecs (HTTP/1.1 404) 4 headers in 179 bytes (1 switches on
> core 0)
> 2016-02-29 13:43:17.397 ERROR barbican.model.repositories
> [req-0554f272-f711-49b7-a1f7-3b8bc87b431b afaa5d797f3543369d05e370a543ef9d
> c141e106a7424d1a8316cf03a8c91e40] Not found for
> d96dccd5-0d39-4f67-ba3a-366a84cfd371
> 2016-02-29 13:43:17.397 TRACE barbican.model.repositories Traceback (most
> recent call last):
> 2016-02-29 13:43:17.397 TRACE barbican.model.repositories   File
> "/opt/stack/barbican/barbican/model/repositories.py", line 354, in get
> 2016-02-29 13:43:17.397 TRACE barbican.model.repositories entity =
> query.one()
> 2016-02-29 13:43:17.397 TRACE barbican.model.repositories   File
> "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line
> 2699, in one
> 2016-02-29 13:43:17.397 TRACE barbican.model.repositories raise
> orm_exc.NoResultFound("No row was found for one()")
> 2016-02-29 13:43:17.397 TRACE barbican.model.repositories NoResultFound:
> No row was found for one()
> 2016-02-29 13:43:17.397 TRACE barbican.model.repositories
> 2016-02-29 13:43:17.398 ERROR barbican.api.controllers
> [req-0554f272-f711-49b7-a1f7-3b8bc87b431b afaa5d797f3543369d05e370a543ef9d
> c141e106a7424d1a8316cf03a8c91e40] Webob error seen
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers Traceback (most
> recent call last):
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers   File
> "/opt/stack/barbican/barbican/api/controllers/__init__.py", line 104, in
> handler
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers return fn(inst,
> *args, **kwargs)
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers   File
> "/opt/stack/barbican/barbican/api/controllers/__init__.py", line 90, in
> enforcer
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers return fn(inst,
> *args, **kwargs)
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers   File
> "/opt/stack/barbican/barbican/api/controllers/__init__.py", line 146, in
> content_types_enforcer
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers return fn(inst,
> *args, **kwargs)
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers   File
> "/opt/stack/barbican/barbican/api/controllers/consumers.py", line 143, in
> on_post
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers
> controllers.containers.container_not_found()
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers   File
> "/opt/stack/barbican/barbican/api/controllers/containers.py", line 36, in
> container_not_found
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers
> pecan.abort(404, u._('Not Found. Sorry but your container is in '
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers   File
> "/usr/local/lib/python2.7/dist-packages/pecan/core.py", line 141, in abort
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers exec('raise
> webob_exception, None, traceback')
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers   File
> "/opt/stack/barbican/barbican/api/controllers/consumers.py", line 141, in
> on_post
> 2016-02-29 13:43:17.398 TRACE barbican.api.controllers

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

[Madhusudhan Kandadai]

:43:17 2016] POST
/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 <
phillip.tooh...@rackspace.com> wrote:

> To further my thoughts, as Adam mentioned, it could be a user issue, which
> to me is what it sounds like. So being able to view the config and have
> other information is pertinent to solving the issue.
>
>
> Phillip V. Toohill III
> Software Developer
> 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] [Neutron][LBaaS][barbican]TLS container
> could not be found
>
>
> We could use some more information.
>
>
> Phillip V. Toohill III
> Software Developer
> phone: 210-312-4366
> mobile: 210-440-8374
>
>
>
> --
> *From:* Madhusudhan Kandadai 
> *Sent:* Monday, February 29, 2016 3:21 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container
> could not be found
>
> Wondering, have you guys figured out this issue? I am seeing the same
> problem that Jiahao is getting.
>
> On Thu, Feb 4, 2016 at 9:53 AM, Adam Harwell 
> wrote:
>
>> Could you provide your neutron-lbaas.conf? Depending on what version
>> you're using, barbican may not be the default secret backend (I believe
>> this has been fixed). Alternatively, it depends on what user accounts are
>> involved -- this should definitely work if you are using only the single
>> admin account, but we haven't done a lot of testing around the ACLs yet to
>> make sure they are working (and I believe there is still an outstanding bug
>> in Barbican that would cause the ACLs to not function properly in our
>> use-case).
>>
>>
>> --Adam
>>
>>
>> --
>> *From:* Jiahao Liang 
>> *Sent:* Thursday, January 28, 2016 12:18 AM
>> *To:* openstack-dev@lists.openstack.org
>> *Subject:* [openstack-dev] [Neutron][LBaaS][barbican]TLS container could
>> not be found
>>
>> Hi community,
>>
>> I was going through
>> https://wiki.openstack.org/wiki/Network/LBaaS/docs/how-to-create-tls-loadbalancer
>>  with
>> devstack. I was stuck at a point when I tried to create a listener within a
>> loadbalancer with this command:
>>
>> neutron lbaas-listener-create --loadbalancer lb1 --protocol-port 443 
>> --protocol TERMINATED_HTTPS --name listener1 
>> --default-tls-container=$(barbican secret container list | awk '/ 
>> tls_container / {print $2}')
>>
>> But the command failed with output:
>>
>> TLS container 
>> http://192.168.100.149:9311/v1/containers/d8b25d56-4fc5-406d-8b2d-5a85de2a1e34
>>  could not be found
>>
>>
>> When I run:
>>
>> barbican secret container list
>>
>> I was able to see the corresponding container in the list and the status
>> is active.
>> (Sorry, the format is a little bit ugly.)
>>
>> +++---++-+-+---+
>> | Container href
>> | Name   | Created   | Status | Type
>>  | Secrets
>> | Consumers |
>>
>> +++---++-+-+---+
>> |
>> http://192.168.100.149:9311/v1/containers/d8b25d56-4fc5-406d-8b2d-5a85de2a1e34
>>  |
>> tls_container  | 2016-01-28 04:58:42+00:00 | ACTIVE | certificate |
>> private_key=
>> http://192.168.100.149:9311/v1/secrets/1bbe33fc-ecd2-43e5-82ce-34007b9f6bfd |
>> None  |
>> |
>>||   ||
>> | certificate=
>> http://192.168.100.149:9311/v1/secrets/6d0211c6-8515-4e55-b1cf-587324a79abe |
>>   |
>> |
>> http://192.168.100.149:9311/v1/containers/31045466-bf7b-426f-9ba8-135c260418ee
>>  |
>> tls_container2 | 2016-01-28 04:59:05+00:00 | ACTIVE | certificate |
>> private_key=
>> http://192

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

[Madhusudhan Kandadai]

Wondering, have you guys figured out this issue? I am seeing the same
problem that Jiahao is getting.

On Thu, Feb 4, 2016 at 9:53 AM, Adam Harwell 
wrote:

> Could you provide your neutron-lbaas.conf? Depending on what version
> you're using, barbican may not be the default secret backend (I believe
> this has been fixed). Alternatively, it depends on what user accounts are
> involved -- this should definitely work if you are using only the single
> admin account, but we haven't done a lot of testing around the ACLs yet to
> make sure they are working (and I believe there is still an outstanding bug
> in Barbican that would cause the ACLs to not function properly in our
> use-case).
>
>
> ​--Adam
>
>
> --
> *From:* Jiahao Liang 
> *Sent:* Thursday, January 28, 2016 12:18 AM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [Neutron][LBaaS][barbican]TLS container could
> not be found
>
> Hi community,
>
> I was going through
> https://wiki.openstack.org/wiki/Network/LBaaS/docs/how-to-create-tls-loadbalancer
>  with
> devstack. I was stuck at a point when I tried to create a listener within a
> loadbalancer with this command:
>
> neutron lbaas-listener-create --loadbalancer lb1 --protocol-port 443 
> --protocol TERMINATED_HTTPS --name listener1 
> --default-tls-container=$(barbican secret container list | awk '/ 
> tls_container / {print $2}')
>
> But the command failed with output:
>
> TLS container 
> http://192.168.100.149:9311/v1/containers/d8b25d56-4fc5-406d-8b2d-5a85de2a1e34
>  could not be found
>
>
> When I run:
>
> barbican secret container list
>
> I was able to see the corresponding container in the list and the status
> is active.
> (Sorry, the format is a little bit ugly.)
>
> +++---++-+-+---+
> | Container href
>   | Name   | Created   | Status | Type|
> Secrets
> | Consumers |
>
> +++---++-+-+---+
> |
> http://192.168.100.149:9311/v1/containers/d8b25d56-4fc5-406d-8b2d-5a85de2a1e34
>  |
> tls_container  | 2016-01-28 04:58:42+00:00 | ACTIVE | certificate |
> private_key=
> http://192.168.100.149:9311/v1/secrets/1bbe33fc-ecd2-43e5-82ce-34007b9f6bfd |
> None  |
> |
>||   ||
> | certificate=
> http://192.168.100.149:9311/v1/secrets/6d0211c6-8515-4e55-b1cf-587324a79abe |
>   |
> |
> http://192.168.100.149:9311/v1/containers/31045466-bf7b-426f-9ba8-135c260418ee
>  |
> tls_container2 | 2016-01-28 04:59:05+00:00 | ACTIVE | certificate |
> private_key=
> http://192.168.100.149:9311/v1/secrets/dba18cbc-9bfe-499e-931e-90574843ca10 |
> None  |
> |
>||   ||
> | certificate=
> http://192.168.100.149:9311/v1/secrets/23e11441-d119-4b24-a288-9ddc963cb698 |
>   |
>
> +++---++-+-+---+
>
>
> Also, if I did a GET method from a RESTful client with correct
> X-Auth-Token to the url:
> http://192.168.100.149:9311/v1/containers/d8b25d56-4fc5-406d-8b2d-5a85de2a1e3,
> I was able to receive the JSON information of the TLS container.
>
>
> Anybody could give some advice on how to fix this problem?
>
> Thank you in advance!
>
> Best,
> Jiahao Liang
>
> __
> 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
>
>
__
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

[openstack-dev] [Octavia] [Tempest] Tempest tests using tempest-plugin

[Madhusudhan Kandadai]

Hi,

We are trying to implement tempest tests for Octavia using tempest-plugin.
I am wondering whether we can import *tempest* common files and use them as
a base to support Octavia tempest tests rather than copying everything in
Octavia tree. I am in favor of importing files directly from tempest to
follow tempest structure. If this is not permissible to import from tempest
directly, do we need to propose any common files in tempest_lib, so we can
import it from tempest_lib instead? I wanted to check with other for
suggestions.

Thanks,
Madhu
__
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][vpnaas] VPNaaS project status

[Madhusudhan Kandadai]

Thanks Paul for leading over the previous releases. Looking forward to have
your guidance in neutron.

On Thu, Nov 12, 2015 at 8:48 PM, Kyle Mestery  wrote:

> On Thu, Nov 12, 2015 at 9:56 AM, Paul Michali  wrote:
>
>> Neutron community,
>>
>> During the past several releases, while leading the VPNaaS project, I've
>> seen many great enhancements and features added to the VPNaaS project by
>> the community, including support for StrongSwan, Libreswan, completion of
>> the project split out, functional and rally tests, endpoint groups,
>> multiple local subnets, vendor drivers, etc.
>>
>> There is still work needed (certificate support the most important,
>> followed by documentation and scale testing), but there is a solid (in my
>> bias and subjective opinion :) foundation in place for people to play with
>> this capability.
>>
>> As I mentioned to Armando at the summit, it's time for me to move on to
>> other areas of Neutron, and as such, I'm stepping down as VPNaaS chair and
>> wrapping up work on the project over the next few weeks. I'll still try to
>> review VPNaaS commits as much as possible, and be available to advise in
>> this area.
>>
>> Towards that end, I've updated the VPNaaS wiki page (
>> https://wiki.openstack.org/wiki/Meetings/VPNaaS) to list what I think
>> are outstanding work that can be done in this area, from important to wish
>> items.  Meetings have transitioned to on-demand, and future meetings can
>> either be done as an on-demand topic in the Neutron IRC meeting, or as an
>> on-demand special meeting.
>>
>> I'll go through the VPNaaS bugs in Launchpad and comment on them, as to
>> my opinion of importance, priority, relevance, etc.
>>
>> Regards,
>>
>>
> Thanks for all your hard work over the previous releases Paul! Looking
> forward to what you'll be doing next in Neutron.
>
> Thanks,
> Kyle
>
>
>> PCM (pc_m)
>>
>> __
>> 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
>>
>>
>
> __
> 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
>
>
__
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] [Tempest] where fwaas tempest tests should be?

[Madhusudhan Kandadai]

On Thu, Oct 15, 2015 at 10:13 AM, Assaf Muller  wrote:

>
>
> On Thu, Oct 15, 2015 at 10:22 AM, Matthew Treinish 
> wrote:
>
>> On Thu, Oct 15, 2015 at 09:02:22AM -0400, Assaf Muller wrote:
>> > On Thu, Oct 15, 2015 at 7:25 AM, Takashi Yamamoto <
>> yamam...@midokura.com>
>> > wrote:
>> >
>> > > hi,
>> > >
>> > > i'm looking in fwaas tempest tests and have a question about code
>> location.
>> > >
>> > > currently,
>> > >
>> > > - fwaas api tests and its rest client are in neutron repo
>> > > - there are no fwaas scenario tests
>> > >
>> > > eventually,
>> > >
>> > > - fwaas api tests should be moved into neutron-fwaas repo
>> > > - fwaaa scenario tests should be in neutron-fwaas repo too.
>> > >
>> >
>> > I believe scenario tests that invoke APIs outside of Neutron should
>> > stay (Or be introduced to) Tempest.
>>
>> So testing the neutron advanced services was actually one of the first
>> things
>> we decided was out of scope for tempest. (like well over a year ago) It
>> took
>> some time to get equivalent testing setup elsewhere, but tests and
>> support for
>> the advanced services were removed from tempest on purpose.
>
>
> This is for both *aaS API tests and scenario tests?
>

I think yes. Scenario tests for LBaaS and VPNaaS are at this path:
LBaaS:
https://github.com/openstack/neutron-lbaas/tree/master/neutron_lbaas/tests/tempest/v2/scenario
VPNaaS: https://github.com/openstack/neutron-vpnaas/blob/master/rally-jobs/
Moving VPN api jobs in VPNaaS tree: https://review.openstack.org/#/c/211381/
(WIP)

>
>
>> I'd suggest that
>> you look at the tempest plugin interface:
>>
>> http://docs.openstack.org/developer/tempest/plugin.html
>>
>> if you'd like to make the fwaas tests (or any other adv. service tests)
>> integrate more cleanly with the rest of tempest.
>>
>> -Matt Treinish
>>
>> __
>> 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
>>
>>
>
> __
> 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
>
>
__
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][vpnaas] Need community guidance please...

[Madhusudhan Kandadai]

My two cents..

On Mon, Aug 24, 2015 at 8:48 AM, Jay Pipes  wrote:

> Hi Paul, comments inline...
>
> On 08/24/2015 07:02 AM, Paul Michali wrote:
>
>> Hi,
>>
>> I'm working on the multiple local subnet feature for VPN (RFE
>> https://bugs.launchpad.net/neutron/+bug/1459423), with a developer
>> reference document detailing the proposed process
>> (https://review.openstack.org/#/c/191944/). The plan is to do this in
>> two steps. The first is to add new APIs and database support for
>> "endpoint groups" (see dev ref for details). The second is to modify the
>> IPSec/VPN APIs to make use of the new information (and no longer use
>> some older, but equivalent info that is being extended).
>>
>> I have a few process/procedural questions for the community...
>>
>> Q1) Should I do this all as one huge commit, as two commits (one for
>> endpoint groups and one for modification to support multiple local
>> subnets), or multiple (chained) commits (e.g. commit for each API for
>> the endpoint groups and for each part of the multiple subnet change)?
>>
>> My thought (now) is to do this as two commits, with the endpoint groups
>> as one, and multiple subnet groups as a second. I started with a commit
>> for create API of endpoint (212692), and then did a chained commit for
>> delete/show/list (215717), thinking they could be reviewed in pieces,
>> but they are not that large and could be easily merged.
>>
>
> My advice would be 2 commits, as you have split them out.
>

I would prefer to have two commits with end-point groups as one and
modification to support multiple local subnets as another. This will be
easy to troubleshoot when in need.

>
> Q2) If the two parts are done separately, should the "endpoint group"
>> portion, which adds a table and API calls, be done as part of the
>> existing version (v2) of VPN, instead of introducing a new version at
>> that step?
>>
>
> Is the Neutron VPN API microversioned? If not, then I suppose your only
> option is to modify the existing v2 API. These seem to be additive changes,
> not modifications to existing API calls, in which case they are
> backwards-compatible (just not discoverable via an API microversion).
>
I suggest to be done as part of the existing version v2 API . As the api
tests are in transition from neutron to neutron-vpnaas repo, we can modify
the tests and submit as a one patch

>
> Q3) For the new API additions, do I create a new subclass for the
>> "interface" that includes all the existing APIs, introduce a new class
>> that is used together with the existing class, or do I add this to the
>> existing API?
>>
>
> Until microversioning is introduced to the Neutron VPN API, it should
> probably be a change to the existing v2 API.
>
+1

>
> Q4) With the final multiple local subnet changes, there will be changes
>> to the VPN service API (delete subnet_id arg) and IPSec connection API
>> (delete peer_cidrs arg, and add local_endpoints and peer_endpoints
>> args). Do we modify the URI so that it calls out v3 (versus v2)? Where
>> do we do that?
>>
>
> Hmm, with the backwards-incompatible API changes like the above, your only
> option is to increment the major version number. The alternative would be
> to add support for microversioning as a prerequisite to the patch that adds
> backwards-incompatible changes, and then use a microversion to introduce
> those changes.
>
Right now, we are beefing up scenario tests for VPN, adding microversioning
feature seems better option for me, but open to have reviews from
community.

>
> Best,
> -jay
>
> I'm unsure of the mechanism of increasing the version.
>>
>> Thanks in advance for any guidance here on how this should be rolled
>> out...
>>
>> Regards,
>>
>> Paul Michali (pc_m)
>>
>>
>> __
>> 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
>>
>>
> __
> 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
>
__
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] I am pleased to propose two new Neutron API/DB/RPC core reviewers!

[Madhusudhan Kandadai]

Congrats Brandon and Russel.
On Aug 22, 2015 13:37, "Miguel Lavalle"  wrote:

> Congrats to Russel and Blogan!
>
> On Sat, Aug 22, 2015 at 3:06 PM, Kyle Mestery  wrote:
>
>> It's been over a week, so I'd like to welcome Brandon and Russell to the
>> API/DB/RPC team in Neutron!
>>
>> Kyle
>>
>> On Wed, Aug 12, 2015 at 6:45 AM, Kyle Mestery 
>> wrote:
>>
>>> It gives me great pleasure to propose Russell Bryant and Brandon Logan
>>> as core reviewers in the API/DB/RPC area of Neutron. Russell and Brandon
>>> have both been incredible contributors to Neutron for a while now. Their
>>> expertise has been particularly helpful in the area they are being proposed
>>> in. Their review stats [1] place them both comfortably in the range of
>>> existing Neutron core reviewers. I expect them to continue working with all
>>> community members to drive Neutron forward for the rest of Liberty and into
>>> Mitaka.
>>>
>>> Existing DB/API/RPC core reviewers (and other Neutron core reviewers),
>>> please vote +1/-1 for the addition of Russell and Brandon.
>>>
>>> Thanks!
>>> Kyle
>>>
>>> [1] http://stackalytics.com/report/contribution/neutron-group/90
>>>
>>
>>
>> __
>> 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
>>
>>
>
> __
> 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
>
>
__
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] questions about scenario tests

[Madhusudhan Kandadai]

Debugging helped solving the issue faced in Jenkins. Per our conversation,
I shall be testing TLS LB scenario and keep you posted if I come across
anything.

Madhu


On Mon, Jul 27, 2015 at 10:47 AM, Phillip Toohill <
phillip.tooh...@rackspace.com> wrote:

>  ​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
>  phone: 210-312-4366
> mobile: 210-440-8374
>
>   ------
> *From:* Madhusudhan Kandadai 
> *Sent:* Sunday, July 26, 2015 10:48 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [neutron][lbaas] questions about scenario tests
>
> Hi there,
>
>  We have two working scenario tests in neutron lbaas tree and those are
> getting succeeded locally, however when running them in Jenkins, it is
> behaving differently: One of them got passed and the other one is facing
> time-out issues when trying to curl two backend servers after setting up
> two simple webservers. Both the tests are using the same base.py to setup
> backend servers. For info:
> https://github.com/openstack/neutron-lbaas/tree/master/neutron_lbaas/tests/tempest/v2/scenario
>
>  Tried increasing the default ping_timeout from 120 to 180, but no luck.
> Their logs are shown here:
> http://logs.openstack.org/13/205713/4/experimental/gate-neutron-lbaasv2-dsvm-scenario/09bbbd1/
>
>  If anyone has any idea about this, could you shed some light on the same?
>
>  Thanks!
>
> Madhu
>
> __
> 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
>
>
__
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] how to debug neutron using eclipse pydev?

[Madhusudhan Kandadai]

I agree with Sean's note.

On Mon, Jul 27, 2015 at 1:49 PM, Assaf Muller  wrote:

> +1
>
> - Original Message -
> > We should have the Wiki page redirect, or link to:
> >
> > https://github.com/openstack/neutron/blob/master/TESTING.rst#debugging
> >
> > And then update that RST file it to add any info we have about
> > debugging under IDEs. Generally, I dislike wikis because they go stale
> > very quick and aren't well maintained, compared to files in the code repo
> > (hopefully).
> >
> >
> > --
> > Sean M. Collins
> >
> >
> __
> > 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
> >
>
> __
> 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
>
__
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

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

[Madhusudhan Kandadai]

Hi there,

We have two working scenario tests in neutron lbaas tree and those are
getting succeeded locally, however when running them in Jenkins, it is
behaving differently: One of them got passed and the other one is facing
time-out issues when trying to curl two backend servers after setting up
two simple webservers. Both the tests are using the same base.py to setup
backend servers. For info:
https://github.com/openstack/neutron-lbaas/tree/master/neutron_lbaas/tests/tempest/v2/scenario

Tried increasing the default ping_timeout from 120 to 180, but no luck.
Their logs are shown here:
http://logs.openstack.org/13/205713/4/experimental/gate-neutron-lbaasv2-dsvm-scenario/09bbbd1/

If anyone has any idea about this, could you shed some light on the same?

Thanks!

Madhu
__
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] questions on neutron-db-migrations

[Madhusudhan Kandadai]

Thanks Ihar. Went through your email and updated HEADS to resolve merging
conflicts for my patch.



On Wed, Jul 15, 2015 at 1:03 PM, Ihar Hrachyshka 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 07/15/2015 07:17 PM, Madhusudhan Kandadai wrote:
> > Hello,
> >
> > I have noticed that neutron project got rid of
> > neutron/db/migration/alembic_migrations/versions/HEAD file and
> > renamed it to
> > neutron/db/migration/alembic_migrations/versions/HEADS
> >
> > May I know the reason why this happened? I may have overlooked
> > some documentation with respect to the change. I have a patch which
> > is in merge conflicts and have a db upgrade with version "XXX" and
> > I use that version in HEAD. When I upgrade them, I use
> > neutron-db-manage --config-file /etc/neutron/neutron.conf
> > --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head.
> >
> > With this recent refactoring related to db, what needs to be done
> > in-order to upgrade db into neutron-db?
> >
>
> Reasoning behind the change and some suggestions on how to proceed can
> be found at:
>
> http://lists.openstack.org/pipermail/openstack-dev/2015-July/069582.html
>
> I will also update devref tomorrow as per suggestion from Salvatore
> there, adding some examples on how to proceed.
>
> Ihar
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJVpryjAAoJEC5aWaUY1u57wtYIAOUlFNjOWQ29DMGV21URt6rJ
> c+M4zzdoiw5/Vtj4sJl39cGrdJ9HGyUJLLu203j7fQdhe5/snOf6Vw8XeC0S8nk9
> WzVtM0wbgJiKeG1uSNLMZTXWtpUfcX62X7fuUxibX6qDQVvMt5lJ86R4DROui8/v
> v9fgJfP7uvARorad80qY06kYL6zZOtxBGQFAfzhCIex2WI8gla5t6BIq73PKh76T
> pmxCL8fIM81JgCOpt/zKkg9r3A1D5XmVklxuh9etx2REKPtgqHNsdL3hPETLH8Bu
> eM9G1HS7L5qMQAagN0Ge5lYbPXyATmsBu15PbqXhwp6YJeWnriSmCI5ssCG+0VI=
> =Jlr0
> -END PGP SIGNATURE-
>
> __
> 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
>
__
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

[openstack-dev] [neutron] questions on neutron-db-migrations

[Madhusudhan Kandadai]

Hello,

I have noticed that neutron project got rid of
neutron/db/migration/alembic_migrations/versions/HEAD file and renamed it
to neutron/db/migration/alembic_migrations/versions/HEADS

May I know the reason why this happened? I may have overlooked some
documentation with respect to the change. I have a patch which is in merge
conflicts and have a db upgrade with version "XXX" and I use that version
in HEAD. When I upgrade them, I use neutron-db-manage --config-file
/etc/neutron/neutron.conf --config-file
/etc/neutron/plugins/ml2/ml2_conf.ini upgrade head.

With this recent refactoring related to db, what needs to be done in-order
to upgrade db into neutron-db?

Thanks,
Madhu
__
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] What does flavor mean for a network?

[Madhusudhan Kandadai]

On Wed, Jul 15, 2015 at 9:25 AM, Kyle Mestery  wrote:

> On Wed, Jul 15, 2015 at 10:54 AM, Neil Jerram 
> wrote:
>
>> I've been reading available docs about the forthcoming Neutron flavors
>> framework, and am not yet sure I understand what it means for a network.
>>
>>
> In reality, this is envisioned more for service plugins (e.g. flavors of
> LBaaS, VPNaaS, and FWaaS) than core neutron resources.
>
Yes. Right put. This is for service plugins and its part of extensions than
core network resources//

>
>
>> Is it a way for an admin to provide a particular kind of network, and
>> then for a tenant to know what they're attaching their VMs to?
>>
>>
> I'll defer to Madhu who is implementing this, but I don't believe that's
> the intention at all.
>
Currently, an admin will be able to assign particular flavors,
unfortunately, this is not going to be tenant specific flavors. As you
might have seen in the review, we are just using tenant_id to bypass the
keystone checks implemented in base.py and it is not stored in the db as
well. It is something to do in the future and documented the same in the
blueprint.

>
>
>> How does it differ from provider:network-type?  (I guess, because the
>> latter is supposed to be for implementation consumption only - but is that
>> correct?)
>>
>>
> Flavors are created and curated by operators, and consumed by API users.
>
+1

>
>
>> Thanks,
>> Neil
>>
>>
>> __
>> 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
>>
>
>
> __
> 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
>
>
__
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] Proposing Al Miller for neutron-lbaas core team

[Madhusudhan Kandadai]

Congratulations Al! Well deserved!

madhu_ak

On Mon, Jul 6, 2015 at 11:55 AM, Brandon Logan 
wrote:

>  congrats Al!
> On Jul 6, 2015 1:06 PM, Paul Michali  wrote:
>  Great to have you as a LBass core Al!
>
>  On Mon, Jul 6, 2015 at 1:29 PM Doug Wiegley 
> wrote:
>
>> Since all cores have responded, I’m going to end this early.  Welcome to
>> the core team, Al.
>>
>>  Thanks,
>> doug
>>
>>On Jul 5, 2015, at 6:27 PM, Kyle Mestery  wrote:
>>
>>  +1 for Al!
>>
>> On Thu, Jul 2, 2015 at 5:16 PM, Doug Wiegley <
>> doug...@parksidesoftware.com> wrote:
>>
>>> Hi all,
>>>
>>> As the Lieutenant of the advanced services, I would like to nominate Al
>>> Miller to be a member of the neutron-lbaas core reviewer team.
>>>
>>> Review stats are in line with other cores[2] and feedback on patches has
>>> been great. Additionally, he has been instrumental in our devstack support
>>> and octavia work.
>>>
>>> Existing cores, please vote +1/-1 for his addition to the team (that’s
>>> Brandon, Phil, and Kyle.)
>>>
>>> Thanks,
>>> doug
>>>
>>> 1.
>>> http://docs.openstack.org/developer/neutron/policies/core-reviewers.html#core-review-hierarchy
>>> 2. http://stackalytics.com/report/contribution/neutron-lbaas/90
>>>
>>> __
>>> 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
>>>
>>
>>
>> __
>> 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
>>
>>
>> __
>> 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
>>
>
> __
> 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
>
>
__
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][tempest] [lbaas] How to enable lbaas related test cases in templest?

[Madhusudhan Kandadai]

Hi Lily,

Could you let us know how and what tests you are running for lbaasv2? To my
understanding, I don't see all the api/scenario tests for lbaasv2 are
skipped. However, there are documents about neutron lbaasv2 and API tests
and they are documented [1][2] respectively.

[1] https://wiki.openstack.org/wiki/Neutron/LBaaS
[2] https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0

Cheers,
Madhu

On Fri, May 29, 2015 at 3:09 AM, Lily.Sing  wrote:

> Hi all,
>
> I try to test neutron LBaaS with tempest, but find all the API and
> scenario test cases related to it are skipped. Is there a way to enable
> these test cases? I have LBaaS service enabled already. Also, is there any
> detailed document about lbaasv2?
>
> Thanks.
>
> Best regards,
> Lily Xing(邢莉莉)
>
> __
> 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
>
>
__
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

[openstack-dev] [Neutron][LBaaS] Jenkins CI failure for patch: https://review.openstack.org/180019

[Madhusudhan Kandadai]

Hello,

I am seeing odd behavior with Jenkins CI for the patch:
https://review.openstack.org/180019

A quick background:

1. I could see all the tests passing on my virtual box and have attached
the logs for your ready reference.
2. Whereas in Jenkins, I could see the different behavior which is not
reproducible on my virtual box. I have tried the following to make it
succeed.
  (a) 'recheck' comment - Jenkins reported unhappy.
  (b) restacked my devstack instance on my vm and run 'tox -e tempest', it
succeeds on virtual box, but not for Jenkins.

Not sure of the exact problem though, but would like to have community help
on the same.

Thanks!
Madhu
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 git commit --amend
[review/madhusudhan_kandadai/pools_admin_ddt_tests acba386] Tempest tests using 
testscenarios for create/update pool
 Author: Ubuntu 
 1 file changed, 169 insertions(+)
 create mode 100644 
neutron_lbaas/tests/tempest/v2/scenario/test_pools_admin_state.py
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 git review
remote: Resolving deltas: 100% (5/5)
remote: Processing changes: updated: 1, refs: 1, done
remote: 
remote: Updated Changes:
remote:   https://review.openstack.org/180019 Tempest tests using testscenarios 
for create/update pool
remote: 
To 
ssh://madhusudhan-kanda...@review.openstack.org:29418/openstack/neutron-lbaas.git
 * [new branch]  HEAD -> refs/publish/master/pools_admin_ddt_tests
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
 tox -e tempest
tempest develop-inst-nodeps: /opt/stack/neutron-lbaas
tempest runtests: PYTHONHASHSEED='3706390691'
tempest runtests: commands[0] | sh tools/pretty_tox.sh 
running testr
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron_lbaas/tests/unit}  

{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor
 [11.086096s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor_extra_attribute
 [0.013065s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor_invalid_attribute
 [0.033716s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor_missing_attribute
 [0.020612s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_delete_health_monitor
 [10.916318s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_get_health_monitor
 [11.037575s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_list_health_monitors_empty
 [0.062835s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_list_health_monitors_one
 [10.991776s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_list_health_monitors_two
 [44.915230s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_udpate_health_monitor_invalid_attribute
 [10.893886s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_update_health_monitor
 [21.516263s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_update_health_monitor_extra_attribute
 [11.019241s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener
 [11.068447s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_admin_state_up
 [0.123651s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_connection_limit
 [0.163494s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_description
 [11.030286s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_load_balancer_id
 [0.127011s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_name
 [11.307731s] ... ok
{0} 
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_crea

Re: [openstack-dev] [Neutron][LBaaS] Clarification required

[Madhusudhan Kandadai]

Thanks Brandon for clearing the confusion.

On Mon, May 4, 2015 at 9:52 AM, Brandon Logan 
wrote:

>  Hi Madhu,​
>
> You won't see any pool details from a GET of a loadbalancer.  For every
> entity, you'll only be shown minor information from their parent (if one
> exists) and their children (if any exist).  We may one day have a call to
> just show everything under a loadbalancer, but thats not there yet.
>
>
>  Thanks,
>
> Brandon
>  ------
> *From:* Madhusudhan Kandadai 
> *Sent:* Friday, May 1, 2015 9:43 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [Neutron][LBaaS] Clarification required
>
>Hello,
>
>  I am playing around with Neutron LBaaS API calls as per Neutron/LBaaS/API
> 2.0 docs. I have noticed below behavior against working devstack. I would
> like to clarify on it:
>
>  1. I create a loadbalancer using RESTAPI with the attributes -
> 'vip_subnet_id' and 'admin_state_up' as 'False'. It is getting created
> successfully
>
>  when I do a GET on loadbalancer, I could see the relevant their
> information.
>
>  2. I create a listener with the loadbalancer_id from step 1 and
> 'admin_state_up' as 'False' and able to create listener.
>
>  when I do a GET on loadbalancer again, I could see listener details
> associated with the loadbalancer as expected
>
>  Now the question comes in:-
>
>  3. I create a pool with listener _id and 'admin_state_up' as 'False' and
> able to create pool accordingly
>
>  But, when I do a GET on loadbalancer, I could not see pool details under
> listener associated with the loadbalancer.
>
>  Just curious, why I could not see like this when I do a GET on
> loadbalancer:
>
> {
>  loadbalancer {
>   listener {
> pools
> }
>}
> }
>
>
>  4. I could see all the details including pool correctly when I do GET on
> loadbalancers//statuses
>
>  Thanks,
>  Madhusudhan
>
> __
> 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
>
>
__
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][tempest] Data-driven testing (DDT) samples

[Madhusudhan Kandadai]

Thanks Salvatore and Tom for your response.

Yes, we were able to write data driven tests in two ways:

(1) using ddt package - needs to be installed separately and invoke the
module when writing the tests
(2) using testscenarios package - this package is already installed and
being used in neutron projects. Except for one project, rest are using
testscenarios.

Hence, the community have decided to stick with option 2 in neutron-lbaas
tree, to follow same process.

Regards,
Madhusudhan

On Mon, May 4, 2015 at 3:08 AM, Tom Barron  wrote:

> On 5/4/15 3:05 AM, Salvatore Orlando wrote:
> > Among the OpenStack project of which I have some knowledge, none of them
> > uses any DDT library.
>
> FYI, manila uses DDT for unit tests.
>
> > If you think there might be a library from which lbaas, neutron, or any
> > other openstack project might take advantage, we should consider it.
> >
> > Salvatore
> >
> > On 14 April 2015 at 20:33, Madhusudhan Kandadai
> >  > <mailto:madhusudhan.openst...@gmail.com>> wrote:
> >
> > Hi,
> >
> > I would like to start a thread for the tempest DDT in neutron-lbaas
> > tree. The problem comes in when we have testcases for both
> > admin/non-admin user. (For example, there is an ongoing patch
> > activity: https://review.openstack.org/#/c/171832/). Ofcourse it has
> > duplication and want to adhere as per the tempest guidelines. Just
> > wondering, whether we are using DDT library in other projects, if it
> > is so, can someone please point me the sample code that are being
> > used currently. It can speed up this DDT activity for neutron-lbaas.
> >
>
>   $ grep -R '@ddt' manila/tests/ | wc -l
> 198
>
> > In the meantime, I am also gathering/researching about that. Should
> > I have any update, I shall keep you posted on the same.
> >
> > Thanks,
> > Madhusudhan
> >
> >
>  __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > <
> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> >
> __
> > 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
> >
>
> Regards,
>
> -- Tom
>
>
>
> __
> 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
>
__
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

[openstack-dev] [Neutron][LBaaS] Clarification required

[Madhusudhan Kandadai]

Hello,

I am playing around with Neutron LBaaS API calls as per Neutron/LBaaS/API
2.0 docs. I have noticed below behavior against working devstack. I would
like to clarify on it:

1. I create a loadbalancer using RESTAPI with the attributes -
'vip_subnet_id' and 'admin_state_up' as 'False'. It is getting created
successfully

when I do a GET on loadbalancer, I could see the relevant their information.

2. I create a listener with the loadbalancer_id from step 1 and
'admin_state_up' as 'False' and able to create listener.

when I do a GET on loadbalancer again, I could see listener details
associated with the loadbalancer as expected

Now the question comes in:-

3. I create a pool with listener _id and 'admin_state_up' as 'False' and
able to create pool accordingly

But, when I do a GET on loadbalancer, I could not see pool details under
listener associated with the loadbalancer.

Just curious, why I could not see like this when I do a GET on loadbalancer:

{
loadbalancer {
 listener {
   pools
}
   }
}


4. I could see all the details including pool correctly when I do GET on
loadbalancers//statuses

Thanks,
Madhusudhan
__
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 v2 not showing operating_status as inactive

[Madhusudhan Kandadai]

Yes you are right. The statuses call is correctly changing the operating
status to DISABLED, but not showing operating status as DISABLED when doing
POST/PUT/GET on loadbalancer upon specifying admin_state_up as 'False'
explicitly. Thanks for confirming though.

Madhu

On Tue, Apr 28, 2015 at 6:59 PM, Brandon Logan 
wrote:

>  ​So that is the right URL for the statuses call.  As I understand the
> issue the statuses call is correctly changing the operating status to
> DISABLED correct?
>
>
>  The problem is when you do an operationg on a loadbalancer and
> admin_state_up = False.  In that case the body returned for those
> operationgs (POST, PUT, GET) should show operating status as DISABLED, and
> it is not.  This is a bug, and I believe it would be quite simple to fix.
> You won't need to call the statuses method as that is just the method that
> is called when the /statuses resource is called.  The create_loadbalancer,
> get_loadbalancer, get_loadbalancers, and update_loadbalancer methods will
> just need to change the operating_status to DISABLED if admin_state_up is
> False.  Should be a very simple change actually.
>
>
>  Let me know if I am articulating the problem correctly.
>
>
>  Thanks,
>
> Brandon
>  --
> *From:* Madhusudhan Kandadai 
> *Sent:* Tuesday, April 28, 2015 3:23 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] Neutron Lbaas v2 not showing
> operating_status as inactive
>
>Hi Anand,
>
>  There is an api which calls 'statuses' method.. I could see the status
> 'DISABLED' in: GET /lbaas/loadbalancers/loadbalancer_id/statuses.
>
> Maybe we need to correct the doc to reflect the right URL to avoid
> confusion. If that is the right API call, I shall update the bug and mark
> it as fixed.
>
>  Regards,
>  Madhu
>
>
>
> On Tue, Apr 28, 2015 at 12:28 PM, Anand shanmugam 
> wrote:
>
>>  Hi ,
>>
>>  I am working on the bug https://bugs.launchpad.net/neutron/+bug/1449286
>>
>>  In this bug the admin_state_up is made to false when creating a lbaas
>> v2 loadbalancer.The operating_state should become DISABLED for the created
>> loadbalancer but it is showing as online.
>>
>>  I can see that there is a method "statuses" which takes care of
>> disabling the opensrting_status (
>> https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/services/loadbalancer/plugin.py#L971)
>> but I cannot find the method which will call this 'satuses' method.
>>
>>  I feel this statuses method is not called at all when creating or
>> updating a loadbalancer.Could someone please help me if there is any other
>> api to call this method?
>>
>>  Regards,
>> Anand S
>>
>> __
>> 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
>>
>>
>
> __
> 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
>
>
__
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 v2 not showing operating_status as inactive

[Madhusudhan Kandadai]

Hi Anand,

There is an api which calls 'statuses' method.. I could see the status
'DISABLED' in: GET /lbaas/loadbalancers/loadbalancer_id/statuses.

Maybe we need to correct the doc to reflect the right URL to avoid
confusion. If that is the right API call, I shall update the bug and mark
it as fixed.

Regards,
Madhu



On Tue, Apr 28, 2015 at 12:28 PM, Anand shanmugam 
wrote:

> Hi ,
>
> I am working on the bug https://bugs.launchpad.net/neutron/+bug/1449286
>
> In this bug the admin_state_up is made to false when creating a lbaas v2
> loadbalancer.The operating_state should become DISABLED for the created
> loadbalancer but it is showing as online.
>
> I can see that there is a method "statuses" which takes care of disabling
> the opensrting_status (
> https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/services/loadbalancer/plugin.py#L971)
> but I cannot find the method which will call this 'satuses' method.
>
> I feel this statuses method is not called at all when creating or updating
> a loadbalancer.Could someone please help me if there is any other api to
> call this method?
>
> Regards,
> Anand S
>
> __
> 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
>
>
__
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] adding lbaas core

[Madhusudhan Kandadai]

Congrats Phill!

On Tue, Apr 21, 2015 at 12:34 PM, Jain, Vivek  wrote:

> Congrats Phil !!
>
> Thanks,
> Vivek
>
> > On Apr 21, 2015, at 10:16 AM, Phillip Toohill <
> phillip.tooh...@rackspace.com> wrote:
> >
> > 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] [neutron][lbaas] adding lbaas core
> >
> > Welcome Phil!
> > 
> > From: Doug Wiegley 
> > Sent: Tuesday, April 21, 2015 11:54 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [neutron][lbaas] adding lbaas core
> >
> > It’s been a week, welcome Phil.
> >
> > Thanks,
> > doug
> >
> >
> >> On Apr 13, 2015, at 2:39 PM, Doug Wiegley 
> wrote:
> >>
> >> Hi all,
> >>
> >> I'd like to nominate Philip Toohill as a neutron-lbaas core. Good guy,
> did a bunch of work on the ref impl for lbaasv2, and and I'll let the
> numbers[1] speak for themselves.
> >>
> >> Existing lbaas cores, please vote.  All three of us.  :-)
> >>
> >> [1] http://stackalytics.com/report/contribution/neutron-lbaas/30
> >>
> >> Thanks,
> >> doug
> >
> >
> >
> __
> > 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
> >
> >
> __
> > 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
> >
> >
> __
> > 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
>
> __
> 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
>
__
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

[openstack-dev] [neutron][lbaas][tempest] Data-driven testing (DDT) samples

[Madhusudhan Kandadai]

Hi,

I would like to start a thread for the tempest DDT in neutron-lbaas tree.
The problem comes in when we have testcases for both admin/non-admin user.
(For example, there is an ongoing patch activity:
https://review.openstack.org/#/c/171832/). Ofcourse it has duplication and
want to adhere as per the tempest guidelines. Just wondering, whether we
are using DDT library in other projects, if it is so, can someone please
point me the sample code that are being used currently. It can speed up
this DDT activity for neutron-lbaas.

In the meantime, I am also gathering/researching about that. Should I have
any update, I shall keep you posted on the same.

Thanks,
Madhusudhan
__
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