Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

[Sławek Kapłoński]

Hi,

Another idea is to modify test that it will:
1. Check how many ports are in tenant,
2. Set quota to actual number of ports + 1 instead of hardcoded 1 as it is now,
3. Try to add 2 ports - exactly as it is now,

I think that this should be still backend agnostic and should fix this problem.

> Wiadomość napisana przez Sławek Kapłoński <sla...@kaplonski.pl> w dniu 
> 06.04.2018, o godz. 17:08:
> 
> Hi,
> 
> I don’t know how networking-ovn is working but I have one question.
> 
> 
>> Wiadomość napisana przez Daniel Alvarez Sanchez <dalva...@redhat.com> w dniu 
>> 06.04.2018, o godz. 15:30:
>> 
>> Hi,
>> 
>> Thanks Lucas for writing this down.
>> 
>> On Thu, Apr 5, 2018 at 11:35 AM, Lucas Alvares Gomes <lucasago...@gmail.com> 
>> wrote:
>> Hi,
>> 
>> The tests below are failing in the tempest API / Scenario job that
>> runs in the networking-ovn gate (non-voting):
>> 
>> neutron_tempest_plugin.api.admin.test_quotas_negative.QuotasAdminNegativeTestJSON.test_create_port_when_quotas_is_full
>> neutron_tempest_plugin.api.test_routers.RoutersIpV6Test.test_router_interface_status
>> neutron_tempest_plugin.api.test_routers.RoutersTest.test_router_interface_status
>> neutron_tempest_plugin.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_prefixlen
>> neutron_tempest_plugin.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_quota
>> neutron_tempest_plugin.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_subnet_cidr
>> 
>> Digging a bit into it I noticed that with the exception of the two
>> "test_router_interface_status" (ipv6 and ipv4) all other tests are
>> failing because the way metadata works in networking-ovn.
>> 
>> Taking the "test_create_port_when_quotas_is_full" as an example. The
>> reason why it fails is because when the OVN metadata is enabled,
>> networking-ovn will metadata port at the moment a network is created
>> [0] and that will already fulfill the quota limit set by that test
>> [1].
>> 
>> That port will also allocate an IP from the subnet which will cause
>> the rest of the tests to fail with a "No more IP addresses available
>> on network ..." error.
>> 
>> With ML2/OVS we would run into the same Quota problem if DHCP would be
>> enabled for the created subnets. This means that if we modify the current 
>> tests
>> to enable DHCP on them and we account this extra port it would be valid for
>> all networking-ovn as well. Does it sound good or we still want to isolate 
>> quotas?
> 
> If DHCP will be enabled for networking-ovn, will it use one more port also or 
> not? If so then You will still have the same problem with DHCP as in ML2/OVS 
> You will have one port created and for networking-ovn it will be 2 ports.
> If it’s not like that then I think that this solution, with some comment in 
> test code why DHCP is enabled should be good IMO.
> 
>> 
>> This is not very trivial to fix because:
>> 
>> 1. Tempest should be backend agnostic. So, adding a conditional in the
>> tempest test to check whether OVN is being used or not doesn't sound
>> correct.
>> 
>> 2. Creating a port to be used by the metadata agent is a core part of
>> the design implementation for the metadata functionality [2]
>> 
>> So, I'm sending this email to try to figure out what would be the best
>> approach to deal with this problem and start working towards having
>> that job to be voting in our gate. Here are some ideas:
>> 
>> 1. Simple disable the tests that are affected by the metadata approach.
>> 
>> 2. Disable metadata for the tempest API / Scenario tests (here's a
>> test patch doing it [3])
>> 
>> IMHO, we don't want to do this as metadata is likely to be enabled in all the
>> clouds either using ML2/OVS or OVN so it's good to keep exercising
>> this part.
>> 
>> 
>> 3. Same as 1. but also create similar tempest tests specific for OVN
>> somewhere else (in the networking-ovn tree?!)
>> 
>> As we discussed on IRC I'm keen on doing this instead of getting bits in
>> tempest to do different things depending on the backend used. Unless
>> we want to enable DHCP on the subnets that these tests create :)
>> 
>> 
>> What you think would be the best way to workaround this problem, any
>> other ideas ?
>> 
>> As for the "test_router_interface_status" tests that are failing
>> independent of the metadata, there's a bug reporting the problem here
>> [4]. So we should just fix it.

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

[Sławek Kapłoński]

Hi,

I don’t know how networking-ovn is working but I have one question.


> Wiadomość napisana przez Daniel Alvarez Sanchez  w dniu 
> 06.04.2018, o godz. 15:30:
> 
> Hi,
> 
> Thanks Lucas for writing this down.
> 
> On Thu, Apr 5, 2018 at 11:35 AM, Lucas Alvares Gomes  
> wrote:
> Hi,
> 
> The tests below are failing in the tempest API / Scenario job that
> runs in the networking-ovn gate (non-voting):
> 
> neutron_tempest_plugin.api.admin.test_quotas_negative.QuotasAdminNegativeTestJSON.test_create_port_when_quotas_is_full
> neutron_tempest_plugin.api.test_routers.RoutersIpV6Test.test_router_interface_status
> neutron_tempest_plugin.api.test_routers.RoutersTest.test_router_interface_status
> neutron_tempest_plugin.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_prefixlen
> neutron_tempest_plugin.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_quota
> neutron_tempest_plugin.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_subnet_cidr
> 
> Digging a bit into it I noticed that with the exception of the two
> "test_router_interface_status" (ipv6 and ipv4) all other tests are
> failing because the way metadata works in networking-ovn.
> 
> Taking the "test_create_port_when_quotas_is_full" as an example. The
> reason why it fails is because when the OVN metadata is enabled,
> networking-ovn will metadata port at the moment a network is created
> [0] and that will already fulfill the quota limit set by that test
> [1].
> 
> That port will also allocate an IP from the subnet which will cause
> the rest of the tests to fail with a "No more IP addresses available
> on network ..." error.
> 
> With ML2/OVS we would run into the same Quota problem if DHCP would be
> enabled for the created subnets. This means that if we modify the current 
> tests
> to enable DHCP on them and we account this extra port it would be valid for
> all networking-ovn as well. Does it sound good or we still want to isolate 
> quotas?

If DHCP will be enabled for networking-ovn, will it use one more port also or 
not? If so then You will still have the same problem with DHCP as in ML2/OVS 
You will have one port created and for networking-ovn it will be 2 ports.
If it’s not like that then I think that this solution, with some comment in 
test code why DHCP is enabled should be good IMO.

> 
> This is not very trivial to fix because:
> 
> 1. Tempest should be backend agnostic. So, adding a conditional in the
> tempest test to check whether OVN is being used or not doesn't sound
> correct.
> 
> 2. Creating a port to be used by the metadata agent is a core part of
> the design implementation for the metadata functionality [2]
> 
> So, I'm sending this email to try to figure out what would be the best
> approach to deal with this problem and start working towards having
> that job to be voting in our gate. Here are some ideas:
> 
> 1. Simple disable the tests that are affected by the metadata approach.
> 
> 2. Disable metadata for the tempest API / Scenario tests (here's a
> test patch doing it [3])
> 
> IMHO, we don't want to do this as metadata is likely to be enabled in all the
> clouds either using ML2/OVS or OVN so it's good to keep exercising
> this part.
> 
> 
> 3. Same as 1. but also create similar tempest tests specific for OVN
> somewhere else (in the networking-ovn tree?!)
> 
> As we discussed on IRC I'm keen on doing this instead of getting bits in
> tempest to do different things depending on the backend used. Unless
> we want to enable DHCP on the subnets that these tests create :)
> 
> 
> What you think would be the best way to workaround this problem, any
> other ideas ?
> 
> As for the "test_router_interface_status" tests that are failing
> independent of the metadata, there's a bug reporting the problem here
> [4]. So we should just fix it.
> 
> [0] 
> https://github.com/openstack/networking-ovn/blob/f3f5257fc465bbf44d589cc16e9ef7781f6b5b1d/networking_ovn/common/ovn_client.py#L1154
> [1] 
> https://github.com/openstack/neutron-tempest-plugin/blob/35bf37d1830328d72606f9c790b270d4fda2b854/neutron_tempest_plugin/api/admin/test_quotas_negative.py#L66
> [2] 
> https://docs.openstack.org/networking-ovn/latest/contributor/design/metadata_api.html#overview-of-proposed-approach
> [3] https://review.openstack.org/#/c/558792/
> [4] https://bugs.launchpad.net/networking-ovn/+bug/1713835
> 
> Cheers,
> Lucas
> 
> Thanks,
> Daniel
> 
> __
> 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

Re: [openstack-dev] [ALL][PTLs] [Community goal] Toggle the debug option at runtime

[Sławek Kapłoński]

Hi,

Thanks Akihiro for help. I added „neutron-dynamic-routing” task to this story 
and I will push patch for it soon.
There is still so many things that I need to learn about OpenStack and Neutron 
:)

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Akihiro Motoki <amot...@gmail.com> w dniu 
> 06.04.2018, o godz. 11:34:
> 
> 
> Hi Slawek,
> 
> 2018-04-06 17:38 GMT+09:00 Sławek Kapłoński <sla...@kaplonski.pl>:
> Hi,
> 
> One more question about implementation of this goal. Should we take care (and 
> add to story board [1]) projects like:
> 
> In my understanding, tasks in the storyboard story are prepared per project 
> team listed in the governance.
> IMHO, repositories which belong to a project team should be handled as a 
> single task.
> 
> The situations vary across repositories.
> 
> 
> openstack/neutron-lbaas
> 
> This should be covered by octavia team.
> 
> openstack/networking-cisco
> openstack/networking-dpm
> openstack/networking-infoblox
> openstack/networking-l2gw
> openstack/networking-lagopus
> 
> The above repos are not official repos.
> Maintainers of each repo can follow the community goal, but there is no need 
> to be tracked as the neutron team.
> 
> openstack/neutron-dynamic-routing
> 
> This repo is part of the neutron team. We, the neutron team need to cover 
> this.
> 
> FYI: The official repositories covered by the neutron team is available here.
> https://governance.openstack.org/tc/reference/projects/neutron.html
> 
> Thanks,
> Akihiro
> 
> 
> Which looks that should be probably also changed in some way. Or maybe list 
> of affected projects in [1] is „closed” and if some project is not there it 
> shouldn’t be changed to accomplish this community goal?
> 
> [1] https://storyboard.openstack.org/#!/story/2001545
> 
> —
> Best regards
> Slawek Kaplonski
> sla...@kaplonski.pl
> 
> 
> 
> 
> > Wiadomość napisana przez ChangBo Guo <glongw...@gmail.com> w dniu 
> > 26.03.2018, o godz. 14:15:
> >
> >
> > 2018-03-22 16:12 GMT+08:00 Sławomir Kapłoński <sla...@kaplonski.pl>:
> > Hi,
> >
> > I took care of implementation of [1] in Neutron and I have couple questions 
> > to about this goal.
> >
> > 1. Should we only change "restart_method" to mutate as is described in [2] 
> > ? I did already something like that in [3] - is it what is expected?
> >
> >  Yes , let's the only  thing.  we need test if that if it works .
> >
> > 2. How I can check if this change is fine and config option are mutable 
> > exactly? For now when I change any config option for any of neutron agents 
> > and send SIGHUP to it it is in fact "restarted" and config is reloaded even 
> > with this old restart method.
> >
> > good question, we indeed thought this question when we proposal  the 
> > goal.  But It seems difficult to test  that consuming projects like Neutron 
> > automatically.
> >
> > 3. Should we add any automatic tests for such change also? Any examples of 
> > such tests in other projects maybe?
> >  There is no example for tests now, we only have some unit tests  in 
> > oslo.service .
> >
> > [1] 
> > https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html
> > [2] https://docs.openstack.org/oslo.config/latest/reference/mutable.html
> > [3] https://review.openstack.org/#/c/554259/
> >
> > —
> > Best regards
> > Slawek Kaplonski
> > sla...@kaplonski.pl
> >
> >
> > __
> > 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
> >
> >
> >
> > --
> > ChangBo Guo(gcb)
> > Community Director @EasyStack
> > __
> > 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



signature.asc
Description: Message signed with OpenPGP
__
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] [ALL][PTLs] [Community goal] Toggle the debug option at runtime

[Sławek Kapłoński]

Hi,

One more question about implementation of this goal. Should we take care (and 
add to story board [1]) projects like:

openstack/neutron-lbaas
openstack/networking-cisco
openstack/networking-dpm
openstack/networking-infoblox
openstack/networking-l2gw
openstack/networking-lagopus
openstack/neutron-dynamic-routing

Which looks that should be probably also changed in some way. Or maybe list of 
affected projects in [1] is „closed” and if some project is not there it 
shouldn’t be changed to accomplish this community goal?

[1] https://storyboard.openstack.org/#!/story/2001545

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez ChangBo Guo  w dniu 26.03.2018, 
> o godz. 14:15:
> 
> 
> 2018-03-22 16:12 GMT+08:00 Sławomir Kapłoński :
> Hi,
> 
> I took care of implementation of [1] in Neutron and I have couple questions 
> to about this goal.
> 
> 1. Should we only change "restart_method" to mutate as is described in [2] ? 
> I did already something like that in [3] - is it what is expected?
> 
>  Yes , let's the only  thing.  we need test if that if it works .
> 
> 2. How I can check if this change is fine and config option are mutable 
> exactly? For now when I change any config option for any of neutron agents 
> and send SIGHUP to it it is in fact "restarted" and config is reloaded even 
> with this old restart method.
> 
> good question, we indeed thought this question when we proposal  the 
> goal.  But It seems difficult to test  that consuming projects like Neutron 
> automatically.
> 
> 3. Should we add any automatic tests for such change also? Any examples of 
> such tests in other projects maybe?
>  There is no example for tests now, we only have some unit tests  in 
> oslo.service .
> 
> [1] 
> https://governance.openstack.org/tc/goals/rocky/enable-mutable-configuration.html
> [2] https://docs.openstack.org/oslo.config/latest/reference/mutable.html
> [3] https://review.openstack.org/#/c/554259/
> 
> —
> Best regards
> Slawek Kaplonski
> sla...@kaplonski.pl
> 
> 
> __
> 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
> 
> 
> 
> --
> ChangBo Guo(gcb)
> Community Director @EasyStack
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Adding Brian Haley to the Neutron Drivers team

[Sławek Kapłoński]

I’m not part of drivers team but big +1 for Brian from me :)

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Miguel Lavalle  w dniu 
> 22.03.2018, o godz. 17:25:
> 
> Hi Neutrinos,
> 
> As we all know, the Neutron Drivers team plays a crucial role in helping the 
> community to evolve the OpenStack Networking architecture to meet the needs 
> of our current and future users [1]. To strengthen this team, I have decided 
> to add Brian Haley to it. Brian has two decades of experience in open source 
> networking technology. He joined the OpenStack community contributing code to 
> nova-network in the Diablo release. His first Neutron commit (known as 
> Quantum at the time) dates back to March of 2013 [2]. Since then, his many 
> contributions include the implementation and evolution of our L3 and DVR 
> code. He is one of our most active core reviewers and a prolific contributor 
> of code to our reference implementation. I am very confident that Brian will 
> be a continuous source of knowledge, experience and valuable insight to the 
> Drivers team.
> 
> Best regards
> 
> Miguel
> 
> 
> [1] 
> https://docs.openstack.org/neutron/pike/contributor/policies/neutron-teams.html#drivers-team
> [2] https://review.openstack.org/#/c/25564/
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Gerrit custom menu entries - help needed

[Sławek Kapłoński]

Thx. It looks very nice. I will have to try it :)

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Poulos, Brianna L. <brianna.pou...@jhuapl.edu> w 
> dniu 12.12.2017, o godz. 16:46:
> 
> Hello,
> 
> I have found the Gerrit Dashboard Creator (see 
> https://github.com/openstack/gerrit-dash-creator ) to be very helpful when 
> putting together queries.
> 
> Thanks,
> ~Brianna
> 
> On 12/8/17, 16:25, "Sławek Kapłoński" <sla...@kaplonski.pl> wrote:
> 
>Hello,
> 
>I’m trying to personalize my Gerrit menus in settings panel on 
> review.openstack.org.
>So I prepared query like:
> 
>(NOT owner:self) AND status:open AND label:Code-Review-0,self AND 
> label:Workflow=0 AND (project:openstack/neutron OR 
> project:openstack/neutron-lib) AND branch:master
> 
>And I wanted to create menu entry with this query. When I’m pasting query:
> 
>
> #/q/(NOT+owner:self)+AND+status:open+AND+label:Code-Review-0%252Cself+AND+label:Workflow%253D0+AND+(project:openstack/neutron+OR+project:openstack/neutron-lib)+AND+branch:master
> 
>On gerrit settings page it replaces me chars like , or = to something else 
> and query looks like:
> 
>
> #/q/(NOT+owner:self)+AND+status:open+AND+label:Code-Review-0%252Cself+AND+label:Workflow%253D0+AND+(project:openstack/neutron+OR+project:openstack/neutron-lib)+AND+branch:master
> 
>And it don’t work properly then.
>So I have a question to more experienced Gerrit users. What I’m doing 
> wrong here and how I should create menu entry with query which I really want?
> 
>—
>Best regards
>Slawek Kaplonski
>sla...@kaplonski.pl
> 
> 
> 
> 
> 
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Gerrit custom menu entries - help needed

[Sławek Kapłoński]

Hello,

I’m trying to personalize my Gerrit menus in settings panel on 
review.openstack.org.
So I prepared query like:

(NOT owner:self) AND status:open AND label:Code-Review-0,self AND 
label:Workflow=0 AND (project:openstack/neutron OR 
project:openstack/neutron-lib) AND branch:master

And I wanted to create menu entry with this query. When I’m pasting query:

#/q/(NOT+owner:self)+AND+status:open+AND+label:Code-Review-0%252Cself+AND+label:Workflow%253D0+AND+(project:openstack/neutron+OR+project:openstack/neutron-lib)+AND+branch:master

On gerrit settings page it replaces me chars like , or = to something else and 
query looks like:

#/q/(NOT+owner:self)+AND+status:open+AND+label:Code-Review-0%252Cself+AND+label:Workflow%253D0+AND+(project:openstack/neutron+OR+project:openstack/neutron-lib)+AND+branch:master

And it don’t work properly then.
So I have a question to more experienced Gerrit users. What I’m doing wrong 
here and how I should create menu entry with query which I really want?

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl






signature.asc
Description: Message signed with OpenPGP
__
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] [python-openstacksdk][shade] New cores proposed for shade/sdk

[Sławek Kapłoński]

Thank You for all Your help and all Your support. I will do my best to help 
develop shade/sdk projects.

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Monty Taylor  w dniu 
> 04.12.2017, o godz. 22:12:
> 
> On 11/30/2017 10:00 AM, Dean Troyer wrote:
>> On Thu, Nov 30, 2017 at 8:00 AM, Monty Taylor  wrote:
>>> So let's add them to the core team, yeah?
>> +1
>> dt
> 
> Hearing no dissent I've added both. Welcome aboard!
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] [OpenStack] [Networking-odl] [Qos] networking-odl is not sending complete data during qos-policy-name update

[Sławek Kapłoński]

Hi,

I checked that on Neutron’s side and I proposed patch to fix it in Ocata: 
https://review.openstack.org/#/c/523133/
I think that this patch from Ocata should be easy to back port to newton also 
if You will need it there.
It is fixed in Pike already.

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Isaku Yamahata  w dniu 
> 22.11.2017, o godz. 02:17:
> 
> Added odl neutron-dev.
> Basically this issue is fixed with master already.
> As newton is about to be EOL, I don't see any point to dig into it.
> 
> Probably you'd like to check the fix in the master and backport it to newton.
> 
> Thanks,
> 
> 
> On Tue, Nov 21, 2017 at 10:08:03AM +,
> A Vamsikrishna  wrote:
> 
>> Hi All,
>> 
>> Networking-odl is not sending bandwidth_limit_rules & dscp_marking_rules 
>> along with the updated qos policy name when I have updated the 
>> qos-policy-name from Vamsi to Krish.
>> 
>> Expected behavior is to have the updated policy name along with 
>> bandwidth_limit_rules & dscp_marking_rules same as that in old 
>> qos-policy-name.
>> 
>> 
>> 
>> Version: Stable/Newton
>> 192.168.56.102 --> Openstack
>> 192.168.56.1 --> ODL
>> 
>> Any thoughts on how to move forward ?
>> 
>> PFA for wireshark cap.
>> 
>> JavaScript Object Notation: application/json
>>Object
>>Member Key: policy
>>Object
>>Member Key: bandwidth_limit_rules
>>Array
>>Key: bandwidth_limit_rules
>>Member Key: name
>>String value: Krish
>>Key: name
>>Member Key: created_at
>>String value: 2017-11-20T19:27:06Z
>>Key: created_at
>>Member Key: updated_at
>>String value: 2017-11-20T19:27:15Z
>>Key: updated_at
>>Member Key: dscp_marking_rules
>>Array
>>Key: dscp_marking_rules
>>Member Key: revision_number
>>Number value: 4
>>Key: revision_number
>>Member Key: shared
>>False value
>>Key: shared
>>Member Key: project_id
>>String value: eacd04d3ff4b4e1d9dc2f5282edbb9e0
>>Key: project_id
>>Member Key: id
>>String value: 066fd21e-2041-43f6-956a-6bec0948bf15
>>Key: id
>>Member Key: description
>>String value:
>>Key: description
>>Key: policy
>> 
>> 
>> Thanks,
>> Vamsi
> 
> 
>> __
>> 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
> 
> 
> --
> Isaku Yamahata 
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Bug deputy report

[Sławek Kapłoński]

Hi all,

I was on bug deputy last week. There was no any high or critical bugs reported 
during this time.
Below is short summary about reported bugs:

L3 HA related bug:
* https://bugs.launchpad.net/neutron/+bug/1731595 - it needs some attention 
from L3 sub team IMO

OVS related bugs:
* https://bugs.launchpad.net/neutron/+bug/1731953 - it’s new one about ovs-fw 
and I want to check it more,
* https://bugs.launchpad.net/neutron/+bug/1730407 - this one has got already 
fix merged to master and pike,
* https://bugs.launchpad.net/neutron/+bug/1730552 - patch in review, also 
related to ovs-fw,
* https://bugs.launchpad.net/neutron/+bug/1731494 - this one I didn’t know what 
priority it should have, but it has already some patch in review also,

One bug related to linuxbridge:
* https://bugs.launchpad.net/neutron/+bug/1728080 - already assigned to Brian 
Haley.

Bugs related to QoS:
* https://bugs.launchpad.net/neutron/+bug/1730605 - this one I was waiting for 
more info and now I want to check it, but I didn’t know what priority it should 
have (medium?)
* https://bugs.launchpad.net/neutron/+bug/1730896 - it’s about QoS docs,

