Hello,
I'm using devstack to have openstack. I installed also monasca using the
following link:
https://github.com/openstack/monasca-api/tree/master/devstack
The problem is that when I log in from horizon, The openstack services and
servers are empty on the monitoring tab.
What should I do in or
Hi Amal,
The status buttons in the monitoring tab correspond to the alarm states for a
given service or node. After installing devstack plugin no alarms are defined
yet. You have to do it manually and alarms should appear.
Take care
Witek
From: amal kammoun
Hi All,
I'd like to propose a QA Dinner night for the QA team at the Dublin PTG. I
initiated a doodle vote [1] to choose Tuesday or Wednesday night.
NOTE: Anyone engaged in QA activities (not necessary to be QA core) are
welcome to join.
[1] https://doodle.com/poll/68fudz937v22ghnv
-gman
Hello everyone,
In my candidacy [1], I mentioned that the TC should provide more tools to help
the PTLs at their duties, for example to track community health.
I have questions for the TC candidates:
- What is your opinion about said toolkit? Do you see a purpose for it?
- Do you think said tool
Excerpts from [email protected]'s message of 2018-09-10 13:15:02 +0200:
> Hello everyone,
>
> In my candidacy [1], I mentioned that the TC should provide more tools to
> help the PTLs at their duties, for example to track community health.
>
> I have questions for the TC candidates:
> - Wh
As I'm not attending the PTG, I thought I might help put some words
against these questions for when you're having the meeting. Plus even if
I did want to be online, it would be something like 4am my time.
Stein will likely see a lot of Adjutant refactor work as I get myself
back onto the project
Hi,all
At first,I find it is supported that we can define hard performance
limits for each volume in doc.openstack.org[1].But only can define hard
performance limits for each volume type in fact. Another, the note"As of the
Nova 18.0.0 Rocky release, front end QoS settings are only suppo
On Mon, 10 Sep 2018 20:31:11 +0900 Doug Hellmann
wrote
> Excerpts from [email protected]'s message of 2018-09-10 13:15:02 +0200:
> > Hello everyone,
> >
> > In my candidacy [1], I mentioned that the TC should provide more tools to
> > help the PTLs at their duties, for ex
On Mon, Sep 10, 2018 at 5:31 AM Doug Hellmann wrote:
> Excerpts from [email protected]'s message of 2018-09-10 13:15:02
> +0200:
> > Hello everyone,
> >
> > In my candidacy [1], I mentioned that the TC should provide more tools
> to help the PTLs at their duties, for example to track commun
I think something we should take into consideration is *what* you consider
health because the way we’ve gone about it over health checks is not something
that can become a toolkit because it was more of question asking, etc
Sent from my iPhone
> On Sep 10, 2018, at 6:29 AM, Rico Lin wrote:
>
On 2018-09-10 06:38:11 -0600 (-0600), Mohammed Naser wrote:
> I think something we should take into consideration is *what* you
> consider health because the way we’ve gone about it over health
> checks is not something that can become a toolkit because it was
> more of question asking, etc
[...]
On 8/31/18 6:03 PM, Raoul Scarazzini wrote:
On 8/31/18 12:07 PM, Jiří Stránský wrote:
[...]
* "for humans" definition differs significantly based on who you ask.
E.g. my intention with [2] was to readily expose *more* knobs and tweaks
and be more transparent with the underlying workings of Ansib
Hi all,
Its been a long while since a "project update" type email about
StoryBoard, but over the past few months we merged some patches which
either are worth mentioning or changed things in ways that would benefit
from some explanation.
# Linking to projects by name
Keen observers might've not
Hi folks,
Last week I wrote a BluePrint and a spec [1] to propose to change the
way we used and managed the Plan in TripleO for the Deployment and the
Life cycle (update/upgrade and scale).
While I was working on trying to simplified the implementation of the
Update and Upgrade for a end user usa
On 2018-09-10 14:43:18 +0100 (+0100), Adam Coldrick wrote:
[...]
> # Linking to projects by name
>
> Keen observers might've noticed that StoryBoard recently grew the ability
> to link to projects by name, rather than by ID number. All the links to
> projects in the UI have been replaced with link
We had talked about Tuesday afternoon. I need to sync up with Lance and
figure out exactly when will work best.
On 09/08/2018 10:58 AM, Jay S Bryant wrote:
Ben,
Ping me when you are planning on having this discussion if you think of
it. Since there is interest in this for Cinder I would like
On 9/9/2018 1:11 PM, Ghanshyam Mann wrote:
Yeah, Tempest would not fit as best location for such tagging or whitelist. I
think nova may be better choice if nothing else.
OK I've thrown this on the nova ptg etherpad agenda [1] for a misc item
to talk about.
[1] https://etherpad.openstack.org
Hi Mathieu,
Thanks for bringing up the topic. There are several efforts currently in
progress which should lead to solving the problems you're describing. We
are working on introducing CLI commands which would perform the deployment
configuration operations on deployment plan in Swift. This is a m
On 10/09/18 10:34 AM, Jeremy Stanley wrote:
On 2018-09-10 14:43:18 +0100 (+0100), Adam Coldrick wrote:
[...]
# Linking to projects by name
Keen observers might've noticed that StoryBoard recently grew the ability
to link to projects by name, rather than by ID number. All the links to
projects i
There are more Topic to discuss for QA at last movement [1]. I have added them
in schedule and there are few topic has been re-scheduled due to that, please
check the latest schedule for QA topic here[2]
I have created the dedicated Etherpad for each topic, links are in main
Etherpad[1]. Reques
On Mon, 2018-09-10 at 12:14 -0400, Zane Bitter wrote:
> On 10/09/18 10:34 AM, Jeremy Stanley wrote:
> > On 2018-09-10 14:43:18 +0100 (+0100), Adam Coldrick wrote:
> > [...]
> > > # Linking to projects by name
> > >
> > > Keen observers might've noticed that StoryBoard recently grew the
> > > abili
Hi Senlin Stable Team,
I would like to nominate Yuanbin Chen (chenyb4) to the Senlin stable
review team. Yuanbin has been doing stable reviews and shown that he
understands the policy for merging stable patches [1].
Voting is open for 7 days. Please reply with your +1 vote in favor or
-1 as a vet
I just realized I booked the room and put it in the etherpad but
forgot to email out the time.
Time: Tuesday 09:00-10:45
Room: Big Thompson
https://etherpad.openstack.org/p/ansible-collaboration-denver-ptg
Thanks,
-Alex
On Tue, Sep 4, 2018 at 1:03 PM, Alex Schultz wrote:
> On Thu, Aug 9, 2018
Hi Senlin Core Team,
I would like to nominate 2 new core reviewers for Senlin:
[1] Jude Cross ([email protected])
[2] Erik Olof Gunnar Andersson ([email protected])
Jude has been doing a number of reviews and contributed some important
patches to Senlin during the Rocky cycle that resol
Hi All
As outgoing PTL I have the honour of organising the team dinner for the
Stein PTG this week.
I'm proposing Wednesday night at Russell's Smokehouse:
https://www.russellssmokehouse.com/
Let me know if you will be along (and if you have a +1) by end of today and
I'll make the reservation!
Sounds great James. Excellent choice of restaurant, I'm in! (My +1 will
probably be pre-occupied with other things that evening, so only count me
for the reservation)
On Mon, Sep 10, 2018 at 11:13 AM James Page
wrote:
> Hi All
>
> As outgoing PTL I have the honour of organising the team dinner
We had an extensive discussion of this in the keystone room today:
https://etherpad.openstack.org/p/keystone-stein-unified-limits
We had a couple of Nova people in the room, so if anyone from other
teams can take a look at the outcomes on the etherpad and let us know if
there are any issues wi
Melanie gave me the go-ahead to propose the patches, so here's the list
of patches for the zuul migration, doc job update, and python 3.6 unit
tests for the nova repositories.
+--++---+
| Subject
On 9/10/2018 7:17 AM, Rambo wrote:
Hi,all
At first,I find it is supported that we can define hard
performance limits for each volume in doc.openstack.org[1].But only
can define hard performance limits for each volume type in fact.
Another, the note"As of the Nova 18.0.0 Rocky release,
On 9/10/2018 11:14 AM, Zane Bitter wrote:
On 10/09/18 10:34 AM, Jeremy Stanley wrote:
On 2018-09-10 14:43:18 +0100 (+0100), Adam Coldrick wrote:
[...]
# Linking to projects by name
Keen observers might've noticed that StoryBoard recently grew the
ability
to link to projects by name, rather
On Mon, Sep 10, 2018 at 6:07 AM, Jeremy Stanley wrote:
> On 2018-09-10 06:38:11 -0600 (-0600), Mohammed Naser wrote:
>> I think something we should take into consideration is *what* you
>> consider health because the way we’ve gone about it over health
>> checks is not something that can become a
> On Mon, Sep 10, 2018 at 05:13:35AM +, [email protected] wrote:
>> Build failed.
>>
>> - publish-openstack-releasenotes
>> http://logs.openstack.org/c8/c89ca61fdcaf603a10750b289228b7f9a3597290/tag/publish-openstack-releasenotes/fbbd0fa/
>> : FAILURE in 4m 03s
The line that is causing this
All,
We have landed on a decision for the Cinder/Manila Dinner plan.
Here are the details:
Location: Casey's Bistro and Pub
* 7:30 pm Tuesday after the Happy Hour
* 7301 E 29th Ave, Denver, CO 80238
* Reservation for Amit
See you all there!
Jay
I agree in that it's dependent on what metrics you think accurately
showcase project health. Is it the number of contributions? The number of
unique contributors? Diversity across participating organizations?
Completion ratios of blueprints or committed fixes over bugs opened? I
imagine different p
I created a nova bug [1] to track a request that came up in the upgrades
SIG room at the PTG today [2] and would like to see if there is any
feedback from other operators/developers that weren't part of the
discussion.
The basic problem is that failing to archive/purge deleted records* from
t
-- Forwarded message -
From: Chris Morgan
Date: Mon, Sep 10, 2018, 5:55 PM
Subject: [Openstack-operators] revamped ops meetup day 2
To: OpenStack Operators , <
[email protected]>
Hi All,
We (ops meetups team) got several additional suggestions for ops meetups
s
Hi Searchlight team,
Because we don't have the team meeting this week so I'm planning to
organize the virtual PTG on 20th Sep, 12:00 UTC. Please join me on the IRC
channel (#openstack-searchlight) and find out an appropriate schedule. The
purposes of this meeting are:
- Talk to the team face-t
On Mon, Sep 10, 2018 at 10:12 AM Jiri Tomasek wrote:
>
> Hi Mathieu,
>
> Thanks for bringing up the topic. There are several efforts currently in
> progress which should lead to solving the problems you're describing. We are
> working on introducing CLI commands which would perform the deploymen
Octavia and Release teams,
I am adding Carlos Goncalves to the Octavia project release management
liaison list for Stein.
He will be assisting with regular stable branch release patches.
Let me know if you have any questions or concerns,
Michael
__
Excerpts from Michael Johnson's message of 2018-09-10 21:48:53 -0600:
> Octavia and Release teams,
>
> I am adding Carlos Goncalves to the Octavia project release management
> liaison list for Stein.
> He will be assisting with regular stable branch release patches.
>
> Let me know if you have an
On Tue, Sep 11, 2018 at 07:39:39AM +1000, Ian Wienand wrote:
> > On Mon, Sep 10, 2018 at 05:13:35AM +, [email protected] wrote:
> >> Build failed.
> >>
> >> - publish-openstack-releasenotes
> >> http://logs.openstack.org/c8/c89ca61fdcaf603a10750b289228b7f9a3597290/tag/publish-openstack-releas
On Wed, Sep 05, 2018 at 10:03:09AM -0500, Matthew Thode wrote:
> The requirements team has gone ahead and made a aweful hack to get gate
> unwedged. The commit message is a very good summary of our reasoning
> why it has to be this way for now. My comment explains our plan going
> forward (there
On Mon, Sep 10, 2018 at 05:58:21AM -0600, Doug Hellmann wrote:
> The python3 version of the job worked. I think both jobs ran because the
> repo is in the middle of its zuul settings transition and the cleanup
> patch hasn't merged yet. Since one of them worked, I think the published
> output sho
Howdy everyone,
Those of us involved in the placement extraction process sat down
together today to discuss the plan for openstack/placement governance.
We agreed on a set of criteria which we will use to determine when we
will switch the openstack/placement governance from the compute project
44 matches
Mail list logo
