+1
On 01/14/2015 07:34 PM, Robert Collins wrote:
+1
On 15 Jan 2015 07:15, Clint Byrum cl...@fewbar.com
mailto:cl...@fewbar.com wrote:
Hello! It has been a while since we expanded our review team. The
numbers aren't easy to read with recent dips caused by the summit and
Hello,
we call it from UI after the deployment
https://github.com/openstack/tuskar-ui/blob/master/tuskar_ui/infrastructure/overview/forms.py#L222
.
There should be conversation on the summit whether to do the call from
somewhere else (tuskar, template..).
Kind Regards,
Ladislav
On
1. os-apply-config: release: 0.1.22 -- 0.1.23
--https://pypi.python.org/pypi/os-apply-config/0.1.23
--
http://tarballs.openstack.org/os-apply-config/os-apply-config-0.1.23.tar.gz
2. os-refresh-config: release: 0.1.7 -- 0.1.8
+1
On 09/09/2014 08:32 PM, Gregory Haynes wrote:
Hello everyone!
I have been working on a meta-review of StevenK's reviews and I would
like to propose him as a new member of our core team.
As I'm sure many have noticed, he has been above our stats requirements
for several months now. More
On 08/20/2014 11:30 AM, Dougal Matthews wrote:
- Original Message -
From: Derek Higgins der...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Wednesday, 20 August, 2014 10:15:51 AM
Subject: Re: [openstack-dev]
Hello,
yes, this is a very needed change, so I'd vote for -2 everything unless
it's rebased to 105347.
Thank you for the patches.
Ladislav
On 08/01/2014 02:19 AM, Steve Baker wrote:
The changes to port tripleo-heat-templates to HOT have been rebased to
the current state and are ready to
Hi,
I believe you are looking for stack convergence in Heat. It's not fully
implemented yet AFAIK.
You can check it out here
https://blueprints.launchpad.net/heat/+spec/convergence
Hope it will help you.
Ladislav
On 07/23/2014 12:31 PM, Howley, Tom wrote:
(Resending to properly start new
Hello Steve,
the spec looks correct to me. Thanks for picking this up, it's very
needed, especially for Tuskar.
Let me know if you will need some help with testing it, or with anything
else.
Kind Regards,
Ladislav
On 04/30/2014 09:02 AM, Steve Kowalik wrote:
Hi,
I'm looking at
/2014 06:23 PM, Neal, Phil wrote:
From: Ladislav Smola [mailto:lsm...@redhat.com]
Sent: Wednesday, April 16, 2014 8:37 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [TripleO] [Tuskar] Undercloud Ceilometer
No response so far, but -1 on the image element for making Ceilometer
On 04/15/2014 08:44 PM, Robert Collins wrote:
I've been watching the nova process, and I think its working out well
- it certainly addresses:
- making design work visible
- being able to tell who has had input
- and providing clear feedback to the designers
I'd like to do the same thing
does it sound?
On 04/14/2014 01:31 PM, Ladislav Smola wrote:
Hello,
I am planning to add Ceilometer to Undercloud as default. Since
Tuskar-UI uses
it as primary source of metering samples and Tuskar should be in
Undercloud
as default, it made sense to me.
So is my assumption correct
Hello,
I am planning to add Ceilometer to Undercloud as default. Since
Tuskar-UI uses
it as primary source of metering samples and Tuskar should be in Undercloud
as default, it made sense to me.
So is my assumption correct or there are some reasons not to do this?
Here are the reviews, that
Hello,
we have used this list of steps for the demo on Fedora 20:
https://wiki.openstack.org/wiki/Tuskar/Devtest
The demo is running on one machine with 24GB RAM and 120GB disk. We are
using
virtualized baremetals(bm_poseur) for development.
KInd Regards,
Ladislav
On 04/10/2014 07:40 PM,
On 04/11/2014 01:03 PM, Thomas Goirand wrote:
On 04/11/2014 06:05 PM, Jaromir Coufal wrote:
On 2014/11/04 10:27, Thomas Goirand wrote:
On 04/10/2014 04:32 PM, Jaromir Coufal wrote:
Dear Stackers,
I am happy to announce that yesterday Tuskar UI (TripleO UI) has tagged
branch 0.1.0 for
+1 for the -core changes
jdon sounds like a pretty cool Mafia name, +1 for Don Jay
On 04/08/2014 09:10 AM, Tomas Sedovic wrote:
On 08/04/14 01:50, Robert Collins wrote:
tl;dr: 3 more core members to propose:
bnemec
greghaynes
jdon
-1, there's a typo in jdob's nick ;-)
In all seriousness, I
+1 to this:
nova:
config:
default.compute_manager:
ironic.nova.compute.manager.ClusterComputeManager
cells.driver: nova.cells.rpc_driver.CellsRPCDriver
Adding a generic mechanism like this and having everything configurable
seems like a best option to me.
On 04/08/2014 01:51
Thanks Mainn for putting this together, looks like a fairly precise list
of things
we need to do in J.
On 04/07/2014 03:36 PM, Tzu-Mainn Chen wrote:
Hi all,
One of the topics of discussion during the TripleO midcycle meetup a few weeks
ago was the direction we'd like to take Tuskar during
On 04/06/2014 11:27 PM, Steve Baker wrote:
On 05/04/14 04:47, Tomas Sedovic wrote:
Hi All,
I was wondering if the time has come to document what exactly are we
doing with tripleo-heat-templates and merge.py[1], figure out what needs
to happen to move away and raise the necessary blueprints on
+1
On 04/03/2014 01:02 PM, Robert Collins wrote:
Getting back in the swing of things...
Hi,
like most OpenStack projects we need to keep the core team up to
date: folk who are not regularly reviewing will lose context over
time, and new folk who have been reviewing regularly should be
On 03/06/2014 04:47 AM, Jason Rist wrote:
On Wed 05 Mar 2014 03:36:22 PM MST, Lyle, David wrote:
I'd like to nominate Radomir Dopieralski to Horizon Core. I find his reviews
very insightful and more importantly have come to rely on their quality. He has
contributed to several areas in
On 02/27/2014 05:02 PM, Ana Krivokapic wrote:
On 02/27/2014 04:41 PM, Tzu-Mainn Chen wrote:
Hello,
I think if we will use Openstack CLI, it has to be something like this
https://github.com/dtroyer/python-oscplugin.
Otherwise we are not Openstack on Openstack.
Btw. abstracting it all to one
On 02/27/2014 04:30 PM, Dougal Matthews wrote:
On 27/02/14 15:08, Ladislav Smola wrote:
Hello,
I think if we will use Openstack CLI, it has to be something like this
https://github.com/dtroyer/python-oscplugin.
Otherwise we are not Openstack on Openstack.
Btw. abstracting it all to one big
Hello,
I think if we will use Openstack CLI, it has to be something like this
https://github.com/dtroyer/python-oscplugin.
Otherwise we are not Openstack on Openstack.
Btw. abstracting it all to one big CLI will be just more confusing when
people will debug issues. So it would
have to be
On 02/23/2014 01:16 AM, Clint Byrum wrote:
Excerpts from Imre Farkas's message of 2014-02-20 15:24:17 +:
On 02/20/2014 03:57 PM, Tomas Sedovic wrote:
On 20/02/14 15:41, Radomir Dopieralski wrote:
On 20/02/14 15:00, Tomas Sedovic wrote:
Are we even sure we need to store the passwords in
Hello,
I would like to have your opinion about how to deal with passwords in
Tuskar-API
The background is, that tuskarAPI is storing heat template parameters in
its database, it's a
preparation for more complex workflows, when we will need to store the
data before the actual
heat
On 02/19/2014 08:05 PM, Dougal Matthews wrote:
On 19/02/14 18:49, Hugh O. Brock wrote:
On Wed, Feb 19, 2014 at 06:31:47PM +, Dougal Matthews wrote:
On 19/02/14 18:29, Jason Rist wrote:
Would it be possible to create some token for use throughout? Forgive
my naivete.
I don't think so,
On 02/19/2014 06:29 PM, Dougal Matthews wrote:
On 19/02/14 17:10, Ladislav Smola wrote:
Hello,
I would like to have your opinion about how to deal with passwords in
Tuskar-API
The background is, that tuskarAPI is storing heat template parameters in
its database, it's a
preparation for more
Hello,
+1 to 'let's work towards having a single Node Profile (flavor)
associated with each Deployment Role (pages 12 13 of the latest
mockups[1])'
Good start.
We could have also more flavors per role now, user just would have to be
advised: You are using one image for multiple hardware,
On 01/30/2014 12:39 PM, Jiří Stránský wrote:
On 01/30/2014 11:26 AM, Tomas Sedovic wrote:
1.1 Treat similar hardware configuration as equal
The way I understand it is this: we use a scheduler filter that wouldn't
do a strict match on the hardware in Ironic. E.g. if our baremetal
flavour said
Hello,
excellent, this is exactly what we need in Tuskar. :-)
Might be good to monitor it via SNMPD. As this daemon will be
already running on each node. And I see it should be possible, though
not very popular.
Then it would be nice to have the data stored in Ceilometer, as
it provides
Hello,
seems like there is no pushback against decrypting in Javascript. So
unless somebody has something against, I guess it is fine.
I would say that it can be the best, to have both client side decrypting
using JS and server side using Nova. We can let the user decide what to use.
On 01/15/2014 10:53 AM, Jaromir Coufal wrote:
On 2014/13/01 13:15, Ladislav Smola wrote:
The usage of roles is new metric which doesn't exist. It is the most
consumed HW resource (which means if CPU is consumed by 60 % and RAM
or disk are less, then the role usage is 60 %). It would be great
Hello,
some answers below:
On 01/10/2014 05:18 PM, Jay Dobies wrote:
Thanks for recording this. A few questions:
- I'm guessing the capacity metrics will come from Ceilometer. Will
Ceilometer provide the averages for the role or is that calculated by
Tuskar?
Definitely Ceilometer, though
Hi,
some answers inline:
On 01/13/2014 10:47 AM, Jaromir Coufal wrote:
Hi Jay,
thanks for your questions, they are great. I am going to answer inline:
On 2014/10/01 17:18, Jay Dobies wrote:
Thanks for recording this. A few questions:
- I'm guessing the capacity metrics will come from
On 12/20/2013 05:51 PM, Clint Byrum wrote:
Excerpts from Ladislav Smola's message of 2013-12-20 05:48:40 -0800:
On 12/20/2013 02:37 PM, Imre Farkas wrote:
On 12/20/2013 12:25 PM, Ladislav Smola wrote:
2. Heat stack create, update
This is locked in the process of the operation, so nobody can
and +1 also from me :-)
Seems like this the way we want to go. So, what will be the next steps?
Seems like this have to be done by cooperation of PTL's of Horizon and
TripleO and ttx probably?
Thank you,
Ladislav
On 12/19/2013 05:29 PM, Lyle, David wrote:
So after a lot of consideration,
May I propose we keep the conversation Icehouse related. I don't think
we can make any sort of locking
mechanism in I.
Though it would be worth of creating some WikiPage that would present it
whole in some consistent
manner. I am kind of lost in these emails. :-)
So, what do you thing are
On 12/20/2013 01:04 PM, Radomir Dopieralski wrote:
On 20/12/13 12:25, Ladislav Smola wrote:
May I propose we keep the conversation Icehouse related. I don't think
we can make any sort of locking
mechanism in I.
By getting rid of tuskar-api and putting all the logic higher up, we are
forfeiting
On 12/20/2013 02:06 PM, Radomir Dopieralski wrote:
On 20/12/13 13:04, Radomir Dopieralski wrote:
[snip]
I have just learned that tuskar-api stays, so my whole ranting is just a
waste of all our time. Sorry about that.
Hehe. :-)
Ok after the last meeting we are ready to say what goes to
On 12/20/2013 02:37 PM, Imre Farkas wrote:
On 12/20/2013 12:25 PM, Ladislav Smola wrote:
2. Heat stack create, update
This is locked in the process of the operation, so nobody can mess with
it while it is updating or creating.
Once we will pack all operations that are now aside in this, we
On 12/17/2013 04:20 PM, Tzu-Mainn Chen wrote:
On 2013/13/12 23:11, Jordan OMara wrote:
On 13/12/13 16:20 +1300, Robert Collins wrote:
However, on instance - 'instance' is a very well defined term in Nova
and thus OpenStack: Nova boot gets you an instance, nova delete gets
rid of an instance,
On 12/16/2013 08:48 PM, Jay Dobies wrote:
On 12/13/2013 01:53 PM, Tzu-Mainn Chen wrote:
On 2013/13/12 11:20, Tzu-Mainn Chen wrote:
These look good! Quick question - can you explain the purpose of Node
Tags? Are they
an additional way to filter nodes through nova-scheduler (is that even
Horizoners,
As an alternative merge option, we could merge directly to Horizon code
base. After some conversation, we have realized that it is possible to
mix codebase of incubated and integrated projects, as Trove showed us.
Contrary to what was said in the last meeting, we do not require
Horizoners,
As discussed in TripleO and Horizon meetings, we are proposing to move
Tuskar UI under the Horizon umbrella. Since we are building our UI
solution on top of Horizon, we think this is a good fit. It will allow
us to get feedback and reviews from the appropriate group of developers.
On 12/11/2013 08:59 PM, James Slagle wrote:
This is really helpful, thanks for pulling it together.
comment inline...
On Wed, Dec 11, 2013 at 2:15 PM, Tzu-Mainn Chen tzuma...@redhat.com wrote:
* NODE a physical general purpose machine capable of running in many roles.
Some nodes may have
Agree with this.
Though I am an optimist, I believe that this time, we can avoid calling
multiple services in one request that depend on each other.
About the multiple users at once, this should be solved inside the API
calls of the services.
So I think we should forbid building these
+1 for Tatiana Mazur to Horizon Core
not sure if only cores should do the vote, but Tatiana has been very
active, so it will be well deserved. :-)
On 12/11/2013 01:09 PM, Jiri Tomasek wrote:
+1 for Tatiana Mazur to Horizon Core
On 12/10/2013 09:24 PM, Lyle, David wrote:
I would like to
Hi,
thanks for starting this conversation.
I will take it little side ways. I think we should be asking why have we
needed the tuskar-api. It has done some more complex logic (e.g.
building a heat template) or storing additional info, not supported by
the services we use (like rack
On 12/11/2013 04:35 PM, James Slagle wrote:
On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský ji...@redhat.com wrote:
Hi all,
TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI
for managing the deployment providing the same fundamental features as UI.
With the planned
On 12/05/2013 03:01 PM, James Slagle wrote:
On Wed, Dec 4, 2013 at 2:10 PM, Robert Collins
robe...@robertcollins.net wrote:
On 5 December 2013 06:55, James Slagle james.sla...@gmail.com wrote:
On Wed, Dec 4, 2013 at 2:12 AM, Robert Collins
Jan, Jordan, Martyn, Jiri and Jaromir are still
On 12/05/2013 11:40 AM, Jan Provaznik wrote:
On 12/04/2013 08:12 AM, Robert Collins wrote:
And the 90 day not-active-enough status:
| jprovazn **| 220 5 10 7 177.3% | 2 (
9.1%) |
|jomara ** | 210 2 4 15 1190.5% | 2 (
9.5%) |
|
On 12/06/2013 09:56 AM, Jaromir Coufal wrote:
On 2013/04/12 08:12, Robert Collins wrote:
Hi,
like most OpenStack projects we need to keep the core team up to
date: folk who are not regularly reviewing will lose context over
time, and new folk who have been reviewing regularly should be
On 12/06/2013 05:36 PM, Ben Nemec wrote:
On 2013-12-06 03:22, Ladislav Smola wrote:
On 12/06/2013 09:56 AM, Jaromir Coufal wrote:
On 2013/04/12 08:12, Robert Collins wrote:
Hi,
like most OpenStack projects we need to keep the core team up to
date: folk who are not regularly reviewing
Hello,
+1 to core update. There are still enough Tuskar-UI guys in the core
team I think.
Ladislav
On 12/04/2013 08:12 AM, Robert Collins wrote:
Hi,
like most OpenStack projects we need to keep the core team up to
date: folk who are not regularly reviewing will lose context over
time,
Hello,
so what is the plan? Tuskar-UI stays in tripleo until tripleo is part of
the integrated release?
Thanks,
Ladislav
On 12/04/2013 08:44 PM, Lyle, David wrote:
On 5 December 2013 12:10, Robert Collins robe...@robertcollins.net wrote:
-snip-
That said, perhaps we should review these
Hello,
just few notes from me:
https://etherpad.openstack.org/p/tripleo-feature-map sounds like a great
idea, we should go through them one by one maybe on meeting.
We should agree on what is doable for I, without violating the Openstack
way in some very ugly way. So do we want to be
Hello Daisy,
the tables were deleted from Horizon, because of that confusion.
https://bugs.launchpad.net/horizon/+bug/1249279
We are going to clearly document each ceilometer meter first. Then this
information will appear again in Horizon.
E.g. the duration as stated in doc
Hello,
seems too big to do the inline comments, so just a few notes here:
If we truly want to have Templates portable, it would mean to have the
'metadata' somehow standardised, right?
Otherwise if every UI will add their own metadata, then I hardly see the
templates as portable. I think
Hello,
as long as node won't be Production dependency, it shouldn't be a
problem, right? I give +1 to that
Regards
Ladislav
On 11/20/2013 05:01 PM, Maxime Vidori wrote:
Hi all, I know it is pretty annoying but I have to resurrect this subject.
With the integration of Angularjs into Horizon
Ok, I'll try to summarize what will be done in the near future for
Undercloud monitoring.
1. There will be Central agent running on the same host(hosts once the
central agent horizontal scaling is finished) as Ironic
2. It will have SNMP pollster, SNMP pollster will be able to get list of
consumption?
On 19 November 2013 20:05, Ladislav Smola lsm...@redhat.com
mailto:lsm...@redhat.com wrote:
Hello,
Seems like only mongo supports the kind of aggregation the
resource usage page needs.I have just
figured that myself today, though the exception is not caught
Hello,
Seems like only mongo supports the kind of aggregation the resource
usage page needs.I have just
figured that myself today, though the exception is not caught correctly
in the Horizon, as i have noticed.
It has to be fixed so it properly shows the error.
Kind regards,
Ladislav
Hi,
+1000 Excellent
I am really excited about having a heavily tested proper client-side
layer. This
is very needed, given that amount of javascript in Horizon is rising.
The hacked
together libraries in JQuery, that are there now are very hard to orient
in and will
be hard to maintain in the
On 10/08/2013 10:27 AM, Robert Collins wrote:
Perhaps the best thing to do here is to get tuskar-ui to be part of
the horizon program, and utilise it's review team?
This is planned. But it wont happen soon.
On 8 October 2013 19:31, Tzu-Mainn Chen tzuma...@redhat.com wrote:
Hi, like most
Hi,
seems like not all people agrees on what should be the 'metric' of a
core reviewer.
Also what justify us to give +1 or +2.
Could it be a topic on today's meeting?
Ladislav
On 10/07/2013 09:03 PM, Robert Collins wrote:
Hi, like most OpenStack projects we need to keep the core team up
Hello Clint,
thank you for your feedback.
On 10/04/2013 06:08 PM, Clint Byrum wrote:
Excerpts from Ladislav Smola's message of 2013-10-04 08:28:22 -0700:
Hello,
just a few words about role of Ceilometer in the Undercloud and the work
in progress.
Why we need Ceilometer in Undercloud:
Hello Chris,
That would be much appreciated, thank you. :-)
Kind Regards,
Ladislav
On 10/05/2013 12:12 AM, Chris Jones wrote:
Hi
On 4 October 2013 16:28, Ladislav Smola lsm...@redhat.com
mailto:lsm...@redhat.com wrote:
test it. Anybody volunteers for this task? There will be a hard
Hello,
just a few words about role of Ceilometer in the Undercloud and the work
in progress.
Why we need Ceilometer in Undercloud:
---
In Tuskar-UI, we will display number of statistics, that will show
Undercloud metrics.
Later also number of
2013, Ladislav Smola wrote:
Yes it would be good if something like this would be supported. -
relation of alarm to multiple entities, that
are result of sample-api query. Could it be worth creating a BP?
Probably indeed.
--
Julien Danjou
# Free Software hacker # independent consultant
# http
On 09/25/2013 01:51 AM, Gabriel Hurley wrote
4. There is a thought about tagging the alarms by user defined tag, so
user can easily group alarms together and then watch them together
based on their tag.
The alarm API don't provide that directly, but you can imagine some sort of
filter based on
Liz,
thank you very much for this, I will try to sort this and pick the ones,
that will need to be implemented in Ceilometer. Will comment the etherpad.
FYI there are only two Agents, that collects Hardware related data now.
This one is almost complete:
Hello everyone,
I am in the process of implementing Ceilometer Alarm API. Here are the
blueprints.
https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-api
https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-management-page
While I am waiting for some Ceilometer
On 09/19/2013 10:08 AM, Tomas Sedovic wrote:
Hi everyone,
Some of us Tuskar developers have had the chance to meet the TripleO
developers face to face and discuss the visions and goals of our
projects.
Tuskar's ultimate goal is to have to a full OpenStack management
solution: letting the
will be
queried from Overcloud Ceilometer
Missing metrics
* System load -- see /proc/loadavg (percentage)
as described here
https://blueprints.launchpad.net/ceilometer/+spec/monitoring-physical-devices
On 09/16/2013 04:10 PM, Ladislav Smola wrote:
Hello,
this is follow up
Hello,
this is follow up of T.Sedovic old email, trying to identify all
metrics, we will need to track for Tuskar.
The Ceilometer API for Horizon is now in progress, so we have time to
finish the list of metrics
and alarms we need. That may also raise the requests for some Ceilometer
API
The Rickshaw library is in the Master. Building of the reusable charts
on top of it is in the progress.
On 08/27/2013 02:51 PM, Chmouel Boudjnah wrote:
Julien Danjou jul...@danjou.info writes:
It sounds like a good plan to pick Rickshaw. Better building on top of
it, contributing back to it,
I have prepared the testing implementation of Rickshaw wrapped into a
general linechart and connected it to Ceilometer here:
https://review.openstack.org/#/c/35590/
(rendering is mostly copied from examples with some parts from Maxime
Vidori)
Rickshaw really works like a charm. I think it
77 matches
Mail list logo
