[openstack-dev] Pike packages for openSUSE and SLES available

[Thomas Bechtold]

Hi,

Pike packages for openSUSE and SLES are now available at:

http://download.opensuse.org/repositories/Cloud:/OpenStack:/Pike/

We maintain + test the packages for SLES 12SP3 and openSUSE Leap 42.3.

If you find issues, please do not hesitate to report them to
opensuse-cloud at opensuse.org or to https://bugzilla.opensuse.org/

Thanks and have a lot of fun,

Tom

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

[openstack-dev] [openstack] [charms] Openstack with OVN

[Aakash Kt]

Hello all,
Resending this mail since I think there might have been some error
sending it the last time.

   I am looking to develop an openstack bundle which uses OVN as the SDN. I
have been reading : https://docs.openstack.org/charm-guide/latest/
I have also read : https://docs.openstack.org/networking-ovn/latest/install/
index.html

As far as I understand, this will require me to replace the
"neutron-openvswitch" charm in the openstack base bundle. However, I am not
able to exactly understand what all I will have to rewrite / replace to
make this work.
Specifically, I need to make neutron work only as an API instead of the
full blown SDN. Also, in the above doc, its mentioned that we have to run
some setup on "controller nodes". How does the term "controller node" map
to the charm?

Thank you for helping out, and sorry if these doubts seem trivial

Thanks again,
Aakash
__
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] Request to delete some unused pages from OpenStack wiki

[Chen Ying]

Thanks a lot.

Best regards
Chen Ying

2017-08-28 16:38 GMT+08:00 Thierry Carrez :

> Chen Ying wrote:
> > The name of the project data protection as a service has been
> > changed to Karbor for a long time.
> > The name smuag is no longer needed. So some pages about smaug could be
> > deleted from OpenStack wiki.
> > But I don't have permissions. Hope that these pages[1] could be deleted
> > by anyone who has the
> > administrator permissions to the wiki. Thanks.
>
> Done!
>
> --
> Thierry Carrez (ttx)
>
> __
> 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] [Cyborg] Cyborg SPDK Driver Review

[We We]

Hi all,

I have submitted the proposal about the cyborg SPDK 
driver(https://review.openstack.org/#/c/498651/), please review at it.

Thx,
heluwei

__
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] [oslo] schedule for Denver PTG is ready !

[ChangBo Guo]

sure, will adjust the schedule

2017-08-29 2:24 GMT+08:00 Doug Hellmann :

> Excerpts from ChangBo Guo's message of 2017-08-28 23:14:05 +0800:
> > Please check  for the draft in [1], we can adjust if you have conflicts
> > with other discussions.
> >
> > We have specific cross projects coding event  in the Tuesday afternoon,
> for
> > more details please
> > check [2] and [3],  please join us if you're free from 1:00 PM to 3: PM
> on
> > Tuesday.
> >
> > [1] https://etherpad.openstack.org/p/oslo-ptg-queens
> > [2]
> > http://lists.openstack.org/pipermail/openstack-dev/2017-
> August/121345.html
> > [3] https://etherpad.openstack.org/p/oslo-queens-tasks
> >
>
> I think we can drop the discussion of retiring oslosphinx from the
> schedule. We had no objections, and the way forward is clear (see the
> other thread [4] for details).
>
> Doug
>
> [4] http://lists.openstack.org/pipermail/openstack-dev/2017-
> August/121564.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
>



-- 
ChangBo Guo(gcb)
__
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] placement/resource providers update 33

[Matt Riedemann]

On 8/25/2017 7:54 AM, Chris Dent wrote:

* https://bugs.launchpad.net/nova/+bug/1712411
   Allocations may not be removed from dest node during failed migrations


Started with the functional recreate test patch:

https://review.openstack.org/#/c/498627/

--

Thanks,

Matt

__
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] [TripleO] CI design session at the PTG

[Clark Boylan]

On Mon, Aug 28, 2017, at 07:19 AM, Paul Belanger wrote:
> On Mon, Aug 28, 2017 at 09:42:45AM -0400, David Moreau Simard wrote:
> > Hi,
> > 
> > (cc whom I would at least like to attend)
> > 
> > The PTG would be a great opportunity to talk about CI design/layout
> > and how we see things moving forward in TripleO with Zuul v3, upstream
> > and in review.rdoproject.org.
> > 
> > Can we have a formal session on this scheduled somewhere ?
> > 
> Wednesday onwards likely is best for me, otherwise, I can find time
> during
> Mon-Tues if that is better.

The Zuulv3 stuff may be appropriate during the Infra team helproom on
Monday and Tuesday. There will be an afternoon Zuulv3 for OpenStack devs
session in Vail at 2pm Monday, but I think we generally plan on helping
with Zuulv3 during the entire helproom time.

Clark

__
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] placement/resource providers update 33

[Matt Riedemann]

On 8/28/2017 5:09 PM, Matt Riedemann wrote:
There are some issues with this, mainly around the fact this is talking 
about scheduling, as I expect it to work today when I came into reading 
this, but it's talking in detail about the alternatives stuff which was 
not implemented in Pike, so I think that should be removed, or amended 
with a big fat note that it's not available yet and anything to do with 
alternatives is future work.


Since patches are welcome, I've put forth a patch:

https://review.openstack.org/#/c/498613/

--

Thanks,

Matt

__
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] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG

[Emilien Macchi]

On Fri, Aug 25, 2017 at 5:00 PM, Emilien Macchi  wrote:
> I created an etherpad: https://etherpad.openstack.org/p/deployment-queens
>
> Please bring topics (and names) - we'll try to be prepared before the
> PTG with an agenda and some scheduling.

I think being together in a room during ~2h would be a good start (if
we need more we can figure that out during the session).
My hope is we can create some ad-hoc collaborations between projects
without having everyone involved at the same time.

I don't have any specific schedule on the Monday & Tuesday (I'll be
walking between rooms and see where I can contribute) - we might want
to block a 2h slot in our agenda to make sure we can meet.

Let's try with Monday 2pm in the Packaging room (dedicated to
Deployment Tools). So we still have the Tuesday in case we need more
sessions together.
I would like to see people from TripleO, Kolla, OpenStack Ansible,
OpenStack Helm (at minimum) signing up on
https://etherpad.openstack.org/p/deployment-queens
and confirming (or not) that schedule would work.

Thanks,
-- 
Emilien Macchi

__
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] [tripleo] PTG Agenda draft - action required

[Emilien Macchi]

Please look https://etherpad.openstack.org/p/tripleo-ptg-queens

and tell us (in private or here) if there is any conflict with your agenda.
This is a draft, a proposal, we can make any change as long as we have
the feedback.

Also, it's still time to propose topics, please go ahead and
contribute to the etherpad. We'll review the schedule before the PTG
(probably during our weekly meetings tomorrow and next week).

Thanks,
-- 
Emilien Macchi

__
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] placement/resource providers update 33

[Matt Riedemann]

On 8/25/2017 7:54 AM, Chris Dent wrote:


There's a stack that documents (with visual aids!) the flow of
scheduler and placement. It is pretty much ready:

https://review.openstack.org/#/c/475810/


I see I am late to the party here, but I've left comments in the 
now-merged patch.


There are some issues with this, mainly around the fact this is talking 
about scheduling, as I expect it to work today when I came into reading 
this, but it's talking in detail about the alternatives stuff which was 
not implemented in Pike, so I think that should be removed, or amended 
with a big fat note that it's not available yet and anything to do with 
alternatives is future work.


--

Thanks,

Matt

__
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] horizon 12.0.0.0rc3 (pike)

[no-reply]

Hello everyone,

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

https://tarballs.openstack.org/horizon/

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

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

http://git.openstack.org/cgit/openstack/horizon/log/?h=stable/pike

