Re: [openstack-dev] [releases]pike release notes missing in Tricircle

[joehuang]

Not an issue.

Just found that the patch needs to be approved by reviewer(s), it's not merged 
automatically.

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 18 August 2017 8:47
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev][releases]pike release notes missing in Tricircle

Hello,

The patch to update the reno( https://review.openstack.org/#/c/494565/ ) has 
been merged after Tricircle stable/pike branch is created, and the 
gate-tricircle-releasenotes
 also worked fine, but the pike release notes is missing in 
https://docs.openstack.org/releasenotes/tricircle/

I found that pike release notes are visible both in Nova/Cinder project 
(https://docs.openstack.org/releasenotes/cinder/  
https://docs.openstack.org/releasenotes/nova/)

Is there something need to do to make pike release notes appearing in the site?

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing 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] Admin dashboard instances index page generated duplicate Glance requests

[Xiong, Huan]

> This may be a bug; I recall it was patched recently and perhaps the same logic
> needs to be applied to the Admin view. It sounds like an oversight.

Thanks, Rob. I filed 1711486. What you mentioned is probably df194c8b.
It added code in Admin dashboard instance index view class to retrieve
image objects, but didn't use them to set instances' image attribute.

Thanks,
Ray

>
> Rob
>
> > On 14 Aug 2017, at 03:46, Xiong, Huan 
> wrote:
> >
> > Hi,
> >
> > I observed accessing Admin dashboard's instance index page generated
> lots of duplicate requests to Glance for converting instance image id to name,
> but accessing Project dashboard's instance index page didn't (my system
> runs Newton, but from what I can tell, Ocata and Pike code seem to have
> same issue).
> >
> > I looked at the code and found the reason. In Project dashboard's instance
> index view class, it first calls Glance's API to get a list of image objects, 
> then
> iterates through instance objects and sets each instance's image attribute to
> corresponding image object. As a result, when instance object's
> image_name() is called later, it gets name from image object. In Admin
> dashboard's instance index view class, however, it doesn't do this and hence
> needs to send request to Glance everytime image_name() is called.
> >
> > I wonder why Admin dashboard's instance index view class doesn't use the
> same approach as Project dashboard? Is it intended?
> >
> > Thanks,
> > Ray
> >
> >
> >
> > This email is intended only for the named addressee. It may contain
> information that is confidential/private, legally privileged, or copyright-
> protected, and you should handle it accordingly. If you are not the intended
> recipient, you do not have legal rights to retain, copy, or distribute this 
> email
> or its contents, and should promptly delete the email and all electronic 
> copies
> in your system; do not retain copies in any media. If you have received this
> email in error, please notify the sender promptly. Thank you.
> >
> >
> >
> >
> __
> 
> >  OpenStack Development Mailing 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



This email is intended only for the named addressee. It may contain information 
that is confidential/private, legally privileged, or copyright-protected, and 
you should handle it accordingly. If you are not the intended recipient, you do 
not have legal rights to retain, copy, or distribute this email or its 
contents, and should promptly delete the email and all electronic copies in 
your system; do not retain copies in any media. If you have received this email 
in error, please notify the sender promptly. Thank you.


__
OpenStack Development Mailing 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] [Horizon] How to monitor and visualize resource utilization after removal of Ceilometer code?

[Ran Lu]

Hi guys,

I am trying to find some precedents as guidance so that I can use
Gnocchi to monitor and visualize CPU, memory and other metrics in real
time. I assumed that Horizon is the right place to look at. But I
learned that Ceilometer code has been deprecated and removed from
Horizon, with no easily accessible explanation in the commit message
[1]. Is there any explanation regarding to the removal of Ceilometer
from Horizon? And how can Horizon monitor resource utilization
dynamically without Ceilometer?

Thanks & Regards,

Ran Lu.

[1].
https://github.com/openstack/horizon/commit/20ea82b9efe78516286c4b35c5dc644b296b4313



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

[openstack-dev] [releases]pike release notes missing in Tricircle

[joehuang]

Hello,

The patch to update the reno( https://review.openstack.org/#/c/494565/ ) has 
been merged after Tricircle stable/pike branch is created, and the 
gate-tricircle-releasenotes
 also worked fine, but the pike release notes is missing in 
https://docs.openstack.org/releasenotes/tricircle/

I found that pike release notes are visible both in Nova/Cinder project 
(https://docs.openstack.org/releasenotes/cinder/  
https://docs.openstack.org/releasenotes/nova/)

Is there something need to do to make pike release notes appearing in the site?

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing 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] Multi-region support in shared Keystone service deployment

[Lingxian Kong]

Thanks, Rob, blueprint is proposed here:
https://blueprints.launchpad.net/horizon/+spec/horizon-multi-region-support


Cheers,
Lingxian Kong (Larry)

On Thu, Aug 17, 2017 at 11:05 PM, Rob Cresswell (rcresswe) <
rcres...@cisco.com> wrote:

> As I mentioned the last time you asked :), we use blueprints, and the
> template is here: https://blueprints.launchpad.net/horizon/+spec/template
>
> Please register a blueprint for discussion / tracking. The change looks
> sensible, although I’d prefer we use a setting name like
> https://docs.openstack.org/horizon/latest/configuration/settings.html#
> openstack-keystone-domain-choices. It’s a bit less ambiguous.
>
> Rob
>
>
>
> On 16 Aug 2017, at 23:03, Lingxian Kong  wrote:
>
> Hi, Horizon developers,
>
> In our OpenStack based public cloud(Catalyst Cloud), Keystone is a shared
> identity service across 3 regions, our customers have been asking for the
> feature that they could select their preferred region when they log in
> Horizon, rather than switching region each time after login.
>
> Unfortunately, the existing 'AVAILABLE_REGIONS' only works with
> multi-keystone, multi-region environment, so for backward compatibility and
> getting rid of potential confusion, a new config option named
> 'AVAILABLE_SERVICE_REGIONS' was introduced in my patch[1][2], the setting
> is supposed to be configured by the cloud operators and the
> 'AVAILABLE_REGIONS' setting will take precedence over
> 'AVAILABLE_SERVICE_REGIONS'.
>
> I am sending this email to ask for more feedback, and do I need to propose
> a feature spec before the code is actually being reviewed?
>
> [1]: https://review.openstack.org/#/c/494083/
> [2]: https://review.openstack.org/#/c/494059/
>
> Cheers,
> Lingxian Kong (Larry)
> __
> OpenStack Development Mailing 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] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG

[David Moreau Simard]

Happy to join in case my perspective from infra and RDO can be useful!

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]

On Aug 17, 2017 10:32 AM, "Emilien Macchi"  wrote:

> Hey folks,
>
> As usual, we'll meet in Denver and I hope we can spend some time
> together (in a meeting room first) to have face to face discussions on
> the recent topics that we had.
> Right now, TripleO sessions are not scheduled in our agenda, so we're
> pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens
>
> I would like to propose one topic (happy to coordinate the discussion)
> on some efforts regarding doing configuration management with Ansible,
> and k8s integration as well.
> Flavio made some progress [1] - I really hope we can make progress here.
>
> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-
> July/119696.html
>
> If you're working on Kolla / OpenStack-Ansible - please let us know if
> you have specific constraints on the schedule, so we can maybe block a
> timeslot in the agenda from now.
> We'll have a "Packaging" room which is reserved for all topics related
> to OpenStack deployments, so we can use this one.
>
> Looking forward to meeting you at PTG!
> 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 Development Mailing 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] Expected VLAN (not received): Deploy OpenStack Via Fuel

[Vichord Wong]

Hi All,


Greetings!


I need some help on deploying OpenStack using Fuel.


I tried to install and deploy openstack on three HP servers, each of them 
consists of 1 CPU with 4 physical cores, 16 GB memory, 500G hard disk, and one 
physical NIC

Server 1: install fuel

Server 2: Ubuntu bootstrap --- discovered by fuel and added as a controller

Server 3: Ubuntu bootstrap --- discovered by fuel and added as a compute node


These servers are plugged into Cisco Linksys E2500 Router.


When I tried to verify the network it always failed at "Expected VLAN (not 
received)". Inside a table, a bunch of VLAN IDs are listed under "Expected VLAN 
(not received)".

For example: 1024, 1026, 1027,1028, 1029, 1030, 1025, 101, 102, 1000, 1001, 
1002, 1003, 1004, 1005, 1006,1007, 1008, 1009, 1010, 1011, 1012, 1013, 1014, 
1015, 1016, 1017, 1018, 1019, 1020, 1021, 1022, 1023.


Could you let me know what causes this issue and how I can fix this problem?


Thanks a lot.


Regards,

Song


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

Re: [openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG

[Jean-Philippe Evrard]

I'd be happy to join.

I don't think we have constraints on the schedule yet, and we can indeed
book slot(s).

Best regards,
JP.

On Thu, Aug 17, 2017 at 3:30 PM, Emilien Macchi  wrote:

> Hey folks,
>
> As usual, we'll meet in Denver and I hope we can spend some time
> together (in a meeting room first) to have face to face discussions on
> the recent topics that we had.
> Right now, TripleO sessions are not scheduled in our agenda, so we're
> pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens
>
> I would like to propose one topic (happy to coordinate the discussion)
> on some efforts regarding doing configuration management with Ansible,
> and k8s integration as well.
> Flavio made some progress [1] - I really hope we can make progress here.
>
> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-
> July/119696.html
>
> If you're working on Kolla / OpenStack-Ansible - please let us know if
> you have specific constraints on the schedule, so we can maybe block a
> timeslot in the agenda from now.
> We'll have a "Packaging" room which is reserved for all topics related
> to OpenStack deployments, so we can use this one.
>
> Looking forward to meeting you at PTG!
> 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 Development Mailing 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] [requirements] Unfreezing of the requirements repo

[Tony Breeds]

On Thu, Aug 17, 2017 at 04:47:14PM -0500, Matthew Thode wrote:
> Hi all,
> 
> It's time to unfreeze the requirements repo.
> 
> For projects that have branched (most everyone at this point) this
> won't be a change.
> 
> For projects that have yet to branch, you will need to look out for
> and block global requirements bot updates until you've branched.
> You will also need to look out for test failures in your gating as you
> mau be pulling in master (queens) upper-constraints instead of pike.
> The workaround for this is to change your tox.ini temporarilly to target
> the pike branch for fetching the upper-constraints.txt file.  It'd be
> better to just branch if you can though.

That won't work.  As the gate doesn't use that URL is copy's the file
from the requirements repo from the same branch into the projects
workspace.  See the various run-*.sh scripts like:
 
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/run-tox.sh#n119

So if a constraints update on master breaks your prep for pike please
reach out quickly to the requirements team.

Yours Tony.


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

[openstack-dev] [requirements] Unfreezing of the requirements repo

[Matthew Thode]

Hi all,

It's time to unfreeze the requirements repo.

For projects that have branched (most everyone at this point) this
won't be a change.

For projects that have yet to branch, you will need to look out for
and block global requirements bot updates until you've branched.
You will also need to look out for test failures in your gating as you
mau be pulling in master (queens) upper-constraints instead of pike.
The workaround for this is to change your tox.ini temporarilly to target
the pike branch for fetching the upper-constraints.txt file.  It'd be
better to just branch if you can though.

