Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

[pranab boruah]

Hi Numan,
Thanks for the input. I did a fresh install again and used an older  OVS
2.6 package.(not using the TOT).
Things are working now.

Pranab


On 2 February 2017 at 19:19, Numan Siddique  wrote:

>
>
> On Thu, Feb 2, 2017 at 6:05 PM, pranab boruah  > wrote:
>
>> Numan,
>> Sorry for making this thread too long.
>> Kind of deadlock scenario here:
>> The process listening on port 6641 is ovsdb-server(not NB db).
>>
>
> ​This is strange. The default port should be 6640 I suppose if not
> specified.
>
> ​
>
>
>> Details:
>> Start OVS:
>> # /usr/share/openvswitch/scripts/ovs-ctl start  --system-id="random"
>> # netstat -putna | grep 6641
>> tcp0  0 192.168.10.10:6641  0.0.0.0:*
>> LISTEN  5118/ovsdb-server
>> # ps -afx | grep ovsdb
>>  5118 ?S< 0:00  \_ ovsdb-server /etc/openvswitch/conf.db
>> -vconsole:emer -vsyslog:err -vfile:info 
>> --remote=punix:/var/run/openvswitch/db.sock
>> --private-key=db:Open_vSwitch,SSL,private_key
>> --certificate=db:Open_vSwitch,SSL,certificate
>> --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --no-chdir
>> --log-file=/var/log/openvswitch/ovsdb-server.log
>> --pidfile=/var/run/openvswitch/ovsdb-server.pid --detach --monitor
>>
>> Start NB db
>> # /usr/share/openvswitch/scripts/ovn-ctl restart_northd
>> --db-sb-create-insecure-remote=yes --db-nb-create-insecure-remote=yes
>>
>> # netstat -putna | grep 6641
>> tcp0  0 192.168.10.10:6641  0.0.0.0:*
>> LISTEN  5118/ovsdb-server
>>
>> # ps -afx | grep ovsdb
>>  5118 ?S< 0:00  \_ ovsdb-server /etc/openvswitch/conf.db
>> -vconsole:emer -vsyslog:err -vfile:info 
>> --remote=punix:/var/run/openvswitch/db.sock
>> --private-key=db:Open_vSwitch,SSL,private_key
>> --certificate=db:Open_vSwitch,SSL,certificate
>> --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --no-chdir
>> --log-file=/var/log/openvswitch/ovsdb-server.log
>> --pidfile=/var/run/openvswitch/ovsdb-server.pid --detach --monitor
>>
>>  5215 ?S  0:00  \_ ovsdb-server --detach --monitor
>> -vconsole:off --log-file=/var/log/openvswitch/ovsdb-server-nb.log
>> --remote=punix:/var/run/openvswitch/ovnnb_db.sock
>> --pidfile=/var/run/openvswitch/ovnnb_db.pid
>> --remote=db:OVN_Northbound,NB_Global,connections --unixctl=ovnnb_db.ctl
>> --private-key=db:OVN_Northbound,SSL,private_key
>> --certificate=db:OVN_Northbound,SSL,certificate
>> --ca-cert=db:OVN_Northbound,SSL,ca_cert --remote=ptcp:6641:192.168.10.10
>> /etc/openvswitch/ovnnb_db.db
>>
>>  5223 ?S  0:00  \_ ovsdb-server --detach --monitor
>> -vconsole:off --log-file=/var/log/openvswitch/ovsdb-server-sb.log
>> --remote=punix:/var/run/openvswitch/ovnsb_db.sock
>> --pidfile=/var/run/openvswitch/ovnsb_db.pid
>> --remote=db:OVN_Southbound,SB_Global,connections --unixctl=ovnsb_db.ctl
>> --private-key=db:OVN_Southbound,SSL,private_key
>> --certificate=db:OVN_Southbound,SSL,certificate
>> --ca-cert=db:OVN_Southbound,SSL,ca_cert --remote=ptcp:6642:192.168.10.10
>> /etc/openvswitch/ovnsb_db.db
>>
>> Northbound DB logs show the same error.
>>
>> Well I am not supposed to kill the ovsdb-server process. Am I ?
>>
>> Also when I kill the ovsdb-server process, the error goes away. But my
>> doubt is we need the ovsdb-server process on the Controller node. Right?
>>
>
> ​OVN as such doesn't expect ovs-vswitchd (and ovsdb-server for ovs db) ​
>
> ​ running in controller node. May be you can stop the ovs-vswitchd service
> if you don't need it in the controller.
> Also you can configure the NB and SB db ports to some other values if you
> wish so and update the new values in appropriate locations.
> ​Glad that you figured out the issue.
>
> Numan
> ​
>
>
>> Thanks for your patience.
>>
>> Pranab
>>
>>
>>
>>
>> On 2 February 2017 at 17:45, Numan Siddique  wrote:
>>
>>> In the ovsdb logs I see
>>>
>>> 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>> 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>> 2017-02-02T11:07:16.182Z|00022|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>> 2017-02-02T11:07:16.183Z|00023|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>>
>>> Probably you can use netstat and see which processes are listening on
>>> port 6641, kill those processes and restart ovn-northd service and see if
>>> it works.
>>>
>>> Thanks
>>> Numan
>>>
>>>
>>> On Thu, Feb 2, 2017 at 5:26 PM, pranab boruah <
>>> pranabjyotibor...@gmail.com> wrote:
>>>
 NB db is not listening on the port 6641:
  # ovn-nbctl --db=tcp:192.168.10.10:6641 show
 2017-02-02T11:35:10Z|1|ovsdb_idl|ERR|tcp:192.168.10.10:6641:
 requested schema not found
 ovn-nbctl: tcp:192.168.10.10:6641: database connection failed (No such
 file or directory)

 # ovn-sbctl --db=tcp:192.168.10.10:6642 show
 Chassis 