Release notes for horizon can be found at:

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




__
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]notification update week 35

[Matt Riedemann]

On 8/28/2017 10:52 AM, Balazs Gibizer wrote:
[Undecided] https://bugs.launchpad.net/nova/+bug/1700496 Notifications 
are emitted per-cell instead of globally
Devstack config has already been modified so notifications are emitted 
to the top level MQ. It seems that only a nova cells doc update is 
needed that tells the admin how to configure the transport_url for the not

ifications.


This was done as part of the cells v2 layout docs here:

https://docs.openstack.org/nova/latest/user/cellsv2_layout.html#notifications

--

Thanks,

Matt

__
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] [ironic] this week's priorities and subteam reports

[Yeleswarapu, Ramamani]

Hi,

We are glad to present this week's priorities and subteam report for Ironic. As 
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)

1. Refactoring of the way we access clients: 
https://review.openstack.org/#/q/topic:bug/1699547
2. Rolling upgrades missing bit: https://review.openstack.org/#/c/497666/
2.1. disallow upgrades from ocata: https://review.openstack.org/#/c/497685/
2.2. check object versions in dbsync tool: 
https://review.openstack.org/#/c/497703/
3. Switch to none auth for standalone mode: 
https://review.openstack.org/#/c/359061/
4. Review specs in preparation for the PTG


Bugs (dtantsur, vdrok, TheJulia)

- Stats (diff between 21 Aug 2017 and 28 Aug 2017)
- Ironic: 250 bugs (+4) + 256 wishlist items (-3). 23 new, 190 in progress 
(+3), 0 critical, 30 high (-2) and 33 incomplete (+2)
- Inspector: 12 bugs + 29 wishlist items. 2 new, 10 in progress, 0 critical, 2 
high and 3 incomplete
- Nova bugs with Ironic tag: 14 (-3). 0 new, 0 critical, 1 high

CI refactoring and missing test coverage

- not considered a priority, it's a 'do it always' thing
- Standalone CI tests (vsaienk0)
- next patch to be reviewed, needed for 3rd party CI: 
https://review.openstack.org/#/c/429770/
- Missing test coverage (all)
- portgroups and attach/detach tempest tests: 
https://review.openstack.org/382476
- local boot with partition images: TODO 
https://bugs.launchpad.net/ironic/+bug/1531149
- adoption: https://review.openstack.org/#/c/344975/
- should probably be changed to use standalone tests
- root device hints: TODO
- node take over?
- resource classes integration tests: 
https://review.openstack.org/#/c/443628/

Essential Priorities


Nova resource class based scheduling changes (dtantsur)
---
- I have to add this, as there are things to finish by end of Pike to avoid 
problems in Queens
- TODO as of 28 Aug 2017:
- all done
- Optionally:
- integration tests: https://review.openstack.org/#/c/443628/

Generic boot-from-volume (TheJulia, dtantsur)
-
- BFV Meetings on hold until September.
- specs and blueprints:
- 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/volume-connection-information.html
- code: https://review.openstack.org/#/q/topic:bug/1526231
- 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/boot-from-volume-reference-drivers.html
- code: https://review.openstack.org/#/q/topic:bug/1559691
- https://blueprints.launchpad.net/nova/+spec/ironic-boot-from-volume
- code: 
https://review.openstack.org/#/q/topic:bp/ironic-boot-from-volume
- status as of 21 Aug 2017:
- Pike stuff is done and released, including also the iRMC implementation
- Queens ideas/thoughts should be posted to the BFV etherpad: 
https://etherpad.openstack.org/p/Ironic-BFV
- Not required for Pike:
- Nova:
https://review.openstack.org/#/c/468353 - Ironic: Get IP address 
for volume connector

Rolling upgrades and grenade-partial (rloo, jlvillal)
-
- spec approved; code patches: 
https://review.openstack.org/#/q/topic:bug/1526283
- status as of most recent weekly meeting:
- add 'ironic-dbsync online_data_migrations' call to regular grenade test 
(not multinode test because grenade multinode test doesn't upgrade all 
services) https://review.openstack.org/497949 - APPROVED
- to address restarting services after unpinning, spec: 'SIGHUP restarts 
services with updated configs': https://review.openstack.org/474309. APPROVED
- code needs rebasing: https://review.openstack.org/#/c/474331/3
- outstanding: dev documentation needs updating: 
https://review.openstack.org/#/c/419439/
- we forgot to set the conductor version in the database :-( So that 
rolling upgrades will work without having to cut another Pike release, 2 
patches starting with:
- conductor saves version in db: 
https://review.openstack.org/#/c/497593/. (Not needed, but would be good to 
backport so less data migration in Rocky)
- patches to switch over/disallow ocata -> queens upgrade, they depend on 
above patch, and start with:
- Add online data migrations for conductor version 
(https://review.openstack.org/#/c/497666/1)

Driver composition (dtantsur)
-
- spec: 
http://specs.openstack.org/openstack/ironic-specs/specs/approved/driver-composition-reform.html
- gerrit topic: https://review.openstack.org/#/q/status:open+topic:bug/1524745
- status as of 28 Aug 2017:
- documentation
- upgrade guide for the remaining drivers: TODO
- ilo: 

Re: [openstack-dev] [ironic] Team dinner at the PTG?

[Arkady.Kanevsky]

Great. See you all there.

-Original Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com] 
Sent: Monday, August 28, 2017 1:07 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [ironic] Team dinner at the PTG?

And the final day is Monday, Sep 11th. See you there! :)

On 08/23/2017 03:46 PM, Dmitry Tantsur wrote:
> Hi folks!
> 
> We're trying to organize an informal team meeting at some place, 
> probably with burgers and beer, in Denver. Note that it won't be sponsored.
> 
> Please vote in the Doodle https://doodle.com/poll/nvavg9ab9ebq2e4v 
> about the days you're available.
> 
> If you're local, we need you help finding a good place to go. Please 
> ping Julia
> (TheJulia) or myself (dtantsur) on IRC if you're willing to help.
> 
> Thanks,
> Dmitry


__
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][infra] Functional job failure rate at 100%

[Jeremy Stanley]

On 2017-08-11 15:31:58 +0200 (+0200), Jakub Libosvar wrote:
[...]
> My best hope is they are gonna backport the fix to 4.4.0 and tag a
> new kernel so we can start running the tests again.

Just to follow up on this thread, it looks like the Ubuntu kernel
team have had the upstream fix patched into xenial-proposed for a
couple weeks already, awaiting confirmation from someone with the
ability to reproduce the issue. Please see
https://launchpad.net/bugs/1709032 if you can help close it out.
-- 
Jeremy Stanley


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] [os-upstream-institute] Meeting reminder

[Ildiko Vancsa]

Hi Training Team,

This is a friendly reminder that we are having our meeting in less than an hour 
(2000 UTC) on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
__
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] [oslo] schedule for Denver PTG is ready !

[Doug Hellmann]

Excerpts from ChangBo Guo's message of 2017-08-28 23:14:05 +0800:
> Please check  for the draft in [1], we can adjust if you have conflicts
> with other discussions.
> 
> We have specific cross projects coding event  in the Tuesday afternoon, for
> more details please
> check [2] and [3],  please join us if you're free from 1:00 PM to 3: PM on
> Tuesday.
> 
> [1] https://etherpad.openstack.org/p/oslo-ptg-queens
> [2]
> http://lists.openstack.org/pipermail/openstack-dev/2017-August/121345.html
> [3] https://etherpad.openstack.org/p/oslo-queens-tasks
> 

I think we can drop the discussion of retiring oslosphinx from the
schedule. We had no objections, and the way forward is clear (see the
other thread [4] for details).

Doug

[4] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121564.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