If you have questions, feel free to reach out to me on irc
(prometheanfire on freenode, #openstack-requirements for the channel) or
email.

-- 
Matthew Thode (prometheanfire)


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

[openstack-dev] No drivers meeting today

[Kevin Benton]

Hi everyone,

I'm canceling the drivers meeting today to allow everyone to focus on fixes
for Pike.

Let me or Armando know right away if you have have any fixes that need to
go into RC2 since he has prepared the RC2 release patch already.

Cheers,
Kevin Benton
__
OpenStack Development Mailing 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] Nova user cannot connect to MYSQL DB

[wahi]

Dear all,

I am deploying Openstack using MAAS-JUJU, I am trying to deploy each 
service one-by-one and build the relation between them, everything is ok 
except that the nova-controller cannot connect to MYSQL db, the DB and 
the controller are on the same host.


I am getting this error from the log:

hook failed: "shared-db-relation-changed:" for mysql:shared-db"

I binded the VM IP to
mysql and granted the user nova to access the mysql with the
auto-generated password. I did the same step for glance and keystone and 
it worked without any problem.


Could you please help me to understand what is the problem ? and how can 
I solve it ?


Thank you very much in advance.


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

[openstack-dev] [all] purplerbot briefly broken

[Chris Dent]

If you don't know what purplerbot is, you can stop reading if you
don't care. If you do see: https://anticdent.org/purple-irc-bot.html

Because I was lazy, I never registered the purplerbot nick with
freenode. Sometime in the recent past freenode made it so that you
had to be a registered nick in order to be able to send private
messages to at least some and maybe all users.

This meant that commands like `p!spy openstack-nova` (that and
additional commands explained in the link above) would result in
no output, no error message, nothing. The bot's server side error
log clued me in and it is now fixed.

If you've now read this and the blog posting and think "hey, I
want purplerbot in my channel", please let me know.

--
Chris Dent  (⊙＿⊙') https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing 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][api] POST /api-sig/news

[michael mccune]

Greetings OpenStack community,

This week's meeting centered around two main topics; the Guided Review 
Process[0] and the inclusion of guidance to discourage extension 
usage[4]. As the working group has now become a Special Interest Group, 
we have begun the work of changing the documentation and infra services 
over to use the new naming (with many thanks to Ed Leafe).


The Guided Review Process document has been accepted by the SIG as a 
document describing an activity that we will be hosting at PTG events, 
and also as requested by teams. Emails will be sent out this week to all 
the project PTLs with instructions about the review process and how they 
can be prepared to participate at the Queens PTG. If you have not seen 
this document yet, you can find it in the review[0], or on the API-SIG 
specs site[2] once it is redeployed.


Work on the guidance to discourage extension usage[4] continues and 
there have been some comments by members of the community to help drive 
this process along. This topic continues to be a tricky discussion, but 
the SIG is making progress in defining a guideline that will be ready 
for community approval. As with last week, we still haven't fully 
decided how these issues will be explained, but we are getting closer 
and continue to hold the ideal that extension URIs are not helpful for 
creating interoperable APIs.


On the topic of the PTG, there was some minor discussion about what we 
will be talking about beyond guided reviews but this is still in the 
nascent stages. Stay tuned for more information about the API-SIG PTG 
events.


# Newly Published Guidelines

None this week.

# API Guidelines Proposed for Freeze

Guidelines that are ready for wider review by the whole community.

None this week

# Guidelines Currently Under Review [3]

* Explain, simply, why extensions are bad
  https://review.openstack.org/#/c/491611/

* A (shrinking) suite of several documents about doing version and 
service discovery

  Start at https://review.openstack.org/#/c/459405/

* WIP: microversion architecture archival doc (very early; not yet ready 
for review)

  https://review.openstack.org/444892

# Highlighting your API impacting issues

If you seek further review and insight from the API WG, please address 
your concerns in an email to the OpenStack developer mailing list[1] 
with the tag "[api]" in the subject. In your email, you should include 
any relevant reviews, links, and comments to help guide the discussion 
of the specific challenge you are facing.


To learn more about the API WG mission and the work we do, see OpenStack 
API Working Group [2].


Thanks for reading and see you next week!

# References

[0] https://review.openstack.org/#/c/487847/
[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[2] http://specs.openstack.org/openstack/api-wg/
[3] 
https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z

[4] https://review.openstack.org/#/c/491611/


Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg

__
OpenStack Development Mailing 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] pike release

[Julia Kreger]

Greetings everyone!

As some of you may have noticed, we released ironic 9.0.0 today. But
wait! There is more!

We triggered this release due to a number of issues, one of which was
that we learned that we needed the stable/pike branch for our grenade
jobs to execute properly. This was not done previously because
Ironic’s release model is incompatible with making release candidate
releases.

Once we’ve confirmed that our grenade testing is passing, we will back
port patches we had previously approved, but that had not landed, from
master to stable/pike.

As a result, please anticipate Ironic’s official Pike release for this
cycle to be 9.1.0, if the stars, gates, and job timeouts align with
us.

If there are any questions, please feel free to stop by
#openstack-ironic. We have also been keeping our general purpose
whiteboard[1] up to date, you can see our notes regarding our current
plan starting at line 120, and notes regarding gate failures and
issues starting at line 37.
Thanks!

-Julia

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

__
OpenStack Development Mailing 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] Redhat overcloud node's introspection failing with timeout

[Paras pradhan]

First thing I would check is if the overcloud nodes are booting from pxe or
not.

-Paras.

On Thu, Aug 17, 2017 at 11:07 AM, Shyam Biradar <
shyambiradarsgg...@gmail.com> wrote:

> Hi,
>
> RedHat introspection is failing with timeout error.
>
> I have deployed undercloud and overcloud nodes as VMs on an ESX node and
> using fake_pxe driver for power management.
> I am managing power status of nodes manually.
>
> More details are, during introspection ironic-introspector is not able to
> add MAC address entry to iptables. From documentation it seems that it
> should add.
>
> [stack@redhat-undercloud ~]$ sudo iptables -L ironic-inspector
> Chain ironic-inspector (1 references)
> target prot opt source   destination
> ACCEPT all  --  anywhere anywhere
>
>
> Here are the snap of introspector logs:
> 
> --
>
> Aug 17 12:01:27 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:27.818 15329 INFO werkzeug [-]
> 11.11.0.1 - - [17/Aug/2017 12:01:27] "GET 
> /v1/introspection/cac58c65-6605-4963-bf75-428295dea0b8
> HTTP/1.1" 200 -
> Aug 17 12:01:31 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:31.664 15329 DEBUG
> futurist.periodics [-] Submitting periodic function
> 'ironic_inspector.main.periodic_update' _process_scheduled
> /usr/lib/python2.7/site-packages/futurist/periodics.py:614
> Aug 17 12:01:31 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:31.687 15329 DEBUG
> ironic_inspector.firewall [-] *Not updating iptables - no changes in MAC
> list set([]) update_filters
> /usr/lib/python2.7/site-packages/ironic_inspector/firewall.py:190*
> Aug 17 12:01:37 redhat-undercloud.triliodata.demo
> ironic-inspector[15329]: 2017-08-17 12:01:37.838 15329 INFO werkzeug [-]
> 11.11.0.1 - - [17/Aug/2017 12:01:37] "GET 
> /v1/introspection/cac58c65-6605-4963-bf75-428295dea0b8
> HTTP/1.1" 200
> 
> --
>
> No other error found in logs.
>
> Any suggestions are welcome.
>
>
> Thanks & Regards,
> Shyam Biradar,
> Email: shyambiradarsgg...@gmail.com,
> Contact: +91 8600266938 <+91%2086002%2066938>.
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [neutron] Call for help with in-tree tempest scenario test failures

[Anil Venkata]

I will work on DVR+HA migration jobs.

Thanks
Anilvenkata

On Fri, Aug 11, 2017 at 2:40 AM, Sławek Kapłoński 
wrote:

> Hello,
>
> I’m still checking this QoS scenario test and I found something strange
> IMHO.
> For example, almost all failed tests from last 2 days were executed on
> nodes with names like:
> * ubuntu-xenial-2-node-citycloud-YYY- - on those nodes almost (or
> even all) all scenario tests was failed due to failed SSH connection to
> instance,
> * ubuntu-xenial-2-node-rax-iad- - on those nodes QoS test was failed
> because of timeout during reading data
>
> I’m noob in gate tests and how it’s exactly working so my conclusions can
> be completely wrong but maybe those issues are related somehow to some
> cloud providers which provides infrastructure for tests?
> Maybe someone more experienced could take a look on that and help me? Thx
> in advance.
>
> —
> Best regards
> Slawek Kaplonski
> sla...@kaplonski.pl
>
>
>
>
> > Wiadomość napisana przez Ihar Hrachyshka  w dniu
> 03.08.2017, o godz. 23:40:
> >
> > Thanks for those who stepped in (Armando and Slawek).
> >
> > We still have quite some failures that would benefit from initial log
> > triage and fixes. If you feel like in this feature freeze time you
> > have less things to do, helping with those scenario failures would be
> > a good way to contribute to the project.
> >
> > Thanks,
> > Ihar
> >
> > On Fri, Jul 28, 2017 at 6:02 AM, Sławek Kapłoński 
> wrote:
> >> Hello,
> >>
> >> I will try to check QoS tests in this job.
> >>
> >> —
> >> Best regards
> >> Slawek Kaplonski
> >> sla...@kaplonski.pl
> >>
> >>
> >>
> >>
> >>> Wiadomość napisana przez Jakub Libosvar  w dniu
> 28.07.2017, o godz. 14:49:
> >>>
> >>> Hi all,
> >>>
> >>> as sending out a call for help with our precious jobs was very
> >>> successful last time and we swept all Python 3 functional from Neutron
> >>> pretty fast (kudos the the team!), here comes a new round of failures.
> >>>
> >>> This time I'm asking for your help  >>> poster here> with gate-tempest-dsvm-neutron-dvr-multinode-scenario
> >>> non-voting job. This job has been part of check queue for a while and
> is
> >>> very very unstable. Such job covers scenarios like router dvr/ha/legacy
> >>> migrations, qos, trunk and dvr. I went through current failures and
> >>> created an etherpad [1] with categorized failures and logstash queries
> >>> that give you latest failures with given particular tests.
> >>>
> >>> If you feel like doing troubleshooting and sending fixes for gates,
> >>> please pick one test and write down your name to the test.
> >>>
> >>> Thanks to all who are willing to participate.
> >>>
> >>> Have a great weekend.
> >>> Jakub
> >>>
> >>>
> >>> [1]
> >>> https://etherpad.openstack.org/p/neutron-dvr-multinode-
> scenario-gate-failures
> >>>
> >>>
> >>> 
> __
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [barbican] [security] custodia @ PTG

[Luke Hinds]

Hi Raildo,

That's great news. Are you around next Thursday to jump on
#openstack-meeting-alt at 17:00 UTC? we can then go over some topics.

@Dave, unless you prefer to use the Barbican meeting that is (possible
synergies to barbican)?