Re: [openstack-dev] [neutron][networking-l2gw] ocata release?

[Gary Kotton]

Done - 
https://review.openstack.org/gitweb?p=openstack/networking-l2gw.git;a=shortlog;h=refs/heads/stable/ocata
A luta continua

On 2/6/17, 8:51 AM, "Gary Kotton"  wrote:

Hi,
Yes, I will go and do this.
Thanks
Gary

On 2/6/17, 4:05 AM, "Takashi Yamamoto"  wrote:

hi,

is anyone going to cut ocata release/branch for networking-l2gw?


__
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][networking-l2gw] ocata release?

[Takashi Yamamoto]

thank you.

On Mon, Feb 6, 2017 at 3:51 PM, Gary Kotton  wrote:
> Hi,
> Yes, I will go and do this.
> Thanks
> Gary
>
> On 2/6/17, 4:05 AM, "Takashi Yamamoto"  wrote:
>
> hi,
>
> is anyone going to cut ocata release/branch for networking-l2gw?
>
> __
> 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] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

[Richard Jones]

That idea has merit, though I don't know what the scope for such a
'neutron-ui' might be. I'm definitely supportive of the Neutron Trunks
UI efforts, but it'd be good to get an answer on this scope question
before rolling along and creating the project.


Richard

On 6 February 2017 at 12:14, Kevin Benton  wrote:
> If the horizon team would like neutron features to live outside, I wonder if
> it would make more sense to create a new 'neutron-ui' repo instead of it
> being trunk specific. That way we don't have to come up with a new repo for
> every new feature that needs a horizon UI.
>
> On Feb 3, 2017 09:26, "Bence Romsics"  wrote:
>>
>> Hi All,
>>
>> I'd like to add support for Neutron Trunks [1][2] into Horizon
>> together with a few colleagues in the Pike cycle. We thought of
>> writing a new Horizon plugin [3] for that purpose. That way I hope to
>> keep it optional for deployment and minimize the maintenance cost for
>> the Horizon core team. Of course we'd welcome all review feedback,
>> especially from the Horizon and Neutron teams.
>>
>> To host the work I'd like create a new project: openstack/neutron-trunk-ui
>>
>> Following the Project Creator's Guide, here's a proposed new project
>> config:
>>
>> https://review.openstack.org/428730
>>
>> And the corresponding governance change:
>>
>> https://review.openstack.org/428796
>>
>> Please review them and if you agree approve. Or guide me to a better
>> change.
>>
>> Thanks in advance,
>> Bence Romsics
>>
>> [1]
>> https://github.com/openstack/openstack-manuals/blob/master/doc/networking-guide/source/config-trunking.rst
>> [2] https://wiki.openstack.org/wiki/Neutron/TrunkPort
>> [3] http://docs.openstack.org/developer/horizon/tutorials/plugin.html
>>
>> __
>> 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][networking-l2gw] ocata release?