Re: [openstack-dev] [ironic] Team dinner at the PTG?

[Dmitry Tantsur]

And the final day is Monday, Sep 11th. See you there! :)

On 08/23/2017 03:46 PM, Dmitry Tantsur wrote:

Hi folks!

We're trying to organize an informal team meeting at some place, probably with 
burgers and beer, in Denver. Note that it won't be sponsored.


Please vote in the Doodle https://doodle.com/poll/nvavg9ab9ebq2e4v about the 
days you're available.


If you're local, we need you help finding a good place to go. Please ping Julia 
(TheJulia) or myself (dtantsur) on IRC if you're willing to help.


Thanks,
Dmitry



__
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] [oslo] scheduling oslosphinx for retirement at the start of queens

[Doug Hellmann]

> On Jul 10, 2017, at 9:10 AM, Doug Hellmann  wrote:
> 
> Oslo team,
> 
> With all documentation now moving to use the openstackdocs theme,
> I propose that we retire the oslosphinx repository during Queens.
> We should go ahead and create the stable/pike branch at the end of
> this cycle, so that we have a way to deal with bugs in existing
> pike releases, but I think we can retire the repository at any point
> after that.

After looking into the retirement process, and discussing it with fungi, I 
think we’re going to have to wait to do anything for now. 

It will be complicated to remove the contents of the master branch now without 
following the full retirement process, and that will make it impossible for us 
to maintain stable releases for the library through the end of Pike's support 
lifetime (because the gate jobs will all be turned off). So for now 
https://review.openstack.org/#/c/498543/1 marks the library as obsolete and 
https://bugs.launchpad.net/oslosphinx/+bug/1713543 will help us remember to 
follow the retirement process later.

Doug


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

Re: [openstack-dev] [docs] [ptls] Install guide testing

[Andreas Jaeger]

On 2017-08-28 18:50, Michał Jastrzębski  wrote:
> One thing I'd be worried about is that not only maintaining this doc
> will be very costly (we're now only talking of few services out of big
> tent..), will cover just basic architectures, but also if someone
> actually uses it, it will make things like upgrade quite hard.
> 
> If it's only meant to be PoC installation guide, we should clearly say
> so, if we mean it to be prod-ready, we need things like HA
> configuration, database clustering, network architecture and so on..

It is intented as POC, see
https://docs.openstack.org/install-guide/overview.html
"This guide covers step-by-step deployment of the major OpenStack
services using a functional example architecture suitable for new users
of OpenStack with sufficient Linux experience. This guide is not
intended to be used for production system installations, but to create a
minimum proof-of-concept for the purpose of learning about OpenStack."

If you think, it could be made much more visible in some more places,
please send patches,

for HA there's a separate guide,
Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] [monasca] Queens Mid-Cycle

[witold.be...@est.fujitsu.com]

Hello everyone,

Monasca team will hold a Mid-Cycle meeting for the Queens release on Sep. 20th 
and 21st via remote conferencing. Please add the topics you would like to 
discuss or features you would like to see in the next release to the etherpad 
[1].
The connection details are included in the etherpad.


Best regards
Witek

[1] https://etherpad.openstack.org/p/monasca_queens_midcycle

__
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] [docs] [ptls] Install guide testing

[Michał Jastrzębski]

One thing I'd be worried about is that not only maintaining this doc
will be very costly (we're now only talking of few services out of big
tent..), will cover just basic architectures, but also if someone
actually uses it, it will make things like upgrade quite hard.

If it's only meant to be PoC installation guide, we should clearly say
so, if we mean it to be prod-ready, we need things like HA
configuration, database clustering, network architecture and so on..

On 28 August 2017 at 09:13, Jay S Bryant  wrote:
> Alex,
>
> Thank you for starting this thread.  I will bring this up with Cinder team
> and see what we can do to help.
>
> Jay
>
>
> On 8/25/2017 3:57 AM, Alexandra Settle wrote:
>
> Hi everyone,
>
>
>
> The documentation team is searching for volunteers to help test and verify
> the OpenStack installation instructions here:
> https://docs.openstack.org/install-guide/
>
>
>
> Previously this action has been undertaken by a series of volunteers, mostly
> from the documentation team. However due to the migration, and a significant
> drop in contributors, we are now seeking new individuals to help us complete
> this task.
>
>
>
> We will be tracking any work here:
> https://wiki.openstack.org/wiki/Documentation/PikeDocTesting You can see
> what we have previously done for testing here:
> https://wiki.openstack.org/wiki/Documentation/OcataDocTesting
>
>
>
> PTLs of cinder/keystone/horizon/neutron/nova/glance – Previously the
> documentation team performed the testing tasks for your respective projects
> as they lived within the openstack-manuals repo. We appreciate that you may
> or may not have the resources to continue this effort, but it would be great
> if your teams are able. Please let me know if you are able to so we can
> verify the instructions of these projects :)
>
>
>
> Thanks,
>
>
>
> Alex
>
>
>
> __
> 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] [docs][ptg] Doc team attendance

[Jay S Bryant]

Alex,

I will be there Monday and Tuesday for sure.  Will try to participate 
some later in the week depending on how the Cinder sessions go, but will 
be mostly tied up Wed-Fri.


Jay


On 8/18/2017 4:02 AM, Alexandra Settle wrote:


Hi everyone,

I’ve updated the docs PTG etherpad with a few details: 
https://etherpad.openstack.org/p/denver-doc-PTG


All those attending, could you please put your names/availability on 
the etherpad.


Also – to those interested who cannot attend on the Mon-Tues for 
Queens planning sessions, please note that I have booked Wednesday 
morning in Colorado Ballroom C for migration-specific discussions. 
See: https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms


If you wish to attend **these** sessions, please put your name in the 
Wednesday slot in the etherpad.


Cheers,

Alex



__
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] [docs] [ptls] Install guide testing

[Jay S Bryant]

Alex,

Thank you for starting this thread.  I will bring this up with Cinder 
team and see what we can do to help.


Jay


On 8/25/2017 3:57 AM, Alexandra Settle wrote:


Hi everyone,

The documentation team is searching for volunteers to help test and 
verify the OpenStack installation instructions here: 
https://docs.openstack.org/install-guide/


Previously this action has been undertaken by a series of volunteers, 
mostly from the documentation team. However due to the migration, and 
a significant drop in contributors, we are now seeking new individuals 
to help us complete this task.


We will be tracking any work here: 
https://wiki.openstack.org/wiki/Documentation/PikeDocTesting You can 
see what we have previously done for testing here: 
https://wiki.openstack.org/wiki/Documentation/OcataDocTesting


*PTLs of cinder/keystone/horizon/neutron/nova/glance*– Previously the 
documentation team performed the testing tasks for your respective 
projects as they lived within the openstack-manuals repo. We 
appreciate that you may or may not have the resources to continue this 
effort, but it would be great if your teams are able. Please let me 
know if you are able to so we can verify the instructions of these 
projects :)


Thanks,

Alex



__
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] [nova] Can we remove the monkey_patch_modules config option?

[Matt Riedemann]

On 8/28/2017 9:51 AM, Alex Schultz wrote:

JFYI,https://review.openstack.org/#/c/494305/

Since this was just added, someone is looking to use it or is using it.


Thanks for pointing this out. I've asked in the puppet review that the 
submitter of that change explain if/why they are using this config 
option and reply to this thread, since the change to deprecate the 
option in nova just merged:


https://review.openstack.org/498113

--

Thanks,

Matt

__
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] [magnum] Weekly meetings

[Spyros Trigazis]

Hello,

As discussed in last week's meeting [0], this week and next we will
discuss plans about Queens and review blueprints. So, if you want
to add discussion items please bring them up tomorrow or next week in
our weekly meeting. If for any reason, you can't attend you can start
a thread in the mailing list.