Regards,

Luke

On Thu, Aug 17, 2017 at 1:10 PM, Raildo Mascena de Sousa Filho <
rmasc...@redhat.com> wrote:

> Hi Luke,
>
> I'll definitely be there, sounds like a great idea, so we can clarify a
> lot of topics and make progress in the community together.
>
> Cheers,
>
>
> On Thu, Aug 17, 2017 at 5:52 AM Luke Hinds  wrote:
>
>> Hi Raildo,
>>
>> Both Barbican and Security have an interest in custodia and we have it
>> marked down as a topic / discussion point for the PTG [1]
>>
>> Would you be interested / willing to join the Barbican room on Thurs /
>> Fri and propose a walk through / overview etc?
>>
>> [1] https://etherpad.openstack.org/p/barbican-ptg-queens
>>
>>
>> Regards,
>>
>> Luke
>>
> --
>
> Raildo mascena
>
> Software Engineer, Identity Managment
>
> Red Hat
>
> 
> 
> TRIED. TESTED. TRUSTED. 
>



-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
__
OpenStack Development Mailing 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] critical situation with CI / upgrade jobs

[Jiří Stránský]

On 17.8.2017 00:47, Emilien Macchi wrote:

Here's an update on the situation.

On Tue, Aug 15, 2017 at 6:33 PM, Emilien Macchi  wrote:

Problem #1: Upgrade jobs timeout from Newton to Ocata
https://bugs.launchpad.net/tripleo/+bug/1702955

[...]

- revert distgit patch in RDO: https://review.rdoproject.org/r/8575
- push https://review.openstack.org/#/c/494334/ as a temporary solution
- we need https://review.openstack.org/#/c/489874/ landed ASAP.
- once https://review.openstack.org/#/c/489874/ is landed, we need to
revert https://review.openstack.org/#/c/494334 ASAP.

We still need some help to find out why upgrade jobs timeout so much
in stable/ocata.


Problem #2: from Ocata to Pike (containerized) missing container upload step
https://bugs.launchpad.net/tripleo/+bug/1710938
Wes has a patch (thanks!) that is currently in the gate:
https://review.openstack.org/#/c/493972

[...]

The patch worked and helped! We've got a successful job running today:
http://logs.openstack.org/00/461000/32/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/2f13627/console.html#_2017-08-16_01_31_32_009061

We're now pushing to the next step: testing the upgrade with pingtest.
See https://review.openstack.org/#/c/494268/ and the Depends-On: on
https://review.openstack.org/#/c/461000/.

If pingtest proves to work, it would be a good news and prove that we
have a basic workflow in place on which we can iterate.

The next iterations afterward would be to work on the 4 scenarios that
are also going to be upgrades from Ocata to pike (001 to 004).
For that, we'll need Problem #1 and #2 resolved before we want to make
any progress here, to not hit the same issues that before.


Problem #3: from Ocata to Pike: all container images are
uploaded/specified, even for services not deployed
https://bugs.launchpad.net/tripleo/+bug/1710992
The CI jobs are timeouting during the upgrade process because
downloading + uploading _all_ containers in local cache takes more
than 20 minutes.
So this is where we are now, upgrade jobs timeout on that. Steve Baker
is currently looking at it but we'll probably offer some help.


Steve is still working on it: https://review.openstack.org/#/c/448328/
Steve, if you need any help (reviewing or coding) - please let us
know, as we consider this thing important to have and probably good to
have in Pike.


Independent, but related issue is that the job doesn't make use of 
CI-local registry mirrors. I seem to recall we already had mirror usage 
implemented at some point, but we must have lost it somehow. Fix is here:


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

Jirka



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

[openstack-dev] [glance] priorities for THURSDAY (17 aug) and FRIDAY (18 aug)

[Brian Rosmaita]

Glancers (and other people interested in the Pike release of Glance),

We need a RC-2, and the sooner we can release it, the better.  So we really
need a review push today and tomorrow.

Glance cores: please direct your attention to the patches listed on this
etherpad:
https://etherpad.openstack.org/p/glance-pike-RC-critical
They are mostly related to the new interoperable image import functionality.

Abhishek and I can only +2 each others work, and Erno is on a well-deserved
vacation, so we need some more eyes on those patches.  Even if you're not a
glance core, your careful review on these patches will be helpful.

thanks,
brian
__
OpenStack Development Mailing 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] Redhat overcloud node's introspection failing with timeout

[Shyam Biradar]

Hi,

RedHat introspection is failing with timeout error.

I have deployed undercloud and overcloud nodes as VMs on an ESX node and
using fake_pxe driver for power management.
I am managing power status of nodes manually.

More details are, during introspection ironic-introspector is not able to
add MAC address entry to iptables. From documentation it seems that it
should add.

[stack@redhat-undercloud ~]$ sudo iptables -L ironic-inspector
Chain ironic-inspector (1 references)
target prot opt source   destination
ACCEPT all  --  anywhere anywhere


Here are the snap of introspector logs:

--

Aug 17 12:01:27 redhat-undercloud.triliodata.demo ironic-inspector[15329]:
2017-08-17 12:01:27.818 15329 INFO werkzeug [-] 11.11.0.1 - - [17/Aug/2017
12:01:27] "GET /v1/introspection/cac58c65-6605-4963-bf75-428295dea0b8
HTTP/1.1" 200 -
Aug 17 12:01:31 redhat-undercloud.triliodata.demo ironic-inspector[15329]:
2017-08-17 12:01:31.664 15329 DEBUG futurist.periodics [-] Submitting
periodic function 'ironic_inspector.main.periodic_update'
_process_scheduled /usr/lib/python2.7/site-packages/futurist/periodics.
py:614
Aug 17 12:01:31 redhat-undercloud.triliodata.demo ironic-inspector[15329]:
2017-08-17 12:01:31.687 15329 DEBUG ironic_inspector.firewall [-] *Not
updating iptables - no changes in MAC list set([]) update_filters
/usr/lib/python2.7/site-packages/ironic_inspector/firewall.py:190*
Aug 17 12:01:37 redhat-undercloud.triliodata.demo ironic-inspector[15329]:
2017-08-17 12:01:37.838 15329 INFO werkzeug [-] 11.11.0.1 - - [17/Aug/2017
12:01:37] "GET /v1/introspection/cac58c65-6605-4963-bf75-428295dea0b8
HTTP/1.1" 200

--

No other error found in logs.

Any suggestions are welcome.


Thanks & Regards,
Shyam Biradar,
Email: shyambiradarsgg...@gmail.com,
Contact: +91 8600266938.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [all][elections] Project Team Lead Election Conclusion and Results

[Sean McGinnis]

> 
> Elections:
> * Documentation:
> http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_d5d9fb5a2354e2a0
> * Ironic: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_0fb06bb4edfd3d08
> Election process details and results are also available here:
> https://governance.openstack.org/election/
> 
> Thank you to all involved in the PTL election process,
> 
> - Kendall Nelson(diablo_rojo)

Thank you to our election officials for running a smooth election!


__
OpenStack Development Mailing 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

[Major Hayden]

On 08/17/2017 09:30 AM, Emilien Macchi wrote:
> If you're working on Kolla / OpenStack-Ansible - please let us know if
> you have specific constraints on the schedule, so we can maybe block a
> timeslot in the agenda from now.
> We'll have a "Packaging" room which is reserved for all topics related
> to OpenStack deployments, so we can use this one.

I don't have any constraints (that I'm aware of), but I'd be interested in 
participating!  Performance in the gate jobs has been one of my tasks lately 
and I'd like to see if we can collaborate there to make improvements without 
ruining infra's day. ;)

As long as you can put up with a few Dad jokes, I'll be there.

--
Major Hayden

__
OpenStack Development Mailing 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

[Flavio Percoco]

On 17/08/17 07:30 -0700, Emilien Macchi wrote:

Hey folks,

As usual, we'll meet in Denver and I hope we can spend some time
together (in a meeting room first) to have face to face discussions on
the recent topics that we had.
Right now, TripleO sessions are not scheduled in our agenda, so we're
pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens

I would like to propose one topic (happy to coordinate the discussion)
on some efforts regarding doing configuration management with Ansible,
and k8s integration as well.
Flavio made some progress [1] - I really hope we can make progress here.

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119696.html

If you're working on Kolla / OpenStack-Ansible - please let us know if
you have specific constraints on the schedule, so we can maybe block a
timeslot in the agenda from now.
We'll have a "Packaging" room which is reserved for all topics related
to OpenStack deployments, so we can use this one.

Looking forward to meeting you at PTG!
Thanks,


Just want to raise my hand to help driving some of these conversations.

I'd love to see some sessions around collaborating with other teams. Some ideas
that we've discussed in the past could use some more discussions. For example:

- Configuration management
- Sharing playbooks with kolla
- Kubernetes based jobs
 - What's there?
 - What can be shared?

Going to add these points to the etherpad,
Flavio

--
@flaper87
Flavio Percoco


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] pike-3 released - now focusing on pike-rc1

[Emilien Macchi]

On Mon, Jul 31, 2017 at 7:26 AM, Emilien Macchi  wrote:
> ## This week until August 28th
> Preparing RC & final releases.
> Feature & CI freeze just started.
> During this time, folks should focus on upgrades from Ocata to Pike,
> fixing bugs [1].
> Please do the FFE (including CI changes) requests on openstack-dev [tripleo].

We'll tag TripleO Pike RC1 on R+O during the week of Aug 28 - Sep 01.
We still have some patches that we need in master and the CI efforts
are still ongoing to validate Pike release, so it doesn't make sense
for us to branch now.
We'll probably tag final Pike 2 weeks.

If there is any thought or question, please let us know.
-- 
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] [all] Secrets of edit-constraints

[Akihiro Motoki]

Thanks Tony for the confirmation.

We have various variants of tox_install.sh. I just wondered we need to
fix it globally
or it depends on someone's development environment.

Anyway we can improve tox_install.sh for more general way :)

Thanks,
Akihiro

2017-08-16 18:14 GMT+09:00 Tony Breeds :
> On Mon, Aug 14, 2017 at 08:36:33AM +, Csatari, Gergely (Nokia - 
> HU/Budapest) wrote:
>> Hi,
>>
>> I have an interesting situation with the parametrization of edit-constraints 
>> in tools/tox_install.sh. This happens at the moment in neutron-lib, but as 
>> amotoki pointed out in [1] the same should happen in any projects (and 
>> actually was happening with me in Vitrage and Mistral).
>>
>> Here is what I experience:
>> With the current parameters of edit-constraints (edit-constraints $localfile 
>> -- $LIB_NAME "-e file://$PWD#egg=$LIB_NAME") the library itself (neutron-lib 
>> in this case) is added to upper-constraints.txt and the installation fails 
>> with "Could not satisfy constraints for 'neutron-lib': installation from 
>> path or url cannot be constrained to a version".
>> If I modify the parameters of edit-constraints in a way that it removes the 
>> library (neutron-lib in this case) instead of adding (edit-constraints 
>> $localfile $LIB_NAME --) it my build succeeds (as I'm playing with api-ref I 
>> use tox -r -e api-ref, but the same also happens with tox -r -e pep8).
>>
>> Is this happening with only me?
>
> No using edit-constraints to remove an item from the constrained set so
> you can use the current developement (git SHA) is the right things to
> do.
>
> Many of the project in the scenario you're describing do just that.
>
> Yours Tony.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

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

[openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG

[Emilien Macchi]

Hey folks,

As usual, we'll meet in Denver and I hope we can spend some time
together (in a meeting room first) to have face to face discussions on
the recent topics that we had.
Right now, TripleO sessions are not scheduled in our agenda, so we're
pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens

I would like to propose one topic (happy to coordinate the discussion)
on some efforts regarding doing configuration management with Ansible,
and k8s integration as well.
Flavio made some progress [1] - I really hope we can make progress here.

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119696.html

If you're working on Kolla / OpenStack-Ansible - please let us know if
you have specific constraints on the schedule, so we can maybe block a
timeslot in the agenda from now.
We'll have a "Packaging" room which is reserved for all topics related
to OpenStack deployments, so we can use this one.

Looking forward to meeting you at PTG!
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] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

[Raildo Mascena de Sousa Filho]

Well, it was the first option but unfortunately, Doug doesn't have any free
time slot on those days, so we have to postpone that discussion to the end
of the week.

On Thu, Aug 17, 2017 at 9:41 AM Thierry Carrez 
wrote:

> Raildo Mascena de Sousa Filho wrote:
> > Hi all,
> >
> > Should we reserve a room in the extra session ethercalc [0
> > <%20https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms%20>] or
> > we already have a time slot scheduled for that discussion?
> >
> > [0] https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms
>
> It feels like this discussion could be scheduled in the Oslo room as
> well. I guess it depends whether you need extra room :)
>
> --
> 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
>
-- 

Raildo mascena

Software Engineer, Identity Managment

Red Hat



TRIED. TESTED. TRUSTED. 
__
OpenStack Development Mailing 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-operators] [openstack-operators][Ceilometer vs Monasca] Alarms: Ceilometer vs Monasca

[Curtis]

On Wed, Aug 16, 2017 at 6:44 AM, Krzysztof Świątek
 wrote:
> Hi,
>
> i have a question about alarms in openstack.
>
> I want autoscaling with heat, and I'm looking for metric/alarm project
> which I can use with heat.
> I found that I can use Monasca or Ceilometer (with Aodh).
> My question is:
> Is any of you using heat (autoscaling) in production?
> If yes what are you using (Monasca, Ceilometer, other) for metric and
> alarms, and why?

I don't think many people know that Monasca can be used with heat for
autoscaling, so it's good that you know. :)

That said, I think it's fairly safe to say that the most common of the
two in production for autoscaling will be ceilometer, and that is the
only one I've used in production. So, it's not to say that one is
better than the other, but rather that Ceilometer is more commonly
used. If it was me I would probably use Ceilometer unless I knew I
also wanted to provide monitoring as a service to my end users and did
not need to provide telemetry to them. Usually ceilometer is useful in
other areas, such as billing, etc.

Ceilometer and it's related systems have changed a lot recently for
the better to separate out some components into other projects like
panko and gnocchi and aodh. There are definitely retention and backend
storage type and tuning that have to be considered.

Thanks,
Curtis.

>
> --
> Pozdrawiam,
> Krzysztof Świątek
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



-- 
Blog: serverascode.com

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

[Openstack-operators] [Large Deployment Team] August Meeting Postponed a Week

[Matt Van Winkle]

Hey LDT folks,
I am sorry for the last minute notice, but due to some conflicts, I need to 
move the meeting to next week. I have already updated the wiki [1].  Any 
members that may have attended the meetup last week in Mexico City please try 
to make the meeting next week.  We would love to hear some details about the 
event.

Also, for those of you in the group that are AUC, don’t forget the voting is 
open for three User Committee seats.  Look for an email from Ed Leafe with 
voting details.  Voting ends tomorrow.

Thanks and see you next week!
VW

[1] https://wiki.openstack.org/wiki/Meetings/LDT

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

Re: [openstack-dev] [tripleo] Proposal to require bugs for tech debt

[Markus Zoeller]

On 16.08.2017 18:40, Alex Schultz wrote:
> On Wed, Aug 16, 2017 at 8:24 AM, Markus Zoeller
>  wrote:
>> On 16.08.2017 02:59, Emilien Macchi wrote:
>>> On Tue, Aug 15, 2017 at 5:46 PM, Alex Schultz  wrote:
 Hey folks,

 I'm proposing that in order to track tech debt that we're adding in as
 part of development that we create a way to track these items and not
 approve them without a bug (and a reference to said bug)[0].  Please
 take a moment to review the proposed policy and comment. I would like
 to start this for the queens cycle.
>>>
>>> I also think we should frequently review the status of these bugs.
>>> Maybe unofficially from time to time and officially during milestone-3
>>> of each cycle.
>>>
>>> I like the proposal so far, thanks.
>>>
>>
>> FWIW, for another (in-house) project, I create a page called "technical
>> debt" in the normal docs directory of the project. That way, I can add
>> the "reminder" with the same commit which introduced the technical debt
>> in the code. Similar to what OpenStack already does with the
>> release-notes. The list of technical debt items is then always visible
>> in the docs and not a query in the bug-tracker with tags (or something
>> like that).
>> Just an idea, maybe it applicable here.
>>
> 
> Yea that would a good choice if we only had a single or a low number
> of projects under the tripleo umbrella. The problem is we have many
> different components which contribute to tech debt so storing it in
> each repo would be hard to track. I proposed bugs because it would be
> a singular place for reporting. For projects with fewer deliverable
> storing it like release notes is a good option.
> 
> Thanks,
> -Alex
> 

No biggie. A single project was my implicit assumption, that's true.
Wish you good luck.

-- 
Regards, Markus Zoeller (markus_z)

>> --
>> Regards, Markus Zoeller (markus_z)
>>
 A real world example of where this would beneficial would be the
 workaround we had for buggy ssh[1]. This patch was merged 6 months ago
 to work around an issue in ssh that was recently fixed. However we
 would most likely never have remembered to revert this. It was only
 because someone[2] spotted it and mentioned it that it is being
 reverted now.

 Thanks,
 -Alex

 [0] https://review.openstack.org/#/c/494044/
 [1] 
 https://review.openstack.org/#/q/6e8e27488da31b3b282fe1ce5e07939b3fa11b2f,n,z
 [2] Thanks pabelanger



__
OpenStack Development Mailing 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.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

[Thierry Carrez]

Raildo Mascena de Sousa Filho wrote:
> Hi all,
> 
> Should we reserve a room in the extra session ethercalc [0
> <%20https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms%20>] or
> we already have a time slot scheduled for that discussion?
> 
> [0] https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms

It feels like this discussion could be scheduled in the Oslo room as
well. I guess it depends whether you need extra room :)

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

Re: [openstack-dev] [tricircle-Service Function Chaining]

[Vega Cai]

Hi Meher,

The document structure of networking-sfc has been changed so the link in
the guide is not accurate. Since you have already deployed Tricircle and
would like to enable service function chaining feature, I think you can
refer to these guides[1, 2] to setup local Neutron server. The
configuration for local Neutron server is /etc/neutron/neutron.conf
and /etc/neutron/plugins/ml2/ml2_conf.ini for the DevStack setup. And
/etc/neutron/neutron.conf.0 is the configuration file for central Neutron
server.

BTW, would you like to join our weekly meeting? The current time(9:00 am
UTC+8 on Wednesday) may not be suitable for you, but we can figure out a
proper time and rearrange the meeting.

[1] https://docs.openstack.org/networking-sfc/latest/install/install.html
[2]
https://docs.openstack.org/networking-sfc/latest/install/configuration.html

BR
Zhiyuan

On Thu, 17 Aug 2017 at 18:10  wrote:

> Hello to all the community of Tricircle,
>
>
>
> I deployed Tricircle according to the architecture proposed by "Multi-pod
> Installation with DevStack". Now I'm trying to apply the "Networking Guide"
> tutorial and more specifically "Service Function Chaining Guide". Indeed, I
> find that the configuration is somewhat ambiguous with regard to the
> configuration of local neutron.
>
>
>
> I thank you in advance for helping me on this by a more detailed
> explanation. Have a great day!
>
>
>
> Best regards,
>
>
>
> Meher
>
>
>
> [image: Logo Orange] 
>
>
>
> *Meher Hihi *
> Intern
> ORANGE/IMT/OLN/WTC/CMA/MAX
>
> Fixe : +33 2 96 07 03 71
> 
> Mobile : +33 7 58 38 68 87
> 
> meher.h...@orange.com
>
>
>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing 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.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

[Raildo Mascena de Sousa Filho]

Hi all,

Should we reserve a room in the extra session ethercalc [0
] or we
already have a time slot scheduled for that discussion?

[0] https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms

Cheers,

On Tue, Aug 8, 2017 at 7:49 AM Thierry Carrez  wrote:

> Emilien Macchi wrote:
> > On Mon, Aug 7, 2017 at 9:15 AM, Doug Hellmann 
> wrote:
> >> Kendall & Thierry, what do we need to do to reserve that room if we
> >> can't find space in another team room?
> >
> > Worst case, we can use a slot from TripleO - this topic is also
> > critical to us and I think we can make our schedule to have one free
> > room during the 2 and a half days that we have.
> > Just let me know.
>
> It could also be scheduled in one of the extra reservable rooms we have
> on Thursday/Friday. The ethercalc for that should be up next week.
>
> --
> 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
>
-- 

Raildo mascena

Software Engineer, Identity Managment

Red Hat



TRIED. TESTED. TRUSTED. 
__
OpenStack Development Mailing 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] [barbican] [security] custodia @ PTG

[Raildo Mascena de Sousa Filho]

Hi Luke,

I'll definitely be there, sounds like a great idea, so we can clarify a lot
of topics and make progress in the community together.

Cheers,


On Thu, Aug 17, 2017 at 5:52 AM Luke Hinds  wrote:

> Hi Raildo,
>
> Both Barbican and Security have an interest in custodia and we have it
> marked down as a topic / discussion point for the PTG [1]
>
> Would you be interested / willing to join the Barbican room on Thurs / Fri
> and propose a walk through / overview etc?
>
> [1] https://etherpad.openstack.org/p/barbican-ptg-queens
>
>
> Regards,
>
> Luke
>
-- 

Raildo mascena

Software Engineer, Identity Managment

Red Hat



TRIED. TESTED. TRUSTED. 
__
OpenStack Development Mailing 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-operators] Not able to take snapshot backup

[Evan Bollig PhD]

Look at the available disk for cinder. If you're not using RBD or another
vendor driver, then you'll need at least as much free space as the size of
the VM. When you run out of space, the services tend to stop and block.

Also, if you set the limits but haven't rebooted, now is a good
opportunity. I think the system level governor will need it. Are you still
seeing the connections error? Any error in the logs is where you should
focus first.

Cheers,
-E


On Thu, Aug 17, 2017 at 7:47 AM Anwar Durrani 
wrote:

> Thanks Evan/Arne, i have done that part but for some instance i have
> notices
>
>  unable to create snapshot of instance. It stuck at 50% for a very long
> time.
>
>
> Thanks
>
> On Thu, Aug 17, 2017 at 4:28 PM, Evan Bollig PhD  wrote:
>
>> Correct, but even increasing the max_connections in your MySQL
>> configuration may not be enough.  Look at your system ulimit, or in or
>> around /etc/sysconfig/limits.conf  where a system-level governor is defined
>> for max_connections (on centos).
>>
>> Cheers,
>> -E
>>
>>
>> On Thu, Aug 17, 2017 at 3:32 AM Arne Wiebalck 
>> wrote:
>>
>>> Anwar,
>>>
>>> “Too many connections” sounds like you hit a limit on the database.
>>> You’ll need to
>>> check if the connection limit is too low or if there are connections
>>> which are stuck.
>>>
>>> HTH,
>>>  Arne
>>>
>>>
>>> On 17 Aug 2017, at 09:07, Anwar Durrani  wrote:
>>>
>>> Hi All,
>>>
>>> I have openstack Kilo installed, presently i am not able to snapshot of
>>> any instance, when i have checked logs on server it says following :
>>>
>>> cinder OperationalError: (OperationalError) (1040, 'Too many
>>> connections') None None
>>>
>>> If you have any clue for the same ?
>>>
>>>
>>> Thanks
>>>
>>> --
>>> Thanks & regards,
>>> Anwar M. Durrani
>>> +91-9923205011 <099232%2005011>
>>> 
>>>
>>>
>>> ___
>>> OpenStack-operators mailing list
>>> OpenStack-operators@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>> --
>>> Arne Wiebalck
>>> CERN IT
>>>
>>> ___
>>> OpenStack-operators mailing list
>>> OpenStack-operators@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>> --
>> --
>> Evan F. Bollig, PhD
>> Scientific Computing Consultant, Application Developer | Scientific
>> Computing Solutions (SCS)
>> Minnesota Supercomputing Institute | msi.umn.edu
>> University of Minnesota | umn.edu
>> boll0...@umn.edu | 612-624-1447 <0612%20624%201447> | Walter Lib Rm 556
>>
>
>
>
> --
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
> 
>
>
> --
--
Evan F. Bollig, PhD
Scientific Computing Consultant, Application Developer | Scientific
Computing Solutions (SCS)
Minnesota Supercomputing Institute | msi.umn.edu
University of Minnesota | umn.edu
boll0...@umn.edu | 612-624-1447 | Walter Lib Rm 556
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Not able to take snapshot backup

[Anwar Durrani]

Thanks Evan/Arne, i have done that part but for some instance i have
notices

 unable to create snapshot of instance. It stuck at 50% for a very long
time.


Thanks

On Thu, Aug 17, 2017 at 4:28 PM, Evan Bollig PhD  wrote:

> Correct, but even increasing the max_connections in your MySQL
> configuration may not be enough.  Look at your system ulimit, or in or
> around /etc/sysconfig/limits.conf  where a system-level governor is defined
> for max_connections (on centos).
>
> Cheers,
> -E
>
>
> On Thu, Aug 17, 2017 at 3:32 AM Arne Wiebalck 
> wrote:
>
>> Anwar,
>>
>> “Too many connections” sounds like you hit a limit on the database.
>> You’ll need to
>> check if the connection limit is too low or if there are connections
>> which are stuck.
>>
>> HTH,
>>  Arne
>>
>>
>> On 17 Aug 2017, at 09:07, Anwar Durrani  wrote:
>>
>> Hi All,
>>
>> I have openstack Kilo installed, presently i am not able to snapshot of
>> any instance, when i have checked logs on server it says following :
>>
>> cinder OperationalError: (OperationalError) (1040, 'Too many
>> connections') None None
>>
>> If you have any clue for the same ?
>>
>>
>> Thanks
>>
>> --
>> Thanks & regards,
>> Anwar M. Durrani
>> +91-9923205011 <099232%2005011>
>> 
>>
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>> --
>> Arne Wiebalck
>> CERN IT
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
> --
> --
> Evan F. Bollig, PhD
> Scientific Computing Consultant, Application Developer | Scientific
> Computing Solutions (SCS)
> Minnesota Supercomputing Institute | msi.umn.edu
> University of Minnesota | umn.edu
> boll0...@umn.edu | 612-624-1447 <0612%20624%201447> | Walter Lib Rm 556
>



-- 
Thanks & regards,
Anwar M. Durrani
+91-9923205011

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

Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon

[BİLGEM BTE]

Hi Julien, 
We developed the monitor dashboard to use it on our private cloud in the first 
place. We have Mitaka release and we use MongoDB with Ceilometer. But you are 
right, we can update the api to use Gnocchi. This release currently supports 
one day monitoring, when we add Gnocchi api support we can add weekly and 
monthly monitoring options. Thanks. 

- Orijinal Mesaj -

Kimden: "Gökhan IŞIK (BİLGEM BTE)"  
Kime: "Julien Danjou"  
Kk: openstack-dev@lists.openstack.org 
Gönderilenler: 14 Ağustos Pazartesi 2017 9:34:51 
Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon 

Hi Julien, 
We developed the monitor dashboard to use it on our private cloud in the first 
place. We have Mitaka release and we use MongoDB with Ceilometer. But you are 
right, we can update the api to use Gnocchi. This release currently supports 
one day monitoring, when we add Gnocchi api support we can add weekly and 
monthly monitoring options. Thanks. 

- Orijinal Mesaj -

Kimden: "Julien Danjou"  
Kime: "Gökhan IŞIK (BİLGEM BTE)"  
Kk: openstack-dev@lists.openstack.org 
Gönderilenler: 11 Ağustos Cuma 2017 15:29:17 
Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon 

On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: 

Hi, 

> We are happy to share with you that we developed an AngularJS based usage 
> monitoring panel for Horizon. 
> The panel visualizes the collected utilization data by Ceilometer. 
> 
> Source code is now available on github [1]. 
> 
> The plugin consists of 3 panels; a monitoring panel for users, a project 
> monitoring panel and a hypervisor monitoring panel for admins. 
> 
> A user can display utilization charts for the current project's instances, 
> export the metrics in csv format and launch alarms using the dashboard. 
> We have another service to capture these alarms and send notification e-mails 
> to the cloud users which is also available on github.com/b3lab. 
> An admin can display projects' utilization charts, export the metrics in csv 
> format in Project Monitor panel. And the Hypervisor Monitor panel is to 
> visualize SNMP based metrics collected from hypervisors. 
> 
> We are currently improving some features. 
> 
> Some screenshots published at our website [2]. We also uploaded two videos 
> showing some features of the plugin [3][4]. 
> 
> All comments and ideas are welcome! 

Did you build all of this against the deprecated Ceilometer API rather 
than Gnocchi? :( 

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


__
OpenStack Development Mailing 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] [OSSN 0080] Aodh can be used to launder Keystone trusts

[Luke Hinds]

Aodh can be used to launder Keystone trusts
---

### Summary ###

When adding an alarm action with the scheme `trust+http:` Aodh does not
verify that the user creating the alarm is the trustor or has the same
rights as the trustor, not that the trust is for the same project as the
alarm.

### Affected Services / Software ###

Aodh the alarm engine of the Telemetry project.

Pike, Ocata and Newton

### Discussion ###

When adding an alarm action with the scheme `trust+http:`, Aodh allows
the user to provide a trust ID to acquire a token with which to make a
webhook request. (If no trust ID is provided then Aodh creates a trust
internally, in which case the issue is not present.) However, Aodh makes
no attempt to verify that the user creating the alarm is the trustor or
has the same rights as the trustor - it also does not attempt to check
that the trust is for the same project as the alarm.

The nature of the `trust+http:` alarm notifier is that it allows the
user to obtain a token given the ID of a trust for which Aodh is the
trustee, since the URL is arbitrary and not limited to services in the
Keystone catalog.

### Recommended Actions ###

A patchfile is attached to the launchpad bug referenced below. It will
block use of trust URLs which contain trust ID's and log an error
message of "trust URL cannot contain a trust ID.". Any trust action
without a trust ID will result in Aodh internally creating a trust ID as
before.

You will also need to restart the web server used for Aodh API. This is
typically apache. In cases of eventlet (in older versions) it will
require restart openstack-aodh-api for centos/RHEL/Suse and aodh-api
for ubuntu.

The fix has also been merged to master (Pike), Ocata and Newton.

### Contacts / References ###
Discoverer: Zane Bitter, Red Hat
Author: Luke Hinds, Red Hat
CVE: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12440
This OSSN : https://wiki.openstack.org/wiki/OSSN/OSSN-0080
Original LaunchPad Bug : https://bugs.launchpad.net/ossn/+bug/1649333
OpenStack Security Project : https://launchpad.net/~openstack-ossg



signature.asc
Description: OpenPGP digital signature
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon

[BİLGEM BTE]

Hi Julien, 
We developed the monitor dashboard to use it on our private cloud in the first 
place. We have Mitaka release and we use MongoDB with Ceilometer. But you are 
right, we can update the api to use Gnocchi. This release currently supports 
one day monitoring, when we add Gnocchi api support we can add weekly and 
monthly monitoring options. Thanks. 

- Orijinal Mesaj -

Kimden: "Julien Danjou"  
Kime: "Gökhan IŞIK (BİLGEM BTE)"  
Kk: openstack-dev@lists.openstack.org 
Gönderilenler: 11 Ağustos Cuma 2017 15:29:17 
Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon 

On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: 

Hi, 

> We are happy to share with you that we developed an AngularJS based usage 
> monitoring panel for Horizon. 
> The panel visualizes the collected utilization data by Ceilometer. 
> 
> Source code is now available on github [1]. 
> 
> The plugin consists of 3 panels; a monitoring panel for users, a project 
> monitoring panel and a hypervisor monitoring panel for admins. 
> 
> A user can display utilization charts for the current project's instances, 
> export the metrics in csv format and launch alarms using the dashboard. 
> We have another service to capture these alarms and send notification e-mails 
> to the cloud users which is also available on github.com/b3lab. 
> An admin can display projects' utilization charts, export the metrics in csv 
> format in Project Monitor panel. And the Hypervisor Monitor panel is to 
> visualize SNMP based metrics collected from hypervisors. 
> 
> We are currently improving some features. 
> 
> Some screenshots published at our website [2]. We also uploaded two videos 
> showing some features of the plugin [3][4]. 
> 
> All comments and ideas are welcome! 

Did you build all of this against the deprecated Ceilometer API rather 
than Gnocchi? :( 

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

__
OpenStack Development Mailing 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] A Monitoring panel plugin for Horizon

[BİLGEM BTE]

Hi Julien, 
We developed the monitor dashboard to use it on our private cloud in the first 
place. We have Mitaka release and we use MongoDB with Ceilometer. But you are 
right, we can update the api to use Gnocchi. This release currently supports 
one day monitoring, when we add Gnocchi api support we can add weekly and 
monthly monitoring options. Thanks. 
- Orijinal Mesaj -

Kimden: "Gökhan IŞIK (BİLGEM BTE)"  
Kime: "Julien Danjou"  
Kk: openstack-dev@lists.openstack.org 
Gönderilenler: 14 Ağustos Pazartesi 2017 9:34:51 
Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon 

Hi Julien, 
We developed the monitor dashboard to use it on our private cloud in the first 
place. We have Mitaka release and we use MongoDB with Ceilometer. But you are 
right, we can update the api to use Gnocchi. This release currently supports 
one day monitoring, when we add Gnocchi api support we can add weekly and 
monthly monitoring options. Thanks. 

- Orijinal Mesaj -

Kimden: "Julien Danjou"  
Kime: "Gökhan IŞIK (BİLGEM BTE)"  
Kk: openstack-dev@lists.openstack.org 
Gönderilenler: 11 Ağustos Cuma 2017 15:29:17 
Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon 

On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: 

Hi, 

> We are happy to share with you that we developed an AngularJS based usage 
> monitoring panel for Horizon. 
> The panel visualizes the collected utilization data by Ceilometer. 
> 
> Source code is now available on github [1]. 
> 
> The plugin consists of 3 panels; a monitoring panel for users, a project 
> monitoring panel and a hypervisor monitoring panel for admins. 
> 
> A user can display utilization charts for the current project's instances, 
> export the metrics in csv format and launch alarms using the dashboard. 
> We have another service to capture these alarms and send notification e-mails 
> to the cloud users which is also available on github.com/b3lab. 
> An admin can display projects' utilization charts, export the metrics in csv 
> format in Project Monitor panel. And the Hypervisor Monitor panel is to 
> visualize SNMP based metrics collected from hypervisors. 
> 
> We are currently improving some features. 
> 
> Some screenshots published at our website [2]. We also uploaded two videos 
> showing some features of the plugin [3][4]. 
> 
> All comments and ideas are welcome! 

Did you build all of this against the deprecated Ceilometer API rather 
than Gnocchi? :( 

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


__
OpenStack Development Mailing 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] [Cyborg]Queens PTL candidacy

[Zhipeng Huang]

Hi Team,

Since the election for the official projects is over, it is safe to say
that we also accomplish our first election. Due to the reason of single
nominee for the PTL candidacy, it is my honor to continue serving as the
project lead for the next cycle.

Thanks for all the hard work and support from the team in the Pike cycle :)

On Wed, Aug 9, 2017 at 10:25 PM, Zhipeng Huang 
wrote:

> Hi Harm,
>
> Thanks for your kind words :) Will try to do my best
>
> On Wed, Aug 9, 2017 at 1:02 AM, Harm Sluiman 
> wrote:
>
>> Howard, I guess you will need some +1 votes and I certainly support you
>> based on our joint early work on these projects.
>> I regret not having time to participate actively this year. However your
>> contribution has been great for the project and the OpenStack community
>>
>> On Thu, Aug 3, 2017 at 3:55 AM, Zhipeng Huang 
>> wrote:
>>
>>> Yes tony I was intended to refer to the official procedure for the
>>> self-nomination period, which would be 5 buiz days.
>>>
>>> Thx for the offer to help with the civs poll :)
>>>
>>> On Thu, Aug 3, 2017 at 3:11 PM, Tony Breeds 
>>> wrote:
>>>
 On Thu, Aug 03, 2017 at 11:59:55AM +0800, Zhipeng Huang wrote:
 > Hi Team,
 >
 > Even though Cyborg is not an official project yet, however with an
 ultimate
 > goal of becoming one it is necessary to conduct our project
 governance with
 > compliance of OpenStack community general requirements/culture.

 You didn't specify how long the self-nomination period is.  I assume
 you're going for 5 business days?

 So any self nominations need to be in within a week from now

 Yours Tony.

 
 __
 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


