On Tue, May 16 2017, Doug Hellmann wrote:
> https://bugs.launchpad.net/pbr/+bug/1691129 describes a traceback
> produced when building the developer documentation through pbr.
>
> https://bugs.launchpad.net/reno/+bug/1691224 describes a change where
> Sphinx now treats log messages at WARNING or
On 16 May 2017 at 16:08, Doug Hellmann wrote:
> Excerpts from Sean Dague's message of 2017-05-16 10:49:54 -0400:
>> On 05/16/2017 09:38 AM, Davanum Srinivas wrote:
>> > Folks,
>> >
>> > See $TITLE :)
>> >
>> > Thanks,
>> > Dims
>>
>> I'd rather avoid #openstack-tc and just use #openstack-dev.
>> #
On 17.05.2017 4:01, Emilien Macchi wrote:
> Hey Raoul,
>
> Thanks for putting this up in the ML. Replying inline:
>
> On Tue, May 16, 2017 at 4:59 PM, Raoul Scarazzini wrote:
>> Hi everybody,
>> as discussed in today's TripleO meeting [1] here's a brief recap of the
>> tripleo-quickstart-utils t
Hi Alexey,
Currently we use 'is_admin' as 'is_admin_project'[1], right?
I think the 'is_admin_project' represent the tenant , not be related to user.
So why 'is_admin_project' alaways return 'True' with all of the user and
tenants is the issue.
What about a user which is not ＇admin' but have
On Wed, May 17 2017, Julien Danjou wrote:
>> There's a patch in review for the reno issue. It would be great if
>> someone had time to look into a fix for pbr to make it work with
>> older and newer Sphinx.
>
> I'll look into it.
Here's the pbr fix:
https://review.openstack.org/#/c/465489/
If
Sean Dague wrote:
> On 05/16/2017 02:39 PM, Doug Hellmann wrote:
>> Excerpts from Michał Jastrzębski's message of 2017-05-16 09:51:00 -0700:
>>> One thing I struggle with is...well...how does *not having* built
>>> containers help with that? If your company have full time security
>>> team, they ca
On 16.05.2017 17:19, Dnyaneshwar Pawar wrote:
> Hi Steve,
>
> Thanks for your reply.
>
> Out of interest, where did you find OS::TripleO::ControllerServer, do we
> have a mistake in our docs somewhere?
>
> I referred below template.
> https://github.com/openstack/tripleo-heat-templates/
Hi,
Yes the ‘is_admin_project’ represent the tenant.
I have tried to use many different users which are part of the admin, alt_demo,
nova, vitrage, new_tenant that I have created and they all returned the
is_admin_project=True.
At the moment as I said only the admin user will be able to see th
On Wed, 17 May 2017, Thierry Carrez wrote:
Back to container image world, if we refresh those images daily and they
are not versioned or archived (basically you can only use the latest and
can't really access past dailies), I think we'd be in a similar situation ?
Yes, this.
--
Chris Dent
On 05/16/2017 07:34 PM, Adrian Turjak wrote:
> Anyway that aside, I'm sold on API keys as a concept in this case
> provided they are project owned rather than user owned, I just don't
> think we should make them too unique, and we shouldn't be giving them a
> unique policy system because that way
+1 to "my preference is to just start with the -dev channel"
Thanks,
Dims
On Wed, May 17, 2017 at 4:23 AM, John Garbutt wrote:
> On 16 May 2017 at 16:08, Doug Hellmann wrote:
>> Excerpts from Sean Dague's message of 2017-05-16 10:49:54 -0400:
>>> On 05/16/2017 09:38 AM, Davanum Srinivas wrote:
On 05/16/2017 01:28 PM, John Dickinson wrote:
> I'm not sure the best place to respond (mailing list or gerrit), so
> I'll write this up and post it to both places.
>
> I think the idea behind this proposal is great. It has the potential
> to bring a lot of benefit to users who are tracing a requ
On Tue, 16 May 2017, Monty Taylor wrote:
The questions:
- Does this help, hurt, no difference?
- servers[].name - servers is a list, containing objects with a name field.
Good or bad?
- servers[].addresses.$network-name - addresses is an object and the keys of
the object are the name of the n
On 17 May 2017 at 06:25, KiYoun Sung wrote:
> Hello,
> Magnum team.
>
> I Installed Openstack newton and magnum.
> I installed Magnum by source(master branch).
>
> I have two questions.
>
> 1.
> After installation,
> I created kubernetes cluster and it's CREATE_COMPLETE,
> and I want to create ku
On 17 May 2017 at 13:58, Spyros Trigazis wrote:
>
>
> On 17 May 2017 at 06:25, KiYoun Sung wrote:
>
>> Hello,
>> Magnum team.
>>
>> I Installed Openstack newton and magnum.
>> I installed Magnum by source(master branch).
>>
>> I have two questions.
>>
>> 1.
>> After installation,
>> I created ku
Yes that’s correct.
VM Heartbeating / Health-check Monitoring would introduce intrusive / white-box
type monitoring of VMs / Instances.
I realize this is somewhat in the gray-zone of what a cloud should be
monitoring or not,
but I believe it provides an alternative for Applications deployed in V
On 05/16/2017 08:08 PM, Zane Bitter wrote:
> On 16/05/17 01:06, Colleen Murphy wrote:
>> Additionally, I think OAuth - either extending the existing OAuth1.0
>> plugin or implementing OAuth2.0 - should probably be on the table.
>
> I believe that OAuth is not a good fit for long-lived things like
Excellent.
Yeah I just watched your Boston Summit presentation and noticed, at least when
you were talking about host-monitoring, you were looking at having alternative
backends for reporting e.g. to masakari-api or to mistral or ... to Vitrage :)
Greg.
From: Adam Spiers
Reply-To: "openstack-d
út 16. 5. 2017 v 18:03 odesílatel Dmitry Tantsur
napsal:
> On 05/15/2017 09:10 PM, Julia Kreger wrote:
> > All,
> >
> > In our new reality, in order to maximize velocity, I propose that we
> > loosen the review requirements for ironic-ui to allow faster
> > iteration. To this end, I suggest we mo
On 05/17/2017 07:40 AM, Chris Dent wrote:
> On Tue, 16 May 2017, Monty Taylor wrote:
>
>> The questions:
>>
>> - Does this help, hurt, no difference?
>> - servers[].name - servers is a list, containing objects with a name
>> field. Good or bad?
>> - servers[].addresses.$network-name - addresses is
There is a bug in diskimage-builder I reported it at 2017-03-10 as
'private security'. I think this bug is a medium severity.
So far there was no reaction at all. I plan to change this bug to public
security on next Monday. If someone is interested in bumping up CVE
count for DIB, please look
On Tue, 16 May 2017, Chris Dent wrote:
Elsewhere I'll create a more complete write up of the Foundation board
meeting that happened on the Sunday before summit, but some comments
from that feel relevant to the purpose of these reports:
Here's the rough notes from the board meeting:
https://an
Hi all,
we can save some memory in our OOOQ multinode jobs by specifying custom
role data -- getting rid of resources and YAQL crunching for roles that
aren't used at all in the end. Shout out to shardy for suggesting we
should look into doing this.
First observations, hopefully at least som
Indeed, recreating the environment with "tox -r" should help here (to
get the new lib)
On 16 May 2017 at 20:28, Ihar Hrachyshka wrote:
> Make sure you have the latest neutron-lib in your tree: neutron-lib==1.6.0
>
> On Tue, May 16, 2017 at 3:05 AM, Vikash Kumar
> wrote:
>> Hi Team,
>>
>> pep8
Hi,
When you attach multiple networks/interfaces to an instance and at
least 2 subnets have a default route, you end up with 2 default routes
in network_data.json.
If cloud-init or any other in-guest agent is used to configure the
network, you could end up with 2 default routes and to an extend,
On Wed, May 17, 2017 at 10:03 AM, Mathieu Gagné wrote:
> Hi,
>
> When you attach multiple networks/interfaces to an instance and at
> least 2 subnets have a default route, you end up with 2 default routes
> in network_data.json.
>
> If cloud-init or any other in-guest agent is used to configure th
Yep :-) That's pretty much exactly what I was suggesting elsewhere in
this thread:
http://lists.openstack.org/pipermail/openstack-dev/2017-May/116748.html
Waines, Greg wrote:
Excellent.
Yeah I just watched your Boston Summit presentation and noticed, at least when
you were talking about host
Thanks for the clarification Greg. This sounds like it has the
potential to be a very useful capability. May I suggest that you
propose a new user story for it, along similar lines to this existing
one?
http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html
Hi!
Following the forum, the session moderators should summarize how their
session went and detail next steps, to give opportunity to those who
couldn't be around in person to catch up if interested. Here is my quick
summary of the "Should we kill Stackalytics" session. You can find the
etherpad a
On 17 May 2017 at 04:14, Chris Dent wrote:
> On Wed, 17 May 2017, Thierry Carrez wrote:
>
>> Back to container image world, if we refresh those images daily and they
>> are not versioned or archived (basically you can only use the latest and
>> can't really access past dailies), I think we'd be in
Sure. I can propose a new user story.
And then are you thinking of including this user story in the scope of what
masakari would be looking at ?
Greg.
From: Adam Spiers
Reply-To: "openstack-dev@lists.openstack.org"
Date: Wednesday, May 17, 2017 at 10:08 AM
To: "openstack-dev@lists.openstac
On Tue, May 16, 2017 at 4:13 PM, Monty Taylor wrote:
> Hey all!
>
> I read the API docs A LOT. (thank you to all of you who have worked on
> writing them)
>
> As I do, a gotcha I hit up against a non-zero amount is mapping the
> descriptions of the response parameters to the form of the response
Michael,
There has been a lot of cost and risk analysis in this thread.
What hasn’t really been discussed at great detail is the “benefit analysis”
which you have started. I think we are all clear on the risks and the costs.
If we as a technical community are going to place a line in the sand
Dear all, Dear Edgar,
Unless I am mistaken, I didn't see any comments regarding my email.
I would like to know whether there should be some follow-up actions/messages or
if the FEMDC Working Group is well established in the OpenStack landscape?
Thanks,
Ad_rien_
- Mail original -
>
Hey folks
I have a fairly simple proposal to make - I'd like to suggest that Feature
Freeze move to being much earlier in the release cycle (no earlier than M.1
and no later than M.2 would be my preference).
In the current arrangement (looking specifically at Pike), FF is scheduled
to happen 5 we
On 2017-05-17 15:57:16 +0300 (+0300), George Shuklin wrote:
> There is a bug in diskimage-builder I reported it at 2017-03-10 as 'private
> security'. I think this bug is a medium severity.
>
> So far there was no reaction at all. I plan to change this bug to public
> security on next Monday. If s
Excerpts from Chris Dent's message of 2017-05-17 12:14:40 +0100:
> On Wed, 17 May 2017, Thierry Carrez wrote:
>
> > Back to container image world, if we refresh those images daily and they
> > are not versioned or archived (basically you can only use the latest and
> > can't really access past dai
Excerpts from Thierry Carrez's message of 2017-05-17 12:19:22 +0200:
> Sean Dague wrote:
> > On 05/16/2017 02:39 PM, Doug Hellmann wrote:
> >> Excerpts from Michał Jastrzębski's message of 2017-05-16 09:51:00 -0700:
> >>> One thing I struggle with is...well...how does *not having* built
> >>> conta
On 17 May 2017 at 08:55, Doug Hellmann wrote:
> Excerpts from Chris Dent's message of 2017-05-17 12:14:40 +0100:
>> On Wed, 17 May 2017, Thierry Carrez wrote:
>>
>> > Back to container image world, if we refresh those images daily and they
>> > are not versioned or archived (basically you can only
Doug,
When a docker image is pushed to dockerhub (or quay.io, etc) a tag is
specified. If the tag already exists, it is overwritten.
Regards
-steve
-Original Message-
From: Doug Hellmann
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, May 17
What kolla's been discussing is having something like:
4.0.0-1, 4.0.0-2, 4.0.0-3, etc.
only keeping the most recent two. and then aliases for:
4.0.0 pointing to the newest.
This allows helm upgrade to atomically roll/forward back properly. If you drop
releases, k8s can't properly do atomic upgrad
On 05/17/2017 05:34 PM, Chris Jones wrote:
Hey folks
I have a fairly simple proposal to make - I'd like to suggest that Feature
Freeze move to being much earlier in the release cycle (no earlier than M.1 and
no later than M.2 would be my preference).
I welcome projects to experiment with it,
You can do that, but doesn't play well with orchestration systems such as k8s
as it removes its ability to know when upgraded containers appear.
Thanks,
Kevin
* As always, sorry for top posting, but my organization does not allow me the
choice of mail software.
_
Hello folks,
Many core members and participants of our project are on vacation now, and
won't be able to participate in IRC meeting today.
Let us cancel it for today and re-convene it next week May 24.
Thanks
Bin
[1] https://wiki.openstack.org/wiki/Gluon
[2] https://wiki.openstack.
As I've mentioned in past meetings, the Manila community needs to decide
whether the OpenStack PTG is a venue we want to take advantage of in the
future. In particular, there's a deadline to declare our plans for the
Denver PTG in September by the end of the week.
Personally I'm conflicted bec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey there,
After my talk[0] at the OpenStack Summit in Boston about the
openstack-ansible-security role, I received plenty of feedback. Thanks to
everyone who attended the talk and suffered through my Texas accent. ;)
One of the pieces of feedba
I don't see any reason why masakari couldn't handle that, but you'd
have to ask Sampath and the masakari team whether they would consider
that in scope for their roadmap.
Waines, Greg wrote:
Sure. I can propose a new user story.
And then are you thinking of including this user story in the sc
Hello Ben,
We started discussing ways of minimizing collisions between projects like
Cinder and Manila for the upcoming PTG and think we are close to a
solution. More details to come, but that doesn't need to be a con as we are
working to address those issues this PTG :)
-Kendall (diablo_rojo)
O
On 5/17/17, 6:25 PM, "Major Hayden" wrote:
1) Should the openstack-ansible-security role be
renamed to alleviate confusion?
Sure, I’ve long thought that the name is misleading.
2) If it should be renamed, what's your suggestion?
My uninspired suggestion is to make it somet
Hello Ben,
That was a great summary of our choices. I believe it is worth mentioning
that the Summit in Sydney will be only 3 days long, so it most likely be a
very tight schedule for some of the participants if we plan to do face to
face discussions there, as there will be a lot going on during t
On Wed, May 17, 2017 at 12:39 PM, Jesse Pretorius
wrote:
> On 5/17/17, 6:25 PM, "Major Hayden" wrote:
>
> 1) Should the openstack-ansible-security role be
> renamed to alleviate confusion?
>
> Sure, I’ve long thought that the name is misleading.
+1 definitely in favor of a rename
>
>So my questions are:
>
> 1) Should the openstack-ansible-security role be
> renamed to alleviate confusion?
+1 on the rename.
>
> 2) If it should be renamed, what's your suggestion?
How about linux-ansible-security?
>
>Thanks!
>
>- --
>Major Hayden
>
>[0]
>https://www.openstack.org/s
Hello,
tripleo-quickstart devmode [1] is used by TripleO developers to test unmerged
changes in review.openstack.org locally and reproduce the upstream TripleO CI.
Functionality has been added to tripleo-quickstart devmode to allow users to
run TripleO deployments on an OVB host cloud.
See the
Excerpts from Michał Jastrzębski's message of 2017-05-17 07:47:31 -0700:
> On 17 May 2017 at 04:14, Chris Dent wrote:
> > On Wed, 17 May 2017, Thierry Carrez wrote:
> >
> >> Back to container image world, if we refresh those images daily and they
> >> are not versioned or archived (basically you c
Hi everyone!
Just wanted to send the community some updates on the vision front and also
get a discussion with the members of the technical committee going here for
next steps on what we're up to with the TC Vision for 2019 [0].
A couple things:
1. We finished our feedback phase by closing the s
On 17 May 2017 at 11:04, Doug Hellmann wrote:
> Excerpts from Michał Jastrzębski's message of 2017-05-17 07:47:31 -0700:
>> On 17 May 2017 at 04:14, Chris Dent wrote:
>> > On Wed, 17 May 2017, Thierry Carrez wrote:
>> >
>> >> Back to container image world, if we refresh those images daily and the
On 05/15/2017 07:16 AM, Sean Dague wrote:
> We had a forum session in Boston on Postgresql and out of that agreed to
> the following steps forward:
>
> 1. explicitly warn in operator facing documentation that Postgresql is
> less supported than MySQL. This was deemed better than just removing
> do
On 17 May 2017 at 11:36, Michał Jastrzębski wrote:
> On 17 May 2017 at 11:04, Doug Hellmann wrote:
>> Excerpts from Michał Jastrzębski's message of 2017-05-17 07:47:31 -0700:
>>> On 17 May 2017 at 04:14, Chris Dent wrote:
>>> > On Wed, 17 May 2017, Thierry Carrez wrote:
>>> >
>>> >> Back to cont
Excerpts from Colette Alexander's message of 2017-05-17 14:29:07 -0400:
> Hi everyone!
>
> Just wanted to send the community some updates on the vision front and also
> get a discussion with the members of the technical committee going here for
> next steps on what we're up to with the TC Vision f
+1, thanks Zhu for your work.
2017-05-16 4:22 GMT-04:00 Andrea Frittoli :
> Hello team,
>
> I'm very pleased to propose Fanglei Zhu (zhufl) for Tempest core.
>
> Over the past two cycle Fanglei has been steadily contributing to Tempest
> and its community.
> She's done a great deal of work in maki
On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote:
[...]
> we need help with completing the migration to infra. If interested
> you can reach out to fungi (Infra team PTL) nor mrmartin (who
> currently helps with the transition work).
[...]
The main blocker for us right now is addressed b
On Wed, May 17, 2017 at 1:47 PM, Doug Hellmann wrote:
> The timeline depends on who signed up to do the next revision. Did
> we get someone to do that, yet, or are we still looking for a
> volunteer? (Note that I am not volunteering here, just asking for
> status.)
I believe John (johnthetubaguy
Excerpts from Michał Jastrzębski's message of 2017-05-17 11:36:40 -0700:
> On 17 May 2017 at 11:04, Doug Hellmann wrote:
>
> > You've presented some positive scenarios. Here's a worst case
> > situation that I'm worried about.
> >
> > Suppose in a few months the top several companies contributing
On 16/05/17 10:32, Lance Haig wrote:
What if instead of a directory per release, we just had a 'deprecated'
directory where we move stuff that is going away (e.g. anything
relying on OS::Glance::Image), and then deleted them when it
disappeared from any supported release (e.g. LBaaSv1 must be clo
I think that a rename is a good idea. Ansible-host-security,
Ansible-host-hardening, Ansible-server-security, etc... all good options.
--
MC
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
Folks-
As of [1], devstack will include color escapes in the default log
formats under systemd. Production deployments can emulate as they see fit.
Note that journalctl will strip those color escapes by default, which
is why we thought we lost log coloring with systemd. Turns ou
On 05/17/2017 04:50 PM, Eric Fried wrote:
> Folks-
>
> As of [1], devstack will include color escapes in the default log
> formats under systemd. Production deployments can emulate as they see fit.
>
> Note that journalctl will strip those color escapes by default, which
> is why we
Hello OpenStack-dev,
I am running Keystone in a virtual environment with LDAP backend.
When user_id_attribute is set to sn (and the LDAP directory is
configured accordingly),
`openstack user list --domain default --group test-group` results in
`Group member `userid` for group `f44a7fbb9e174ba58234
( I have been having a discussion with Adam Spiers on
[openstack-dev][vitrage][nova] on this topic ... thought I would switchover to
[masakari] )
I am interested in contributing an implementation of Intrusive Instance
Monitoring,
initially specifically VM Heartbeat / Heath-check Monitoring thru
On 5/17/2017 11:20 AM, Dmitry Tantsur wrote:
On 05/17/2017 05:34 PM, Chris Jones wrote:
Hey folks
I have a fairly simple proposal to make - I'd like to suggest that
Feature Freeze move to being much earlier in the release cycle (no
earlier than M.1 and no later than M.2 would be my preference).
Hi everyone,
It was great to meet you at the Boston summit and agree on the best way to
fix the 404 error code bug on geo-replicated clusters with write affinity.
As you know, this is a topic that is dear to us at Catalyst, and we would
like to provide a patch to it. Since we are relatively new t
Hi Bruno,
On Wed, May 17, 2017 at 3:47 PM, Bruno L wrote:
>
> I see multiple bugs in launchpad that are related to this issue.
>
AFAIK, only one bug for this issue is still open, and has the most recent
thoughts added from the Forum
https://bugs.launchpad.net/swift/+bug/1503161
write a brief
I missed the summit, so I also missed out on some of the decisions that were
made. I don’t feel that some of them were ideal, and in talking to the people
involved I’ve gotten various degrees of certainty about how settled things
were. So I’ve not only pushed a series of patches as POC code [0]
Hello, Spyros/
Thank you for your reply.
I executed "kubectl create" command in my openstack controller node.
I downloaded kubectl binary, it's version is 2.5.1.
Below are my steps.
1) install openstack newton by fuel 10.0
2) install magnum by source (master branch) in controller node
3) install
TripleO currently uses the default "loopback" docker storage device.
This is not recommended for production (see 'docker info').
We've been poking around with docker storage backends in TripleO for
almost 2 months now here:
https://review.openstack.org/#/c/451916/
For TripleO there are a couple
Be careful with overlay, I've seen it acting in a ways you don't want
it to act up. That was some time ago, but memories persist. To my
experience best option is btrfs. If you don't want to repartition
disk, btrfs on loopback isn't horrible too. deviemapper on loopback is
horrible, but that's diffe
I've only used btrfs and devicemapper on el7. btrfs has worked well.
devicemapper ate may data on multiple occasions. Is redhat supporting overlay
in the el7 kernels now?
Thanks,
Kevin
From: Dan Prince [dpri...@redhat.com]
Sent: Wednesday, May 17, 2017 5:
On 17/05/17 23:20, Sean Dague wrote:
> On 05/16/2017 07:34 PM, Adrian Turjak wrote:
>
>> Anyway that aside, I'm sold on API keys as a concept in this case
>> provided they are project owned rather than user owned, I just don't
>> think we should make them too unique, and we shouldn't be giving t
btrfs and direct-lvm is recommended for prod env.
overlay is bad.
On Thu, May 18, 2017 at 8:38 AM, Fox, Kevin M wrote:
> I've only used btrfs and devicemapper on el7. btrfs has worked well.
> devicemapper ate may data on multiple occasions. Is redhat supporting
> overlay in the el7 kernels now
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, May 18th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_May_18th_2017_.280900_UTC.29
An
On Thu, May 18, 2017 at 12:38 PM, Fox, Kevin M wrote:
> I've only used btrfs and devicemapper on el7. btrfs has worked well.
> devicemapper ate may data on multiple occasions. Is redhat supporting
> overlay in the el7 kernels now?
>
overlay2 is documented as a Technology Preview graph driver in
Hello folks
The gnocchi-api command allows running the API server usign a spefic port:
usage: gnocchi-api [-h] [--port PORT] -- [passed options]
positional arguments:
-- [passed options] '--' is the separator of the arguments used to start
the WSGI server and the argu
My experience with BTRFS has been flawless. My experience with overlayfs is
that occasionally (older centos kernels) returned as permissions
(rather the drwxrwrw). This most often happened after using the yum overlay
driver. I’ve found overlay to be pretty reliable as a “read-only” f
Hi,
On Thu, May 18, 2017 at 11:14:06AM +0800, Andres Alvarez wrote:
Hello folks
The gnocchi-api command allows running the API server usign a spefic port:
usage: gnocchi-api [-h] [--port PORT] -- [passed options]
positional arguments:
-- [passed options] '--' is the separator of the argume
Hi,
On Mon, May 15, 2017 at 01:01:57PM -0400, Zane Bitter wrote:
On 15/05/17 12:10, Steven Hardy wrote:
On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
Hi Steve,
I am happy to assist in any way to be honest.
It was great to meet you in Boston, and thanks very much for
volunteer
I do not need this functionality for production, but for testing. I think it
would be nice if we can specify the interface for the gnocchi-api even for
test purposes, just like the port.
--
View this message in context:
http://openstack.10931.n7.nabble.com/gnocchi-Running-Gnocchi-API-in-specifi
86 matches
Mail list logo