Also this week, we will go through our blueprint list and clean it up from
obsolete blueprints.

Finally, I would like to ask you to review this blueprint [1] about cluster
federation, add your ideas and comments in the review.

Cheers,
Spyros

[0] 
http://eavesdrop.openstack.org/meetings/containers/2017/containers.2017-08-22-16.00.html
[1] https://review.openstack.org/#/c/489609/

On 22 August 2017 at 17:47, Spyros Trigazis  wrote:
> Hello,
>
> Recently we decided to have bi-weekly meetings. Starting from today we will
> have weekly meetings again.
>
> From now on, we will have our meeting every Tuesday at 1600 UTC
> in #openstack-meeting-alt . For today, that is in 13 minutes.
>
> Cheers,
> Spyros

__
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] [nova]notification update week 35

[Balazs Gibizer]

Hi,

After a couple of weeks of silence here is the status update / focus 
settings mail for w35.


Bugs


As there was no critical bug for Pike in the notification area there 
was not much progress in the bugs below.


[Low] https://bugs.launchpad.net/nova/+bug/1696152 nova notifications
use nova-api as binary name instead of nova-osapi_compute
Agreed not to change the binary name in the notifications. Instead we
make an enum for that name to show that the name is intentional.
The patch was split to two parts:
* https://review.openstack.org/#/c/487126 rename binary to source in
versioned notifications
* https://review.openstack.org/#/c/476538 Use enum value instead of
string service name
While I was preparing this mail both patches has been approved.

[Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault
notification is never emitted
Still no response on the ML thread about the way forward.
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118639.html

[High] https://bugs.launchpad.net/nova/+bug/1706563
TestRPC.test_cleanup_notifier_null fails with timeout
[High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error:
Cannot recover from stack overflow. - in py35 unit test job
The first bug is just a duplicate of the second. It seems the TetRPC
test suite has a way to end up in an infinite recusion.
I don't know about a way to reproduce it localy or to change the gate
env so that python prints out the full stack trace to see where the
problematic call is. Also adding extra log messages won't help as a
timed out test doesn't have the log messages printed to the logs. So
this bug is pretty stuck.

[Undecided] https://bugs.launchpad.net/nova/+bug/1700496 Notifications 
are emitted per-cell instead of globally
Devstack config has already been modified so notifications are emitted 
to the top level MQ. It seems that only a nova cells doc update is 
needed that tells the admin how to configure the transport_url for the 
not

ifications.

Versioned notification transformation
-
BP for Queens are approved, some patch was already re-proposed to the 
new BP. I think we have to start reviewing those soon.

https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-queens

Searchlight integration
---
I opened a follow up bp for Queens:
https://blueprints.launchpad.net/nova/+spec/additional-notification-fields-for-searchlight-queens
I left it in drafting state as I expect the Searchlight team to come
back with some feedback and / or extra needs. I pinged the Searchlight 
folks on IRC to get some feedback on this BP.


Small improvements
--

* https://review.openstack.org/#/c/428199/ Improve assertJsonEqual
error reporting. This is on the gate now. :)

* https://review.openstack.org/#/q/topic:refactor-notification-samples
Factor out duplicated notification sample data
This is a start of a longer patch series to deduplicate notification
sample data. The third patch already shows how much sample data can be
deleted from nova tree. We added a minimal hand rolled json ref
implementation to notification sample test as the existing python json
ref implementations are not well maintained.
I will rebase the series and resolve the merge conflicts then I will 
ask for feedback about the validity of the current direction.



Weekly meeting
--
After a long pause let's have a short subteam meeting at the usual 
place and time:

Tuesday 17:00 UTC on openstack-meeting-4.
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170829T17

Cheers,
gibi




__
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] [os-upstream-institute][all] Get together at the PTG

[Jay S Bryant]

Ildiko,

Thanks for setting this up.  I will be there and would love to join.  I 
too have more flexibility on Monday and Tuesday.


Thanks!

Jay



On 8/25/2017 9:36 AM, Ildiko Vancsa wrote:

Hi Training Team and All,

As we have our next PTG coming up shortly I think that would be a great 
opportunity for the team and everyone who’s interested to meet and check where 
we are and what our future plans are. :)

I would like to ask you to raise your hand by replying to this mail if you will 
be around during the PTG week in Denver and would be interested in joining. 
Please also indicate your availability for the week.

Based on the responses we will pick a day and a time that works best for most 
to have our gathering.

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)



__
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] [TripleO] CI design session at the PTG

[David Moreau Simard]

On Mon, Aug 28, 2017 at 10:25 AM, Wesley Hayutin  wrote:
> +1 from me, I'm sure John, Sagi, and Arx are also interested.

Yes, of course, I just went with whom I knew were going to the PTG.
Anyone else is welcome to join as well !


David Moreau Simard
Senior Software Engineer | OpenStack RDO

dmsimard = [irc, github, twitter]


On Mon, Aug 28, 2017 at 10:25 AM, Wesley Hayutin  wrote:
>
>
> On Mon, Aug 28, 2017 at 10:19 AM, Paul Belanger 
> wrote:
>>
>> On Mon, Aug 28, 2017 at 09:42:45AM -0400, David Moreau Simard wrote:
>> > Hi,
>> >
>> > (cc whom I would at least like to attend)
>> >
>> > The PTG would be a great opportunity to talk about CI design/layout
>> > and how we see things moving forward in TripleO with Zuul v3, upstream
>> > and in review.rdoproject.org.
>> >
>> > Can we have a formal session on this scheduled somewhere ?
>> >
>> Wednesday onwards likely is best for me, otherwise, I can find time during
>> Mon-Tues if that is better.
>>
>
> +1 from me, I'm sure John, Sagi, and Arx are also interested.
>
> Thanks
>

__
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] [TripleO] CI design session at the PTG

[David Moreau Simard]

On Mon, Aug 28, 2017 at 10:58 AM, Emilien Macchi  wrote:
> Yeah, this session would be interesting to do.
> Feel free to add it on https://etherpad.openstack.org/p/tripleo-ptg-queens
> We need to work on scheduling before the PTG but it would likely
> happen between Wednesday and Friday morning.

Good idea, I've added it to the etherpad [1] and I've created a pad
for the session as well [2].

[1]: https://etherpad.openstack.org/p/tripleo-ptg-queens
[2]: https://etherpad.openstack.org/p/tripleo-ptg-queens-ci

David Moreau Simard
Senior Software Engineer | OpenStack RDO

dmsimard = [irc, github, twitter]

__
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] [Monasca] GridDB repository support

[gordon chung]

On 28/08/17 10:32 AM, witold.be...@est.fujitsu.com wrote:
> The number looks good but the test you have referenced was performed with the 
> file storage driver which is not really scalable. It would be great if you 
> could provide numbers for the Ceph backend.
> Please keep us updated.

these are numbers i got using a ceph backend with gnocchi v3[1]. i 
should mention that v3 wasn't targeting write performance improvements 
(not directly). for reference, i think my ceph cluster had 30 OSDs.

the actual write throughput will depend on the driver you select (redis 
probably fastest, ceph a close second) and as jd mentioned, the batch sizes.

[1] https://www.slideshare.net/GordonChung/gnocchi-v3/18

-- 
gord
__
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] [oslo][oslo.messaging] Proposing Andy Smith as an oslo.messaging core reviewers

[Andy Smith]

Thank you all for your consideration and support. I look forward to
increased engagement and participation as an olso.message core reviewer.

On Mon, Aug 28, 2017 at 9:43 AM, ChangBo Guo  wrote:

> There is no objection during last two weeks,  added Andy Smith as
> oslo.message core reviewer
> Welcome Andy !
>
> 2017-08-16 23:06 GMT+08:00 Ken Giusti :
>
>> +1
>>
>> On Mon, Aug 14, 2017 at 6:59 AM, ChangBo Guo  wrote:
>>
>>> I propose that we add Andy Smith to the oslo.messaging team.
>>>
>>> Andy Smith has been actively contributing to oslo.messaging for a while
>>> now, both
>>> in helping make oslo.messaging better via code contribution(s) and by
>>> helping with
>>> the review load when he can. He's been involved on the AMQP 1.0 side for
>>> awhile. He's really interested in taking ownership of the experimental
>>> Kafka driver, which would be great to have someone able to drive that.
>>>
>>> Please respond with +1/-1
>>>
>>> Voting will last 2 weeks and will end at 28th of August.
>>>
>>> Cheers,
>>> --
>>> ChangBo Guo(gcb)
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Ken Giusti  (kgiu...@gmail.com)
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> ChangBo Guo(gcb)
>
> __
> 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] [tripleo] add mistral to the auto-update package list for TripleO CI

[Dougal Matthews]

On 25 August 2017 at 13:27, Brad P. Crochet  wrote:

> On Thu, Aug 24, 2017 at 5:35 PM, Ben Nemec  wrote:
> > I think I'm +0 on this.  On the one hand we do have the gating job on
> > Mistral, on the other hand our gate jobs don't exercise all of the
> > functionality of some projects, especially Mistral.  I know in the past
> > introspection has been broken by changes in Mistral, and that wouldn't be
> > caught by gate jobs.  If we start using master all the time that becomes
> a
> > blocker for TripleO since it will prevent our OVB jobs from passing.
> >
> > So I can understand the desire to use master of a tightly coupled project
> > like Mistral, but it does open a hole in our promotion pipeline which I
> > don't feel great about.  If we had an OVB job running on every patch (and
> > respected by the Mistral cores) I'd be +1 with no reservations.
>
> I am +1 on this. However, I do echo Ben's concerns. I will bring this
> up with the Mistral group at the PTG. We already have an experimental
> job available, but I'm guessing the major concern will be the amount
> of time it takes for a TripleO job to run. It would likely double the
> amount of time that a Mistral patch takes to get through CI.
>

I agree with you both. So would be +1 to adding Mistral (and adding an OVB
job to Mistral).

I think the length of time will be a concern, but I think the overhead of
Mistral contributors having to understand and debug failed tripleo gates
could be a bigger problem.


>
> >
> >
> > On 08/24/2017 04:04 PM, Wesley Hayutin wrote:
> >>
> >> Greetings,
> >>
> >> I'd like to propose that the mistral project be added to the list of
> >> projects where in CI the very latest built packages are added to each
> CI run
> >> [1].
> >>
> >> This will help get patches that depend on mistral patches to more
> quickly
> >> be tested and merged.  For example Honza's patch [2] depends on a merged
> >> mistral change.  The mistral change has not yet landed in a tripleo
> build
> >> and mistral is not on the auto-update list, so the patch fails.
> >>
> >> Please respond if you would like to see mistral added or have any
> comments
> >> or concerns.
> >>
> >> Note that we are able to consider mistral for auto-updates because the
> >> mistral project has a voting tripleo job [3] and the tripleo project
> can be
> >> assured that the latest mistral patches will not break tripleo-ci.
> >>
> >> I would encourage other projects to consider adding tripleo jobs to
> their
> >> project to enable auto-updates as well [4] 
> >>
> >> [1]
> >> https://github.com/openstack/tripleo-quickstart/blob/
> master/config/release/tripleo-ci/master.yml#L54-L70
> >> [2] https://review.openstack.org/#/c/469608/
> >> [3]
> >> https://github.com/openstack-infra/project-config/blob/
> master/zuul/layout.yaml#L11665
> >> [4]
> >> https://docs.openstack.org/tripleo-docs/latest/
> contributor/check_gates.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
> >>
> >
>
>
>
> --
> Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
> Principal Software Engineer
>
> __
> 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] [all] [oslo] schedule for Denver PTG is ready !

[ChangBo Guo]

Please check  for the draft in [1], we can adjust if you have conflicts
with other discussions.

We have specific cross projects coding event  in the Tuesday afternoon, for
more details please
check [2] and [3],  please join us if you're free from 1:00 PM to 3: PM on
Tuesday.

[1] https://etherpad.openstack.org/p/oslo-ptg-queens
[2]
http://lists.openstack.org/pipermail/openstack-dev/2017-August/121345.html
[3] https://etherpad.openstack.org/p/oslo-queens-tasks

-- 
ChangBo Guo(gcb)
__
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] [TripleO] CI design session at the PTG

[Emilien Macchi]

On Mon, Aug 28, 2017 at 6:42 AM, David Moreau Simard  wrote:
[...]
> Can we have a formal session on this scheduled somewhere ?

Yeah, this session would be interesting to do.
Feel free to add it on https://etherpad.openstack.org/p/tripleo-ptg-queens
We need to work on scheduling before the PTG but it would likely
happen between Wednesday and Friday morning.

Thanks,
-- 
Emilien Macchi

__
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] Can we remove the monkey_patch_modules config option?

[Alex Schultz]

On Fri, Aug 25, 2017 at 3:51 PM, Matt Riedemann  wrote:
> I'm having a hard time tracing what this is necessary for. It's related to
> the notify_decorator which is around for legacy notifications but I don't
> actually see that decorator used anywhere. Given there are other options
> related to the notify_decorator, like "default_publisher_id" if we can start
> unwinding and removing this legacy stuff it would make the config (.005%)
> simpler.
>
> It also just looks like we have a monkey_patch option that is run at the
> beginning of every service, uses monkey_patch_modules and if loaded, monkey
> patches whatever is configured for modules.
>
> I mean, if we thought hooks were bad, this is pretty terrible.
>

JFYI, https://review.openstack.org/#/c/494305/

Since this was just added, someone is looking to use it or is using it.

Thanks,
-Alex

> --
>
> Thanks,
>
> Matt
>
> __
> 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] [Monasca] GridDB repository support

[witold.be...@est.fujitsu.com]

> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: Montag, 28. August 2017 16:03
> To: Bedyk, Witold 
> Cc: OpenStack Development Mailing List (not for usage questions)
> 
> Subject: Re: [openstack-dev] [Monasca] GridDB repository support
> 
> On Mon, Aug 28 2017, witold.be...@est.fujitsu.com wrote:
> 
> > Can you give some reference to Gnocchi's performance measurements?
> > I have seen you presentation from the last Summit [1] but I cannot
> > find information about Gnocchi's write throughput. In the issues slide
> > you note the slow post API. The API responsiveness test shows that the
> > API can handle correctly up to 2500 instances. You collect around 60
> > metrics per instance and use polling interval of 10 minutes. That would
> translate to:
> >
> > 2500 instances * 60 metrics/instance / 600 s = 250 metrics/s
> >
> > Are these assumptions correct?
> 
> It really depends on the number of measures you include in each of your API
> requests. Ceilometer does very little batching.
> 
> If you batch those measurements, you could achieve up to 120k measures/s
> in Gnocchi already 2 years ago¹. Considering the various improvement we did
> over that timeframe, you can likely go higher.
> 
> And since it scales horizontally, you can double the request handling by
> adding another node. :)
> 
> I'll probably try to do some benchmark one of these days, but I don't have
> proper hardware to do so for now. :)
> 
> ¹  https://julien.danjou.info/blog/2015/gnocchi-benchmarks


The number looks good but the test you have referenced was performed with the 
file storage driver which is not really scalable. It would be great if you 
could provide numbers for the Ceph backend.
Please keep us updated.