One bug related to Quotas:
* https://bugs.launchpad.net/neutron/+bug/1731250 - but it was reported only 
for Ocata so I wanted to test it for master but I didn’t have time yet.

There is one more for docs:
* https://bugs.launchpad.net/neutron/+bug/1731713 - I marked it as „Invalid” as 
it was probably created automatically because of flag „docimpact” in commit 
message. Maybe we should consider disable/remove this script which is creating 
such bug reports as „DocImpact” is already removed?

One bug about neutronclient: https://bugs.launchpad.net/neutron/+bug/1731597 
but do we still should fix such bugs? I’m not sure about current status of it.

And there is also one RFE bug: https://bugs.launchpad.net/neutron/+bug/1730959 
but as it is something for LBaaS I didn’t add „rfe” tag because I’m not sure if 
it should be discussed by Neutron’s drivers team.

That’s all on my side for this week.

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl






signature.asc
Description: Message signed with OpenPGP
__
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] Gertty dashboards

[Sławek Kapłoński]

Hello,

> Wiadomość napisana przez James E. Blair <cor...@inaugust.com> w dniu 
> 23.10.2017, o godz. 18:04:
> 
> Sławek Kapłoński <sla...@kaplonski.pl> writes:
> 
>> Hello,
>> 
>> Recently I started using Getty and I think it’s good tool.
>> I have one problem which I don’t know how to solve. On web based
>> gerrit page (review.openstack.org) I have defined page with own query:
>> 
>> "(NOT owner:self) status:open label:Code-Review-0,self
>> label:Workflow=0 (project:openstack/neutron OR
>> project:openstack/neutron-lib OR project:openstack/shade)
>> branch:master”
> 
> If you haven't already, make sure you are subscribed to those three
> projects in Gertty.  That will cause it to keep up with all of the
> changes in those projects.  It also will also enable a per-project view
> of open unreviewed changes for each project, very similar to your
> dashboard.

Yes, I am subscribed to all those projects and all is synced.
I’m also using those „project views” there but I was thinking if it’s possible 
to have one view for all interesting projects for me :)

> 
> -Jim

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl



signature.asc
Description: Message signed with OpenPGP
__
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] Gertty dashboards

[Sławek Kapłoński]

Hello,

> Wiadomość napisana przez Jeremy Stanley <fu...@yuggoth.org> w dniu 
> 23.10.2017, o godz. 15:02:
> 
> On 2017-10-22 11:56:06 +0200 (+0200), Sławek Kapłoński wrote:
> [...]
>> I suppose that gertty is looking only for patches which are
>> already in local database. Is it true?
> 
> Basically, yes. As far as I've seen it syncs status for any changes
> on projects to which you've explicitly subscribed, as well as any
> for which your account is the owner in Gerrit. I believe it will
> also include changes which are in its DB because you've directly
> loaded them, but does not automatically sync/update status changes
> for those unless you view and refresh them manually. I tend to work
> around this by subscribing Gertty to all the projects in which I
> regularly participate.

I am subscribed to all of projects listed in this query which I asked for. And 
still result of this query in gertty is different than result in Gerrit webpage.
Also gertty shows me that all projects are synced.

> 
>> And is there any possibility to change it?
> 
> It's software, so probably. That said, I expect Gertty would need
> some sort of first-class dashboard support where it knows (beyond
> simple keybindings for arbitrary queries, maybe similar to how it
> treats owner:self changes?) that you want all changes for dashboards
> pulled into the local DB and kept in sync so that it has them
> available for offline operation... not sure what impact that may
> have on performance either.

Yes, I know that it’s software and that it’s open source so it’s possible to 
patch it but my question was more about if it’s possible with some config 
options currently :)

> 
> And of course you'd need to convince its author this is a worthwhile
> behavior change, since there may be good reasons it was designed to
> work this way from the outset. I'll bring this thread to Jim's
> attention once he's around today; he will doubtless have more
> accurate details and concrete suggestions than I.

Thx.

> --
> Jeremy Stanley
> __
> 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

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl



signature.asc
Description: Message signed with OpenPGP
__
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] Gertty dashboards

[Sławek Kapłoński]

Thx for pointing those typos but it doesn’t fix „main problem” :)

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Jeremy Freudberg <jeremyfreudb...@gmail.com> w dniu 
> 23.10.2017, o godz. 02:17:
> 
> I know nothing about Gertty, but it looks like you have two typos:
> 
> - Code-Review-0 should be Code-Review=0
> - openstack/shade should openstack-infra/shade
> 
> 
> That being said, there could still be other Gertty-specific things to discuss 
> here. Hope you get the answers you need!
> 
> On Sun, Oct 22, 2017 at 5:56 AM, Sławek Kapłoński <sla...@kaplonski.pl> wrote:
> Hello,
> 
> Recently I started using Getty and I think it’s good tool.
> I have one problem which I don’t know how to solve. On web based gerrit page 
> (review.openstack.org) I have defined page with own query:
> 
> "(NOT owner:self) status:open label:Code-Review-0,self label:Workflow=0 
> (project:openstack/neutron OR project:openstack/neutron-lib OR 
> project:openstack/shade) branch:master”
> 
> And it gives me list of many patches (more than 100 I think). Problem is that 
> when I configured own dashboard with exactly same query in gertty.yml file I 
> had only 22 patches displayed.
> I suppose that gertty is looking only for patches which are already in local 
> database. Is it true? And is there any possibility to change it?
> 
> —
> Best regards
> Slawek Kaplonski
> sla...@kaplonski.pl
> 
> 
> 
> 
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Gertty dashboards

[Sławek Kapłoński]

Hello,

Recently I started using Getty and I think it’s good tool.
I have one problem which I don’t know how to solve. On web based gerrit page 
(review.openstack.org) I have defined page with own query:

"(NOT owner:self) status:open label:Code-Review-0,self label:Workflow=0 
(project:openstack/neutron OR project:openstack/neutron-lib OR 
project:openstack/shade) branch:master”

And it gives me list of many patches (more than 100 I think). Problem is that 
when I configured own dashboard with exactly same query in gertty.yml file I 
had only 22 patches displayed.
I suppose that gertty is looking only for patches which are already in local 
database. Is it true? And is there any possibility to change it?

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl






signature.asc
Description: Message signed with OpenPGP
__
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] Denver Team Dinner

[Sławek Kapłoński]

+1

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Miguel Lavalle  w dniu 
> 12.09.2017, o godz. 17:23:
> 
> Dear Neutrinos,
> 
> Our social event will take place on Thursday September 12th at 7:30pm. The 
> venue is going to be https://www.famousdaves.com/Denver-Stapleton. It is 
> located 0.4 miles from the Renaissance Hotel, which translates to an easy 9 
> minutes walk.
> 
> I have a reservation for a group of 30 people under my name. Please respond 
> to this message with your attendance confirmation by Wednesday night, so I 
> can get a more accurate head count.
> 
> Looking forward to see y'all Thursday night
> 
> Best regards
> 
> Miguel
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] [ptg][nova][neutron] modelling network capabilities and capacity in placement and nova neutron port binding negociation.

[Sławek Kapłoński]

Hello,

I’m also interested in this as it can help to provide guarantee minimum 
bandwidth for instances.

—
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl




> Wiadomość napisana przez Mooney, Sean K <sean.k.moo...@intel.com> w dniu 
> 11.09.2017, o godz. 11:11:
> 
> Hi everyone,
> 
> I’m interested in set up a white boarding session at the ptg to discuss
> How to model network backend in placement and use that info as part of 
> scheduling
> 
> This work would also intersect on the nova neutron port binding  negotiation
> Work that is also in flight so I think there is merit in combining both topic 
> into one
> Session.
> 
> For several release we have been discussing a negotiation protocol that would
> Allow nova/compute services to tell neutron what virtual and physical 
> interfaces
> a hypervisor can support and then allow neutron to select from that set the 
> most appriote
> vif type based on the capabilities of the network backend deployed by the 
> host.
> 
> Extending that concept with the capabilities provided by placement and trait
> Will enable us to model the network capablites of a specific network backend
> In an scheduler friendly way without nova needing to understand networking.
> 
> To that end  if people are interested in  having a while boarding session to 
> dig
> Into this let me know.
> 
> Regards
> Seán
> --
> Intel Shannon Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> Business address: Dromore House, East Park, Shannon, Co. Clare
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Call for help with in-tree tempest scenario test failures

[Sławek Kapłoński]

Hello,

I’m still checking this QoS scenario test and I found something strange IMHO.
For example, almost all failed tests from last 2 days were executed on nodes 
with names like:
* ubuntu-xenial-2-node-citycloud-YYY- - on those nodes almost (or even all) 
all scenario tests was failed due to failed SSH connection to instance,
* ubuntu-xenial-2-node-rax-iad- - on those nodes QoS test was failed 
because of timeout during reading data

I’m noob in gate tests and how it’s exactly working so my conclusions can be 
completely wrong but maybe those issues are related somehow to some cloud 
providers which provides infrastructure for tests?
Maybe someone more experienced could take a look on that and help me? Thx in 
advance.

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Ihar Hrachyshka <ihrac...@redhat.com> w dniu 
> 03.08.2017, o godz. 23:40:
> 
> Thanks for those who stepped in (Armando and Slawek).
> 
> We still have quite some failures that would benefit from initial log
> triage and fixes. If you feel like in this feature freeze time you
> have less things to do, helping with those scenario failures would be
> a good way to contribute to the project.
> 
> Thanks,
> Ihar
> 
> On Fri, Jul 28, 2017 at 6:02 AM, Sławek Kapłoński <sla...@kaplonski.pl> wrote:
>> Hello,
>> 
>> I will try to check QoS tests in this job.
>> 
>> —
>> Best regards
>> Slawek Kaplonski
>> sla...@kaplonski.pl
>> 
>> 
>> 
>> 
>>> Wiadomość napisana przez Jakub Libosvar <jlibo...@redhat.com> w dniu 
>>> 28.07.2017, o godz. 14:49:
>>> 
>>> Hi all,
>>> 
>>> as sending out a call for help with our precious jobs was very
>>> successful last time and we swept all Python 3 functional from Neutron
>>> pretty fast (kudos the the team!), here comes a new round of failures.
>>> 
>>> This time I'm asking for your help >> poster here> with gate-tempest-dsvm-neutron-dvr-multinode-scenario
>>> non-voting job. This job has been part of check queue for a while and is
>>> very very unstable. Such job covers scenarios like router dvr/ha/legacy
>>> migrations, qos, trunk and dvr. I went through current failures and
>>> created an etherpad [1] with categorized failures and logstash queries
>>> that give you latest failures with given particular tests.
>>> 
>>> If you feel like doing troubleshooting and sending fixes for gates,
>>> please pick one test and write down your name to the test.
>>> 
>>> Thanks to all who are willing to participate.
>>> 
>>> Have a great weekend.
>>> Jakub
>>> 
>>> 
>>> [1]
>>> https://etherpad.openstack.org/p/neutron-dvr-multinode-scenario-gate-failures
>>> 
>>> 
>>> __
>>> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Call for help with in-tree tempest scenario test failures

[Sławek Kapłoński]

Hello,

I will try to check QoS tests in this job.

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Jakub Libosvar  w dniu 
> 28.07.2017, o godz. 14:49:
> 
> Hi all,
> 
> as sending out a call for help with our precious jobs was very
> successful last time and we swept all Python 3 functional from Neutron
> pretty fast (kudos the the team!), here comes a new round of failures.
> 
> This time I'm asking for your help  poster here> with gate-tempest-dsvm-neutron-dvr-multinode-scenario
> non-voting job. This job has been part of check queue for a while and is
> very very unstable. Such job covers scenarios like router dvr/ha/legacy
> migrations, qos, trunk and dvr. I went through current failures and
> created an etherpad [1] with categorized failures and logstash queries
> that give you latest failures with given particular tests.
> 
> If you feel like doing troubleshooting and sending fixes for gates,
> please pick one test and write down your name to the test.
> 
> Thanks to all who are willing to participate.
> 
> Have a great weekend.
> Jakub
> 
> 
> [1]
> https://etherpad.openstack.org/p/neutron-dvr-multinode-scenario-gate-failures
> 
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] Journey to running functional job with Python 3

[Sławek Kapłoński]

Hello,

I just added fullstack python35 job in project-config
Patch to add testing in tox.ini is ready to review also: 
https://review.openstack.org/#/c/477681
I also wrote some notes in Your etherpad and made first patch to fix fullstack 
tests: https://review.openstack.org/#/c/478652
I hope it will be helpful for You :)

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Jakub Libosvar  w dniu 
> 13.06.2017, o godz. 18:39:
> 
> Hi folks,
> 
> we've been tracking the OpenStack common goal for Python 3 in our
> Neutron CI meetings. As an outcome we created a list of categorized
> failures in current non-voting job. There are 250 failures that we split
> into 14 categories. The list can be found here:
> 
> https://etherpad.openstack.org/p/py3-neutron-pike
> 
> Consider this email as a call-for-action in case you'd like to
> participate in this goal. If you decide to work on one failure category,
> please write down your name to the etherpad above.
> 
> Thanks to all who will join this effort! :)
> 
> Jakub
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP
__
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] stepping down from neutron core team

[Sławek Kapłoński]

Hello,

Thank you for all Your help.
Good luck in Your new projects :)

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl




> Wiadomość napisana przez Miguel Angel Ajo Pelayo  w dniu 
> 28.04.2017, o godz. 11:02:
> 
> 
> Hi everybody,
> 
> Some of you already know, but I wanted to make it official.
> 
> Recently I moved to work on the networking-ovn component,
> and OVS/OVN itself, and while I'll stick around and I will be available
> on IRC for any questions I'm already not doing a good work with
> neutron reviews, so...
> 
> It's time to leave room for new reviewers.
> 
> It's always a pleasure to work with you folks.
> 
> Best regards,
> Miguel Ángel Ajo.



signature.asc
Description: Message signed with OpenPGP
__
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] Changes in QoS service plugin

[Sławek Kapłoński]

Hello,

Some time ago my patch [1] was merged. It changes list of supported 
qos_rule_types to dict with rule types as keys and list of supported parameters 
and values for each rule type.
Additionally now almost merged (I hope) is patch [2] which introduce new 
attribute `direction` to bandwidth_limit_rule type. By default it will have 
EGRESS value so it’s exactly like it was up to now.

So similar changes should be done in 3rd party QoS drivers also. I made patches 
[3], [4], [5] to networking-ovn, networking-odl and networking-midonet repos 
because I found that in those repos there is QoS driver already.

If You have QoS driver in Your repo, please update it also.

[1] https://review.openstack.org/#/c/426946/
[2] https://review.openstack.org/#/c/457816/
[3] https://review.openstack.org/#/c/460734/
[4] https://review.openstack.org/#/c/460737/
[5] https://review.openstack.org/#/c/460741/

—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl





signature.asc
Description: Message signed with OpenPGP
__
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] Development workflow for bunch of patches

[Sławek Kapłoński]

Hello,

Thanks a lot :)

— 
Best regards
Slawek Kaplonski
sla...@kaplonski.pl



> Wiadomość napisana przez Kevin Benton <ke...@benton.pub> w dniu 19.04.2017, o 
> godz. 10:25:
> 
> Whenever you want to work on the second patch you would need to first 
> checkout the latest version of the first patch and then cherry-pick the later 
> patch on top of it. That way when you update the second one it won't affect 
> the first patch.
> 
> The -R flag can also be used to prevent unexpected rebases of the parent 
> patch. More details here:
> 
> https://docs.openstack.org/infra/manual/developers.html#adding-a-dependency 
> <https://docs.openstack.org/infra/manual/developers.html#adding-a-dependency>
> 
> On Wed, Apr 19, 2017 at 1:11 AM, Sławek Kapłoński <sla...@kaplonski.pl 
> <mailto:sla...@kaplonski.pl>> wrote:
> Hello,
> 
> I have a question about how to deal with bunch of patches which depends one 
> on another.
> I did patch to neutron (https://review.openstack.org/#/c/449831/ 
> <https://review.openstack.org/#/c/449831/>) which is not merged yet but I 
> wanted to start also another patch which is depend on this one 
> (https://review.openstack.org/#/c/457816/ 
> <https://review.openstack.org/#/c/457816/>).
> Currently I was trying to do something like:
> 1. git review -d 
> 2. git checkout -b new_branch_for_second_patch
> 3. Make second patch, commit all changes
> 4. git review <— this will ask me if I really want to push two patches to 
> gerrit so I answered „yes”
> 
> Everything is easy for me as long as I’m not doing more changes in first 
> patch. How I should work with it if I let’s say want to change something in 
> first patch and later I want to make another change to second patch? IIRC 
> when I tried to do something like that and I made „git review” to push 
> changes in second patch, first one was also updated (and I lost changes made 
> for this one in another branch).
> How I should work with something like that? Is there any guide about that (I 
> couldn’t find such)?
> 
> — 
> Best regards
> Slawek Kaplonski
> sla...@kaplonski.pl <mailto:sla...@kaplonski.pl>
> 
> 
> 
> 
> __
> 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 
> <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] Development workflow for bunch of patches

[Sławek Kapłoński]

Hello,

I have a question about how to deal with bunch of patches which depends one on 
another.
I did patch to neutron (https://review.openstack.org/#/c/449831/ 
) which is not merged yet but I 
wanted to start also another patch which is depend on this one 
(https://review.openstack.org/#/c/457816/ 
).
Currently I was trying to do something like:
1. git review -d 
2. git checkout -b new_branch_for_second_patch
3. Make second patch, commit all changes
4. git review <— this will ask me if I really want to push two patches to 
gerrit so I answered „yes”

Everything is easy for me as long as I’m not doing more changes in first patch. 
How I should work with it if I let’s say want to change something in first 
patch and later I want to make another change to second patch? IIRC when I 
tried to do something like that and I made „git review” to push changes in 
second patch, first one was also updated (and I lost changes made for this one 
in another branch).
How I should work with something like that? Is there any guide about that (I 
couldn’t find such)?

— 
Best regards
Slawek Kaplonski
sla...@kaplonski.pl



__
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][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

My patch [1] to fix it in Neutron is now merged. Thx Ihar and Kevin for
so fast review :)
It looks that now functional tests are working fine.

[1] https://review.openstack.org/#/c/426550/

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sun, 29 Jan 2017, Sławek Kapłoński wrote:

> Hello,
> 
> I made small patch to Neutron to fix [1] this issue. It looks that
> functional tests are fine with it [2].
> Please review it if it makes sense for You :)
> 
> [1] https://review.openstack.org/#/c/426550/
> [2] 
> http://logs.openstack.org/50/426550/1/check/gate-neutron-dsvm-functional-ubuntu-xenial/4b56e71/console.html
> 
> -- 
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
> 
> On Sun, 29 Jan 2017, Sławek Kapłoński wrote:
> 
> > Hello,
> > 
> > Thanks for explaining that. I'm don't know this part well and that's why
> > I asked here if it's oslo or neutron issue.
> > So it looks like it is issue in Neutron nor Oslo.context, right?
> > 
> > -- 
> > Best regards / Pozdrawiam
> > Sławek Kapłoński
> > sla...@kaplonski.pl
> > 
> > On Sat, 28 Jan 2017, Joshua Harlow wrote:
> > 
> > > Yup, all that should be needed is to read the docs and adjust it.
> > > 
> > > "once" - print only the first occurrence of matching warnings, regardless 
> > > of
> > > location
> > > 
> > > "always" - always print matching warnings
> > > 
> > > Changing it to 'once' should gather less repeated logs; IMHO 'always' 
> > > should
> > > never be used, so that was probably just a mistake for whoever committed
> > > that fixture with it set like that.
> > > 
> > > -Josh
> > > 
> > > Davanum Srinivas wrote:
> > > > Graham, Sławek,
> > > > 
> > > > Have you seen this?
> > > > 
> > > > Neutron has/uses a WarningFixture:
> > > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> > > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
> > > > 
> > > > Which uses filterwarnings:
> > > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
> > > > 
> > > > Where "always" is being used:
> > > > https://docs.python.org/2/library/warnings.html
> > > > 
> > > > Which prints warnings every single time.
> > > > 
> > > > So, can we please "fix" it in there quickly?
> > > > 
> > > > Thanks,
> > > > Dims
> > > > 
> > > > On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński<sla...@kaplonski.pl>  
> > > > wrote:
> > > > > Hello,
> > > > > 
> > > > > Thanks. I just filled bug report to oslo project:
> > > > > https://bugs.launchpad.net/oslo.context/+bug/1660088
> > > > > 
> > > > > --
> > > > > Best regards / Pozdrawiam
> > > > > Sławek Kapłoński
> > > > > sla...@kaplonski.pl
> > > > > 
> > > > > On Sat, 28 Jan 2017, Hayes, Graham wrote:
> > > > > 
> > > > > > On 28/01/17 20:54, Sławek Kapłoński wrote:
> > > > > > > Hello,
> > > > > > > 
> > > > > > > I pushed today patch in Neutron to gerrit [1] and I noticed that 
> > > > > > > functional
> > > > > > > tests are failing. In logs there is huge number of deprecation 
> > > > > > > warnings
> > > > > > > displayed [2]. Tests are failing because of global timeout is 
> > > > > > > reached and IMO
> > > > > > > reason of this timeout is this huge amount of deprecation 
> > > > > > > warnings.
> > > > > > > I checked that those warnings are disaplyed when 
> > > > > > > oslo.context==2.12.0 is
> > > > > > > installed. With oslo.context==2.11.0 all is fine.
> > > > > > > Should it be reported as bug in Neutron or in Oslo project? Or 
> > > > > > > maybe You
> > > > > > > already know about it and there is some patch to fix it but I 
> > > > > > > couldn't find it?
> > > > > > Its an oslo.context bug - I can't see one filed for it yet.
> > > > > > > [1] https://review.openstack.org/#/c/426429/

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

I made small patch to Neutron to fix [1] this issue. It looks that
functional tests are fine with it [2].
Please review it if it makes sense for You :)

[1] https://review.openstack.org/#/c/426550/
[2] 
http://logs.openstack.org/50/426550/1/check/gate-neutron-dsvm-functional-ubuntu-xenial/4b56e71/console.html

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sun, 29 Jan 2017, Sławek Kapłoński wrote:

