Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Lajos Katona]

Hi,

Thanks, I check via mobile net than.

Regards
Lajos

On 2018. 11. 07. 11:20, Colleen Murphy wrote:
> On Wed, Nov 7, 2018, at 11:12 AM, Lajos Katona wrote:
>> Hi,
>>
>> Maybe I missed something but I got the message: "Already voted
>> A vote has already been cast using your voter key.
>>
>> Poll results will be available only to the following users:
>>
>> t...@bakeyournoodle.com<mailto:t...@bakeyournoodle.com>"
>>
>> Could you help me to have a correct link?
> The public polling service limits voting to one vote per IP address. If 
> someone in your office space has already voted, the poll won't let anyone 
> else in the office vote. You need to find a different public IP address to 
> vote from, either by tunneling through a proxy or physically going somewhere 
> else with a different network.
>
> Colleen
>
>> Regards
>> Lajos
>>
>> On 2018. 11. 06. 3:19, Tony Breeds wrote:
>>
>>
>> Hi all,
>>
>> Time is running out for you to have your say in the T release name
>> poll.  We have just under 3 days left.  If you haven't voted please do!
>>
>> On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:
>>
>>
>> Hi folks,
>>
>> It is time again to cast your vote for the naming of the T Release.
>> As with last time we'll use a public polling option over per user private 
>> URLs
>> for voting.  This means, everybody should proceed to use the following URL to
>> cast their vote:
>>
>>
>> https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df=b9e448b340787f0e
>>
>> We've selected a public poll to ensure that the whole community, not just 
>> gerrit
>> change owners get a vote.  Also the size of our community has grown such 
>> that we
>> can overwhelm CIVS if using private urls.  A public can mean that users
>> behind NAT, proxy servers or firewalls may receive an message saying
>> that your vote has already been lodged, if this happens please try
>> another IP.
>>
>> Because this is a public poll, results will currently be only viewable by 
>> myself
>> until the poll closes. Once closed, I'll post the URL making the results
>> viewable to everybody. This was done to avoid everybody seeing the results 
>> while
>> the public poll is running.
>>
>> The poll will officially end on 2018-11-08 00:00:00+00:00[1], and
>> results will be
>> posted shortly after.
>>
>> [1] https://governance.openstack.org/tc/reference/release-naming.html
>> ---
>>
>> According to the Release Naming Process, this poll is to determine the
>> community preferences for the name of the T release of OpenStack. It is
>> possible that the top choice is not viable for legal reasons, so the second 
>> or
>> later community preference could wind up being the name.
>>
>> Release Name Criteria
>> -
>>
>> Each release name must start with the letter of the ISO basic Latin alphabet
>> following the initial letter of the previous release, starting with the
>> initial release of "Austin". After "Z", the next name should start with
>> "A" again.
>>
>> The name must be composed only of the 26 characters of the ISO basic Latin
>> alphabet. Names which can be transliterated into this character set are also
>> acceptable.
>>
>> The name must refer to the physical or human geography of the region
>> encompassing the location of the OpenStack design summit for the
>> corresponding release. The exact boundaries of the geographic region under
>> consideration must be declared before the opening of nominations, as part of
>> the initiation of the selection process.
>>
>> The name must be a single word with a maximum of 10 characters. Words that
>> describe the feature should not be included, so "Foo City" or "Foo Peak"
>> would both be eligible as "Foo".
>>
>> Names which do not meet these criteria but otherwise sound really cool
>> should be added to a separate section of the wiki page and the TC may make
>> an exception for one or more of them to be considered in the Condorcet poll.
>> The naming official is responsible for presenting the list of exceptional
>> names for consideration to the TC before the poll opens.
>>
>> Exact Geographic Region
>> ---
>>
>> The Geographic Region from where names for the S release will come is 
>> Colorado
>>
>> Proposed Names
>> --
>>
>> * Tar

Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Lajos Katona]

Hi,

Maybe I missed something but I got the message: "Already voted
A vote has already been cast using your voter key.

Poll results will be available only to the following users:

t...@bakeyournoodle.com"

Could you help me to have a correct link?

Regards
Lajos

On 2018. 11. 06. 3:19, Tony Breeds wrote:


Hi all,

   Time is running out for you to have your say in the T release name
poll.  We have just under 3 days left.  If you haven't voted please do!

