IMHO it is important to keep plugin examples and keep testing them, very
valuable for plugin developers.
For example, I've encountered [0] the case where "plugin as role" feature
wasn't easily testable with fuel-qa because not compliant with the last
plugin data structure,
and more recently we've
Sergii,
I'm also curious, what about plugins which intend to be compatible with
both MOS 7 and MOS 8?
I've in mind the LMA plugins stable/0.8
BR
--
Swann
On Wed, Jan 20, 2016 at 8:34 PM, Sergii Golovatiuk wrote:
> Plugin master branch won't be compatible with older versions. Though the
> plugi
+2 to sergii
and btw create dedicated repos for plugin examples
On Wed, Sep 9, 2015 at 12:34 PM, Sergii Golovatiuk wrote:
> +1 to Simon
>
> Also the structure of fuel-plugin-builder should be refactored to
> community standards. everything in 'fuel_plugin_builder' directory should
> moved to to
within next
plugin framework releases.
If this effort can be made on the whole fuel internals and let plugins
enjoy it I would be happy.
do you have any pointers about these rumours, any BP ?
--
BR
Swann
> Regards,
> Igor
>
> On Mon, Sep 7, 2015 at 3:27 PM, Swann Croiset
> wrote:
&g
ugins, the LMA-Collector plugin must be
deployed/installed before LMA-Infrastructure-Alerting plugin (to avoid
false alerts UNKNOWN state) but the last may not be enabled for the
deployment.
Thanks,
> Igor
>
>
About tasks.yaml, we must support it until an equivalent 'deployment
Hi fuelers,
We're currently porting nearly all LMA plugins to the new plugin fwk 3.0.0
to leverage custom role capabilities.
That brings up a lot of simplifications for node assignment, disk
management, network config, reuse core tasks and so on .. thanks to the fwk.
However, we still need deploy
gt; +1
> Regards,
> Alex
>
> On Wed, Jul 22, 2015 at 2:42 PM, Irina Povolotskaya <
> ipovolotsk...@mirantis.com> wrote:
>
>> Hi to all,
>>
>> Swann Croiset reported a bug on Hiera nodes [1].
>>
> for history, Samuel Bartel encountered this bug, I
wrong :) so I
> would still suggest you to re-install with the last iso.
>
> Hope this will be helpful for you!
>
> [1] -
> https://github.com/stackforge/fuel-web/blob/master/docs/develop/nailgun/development/env.rst#running-nailgun-in-fake-mode
>
> On Thu, May 28, 2015 at
support 'none'
> action in their restrictions. Thank you for catching it!
> And we've prepared the *fix*: https://review.openstack.org/#/c/186049/. It
> should be merged ASAP.
>
> Best regards,
> Julia
>
> On Wed, May 27, 2015 at 5:57 PM, Swann Croiset
> wrote:
Folks,
With our plugin UI definition [0] I'm trying to use a restriction with
'action: "none"' to display a message but nothing happen.
According to the doc this should just works [1], btw I didn't find any
similar example on fuel-web/nailgun.
So I guess I hit a bug here or smth is wrong with plu
at 9:38 AM Jay Pipes wrote:
>
>> ++
>>
>> On 05/13/2015 11:57 AM, Swann Croiset wrote:
>> > Hi Fuelers,
>> >
>> > It would be valuable to configure the healthcheck middleware [0] for all
>> > services deployed by fuel, available since Kil
Hi,
first issue opened :)
On Fri, May 15, 2015 at 6:59 PM, Debojyoti Dutta wrote:
> Hi!
>
> Its a pleasure to introduce CephEWS, an awesome dashboard for Ceph with a
> twist - it has ceph health checks and warnings built in along with OSD and
> CRUSH map viz etc. https://github.com/CiscoSystems
Hi Fuelers,
It would be valuable to configure the healthcheck middleware [0] for all
services deployed by fuel, available since Kilo.
Several (obvious) benefits:
- Provide a common API for healthcheck across OpenStack services
- HAproxy performs more accurate HTTP checks for its backend status
-
Hi,
try to configure nova.conf:
[DEFAULT]
notification_driver=messaging
BR
2015-04-16 11:04 GMT+02:00 Eduard Matei :
>
>
> Hi,
>
> I've been trying to enable nova notifications on various actions, but
> nothing is actually sent.
> I found the cause in the _notify method
> of /usr/local/lib/pyt
Hi,
definitely nice to have an OS monitoring system alive with Fuel deployments!
I've some questions inline ..
thanks
2014-06-18 11:07 GMT+02:00 Alexander Kislitsky :
> 18.07.2014
>
> Participants:
> Szymon Banka,
> Bartek Kupidura,
> Dmitry Nikishov
> Alexander Kislitsky
>
> Discussed limitat
+1
2014-04-24 12:10 GMT+02:00 Dina Belova :
> I propose to add Pablo Andreas Fuente (pafuent on the IRC) to Climate core
> team.
>
> He's Python contributor from Intel, and he took great part in Climate
> development including design suggestions and great ideas. He has been
> quite active durin
Hi,
seems your ceilo api is either not started or you're using a bad hostname
(controller)
first you must check ceilo api log to valid that the service is well
started.
from where are you using the ceilo cli (I guess you use the cli)? is the
controller is accessible from here? , try to ping cont
Hi Ilya,
Interresting, thanks for sharing.
So the quick conclusion to your numbers seems indicated that mongodb is
more efficient for both reading and writing,
except for 2 cases for retrieving data (meters and resouces listing) ..
However for the reading operations,
it's should be confirmed (or
Hi Yuanjing,
some pointers inline.
2014-04-03 4:33 GMT+02:00 Yuanjing (D) :
> Hi
>
> I have a requirement of monitoring VMs, if a VM's meter like cpu_util
> become too high, then system generate an alarm for this VM with meter
> information.
>
> I have tested alarm function of ceilometer, be
Hi Nader,
These notifications must be handled by Ceilometer like others [1].
it is surprising that it does not already identity meters indeed...
probably nobody needs them before you.
I guess it remains to open a BP and code them like I recently did for Heat
[2]
http://docs.openstack.org/develop
Thanks Sandy to confirm the gap and pointing to me the CADF effort .. very
interresting with many impacts! I'll definitely follow that.
So I guess OpenStack can live with these notifications until we have better
things.
Anyway, I will be proposing may be a patch to oslo to temporarily fix this
..
Hi,
I won't be at office before Wednesday 5.
No need to switch for me, Sylvain will take my voice.
FYI, I'll continue the Belgium tour after Brussel : Gent for the
http://cfgmgmtcamp.eu/
2014-01-30 Dina Belova
> I'm ok with Tuesday 1500 UTC. We may go to #openstack-meeting-3 if we'll
> need
Hi stackers,
I would like to share my wonder here about Notifications.
I'm working [1] on Heat notifications and I noticed that :
1/ Heat uses his context to store 'password'
2/ Heat and Nova store 'auth_token' in context too. Didn't check for other
projects except for neutron which doesn't store
Hi,
Your result is interesting and not surprising due to the different design
you have described.
The Ceilo team will work on the improvements IIUC.
I found two relevant links [1] [2]
@jay : the first case seems to be impossible, no scalable .. I bet for the
last :)
@June li
I am curious to know
/meetingdetails.html?year=2013&month=10&day=28&hour=10&min=0&sec=0&p1=195&p2=166
-Sylvain
--
Swann Croiset
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
25 matches
Mail list logo