> Hello,
> 
> Thanks for explaining that. I'm don't know this part well and that's why
> I asked here if it's oslo or neutron issue.
> So it looks like it is issue in Neutron nor Oslo.context, right?
> 
> -- 
> Best regards / Pozdrawiam
> Sławek Kapłoński
> sla...@kaplonski.pl
> 
> On Sat, 28 Jan 2017, Joshua Harlow wrote:
> 
> > Yup, all that should be needed is to read the docs and adjust it.
> > 
> > "once" - print only the first occurrence of matching warnings, regardless of
> > location
> > 
> > "always" - always print matching warnings
> > 
> > Changing it to 'once' should gather less repeated logs; IMHO 'always' should
> > never be used, so that was probably just a mistake for whoever committed
> > that fixture with it set like that.
> > 
> > -Josh
> > 
> > Davanum Srinivas wrote:
> > > Graham, Sławek,
> > > 
> > > Have you seen this?
> > > 
> > > Neutron has/uses a WarningFixture:
> > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
> > > 
> > > Which uses filterwarnings:
> > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
> > > 
> > > Where "always" is being used:
> > > https://docs.python.org/2/library/warnings.html
> > > 
> > > Which prints warnings every single time.
> > > 
> > > So, can we please "fix" it in there quickly?
> > > 
> > > Thanks,
> > > Dims
> > > 
> > > On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński<sla...@kaplonski.pl>  
> > > wrote:
> > > > Hello,
> > > > 
> > > > Thanks. I just filled bug report to oslo project:
> > > > https://bugs.launchpad.net/oslo.context/+bug/1660088
> > > > 
> > > > --
> > > > Best regards / Pozdrawiam
> > > > Sławek Kapłoński
> > > > sla...@kaplonski.pl
> > > > 
> > > > On Sat, 28 Jan 2017, Hayes, Graham wrote:
> > > > 
> > > > > On 28/01/17 20:54, Sławek Kapłoński wrote:
> > > > > > Hello,
> > > > > > 
> > > > > > I pushed today patch in Neutron to gerrit [1] and I noticed that 
> > > > > > functional
> > > > > > tests are failing. In logs there is huge number of deprecation 
> > > > > > warnings
> > > > > > displayed [2]. Tests are failing because of global timeout is 
> > > > > > reached and IMO
> > > > > > reason of this timeout is this huge amount of deprecation warnings.
> > > > > > I checked that those warnings are disaplyed when 
> > > > > > oslo.context==2.12.0 is
> > > > > > installed. With oslo.context==2.11.0 all is fine.
> > > > > > Should it be reported as bug in Neutron or in Oslo project? Or 
> > > > > > maybe You
> > > > > > already know about it and there is some patch to fix it but I 
> > > > > > couldn't find it?
> > > > > Its an oslo.context bug - I can't see one filed for it yet.
> > > > > > [1] https://review.openstack.org/#/c/426429/
> > > > > > [2] 
> > > > > > http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
> > > > > > 
> > > > > It looks like the warnings function was miss used - this should be set
> > > > > as a once only message. The stack trace level seems suspect, as it
> > > > > points as neutron/context.py as the one sending out the notice, not
> > > > > oslo.contexts base class.
> > > > > 
> > > > > [3] seems to the cause - I would suggest reverting this commit and
> > > > > doing a 2.13.0 release. This is going to be *really* noisy. (logstash
> > > > > has 2.5 million items for this string in the last 24 hours)
> > > > > 
> > > > > 3 -
&

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

Thanks for explaining that. I'm don't know this part well and that's why
I asked here if it's oslo or neutron issue.
So it looks like it is issue in Neutron nor Oslo.context, right?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sat, 28 Jan 2017, Joshua Harlow wrote:

> Yup, all that should be needed is to read the docs and adjust it.
> 
> "once" - print only the first occurrence of matching warnings, regardless of
> location
> 
> "always" - always print matching warnings
> 
> Changing it to 'once' should gather less repeated logs; IMHO 'always' should
> never be used, so that was probably just a mistake for whoever committed
> that fixture with it set like that.
> 
> -Josh
> 
> Davanum Srinivas wrote:
> > Graham, Sławek,
> > 
> > Have you seen this?
> > 
> > Neutron has/uses a WarningFixture:
> > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
> > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
> > 
> > Which uses filterwarnings:
> > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n80
> > 
> > Where "always" is being used:
> > https://docs.python.org/2/library/warnings.html
> > 
> > Which prints warnings every single time.
> > 
> > So, can we please "fix" it in there quickly?
> > 
> > Thanks,
> > Dims
> > 
> > On Sat, Jan 28, 2017 at 6:46 PM, Sławek Kapłoński<sla...@kaplonski.pl>  
> > wrote:
> > > Hello,
> > > 
> > > Thanks. I just filled bug report to oslo project:
> > > https://bugs.launchpad.net/oslo.context/+bug/1660088
> > > 
> > > --
> > > Best regards / Pozdrawiam
> > > Sławek Kapłoński
> > > sla...@kaplonski.pl
> > > 
> > > On Sat, 28 Jan 2017, Hayes, Graham wrote:
> > > 
> > > > On 28/01/17 20:54, Sławek Kapłoński wrote:
> > > > > Hello,
> > > > > 
> > > > > I pushed today patch in Neutron to gerrit [1] and I noticed that 
> > > > > functional
> > > > > tests are failing. In logs there is huge number of deprecation 
> > > > > warnings
> > > > > displayed [2]. Tests are failing because of global timeout is reached 
> > > > > and IMO
> > > > > reason of this timeout is this huge amount of deprecation warnings.
> > > > > I checked that those warnings are disaplyed when oslo.context==2.12.0 
> > > > > is
> > > > > installed. With oslo.context==2.11.0 all is fine.
> > > > > Should it be reported as bug in Neutron or in Oslo project? Or maybe 
> > > > > You
> > > > > already know about it and there is some patch to fix it but I 
> > > > > couldn't find it?
> > > > Its an oslo.context bug - I can't see one filed for it yet.
> > > > > [1] https://review.openstack.org/#/c/426429/
> > > > > [2] 
> > > > > http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
> > > > > 
> > > > It looks like the warnings function was miss used - this should be set
> > > > as a once only message. The stack trace level seems suspect, as it
> > > > points as neutron/context.py as the one sending out the notice, not
> > > > oslo.contexts base class.
> > > > 
> > > > [3] seems to the cause - I would suggest reverting this commit and
> > > > doing a 2.13.0 release. This is going to be *really* noisy. (logstash
> > > > has 2.5 million items for this string in the last 24 hours)
> > > > 
> > > > 3 -
> > > > https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
> > > > 
> > > > __
> > > > 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


signature.asc
Description: 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

Re: [openstack-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

Thanks. I just filled bug report to oslo project:
https://bugs.launchpad.net/oslo.context/+bug/1660088

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sat, 28 Jan 2017, Hayes, Graham wrote:

> On 28/01/17 20:54, Sławek Kapłoński wrote:
> > Hello,
> > 
> > I pushed today patch in Neutron to gerrit [1] and I noticed that functional 
> > tests are failing. In logs there is huge number of deprecation warnings 
> > displayed [2]. Tests are failing because of global timeout is reached and 
> > IMO 
> > reason of this timeout is this huge amount of deprecation warnings.
> > I checked that those warnings are disaplyed when oslo.context==2.12.0 is 
> > installed. With oslo.context==2.11.0 all is fine.
> > Should it be reported as bug in Neutron or in Oslo project? Or maybe You 
> > already know about it and there is some patch to fix it but I couldn't find 
> > it?
> 
> Its an oslo.context bug - I can't see one filed for it yet.
> > 
> > [1] https://review.openstack.org/#/c/426429/
> > [2] 
> > http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
> > 
> 
> It looks like the warnings function was miss used - this should be set
> as a once only message. The stack trace level seems suspect, as it
> points as neutron/context.py as the one sending out the notice, not
> oslo.contexts base class.
> 
> [3] seems to the cause - I would suggest reverting this commit and
> doing a 2.13.0 release. This is going to be *really* noisy. (logstash
> has 2.5 million items for this string in the last 24 hours)
> 
> 3 -
> https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea
> 
> __
> 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


signature.asc
Description: 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-dev] [Neutron][Oslo] Huge number of deprecation warnings in functional tests

[Sławek Kapłoński]

Hello,

I pushed today patch in Neutron to gerrit [1] and I noticed that functional 
tests are failing. In logs there is huge number of deprecation warnings 
displayed [2]. Tests are failing because of global timeout is reached and IMO 
reason of this timeout is this huge amount of deprecation warnings.
I checked that those warnings are disaplyed when oslo.context==2.12.0 is 
installed. With oslo.context==2.11.0 all is fine.
Should it be reported as bug in Neutron or in Oslo project? Or maybe You 
already know about it and there is some patch to fix it but I couldn't find it?

[1] https://review.openstack.org/#/c/426429/
[2] 
http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html
-- 
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

signature.asc
Description: This is a digitally signed message part.
__
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][ml2] Mechanism drivers ! OpenvSwich or Linuxbridge or both of them?

[Sławek Kapłoński]

Hello,

I don't know what is hierarchical port binding but about mechanism
drivers, You should use this mechanism driver which L2 agent You are
using on compute/network nodes. If You have OVS L2 agent then You should
have enabled openvswitch mechanism driver.
In general both of those drivers are doing similar work on
neutron-server side because they are checking if proper agent type is
working on host and if other conditions required to bind port are valid.
Mechanism drivers can have also some additional informations about
backend driver, e.g. there is info about supported QoS rule types for
each backend driver (OVS, Linuxbridge and SR-IOV).

BTW. IMHO You should send such questions to openst...@lists.openstack.org

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Fri, 30 Dec 2016, zhi wrote:

> Hi, all
> 
> First of all. Happy New year for everyone!
> 
> I have a question about mechanism drivers when using ML2 driver.
> 
> When should I use openvswitch mechanism driver ?
> 
> When should I use linuxbridge mechanism driver ?
> 
> And, when should I use openvswitch and linuxbridge mechanism drivers ?
> 
> In my opinion, ML2 driver has supported hierarchical port binding. By using
> hierarchical port binding,
> neutron will know every binding info in network topology, isn't it? If yes,
> where I can found the every binding info. And what the relationship between
> hierarchical port binding and mechanism drivers?
> 
> 
> Hope for your reply.
> 
> Thanks
> Zhi Chang

> __
> 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



signature.asc
Description: 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-dev] [neutron] [fullstack] Test of DHCP agent HA

[Sławek Kapłoński]

Hello,

Some time ago I introduced basic test for DHCP agent in fullstack tests
([1]).
Now I want to add test(s) for HA of DHCP agent - I started it in [2]. I
want to add which will:
* create environment with 2 hosts and 2 dhcp agents,
* spawn FakeMachine and check if it will get IP address,
* kill DHCP agent which hosts DHCP for created network,
* wait a while and check if another DHCP agent starts hosting this
  network,
* spawn new FakeMachine and check if it will get IP address from DHCP

So it looks quite easy but there is one problem. Dhcp agent creates
network namespace with name "qdhcp-" and spawn there dnsmasq
process. This dnsmasq is using tap interface in this namespace. So when
I killed first dhcp agent, it not removes qdhcp- namespace
so second agent want's to "reuse" it. Problem is that in this namespace
still is running dnsmasq spawned by first agent.
So I think that best solution would be to change somehow DHCP agent that
each agent will create namespaces with names like
"qdhcp--some-random-suffix". And my question is how to do it
in easiest way? I wanted to do it in same way how it is in L3 agent in
fullstack but I would need to "override" couple methods from agent only
for tests and I don't think it's good idea.
Maybe someone more experienced will have some better ideas how to do it.


[1] https://review.openstack.org/#/c/409432/
[2] https://review.openstack.org/#/c/413994/

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl



signature.asc
Description: 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

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

[Sławek Kapłoński]

Hello,

Ok, I will try maybe to write such specs if I will have a while.

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Thu, 17 Nov 2016, Chris Friesen wrote:

> On 11/17/2016 04:58 AM, Sławek Kapłoński wrote:
> > Hello,
> > 
> > Ok. So it's different case. I was thinking only about issues with
> > quotas.
> > For me this which You described is more related to scheduler/placement
> > API(?).
> > Do You think that it should be taken in same specs?
> 
> Given that we need a spec to cover any changes to publicly-visible
> behaviour, I think it would make sense to lump together any changes around
> what happens when you try to boot multiple instances and only some of them
> can be booted.
> 
> I think it's basically irrelevant what the reasons are why some couldn't be
> booted--as long as the requested "min-count" instances can be booted
> successfully then they should proceed to boot and the request should count
> as successful.
> 
> And as I said before, if at least "min-count" instances can be booted
> successfully then the remaining instances should not go into error state but
> rather should just be transparently deleted as though they never existed.

I agree here with You. It is like that in some cases, e.g. like I
described before on summary which I made.

> 
> Chris
> 
> __
> 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


signature.asc
Description: 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

Re: [openstack-dev] [neutron][osc] Openstack client, Openstack SDK and neutronclient consistency

[Sławek Kapłoński]

Hello,

Thx for clarifications and closing this bug.

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Thu, 17 Nov 2016, Akihiro Motoki wrote:

> I totally agree with the direction of OSC and shade.
> The similar discussion happens in neutronclient side before too.
> 
> From user perspective, 'name' is really useful to identify resources,
> even though admin usually use ID to identify resources.
> In the past neutronclient discussion, requiring at least one parameter is
> useful
> to avoid issuing a command line by mistake. It is another feedback from
> user experience.
> 
> The neutronclient bug should be closed with Won't Fix.
> 
> Akihiro
> 
> 
> 2016-11-17 19:55 GMT+09:00 Sławek Kapłoński <sla...@kaplonski.pl>:
> 
> > Hello,
> >
> > Thx all of You for explanations. So I think that [1] can be closed as
> > "Won't fix" now. Am I right?
> >
> > [1] https://bugs.launchpad.net/neutron/+bug/1640767
> >
> > --
> > Best regards / Pozdrawiam
> > Sławek Kapłoński
> > sla...@kaplonski.pl
> >
> > On Wed, 16 Nov 2016, Dean Troyer wrote:
> >
> > > > Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100:
> > > >> Hello,
> > > >> So I want to ask all of You how in Your opinion it should be solved.
> > > >> Currently there is inconsistency between CLI clients and
> > > >> API/Horizon/Openstack SDK (I checked that it is possible to create
> > > >> resource without name via SDK).
> > >
> > > There are a number of intentional inconsistencies between OSC and the
> > > various REST APIs, precisely because many of the the APIs themselves
> > > are very inconsistent not only between projects but even within each
> > > project.  When those APIs are directly reflected in the CLI, like
> > > happens with many of the project-specific CLIs, the users suffer due
> > > to the inconsistencies.
> > >
> > >
> > > On Wed, Nov 16, 2016 at 4:03 PM, Doug Hellmann <d...@doughellmann.com>
> > wrote:
> > > > The OpenStackClient team made the decision to always require names
> > > > for newly created resources. Perhaps Dean or Steve can fill in more
> > > > of the background, but my understanding is that this is a design
> > > > decision for the user interface implemented by OSC, and not is not
> > > > considered a bug.
> > >
> > > Doug is correct here, we (OpenStackClient) made a specific decision in
> > > the command structure to always use the resource name as the
> > > positional argument of a create command.  In this case I believe the
> > > consistency is worth what pain it may cause to invent a name for a new
> > > policy.
> > >
> > > We have done UX surveys with OSC at the last two summits and the
> > > number one favorable comment from the users (varying from cloud
> > > consumers to operators to OpenStack developers) has been regarding how
> > > much they appreciate the command consistency.  This is our biggest
> > > feature.
> > >
> > > dt
> > >
> > > --
> > >
> > > Dean Troyer
> > > dtro...@gmail.com
> > >
> > > 
> > __
> > > 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



signature.asc
Description: 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

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

[Sławek Kapłoński]

Hello,

Ok. So it's different case. I was thinking only about issues with
quotas.
For me this which You described is more related to scheduler/placement
API(?).
Do You think that it should be taken in same specs?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Thu, 17 Nov 2016, Chris Friesen wrote:

> On 11/17/2016 12:27 AM, Chris Friesen wrote:
> > On 11/16/2016 03:55 PM, Sławek Kapłoński wrote:
> > > As I said before, I was testing it and I didn't have instances in Error
> > > state. Can You maybe check it once again on current master branch?
> > 
> > I don't have a master devstack handy...will try and set one up.  I just 
> > tried on
> > a stable/mitaka devstack--I bumped up the quotas and ran:
> > 
> > nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec --min-count 1
> > --max-count 100 blah
> > 
> > All the instances went to the "scheduling" state, the first 21 instances
> > scheduled successfully then one failed the RamFilter.  I ended up with 100
> > instances all in the "error" state.
> 
> I located a running devstack based on master, the nova repo was using commit
> 633c817d from Nov 12.
> 
> It behaved the same...I jacked up the quotas to give it space, then ran:
> 
> nova boot --flavor m1.xlarge --image cirros-0.3.4-x86_64-uec --min-count 1
> --max-count 20 blah
> 
> 
> The first nine instances scheduled successfully, the next one failed the
> RamFilter filter, and all the instances went to the "error" state.
> 
> This is what we'd expect given that in ComputeTaskManager.build_instances()
> if the call to self._schedule_instances() raises an exception we'll hit the
> "except" clause and loop over all the instances, setting them to the error
> state.  And down in FilterScheduler.select_destinations() we will raise an
> exception if we couldn't schedule all the hosts:
> 
> if len(selected_hosts) < num_instances:
>   
>   reason = _('There are not enough hosts available.')
>   raise exception.NoValidHost(reason=reason)
> 
> Chris
> 
> __
> 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


signature.asc
Description: 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

Re: [openstack-dev] [neutron][osc] Openstack client, Openstack SDK and neutronclient consistency

[Sławek Kapłoński]

Hello,

Thx all of You for explanations. So I think that [1] can be closed as
"Won't fix" now. Am I right?

[1] https://bugs.launchpad.net/neutron/+bug/1640767

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Wed, 16 Nov 2016, Dean Troyer wrote:

> > Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100:
> >> Hello,
> >> So I want to ask all of You how in Your opinion it should be solved.
> >> Currently there is inconsistency between CLI clients and
> >> API/Horizon/Openstack SDK (I checked that it is possible to create
> >> resource without name via SDK).
> 
> There are a number of intentional inconsistencies between OSC and the
> various REST APIs, precisely because many of the the APIs themselves
> are very inconsistent not only between projects but even within each
> project.  When those APIs are directly reflected in the CLI, like
> happens with many of the project-specific CLIs, the users suffer due
> to the inconsistencies.
> 
> 
> On Wed, Nov 16, 2016 at 4:03 PM, Doug Hellmann <d...@doughellmann.com> wrote:
> > The OpenStackClient team made the decision to always require names
> > for newly created resources. Perhaps Dean or Steve can fill in more
> > of the background, but my understanding is that this is a design
> > decision for the user interface implemented by OSC, and not is not
> > considered a bug.
> 
> Doug is correct here, we (OpenStackClient) made a specific decision in
> the command structure to always use the resource name as the
> positional argument of a create command.  In this case I believe the
> consistency is worth what pain it may cause to invent a name for a new
> policy.
> 
> We have done UX surveys with OSC at the last two summits and the
> number one favorable comment from the users (varying from cloud
> consumers to operators to OpenStack developers) has been regarding how
> much they appreciate the command consistency.  This is our biggest
> feature.
> 
> dt
> 
> -- 
> 
> Dean Troyer
> dtro...@gmail.com
> 
> __
> 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


signature.asc
Description: 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

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

[Sławek Kapłoński]

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Wed, 16 Nov 2016, Chris Friesen wrote:

> On 11/15/2016 06:50 PM, melanie witt wrote:
> > On Tue, 15 Nov 2016 18:10:40 -0600, Chris Friesen wrote:
> > > I'm in favor of your change, since the existing behaviour doesn't make
> > > sense.
> > > 
> > > But at some point I guess consistency trumps correctness, and if a new
> > > microversion is necessary to mark the new behaviour then a spec is
> > > required, and at that point we might want to fix the other issues with
> > > multi-boot at the same time.  (Like
> > > https://bugs.launchpad.net/nova/+bug/1458122 )
> > 
> > I think what Sławek is saying is that the quota behavior for multi-create
> > already changed at some point in the past, without a spec. He did 
> > experiments
> > recently that show a multi-create request succeeds as long as the min_count 
> > is
> > satisfied when there isn't enough quota for max_count. This is different 
> > than
> > the behavior at the time you opened the bug. So it seems the horse has left 
> > the
> > barn on this one.
> 
> The bug I reported is not related to quota, but rather the ability to
> schedule the instances.
> 
> The issue in the bug report is that if I ask to boot a min of X and a max of
> Z instances, and only Y instances can be scheduled (where X<Y<Z) then the
> request will fail and all the instances will be put into an ERROR state.

As I said before, I was testing it and I didn't have instances in Error
state. Can You maybe check it once again on current master branch?

> 
> Arguably what *should* happen is that Y instances get created.  Also I think
> it would make more sense if the remaining  Z-Y instances are just never
> created rather than being created in an ERROR state.
> 
> Chris
> 
> 
> 
> __
> 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


signature.asc
Description: 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-dev] [neutron] Openstack client, Openstack SDK and neutronclient consistency

[Sławek Kapłoński]

Hello,

Few days ago someone reported bug [1] and I started checking it. I found
that when I'm trying to create QoS policy with neutronclient or OSC then
name parameter is neccessary.
But this parameter is not neccessary in Neutron API - I can create
policy without name when calling API directly (e.g. with curl).
For me it is bug on neutronclient and openstack client side and it
should be IMHO fixed to allow creating QoS policy without name (so
without any parameter given in fact: "neutron qos-policy-create").

But today on QoS IRC meeting we were talking about it and reedip point
us another bug [2] (and his patch [3]) which concerns same problem but with
different parameter.
And in this patchset amotoki said that it can't be fixed in way that
allows to create resource without any parameter given in
openstack/neutron client.

So I want to ask all of You how in Your opinion it should be solved.
Currently there is inconsistency between CLI clients and
API/Horizon/Openstack SDK (I checked that it is possible to create
resource without name via SDK).
I checked it for QoS policy (and network in SDK) but I think that it
might be more generic issue.

[1] https://bugs.launchpad.net/neutron/+bug/1640767
[2] https://launchpad.net/bugs/1520055
[3] https://review.openstack.org/#/c/250587/

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl



signature.asc
Description: 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

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

[Sławek Kapłoński]

Hello,

IMHO receiving multiple uuids is not related to bug which I want to
resolve somehow but if Chris wrote it I thought that it is maybe somehow
related to "spawn multiple instances" feature.
So can You maybe review my patch
https://review.openstack.org/#/c/371592/ to fix
https://bugs.launchpad.net/nova/+bug/1623809 or I really need new specs
for that?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Mon, 14 Nov 2016, melanie witt wrote:

> On Mon, 14 Nov 2016 17:34:28 -0600, Matt Riedemann wrote:
> > Why do we want to return a list of uuids for servers created? I thought
> > that's why we have the 'return_reservation_id' request parameter for the
> > server multiple-create scenario so that you can get a single reservation
> > ID back and all of the servers created are using that same
> > reservation_id and then you can query them by that later if you want to
> > list them out.
> 
> As far as I know, doing that would be a nice-to-have for people using
> multi-create, so they get the uuids in one step instead of having to do a
> second query for them using the reservation_id. It's not technically
> necessary and I don't think it's related to this multi-create quota behavior
> issue.
> 
> -melanie
> 
> 
> 
> 
> __
> 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