On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:


Hi folks,

It is time again to cast your vote for the naming of the T Release.
As with last time we'll use a public polling option over per user private URLs
for voting.  This means, everybody should proceed to use the following URL to
cast their vote:

  
https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df=b9e448b340787f0e

We've selected a public poll to ensure that the whole community, not just gerrit
change owners get a vote.  Also the size of our community has grown such that we
can overwhelm CIVS if using private urls.  A public can mean that users
behind NAT, proxy servers or firewalls may receive an message saying
that your vote has already been lodged, if this happens please try
another IP.

Because this is a public poll, results will currently be only viewable by myself
until the poll closes. Once closed, I'll post the URL making the results
viewable to everybody. This was done to avoid everybody seeing the results while
the public poll is running.

The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results will 
be
posted shortly after.

[1] https://governance.openstack.org/tc/reference/release-naming.html
---

According to the Release Naming Process, this poll is to determine the
community preferences for the name of the T release of OpenStack. It is
possible that the top choice is not viable for legal reasons, so the second or
later community preference could wind up being the name.

Release Name Criteria
-

Each release name must start with the letter of the ISO basic Latin alphabet
following the initial letter of the previous release, starting with the
initial release of "Austin". After "Z", the next name should start with
"A" again.

The name must be composed only of the 26 characters of the ISO basic Latin
alphabet. Names which can be transliterated into this character set are also
acceptable.

The name must refer to the physical or human geography of the region
encompassing the location of the OpenStack design summit for the
corresponding release. The exact boundaries of the geographic region under
consideration must be declared before the opening of nominations, as part of
the initiation of the selection process.

The name must be a single word with a maximum of 10 characters. Words that
describe the feature should not be included, so "Foo City" or "Foo Peak"
would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may make
an exception for one or more of them to be considered in the Condorcet poll.
The naming official is responsible for presenting the list of exceptional
names for consideration to the TC before the poll opens.

Exact Geographic Region
---

The Geographic Region from where names for the S release will come is Colorado

Proposed Names
--

* Tarryall
* Teakettle
* Teller
* Telluride
* Thomas : the Tank Engine
* Thornton
* Tiger
* Tincup
* Timnath
* Timber
* Tiny Town
* Torreys
* Trail
* Trinidad
* Treasure
* Troublesome
* Trussville
* Turret
* Tyrone

Proposed Names that do not meet the criteria (accepted by the TC)
-

* Train : Many Attendees of the first Denver PTG have a story to tell about 
the trains near the PTG hotel.  We could celebrate those stories with this name

Yours Tony.







__
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



Yours Tony.




__
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] [heat][neutron] Extraroute support

[Lajos Katona]

Thanks for the answer.

On 2018-06-01 18:04, Kevin Benton wrote:
The neutron API now supports compare and swap updates with an If-Match 
header so the race condition can be avoided.

https://bugs.launchpad.net/neutron/+bug/1703234



On Fri, Jun 1, 2018, 04:57 Rabi Mishra <mailto:ramis...@redhat.com>> wrote:



On Fri, Jun 1, 2018 at 3:57 PM, Lajos Katona
mailto:lajos.kat...@ericsson.com>> wrote:

Hi,

Could somebody help me out with Neutron's Extraroute support
in Hot templates.
The support status of the Extraroute is support.UNSUPPORTED in
heat, and only create and delete are the supported operations.
see:

https://github.com/openstack/heat/blob/master/heat/engine/resources/openstack/neutron/extraroute.py#LC35

As I see the unsupported tag was added when the feature was
moved from the contrib folder to in-tree
(https://review.openstack.org/186608)
Perhaps you can help me out why only create and delete are
supported and update not.


I think most of the resources when moved from contrib to in-tree
are marked as unsupported. Adding routes to an existing router by
multiple stacks can be racy and is probably the reason use of this
resource is not encouraged and hence it's not supported. You can
see the discussion in the original patch that proposed this
resource https://review.openstack.org/#/c/41044/

Not sure if things have changed on neutron side for us to revisit
the concerns.

Also it does not have any update_allowed properties, hence no
handle_update(). It would be replaced if you change any property.

Hope it helps.

Thanks in advance for  the help.

Regards
Lajos



__
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




-- 
Regards,

Rabi Mishra

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
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] [heat][neutron] Extraroute support