[Gary Kotton]

Hi,
Yes, I will go and do this.
Thanks
Gary

On 2/6/17, 4:05 AM, "Takashi Yamamoto"  wrote:

hi,

is anyone going to cut ocata release/branch for networking-l2gw?

__
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] OpenStack Summit Boston-CFP closes February 6th

[Tom Fifield]

Should be good for another 24.5 hours now :) Get those presentations in!

On 廿十七年二月六日 暮 01:26, shubham sharma wrote:

Hi,

I am in IST timezone (UTC+5:30) and I am getting error in submitting
proposal with following error.
" *Warning!* Call for Presentations is closed!. "

Anybody else facing this issue?

Regards
Shubham

On Thu, Feb 2, 2017 at 12:44 AM, Erin Disney > wrote:

Hi Everyone-

Don’t forget: the Call for Presentations for the upcoming OpenStack
Summit Boston closes next week!

The submission deadline is February 6, 2017 at 11:59PM PDT (February
7, 2017 at 6:59 UTC).

Reminder: Proposed sessions must indicate a format: Panel,
presentation or lightning talk. Each format has a maximum number of
speakers associated. Panels are allowed a total of four speakers
plus one moderator, whereas presentations and lightning talks are
limited to two speakers.

As a reminder, speakers are limited to a maximum of three
submissions total.

Contact speakersupp...@openstack.org
with any submission questions.

BOSTON REGISTRATION
Attendee registration is now open
. Purchase your
discounted early bird passes now. Prices will increase in mid March.

SPONSORSHIP SALES
Summit sponsorship sales are also open. You can now sign the
electronic contract here

.
If you plan to sponsor both 2017 OpenStack Summits (Boston in May &
Sydney in November), then check out page 4 of the Boston Summit
Sponsorship Prospectus

for
a special 15% discount on Sydney Summit sponsorship packages. Please
note this only applies to companies who sponsor boththe Boston
Summit and Sydney Summit. Full details of the sponsorship signing
process are outlined here
.

If you have any general Summit questions, contact us at
sum...@openstack.org .


Erin Disney
OpenStack Marketing
e...@openstack.org 


__
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] OpenStack Summit Boston-CFP closes February 6th

[shubham sharma]

Hi,

I am in IST timezone (UTC+5:30) and I am getting error in submitting
proposal with following error.
" *Warning!* Call for Presentations is closed!. "

Anybody else facing this issue?

Regards
Shubham

On Thu, Feb 2, 2017 at 12:44 AM, Erin Disney  wrote:

> Hi Everyone-
>
> Don’t forget: the Call for Presentations for the upcoming OpenStack Summit
> Boston closes next week!
>
> The submission deadline is February 6, 2017 at 11:59PM PDT (February 7,
> 2017 at 6:59 UTC).
>
> Reminder: Proposed sessions must indicate a format: Panel, presentation or
> lightning talk. Each format has a maximum number of speakers associated.
> Panels are allowed a total of four speakers plus one moderator, whereas
> presentations and lightning talks are limited to two speakers.
>
> As a reminder, speakers are limited to a maximum of three submissions
> total.
>
> Contact speakersupp...@openstack.org with any submission questions.
>
> BOSTON REGISTRATION
> Attendee registration is now open
> . Purchase your
> discounted early bird passes now. Prices will increase in mid March.
>
> SPONSORSHIP SALES
> Summit sponsorship sales are also open. You can now sign the electronic
> contract here
> .
> If you plan to sponsor both 2017 OpenStack Summits (Boston in May & Sydney
> in November), then check out page 4 of the Boston Summit Sponsorship
> Prospectus
> 
> for a special 15% discount on Sydney Summit sponsorship packages. Please
> note this only applies to companies who sponsor both the Boston Summit
> and Sydney Summit. Full details of the sponsorship signing process are
> outlined here .
>
> If you have any general Summit questions, contact us at
> sum...@openstack.org.
>
>
> Erin Disney
> OpenStack Marketing
> e...@openstack.org
>
>
> __
> 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][networking-l2gw] ocata release?