>>>
>>>
>>> --
>>> Zhipeng (Howard) Huang
>>>
>>> Standard Engineer
>>> IT Standard & Patent/IT Product Line
>>> Huawei Technologies Co,. Ltd
>>> Email: huangzhip...@huawei.com
>>> Office: Huawei Industrial Base, Longgang, Shenzhen
>>>
>>> (Previous)
>>> Research Assistant
>>> Mobile Ad-Hoc Network Lab, Calit2
>>> University of California, Irvine
>>> Email: zhipe...@uci.edu
>>> Office: Calit2 Building Room 2402
>>>
>>> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>>>
>>> 
>>> __
>>> 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
>>>
>>>
>>
>>
>> --
>> 宋慢
>> Harm Sluiman
>>
>>
>>
>>
>>
>> 
>> __
>> 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
>>
>>
>
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Product Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing 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] Multi-region support in shared Keystone service deployment

[Rob Cresswell (rcresswe)]

As I mentioned the last time you asked :), we use blueprints, and the template 
is here: https://blueprints.launchpad.net/horizon/+spec/template

Please register a blueprint for discussion / tracking. The change looks 
sensible, although I’d prefer we use a setting name like 
https://docs.openstack.org/horizon/latest/configuration/settings.html#openstack-keystone-domain-choices.
 It’s a bit less ambiguous.

Rob



On 16 Aug 2017, at 23:03, Lingxian Kong 
> wrote:

Hi, Horizon developers,

In our OpenStack based public cloud(Catalyst Cloud), Keystone is a shared 
identity service across 3 regions, our customers have been asking for the 
feature that they could select their preferred region when they log in Horizon, 
rather than switching region each time after login.

Unfortunately, the existing 'AVAILABLE_REGIONS' only works with multi-keystone, 
multi-region environment, so for backward compatibility and getting rid of 
potential confusion, a new config option named 'AVAILABLE_SERVICE_REGIONS' was 
introduced in my patch[1][2], the setting is supposed to be configured by the 
cloud operators and the 'AVAILABLE_REGIONS' setting will take precedence over 
'AVAILABLE_SERVICE_REGIONS'.

I am sending this email to ask for more feedback, and do I need to propose a 
feature spec before the code is actually being reviewed?

[1]: https://review.openstack.org/#/c/494083/
[2]: https://review.openstack.org/#/c/494059/

Cheers,
Lingxian Kong (Larry)
__
OpenStack Development Mailing 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-operators] Not able to take snapshot backup

[Evan Bollig PhD]

Correct, but even increasing the max_connections in your MySQL
configuration may not be enough.  Look at your system ulimit, or in or
around /etc/sysconfig/limits.conf  where a system-level governor is defined
for max_connections (on centos).

Cheers,
-E


On Thu, Aug 17, 2017 at 3:32 AM Arne Wiebalck  wrote:

> Anwar,
>
> “Too many connections” sounds like you hit a limit on the database. You’ll
> need to
> check if the connection limit is too low or if there are connections which
> are stuck.
>
> HTH,
>  Arne
>
>
> On 17 Aug 2017, at 09:07, Anwar Durrani  wrote:
>
> Hi All,
>
> I have openstack Kilo installed, presently i am not able to snapshot of
> any instance, when i have checked logs on server it says following :
>
> cinder OperationalError: (OperationalError) (1040, 'Too many connections')
> None None
>
> If you have any clue for the same ?
>
>
> Thanks
>
> --
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
> 
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
> --
> Arne Wiebalck
> CERN IT
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-- 
--
Evan F. Bollig, PhD
Scientific Computing Consultant, Application Developer | Scientific
Computing Solutions (SCS)
Minnesota Supercomputing Institute | msi.umn.edu
University of Minnesota | umn.edu
boll0...@umn.edu | 612-624-1447 | Walter Lib Rm 556
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [horizon] Admin dashboard instances index page generated duplicate Glance requests

[Rob Cresswell (rcresswe)]

This may be a bug; I recall it was patched recently and perhaps the same logic 
needs to be applied to the Admin view. It sounds like an oversight.

Rob

> On 14 Aug 2017, at 03:46, Xiong, Huan  wrote:
> 
> Hi,
> 
> I observed accessing Admin dashboard's instance index page generated lots of 
> duplicate requests to Glance for converting instance image id to name, but 
> accessing Project dashboard's instance index page didn't (my system runs 
> Newton, but from what I can tell, Ocata and Pike code seem to have same 
> issue).
> 
> I looked at the code and found the reason. In Project dashboard's instance 
> index view class, it first calls Glance's API to get a list of image objects, 
> then iterates through instance objects and sets each instance's image 
> attribute to corresponding image object. As a result, when instance object's 
> image_name() is called later, it gets name from image object. In Admin 
> dashboard's instance index view class, however, it doesn't do this and hence 
> needs to send request to Glance everytime image_name() is called.
> 
> I wonder why Admin dashboard's instance index view class doesn't use the same 
> approach as Project dashboard? Is it intended?
> 
> Thanks,
> Ray
> 
> 
> 
> This email is intended only for the named addressee. It may contain 
> information that is confidential/private, legally privileged, or 
> copyright-protected, and you should handle it accordingly. If you are not the 
> intended recipient, you do not have legal rights to retain, copy, or 
> distribute this email or its contents, and should promptly delete the email 
> and all electronic copies in your system; do not retain copies in any media. 
> If you have received this email in error, please notify the sender promptly. 
> Thank you.
> 
> 
> 
> __
> OpenStack Development Mailing 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] [OSSN 0080] Aodh can be used to launder Keystone trusts

[Luke Hinds]

Aodh can be used to launder Keystone trusts
---

### Summary ###

When adding an alarm action with the scheme `trust+http:` Aodh does not
verify that the user creating the alarm is the trustor or has the same
rights as the trustor, not that the trust is for the same project as the
alarm.

### Affected Services / Software ###

Aodh the alarm engine of the Telemetry project.

Pike, Ocata and Newton

### Discussion ###

When adding an alarm action with the scheme `trust+http:`, Aodh allows
the user to provide a trust ID to acquire a token with which to make a
webhook request. (If no trust ID is provided then Aodh creates a trust
internally, in which case the issue is not present.) However, Aodh makes
no attempt to verify that the user creating the alarm is the trustor or
has the same rights as the trustor - it also does not attempt to check
that the trust is for the same project as the alarm.

The nature of the `trust+http:` alarm notifier is that it allows the
user to obtain a token given the ID of a trust for which Aodh is the
trustee, since the URL is arbitrary and not limited to services in the
Keystone catalog.

### Recommended Actions ###

A patchfile is attached to the launchpad bug referenced below. It will
block use of trust URLs which contain trust ID's and log an error
message of "trust URL cannot contain a trust ID.". Any trust action
without a trust ID will result in Aodh internally creating a trust ID as
before.

You will also need to restart the web server used for Aodh API. This is
typically apache. In cases of eventlet (in older versions) it will
require restart openstack-aodh-api for centos/RHEL/Suse and aodh-api
for ubuntu.

The fix has also been merged to master (Pike), Ocata and Newton.

### Contacts / References ###
Discoverer: Zane Bitter, Red Hat
Author: Luke Hinds, Red Hat
CVE: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12440
This OSSN : https://wiki.openstack.org/wiki/OSSN/OSSN-0080
Original LaunchPad Bug : https://bugs.launchpad.net/ossn/+bug/1649333
OpenStack Security Project : https://launchpad.net/~openstack-ossg



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

Re: [openstack-dev] Tacker

[CRISTIAN ARRIBAS GONZALEZ]

Hello! I can´t see any log, because when i go the /opt/logs, any log of
tacker there  is...