[Lajos Katona]

Hi,

Could somebody help me out with Neutron's Extraroute support in Hot 
templates.
The support status of the Extraroute is support.UNSUPPORTED in heat, and 
only create and delete are the supported operations.
see: 
https://github.com/openstack/heat/blob/master/heat/engine/resources/openstack/neutron/extraroute.py#LC35


As I see the unsupported tag was added when the feature was moved from 
the contrib folder to in-tree (https://review.openstack.org/186608)
Perhaps you can help me out why only create and delete are supported and 
update not.


Thanks in advance for  the help.

Regards
Lajos


__
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] [horizon] FFE Request for Queens

[Lajos Katona]

Thanks Akihiro
I will bring it up on today's meeting.

Regards
Lajos

On 2018-01-31 10:39, Akihiro Motoki wrote:

+1 for FFE. I can support it.

We need a final ack from our PTL.

Akihiro

2018-01-30 5:13 GMT+09:00 Lajos Katona <lajos.kat...@ericsson.com>:

Hi,

I would like to ask for FFE on the neutron-trunk-ui blueprint to let the
admin panel for trunks be accepted for Queens.

Based on discussion on IRC
(http://eavesdrop.openstack.org/irclogs/%23openstack-horizon/%23openstack-horizon.2018-01-29.log.html#t2018-01-29T14:36:58
) the remaining part of the blueprint neutron-trunk-ui
(https://blueprints.launchpad.net/horizon/+spec/neutron-trunk-ui) should be
handled separately:

The admin panel (https://review.openstack.org/516657) should be part of the
Queens release, as now that is not dependent on the ngDetails patches. With
this the blueprint should be set to implemented.
The links (https://review.openstack.org/524619) for the ports details (trunk
parent and subports) from the trunk panel should be handled in a bug report:

https://bugs.launchpad.net/horizon/+bug/1746082

Regards
Lajos Katona

__
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] [horizon] FFE Request for Queens

[Lajos Katona]

Hi,

I would like to ask for FFE on the neutron-trunk-ui blueprint to let the 
admin panel for trunks be accepted for Queens.


Based on discussion on IRC 
(http://eavesdrop.openstack.org/irclogs/%23openstack-horizon/%23openstack-horizon.2018-01-29.log.html#t2018-01-29T14:36:58 
) the remaining part of the blueprint neutron-trunk-ui 
(https://blueprints.launchpad.net/horizon/+spec/neutron-trunk-ui) should 
be handled separately:


 * The admin panel (https://review.openstack.org/516657) should be part
   of the Queens release, as now that is not dependent on the ngDetails
   patches. With this the blueprint should be set to implemented.
 * The links (https://review.openstack.org/524619) for the ports
   details (trunk parent and subports) from the trunk panel should be
   handled in a bug report:
 o https://bugs.launchpad.net/horizon/+bug/1746082

Regards
Lajos Katona
__
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] [horizon][trunk][ngdetails] Trunk admin panel and changes related to ngdetails patches

[Lajos Katona]

Hi Horizon Team

I read the meeting log 
(http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-01-10-20.00.log.html) 
and if I understand well the proposal is to merge part of the ngdetails 
patches 
(https://review.openstack.org/#/q/topic:bug/1681627+(status:open) ) in 
Queens, and address the remaining issues in Rocky, am I right?


Could you help me to find a way to proceed with the remaining trunk 
related patches which are dependent on the above patches

(https://review.openstack.org/#/q/project:openstack/horizon+status:open+AND+owner:%22Lajos+Katona+%253Clajos.katona%2540ericsson.com%253E%22).

What do you think, shall I remove the dependency for ngdetails fix and 
add TODOs or similar to the code or wait for and help Shu with his work?


Thanks in advance for the help.

Regards
Lajos

__
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] q-agt failed to start with ovs firevalldriver

[Lajos Katona]

Hi,

Perhaps this is my fault but this morning I wanted to start devstack 
(master) with q-trunk enabled, and got this error:
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]:   File 
"/usr/local/lib/python2.7/dist-packages/ryu/lib/hub.py", line 65, in _launch

Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: raise e
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ImportError: 
Class not found.
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: CRITICAL 
neutron [-] Unhandled error: ImportError: Class not found.
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR neutron 
Traceback (most recent call last):
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File "/usr/local/bin/neutron-openvswitch-agent", line 10, in 

Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron sys.exit(main())
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File 
"/opt/stack/neutron/neutron/cmd/eventlet/plugins/ovs_neutron_agent.py", 
line 20, in main
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron agent_main.main()
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File 
"/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/main.py", 
line 49, in main
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron mod.main()
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File 
"/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/main.py", 
line 35, in main
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron 'neutron.plugins.ml2.drivers.openvswitch.agent.'
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File 
"/usr/local/lib/python2.7/dist-packages/ryu/base/app_manager.py", line 
375, in run_apps
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron hub.joinall(services)
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File "/usr/local/lib/python2.7/dist-packages/ryu/lib/hub.py", 
line 103, in joinall
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron t.wait()
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 
175, in wait
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron return self._exit_event.wait()
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 125, in 
wait
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron current.throw(*self._exc)
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 
214, in main
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron result = function(*args, **kwargs)
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron   File "/usr/local/lib/python2.7/dist-packages/ryu/lib/hub.py", 
line 65, in _launch
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR 
neutron raise e
Oct 30 08:59:22 horizon neutron-openvswitch-agent[24556]: ERROR neutron 
ImportError: Class not found.


I started successfully with the noop firewall driver after the problem.
I run devstack with *PIP_UPGRADE=True* & *RECLONE=yes*.

Could you help me if this is some misconfiguration from my side, or 
perhaps some requirements issue?


Regards
Lajos

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

[Lajos Katona]

Hi,

I copy here the answer from Maruti Haridas Kamat (part of the team which 
originally designed networking-l2gw) to the question why this was 
originally designed this way (no update is possible if there is an 
active connection on the gw):

"

I understand your use case, and we thought about it when we were 
designing the solution.


 Consider you have an interface and a physical switch that is 
present inside a neutron logical l2gw, and create a connection, then you 
have already created VXLAN-to-VLAN bindings on that interface on the 
physical switch or OVS. If you allow a user to update the gateway to 
modify the interface or switch list, then we need to fiddle with the 
VXLAN-to-VLAN bindings on the switch (es).


Steps:

1. The user creates a logical gateway gw1 comprising of switch s1 and
   interface i1. No validation is performed here.
2. The user creates a connection VXLAN (1000) to physical VLAN (100)
   binding. This performs all the validation inside the DB where the
   specified switch s1 and interface i1 exist. Whether the specified
   binding already exists or not. Finally, the plugin communicates to
   the southbound (agent) that creates the binding 1000 <-> 100 on the
   interface i1 on the switch (OVS).
3. Consider that the user tries to add another interface i2 now to the
   same gateway gw1 using update gw1 command. It does not perform any
   validation. The entire validation we do in step 2 has to be moved to
   this step now. Also, the code (south bound) that makes changes on
   the OVS has to be introduced.
4. We avoided this because the user may try to add and remove the
   interfaces in one go in the same command. If we had to allow update
   connection command, then internally we have to perform binding of
   vxlan with vlan for interface i2 but we have to remove the binding
   from i1 (considering i1 has been removed from the gw1) at the same time.
5. It is not that it is not possible, but for the first version of L2gw
   in first six months, we thought of supporting basic framework of all
   these CLIs/REST APIs and enhance them later.

"
It will not give too much extra, but perhaps good to see the reasoning 
from another perspective.


Regards Lajos

On 2017-10-12 01:55, Dayavanti Gopal Kamath wrote:


Hi ricardo,

Since the l2gw connection semantics is applied on the l2gw object as a 
whole, we could assume any connections applied on the l2gw object can 
be retroactively applied to the ports that are affected by the the 
l2gw update. so, if a port is added to an existing l2gw, all existing 
l2gw connections get applied on that port, and if a port is deleted 
from an l2gw, all existing l2gw connections get removed from this port.


Thanks,

daya

*From:*Ricardo Noriega De Soto [mailto:rnori...@redhat.com]
*Sent:* Tuesday, October 10, 2017 6:14 AM
*To:* OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
*Cc:* Gary Kotton <gkot...@vmware.com>; Ihar Hrachyshka 
<ihrac...@redhat.com>; arma...@gmail.com; miguel.lava...@huawei.com; 
Luis Tomas Bolivar <ltoma...@redhat.com>; maruti.ka...@radisys.com; 
Lajos Katona <lajos.kat...@ericsson.com>; Dayavanti Gopal Kamath 
<dayavanti.gopal.kam...@ericsson.com>; George Offord 
<george.off...@ericsson.com>

*Subject:* Re: [openstack-dev] l2gw

I've been taking a look at the implementation and thinking about which 
cases update should be allowed.


At a first glance, I would say that we should allow updates:

·Add a new interface (neutron l2-gateway-update gw1 --device 
name=hwvtep,interface_names=eth0,*eth1*) being eth1 the new interface.


·Delete interface (neutron l2-gateway-update gw1 --device 
name=hwvtep,interface_names=eth0) removing eth1. In this case, we 
should check that the port has not any active connection.


However, in both cases there is a big issue, which is the granularity 
of the segmentation-ids per port, right?? You cannot add or remove an 
l2gw connection per port, which bring us to a dead end.


Let's say I add eth1 to an existing l2gw. How can I get a vlan tag to 
that interface?? There is not l2gw-connection-update command... and 
trying to create the same one will fail. Even if you try to update the 
l2gw instance specifying the seg-id per port, it won't be active until 
a new connection is created.


Folks, based on your experience, what's your take on this??

IMHO, there is no easy way of solving this but with a big re-architecture.

On Fri, Sep 29, 2017 at 1:46 PM, Lajos Katona 
<lajos.kat...@ericsson.com <mailto:lajos.kat...@ericsson.com>> wrote:


Hi Ricardo,

That is the exception which gives us the trouble.

If you have ideas as you mentioned in which case a gw should be
updated, and in what not, that would be really nice.
Actually now we have a kind of development environment with
devstack and vtep emulator
(http://docs.openvswitch.org/en/latest/how

Re: [openstack-dev] [self-healing] When shall have self-healing meeting?

[Lajos Katona]

Hi,

Is there any news, rumors anything about this self-healing meeting and SIG?
Any information is appreciated.

Regards
Lajos

On 2017-09-22 08:08, Lajos Katona wrote:

Hi,

In Denver there was a session on self-healing and how to give 
direction to the ambitions around the topic, and some agreement that 
bi-weekly meeting should be organized.
Is there anybody who knows some details about that? Doddle, irc 
channel etc?


Thanks in advance for the answer.
Regards
Lajos

__ 


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] l2gw

[Lajos Katona]

Hi Ricardo,

That is the exception which gives us the trouble.

If you have ideas as you mentioned in which case a gw should be updated, 
and in what not, that would be really nice.
Actually now we have a kind of development environment with devstack and 
vtep emulator (http://docs.openvswitch.org/en/latest/howto/vtep/) on the 
same host, what do you think is that enough to go on with this problem?
I am not so sure if with vtep emulator we can cover all the good and bad 
(I mean when we mustn't do the update for example) scenarios.


Regards
Lajos

On 2017-09-28 14:12, Ricardo Noriega De Soto wrote:

I see the exception now Lajos:

class L2GatewayInUse(exceptions.InUse):
    message = _("L2 Gateway '%(gateway_id)s' still has active mappings "
                "with one or more neutron networks.")

:-)

On Wed, Sep 27, 2017 at 6:40 PM, Ricardo Noriega De Soto 
<rnori...@redhat.com <mailto:rnori...@redhat.com>> wrote:


Hey Lajos,

Is this the exception you are encountering?

(neutron) l2-gateway-update --device
name=hwvtep,interface_names=eth0,eth1 gw1
L2 Gateway 'b8ef7f98-e901-4ef5-b159-df53364ca996' still has active
mappings with one or more neutron networks.
Neutron server returns request_ids:
['req-f231dc53-cb7d-4221-ab74-fa8715f85869']

I don't see the L2GatewayInUse exception you're talking about, but
I guess it's the same situation.

We should discuss in which case the l2gw instance could be
updated, and in which cases it shouldn't.

Please, let me know!



On Wed, Aug 16, 2017 at 11:14 AM, Lajos Katona
<lajos.kat...@ericsson.com <mailto:lajos.kat...@ericsson.com>> wrote:

Hi,

We faced an issue with l2-gw-update, which means that actually
if there are connections for a gw the update will throw an
exception (L2GatewayInUse), and the update is only possible
after deleting first the connections, do the update and add
the connections back.

It is not exactly clear why this restriction is there in the
code (at least I can't find it in docs or comments in the
code, or review).
As I see the check for network connections was introduced in
this patch:
https://review.openstack.org/#/c/144097
<https://review.openstack.org/#/c/144097>

(https://review.openstack.org/#/c/144097/21..22/networking_l2gw/db/l2gateway/l2gateway_db.py

<https://review.openstack.org/#/c/144097/21..22/networking_l2gw/db/l2gateway/l2gateway_db.py>)

Could you please give me a little background why the update
operation is not allowed on an l2gw with network connections?

Thanks in advance for the help.

Regards
Lajos


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




-- 
Ricardo Noriega


Senior Software Engineer - NFV Partner Engineer | Office of
Technology  | Red Hat
irc: rnoriega @freenode




--
Ricardo Noriega

Senior Software Engineer - NFV Partner Engineer | Office of Technology 
 | Red Hat

irc: rnoriega @freenode



__
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] [self-healing] When shall have self-healing meeting?

[Lajos Katona]

Hi,

In Denver there was a session on self-healing and how to give direction 
to the ambitions around the topic, and some agreement that bi-weekly 
meeting should be organized.
Is there anybody who knows some details about that? Doddle, irc channel 
etc?


Thanks in advance for the answer.
Regards
Lajos

__
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] Fwd: [l2gw]

[Lajos Katona]

Hi,

We faced an issue with l2-gw-update, which means that actually if there
are connections for a gw the update will throw an exception
(L2GatewayInUse), and the update is only possible after deleting first
the connections, do the update and add the connections back.

It is not exactly clear why this restriction is there in the code (at
least I can't find it in docs or comments in the code, or review).
As I see the check for network connections was introduced in this patch:
https://review.openstack.org/#/c/144097
(https://review.openstack.org/#/c/144097/21..22/networking_l2gw/db/l2gateway/l2gateway_db.py)

Could you please give me a little background why the update operation is
not allowed on an l2gw with network connections?

Thanks in advance for the help.

Regards
Lajos

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

[Lajos Katona]

Hi,

We faced an issue with l2-gw-update, which means that actually if there 
are connections for a gw the update will throw an exception 
(L2GatewayInUse), and the update is only possible after deleting first 
the connections, do the update and add the connections back.


It is not exactly clear why this restriction is there in the code (at 
least I can't find it in docs or comments in the code, or review).

As I see the check for network connections was introduced in this patch:
https://review.openstack.org/#/c/144097 
(https://review.openstack.org/#/c/144097/21..22/networking_l2gw/db/l2gateway/l2gateway_db.py)


Could you please give me a little background why the update operation is 
not allowed on an l2gw with network connections?


Thanks in advance for the help.

Regards
Lajos

__
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] [horizon][trunk] forever spinning modalspinner when deleting resource from details page

[Lajos Katona]

Hi,

I am working on the neutron-trunk-ui, to make the possibility for the 
user to use trunks via web GUI.
For the patch which shows the details for the trunk 
(https://review.openstack.org/464727) I realized that
the Delete action actually seems to be hanging if I delete from the 
detail page.


Symptoms:

 * There is an error toast (and 404 in the console) that the trunk
   can't be accessed. That should be normal, as I just deleted it.
 o As I see from old django pages the way of working in these
   situations should be to suppress the 404 and the error toast,
   and go back to the list of resources table, am I right?
 * The modal spinner ("Please Wait") hangs for ever => That is the
   more serious problem.
 o I tried to check the fully working angular example which is for
   me the images panel, and actually that is working the same way:
 + Click on an image
 + On the details page click on delete and there is the forever
   spinning modal

In my latest patch I get rid of the forever spinning modal, and I should 
get rid of the error toast as well, and go back to the

list of trunks table.
BUT I have the feeling that I mess up the horizon framework.

Could somebody help me out what should be the direction to solve this 
problem in a horizon/angular way?


Thanks in advance for the help.

Regards
Lajos
__
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] [infra][devstack] stable/kilo devstack fails with pkg_resources.ContextualVersionConflict

[Lajos Katona]

Hi,

In our internal CI system we realized that stable/kilo devstack fails 
with the following stack trace:

2016-04-18 13:11:30.344 | + /usr/local/bin/*keystone-manage db_sync*
2016-04-18 13:11:31.142 | Traceback (most recent call last):
2016-04-18 13:11:31.142 | File "/usr/local/bin/keystone-manage", line 4, 
in 
2016-04-18 13:11:31.142 | 
__import__('pkg_resources').require('keystone==2015.1.4.dev4')
2016-04-18 13:11:31.142 | File 
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2927, in 

2016-04-18 13:11:31.143 | @_call_aside
2016-04-18 13:11:31.143 | File 
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2913, in _call_aside

2016-04-18 13:11:31.143 | f(*args, **kwargs)
2016-04-18 13:11:31.143 | File 
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2940, in _initialize_master_working_set

2016-04-18 13:11:31.144 | working_set = WorkingSet._build_master()
2016-04-18 13:11:31.144 | File 
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
637, in _build_master

2016-04-18 13:11:31.144 | return cls._build_from_requirements(__requires__)
2016-04-18 13:11:31.144 | File 
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
650, in _build_from_requirements

2016-04-18 13:11:31.145 | dists = ws.resolve(reqs, Environment())
2016-04-18 13:11:31.145 | File 
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
834, in resolve
2016-04-18 13:11:31.145 | raise VersionConflict(dist, 
req).with_context(dependent_req)
2016-04-18 13:11:31.145 | *pkg_resources.ContextualVersionConflict: (pbr 
0.11.1 (/usr/local/lib/python2.7/dist-packages), 
Requirement.parse('pbr>=1.8'), set(['testresources']))*


It seems that the root cause is that testresources has a new version 
2.0.0 from 18 April.


I tried to find similar errors on openstack infra, but for me 
http://logstash.openstack.org/ gives back no result.


I have a patch in requirements (https://review.openstack.org/307174) but 
I got the same error for those runs.


Could somebody help to find a solution for this?

Regards
Lajos

__
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] [tempest] Is there a sandbox project how to use tempest test plugin interface?

[Lajos Katona]

Hi Matthew,

Finally I made it working, so now I have a dummy plugin.

Few questions, remarks:
- For me it was little hard to merge my weak knowledge from python 
packaging with the documentation for tempest plugins, do you mind if I 
push an example to github, and I add the link to that to the documentation.


- From this point the generation of the idempotent id is not clear for 
me. I was able to use the check_uuid.py, and as I used a virtenv, the 
script edited the 
/.tox/venv/local/lib/python2.7/site-packages/dummyplugin// file.
Would be good maybe to add an extra path option to the check_uuid.py to 
make it possible to edit the real source files in similar cases not the 
ones in the venv.


Regards
Lajos

On 09/11/2015 08:50 AM, Lajos Katona wrote:

Hi Matthew,

Thanks for the help, this helped a lot a start the work.

regards
Lajos

On 09/10/2015 04:13 PM, Matthew Treinish wrote:

On Thu, Sep 10, 2015 at 02:56:31PM +0200, Lajos Katona wrote:

Hi,

I just noticed that from tag 6, the test plugin interface considered ready,
and I am eager to start to use it.
I have some questions:

If I understand well in the future the plugin interface will be moved to
tempest-lib, but now I have to import module(s) from tempest to start to use
the interface.
Is there a plan for this, I mean when the whole interface will be moved to
tempest-lib?

The only thing which will eventually move to tempest-lib is the abstract class
that defines the expected methods of a plugin class [1] The other pieces will
remain in tempest. Honestly this won't likely happen until sometime during
Mitaka. Also when it does move to tempest-lib we'll deprecate the tempest
version and keep it around to allow for a graceful switchover.

The rationale behind this is we really don't provide any stability guarantees
on tempest internals (except for a couple of places which are documented, like
this plugin class) and we want any code from tempest that's useful to external
consumers to really live in tempest-lib.


If I start to create a test plugin now (from tag 6), what should be the best
solution to do this?
I thought to create a repo for my plugin and add that as a subrepo to my
local tempest repo, and than I can easily import stuff from tempest, but I
can keep my test code separated from other parts of tempest.
Is there a better way of doing this?

To start I'd take a look at the documentation for tempest plugins:

http://docs.openstack.org/developer/tempest/plugin.html

>From tempest's point of view a plugin is really just an entry point that points
to a class that exposes certain methods. So the Tempest plugin can live anywhere
as long as it's installed as an entry point in the proper namespace. Personally
I feel like including it as a subrepo in a local tempest tree is a bit strange,
but I don't think it'll cause any issues if you do that.


If there would be an example plugin somewhere, that would be the most
preferable maybe.

There is a cookiecutter repo in progress. [2] Once that's ready it'll let you
create a blank plugin dir that'll be ready for you to populate. (similar to the
devstack plugin cookiecutter that already exists)

For current examples the only project I know of that's using a plugin interface
is manila [3] so maybe take a look at what they're doing.

-Matt Treinish

[1]http://git.openstack.org/cgit/openstack/tempest/tree/tempest/test_discover/plugins.py#n26
[2]https://review.openstack.org/208389
[3]https://review.openstack.org/#/c/201955


__
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] [tempest] Is there a sandbox project how to use tempest test plugin interface?

[Lajos Katona]

Hi Matthew,

Thanks for the help, this helped a lot a start the work.

regards
Lajos

On 09/10/2015 04:13 PM, Matthew Treinish wrote:

On Thu, Sep 10, 2015 at 02:56:31PM +0200, Lajos Katona wrote:

Hi,

I just noticed that from tag 6, the test plugin interface considered ready,
and I am eager to start to use it.
I have some questions:

If I understand well in the future the plugin interface will be moved to
tempest-lib, but now I have to import module(s) from tempest to start to use
the interface.
Is there a plan for this, I mean when the whole interface will be moved to
tempest-lib?

The only thing which will eventually move to tempest-lib is the abstract class
that defines the expected methods of a plugin class [1] The other pieces will
remain in tempest. Honestly this won't likely happen until sometime during
Mitaka. Also when it does move to tempest-lib we'll deprecate the tempest
version and keep it around to allow for a graceful switchover.

The rationale behind this is we really don't provide any stability guarantees
on tempest internals (except for a couple of places which are documented, like
this plugin class) and we want any code from tempest that's useful to external
consumers to really live in tempest-lib.


If I start to create a test plugin now (from tag 6), what should be the best
solution to do this?
I thought to create a repo for my plugin and add that as a subrepo to my
local tempest repo, and than I can easily import stuff from tempest, but I
can keep my test code separated from other parts of tempest.
Is there a better way of doing this?

To start I'd take a look at the documentation for tempest plugins:

http://docs.openstack.org/developer/tempest/plugin.html

 From tempest's point of view a plugin is really just an entry point that points
to a class that exposes certain methods. So the Tempest plugin can live anywhere
as long as it's installed as an entry point in the proper namespace. Personally
I feel like including it as a subrepo in a local tempest tree is a bit strange,
but I don't think it'll cause any issues if you do that.


If there would be an example plugin somewhere, that would be the most
preferable maybe.

There is a cookiecutter repo in progress. [2] Once that's ready it'll let you
create a blank plugin dir that'll be ready for you to populate. (similar to the
devstack plugin cookiecutter that already exists)

For current examples the only project I know of that's using a plugin interface
is manila [3] so maybe take a look at what they're doing.

-Matt Treinish

[1] 
http://git.openstack.org/cgit/openstack/tempest/tree/tempest/test_discover/plugins.py#n26
[2] https://review.openstack.org/208389
[3] https://review.openstack.org/#/c/201955


__
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] [tempest] Is there a sandbox project how to use tempest test plugin interface?

[Lajos Katona]

Hi,

I just noticed that from tag 6, the test plugin interface considered 
ready, and I am eager to start to use it.

I have some questions:

If I understand well in the future the plugin interface will be moved to 
tempest-lib, but now I have to import module(s) from tempest to start to 
use the interface.
Is there a plan for this, I mean when the whole interface will be moved 
to tempest-lib?


If I start to create a test plugin now (from tag 6), what should be the 
best solution to do this?
I thought to create a repo for my plugin and add that as a subrepo to my 
local tempest repo, and than I can easily import stuff from tempest, but 
I can keep my test code separated from other parts of tempest.

Is there a better way of doing this?

If there would be an example plugin somewhere, that would be the most 
preferable maybe.


Thanks in advance for the help.

Regards
Lajos

__
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