[Takashi Yamamoto]

hi,

is anyone going to cut ocata release/branch for networking-l2gw?

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

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

[Takashi Yamamoto]

On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto  wrote:
> hi,
>
> On Fri, Jan 27, 2017 at 7:46 AM, Doug Hellmann  wrote:
>> Excerpts from Takashi Yamamoto's message of 2017-01-26 11:42:48 +0900:
>>> hi,
>>>
>>> On Sat, Jan 14, 2017 at 2:17 AM, Doug Hellmann  
>>> wrote:
>>> > Excerpts from Dariusz Śmigiel's message of 2017-01-13 09:11:01 -0600:
>>> >> 2017-01-12 21:43 GMT-06:00 Takashi Yamamoto :
>>> >> > hi,
>>> >> >
>>> >> > On Wed, Nov 16, 2016 at 11:02 AM, Armando M.  wrote:
>>> >> >> Hi
>>> >> >>
>>> >> >> As of today, the project neutron-vpnaas is no longer part of the 
>>> >> >> neutron
>>> >> >> governance. This was a decision reached after the project saw a 
>>> >> >> dramatic
>>> >> >> drop in active development over a prolonged period of time.
>>> >> >>
>>> >> >> What does this mean in practice?
>>> >> >>
>>> >> >> From a visibility point of view, release notes and documentation will 
>>> >> >> no
>>> >> >> longer appear on openstack.org as of Ocata going forward.
>>> >> >> No more releases will be published by the neutron release team.
>>> >> >> The neutron team will stop proposing fixes for the upstream CI, if not
>>> >> >> solely on a voluntary basis (e.g. I still felt like proposing [2]).
>>> >> >>
>>> >> >> How does it affect you, the user or the deployer?
>>> >> >>
>>> >> >> You can continue to use vpnaas and its CLI via the 
>>> >> >> python-neutronclient and
>>> >> >> expect it to work with neutron up until the newton
>>> >> >> release/python-neutronclient 6.0.0. After this point, if you want a 
>>> >> >> release
>>> >> >> that works for Ocata or newer, you need to proactively request a 
>>> >> >> release
>>> >> >> [5], and reach out to a member of the neutron release team [3] for 
>>> >> >> approval.
>>> >> >
>>> >> > i want to make an ocata release. (and more importantly the stable 
>>> >> > branch,
>>> >> > for the benefit of consuming subprojects)
>>> >> > for the purpose, the next step would be ocata-3, right?
>>> >>
>>> >> Hey Takashi,
>>> >> If you want to release new version of neutron-vpnaas, please look at [1].
>>> >> This is the place, which you need to update and based on provided
>>> >> details, tags and branches will be cut.
>>> >>
>>> >> [1] 
>>> >> https://github.com/openstack/releases/blob/master/deliverables/ocata/neutron-vpnaas.yaml
>>> >
>>> > Unfortunately, since vpnaas is no longer part of an official project,
>>> > we won't be using the releases repository to manage and publish
>>> > information about the releases. It'll need to be done by hand.
>>>
>>> who can/should do it by hand?
>>
>> I can do it. Let me know the version number, and for each repository the
>> SHA of the commit on the master branch to be tagged.

please make it with the following.  thank you!

stable/ocata
10.0.0
openstack/neutron-vpnaas
d6db1238a4950df03dfb28acabcf4df14ebfa3ac

>
> thank you. i'll ask you when necessary.
>
> i think it's fine to just make a branch from master when stable branch is cut
> for neutron.  how others think?
>
>>
>> Doug
>>
>>>
>>> >
>>> > Doug
>>> >
>>> >>
>>> >> BR, Dariusz
>>> >>
>>> >
>>> > __
>>> > 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] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

[Kevin Benton]

If the horizon team would like neutron features to live outside, I wonder
if it would make more sense to create a new 'neutron-ui' repo instead of it
being trunk specific. That way we don't have to come up with a new repo for
every new feature that needs a horizon UI.