Cheers
Witek
__
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] [TripleO] CI design session at the PTG

[Wesley Hayutin]

On Mon, Aug 28, 2017 at 10:19 AM, Paul Belanger 
wrote:

> On Mon, Aug 28, 2017 at 09:42:45AM -0400, David Moreau Simard wrote:
> > Hi,
> >
> > (cc whom I would at least like to attend)
> >
> > The PTG would be a great opportunity to talk about CI design/layout
> > and how we see things moving forward in TripleO with Zuul v3, upstream
> > and in review.rdoproject.org.
> >
> > Can we have a formal session on this scheduled somewhere ?
> >
> Wednesday onwards likely is best for me, otherwise, I can find time during
> Mon-Tues if that is better.
>
>
+1 from me, I'm sure John, Sagi, and Arx are also interested.

Thanks
__
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] [TripleO] CI design session at the PTG

[Paul Belanger]

On Mon, Aug 28, 2017 at 09:42:45AM -0400, David Moreau Simard wrote:
> Hi,
> 
> (cc whom I would at least like to attend)
> 
> The PTG would be a great opportunity to talk about CI design/layout
> and how we see things moving forward in TripleO with Zuul v3, upstream
> and in review.rdoproject.org.
> 
> Can we have a formal session on this scheduled somewhere ?
> 
Wednesday onwards likely is best for me, otherwise, I can find time during
Mon-Tues if that is better.

__
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][nova][neutron][qa][panko][blazar]: OpenStack meets ETSI NFV workshop on 12.09.2017

[Csatari, Gergely (Nokia - HU/Budapest)]

Hi, 

Thanks for the clarification. 

Our understanding was that with Panko it is possible to subscribe to the state 
of the different resource of the cloud as it is descibed in [1]. This is why we 
mapped the Virtualised [Compute|Network|Storage] Resources Capacity Management 
Interfaces to Panko. 

[1]: https://wiki.openstack.org/wiki/Telemetry#Managed

Br, 
Gerg0


-Original Message-
From: gordon chung [mailto:g...@live.ca] 
Sent: Monday, August 28, 2017 3:05 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all][nova][neutron][qa][panko][blazar]: OpenStack 
meets ETSI NFV workshop on 12.09.2017


> Gaps to be discussed are here:
> https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-expla
> ined

i added a note in etherpad but it seems you want Ceilometer (+Gnocchi if you 
need storagE) and not Panko. Panko only handles storage of events (more 
metadata focused data) while Ceilometer handles the actual generation of both 
events and metrics, the latter being the one you want it seems. Gnocchi is used 
for optimised time-series metric storage.

unfortunately, i don't believe anyone from Telemetry teams are attending the 
PTG but we can be reached on ML or #openstack-telemetry.

cheers,

--
gord
__
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] [Monasca] GridDB repository support

[Julien Danjou]

On Mon, Aug 28 2017, witold.be...@est.fujitsu.com wrote:

> Can you give some reference to Gnocchi's performance measurements?
> I have seen you presentation from the last Summit [1] but I cannot find
> information about Gnocchi's write throughput. In the issues slide you note the
> slow post API. The API responsiveness test shows that the API can handle
> correctly up to 2500 instances. You collect around 60 metrics per instance and
> use polling interval of 10 minutes. That would translate to:
>
> 2500 instances * 60 metrics/instance / 600 s = 250 metrics/s
>
> Are these assumptions correct?

It really depends on the number of measures you include in each of your
API requests. Ceilometer does very little batching.

If you batch those measurements, you could achieve up to 120k measures/s
in Gnocchi already 2 years ago¹. Considering the various improvement we
did over that timeframe, you can likely go higher.

And since it scales horizontally, you can double the request handling by
adding another node. :)

I'll probably try to do some benchmark one of these days, but I don't
have proper hardware to do so for now. :)

¹  https://julien.danjou.info/blog/2015/gnocchi-benchmarks

-- 
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info


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] [TripleO] CI design session at the PTG

[Harry Rybacki]

On Mon, Aug 28, 2017 at 9:42 AM, David Moreau Simard  wrote:
> Hi,
>
> (cc whom I would at least like to attend)
>
> The PTG would be a great opportunity to talk about CI design/layout
> and how we see things moving forward in TripleO with Zuul v3, upstream
> and in review.rdoproject.org.
>
> Can we have a formal session on this scheduled somewhere ?
>
+1

> David Moreau Simard
> Senior Software Engineer | OpenStack RDO
>
> dmsimard = [irc, github, twitter]
>
> __
> 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] [all][nova][neutron][qa][panko][blazar]: OpenStack meets ETSI NFV workshop on 12.09.2017

[Csatari, Gergely (Nokia - HU/Budapest)]

Hi, 

Going inline. 

-Original Message-
From: Ghanshyam Mann [mailto:ghanshyamm...@gmail.com] 
Sent: Monday, August 28, 2017 1:03 PM

On Fri, Aug 25, 2017 at 10:58 PM, Csatari, Gergely (Nokia -
HU/Budapest)  wrote:
> Hi,
>
>
>
> During the week of the PTG ETSI NFV will have its plenary meeting in Denver.
> To benefit from this coincidence there will be a small workshop 
> between ETSI NFV delegates and OpenStack contributors in the PTG hotel.
>
>
>
> The workshop intends to provide a forum to identify and discuss the 
> common use cases and tasks between OpenStack and ETSI NFV and take 
> these items to the next level. The co-located workshop will be a 
> working event to discuss the gaps and requirements on both sides in 
> details and work on the technical solutions and next steps.
>
>
>
> We plan to cover the following agenda:
>
> ETSI NFV, Motivation and target, how to make things happen there 
> OpenStack, Motivation and target, how to make things happen there TST 
> 003 -> Gap analysis between ETSI NFV specifications and OpenStack 
> Collaboration via testing

Thanks Gergely for notifying this.
Ildiko also informed about this workshop in QA meeting and OpenStack QA team 
will try to join and help on this part.  Collaboration between both communities 
will be great. Myself and Andrea added our availability on etherpad.

[G0]: Okay, great.

> Introduction to the NFV PoC program and the opportunities around 
> Plugtests

I do not know the much details on this PoC program but would like to understand 
it more. In NEC, we are doing a PoC on NFV to deploy telecom app on multisite 
env with fault management and auto-scaling things. I would like to share that 
and collaborate in possible area.

[G0]: You will hear about the PoC program and the Plugtests from the best 
possible person. 

Br, 
Gerg0

>
>
>
> More detailed agenda and registration here:
> https://etherpad.openstack.org/p/etsi-nfv-openstack-gathering-denver
>
> Gaps to be discussed are here:
> https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-expla
> ined
>
> (as most probably we will not have time to cover all of them, please 
> mark with +1 the ones which are interesting to you).
>
>
>
> Also please do not forget the workshop organized on Monday around 
> similar
> topics: https://nfvwiki.etsi.org/index.php?title=ETSI_NFV_Tutorial
>
>
>
> In case of any questions do not hesitate to contact me.
>
>
>
> Br,
>
> Gerg0
>
>
>
>
> __
>  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] [vitrage] Collectd - to - Vitrage setup issues

[Afek, Ifat (Nokia - IL/Kfar Sava)]

Hi Greg,

I’m less familiar with the collectd configuration and the events that it sends.

Regarding the collectd_conf.yaml, it is definitely missing. You should add a 
/etc/vitrage/collectd_conf.yaml file that looks like that:

collectd:
- collectd_host: 
   type: 
   name: 
- collectd_host: …


This file maps a Collectd resource to the corresponding resource in OpenStack. 
Only resources that are listed in this file will have their alarms imported to 
Vitrage.

Next, you should add a reference to this file in /etc/vitrage/vitrage.conf:

[collectd]
config_file = /etc/vitrage/collectd_conf.yaml

Then you should restart vitrage-graph.

Let me know if it helped,
Ifat.


From: "Waines, Greg" 
Date: Wednesday, 23 August 2017 at 21:19

I am trying to get collectd to report some alarms to vitrage in a devstack 
setup,

I am using a devstack created on a late version of ocata.
And my devstack with vitrage appears to be working ok otherwise;
e.g.  I can create VMs, and raise fake alarms using “vitrage event post 
-type=compute.host.down ...” or with “aodh alarm create ... 
resource_id=instance-uuid” ... and they get reported fine in vitrage.

UNFORTUNATELY not seeing anything in vitrage from collectd, and
  don’t believe I’m seeing anything even from collectd, 
for example from the syslog output plugin.

I’ve attached the following files:   ( not sure if these get distributed on 
mailing list )
· /etc/collectd/collectd.conf   <-- do these look ok ?
· /etc/vitrage/vitrage.conf  <-- do these look ok ?
· /var/log/syslog ... around the time when I updated 
collectd.conf and vitrage.conf and restarted collectd and vitrage-graph
oQUESTIONS
•  NOTE THE FOLLOWING ERRORS IN THE SYSLOG FILE ... where do I get the 
collectd_conf.yaml file from ?  Can’t see it in the devstack files for vitrage.
· Aug 23 14:09:31 localhost vitrage-graph[25962]: 2017-08-23 
14:09:31.039 25962 ERROR vitrage.utils.file [-] File doesn't exist: 
/etc/vitrage/collectd_conf.yaml.
· Aug 23 14:09:31 localhost vitrage-graph[25962]: 2017-08-23 
14:09:31.040 25962 ERROR vitrage.datasources.collectd.driver [-] failed in init 
'NoneType' object has no attribute '__getitem__' : TypeError: 'NoneType' object 
has no attribute '__getitem__'
· Aug 23 14:09:31 localhost vitrage-graph[25962]: 2017-08-23 
14:09:31.040 25962 ERROR vitrage.datasources.collectd.driver Traceback (most 
recent call last):
· Aug 23 14:09:31 localhost vitrage-graph[25962]: 2017-08-23 
14:09:31.040 25962 ERROR vitrage.datasources.collectd.driver   File 
"/opt/stack/vitrage/vitrage/datasources/collectd/driver.py", line 65, in 
_configuration_mapping
· Aug 23 14:09:31 localhost vitrage-graph[25962]: 2017-08-23 
14:09:31.040 25962 ERROR vitrage.datasources.collectd.driver 
collectd_config_elements = collectd_config[COLLECTD_DATASOURCE]
· Aug 23 14:09:31 localhost vitrage-graph[25962]: 2017-08-23 
14:09:31.040 25962 ERROR vitrage.datasources.collectd.driver TypeError: 
'NoneType' object has no attribute '__getitem__'
· Aug 23 14:09:31 localhost vitrage-graph[25962]: 2017-08-23 
14:09:31.040 25962 ERROR vitrage.datasources.collectd.driver
•
•  IT DOESN”T SEEM LIKE collectd is actually getting any events anyways ... 
shouldn’t I see some collectd events being reported in /var/log/syslog from 
some of the monitoring plugins that are loaded ?
· gregs-air:collectd-info gregwaines$ fgrep "localhost collectd" syslog
· Aug 23 13:56:07 localhost collectd[23267]: supervised by systemd, 
will signal readyness
· Aug 23 13:56:07 localhost collectd[23267]: Initialization complete, 
entering read-loop.
· Aug 23 13:56:07 localhost collectd[23267]: rrdtool plugin: Adjusting 
"RandomTimeout" to 0.000 seconds.
· Aug 23 14:09:05 localhost collectd[23267]: Exiting normally.
· Aug 23 14:09:05 localhost collectd[23267]: collectd: Stopping 5 read 
threads.
· Aug 23 14:09:05 localhost collectd[23267]: rrdtool plugin: Shutting 
down the queue thread.
· Aug 23 14:09:05 localhost collectd[23267]: collectd: Stopping 5 write 
threads.
· Aug 23 14:09:07 localhost collectd[25824]: supervised by systemd, 
will signal readyness
· Aug 23 14:09:07 localhost collectd[25824]: Initialization complete, 
entering read-loop.
· Aug 23 14:09:07 localhost collectd[25824]: rrdtool plugin: Adjusting 
"RandomTimeout" to 0.000 seconds.
·
· /etc/vitrage/templates/host_down_scenarios.yaml
· /etc/vitrage/templates/host_high_cpu_load_scenarios.yaml
oAm I suppose to have some templates that are specific to the collectd 
events/alarms that are being reported to vitrage ?

Any other suggestions on things to look at in order to understand what’s wrong ?

Greg.


__
OpenStack Development Mailing List (not for 

Re: [openstack-dev] [oslo][oslo.messaging] Proposing Andy Smith as an oslo.messaging core reviewers

[ChangBo Guo]

There is no objection during last two weeks,  added Andy Smith as
oslo.message core reviewer
Welcome Andy !

2017-08-16 23:06 GMT+08:00 Ken Giusti :

> +1
>
> On Mon, Aug 14, 2017 at 6:59 AM, ChangBo Guo  wrote:
>
>> I propose that we add Andy Smith to the oslo.messaging team.
>>
>> Andy Smith has been actively contributing to oslo.messaging for a while
>> now, both
>> in helping make oslo.messaging better via code contribution(s) and by
>> helping with
>> the review load when he can. He's been involved on the AMQP 1.0 side for
>> awhile. He's really interested in taking ownership of the experimental
>> Kafka driver, which would be great to have someone able to drive that.
>>
>> Please respond with +1/-1
>>
>> Voting will last 2 weeks and will end at 28th of August.
>>
>> Cheers,
>> --
>> ChangBo Guo(gcb)
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Ken Giusti  (kgiu...@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
>
>


-- 
ChangBo Guo(gcb)
__
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] [TripleO] CI design session at the PTG

[David Moreau Simard]

Hi,

(cc whom I would at least like to attend)

The PTG would be a great opportunity to talk about CI design/layout
and how we see things moving forward in TripleO with Zuul v3, upstream
and in review.rdoproject.org.

Can we have a formal session on this scheduled somewhere ?

David Moreau Simard
Senior Software Engineer | OpenStack RDO

dmsimard = [irc, github, twitter]

__
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] [Monasca] GridDB repository support

[witold.be...@est.fujitsu.com]

> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: Dienstag, 22. August 2017 15:50
> To: Bedyk, Witold 
> Cc: OpenStack Development Mailing List (not for usage questions)
> 
> Subject: Re: [openstack-dev] [Monasca] GridDB repository support



> We don't have any recent comparison with InfluxDB but last time we tried,
> Gnocchi was already getting faster than it. And scalable horizontally, so…


Hi Julien,

Can you give some reference to Gnocchi's performance measurements?
I have seen you presentation from the last Summit [1] but I cannot find 
information about Gnocchi's write throughput. In the issues slide you note the 
slow post API. The API responsiveness test shows that the API can handle 
correctly up to 2500 instances. You collect around 60 metrics per instance and 
use polling interval of 10 minutes. That would translate to:

2500 instances * 60 metrics/instance / 600 s = 250 metrics/s

Are these assumptions correct?

Best greetings
Witek


[1] 
https://julien.danjou.info/talks/OpenStack_Telemetry_and_the_1_Instances.pdf
__
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][nova][neutron][qa][panko][blazar]: OpenStack meets ETSI NFV workshop on 12.09.2017

[gordon chung]

> Gaps to be discussed are here:
> https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained

i added a note in etherpad but it seems you want Ceilometer (+Gnocchi if 
you need storagE) and not Panko. Panko only handles storage of events 
(more metadata focused data) while Ceilometer handles the actual 
generation of both events and metrics, the latter being the one you want 
it seems. Gnocchi is used for optimised time-series metric storage.

unfortunately, i don't believe anyone from Telemetry teams are attending 
the PTG but we can be reached on ML or #openstack-telemetry.

cheers,

-- 
gord
__
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] [os-upstream-institute][all] Get together at the PTG

[Brian Rosmaita]

Monday or Tuesday for me, too.

On Fri, Aug 25, 2017 at 10:36 AM, Ildiko Vancsa  wrote:
> Hi Training Team and All,
>
> As we have our next PTG coming up shortly I think that would be a great 
> opportunity for the team and everyone who’s interested to meet and check 
> where we are and what our future plans are. :)
>
> I would like to ask you to raise your hand by replying to this mail if you 
> will be around during the PTG week in Denver and would be interested in 
> joining. Please also indicate your availability for the week.
>
> Based on the responses we will pick a day and a time that works best for most 
> to have our gathering.
>
> Please let me know if you have any questions.
>
> Thanks and Best Regards,
> Ildikó
> (IRC: ildikov)
>
>
>
> __
> 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] [all][nova][neutron][qa][panko][blazar]: OpenStack meets ETSI NFV workshop on 12.09.2017

[Ghanshyam Mann]

On Fri, Aug 25, 2017 at 10:58 PM, Csatari, Gergely (Nokia -
HU/Budapest)  wrote:
> Hi,
>
>
>
> During the week of the PTG ETSI NFV will have its plenary meeting in Denver.
> To benefit from this coincidence there will be a small workshop between ETSI
> NFV delegates and OpenStack contributors in the PTG hotel.
>
>
>
> The workshop intends to provide a forum to identify and discuss the common
> use cases and tasks between OpenStack and ETSI NFV and take these items to
> the next level. The co-located workshop will be a working event to discuss
> the gaps and requirements on both sides in details and work on the technical
> solutions and next steps.
>
>
>
> We plan to cover the following agenda:
>
> ETSI NFV, Motivation and target, how to make things happen there
> OpenStack, Motivation and target, how to make things happen there
> TST 003 -> Gap analysis between ETSI NFV specifications and OpenStack
> Collaboration via testing

Thanks Gergely for notifying this.
Ildiko also informed about this workshop in QA meeting and OpenStack
QA team will try to join and help on this part.  Collaboration between
both communities will be great. Myself and Andrea added our
availability on etherpad.

> Introduction to the NFV PoC program and the opportunities around Plugtests

I do not know the much details on this PoC program but would like to
understand it more. In NEC, we are doing a PoC on NFV to deploy
telecom app on multisite env with fault management and auto-scaling
things. I would like to share that and collaborate in possible area.

>
>
>
> More detailed agenda and registration here:
> https://etherpad.openstack.org/p/etsi-nfv-openstack-gathering-denver
>
> Gaps to be discussed are here:
> https://etherpad.openstack.org/p/ptg-denver-etsi-nfv-tst003-gaps-explained
>
> (as most probably we will not have time to cover all of them, please mark
> with +1 the ones which are interesting to you).
>
>
>
> Also please do not forget the workshop organized on Monday around similar
> topics: https://nfvwiki.etsi.org/index.php?title=ETSI_NFV_Tutorial
>
>
>
> In case of any questions do not hesitate to contact me.
>
>
>
> Br,
>
> Gerg0
>
>
>
>
> __
> 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] [nova] Proposing Balazs Gibizer for nova-core

[Sean Dague]

On 08/22/2017 09:18 PM, Matt Riedemann wrote:
> I'm proposing that we add gibi to the nova core team. He's been around
> for awhile now and has shown persistence and leadership in the
> multi-release versioned notifications effort, which also included
> helping new contributors to Nova get involved which helps grow our
> contributor base.
> 
> Beyond that though, gibi has a good understanding of several areas of
> Nova, gives thoughtful reviews and feedback, which includes -1s on
> changes to get them in shape before a core reviewer gets to them,
> something I really value and look for in people doing reviews who aren't
> yet on the core team. He's also really helpful with not only reporting
> and triaging bugs, but writing tests to recreate bugs so we know when
> they are fixed, and also works on fixing them - something I expect from
> a core maintainer of the project.
> 
> So to the existing core team members, please respond with a yay/nay and
> after about a week or so we should have a decision (knowing a few cores
> are on vacation right now).
> 

+1

-- 
Sean Dague
http://dague.net

__
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] [classifier] Asking for feedback regarding Classification Types

[Duarte Cardoso, Igor]

Hi Neutron,

The CCF team has been discussing what protocols should be supported on the 
first version of the CCF (Common Classification Framework).

A potential list exhaustive list is available at [1]. However, this is likely 
overkill in terms of protocols that will actually be used for classification 
purposes at the API layer in Neutron (Neutron Stadium).

So think of this mail as a call for protocols that definitely have to be 
implemented in the CCF so that interested services/projects can consume from it.

If you have any other comments or important information, definitely let us know.

[1] 
https://github.com/openstack/neutron-lib/blob/99d4f1f35f8d915f48bfaa677f690b29bc4b0dbe/neutron_lib/constants.py#L176-L198
CCF: https://wiki.openstack.org/wiki/Neutron/CommonClassificationFramework

Best regards,
Igor D.C.

__
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] [ironic]user image boot error

[王俊]

Hi:
 I created a new centos image by diskimage-builder，it canbe installed 
in node successful and worked well.After that, I used an image which worked 
very well on KVM  instead  of it, and the new image was created by 
virt-builder, but the node system can’t boot.The Dracut log is like this:
> Dracut-initqueue:Warning: Dracut-initqueue timeout �C starting timeout scripts
> Dracut-initqueue:warning: could not boot
> Dracut-initqueue:warning:/dev/disk/by-uuid/xxx--xxx does not exist.

What’s wrong in these steps?

保密：本函仅供收件人使用，如阁下并非抬头标明的收件人，请您即刻删除本函，勿以任何方式使用及传播，并请您能将此误发情形通知发件人，谢谢！
__
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] [ironic] PTG planning etherpad

[Dmitry Tantsur]

Hi all!

You have just a few more hours to propose your topics to 
https://etherpad.openstack.org/p/ironic-queens-ptg, please do it *right now*. I 
cannot guarantee that we accept your topic afterwards.


Also please do vote for dinner date options today as well: 
https://doodle.com/poll/nvavg9ab9ebq2e4v. We will need some time to do the 
booking in advance.


On 08/21/2017 08:00 PM, Dmitry Tantsur wrote:

A reminder that the PTG is coming :)

We have only two Mondays left, and Sep 4th is apparently a holiday in the US. 
That means we have to more or less decide on the schedule next Monday, Aug 28th. 
Please add your ideas by that time!


On 07/28/2017 12:19 PM, Dmitry Tantsur wrote:

Hi all!

It was already announced on the meeting, but not on the ML.
Here is our planning etherpad for the PTG:
https://etherpad.openstack.org/p/ironic-queens-ptg

Please check "The Rules" section before proposing a topic. Please also add 
yourself to the list of potential attendees in the bottom.


Thanks





__
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] Request to delete some unused pages from OpenStack wiki

[Thierry Carrez]

Chen Ying wrote:
> The name of the project data protection as a service has been
> changed to Karbor for a long time. 
> The name smuag is no longer needed. So some pages about smaug could be
> deleted from OpenStack wiki.
> But I don't have permissions. Hope that these pages[1] could be deleted
> by anyone who has the 
> administrator permissions to the wiki. Thanks.

Done!

-- 
Thierry Carrez (ttx)

__
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