signature.asc
Description: 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

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

[Sławek Kapłoński]

Hello,

I remember that Melanie told me that there was another issues there and
I talked with her to check all cases. Are You sure that but
https://bugs.launchpad.net/nova/+bug/1458122 is still valid? I tried to
spawn instances with min=3 and max=11 when quota was set to 10 and I had
spawned 10 instances properly (no any in error state). I also checked it
with givin only max=11 (no min value, so set to 1 by default) and I had
also 10 instances spawned.

All results of my tests can be found in http://pastebin.com/Te71HJ8q if
You want.

I agree that it would be nice to e.g. return uuids of all instances but
is really necessary specs to fix this issue which I reported (and IMHO
only inconsistency there)?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Mon, 14 Nov 2016, Chris Friesen wrote:

> On 11/11/2016 07:07 AM, Sławek Kapłoński wrote:
> > Hello,
> > 
> > Can maybe someone (from core team) take a look on that? Thx in advance :)
> 
> 
> As Melanie Witt mentioned on your bug report, there are a number of issues
> around multi-boot.   (I reported
> https://bugs.launchpad.net/nova/+bug/1458122 last year, for example.)
> 
> Getting rid of multi-boot has been proposed a number of times but was shot
> down on efficiency arguments.
> 
> In order to improve this someone needs to write up a spec to make the whole
> multi-boot story coherent.  At a minimum this would need to address:
> 
> 1) the quota issue you raised
> 2) the partial completion issue I raised
> 3) returning the uuids of all instances booted as a result of the multiboot 
> API call
> 
> Since it means a spec, probably nothing will happen in Ocata...we could
> maybe see about Pike.
> 
> Chris
> 
> __
> 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


signature.asc
Description: 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

Re: [openstack-dev] [nova] Problem with Quota and servers spawned in groups

[Sławek Kapłoński]

Hello,

Can maybe someone (from core team) take a look on that? Thx in advance :)

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Mon, 07 Nov 2016, Sławek Kapłoński wrote:

> Hello,
> 
> Some time ago I found that there is problem with unconsistent behaviour
> (IMHO) of Nova API when user wants to spawn bunch of instances in server
> group (affinity or anti-affinity). I described it in [1].
> I also made some summary how Nova is working in different cases of
> spawning instances. Results are like below:
> 
> +-+---+---++-+
> | QUOTAS  |   |   |   
>  | |
> +--+--+ min_count | max_count |  number of 
> spawned instances   | Expected result |
> |instances | server_group_members |   |   |   
>  | |
> +==+==+===+===++=+
> |10|  5   | 3 | 4 | 4 
>  |4|
> +--+--+---+---++-+
> |10|  5   | 6 | 9 |Quota exceeded, 
> too many servers|Group Quota  |
> |  |  |   |   |in group (HTTP 
> 403) |exceeded |
> +--+--+---+---++-+
> |10|  5   | 3 | 6 |Quota exceeded, 
> too many servers|5|
> |  |  |   |   |in group (HTTP 
> 403) | |
> +--+--+---+---++-+
> |10|  5   | 3 |11 |Quota exceeded, 
> too many servers|5|
> |  |  |   |   |in group (HTTP 
> 403) | |
> +--+--+---+---++-+
> |10|  5   | 6 |11 |Quota exceeded, 
> too many servers|Group Quota  |
> |  |  |   |   |in group (HTTP 
> 403) |exceeded |
> +--+--+---+---++-+
> |10|  5   | 3 | - | 3 
>  |3|
> +--+--+---+---++-+
> |10|  5   | 6 | - |Quota exceeded, 
> too many servers|Group Quota  |
> |  |  |   |   |in group (HTTP 
> 403) |exceeded |
> +--+--+---+---++-+
> |10|  5   | 11| - |Quota exceeded for 
> instances:   |Servers Quota|
> |  |  |   |   |Requested 11, but 
> already used 0|exceeded |
> |  |  |   |   | of 10 instances   
>  | |
> +--+--+---+---++-+
> |10|  5   | - | 3 | 3 
>  |3|
> +--+--+---+---++-+
> |10|  5   | - | 6 |Quota exceeded, 
> too many servers|Group Quota  |
> |  |  |   |   |in group (HTTP 
> 403) |exceeded |
> +--+--+---+---++-+
> |10|  5   | - | 11|Quota exceeded, 
> too many servers|Group Quota  |
> |  |  |   |   |in group (HTTP 
> 403) |exceeded |
> +--+--+---+---++-+
> 
> In "expected result" I described behaviour which I suppose that is should be
> there.
> Can 

[openstack-dev] [nova] Problem with Quota and servers spawned in groups

[Sławek Kapłoński]

Hello,

Some time ago I found that there is problem with unconsistent behaviour
(IMHO) of Nova API when user wants to spawn bunch of instances in server
group (affinity or anti-affinity). I described it in [1].
I also made some summary how Nova is working in different cases of
spawning instances. Results are like below:

+-+---+---++-+
| QUOTAS  |   |   | 
   | |
+--+--+ min_count | max_count |  number of spawned 
instances   | Expected result |
|instances | server_group_members |   |   | 
   | |
+==+==+===+===++=+
|10|  5   | 3 | 4 | 4   
   |4|
+--+--+---+---++-+
|10|  5   | 6 | 9 |Quota exceeded, too 
many servers|Group Quota  |
|  |  |   |   |in group (HTTP 403)  
   |exceeded |
+--+--+---+---++-+
|10|  5   | 3 | 6 |Quota exceeded, too 
many servers|5|
|  |  |   |   |in group (HTTP 403)  
   | |
+--+--+---+---++-+
|10|  5   | 3 |11 |Quota exceeded, too 
many servers|5|
|  |  |   |   |in group (HTTP 403)  
   | |
+--+--+---+---++-+
|10|  5   | 6 |11 |Quota exceeded, too 
many servers|Group Quota  |
|  |  |   |   |in group (HTTP 403)  
   |exceeded |
+--+--+---+---++-+
|10|  5   | 3 | - | 3   
   |3|
+--+--+---+---++-+
|10|  5   | 6 | - |Quota exceeded, too 
many servers|Group Quota  |
|  |  |   |   |in group (HTTP 403)  
   |exceeded |
+--+--+---+---++-+
|10|  5   | 11| - |Quota exceeded for 
instances:   |Servers Quota|
|  |  |   |   |Requested 11, but 
already used 0|exceeded |
|  |  |   |   | of 10 instances 
   | |
+--+--+---+---++-+
|10|  5   | - | 3 | 3   
   |3|
+--+--+---+---++-+
|10|  5   | - | 6 |Quota exceeded, too 
many servers|Group Quota  |
|  |  |   |   |in group (HTTP 403)  
   |exceeded |
+--+--+---+---++-+
|10|  5   | - | 11|Quota exceeded, too 
many servers|Group Quota  |
|  |  |   |   |in group (HTTP 403)  
   |exceeded |
+--+--+---+---++-+

In "expected result" I described behaviour which I suppose that is should be
there.
Can You maybe check it and tell me if I'm right here and there is really bug as
described in [1]?

I also made some patch to fix it [2] so please review it if You think that it
is worth to fix this behaviour.

[1] https://bugs.launchpad.net/nova/+bug/1623809
[2] https://review.openstack.org/#/c/371592/

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl



signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
U

Re: [openstack-dev] [neutron][linux bridge]

[Sławek Kapłoński]

Hello,

What about tc_lib.py and function to set bandwidth limits which
linuxbridge agent is currently using?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Thu, 07 Jul 2016, Bhatia, Manjeet S wrote:

> Hi,
> 
> There is work in progress for pure python driven linux network configuration. 
> I think most
> of work will be done with this patch https://review.openstack.org/#/c/155631/ 
> . The only
> thing left after this will be linux bridge configuration, Which I would like 
> to discuss with
> community. There are two ways at the moment I can think to do that 
> implementation,
> First, use pybrctl which may need some changes in library itself in order for 
> full support.
> It will clean up the code from neutron. But looking pybrctl code which is 
> just executing
> Shell commands, another solution which Brandon Logan discussed is move the 
> existing
> Code for executing those commands to neutron-lib, which I think is better 
> solution. I would
> like to have views of community, especially people working neutron-lib about 
> moving
> python code for executing brctl commands to neutron-lib.
> 
> 
> Thanks and Regards !
> Manjeet Singh Bhatia

> __
> 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



signature.asc
Description: Digital 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-dev] [neutron][alembic] Upgrade of db with alembic migration script

[Sławek Kapłoński]

Hello,

I'm working on patch to add QoS ingress bandwidth limit to Neutron
currently: https://review.openstack.org/303626 and I have small problem
with db upgrade with alembic.
Problem description:
In qos_bandwidth_limit_rules table now there is foreign key
"qos_policy_id" with unique constraint.
I need to add new column called "direction" to this table and then remove
unique constraint for qos_policy_id. At the end I need to add new unique
constraint to pair (direction, qos_policy_id).
To do that I need to:
1. remove qos_policy_id foreign key
2. remove unique constraint for qos_policy_id (because it is not removed
automatically)
3. add new column
4. add new unique constraint

Points 3 and 4 are easy and there is no problem with it.

Problem is with point 2 (remove unique constraint)
To remove qos_policy_id fk I used function:
neutron.db.migration.migration.remove_fks_from_table() and it is working
fine but it's not removing unique constraint.
I made some modification to this function:
https://review.openstack.org/#/c/303626/21/neutron/db/migration/__init__.py
and this modifications works fine for mysql but in pgsql this unique
constraint is not removed so after all there is two constraints in table
and this is wrong.

I'm not expert in pgsql and alembic. Maybe someone with bigger
experience can look on it and help me how to do such migration script?

Thx in advance for any help.

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl



signature.asc
Description: Digital 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

Re: [openstack-dev] [neutron] Social at the summit

[Sławek Kapłoński]

Hello,

+1

-- 
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia poniedziałek, 25 kwietnia 2016 17:21:56 CDT Korzeniewski, Artur pisze:
> Sign me up :)
> 
> Artur
> IRC: korzen
> 
> -Original Message-
> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
> Sent: Monday, April 25, 2016 7:19 PM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [neutron]
> Social at the summit
> 
> Count me in!
> Will be good to meet all you guys!
> 
> Darek (dasm) Smigiel
> 
> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley <doug...@parksidesoftware.com> 
wrote:
> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka <ihrac...@redhat.com>
> >> wrote:
> >> 
> >> WAT???
> >> 
> >> It was never supposed to be core only. Everyone is welcome!
> > 
> > +2
> > 
> > irony intended.
> > 
> > Socials are not controlled by gerrit ACLs.  :-)
> > 
> > doug
> > 
> >> Sent from my iPhone
> >> 
> >>> On 25 Apr 2016, at 11:56, Edgar Magana <edgar.mag...@workday.com> wrote:
> >>> 
> >>> Would you extend it to ex-cores?
> >>> 
> >>> Edgar
> >>> 
> >>>> On 4/25/16, 10:55 AM, "Kyle Mestery" <mest...@mestery.com> wrote:
> >>>> 
> >>>> Ihar, Henry and I were talking and we thought Thursday night makes
> >>>> sense for a Neutron social in Austin. If others agree, reply on this
> >>>> thread and we'll find a place.
> >>>> 
> >>>> Thanks!
> >>>> Kyle
> >>>> 
> >>>> ___
> >>>> ___ 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 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


signature.asc
Description: This is a digitally signed message part.
__
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][kilo] - vxlan's max bandwidth

[Sławek Kapłoński]

Hello,

We made it exactly in that way on vms :)

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Mon, 18 Apr 2016, Akihiro Motoki wrote:

> 2016-04-18 15:58 GMT+09:00 Ihar Hrachyshka <ihrac...@redhat.com>:
> > Sławek Kapłoński <sla...@kaplonski.pl> wrote:
> >
> >> Hello,
> >>
> >> What MTU have You got configured on VMs? I had issue with performance on
> >> vxlan network with standard MTU (1500) but when I configured Jumbo
> >> frames on vms and on hosts then it was much better.
> >
> >
> > Right. Note that custom MTU works out of the box only starting from Mitaka.
> > You can find details on how to configure Neutron for Jumbo frames in the
> > official docs:
> >
> > http://docs.openstack.org/mitaka/networking-guide/adv-config-mtu.html
> 
> If you want to advertise MTU using DHCP in releases before Mitaka,
> you can prepare your custom dnsmasq config file like below and
> set it to dhcp-agent dnsmasq_config_file config option.
> You also need to set network_device_mtu config parameters appropriately.
> 
> sample dnsmasq config file:
> --
> dhcp-option-force=26,8950
> --
> dhcp option 26 specifies MTU.
> 
> Akihiro
> 
> 
> >
> >
> > Ihar
> > __
> > 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


signature.asc
Description: Digital 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

Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

[Sławek Kapłoński]

Hello,

What MTU have You got configured on VMs? I had issue with performance on
vxlan network with standard MTU (1500) but when I configured Jumbo
frames on vms and on hosts then it was much better.

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Fri, 15 Apr 2016, Rick Jones wrote:

> On 04/14/2016 07:10 PM, Kenny Ji-work wrote:
> >Hi all,
> >
> >In the environment of openstack kilo, I test the bandwidth in the scene
> >which VxLan being used. The result show that the vxlan can only support
> >up to 1 gbits bandwidth. Is this a bug or any else issue, or is there
> >some hotfix to solve the issue? Thank you for answering!
> 
> I'm glossing over some details, but broadly speaking, a single network flow
> cannot take advantage of more than one CPU in a system.  And while network
> speeds have been continuing to increase, per-core speeds haven't really gone
> up much over the last five to ten years.
> 
> So, to get "speed/link rate" networking stacks have become dependent on
> stateless offloads - Checksum Offload (CKO) TCP Segmentation Offload
> (TSO/GSO) and Generic Receive Offload 9GRO).  And until somewhat recently,
> NICs did not offer stateless offloads for VxLAN-encapsulated traffic.  So,
> one effectively has a "dumb" NIC without stateless offloads.  And depending
> on what sort of processor you have, that limit could be down around 1
> Gbit/s.  Only some of the more recent 10GbE NICs offer stateless offload of
> VxLAN-encapsulated traffic, and similarly their more recent drivers and
> networking stacks.
> 
> In olden days, before the advent of stateless offloads there was a rule of
> thumb - 1 Mbit/s per MHz.  That was with "pure" bare-iron networking - no
> VMs, no encapsulation.  Even then it was a bit hand-wavy, and may have
> originated in the land of SPARC processors.  But hopefully it conveys the
> idea of what it means to lose the stateless offloads.
> 
> So, it would be good to know what sort of CPUs are involved (down to the
> model names and frequencies) as well as the NICs involved - again, full
> naming, not just the brand name.
> 
> And it is just a paranoid question, but is there any 1 Gbit/s networking in
> your setup at all?
> 
> happy benchmarking,
> 
> rick jones
> 
> 
> __
> 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


signature.asc
Description: Digital 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

Re: [openstack-dev] Does Neutron itself add VM ports to ovs?

[Sławek Kapłoński]

Hello,

It's nova-compute service which is configuring it. This service is running on 
compute node: http://docs.openstack.org/developer/nova/architecture.html

-- 
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia wtorek, 12 kwietnia 2016 16:16:25 CEST 张晨 pisze:
> Thx for the answer, i finally locate the implementation in
> nova.network.linux_net.create_ovs_vif_port
> 
> 
> but how could nova execute the ovs-vsctl for the compute-node hypervisor
> just in the control-node?
> At 2016-04-12 13:13:48, "Sławek Kapłoński" <sla...@kaplonski.pl> wrote:
> >Hello,
> >
> >I don't know this ODL and how it works but for ovs-agent nova-compute is
> >part which adds port to ovs bridge (see for example
> >nova/virt/libvirt/vif.py)>
> >> Hello everyone,
> >> 
> >> 
> >> I have a question about Neutron. I learn that the ovs-agent receives the
> >> update-port rpc notification,and updates ovsdb data for VM port.
> >> 
> >> 
> >> But what is the situation when i use SDN controllers instead of OVS
> >> mechanism driver? I found no where in ODL to add the VM port to ovs.
> >> 
> >> 
> >> I asked the author of the related ODL plugin, but he told me that
> >> OpenStack
> >> adds the VM port to ovs.
> >> 
> >> 
> >> Then, where is the implementation in OpenStack to  add the VM port to
> >> ovs,
> >> when i'm using ODL replacing the OVSmechanism driver?
> >> 
> >> 
> >> Thanks

signature.asc
Description: This is a digitally signed message part.
__
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] Does Neutron itself add VM ports to ovs?

[Sławek Kapłoński]

Hello,

I don't know this ODL and how it works but for ovs-agent nova-compute is part 
which adds port to ovs bridge (see for example nova/virt/libvirt/vif.py)

-- 
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia wtorek, 12 kwietnia 2016 12:31:01 CEST 张晨 pisze:
> Hello everyone,
> 
> 
> I have a question about Neutron. I learn that the ovs-agent receives the
> update-port rpc notification,and updates ovsdb data for VM port.
> 
> 
> But what is the situation when i use SDN controllers instead of OVS
> mechanism driver? I found no where in ODL to add the VM port to ovs.
> 
> 
> I asked the author of the related ODL plugin, but he told me that OpenStack
> adds the VM port to ovs.
> 
> 
> Then, where is the implementation in OpenStack to  add the VM port to ovs,
> when i'm using ODL replacing the OVSmechanism driver?
> 
> 
> Thanks

signature.asc
Description: This is a digitally signed message part.
__
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] Fullstack tests question

[Sławek Kapłoński]

Hello,

I'm currently working on patch https://review.openstack.org/#/c/248938/7 which 
will provide support for LinuxBridge agent in fullstack tests (and make 
connectivity test for that type of agents).
In this test I'm spawning LinuxBridge agent in "host" namespace.
Generally tests are working fine now if I run it as root. When I run it as 
normal user then LinuxBridge agent process is not spawned in namespace and 
tests are failing.
I suppose that problem is with missing rootwrap rule for spawning such process 
in namespace but I have no idea how to add such rootwrap rules for fullstack 
tests. Can You maybe help me with that or point some links to documentation 
where I could find any info about that?

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

signature.asc
Description: This is a digitally signed message part.
__
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] ML2 TypeManager question

[Sławek Kapłoński]

Hello,

In fact we were creating our own type driver and we want to use this tenant_id 
so it was good that it is here :) But I was just curious why it is like that. 
Thanks.

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia Wednesday 09 of December 2015 09:55:36 Kevin Benton pisze:
> It does not appear to be used. I suspect maybe the original intention is
> that this could be passed to the type driver which might do something
> special depending on the tenant_id. However, the type driver interface does
> not include the tenant_id in 'allocate_tenant_segment' so we should either
> update the type driver interface to include that or just remove it from
> create_network_segments.
> 
> On Mon, Dec 7, 2015 at 9:28 AM, Sławek Kapłoński <sla...@kaplonski.pl>
> 
> wrote:
> > Hello,
> > 
> > Recently I was checking something in code of ML2 Type manager
> > (neutron.plugins.ml2.managers) and I found in TypeManager class in method
> > create_network_segments that to this method as argument is passed
> > "tenant_id"
> > but I can't find where it is used.
> > Can someone more experienced explain me why this tenant_id is passed there
> > and
> > where it is used? Thx in advance :)
> > 
> > --
> > Pozdrawiam / Best regards
> > Sławek Kapłoński
> > sla...@kaplonski.pl
> > __
> > 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

signature.asc
Description: This is a digitally signed message part.
__
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] ML2 TypeManager question

[Sławek Kapłoński]

Hello,

Recently I was checking something in code of ML2 Type manager 
(neutron.plugins.ml2.managers) and I found in TypeManager class in method 
create_network_segments that to this method as argument is passed "tenant_id" 
but I can't find where it is used.
Can someone more experienced explain me why this tenant_id is passed there and 
where it is used? Thx in advance :)

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

signature.asc
Description: This is a digitally signed message part.
__
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] Question about Microsoft Hyper-V CI tests

[Sławek Kapłoński]

Hello,

I'm now working on patch to neutron to add QoS in linuxbridge: https://
review.openstack.org/#/c/236210/
Patch is not finished yet but I have some "problem" with some tests. For 
example Microsoft Hyper-V CI check are failing. When I checked logs of this 
tests in http://64.119.130.115/neutron/236210/7/results.html.gz file I found 
error like:

ft1.1: setUpClass 
(tempest.api.network.test_networks.NetworksIpV6TestAttrs)_StringException: 
Traceback (most recent call last):
  File "tempest/test.py", line 274, in setUpClass
six.reraise(etype, value, trace)
  File "tempest/test.py", line 267, in setUpClass
cls.resource_setup()
  File "tempest/api/network/test_networks.py", line 65, in resource_setup
cls.network = cls.create_network()
  File "tempest/api/network/base.py", line 152, in create_network
body = cls.networks_client.create_network(name=network_name)
  File "tempest/services/network/json/networks_client.py", line 21, in 
create_network
return self.create_resource(uri, post_data)
  File "tempest/services/network/json/base.py", line 59, in create_resource
resp, body = self.post(req_uri, req_post_data)
  File "/usr/local/lib/python2.7/dist-packages/tempest_lib/common/
rest_client.py", line 259, in post
return self.request('POST', url, extra_headers, headers, body)
  File "/usr/local/lib/python2.7/dist-packages/tempest_lib/common/
rest_client.py", line 639, in request
resp, resp_body)
  File "/usr/local/lib/python2.7/dist-packages/tempest_lib/common/
rest_client.py", line 757, in _error_checker
resp=resp)
tempest_lib.exceptions.UnexpectedResponseCode: Unexpected response code 
received
Details: 503


It is strange for me because it looks that error is somewhere in 
create_network. I didn't change anything in code which is creating networks. 
Other tests are fine IMHO.
So my question is: should I check reason of this errors and try to fix it also 
in my patch? Or how should I proceed with such kind of errors?

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

signature.asc
Description: This is a digitally signed message part.
__
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] Openvswitch agent unit tests

[Sławek Kapłoński]

Hello,

Thx for Your tips. So I should focus more on write new functional tests
for ovs agent if there are missing some rather then doing unit tests for
it?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Mon, 28 Sep 2015, Assaf Muller wrote:

> Generally speaking, testing agent methods that interact with the system
> heavily with unit tests provide very little,
> and arguably negative value to the project. Mocking internal methods and
> asserting that they were called is a
> clear anti-pattern to my mind. In Neutron-land we prefer to test agent code
> with functional tests.
> Since 'functional tests' is a very over-loaded term, what I mean by that is
> specifically running the actual unmocked
> code on the system and asserting the expected behavior.
> 
> Check out:
> neutron/tests/functional/agent/test_ovs_lib
> neutron/tests/functional/agent/test_l2_ovs_agent
> 
> On Mon, Sep 28, 2015 at 3:45 PM, Sławek Kapłoński <sla...@kaplonski.pl>
> wrote:
> 
> > Hello,
> >
> > I'm new developer who want to start contributing to neutron. I have some
> > small experience with neutron already but I didn't do anything which I
> > could push to upstream for now. So I searched for some bug on launchpad
> > and I found such bug which I took:
> > https://bugs.launchpad.net/neutron/+bug/1285893 and I started to
> > checking how I can write new tests (I think that it is quite easy job to
> > do for the beginning but maybe I'm wrong).
> > Now I have some questions to You:
> > 1. From test-coverage I can see that for example there is missing
> > coverage like in lines 349-350 in method _restore_local_vlan_map(self) -
> > should
> > I create new test and call that metod to check if proper exception will
> > be raised? or maybe it is not neccessary at all and such "one lines"
> > missing coverage is not really needed to be checked? Or maybe it should
> > be done in some different way?
> >
> > 2. What about tests for methods like: "_local_vlan_for_flat" which is
> > not checked at all? should be created new test for such method? or maybe
> > it should be covered by some different test?
> >
> > Thanks in advance for any advice and tips how to write such unit tests
> > properly :)
> >
> > --
> > Best regards / Pozdrawiam
> > Sławek Kapłoński
> > sla...@kaplonski.pl
> >
> >
> > __
> > 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



signature.asc
Description: Digital 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-dev] Openvswitch agent unit tests

[Sławek Kapłoński]

Hello,

I'm new developer who want to start contributing to neutron. I have some
small experience with neutron already but I didn't do anything which I
could push to upstream for now. So I searched for some bug on launchpad
and I found such bug which I took:
https://bugs.launchpad.net/neutron/+bug/1285893 and I started to
checking how I can write new tests (I think that it is quite easy job to
do for the beginning but maybe I'm wrong).
Now I have some questions to You:
1. From test-coverage I can see that for example there is missing
coverage like in lines 349-350 in method _restore_local_vlan_map(self) - should
I create new test and call that metod to check if proper exception will
be raised? or maybe it is not neccessary at all and such "one lines"
missing coverage is not really needed to be checked? Or maybe it should
be done in some different way?

2. What about tests for methods like: "_local_vlan_for_flat" which is
not checked at all? should be created new test for such method? or maybe
it should be covered by some different test?

Thanks in advance for any advice and tips how to write such unit tests
properly :)

--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl



signature.asc
Description: Digital 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

Re: [openstack-dev] Where can I find the neutron ml2 mechanism driver list?

[Sławek Kapłoński]

Hello,

Check setup.cfg file - there are entry points for all drivers in this
file.

--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Sun, Apr 19, 2015 at 12:13:30AM -0700, Sam Su wrote:
 Hi,
 
 I am learning the existing Neutron code (Juno) and am going to add a ML2
 driver. I can see the following debug info in neutron.log:
 
 
 
 
 
 *2015-04-18 23:21:13.729 11068 DEBUG stevedore.extension [-] found
 extension EntryPoint.parse('hyperv =
 neutron.plugins.ml2.drivers.mech_hyperv:HypervMechanismDriver')
 _load_plugins
 /usr/lib/python2.7/site-packages/stevedore/extension.py:1562015-04-18
 23:21:13.729 11068 DEBUG stevedore.extension [-] found extension
 EntryPoint.parse('l2population =
 neutron.plugins.ml2.drivers.l2pop.mech_driver:L2populationMechanismDriver')
 _load_plugins
 /usr/lib/python2.7/site-packages/stevedore/extension.py:1562015-04-18
 23:21:13.729 11068 DEBUG stevedore.extension [-] found extension
 EntryPoint.parse('cisco_apic =
 neutron.plugins.ml2.drivers.cisco.apic.mechanism_apic:APICMechanismDriver')
 _load_plugins
 /usr/lib/python2.7/site-packages/stevedore/extension.py:1562015-04-18
 23:21:13.730 11068 DEBUG stevedore.extension [-] found extension
 EntryPoint.parse('arista =
 neutron.plugins.ml2.drivers.arista.mechanism_arista:AristaDriver')
 _load_plugins
 /usr/lib/python2.7/site-packages/stevedore/extension.py:156...( Click
 http://pastebin.com/3ssdHGZf http://pastebin.com/3ssdHGZf for the detail
 )*
 
 From the above log we can see, neutron.plugins.ml2.managers can find all
 driver extensions e.g. hyperv, l2population etc, as my understanding, there
 should exist a driver list on somewhere. If I am right, where can I find
 the driver list? If not, can someone give me a clue?
 
 Any help will be much appreciated.
 
 Thanks,
 Sam

 __
 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] openwrt VM as service

[Sławek Kapłoński]

Hello,

-- 
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Wed, Apr 15, 2015 at 11:06:49PM +0200, Salvatore Orlando wrote:
 I think this work falls into the service VM category.
 
 openwrt unlike other service VMs used for networking services (like
 cloudstack's router vm) is very lightweight, and it's fairly easy to
 provision such VMs on the fly. It should be easy also to integrate with a
 ML2 control plane or even with other plugins.
 
 It is a decent alternative to the l3 agent. Possibly to the dhcp agent as
 well. As I see this as an alternative to part of the reference control
 plane, I expect it to provide its own metadata proxy. The only change in
 neutron would be some sort of configurability in the metadata proxy
 launcher (assuming you do not provide DHCP as well via openwrt, in which
 case the problem would not exist, probably).
 
 It's not my call about whether this should live in neutron or not. My vote
 is not - simply because I believe that neutron is not a control plane, and
 everything that is control plane or integration with it should live outside
 of neutron, including our agents.
 
 On the other hand, I don't really see what the 'aaS' part of this. You're
 not exposing anything as a service specific to openwrt, are you?

I told here only my (maybe not good) idea that instead of openwrt as a
service which will provide router functionalities in vm maybe better
would be to provide some mechanism to make possibility to connect
different vms which provide such router functionalities (something like
service here).

 
 Salvatore
 
 
 
 On 15 April 2015 at 22:06, Sławek Kapłoński sla...@kaplonski.pl wrote:
 
  Hello,
 
  I agree. IMHO it should be maybe something like *aaS deployed on VM. I
  think that Octavia is something like that for LBaaS now.
  Maybe it could be something like RouteraaS which will provide all such
  functions in VM?
 
  --
  Best regards / Pozdrawiam
  Sławek Kapłoński
  sla...@kaplonski.pl
 
  On Wed, Apr 15, 2015 at 11:55:06AM -0500, Dean Troyer wrote:
   On Wed, Apr 15, 2015 at 2:37 AM, Guo, Ruijing ruijing@intel.com
  wrote:
  
  I’d like to propose openwrt VM as service.
   
   
   
What’s openWRT VM as service:
   
   
   
a)Tenant can download openWRT VM from
http://downloads.openwrt.org/
   
b)Tenant can create WAN interface from external public
  network
   
c)Tenant can create private network and create instance
  from
private network
   
d)Tenent can configure openWRT for several services
  including
DHCP, route, QoS, ACL and VPNs.
   
  
  
   So first off, I'll be the first on in line to promote using OpenWRT for
  the
   basis of appliances for this sort of thing.  I use it to overcome the
  'joy'
   of VirtualBox's local networking and love what it can do in 64M RAM.
  
   However, what you are describing are services, yes, but I think to focus
  on
   the OpenWRT part of it is missing the point.  For example, Neutron has a
   VPNaaS already, but I agree it can also be built using OpenWRT and
   OpenVPN.  I don't think it is a stand-alone service though, using a
   combination of Heat/{ansible|chef|puppet|salt}/any other
   deployment/orchestration can get you there.  I have a shell script
   somewhere for doing exactly that on AWS from way back.
  
   What I've always wanted was an image builder that would customize the
   packages pre-installed.  This would be especially useful for disposable
   ramdisk-only or JFFS images that really can't install additional
  packages.
   Such a front-end to the SDK/imagebuilder sounds like about half of what
  you
   are talking about above.
  
   Also, FWIW, a while back I packaged up a micro cloud-init replacement[0]
  in
   shell that turns out to be really useful.  It's based on something I
   couldn't find again to give proper attribution so if anyone knows who
   originated this I'd be grateful.
  
   dt
  
   [0] https://github.com/dtroyer/openwrt-packages/tree/master/rc.cloud
   --
  
   Dean Troyer
   dtro...@gmail.com
 
  
  __
   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] openwrt VM as service

[Sławek Kapłoński]

Hello,

I agree. IMHO it should be maybe something like *aaS deployed on VM. I
think that Octavia is something like that for LBaaS now.
Maybe it could be something like RouteraaS which will provide all such
functions in VM?

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

On Wed, Apr 15, 2015 at 11:55:06AM -0500, Dean Troyer wrote:
 On Wed, Apr 15, 2015 at 2:37 AM, Guo, Ruijing ruijing@intel.com wrote:
 
I’d like to propose openwrt VM as service.
 
 
 
  What’s openWRT VM as service:
 
 
 
  a)Tenant can download openWRT VM from
  http://downloads.openwrt.org/
 
  b)Tenant can create WAN interface from external public network
 
  c)Tenant can create private network and create instance from
  private network
 
  d)Tenent can configure openWRT for several services including
  DHCP, route, QoS, ACL and VPNs.
 
 
 
 So first off, I'll be the first on in line to promote using OpenWRT for the
 basis of appliances for this sort of thing.  I use it to overcome the 'joy'
 of VirtualBox's local networking and love what it can do in 64M RAM.
 
 However, what you are describing are services, yes, but I think to focus on
 the OpenWRT part of it is missing the point.  For example, Neutron has a
 VPNaaS already, but I agree it can also be built using OpenWRT and
 OpenVPN.  I don't think it is a stand-alone service though, using a
 combination of Heat/{ansible|chef|puppet|salt}/any other
 deployment/orchestration can get you there.  I have a shell script
 somewhere for doing exactly that on AWS from way back.
 
 What I've always wanted was an image builder that would customize the
 packages pre-installed.  This would be especially useful for disposable
 ramdisk-only or JFFS images that really can't install additional packages.
 Such a front-end to the SDK/imagebuilder sounds like about half of what you
 are talking about above.
 
 Also, FWIW, a while back I packaged up a micro cloud-init replacement[0] in
 shell that turns out to be really useful.  It's based on something I
 couldn't find again to give proper attribution so if anyone knows who
 originated this I'd be grateful.
 
 dt
 
 [0] https://github.com/dtroyer/openwrt-packages/tree/master/rc.cloud
 -- 
 
 Dean Troyer
 dtro...@gmail.com

 __
 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] :Blueprint for FwaaS

[Sławek Kapłoński]

Ok, thanks for information and tips about that :)

On Mon, Apr 06, 2015 at 10:11:27AM +, Vikram Choudhary wrote:
 Hi Slawek,
 
 Please find my respose inline.
 
 Thanks
 Vikram
 
 -Original Message-
 From: Sławek Kapłoński [mailto:sla...@kaplonski.pl] 
 Sent: 06 April 2015 14:54
 To: openstack-dev@lists.openstack.org
 Subject: [openstack-dev] :Blueprint for FwaaS
 
 Hello,
 
 I made blueprint for fwaas:
 https://blueprints.launchpad.net/neutron/+spec/fwaas-rules-directions
 AFAIU Now I should write specs for that change. And here is my question:
 
 
 I see that fwaas is now separate project so should I make my specs in 
 http://git.openstack.org/cgit/openstack/neutron-specs/ or maybe there is some 
 other place to put such specs for neutron-fwaas?
  FWAAS is an advanced service defined under neutron hood. So, any 
  changes/proposal for FWAAS must fall under neutron. You must specify the 
  release version for your spec. Currently, neutron spec is opened for 
  liberty release. 
 
 FYI: You can refer to  https://www.youtube.com/watch?v=eEZqPfeL1Eo;  or  
 Working on Specifications and Blueprints as mentioned in 
 http://docs.openstack.org/infra/manual/developers.html  for more details.
 
 It is my first try to do something like that so maybe I'm completly wrong and 
 I should do it in different way?
 
 --
 Pozdrawiam / Best regards
 Sławek Kapłoński
 sla...@kaplonski.pl
 
 __
 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

-- 
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

__
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] :Blueprint for FwaaS

[Sławek Kapłoński]

Hello,

I made blueprint for fwaas:
https://blueprints.launchpad.net/neutron/+spec/fwaas-rules-directions
AFAIU Now I should write specs for that change. And here is my question:
I see that fwaas is now separate project so should I make my specs in
http://git.openstack.org/cgit/openstack/neutron-specs/ or maybe there is
some other place to put such specs for neutron-fwaas?
It is my first try to do something like that so maybe I'm completly
wrong and I should do it in different way?

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

__
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] [ML2] using binding:tun_ip instead of agent_ip for l2pop to support agentless backend

[Sławek Kapłoński]

Hello,

I think that easiest way could be to have own mech_driver (AFAIK such
drivers are for such usage) to talk with external devices to tell them
what tunnels should it establish.
With change to tun_ip Henry propese l2_pop agent will be able to
establish tunnel with external device.

On Mon, Mar 30, 2015 at 10:19:38PM +0200, Mathieu Rohon wrote:
 hi henry,
 
 thanks for this interesting idea. It would be interesting to think about
 how external gateway could leverage the l2pop framework.
 
 Currently l2pop sends its fdb messages once the status of the port is
 modified. AFAIK, this status is only modified by agents which send
 update_devce_up/down().
 This issue has also to be addressed if we want agent less equipments to be
 announced through l2pop.
 
 Another way to do it is to introduce some bgp speakers with e-vpn
 capabilities at the control plane of ML2 (as a MD for instance). Bagpipe
 [1] is an opensource bgp speaker which is able to do that.
 BGP is standardized so equipments might already have it embedded.
 
 last summit, we talked about this kind of idea [2]. We were going further
 by introducing the bgp speaker on each compute node, in use case B of [2].
 
 [1]https://github.com/Orange-OpenSource/bagpipe-bgp
 [2]http://www.slideshare.net/ThomasMorin1/neutron-and-bgp-vpns-with-bagpipe
 
 On Thu, Mar 26, 2015 at 7:21 AM, henry hly henry4...@gmail.com wrote:
 
  Hi ML2er,
 
  Today we use agent_ip in L2pop to store endpoints for ports on a
  tunnel type network, such as vxlan or gre. However this has some
  drawbacks:
 
  1) It can only work with backends with agents;
  2) Only one fixed ip is supported per-each agent;
  3) Difficult to interact with other backend and world outside of Openstack.
 
  L2pop is already widely accepted and deployed in host based overlay,
  however because it use agent_ip to populate tunnel endpoint, it's very
  hard to co-exist and inter-operating with other vxlan backend,
  especially agentless MD.
 
  A small change is suggested that the tunnel endpoint should not be the
  attribute of *agent*, but be the attribute of *port*, so if we store
  it in something like *binding:tun_ip*, it is much easier for different
  backend to co-exists. Existing ovs agent and bridge need a small
  patch, to put the local agent_ip into the port context binding fields
  when doing port_up rpc.
 
  Several extra benefits may also be obtained by this way:
 
  1) we can easily and naturally create *external vxlan/gre port* which
  is not attached by an Nova booted VM, with the binding:tun_ip set when
  creating;
  2) we can develop some *proxy agent* which manage a bunch of remote
  external backend, without restriction of its agent_ip.
 
  Best Regards,
  Henry
 
  __
  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


-- 
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

__
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] Generic question about synchronizing neutron agent on compute node with DB

[Sławek Kapłoński]

Hello,

I read blueprint which You send but I don't know how it should solve for 
example problems like can be in l2pop mechanism. It send message to fanout 
cast and forget about it. There is no any exception in port_update_postcommit 
operation but message can be not consumed by some agents (or maybe I'm wrong 
and it couldn't happen?) and then this agent is not synced with neutron db. 

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia poniedziałek, 16 marca 2015 11:05:45 Mohammad Banikazemi pisze:
 It is perhaps worth mentioning that there is an effort to implement a
 generic synchronization mechanism (between Neutron and backend
 controllers/devices) in the ML2 plugin [1]. A possible framework for its
 eventual implementation is in an early discussion/proof-of-concept WIP
 state [2].
 
 -Mohammad
 
 [1] https://blueprints.launchpad.net/neutron/+spec/ml2-driver-sync
 [2] https://review.openstack.org/#/c/154333/
 
 
 
 From: Cory Benfield cory.benfi...@metaswitch.com
 To:   OpenStack Development Mailing List (not for usage questions)
 openstack-dev@lists.openstack.org
 Date: 03/16/2015 04:48 AM
 Subject:  Re: [openstack-dev] [neutron] Generic question about
 synchronizing neutron agent on compute node with DB
 
 On Sun, Mar 15, 2015 at 22:37:59, Sławek Kapłoński wrote:
  Maybe good idea for the beginning could be to implement some periodic
  task
  called from agent to check db config and compare it with real state on
  host?
  What do You think? Or maybe I'm competly wrong with such idea and it
  should be
  done in different way?
 
 This is almost exactly what we do in our Calico ML2 driver. Each of our
 agents will periodically request its complete state from a neutron-server
 node and will ensure that its local state matches that expected state. This
 interval is configurable, to allow administrators to make a trade-off
 between DB/network load and convergence time.
 
 With reliable transport this is in principle almost never needed (messages
 only really get lost on agent crash, and the agent will resynchronize when
 it starts back up anyway), but it provides assurances that the fabric is
 capable of bringing itself into consistency without administrator
 intervention.
 
 Having similar function in other neutron agents would be valuable for the
 exact same reasons, but do bear in mind the potentially increased load this
 kind of resynchronization can place on databases and servers.
 
 Cory
 __
 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] Generic question about synchronizing neutron agent on compute node with DB

[Sławek Kapłoński]

Hello,

Thanks. I didn't find it before.
When we will upgrade our infra we will see if this problem will still present. 
I hope that this was due to that bug maybe and will be fixed then :) 

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia poniedziałek, 16 marca 2015 00:14:57 Mathieu Rohon pisze:
 Hi slawek,
 
 may be you're hitting this l2pop bug :
 https://bugs.launchpad.net/neutron/+bug/1372438
 
 On Sun, Mar 15, 2015 at 11:37 PM, Sławek Kapłoński sla...@kaplonski.pl
 
 wrote:
  Hello,
  
  Dnia niedziela, 15 marca 2015 17:45:05 Salvatore Orlando pisze:
   On 14 March 2015 at 11:19, Sławek Kapłoński sla...@kaplonski.pl wrote:
Hello,

I'm using ovs agents with L2 population mechanism in ML2 plugin. I
  
  noticed
  
that sometimes agents don't receive proper RPC to add new vxlan tunnel
openflow rules and then vxlan network between some compute nodes not
working.
I'm now using still havana release but want to upgrade to Juno. I was
checking
Juno code in l2 population mech driver and ovs plugin and I didn't
find
anything like periodic check if openflow rules are proper set or maybe
resynced.
Maybe it would be also good idea to add something like that to ovs
  
  agent?
  
   It would surely be a good idea to add some form of reliability into
   communications between server and agents.
   So far there are still several instances where the server sends a fire
  
  and
  
   forget notification to the agent, and does not take any step to ensure
  
  the
  
   state change associated with that notification has been actually applied
  
  to
  
   the agent. This applies also to some messages from the agent side, such
  
  as
  
   status change notifications.
  
  Maybe good idea for the beginning could be to implement some periodic task
  called from agent to check db config and compare it with real state on
  host?
  What do You think? Or maybe I'm competly wrong with such idea and it
  should be
  done in different way?
  
   This is something that can be beneficial any neutron implementation
   which
   depends on one or more agents, not just for those using the ovs/linux
   bridge agents with the l2-population driver.
  
  Probably yes, but I had this problem only with this l2-population driver
  so
  far and that's why I wrote about it :)
  
  --
  Pozdrawiam / Best regards
  Sławek Kapłoński
  sla...@kaplonski.pl
  
   Salvatore
   
--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia piątek, 13 marca 2015 11:18:28 YAMAMOTO Takashi pisze:
  However, I briefly looked through the L2 agent code and didn't see
  
  a
  
  periodic task to resync the port information to protect from a
  
  neutron
  
  server that failed to send a notification because it crashed or
  
  lost
  
its

  amqp connection. The L3 agent has a period sync routers task that

helps in

  this regard. Maybe another neutron developer more familiar with
  
  the L2
  
  agent can chime in here if I'm missing anything.
 
 i don't think you are missing anything.
 periodic sync would be a good improvement.
 
 YAMAMAOTO Takashi
  
  __
  
 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] Generic question about synchronizing neutron agent on compute node with DB

[Sławek Kapłoński]

Hello,

Dnia niedziela, 15 marca 2015 17:45:05 Salvatore Orlando pisze:
 On 14 March 2015 at 11:19, Sławek Kapłoński sla...@kaplonski.pl wrote:
  Hello,
  
  I'm using ovs agents with L2 population mechanism in ML2 plugin. I noticed
  that sometimes agents don't receive proper RPC to add new vxlan tunnel
  openflow rules and then vxlan network between some compute nodes not
  working.
  I'm now using still havana release but want to upgrade to Juno. I was
  checking
  Juno code in l2 population mech driver and ovs plugin and I didn't find
  anything like periodic check if openflow rules are proper set or maybe
  resynced.
  Maybe it would be also good idea to add something like that to ovs agent?
 
 It would surely be a good idea to add some form of reliability into
 communications between server and agents.
 So far there are still several instances where the server sends a fire and
 forget notification to the agent, and does not take any step to ensure the
 state change associated with that notification has been actually applied to
 the agent. This applies also to some messages from the agent side, such as
 status change notifications.

Maybe good idea for the beginning could be to implement some periodic task 
called from agent to check db config and compare it with real state on host?
What do You think? Or maybe I'm competly wrong with such idea and it should be 
done in different way?

 
 This is something that can be beneficial any neutron implementation which
 depends on one or more agents, not just for those using the ovs/linux
 bridge agents with the l2-population driver.

Probably yes, but I had this problem only with this l2-population driver so 
far and that's why I wrote about it :)

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

 
 Salvatore
 
  --
  Pozdrawiam / Best regards
  Sławek Kapłoński
  sla...@kaplonski.pl
  
  Dnia piątek, 13 marca 2015 11:18:28 YAMAMOTO Takashi pisze:
However, I briefly looked through the L2 agent code and didn't see a
periodic task to resync the port information to protect from a neutron
server that failed to send a notification because it crashed or lost
  
  its
  