2017-08-17 12:54 GMT+02:00 Daniel Mellado :

> On 08/17/2017 12:43 PM, CRISTIAN ARRIBAS GONZALEZ wrote:
> > Hello,
> >
> > my name is Cristian Arribas, i´m getting stated to use Tacker. I
> > installed tacker
> > with devstack. When I want to deploy the ns service with Tosca Template,
> > a one error ocurre:
> >
> > *Error: *Failed to create NS: Request Failed: internal server error
> > while processing your request.
> >
> > ¿What could be the problem?
> >
> > Best regards.
> >
> > --
> > Cristian Arribas González
> > Ingeniería de Telemática
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> Hi Christian, welcome aboard! Did you get to check any logs? I'd
> recommend you to first take a look at that in order to narrow the scope.
>
> Best!
>
> Daniel
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Cristian Arribas González
Ingeniería de Telemática
__
OpenStack Development Mailing 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] Tacker

[Daniel Mellado]

On 08/17/2017 12:43 PM, CRISTIAN ARRIBAS GONZALEZ wrote:
> Hello,
> 
> my name is Cristian Arribas, i´m getting stated to use Tacker. I
> installed tacker
> with devstack. When I want to deploy the ns service with Tosca Template,
> a one error ocurre:
> 
> *Error: *Failed to create NS: Request Failed: internal server error
> while processing your request.
> 
> ¿What could be the problem?
> 
> Best regards.
> 
> -- 
> Cristian Arribas González
> Ingeniería de Telemática
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
Hi Christian, welcome aboard! Did you get to check any logs? I'd
recommend you to first take a look at that in order to narrow the scope.

Best!

Daniel

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

Re: [openstack-dev] Tacker

[Trinath Somanchi]

Can you check the tacker logs at /opt/stack/ for exceptions for this error.


Best Regards,
Trinath Somanchi | NXP | HSDC, INDIA

From: CRISTIAN ARRIBAS GONZALEZ [mailto:100304...@alumnos.uc3m.es]
Sent: Thursday, August 17, 2017 4:14 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] Tacker

Hello,

my name is Cristian Arribas, i´m getting stated to use Tacker. I installed 
tacker
with devstack. When I want to deploy the ns service with Tosca Template, a one 
error ocurre:

Error: Failed to create NS: Request Failed: internal server error while 
processing your request.

¿What could be the problem?

Best regards.

--
Cristian Arribas González
Ingeniería de Telemática
__
OpenStack Development Mailing 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] Tacker

[CRISTIAN ARRIBAS GONZALEZ]

Hello,

my name is Cristian Arribas, i´m getting stated to use Tacker. I installed
tacker
with devstack. When I want to deploy the ns service with Tosca Template, a
one error ocurre:

*Error: *Failed to create NS: Request Failed: internal server error while
processing your request.

¿What could be the problem?

Best regards.

-- 
Cristian Arribas González
Ingeniería de Telemática
__
OpenStack Development Mailing 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] [tricircle-Service Function Chaining]

[meher.hihi]

Hello to all the community of Tricircle,

I deployed Tricircle according to the architecture proposed by "Multi-pod 
Installation with DevStack". Now I'm trying to apply the "Networking Guide" 
tutorial and more specifically "Service Function Chaining Guide". Indeed, I 
find that the configuration is somewhat ambiguous with regard to the 
configuration of local neutron.

I thank you in advance for helping me on this by a more detailed explanation. 
Have a great day!

Best regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

__
OpenStack Development Mailing 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-docs] [all][elections] Project Team Lead Election Conclusion and Results

[Alexandra Settle]

Sigh. The Queen release deliverables*, not the Pike release deliverables.

One day I will send out an email without something incorrect.


From: Alexandra Settle 
Date: Thursday, August 17, 2017 at 10:22 AM
To: openstack-docs , "OpenStack Development 
Mailing List (not for usage questions)" 
Subject: Re: [OpenStack-docs] [openstack-dev] [all][elections] Project Team 
Lead Election Conclusion and Results

Hi everyone,

The PTL nomination period is now over, so I'm pleased to be able to confirm 
that Petr Kovar is our new PTL for Queens.

Congratulations, Petr! I am excited to be working with you on the doc team 
future, and I can't wait to see what the docs team can achieve under your 
stewardship.

I would also like to thank Chason Chan for stepping up to represent our team.

On immediate practical matters: I will continue to handle the Pike release, 
along with our release team, while Petr will be organising the PTG in Denver, 
and the Pike release deliverables. I will be working closely with Petr over the 
next couple of weeks to ensure he has all the tools he needs to serve as your 
PTL.

Congratulations :)

Alex

From: Kendall Nelson 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, August 17, 2017 at 1:25 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [all][elections] Project Team Lead Election Conclusion 
and Results


Hello Everyone!

Thank you to the electorate, to all those who voted and to all candidates who 
put their name forward for Project Team Lead (PTL) in this election. A healthy, 
open process breeds trust in our decision making capability thank you to all 
those who make this process possible.



Now for the results of the PTL election process, please join me in extending 
congratulations to the following PTLs:



 * Barbican  : Dave McCowan

 * Chef OpenStack: Samuel Cassiba

 * Cinder: Jay Bryant

 * Cloudkitty: Christophe Sauthier

 * Congress  : Eric Kao

 * Designate : Graham Hayes

 * Documentation : Petr Kovar

 * Dragonflow: Omer Anson

 * Ec2 Api   : Andrey Pavlov

 * Freezer   : Saad Zaher

 * Glance: Brian Rosmaita

 * Heat  : Rico Lin

 * Horizon   : Ying Zuo

 * I18n  : Frank Kloeker

 * Infrastructure: Clark Boylan

 * Ironic: Dmitry Tantsur

 * Karbor: Chenying Chenying

 * Keystone  : Lance Bragstad

 * Kolla : Michal Jastrzebski

 * Kuryr : Antoni Segura Puimedon

 * Magnum: Spyros Trigazis

 * Manila: Ben Swartzlander

 * Mistral   : Renat Renat

 * Monasca   : Witold Bedyk

 * Murano: Zhurong Zhurong

 * Neutron   : Kevin Benton

 * Nova  : Matt Riedemann

 * Octavia   : Michael Johnson

 * OpenStackAnsible  : Jean-Philippe Evrard

 * OpenStackClient   : Dean Troyer

 * OpenStack Charms  : James Page

 * Oslo  : ChangBo Guo

 * Packaging Rpm : Thomas Bechtold

 * Puppet OpenStack  : Mohammed Naser

 * Quality Assurance : Andrea Frittoli

 * Rally : Andrey Kurilin

 * RefStack  : Chris Hoge

 * Release Management: Sean McGinnis

 * Requirements  : Matthew Thode

 * Sahara: Telles Mota Vidal Nóbrega

 * Searchlight   : Steve McLellan

 * Security  : Luke Hinds

 * Senlin: RUIJIE YUAN

 * Shade : Monty Taylor

 * Solum : Zhurong Zhurong

 * Stable Branch Maintenance : Tony Breeds

 * Storlets  : Kota Tsuyuzaki

 * Swift : John Dickinson

 * Tacker: Gongysh Gongysh

 * Telemetry : Gordon Chung

 * Tricircle : Zhiyuan Cai

 * Tripleo   : Alex Schultz

 * Trove : Amrith Kumar

 * Vitrage   : Ifat Afek

 * Watcher   : Alexander Chadin

 * Winstackers   : Claudiu Belu

 * Zaqar : Feilong Wang

 * Zun   : Hongbin Lu



Elections:

* Documentation: 
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_d5d9fb5a2354e2a0

* Ironic: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_0fb06bb4edfd3d08



Election process details and results are also available here: 

Re: [openstack-dev] [all][elections] Project Team Lead Election Conclusion and Results

[Alexandra Settle]

Hi everyone,

The PTL nomination period is now over, so I'm pleased to be able to confirm 
that Petr Kovar is our new PTL for Queens.

Congratulations, Petr! I am excited to be working with you on the doc team 
future, and I can't wait to see what the docs team can achieve under your 
stewardship.

I would also like to thank Chason Chan for stepping up to represent our team.

On immediate practical matters: I will continue to handle the Pike release, 
along with our release team, while Petr will be organising the PTG in Denver, 
and the Pike release deliverables. I will be working closely with Petr over the 
next couple of weeks to ensure he has all the tools he needs to serve as your 
PTL.

Congratulations :)

Alex

From: Kendall Nelson 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, August 17, 2017 at 1:25 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [all][elections] Project Team Lead Election Conclusion 
and Results


Hello Everyone!

Thank you to the electorate, to all those who voted and to all candidates who 
put their name forward for Project Team Lead (PTL) in this election. A healthy, 
open process breeds trust in our decision making capability thank you to all 
those who make this process possible.



Now for the results of the PTL election process, please join me in extending 
congratulations to the following PTLs:



 * Barbican  : Dave McCowan

 * Chef OpenStack: Samuel Cassiba

 * Cinder: Jay Bryant

 * Cloudkitty: Christophe Sauthier

 * Congress  : Eric Kao

 * Designate : Graham Hayes

 * Documentation : Petr Kovar

 * Dragonflow: Omer Anson

 * Ec2 Api   : Andrey Pavlov

 * Freezer   : Saad Zaher

 * Glance: Brian Rosmaita

 * Heat  : Rico Lin

 * Horizon   : Ying Zuo

 * I18n  : Frank Kloeker

 * Infrastructure: Clark Boylan

 * Ironic: Dmitry Tantsur

 * Karbor: Chenying Chenying

 * Keystone  : Lance Bragstad

 * Kolla : Michal Jastrzebski

 * Kuryr : Antoni Segura Puimedon

 * Magnum: Spyros Trigazis

 * Manila: Ben Swartzlander

 * Mistral   : Renat Renat

 * Monasca   : Witold Bedyk

 * Murano: Zhurong Zhurong

 * Neutron   : Kevin Benton

 * Nova  : Matt Riedemann

 * Octavia   : Michael Johnson

 * OpenStackAnsible  : Jean-Philippe Evrard

 * OpenStackClient   : Dean Troyer

 * OpenStack Charms  : James Page

 * Oslo  : ChangBo Guo

 * Packaging Rpm : Thomas Bechtold

 * Puppet OpenStack  : Mohammed Naser

 * Quality Assurance : Andrea Frittoli

 * Rally : Andrey Kurilin

 * RefStack  : Chris Hoge

 * Release Management: Sean McGinnis

 * Requirements  : Matthew Thode

 * Sahara: Telles Mota Vidal Nóbrega

 * Searchlight   : Steve McLellan

 * Security  : Luke Hinds

 * Senlin: RUIJIE YUAN

 * Shade : Monty Taylor

 * Solum : Zhurong Zhurong

 * Stable Branch Maintenance : Tony Breeds

 * Storlets  : Kota Tsuyuzaki

 * Swift : John Dickinson

 * Tacker: Gongysh Gongysh

 * Telemetry : Gordon Chung

 * Tricircle : Zhiyuan Cai

 * Tripleo   : Alex Schultz

 * Trove : Amrith Kumar

 * Vitrage   : Ifat Afek

 * Watcher   : Alexander Chadin

 * Winstackers   : Claudiu Belu

 * Zaqar : Feilong Wang

 * Zun   : Hongbin Lu