On Feb 3, 2017 09:26, "Bence Romsics"  wrote:

> Hi All,
>
> I'd like to add support for Neutron Trunks [1][2] into Horizon
> together with a few colleagues in the Pike cycle. We thought of
> writing a new Horizon plugin [3] for that purpose. That way I hope to
> keep it optional for deployment and minimize the maintenance cost for
> the Horizon core team. Of course we'd welcome all review feedback,
> especially from the Horizon and Neutron teams.
>
> To host the work I'd like create a new project: openstack/neutron-trunk-ui
>
> Following the Project Creator's Guide, here's a proposed new project
> config:
>
> https://review.openstack.org/428730
>
> And the corresponding governance change:
>
> https://review.openstack.org/428796
>
> Please review them and if you agree approve. Or guide me to a better
> change.
>
> Thanks in advance,
> Bence Romsics
>
> [1] https://github.com/openstack/openstack-manuals/blob/master/
> doc/networking-guide/source/config-trunking.rst
> [2] https://wiki.openstack.org/wiki/Neutron/TrunkPort
> [3] http://docs.openstack.org/developer/horizon/tutorials/plugin.html
>
> __
> 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][taas] ocata

[Takashi Yamamoto]

tap-as-a-service folks,

unless anyone objects, i'll make a ocata release and thus stable
branch this week.
(otherwise the CI of consuming subprojects will break)

__
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] [trove] trove 7.0.0.0rc1 (ocata)

[no-reply]

Hello everyone,

A new release candidate for trove for the end of the Ocata
cycle is available!  You can find the source code tarball at:

https://tarballs.openstack.org/trove/

Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally released as the
final Ocata release. You are therefore strongly
encouraged to test and validate this tarball!

Alternatively, you can directly test the stable/ocata release
branch at:

http://git.openstack.org/cgit/openstack/trove/log/?h=stable/ocata

Release notes for trove can be found at:

http://docs.openstack.org/releasenotes/trove/



__
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] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

[Matt Riedemann]

On 2/5/2017 1:19 PM, Clint Byrum wrote:


Also I wonder if there's ever been any serious consideration given to
switching to protobuf? Feels like one could make oslo.versionedobjects
a wrapper around protobuf relatively easily, but perhaps that's already
been explored in a forum that I wasn't paying attention to.


I've never heard of anyone attempting that.

--

Thanks,

Matt Riedemann

__
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] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

[Clint Byrum]

Excerpts from Matt Riedemann's message of 2017-02-04 16:09:56 -0600:
> On 2/2/2017 4:01 PM, Sean Dague wrote:
> >
> > The only services that are running on Apache in standard gate jobs are
> > keystone and the placement api. Everything else is still the
> > oslo.service stack (which is basically run eventlet as a preforking
> > static worker count webserver).
> >
> > The ways in which OpenStack and oslo.service uses eventlet are known to
> > have scaling bottle necks. The Keystone team saw substantial throughput
> > gains going over to apache hosting.
> >
> > -Sean
> >
> 
> FWIW, coincidentally the nova team is going to work on running nova-api 
> under apache in some select jobs in Pike because it turns out that 
> TripleO was running that configuration in Newton which is considered 
> experimental in nova (we don't do some things when running in that mode 
> which are actually pretty critical to how the code functions for 
> upgrades). So if Apache/eventlet is related, maybe we'll see some 
> differences after making that change.
> 
> But I also wouldn't be surprised if Nova is creating more versioned 
> objects which reference other full versioned objects (rather than just 
> an id reference) and maybe some of those are hanging around longer than 
> they should be.
> 

Has there ever been an effort to profile memory usage of oslo versioned
objects, including the actual objects defined in each major project? I
would be willing to wager there are enough circular references that
they're pretty sticky.

Also I wonder if there's ever been any serious consideration given to
switching to protobuf? Feels like one could make oslo.versionedobjects
a wrapper around protobuf relatively easily, but perhaps that's already
been explored in a forum that I wasn't paying attention to. I feel like
that's another example of something I hear in the hallways that doesn't
get any forward progress.

__
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