amqp connection. The L3 agent has a period sync routers task that
  
  helps in
  
this regard. Maybe another neutron developer more familiar with the L2
agent can chime in here if I'm missing anything.
   
   i don't think you are missing anything.
   periodic sync would be a good improvement.
   
   YAMAMAOTO Takashi
  
  __
  
   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] Generic question about synchronizing neutron agent on compute node with DB

[Sławek Kapłoński]

Hello,

I'm using ovs agents with L2 population mechanism in ML2 plugin. I noticed 
that sometimes agents don't receive proper RPC to add new vxlan tunnel 
openflow rules and then vxlan network between some compute nodes not working.
I'm now using still havana release but want to upgrade to Juno. I was checking 
Juno code in l2 population mech driver and ovs plugin and I didn't find 
anything like periodic check if openflow rules are proper set or maybe 
resynced. 
Maybe it would be also good idea to add something like that to ovs agent?

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia piątek, 13 marca 2015 11:18:28 YAMAMOTO Takashi pisze:
  However, I briefly looked through the L2 agent code and didn't see a
  periodic task to resync the port information to protect from a neutron
  server that failed to send a notification because it crashed or lost its
  amqp connection. The L3 agent has a period sync routers task that helps in
  this regard. Maybe another neutron developer more familiar with the L2
  agent can chime in here if I'm missing anything.
 
 i don't think you are missing anything.
 periodic sync would be a good improvement.
 
 YAMAMAOTO Takashi
 
 __
 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] Question about bug 1314614

[Sławek Kapłoński]

Hello,

Answears below

Dnia niedziela, 8 marca 2015 13:53:51 Ian Wells pisze:
 On 6 March 2015 at 13:16, Sławek Kapłoński sla...@kaplonski.pl wrote:
  Hello,
  
  Today I found bug https://bugs.launchpad.net/neutron/+bug/1314614 because
  I
  have such problem on my infra.
 
 (For reference, if you delete a port that a Nova is using - it just goes
 ahead and deletes the port from Neutron and leaves the VIF in an odd state,
 disconnected and referring to a port that no longer exists.)

I know and for me problem is that in such situation nova on some instance 
still have got some IP and neutron provide it to other vm because it is free 
in neutron's db.

 
 I saw that bug is In progress but change is abandoned quite long time
 
  ago. I
  was wondering is it possible that neutron will send notification to nova
  that
  such port was deleted in neutron? I know that in Juno neutron is sending
  notifications to nova when port is UP on compute node so maybe same
  mechanism
  can be used to notify nova that port is no longer exists and nova should
  delete it?
 
 What behaviour are you looking for?
I was thinking that maybe neutron can send notification to nova in such 
situation and nova can do interface-detach in that case.

 
 The patch associated with the bug falls attempts to stop deletion of used
 ports.  It falls far short of implementing consistent behaviour, which
 would have to take into account everything that used ports (including DHCP,
 L3, network services, etc.), it would probably need to add an 'in-use' flag
 to the port itself, and it changes the current API behaviour rather
 markedly.  We could go there but there's much more code to be written.
 


 Someone on the bug suggests removing the VIF from the instance if the port
 is deleted, but I don't think that's terribly practical - for some instance
 containers it would not be possible.
Ok, so if it is not possible for some containers, than I was wrong and idea 
about notification to nova is not good. I was using only kvm vms so for me 
such solution is possible I think.
 
 The current behaviour does seem to be consistent and logical, if perhaps
 unexpected and a bit rough around the edges.  I'm not sure orphaning and
 isolating a VIF is actually a bad thing if you know it's going to happen,
 though it needs to be clear from the non-Neutron side that the VIF is no
 longer bound to a port, which is where things seem to fall down right now.
 
I see only problem with IP assignment in such situation.

 I've also found no documentation about when delete should work and when it
 shouldn't, or what happens if the port is bound (the API and CLI document
 say that the operation 'deletes a port' and not much else).

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

__
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] Question about bug 1314614

[Sławek Kapłoński]

Hello,

Today I found bug https://bugs.launchpad.net/neutron/+bug/1314614 because I 
have such problem on my infra. 
I saw that bug is In progress but change is abandoned quite long time ago. I 
was wondering is it possible that neutron will send notification to nova that 
such port was deleted in neutron? I know that in Juno neutron is sending 
notifications to nova when port is UP on compute node so maybe same mechanism 
can be used to notify nova that port is no longer exists and nova should 
delete it?

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

__
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] FWaaS - question about drivers

[Sławek Kapłoński]

Hello,

Thanks a lot for explanation. Now is is more clear for me :)

--
Pozrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

W dniu 2015-02-21 o 01:20, Sumit Naiksatam pisze:

Inline...

On Fri, Feb 20, 2015 at 3:38 PM, Sławek Kapłoński sla...@kaplonski.pl wrote:

Hello,

Thx guys. Now it is clear for me :)
One more question. I saw that in this service plugin there is hardcoded quota
1 firewall per tenant. Do you know why it is so limited? Is there any
important reason for that?


This is a current limitation of the reference implementation, since we
associate the FWaaS firewall resource with all the neutron routers.
Note that this is not a limitation of the FWaaS model, hence, if your
backend can support it, you can override this limitation.


And second thing. As there is only one firewall per tenant so all rules from
it will be applied on all routers (L3 agents) from this tenant and for all
tenant networks, am I right? If yes, how it is solved to set firewall rules


In general, this limitation is going away in the Kilo release. See the
following patch under review which removes the limitation of one
router per tenant:
https://review.openstack.org/#/c/152697/


when for example new router is created? L3 agent is asking about rules via rpc
or FwaaS is sending such notification to L3 agent?


In the current implementation this is automatically reconciled.
Whenever a new router comes up, the FWaaS agent pulls the rules, and
applies it on the interfaces of the new router.


Sorry if my questions are silly but I didn't do anything with this service
plugins yet :)

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia piątek, 20 lutego 2015 16:27:33 Doug Wiegley pisze:

Same project, shiny new repo.

doug


On Feb 20, 2015, at 4:05 PM, Sławek Kapłoński sla...@kaplonski.pl wrote:

Hello,

Thx for tips. I have one more question. You point me fo neutron-fwaas
project which for me looks like different project then neutron. I saw
fwaas service plugin directly in neutron in Juno. So which version
should I use: this neutron-fwaas or service plugin from neutron? Or maybe
it is the same or I misunderstand something?

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia piątek, 20 lutego 2015 14:44:21 Sumit Naiksatam pisze:

Inline...

On Wed, Feb 18, 2015 at 7:48 PM, Vikram Choudhary

vikram.choudh...@huawei.com wrote:

Hi,

You can write your own driver. You can refer to below links for getting
some idea about the architecture.

https://wiki.openstack.org/wiki/Neutron/ServiceTypeFramework


This is a legacy construct and should not be used.


https://wiki.openstack.org/wiki/Neutron/LBaaS/Agent


The above pointer is to a LBaaS Agent which is very different from a
FWaaS driver (which was the original question in the email).

FWaaS does use pluggable drivers and the default is configured here:
https://github.com/openstack/neutron-fwaas/blob/master/etc/fwaas_driver.i
ni

For example for FWaaS driver implementation you can check here:
https://github.com/openstack/neutron-fwaas/tree/master/neutron_fwaas/serv
ice s/firewall/drivers


Thanks
Vikram

-Original Message-
From: Sławek Kapłoński [mailto: ]
Sent: 19 February 2015 02:33
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] FWaaS - question about drivers

Hello,

I'm looking to use FWaaS service plugin with my own router solution (I'm
not using L3 agent at all). If I want to use FWaaS plugin also, should I
write own driver to it, or should I write own service plugin? I will be
grateful for any links to some description about this FWaaS and it's
architecture :) Thx a lot for any help


--
Best regards
Sławek Kapłoński
sla...@kaplonski.pl


__
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

Re: [openstack-dev] [Neutron] FWaaS - question about drivers

[Sławek Kapłoński]

Hello,

Thx for tips. I have one more question. You point me fo neutron-fwaas project 
which for me looks like different project then neutron. I saw fwaas service 
plugin directly in neutron in Juno. So which version should I use: this 
neutron-fwaas or service plugin from neutron? Or maybe it is the same or I 
misunderstand something?

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia piątek, 20 lutego 2015 14:44:21 Sumit Naiksatam pisze:
 Inline...
 
 On Wed, Feb 18, 2015 at 7:48 PM, Vikram Choudhary
 
 vikram.choudh...@huawei.com wrote:
  Hi,
  
  You can write your own driver. You can refer to below links for getting
  some idea about the architecture.
  
  https://wiki.openstack.org/wiki/Neutron/ServiceTypeFramework
 
 This is a legacy construct and should not be used.
 
  https://wiki.openstack.org/wiki/Neutron/LBaaS/Agent
 
 The above pointer is to a LBaaS Agent which is very different from a
 FWaaS driver (which was the original question in the email).
 
 FWaaS does use pluggable drivers and the default is configured here:
 https://github.com/openstack/neutron-fwaas/blob/master/etc/fwaas_driver.ini
 
 For example for FWaaS driver implementation you can check here:
 https://github.com/openstack/neutron-fwaas/tree/master/neutron_fwaas/service
 s/firewall/drivers
  Thanks
  Vikram
  
  -Original Message-
  From: Sławek Kapłoński [mailto: ]
  Sent: 19 February 2015 02:33
  To: openstack-dev@lists.openstack.org
  Subject: [openstack-dev] [Neutron] FWaaS - question about drivers
  
  Hello,
  
  I'm looking to use FWaaS service plugin with my own router solution (I'm
  not using L3 agent at all). If I want to use FWaaS plugin also, should I
  write own driver to it, or should I write own service plugin? I will be
  grateful for any links to some description about this FWaaS and it's
  architecture :) Thx a lot for any help
  
  
  --
  Best regards
  Sławek Kapłoński
  sla...@kaplonski.pl
  
  __
  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] FWaaS - question about drivers

[Sławek Kapłoński]

Hello,

Thx guys. Now it is clear for me :)
One more question. I saw that in this service plugin there is hardcoded quota 
1 firewall per tenant. Do you know why it is so limited? Is there any 
important reason for that?
And second thing. As there is only one firewall per tenant so all rules from 
it will be applied on all routers (L3 agents) from this tenant and for all 
tenant networks, am I right? If yes, how it is solved to set firewall rules 
when for example new router is created? L3 agent is asking about rules via rpc 
or FwaaS is sending such notification to L3 agent?
Sorry if my questions are silly but I didn't do anything with this service 
plugins yet :)

--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia piątek, 20 lutego 2015 16:27:33 Doug Wiegley pisze:
 Same project, shiny new repo.
 
 doug
 
  On Feb 20, 2015, at 4:05 PM, Sławek Kapłoński sla...@kaplonski.pl wrote:
  
  Hello,
  
  Thx for tips. I have one more question. You point me fo neutron-fwaas
  project which for me looks like different project then neutron. I saw
  fwaas service plugin directly in neutron in Juno. So which version
  should I use: this neutron-fwaas or service plugin from neutron? Or maybe
  it is the same or I misunderstand something?
  
  --
  Pozdrawiam / Best regards
  Sławek Kapłoński
  sla...@kaplonski.pl
  
  Dnia piątek, 20 lutego 2015 14:44:21 Sumit Naiksatam pisze:
  Inline...
  
  On Wed, Feb 18, 2015 at 7:48 PM, Vikram Choudhary
  
  vikram.choudh...@huawei.com wrote:
  Hi,
  
  You can write your own driver. You can refer to below links for getting
  some idea about the architecture.
  
  https://wiki.openstack.org/wiki/Neutron/ServiceTypeFramework
  
  This is a legacy construct and should not be used.
  
  https://wiki.openstack.org/wiki/Neutron/LBaaS/Agent
  
  The above pointer is to a LBaaS Agent which is very different from a
  FWaaS driver (which was the original question in the email).
  
  FWaaS does use pluggable drivers and the default is configured here:
  https://github.com/openstack/neutron-fwaas/blob/master/etc/fwaas_driver.i
  ni
  
  For example for FWaaS driver implementation you can check here:
  https://github.com/openstack/neutron-fwaas/tree/master/neutron_fwaas/serv
  ice s/firewall/drivers
  
  Thanks
  Vikram
  
  -Original Message-
  From: Sławek Kapłoński [mailto: ]
  Sent: 19 February 2015 02:33
  To: openstack-dev@lists.openstack.org
  Subject: [openstack-dev] [Neutron] FWaaS - question about drivers
  
  Hello,
  
  I'm looking to use FWaaS service plugin with my own router solution (I'm
  not using L3 agent at all). If I want to use FWaaS plugin also, should I
  write own driver to it, or should I write own service plugin? I will be
  grateful for any links to some description about this FWaaS and it's
  architecture :) Thx a lot for any help
  
  
  --
  Best regards
  Sławek Kapłoński
  sla...@kaplonski.pl
  
  
  __
  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] FWaaS - question about drivers

[Sławek Kapłoński]

Hello,

I'm looking to use FWaaS service plugin with my own router solution (I'm
not using L3 agent at all). If I want to use FWaaS plugin also, should I
write own driver to it, or should I write own service plugin?
I will be grateful for any links to some description about this FWaaS
and it's architecture :)
Thx a lot for any help


-- 
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

__
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] Writing own L3 service plugin

[Sławek Kapłoński]

Hello,

I want to use L3 functionalities with own device in place of normal 
L3agent. So I think that best way will be to write own L3 service plugin 
which will configure my router on my special device. But I don't know 
now few things. For example if I'm creating new port in router 
(router-interface-add) then new port in network is created but it is not 
bound anywhere. So how I should do it that it will be bound to my device 
and for example ovs_agents will be able to establish vxlan tunnels to 
this device?


--
Pozdrawiam
Sławek Kapłonski
sla...@kaplonski.pl

__
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] Let's fix all neutron bugs! (NOT)

[Sławek Kapłoński]

Hello,

I'm not very experienced in neutron coding for upstream but I have some 
knowledge about ml2 plugin and openvswitch agent (mostly). I also be very 
happy if I can start making something for neutron project and I think that 
some small bugs will be best on the beginning.
So I would like to help if it will be possible somehow :)
My launchpad profile is https://launchpad.net/~slawek-t

---
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia piątek, 7 listopada 2014 12:17:05 Eugene Nikanorov pisze:
 Hi folks,
 
 I have been supervising bug list for neutron during the last release cycle,
 trying
 to do some housekeeping, prioritizing issues and fixing some of them.
 
 As you might see, amount of bugs (even staying in New state) doesn't go
 down.
 Bugs appear at quite fast pace, and some of them hang for quite a long
 time, especially if someone has assigned the bug on himself and then
 abandoned working on it.
 One of the other reasons for that is that we lack volunteers willing to fix
 those bugs.
 
 So,
 
 If you're willing to help, have some knowledge of neutron and its codebase
 or you have a lab where you can reproduce (and hence, confirm) the bug and
 provide more additional debugging info, that would be great!
 My plan is to get your contact, knowing what part of neutron project you
 familiar with, and then assign bugs directly to you if I feel that the
 issue matches your experience.
 
 I just want to make bug triaging/fixing process a bit more iterative and
 efficient, with a help of community.
 So please reach directly to me and let me know what you are
 interested/experienced with.
 
 Thanks,
 Eugene.

signature.asc
Description: This is a digitally signed message part.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] How to write extension

[Sławek Kapłoński]

Hello,

Thanks for link to blueprint Mathieu but I'm using now still Havana version of 
openstack.
I need extension which allow me add to private network something like 
external router that ovs agent will know that should make vxlan or gre 
tunnel to that external device. Maybe there is some solution which allow me to 
do something like that? :)
@Damon: I read those articles before You send me it but something is wrong for 
me (or I don't understand it). I'm trying to do almost exactly what was 
described on 
http://control-that-vm.blogspot.com/2014/05/writing-api-extensions-in-neutron.html
 - I made my file with extension in 
neutron/extensions/my_ext.py and I add name of this extension to ml2 
supported_extension_aliases. When I now do neutron ext-list then I see my 
extension on list but when I send request with curl I have 404 error or error 
500 and in neutron-server logs there is info that ML2 plugin has no method 
xxx. 
So I don't know, should I add methods added by my plugin to ML2 plugin? Or 
should I add by plugin class to classes from which ml2 inherits?

---
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia środa 08 październik 2014 14:14:56 Mathieu Rohon pisze:
 Hi,
 
 please tell us about the extension you want to write, it would really help.
 In ML2, you now have the ability to easily add extensions thanks to this
 work :
 
 https://blueprints.launchpad.net/neutron/+spec/extensions-in-ml2
 
 Mathieu
 
 On Wed, Oct 8, 2014 at 7:52 AM, Damon Wang damon.dev...@gmail.com wrote:
  Hi Kapłoński,
  
  I recommend you to read these materials:
  
  Keynotes:
  https://www.openstack.org/assets/presentation-media/insideneutron2.pdf
  Video:
  https://www.openstack.org/summit/openstack-summit-hong-kong-2013/session-v
  ideos/presentation/deep-dive-into-neutron Post:
  http://control-that-vm.blogspot.com/2014/05/writing-api-extensions-in-neut
  ron.html
  
  Regards,
  Wang Wei
  
  2014-10-08 3:29 GMT+08:00 Sławek Kapłoński sla...@kaplonski.pl:
  Hello,
  
  Can You send me some examples or link to tutorial how to write extension
  to
  neutron. I'm using ML2 plugin in neutron and I want to add some new
  functionality and API methods to this neutron. So imho I should do it via
  extension but how exactly write it that it will work in existing ML2
  plugin?
  
  ---
  Best regards
  Sławek Kapłoński
  sla...@kaplonski.pl
  ___
  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
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

signature.asc
Description: This is a digitally signed message part.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron] How to write extension

[Sławek Kapłoński]

Hello,

Can You send me some examples or link to tutorial how to write extension to 
neutron. I'm using ML2 plugin in neutron and I want to add some new 
functionality and API methods to this neutron. So imho I should do it via 
extension but how exactly write it that it will work in existing ML2 plugin?

---
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

signature.asc
Description: This is a digitally signed message part.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] Glance on swift problem

[Sławek Kapłoński]

Hello,

I make some more debugging on that problem and I found what is happend:
Glance is sending first chunk (in my config it was 200MB) and after 
finishing sending it to swift it send some bad http request. Swift has 
got in logs something like:
proxy-server ERROR WSGI: code 400, message Bad request syntax 
('\x01\x00\x1c[n\x01\x00\x00\x96s\x01\x00\x00*t') (txn: 
txa21d64d49ac347bb87023-00542d4e59) (client_ip: X.X.X.X)

and uploading is finished with error in glance

Maybe someone of You know such bug?

Best regards
Slawek Kaplonski

W dniu 2014-09-30 16:20, Sławek Kapłoński napisał(a):

Hello,

I'm using openstack havana release and glance with swift backend.
Today I found that I have problem when I create image with url in
--copy-from when image is bigger than my
swift_store_large_object_size because then glance is trying to split
image to chunks with size given in
swift_store_large_object_chunk_size and when try to upload first
chunk to swift I have error:

2014-09-30 15:05:29.361 18023 ERROR glance.store.swift [-] Error
during chunked upload to backend, deleting stale chunks
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift Traceback (most
recent call last):
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/glance/store/swift.py, line 384, in
add
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
content_length=content_length)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1234,
in put_object
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
response_dict=response_dict)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1143,
in _retry
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
reset_func(func, *args, **kwargs)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1215,
in _default_reset
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift % 
(container, obj))

2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
ClientException: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
2014-09-30 15:05:29.362 18023 ERROR glance.store.swift [-] Failed to
add object to Swift.
Got error from Swift: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.
2014-09-30 15:05:29.362 18023 ERROR glance.api.v1.upload_utils [-]
Failed to upload image 9f56ccec-deeb-4020-95ba-ca7bf1170056
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
Traceback (most recent call last):
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   File
/usr/lib/python2.7/dist-packages/glance/api/v1/upload_utils.py, line
101, in upload_data_to_store
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
store)

2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   File
/usr/lib/python2.7/dist-packages/glance/store/__init__.py, line 333,
in store_add_to_backend
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
(location, size, checksum, metadata) = store.add(image_id, data, size)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   File
/usr/lib/python2.7/dist-packages/glance/store/swift.py, line 447, in
add
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
raise glance.store.BackendException(msg)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
BackendException: Failed to add object to Swift.
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils Got
error from Swift: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.


Does someone of You got same error and know what is solution of it? I
was searching about that in google but I not found anything what could
solve my problem.


--
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] Glance on swift problem

[Sławek Kapłoński]

Hello,

W dniu 2014-09-30 20:28, Timur Nurlygayanov napisał(a):

Hi Slawek,

we faced the same error and this is issue with Swift.
We can see 100% disk usage on the Swift node during the file upload
and looks like Swift can't send info about status of the file loading
in time.

On our environments we found the workaround for this issue:

1. Set  swift_store_large_object_size = 200 in glance.conf.


I have it set to 1024 - should it be lower? Value which I have is too 
big now?




2. Add to Swift proxy-server.conf:

[DEFAULT]
 ...
 node_timeout = 90

Probably we can set this value as default value for this parameter
instead of '30'?

Regards,

Timur

On Tue, Sep 30, 2014 at 7:41 PM, Sławek Kapłoński
sla...@kaplonski.pl wrote:


Hello,

I can't find that upload from was previous logs but I now try to
upload same image once again. In glance there was exactly same
error. In swift logs I have:

Sep 30 17:35:10 127.0.0.1 proxy-server X.X.X.X Y.Y.Y.Y
30/Sep/2014/15/35/10 HEAD
/v1/AUTH_7ef5a7661ccd4c069e3ad387a6dceebd/glance HTTP/1.0 204
Sep 30 17:35:16 127.0.0.1 proxy-server X.X.X.X Y.Y.Y.Y
30/Sep/2014/15/35/16 PUT


/v1/AUTH_7ef5a7661ccd4c069e3ad387a6dceebd/glance/fa5dfe09-74f5-4287-9852-d2f1991eebc0-1

HTTP/1.0 201 - -

Best regards
Slawek Kaplonski

W dniu 2014-09-30 17:03, Kuo Hugo napisał(a):

Hi ,

Could you please post the log of related requests in Swift's log
???

Thanks // Hugo

2014-09-30 22:20 GMT+08:00 Sławek Kapłoński
sla...@kaplonski.pl:

Hello,

I'm using openstack havana release and glance with swift backend.
Today I found that I have problem when I create image with url in
--copy-from when image is bigger than my
swift_store_large_object_size because then glance is trying to
split image to chunks with size given in
swift_store_large_object_chunk_size and when try to upload first
chunk to swift I have error:

2014-09-30 15:05:29.361 18023 ERROR glance.store.swift [-] Error
during chunked upload to backend, deleting stale chunks
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift Traceback
(most recent call last):
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/glance/store/swift.py, line 384,
in add
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   
 content_length=content_length)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line