Elections:

* Documentation: 
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_d5d9fb5a2354e2a0

* Ironic: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_0fb06bb4edfd3d08



Election process details and results are also available here: 
https://governance.openstack.org/election/



Thank you to all involved in the PTL election process,

- Kendall Nelson(diablo_rojo)
__
OpenStack Development Mailing 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] [openstack-dev] package gluster-swift with Openstack swift repository

[Venkata R Edara]

Thanks for the reply .  I have sent other email to rdo list.


On 08/10/2017 07:08 PM, Haïkel wrote:

2017-08-10 9:52 GMT+02:00 Venkata R Edara :

Hello All,

we are from Red Hat and we have product called Gluster which is distributed
file system. we have integrated Gluster with openstack-swift , the product
is called

gluster-swift . gluster-swift allows users to have SWIFT/S3 APIs with
Gluster filesystem as back-end. we did re-base of gluster-swift with
openstack-swift Newton release.

As gluster-swift is dependent on openstack-swift we would like to have it
packaged in openstack-swift newton repository.

Is it possible to package gluster-swift project in openstack repository?.

we would like to know the process of packaging with openstack repo if
openstack community agrees for that.

-Thanks

Venkata R Edara.



Hi,

AFAIK, shipping binary packages is the responsibility of downstream
distributions of OpenStack, though
there are efforts to collaborate on packaging within OpenStack.
I'm one of the RDO Release Engineer, RDO community would be happy to
help you packaging gluster-swift.
Please contact the RDO mailing list or join RDO weekly irc meetings.

Regards,
H.



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


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



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

[openstack-dev] [barbican] [security] custodia @ PTG

[Luke Hinds]

Hi Raildo,

Both Barbican and Security have an interest in custodia and we have it
marked down as a topic / discussion point for the PTG [1]

Would you be interested / willing to join the Barbican room on Thurs / Fri
and propose a walk through / overview etc?

[1] https://etherpad.openstack.org/p/barbican-ptg-queens


Regards,

Luke
__
OpenStack Development Mailing 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] package gluster-swift with Openstack swift repository

[Venkata R Edara]

Thanks for the reply .  I have sent other email to rdo list.


On 08/10/2017 07:08 PM, Haïkel wrote:

2017-08-10 9:52 GMT+02:00 Venkata R Edara :

Hello All,

we are from Red Hat and we have product called Gluster which is distributed
file system. we have integrated Gluster with openstack-swift , the product
is called

gluster-swift . gluster-swift allows users to have SWIFT/S3 APIs with
Gluster filesystem as back-end. we did re-base of gluster-swift with
openstack-swift Newton release.

As gluster-swift is dependent on openstack-swift we would like to have it
packaged in openstack-swift newton repository.

Is it possible to package gluster-swift project in openstack repository?.

we would like to know the process of packaging with openstack repo if
openstack community agrees for that.

-Thanks

Venkata R Edara.



Hi,

AFAIK, shipping binary packages is the responsibility of downstream
distributions of OpenStack, though
there are efforts to collaborate on packaging within OpenStack.
I'm one of the RDO Release Engineer, RDO community would be happy to
help you packaging gluster-swift.
Please contact the RDO mailing list or join RDO weekly irc meetings.

Regards,
H.



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


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



__
OpenStack Development Mailing 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] [ptg] Reservable extra discussion rooms

[Thierry Carrez]

Hi everyone,

The PTG is only in 4 weeks ! It's still time to join the crowd that will
be discussing and organizing the Queens development cycle in Denver.

Like for Atlanta, for discussions that don't fit in any particular room,
we have extra reservable discussion rooms available. Reservation is done
through an ethercalc on a first-come first-serve basis (with priority
given to official project teams) at:

https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms

For easier access (especially from mobile devices), the sessions
scheduled on the current day will also be published to a static,
mobile-friendly page that exposes the topics being currently discussed
at the PTG (driven by the ptgbot[1]).

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-May/116974.html

See you there !

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

Re: [openstack-dev] [nova][keystone] keystoneauth1 and keystonemiddle setting

[Chen CH Ji]

ok, thanks for Morgan and Brant's comments, will rework the patch based on
the comments, thanks!

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   Morgan Fainberg 
To: "OpenStack Development Mailing List (not for usage questions)"

Date:   08/17/2017 07:51 AM
Subject:Re: [openstack-dev] [nova][keystone] keystoneauth1 and
keystonemiddle setting





On Aug 16, 2017 11:31, "Brant Knudson"  wrote:


  On Mon, Aug 14, 2017 at 2:48 AM, Chen CH Ji  wrote:
   In fixing bug 1704798, there's a proposed patch
   https://review.openstack.org/#/c/485121/7
   but we stuck at http_connection_timeout and timeout value in
   keystoneauth1 and keystonemiddle repo

   basically we want to reuse the keystone_auth section in nova.conf to
   avoid create another section so we can
   use following to create a session

   sess = ks_loading.load_session_from_conf_options(CONF,
   'keystone_authtoken', auth=context.get_auth_plugin())

   any comments or we have to create another section and configure it
   anyway? thanks


   Best Regards!

   Kevin (Chen) Ji 纪 晨

   Engineer, zVM Development, CSTL
   Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
   Phone: +86-10-82451493
   Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
   District, Beijing 100193, PRC

   __

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


  I think reusing the keystone_authtoken config is a bad idea.
  keystone_authtoken contains the configuration for the auth_token
  middleware so this is what we keystone developers expect it to be used
  for. A deployment may have different security needs for the auth_token
  middleware vs checking quotas in which case they'll need different users
  or project for the auth_token middleware and quota checking. And even if
  we don't need it now we might need it in the future, and it's going to
  create a lot of work going forward to rearchitect.

  If a deployer wants to use the same authentication for both auth_token
  middleware and the proxy, they can create a new section with the config
  and point both keystone_authtoken and quota checking to it (by setting
  the auth_section).

  --
  - Brant

  __

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



What Brant said. Please do not lean on the options from keystone middleware
for anything outside of keystone middleware. We have had to change these
options before and those changes should only ever impact the keystone
middleware code. If you re-use those options for something in Nova, it will
likely break and need to be split into it's own option block in the future.

Please create a new option block (even if a deployers uses the same
user/passord) rather than using the authtoken config section for anything
outside of authtoken.

--Morgan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0=tObIBKyCbf77oLwdSwaHb3_FM8au2aTVSaHGYMH8-1Q=vRncIuk0n5yybdLrZA8uRBC3A0UZDhzj5-pX5alqUc0=



__
OpenStack Development Mailing 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][elections] Project Team Lead Election Conclusion and Results

[Thierry Carrez]

Kendall Nelson wrote:
> Hello Everyone!
> 
> Thank you to the electorate, to all those who voted and to all
> candidates who put their name forward for Project Team Lead (PTL) in
> this election. A healthy, open process breeds trust in our decision
> making capability thank you to all those who make this process possible.
> Now for the results of the PTL election process, please join me in
> extending congratulations to the following PTLs:
> [...]

Congratulations to all the elected PTLs, new names and returning ones!

The PTLs are at the same time a steward for their team, facilitating the
work of their teammates, an ambassador for the project, communicating
the work being done to the outside world, and a default contact point
for anyone having questions about a given team.

That can be daunting, especially for larger teams. Don't hesitate to
delegate as much of those tasks as you can!

Thank you again for your help. Let's make Queens a great cycle!

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

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[Thierry Carrez]

Tony Breeds wrote:
> On Wed, Aug 16, 2017 at 02:37:50PM -0400, William M Edmonds wrote:
>>
>> Julien Danjou  wrote on 08/16/2017 02:13:10 PM:
>>> AFAIU it's impossible to cut a branch for our projects and release a rc1
>>> because of the release model we use. The release team does not allow us
>>> to do that. We need to release directly a stable version and cut a
>>> branch.
>>>
>>> I guess we'll do that in a couple of week, at release time.
>>
>> That doesn't fit my understanding of cycle-with-intermediary, which is the
>> the ceilometer release model per [0]. As I read the release model
>> definitions [1], cycle-with-intermediary means that you can have
>> intermediate releases *as well*, but you still have to have a cycle-ending
>> release in line with the projects using the cycle-with-milestones model.
>>
>> Can someone on the release team clarify this for us?
> 
> That's correct the bit you're missing is cycle-with-intermediary doesn't
> have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels
> they have the code in shape for a release they'll tag that release and
> cut a stable/pike branch at the tag point.

Exactly. As explained a couple weeks ago in the release countdown email[1]:

> Deliverables following the cycle-with-intermediary model should also
> create their Pike release branch next week. That means potentially
> making a last Pike release, and in all cases posting the stable/pike
> branch creation request:
> 
> ...
> branches:
>   - location: YOUR.PIKE.VERSION
> name: stable/pike

[1]
http://lists.openstack.org/pipermail/openstack-dev/2017-August/120574.html

-- 
Thierry Carrez (ttx)



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

Re: [Openstack-operators] Not able to take snapshot backup

[Arne Wiebalck]

Anwar,

“Too many connections” sounds like you hit a limit on the database. You’ll need 
to
check if the connection limit is too low or if there are connections which are 
stuck.

HTH,
 Arne


On 17 Aug 2017, at 09:07, Anwar Durrani 
> wrote:

Hi All,

I have openstack Kilo installed, presently i am not able to snapshot of any 
instance, when i have checked logs on server it says following :


cinder OperationalError: (OperationalError) (1040, 'Too many connections') None 
None

If you have any clue for the same ?


Thanks

--
Thanks & regards,
Anwar M. Durrani
+91-9923205011



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

--
Arne Wiebalck
CERN IT

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

[Openstack-operators] Not able to take snapshot backup

[Anwar Durrani]

Hi All,

I have openstack Kilo installed, presently i am not able to snapshot of any
instance, when i have checked logs on server it says following :

cinder OperationalError: (OperationalError) (1040, 'Too many connections')
None None

If you have any clue for the same ?


Thanks

-- 
Thanks & regards,
Anwar M. Durrani
+91-9923205011

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

[Openstack] Cinder: Migrate Volume to VMDK backend

[Oisin O'Malley]

Hi All,

We're looking at migrating some VMs from KVM to VMware hypervisors.

Is it possible retype and/or migrate a detached Cinder volume that is in .RAW 
format from a NetApp NFS backend to a Cinder VMware VMDK backend? Will the file 
format be converted to a VMDK?

Regards,
Oisin

Oisin O'Malley

Systems Engineer





[cid:logo_b3c002ac-e953-4f9f-8684-5bd8480aa997.gif]


Iocane Pty Ltd, 763 South Road,
Black Forest, SA 5035



Office: +61 (8) 8413 1010 Fax: +61 (8) 8231 2050
Email: oisin.omal...@iocane.com.au



[LinkedIn]

www.iocane.com.au






[Better for business]


This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to which they are addressed. If 
you have received this email in error, please notify the system manager. Please 
note that any views or opinions presented in this email are solely those of the 
author. Iocane Pty Ltd accepts no liability for the content of this email.

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