1234,
in put_object
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   
 response_dict=response_dict)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line
1143,
in _retry
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   
 reset_func(func, *args, **kwargs)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line
1215,
in _default_reset
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift     %
(container, obj))
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
ClientException: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
2014-09-30 15:05:29.362 18023 ERROR glance.store.swift [-] Failed
to add object to Swift.
Got error from Swift: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.
2014-09-30 15:05:29.362 18023 ERROR glance.api.v1.upload_utils [-]
Failed to upload image 9f56ccec-deeb-4020-95ba-ca7bf1170056
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
Traceback (most recent call last):
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
 File
/usr/lib/python2.7/dist-packages/glance/api/v1/upload_utils.py,
line 101, in upload_data_to_store
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   
 store)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
 File /usr/lib/python2.7/dist-packages/glance/store/__init__.py,
line 333, in store_add_to_backend
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   
 (location, size, checksum, metadata) = store.add(image_id, data,
size)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
 File /usr/lib/python2.7/dist-packages/glance/store/swift.py,
line 447, in add
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   
 raise glance.store.BackendException(msg)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
BackendException: Failed to add object to Swift.
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils Got
error from Swift: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.

Does someone of You got same error and know what is solution of it?
I was searching about that in google but I not found anything what
could solve my problem.

--
Best regards

Re: [openstack-dev] [Openstack] Glance on swift problem

[Sławek Kapłoński]

Hello,

Thanks for Your help but it not helps. I checked that for sure on each swift 
node there is a lot of free space. What can confirm that is fact that when I 
try to create image with size about 1.7GB and I have 
swift_store_large_object_size set to 1GB than there is error (always after 
send first chunk to swift (200MB). When I only change 
swift_store_large_object_size to 2GB and restart glance-api than the same 
image is created correctly (it is then in one big object).

---
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

Dnia wtorek, 30 września 2014 22:28:11 Timur Nurlygayanov pisze:
 Hi Slawek,
 
 we faced the same error and this is issue with Swift.
 We can see 100% disk usage on the Swift node during the file upload and
 looks like Swift can't send info about status of the file loading in time.
 
 On our environments we found the workaround for this issue:
 1. Set  swift_store_large_object_size = 200 in glance.conf.
 2. Add to Swift proxy-server.conf:
 
 [DEFAULT]
 ...
 node_timeout = 90
 
 Probably we can set this value as default value for this parameter instead
 of '30'?
 
 
 Regards,
 Timur
 
 
 On Tue, Sep 30, 2014 at 7:41 PM, Sławek Kapłoński sla...@kaplonski.pl
 
 wrote:
  Hello,
  
  I can't find that upload from was previous logs but I now try to upload
  same image once again. In glance there was exactly same error. In swift
  logs I have:
  
  Sep 30 17:35:10 127.0.0.1 proxy-server X.X.X.X Y.Y.Y.Y
  30/Sep/2014/15/35/10 HEAD /v1/AUTH_7ef5a7661ccd4c069e3ad387a6dceebd/glance
  HTTP/1.0 204
  Sep 30 17:35:16 127.0.0.1 proxy-server X.X.X.X Y.Y.Y.Y
  30/Sep/2014/15/35/16 PUT /v1/AUTH_7ef5a7661ccd4c069e3ad387a6dcee
  bd/glance/fa5dfe09-74f5-4287-9852-d2f1991eebc0-1 HTTP/1.0 201 - -
  
  Best regards
  Slawek Kaplonski
  
  W dniu 2014-09-30 17:03, Kuo Hugo napisał(a):
  Hi ,
  
  Could you please post the log of related requests in Swift's log ???
  
  Thanks // Hugo
  
  2014-09-30 22:20 GMT+08:00 Sławek Kapłoński sla...@kaplonski.pl:
   Hello,
   
  I'm using openstack havana release and glance with swift backend.
  Today I found that I have problem when I create image with url in
  --copy-from when image is bigger than my
  swift_store_large_object_size because then glance is trying to
  split image to chunks with size given in
  swift_store_large_object_chunk_size and when try to upload first
  chunk to swift I have error:
  
  2014-09-30 15:05:29.361 18023 ERROR glance.store.swift [-] Error
  during chunked upload to backend, deleting stale chunks
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift Traceback
  (most recent call last):
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
  /usr/lib/python2.7/dist-packages/glance/store/swift.py, line 384,
  in add
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
  
   content_length=content_length)
  
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
  /usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1234,
  in put_object
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
  
   response_dict=response_dict)
  
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
  /usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1143,
  in _retry
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
  
   reset_func(func, *args, **kwargs)
  
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
  /usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1215,
  in _default_reset
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift %
  (container, obj))
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
  ClientException: put_object('glance',
  '9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
  ability to reset contents for reupload.
  2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
  2014-09-30 15:05:29.362 18023 ERROR glance.store.swift [-] Failed
  to add object to Swift.
  Got error from Swift: put_object('glance',
  '9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
  ability to reset contents for reupload.
  2014-09-30 15:05:29.362 18023 ERROR glance.api.v1.upload_utils [-]
  Failed to upload image 9f56ccec-deeb-4020-95ba-ca7bf1170056
  2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
  Traceback (most recent call last):
  2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
  
   File
  
  /usr/lib/python2.7/dist-packages/glance/api/v1/upload_utils.py,
  line 101, in upload_data_to_store
  2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
  
   store)
  
  2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
  
   File /usr/lib/python2.7/dist-packages/glance/store/__init__.py,
  
  line 333, in store_add_to_backend
  2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
  
   (location, size, checksum, metadata) = store.add(image_id, data,
  
  size)
  2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
  
   File /usr/lib

[openstack-dev] [Openstack] Glance on swift problem

[Sławek Kapłoński]

Hello,

I'm using openstack havana release and glance with swift backend. Today 
I found that I have problem when I create image with url in 
--copy-from when image is bigger than my 
swift_store_large_object_size because then glance is trying to split 
image to chunks with size given in swift_store_large_object_chunk_size 
and when try to upload first chunk to swift I have error:


2014-09-30 15:05:29.361 18023 ERROR glance.store.swift [-] Error during 
chunked upload to backend, deleting stale chunks
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift Traceback (most 
recent call last):
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File 
/usr/lib/python2.7/dist-packages/glance/store/swift.py, line 384, in 
add
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift 
content_length=content_length)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File 
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1234, in 
put_object
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift 
response_dict=response_dict)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File 
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1143, in 
_retry
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift 
reset_func(func, *args, **kwargs)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File 
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1215, in 
_default_reset
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift % (container, 
obj))
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift ClientException: 
put_object('glance', '9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) 
failure and no ability to reset contents for reupload.

2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
2014-09-30 15:05:29.362 18023 ERROR glance.store.swift [-] Failed to add 
object to Swift.
Got error from Swift: put_object('glance', 
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no 
ability to reset contents for reupload.
2014-09-30 15:05:29.362 18023 ERROR glance.api.v1.upload_utils [-] 
Failed to upload image 9f56ccec-deeb-4020-95ba-ca7bf1170056
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils Traceback 
(most recent call last):
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   File 
/usr/lib/python2.7/dist-packages/glance/api/v1/upload_utils.py, line 
101, in upload_data_to_store
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
store)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   File 
/usr/lib/python2.7/dist-packages/glance/store/__init__.py, line 333, 
in store_add_to_backend
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
(location, size, checksum, metadata) = store.add(image_id, data, size)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   File 
/usr/lib/python2.7/dist-packages/glance/store/swift.py, line 447, in 
add
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils raise 
glance.store.BackendException(msg)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
BackendException: Failed to add object to Swift.
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils Got error 
from Swift: put_object('glance', 
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no 
ability to reset contents for reupload.



Does someone of You got same error and know what is solution of it? I 
was searching about that in google but I not found anything what could 
solve my problem.


--
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openst...@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] Glance on swift problem

[Sławek Kapłoński]

Hello,

I can't find that upload from was previous logs but I now try to upload 
same image once again. In glance there was exactly same error. In swift 
logs I have:


Sep 30 17:35:10 127.0.0.1 proxy-server X.X.X.X Y.Y.Y.Y 
30/Sep/2014/15/35/10 HEAD 
/v1/AUTH_7ef5a7661ccd4c069e3ad387a6dceebd/glance HTTP/1.0 204
Sep 30 17:35:16 127.0.0.1 proxy-server X.X.X.X Y.Y.Y.Y 
30/Sep/2014/15/35/16 PUT 
/v1/AUTH_7ef5a7661ccd4c069e3ad387a6dceebd/glance/fa5dfe09-74f5-4287-9852-d2f1991eebc0-1 HTTP/1.0 201 - -


Best regards
Slawek Kaplonski

W dniu 2014-09-30 17:03, Kuo Hugo napisał(a):

Hi ,

Could you please post the log of related requests in Swift's log ???

Thanks // Hugo

2014-09-30 22:20 GMT+08:00 Sławek Kapłoński sla...@kaplonski.pl:


Hello,

I'm using openstack havana release and glance with swift backend.
Today I found that I have problem when I create image with url in
--copy-from when image is bigger than my
swift_store_large_object_size because then glance is trying to
split image to chunks with size given in
swift_store_large_object_chunk_size and when try to upload first
chunk to swift I have error:

2014-09-30 15:05:29.361 18023 ERROR glance.store.swift [-] Error
during chunked upload to backend, deleting stale chunks
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift Traceback
(most recent call last):
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/glance/store/swift.py, line 384,
in add
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   
 content_length=content_length)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1234,
in put_object
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   
 response_dict=response_dict)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1143,
in _retry
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   
 reset_func(func, *args, **kwargs)
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift   File
/usr/lib/python2.7/dist-packages/swiftclient/client.py, line 1215,
in _default_reset
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift     %
(container, obj))
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
ClientException: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.
2014-09-30 15:05:29.361 18023 TRACE glance.store.swift
2014-09-30 15:05:29.362 18023 ERROR glance.store.swift [-] Failed
to add object to Swift.
Got error from Swift: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.
2014-09-30 15:05:29.362 18023 ERROR glance.api.v1.upload_utils [-]
Failed to upload image 9f56ccec-deeb-4020-95ba-ca7bf1170056
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
Traceback (most recent call last):
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
 File
/usr/lib/python2.7/dist-packages/glance/api/v1/upload_utils.py,
line 101, in upload_data_to_store
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   
 store)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
 File /usr/lib/python2.7/dist-packages/glance/store/__init__.py,
line 333, in store_add_to_backend
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   
 (location, size, checksum, metadata) = store.add(image_id, data,
size)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils 
 File /usr/lib/python2.7/dist-packages/glance/store/swift.py,
line 447, in add
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils   
 raise glance.store.BackendException(msg)
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils
BackendException: Failed to add object to Swift.
2014-09-30 15:05:29.362 18023 TRACE glance.api.v1.upload_utils Got
error from Swift: put_object('glance',
'9f56ccec-deeb-4020-95ba-ca7bf1170056-1', ...) failure and no
ability to reset contents for reupload.

Does someone of You got same error and know what is solution of it?
I was searching about that in google but I not found anything what
could solve my problem.

--
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

___
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]
Post to     : openst...@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]




Links:
--
[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


--
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openst...@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
OpenStack-dev

[openstack-dev] [Neutron] Starting contributing to project

[Sławek Kapłoński]

Hello,

I want to start contributing to neutron project. I found bug which I
want to try fix: https://bugs.launchpad.net/neutron/+bug/1204956 and I
have question about workflow in such case. Should I clone neutron
reposiotory from branch master and do changes based on master branch or
maybe should I do my changes starting from any other branch? What
should I do next when I will for example do patch for such bug?
Thanks in advance for any help and explanation about that

-- 
Best regards
Slawek Kaplonski
sla...@kaplonski.pl


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] reservation of fixed ip

[Sławek Kapłoński]

Hello,

Thanks for link to this patch. It should solve my current need :)


-- 
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl


Dnia Fri, 23 May 2014 15:23:49 +0100
Salvatore Orlando sorla...@nicira.com napisał:

 Hi Jack,
 
 Do you mean this change by any chance?
 https://review.openstack.org/#/c/77043/
 
 Salvatore
 
 
 On 23 May 2014 15:10, McCann, Jack jack.mcc...@hp.com wrote:
 
   From the original ask:
 
 
 
   I know that there is possibility to create port with IP
   and later connect VM to this port. This solution is almost ok
   for me but problem is when user delete this instance - then
   port is also deleted and it is not reserved still for the same
   user and tenant.
 
 
 
  This sounds like the problem of nova deleting a port that it did not
 
  create.  We could look at a change (likely involving nova and
  neutron)
 
  such that if I create a port and pass it in to nova boot, nova would
 
  not delete that port when the VM is deleted.
 
 
 
  - Jack
 
 
 
  *From:* Mohammad Banikazemi [mailto:m...@us.ibm.com]
  *Sent:* Thursday, May 22, 2014 10:41 PM
 
  *To:* OpenStack Development Mailing List (not for usage questions)
  *Cc:* OpenStack Development Mailing List (not for usage questions)
 
  *Subject:* Re: [openstack-dev] [Neutron] reservation of fixed ip
 
 
 
  Well, for a use case we had in mind we were trying to figure out
  how to simply get an IP address on a subnet. We essentially want to
  use such an address internally by the controller and make sure it
  is not used for a port that gets created on a network with that
  subnet. In this use case, an interface to IPAM for removing an
  address from the pool of available addresses (and the interface to
  possibly return the address to the pool) would be sufficient.
 
  Mohammad
 
  [image: Inactive hide details for Carl Baldwin ---05/22/2014
  06:19:16 PM---If an IP is reserved for a tenant, should the tenant
  need to]Carl Baldwin ---05/22/2014 06:19:16 PM---If an IP is
  reserved for a tenant, should the tenant need to explicitly ask for
  that specific IP to
 
  From: Carl Baldwin c...@ecbaldwin.net
  To: OpenStack Development Mailing List (not for usage questions) 
  openstack-dev@lists.openstack.org,
  Date: 05/22/2014 06:19 PM
  Subject: Re: [openstack-dev] [Neutron] reservation of fixed ip
   --
 
 
 
 
  If an IP is reserved for a tenant, should the tenant need to
  explicitly ask for that specific IP to be allocated when creating a
  floating ip or port?  And it would pull from the regular pool if a
  specific IP is not requested.  Or, does the allocator just pull from
  the tenant's reserved pool whenever it needs an IP on a subnet?  If
  the latter, then I think Salvatore's concern still a valid one.
 
  I think if a tenant wants an IP address reserved then he probably
  has a specific purpose for that IP address in mind.  That leads me
  to think that he should be required to pass the specific address
  when creating the associated object in order to make use of it.  We
  can't do that yet with all types of allocations but there are
  reviews in progress [1][2].
 
  Carl
 
  [1] https://review.openstack.org/#/c/70286/
  [2] https://review.openstack.org/#/c/83664/
 
  On Thu, May 22, 2014 at 12:04 PM, Sławek Kapłoński
  sla...@kaplonski.pl wrote:
   Hello
  
  
   Dnia Wed, 21 May 2014 23:51:48 +0100
   Salvatore Orlando sorla...@nicira.com napisał:
  
   In principle there is nothing that should prevent us from
   implementing an IP reservation mechanism.
  
   As with anything, the first thing to check is literature or
   related work! If any other IaaS system is implementing such a
   mechanism, is it exposed through the API somehow?
   Also this feature is likely to be provided by IPAM systems. If
   yes, what constructs do they use?
   I do not have the answers to this questions, but I'll try to
   document myself; if you have them - please post them here.
  
   This new feature would probably be baked into neutron's IPAM
   logic. When allocating an IP, first check from within the IP
   reservation pool, and then if it's not found check from standard
   allocation pools (this has non negligible impact on availability
   ranges management, but these are implementation details).
   Aspects to consider, requirement-wise, are:
   1) Should reservations also be classified by qualification of
   the port? For instance, is it important to specify that an IP
   should be used for the gateway port rather than for a floating
   IP port?
  
   IMHO it is not required when IP is reserved. User should have
   possibility to reserve such IP for his tenant and later use it as
   he want (floating ip, instance or whatever)
  
   2) Are reservations something that an admin could specify on a
   tenant-basis (hence an admin API extension), or an implicit
   mechanism that can be tuned using configuration variables (for
   instance create an IP reservation a for gateway port for a given
   tenant when

Re: [openstack-dev] [Neutron] reservation of fixed ip

[Sławek Kapłoński]

Hello


Dnia Wed, 21 May 2014 23:51:48 +0100
Salvatore Orlando sorla...@nicira.com napisał:

 In principle there is nothing that should prevent us from
 implementing an IP reservation mechanism.
 
 As with anything, the first thing to check is literature or related
 work! If any other IaaS system is implementing such a mechanism, is
 it exposed through the API somehow?
 Also this feature is likely to be provided by IPAM systems. If yes,
 what constructs do they use?
 I do not have the answers to this questions, but I'll try to document
 myself; if you have them - please post them here.
 
 This new feature would probably be baked into neutron's IPAM logic.
 When allocating an IP, first check from within the IP reservation
 pool, and then if it's not found check from standard allocation pools
 (this has non negligible impact on availability ranges management, but
 these are implementation details).
 Aspects to consider, requirement-wise, are:
 1) Should reservations also be classified by qualification of the
 port? For instance, is it important to specify that an IP should be
 used for the gateway port rather than for a floating IP port?

IMHO it is not required when IP is reserved. User should have
possibility to reserve such IP for his tenant and later use it as he
want (floating ip, instance or whatever)

 2) Are reservations something that an admin could specify on a
 tenant-basis (hence an admin API extension), or an implicit mechanism
 that can be tuned using configuration variables (for instance create
 an IP reservation a for gateway port for a given tenant when a router
 gateway is set).
 
 I apologise if these questions are dumb. I'm just trying to frame this
 discussion into something which could then possibly lead to
 submitting a specification.
 
 Salvatore
 
 
 On 21 May 2014 21:37, Collins, Sean sean_colli...@cable.comcast.com
 wrote:
 
  (Edited the subject since a lot of people filter based on the
  subject line)
 
  I would also be interested in reserved IPs - since we do not deploy
  the layer 3 agent and use the provider networking extension and a
  hardware router.
 
  On Wed, May 21, 2014 at 03:46:53PM EDT, Sławek Kapłoński wrote:
   Hello,
  
   Ok, I found that now there is probably no such feature to reserve
   fixed ip for tenant. So I was thinking about add such feature to
   neutron. I mean that it should have new table with reserved ips
   in neutron database and neutron will check this table every time
   when new port will be created (or updated) and IP should be
   associated with this port. If user has got reserved IP it should
   be then used for new port, if IP is reserver by other tenant - it
   shouldn't be used. What You are thinking about such possibility?
   Is it possible to add it in some future release of neutron?
  
   --
   Best regards
   Sławek Kapłoński
   sla...@kaplonski.pl
  
  
   Dnia Mon, 19 May 2014 20:07:43 +0200
   Sławek Kapłoński sla...@kaplonski.pl napisał:
  
Hello,
   
I'm using openstack with neutron and ML2 plugin. Is there any
way to reserve fixed IP from shared external network for one
tenant? I know that there is possibility to create port with IP
and later connect VM to this port. This solution is almost ok
for me but problem is when user delete this instance - then
port is also deleted and it is not reserved still for the same
user and tenant. So maybe there is any solution to reserve it
permanent? I know also about floating IPs but I don't use L3
agents so this is probably not for me :)
   
  
   ___
   OpenStack-dev mailing list
   OpenStack-dev@lists.openstack.org
   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
  --
  Sean M. Collins
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 

-- 
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] reservation of fixed ip

[Sławek Kapłoński]

Hello,

Thanks for answears and info about this project - I will take a look on
that for sure :)
For me now reservation of fixed ips is enough and I don't know what
else can be reserved in neutron. Floating IP you can now assign to
tenant and this is some kind of reservation. Maybe someone else will
have other ideas about resources for reservation from neutron.

-- 
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl


Dnia Thu, 22 May 2014 10:15:11 -0700
Nikolay Starodubtsev nstarodubt...@mirantis.com napisał:

 Hi,
 I'm agree with Pablo. We've looked at Neutron resource reservations
 some time ago.
 But we can't decide which resources should be reserved and this
 question has been delayed.
 
 
 
 Nikolay Starodubtsev
 
 Software Engineer
 
 Mirantis Inc.
 
 
 Skype: dark_harlequine1
 
 
 2014-05-22 10:00 GMT-07:00 Fuente, Pablo A pablo.a.fue...@intel.com:
 
  Hi,
  I'm part of a project that aims to manage Reservations on
  OpenStack.
  Maybe this could be implemented on it. The name of the project is
  Blazar (ex Climate). Currently we have two reservation plugins: one
  for physical host reservations and other for virtual instances
  reservation. We are planning to implement some new plugins: volume
  reservation and neutron resource reservation. For the later we are
  still analyzing which resources reserve, but from this email seems
  that fixed IP should be one of them. Of course we already have
  implemented all the things needed to handle reservations in our
  core code: reservation life cycle, leases states (under review),
  notifications (using oslo), pluging mechanism for new resource
  reservations, DB schema with alembic migrations, REST API (with
  Pecan), etc. And yes, should be easy to try Blazar using our
  Devstack integration. If you need more information about the
  project please visit our wiki
  [1] or send me an email.
 
  Pablo.
 
  [1] https://wiki.openstack.org/wiki/Climate
 
  On Wed, 2014-05-21 at 23:51 +0100, Salvatore Orlando wrote:
   In principle there is nothing that should prevent us from
   implementing an IP reservation mechanism.
  
  
   As with anything, the first thing to check is literature or
   related work! If any other IaaS system is implementing such a
   mechanism, is it exposed through the API somehow?
   Also this feature is likely to be provided by IPAM systems. If
   yes, what constructs do they use?
   I do not have the answers to this questions, but I'll try to
   document myself; if you have them - please post them here.
  
  
   This new feature would probably be baked into neutron's IPAM
   logic. When allocating an IP, first check from within the IP
   reservation pool, and then if it's not found check from standard
   allocation pools (this has non negligible impact on availability
   ranges management, but these are implementation details).
   Aspects to consider, requirement-wise, are:
   1) Should reservations also be classified by qualification of
   the port? For instance, is it important to specify that an IP
   should be used for the gateway port rather than for a floating IP
   port? 2) Are reservations something that an admin could specify
   on a tenant-basis (hence an admin API extension), or an implicit
   mechanism that can be tuned using configuration variables (for
   instance create an IP reservation a for gateway port for a given
   tenant when a router gateway is set).
  
  
   I apologise if these questions are dumb. I'm just trying to frame
   this discussion into something which could then possibly lead to
   submitting a specification.
  
  
   Salvatore
  
  
   On 21 May 2014 21:37, Collins, Sean
   sean_colli...@cable.comcast.com wrote:
   (Edited the subject since a lot of people filter based on
   the subject
   line)
  
   I would also be interested in reserved IPs - since we do
   not deploy the
   layer 3 agent and use the provider networking extension
   and a hardware
   router.
  
   On Wed, May 21, 2014 at 03:46:53PM EDT, Sławek Kapłoński
   wrote:
Hello,
   
Ok, I found that now there is probably no such feature
to
   reserve fixed
ip for tenant. So I was thinking about add such feature
to
   neutron. I
mean that it should have new table with reserved ips in
   neutron
database and neutron will check this table every time
when
   new port
will be created (or updated) and IP should be associated
   with this
port. If user has got reserved IP it should be then
used for
   new port,
if IP is reserver by other tenant - it shouldn't be
used. What You are thinking about such possibility? Is
it possible
   to add it
in some future release of neutron?
   
--
Best regards
Sławek

Re: [openstack-dev] [Openstack] Neutron - reservation of fixed ip

[Sławek Kapłoński]

Hello,

Ok, I found that now there is probably no such feature to reserve fixed
ip for tenant. So I was thinking about add such feature to neutron. I
mean that it should have new table with reserved ips in neutron
database and neutron will check this table every time when new port
will be created (or updated) and IP should be associated with this
port. If user has got reserved IP it should be then used for new port,
if IP is reserver by other tenant - it shouldn't be used. 
What You are thinking about such possibility? Is it possible to add it
in some future release of neutron?

-- 
Best regards
Sławek Kapłoński
sla...@kaplonski.pl


Dnia Mon, 19 May 2014 20:07:43 +0200
Sławek Kapłoński sla...@kaplonski.pl napisał:

 Hello,
 
 I'm using openstack with neutron and ML2 plugin. Is there any way to
 reserve fixed IP from shared external network for one tenant? I know
 that there is possibility to create port with IP and later connect VM
 to this port. This solution is almost ok for me but problem is when
 user delete this instance - then port is also deleted and it is not
 reserved still for the same user and tenant. So maybe there is any
 solution to reserve it permanent?
 I know also about floating IPs but I don't use L3 agents so this is
 probably not for me :)
 

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ML2] L2 population mechanism driver

[Sławek Kapłoński]

Hello,

Thanks for explanation. Now it is clear for me :) I made my own driver because 
I made config on hosts in special way but I can't describe details :/

Best regards
Slawek Kaplonski
sla...@kaplonski.pl

Dnia wtorek, 6 maja 2014 10:35:05 Mathieu Rohon pisze:
 Hi slawek,
 
 As soon as you declare l2population in the  MD section of the config
 file, it will be loaded by ML2 plugin. l2population MD will listen to
 ML2 DB events and send RPC messages to ovs agent when needed.
 l2population MD will not bind the port, ovs MD will.
 By the way, you need to ad add the flag l2population in config file of
 the agent.
 
 just to be curious, what your MD which inherit from l2_pop MD is made for?
 
 regards
 
 Mathieu
 
 On Mon, May 5, 2014 at 11:06 PM, Sławek Kapłoński sla...@kaplonski.pl 
wrote:
  Hello,
  
  Thanks for answear. Now I made my own mech_driver which inherits from
  l2_pop driver and it is working ok. But If I will set it as:
  mechanism_drivers=openvswitch,l2population than ports will be binded
  with
  ovs driver so population mechanism will be working in such network?
  
  Best regards
  Slawek Kaplonski
  sla...@kaplonski.pl
  
  Dnia poniedziałek, 5 maja 2014 00:29:56 Narasimhan, Vivekanandan pisze:
  Hi Slawek,
  
  I think L2 pop driver needs to be used in conjunction with other
  mechanism
  drivers.
  
  It only deals with pro-actively informing agents on which MAC Addresses
  became available/unavailable on cloud nodes and is not meant for
  binding/unbinding ports on segments.
  
  If you configure mechanism_drivers=openvswitch,l2population in your
  ml2_conf.ini and restart your neutron-server, you'll notice that
  bind_port
  is handled by OVS mechanism driver (via AgentMechanismDriverBase inside
  ml2/drivers/mech_agent.py).
  
  --
  Thanks,
  
  Vivek
  
  
  -Original Message-
  From: Sławek Kapłoński [mailto:sla...@kaplonski.pl]
  Sent: Sunday, May 04, 2014 12:32 PM
  To: openstack-dev@lists.openstack.org
  Subject: [openstack-dev] [ML2] L2 population mechanism driver
  
  Hello,
  
  Last time I want to try using L2pop mechanism driver in ML2 (and
  openvswitch agents on compute nodes). But every time when I try to spawn
  instance I have got error binding failed. After some searching in code
  I found that l2pop driver have not implemented method bind_port and as
  it inherit directly from MechanismDriver this method is in fact not
  implemented. Is is ok and this mechanism driver should be used in other
  way or maybe there is some bug in this driver and it miss this method?
  
  Best regards
  Slawek Kaplonski
  sla...@kaplonski.pl
  
  ___
  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
  
  ___
  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


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ML2] L2 population mechanism driver

[Sławek Kapłoński]

Hello,

Thanks for answear. Now I made my own mech_driver which inherits from l2_pop 
driver and it is working ok. But If I will set it as: 
mechanism_drivers=openvswitch,l2population than ports will be binded with 
ovs driver so population mechanism will be working in such network?

Best regards
Slawek Kaplonski
sla...@kaplonski.pl

Dnia poniedziałek, 5 maja 2014 00:29:56 Narasimhan, Vivekanandan pisze:
 Hi Slawek,
 
 I think L2 pop driver needs to be used in conjunction with other mechanism
 drivers.
 
 It only deals with pro-actively informing agents on which MAC Addresses
 became available/unavailable on cloud nodes and is not meant for
 binding/unbinding ports on segments.
 
 If you configure mechanism_drivers=openvswitch,l2population in your
 ml2_conf.ini and restart your neutron-server, you'll notice that bind_port
 is handled by OVS mechanism driver (via AgentMechanismDriverBase inside
 ml2/drivers/mech_agent.py).
 
 --
 Thanks,
 
 Vivek
 
 
 -Original Message-
 From: Sławek Kapłoński [mailto:sla...@kaplonski.pl]
 Sent: Sunday, May 04, 2014 12:32 PM
 To: openstack-dev@lists.openstack.org
 Subject: [openstack-dev] [ML2] L2 population mechanism driver
 
 Hello,
 
 Last time I want to try using L2pop mechanism driver in ML2 (and openvswitch
 agents on compute nodes). But every time when I try to spawn instance I
 have got error binding failed. After some searching in code I found that
 l2pop driver have not implemented method bind_port and as it inherit
 directly from MechanismDriver this method is in fact not implemented.
 Is is ok and this mechanism driver should be used in other way or maybe
 there is some bug in this driver and it miss this method?
 
 Best regards
 Slawek Kaplonski
 sla...@kaplonski.pl
 
 ___
 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


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ML2] L2 population mechanism driver

[Sławek Kapłoński]

Hello,

Last time I want to try using L2pop mechanism driver in ML2 (and openvswitch 
agents on compute nodes). But every time when I try to spawn instance I have 
got error binding failed. After some searching in code I found that l2pop 
driver have not implemented method bind_port and as it inherit directly from 
MechanismDriver this method is in fact not implemented. 
Is is ok and this mechanism driver should be used in other way or maybe there 
is some bug in this driver and it miss this method?

Best regards
Slawek Kaplonski
sla...@kaplonski.pl

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] [NOVA] Missing network info in nova list

[Sławek Kapłoński]

Hello,

In nova logs there was not any error or TRACE. Everything looks ok
there but I probably found reason and solution of that problem. It was
probably related to bug: https://bugs.launchpad.net/nova/+bug/1254320
When I apply this patch on my compute nodes I have no any new instance
with missing network information in nova list or nova show.

-- 
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl


Dnia Wed, 2 Apr 2014 19:14:30 -0700
Aaron Rosen aaronoro...@gmail.com napisał:

 Hi Slawek,
 
 Interesting, I haven't seen this issue of network info not showing up
 on nova list and the instance being in ACTIVE state. Could you check
 out the nova logs and see if there are any TRACE's there?  If you're
 using icehouse you should be able to do neutron port-update port_id
 that maps to the instance's port and doing that will send a
 notification to nova  to update it's cache for the instance.
 
 Best,
 
 Aaron
 
 
 On Tue, Apr 1, 2014 at 12:10 AM, Sławek Kapłoński
 sla...@kaplonski.plwrote:
 
  Hello,
 
  Maybe the problem is not that missing data in nova's database
  becasue when I
  made:
  nova --debug list
  then I see that it is asking neutron about ports and this missing
  IP is corretly send from neutron.
  Also when I made:
  nova interface-list instance_id
  then there is no problem and IP is displayed. But still this IP is
  missing in
  list of instances and I displaying instance details (also in
  horizon).
 
  --
  Best regards
  Sławek Kapłoński
 
  Dnia poniedziałek, 31 marca 2014 18:17:18 Sławek Kapłoński pisze:
   Hello,
  
   I have openstack installation with neutron. When I made test and
   create many instances in one query (using --num-instances) all
   was ok but one instance (from 80 created) has no IP address when
   I made nova list or nova show . I found that there is missing
   value in network info in nova database in Instance-info-cache
   table. Everything except that is working fine: port with this IP
   is assigned to instance in neutron, binding is ok, instance has
   got configured this IP and I can ping it. Maybe someone know why
   this informations are missing in nova database and how to refresh
   it?
 
  ___
  Mailing list:
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
  Post to : openst...@lists.openstack.org
  Unsubscribe :
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
  ___
  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

[openstack-dev] [Openstack] [NOVA] Missing network info in nova list

[Sławek Kapłoński]

Hello,

I have openstack installation with neutron. When I made test and create 
many instances in one query (using --num-instances) all was ok but one 
instance (from 80 created) has no IP address when I made nova list or 
nova show . I found that there is missing value in network info in 
nova database in Instance-info-cache table. Everything except that is 
working fine: port with this IP is assigned to instance in neutron, 
binding is ok, instance has got configured this IP and I can ping it.
Maybe someone know why this informations are missing in nova database 
and how to refresh it?


--
Best regards
Sławek Kapłoński
sla...@kaplonski.pl

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openst...@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] [NOVA] Missing network info in nova list

[Sławek Kapłoński]

Hello,

Maybe the problem is not that missing data in nova's database becasue when I 
made: 
nova --debug list
then I see that it is asking neutron about ports and this missing IP is 
corretly send from neutron. 
Also when I made:
nova interface-list instance_id
then there is no problem and IP is displayed. But still this IP is missing in 
list of instances and I displaying instance details (also in horizon). 

--
Best regards
Sławek Kapłoński

Dnia poniedziałek, 31 marca 2014 18:17:18 Sławek Kapłoński pisze:
 Hello,
 
 I have openstack installation with neutron. When I made test and create
 many instances in one query (using --num-instances) all was ok but one
 instance (from 80 created) has no IP address when I made nova list or
 nova show . I found that there is missing value in network info in
 nova database in Instance-info-cache table. Everything except that is
 working fine: port with this IP is assigned to instance in neutron,
 binding is ok, instance has got configured this IP and I can ping it.
 Maybe someone know why this informations are missing in nova database
 and how to refresh it?

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openst...@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack][Multi-Node][ML2][MechanismDriver] How to load mechanism driver on compute nodes

[Sławek Kapłoński]

Hello,

Maybe I'm not an expert but You probably should use agent (like openvswitch 
agent) and send such messages from neutron server to compute nodes via RPC.
This is how I do such things (I'm using openvswitch agent which is modified by 
me a little bit)

--
Pozdrawiam
Sławek Kapłoński

Dnia środa, 12 marca 2014 14:27:01 Nader Lahouti pisze:
 Hi All,
 
 I installed multi nodes openstack (using devstack)  with ML2 as core
 plugin. I need to perform a task when update_port_pre/post_commit methods
 is called during installation of VM.
 As I enabled q-svc and q-agt on control and only q-agt on the compute node,
 compute node won't run neutron-server so no mechanism driver is loaded.
 I see the port event on compute node with this failure shown below.
 
 Is there anyway to load mechanism driver for compute nodes?
 
 2014-03-12 10:35:05.418 TRACE
 neutron.plugins.openvswitch.agent.ovs_neutron_agent   File
 /opt/stack/neutron/neutron/openstack/common/rpc/amqp.py, line 516, in
 __iter__
 
 2014-03-12 10:35:05.418 TRACE
 neutron.plugins.openvswitch.agent.ovs_neutron_agent raise result
 
 2014-03-12 10:35:05.418 TRACE
 neutron.plugins.openvswitch.agent.ovs_neutron_agent RemoteError: Remote
 error: MechanismDriverError update_port_postcommit failed.
 
 2014-03-12 10:35:05.418 TRACE
 neutron.plugins.openvswitch.agent.ovs_neutron_agent [u'Traceback (most
 recent call last):\n', u'  File
 /opt/stack/neutron/neutron/openstack/common/rpc/amqp.py, line 438, in
 _process_data\n**args)\n', u'  File
 /opt/stack/neutron/neutron/common/rpc.py, line 44, in dispatch\n
 neutron_ctxt, version, method, namespace, **kwargs)\n', u'  File
 /opt/stack/neutron/neutron/openstack/common/rpc/dispatcher.py, line 172,
 in dispatch\nresult = getattr(proxyobj, method)(ctxt, **kwargs)\n', u'
 File /opt/stack/neutron/neutron/plugins/ml2/rpc.py, line 192, in
 update_device_up\nq_const.PORT_STATUS_ACTIVE)\n', u'  File
 /opt/stack/neutron/neutron/plugins/ml2/plugin.py, line 681, in
 update_port_status\n
 self.mechanism_manager.update_port_postcommit(mech_context)\n', u'  File
 /opt/stack/neutron/neutron/plugins/ml2/managers.py, line 395, in
 update_port_postcommit\nself._call_on_drivers(update_port_postcommit,
 context)\n', u'  File /opt/stack/neutron/neutron/plugins/ml2/managers.py,
 line 167, in _call_on_drivers\nmethod=method_name\n',
 u'MechanismDriverError: update_port_postcommit failed.\n'].
 
 
 Regards,
 
 Nader

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Neutron ML2 and openvswitch agent

[Sławek Kapłoński]

Hello,

I have question to You guys. Can someone explain me (or send to link 
with such explanation) how exactly ML2 plugin which is working on 
neutron server is communicating with compute hosts with openvswitch 
agents? I suppose that this is working with rabbitmq queues but I need 
to add own function which will be called in this agent and I don't know 
how to do that. It would be perfect if such think will be possible with 
writing for example new mechanical driver in ML2 plugin (but how?). 
Thanks in advance for any help from You :)


--
Best regards
Slawek Kaplonski
sla...@kaplonski.pl

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Neutron ML2 and openvswitch agent

[Sławek Kapłoński]

Hello,

Trinath, this presentation I saw before You send me it. There is nice 
explanation what methods are (and should be) in type driver and mech driver 
but I need exactly that information what sent me Assaf. Thanks both of You for 
Your help :)

--
Best regards
Sławek Kapłoński
Dnia wtorek, 25 lutego 2014 12:18:50 Assaf Muller pisze:

 - Original Message -
 
  Hi
  
  Hope this helps
  
  http://fr.slideshare.net/mestery/modular-layer-2-in-openstack-neutron
  
  ___
  
  Trinath Somanchi
  
  _
  From: Sławek Kapłoński [sla...@kaplonski.pl]
  Sent: Tuesday, February 25, 2014 9:24 PM
  To: openstack-dev@lists.openstack.org
  Subject: [openstack-dev] Neutron ML2 and openvswitch agent
  
  Hello,
  
  I have question to You guys. Can someone explain me (or send to link
  with such explanation) how exactly ML2 plugin which is working on
  neutron server is communicating with compute hosts with openvswitch
  agents?
 
 Maybe this will set you on your way:
 ml2/plugin.py:Ml2Plugin.update_port uses _notify_port_updated, which then
 uses ml2/rpc.py:AgentNotifierApi.port_update, which makes an RPC call with
 the topic stated in that file.
 
 When the message is received by the OVS agent, it calls:
 neutron/plugins/openvswitch/agent/ovs_neutron_agent.py:OVSNeutronAgent.port_
 update.
  I suppose that this is working with rabbitmq queues but I need
  to add own function which will be called in this agent and I don't know
  how to do that. It would be perfect if such think will be possible with
  writing for example new mechanical driver in ML2 plugin (but how?).
  Thanks in advance for any help from You :)
  
  --
  Best regards
  Slawek Kaplonski
  sla...@kaplonski.pl
  
  ___
  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
 
 ___
 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

Re: [openstack-dev] [Openstack-dev] [neutron] [ml2] Neutron and ML2 - adding new network type

[Sławek Kapłoński]

Hello,

I added my own type_driver and it looks that works ok because I can make 
network with this my type. But how to add own mechanism_driver (to any 
of network type) - I think that this could be possible too. Can someone 
send me some info about that, or maybe link to some documentation about 
that?


Thanks in advance
Slawek

W dniu 2014-02-18 22:53, Sławek Kapłoński napisał(a):

Hello,

Thanks for an answear.
I want to add own network type which will be very similiar to flat 
network (in
type_driver I think it will be the same) but will assign IPs to 
instances in
different way (not exactly with some L2 protocol). I want to add own 
network
because I want to have own name of this network that I can distinguish 
it.

Maybe there is other reason to do that.

--
Best regards
Sławek Kapłoński

Dnia wtorek, 18 lutego 2014 10:08:50 piszesz:

[Moving to -dev list]

On Feb 18, 2014, at 9:12 AM, Sławek Kapłoński sla...@kaplonski.pl 
wrote:

 Hello,

 I'm trying to make something with neutron and ML2 plugin. Now I need to
 add my own external network type (as there are Flat, VLAN, GRE and
 so on). I searched for manuals for that but I can't found anything. Can
 someone of You explain me how I should do that? Is it enough to add own
 type_driver and mechanism_driver to ML2? Or I should do something else
 also?
Hi Sławek:

Can you explain more about what you’re looking to achieve here? I’m 
just
curious how the existing TypeDrivers won’t cover your use case. ML2 
was

designed to remove segmentation management from the MechanismDrivers
so they could all share segment types. Perhaps understanding what 
you’re
trying to achieve would help better understand the approach to take 
here.


Thanks,
Kyle

 Thanks in advance
 --
 Sławek Kapłoński
 sla...@kaplonski.pl

 ___
 Mailing list:
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 Post to : openst...@lists.openstack.org
 Unsubscribe :
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev] [neutron] [ml2] Neutron and ML2 - adding new network type

[Sławek Kapłoński]

Hello,

In fact I want to make something similiar to flat network but when IP is 
assigned to instance (port bind, yes?) then it should be not with arping 
announsed in network but with bgp (bgp server is installed on host). I 
know that it is not L2 protocol but I want to try that. So I want to 
write and use own Mechanism driver (or maybe I'm wrong and there is 
something other to make such things). So do You know how to add own 
mechanism driver and use it in neutron?


Thanks in advance
Slawek

W dniu 2014-02-19 11:26, Akihiro Motoki napisał(a):

Hi,

I think you are trying to use different IP allocation algorithm
for a network based on some attribute of the network.
network_type of the provider network specifies how layer2 network
is segmented and ML2 type drivers are defined per network_type.
I think it is different from your need.

IMO it looks better to introduce a new attribute to select
IP allocation algorithm to network resource.
The idea of Pluggable IP allocation algorithms exists for
a long time in Neutron community but the progress is not good.
Once pluggable mechanism is implemented, we need a way to
map networks to IP allocation algorithms and this kind of
new attribute is one possible choice.

Thanks,
Akihiro

(2014/02/19 6:53), Sławek Kapłoński wrote:

Hello,

Thanks for an answear.
I want to add own network type which will be very similiar to flat 
network (in
type_driver I think it will be the same) but will assign IPs to 
instances in
different way (not exactly with some L2 protocol). I want to add own 
network
because I want to have own name of this network that I can distinguish 
it.

Maybe there is other reason to do that.

--
Best regards
Sławek Kapłoński

Dnia wtorek, 18 lutego 2014 10:08:50 piszesz:

[Moving to -dev list]

On Feb 18, 2014, at 9:12 AM, Sławek Kapłoński sla...@kaplonski.pl 
wrote:

Hello,

I'm trying to make something with neutron and ML2 plugin. Now I need 
to
add my own external network type (as there are Flat, VLAN, GRE 
and
so on). I searched for manuals for that but I can't found anything. 
Can
someone of You explain me how I should do that? Is it enough to add 
own
type_driver and mechanism_driver to ML2? Or I should do something 
else

also?

Hi Sławek:

Can you explain more about what you’re looking to achieve here? I’m 
just
curious how the existing TypeDrivers won’t cover your use case. ML2 
was

designed to remove segmentation management from the MechanismDrivers
so they could all share segment types. Perhaps understanding what 
you’re
trying to achieve would help better understand the approach to take 
here.


Thanks,
Kyle


Thanks in advance
--
Sławek Kapłoński
sla...@kaplonski.pl

___
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openst...@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
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


--
Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev] [neutron] [ml2] Neutron and ML2 - adding new network type

[Sławek Kapłoński]

Hello,

Thanks for an answear.
I want to add own network type which will be very similiar to flat network (in 
type_driver I think it will be the same) but will assign IPs to instances in 
different way (not exactly with some L2 protocol). I want to add own network 
because I want to have own name of this network that I can distinguish it.
Maybe there is other reason to do that.

--
Best regards
Sławek Kapłoński

Dnia wtorek, 18 lutego 2014 10:08:50 piszesz:
 [Moving to -dev list]
 
 On Feb 18, 2014, at 9:12 AM, Sławek Kapłoński sla...@kaplonski.pl wrote:
  Hello,
  
  I'm trying to make something with neutron and ML2 plugin. Now I need to
  add my own external network type (as there are Flat, VLAN, GRE and
  so on). I searched for manuals for that but I can't found anything. Can
  someone of You explain me how I should do that? Is it enough to add own
  type_driver and mechanism_driver to ML2? Or I should do something else
  also?
 Hi Sławek:
 
 Can you explain more about what you’re looking to achieve here? I’m just
 curious how the existing TypeDrivers won’t cover your use case. ML2 was
 designed to remove segmentation management from the MechanismDrivers
 so they could all share segment types. Perhaps understanding what you’re
 trying to achieve would help better understand the approach to take here.
 
 Thanks,
 Kyle
 
  Thanks in advance
  --
  Sławek Kapłoński
  sla...@kaplonski.pl
  
  ___
  Mailing list:
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
  Post to : openst...@lists.openstack.org
  Unsubscribe :
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev