Hi Matthew,
I¹m interested to help in this switch to python logging framework for
shipping to logstash/etc. Are you working on a blueprint for this?
Cheers,
Cristian
On 27/01/14 11:07, "Macdonald-Wallace, Matthew"
wrote:
>Hi Sean,
>
>I'm currently working on moving away from the "built-in" lo
Module's "ini" configuration format.
>
>Hope that helps,
>
>Matt
>
>> -Original Message-
>> From: Sanchez, Cristian A [mailto:cristian.a.sanc...@intel.com]
>> Sent: 29 January 2014 17:57
>> To: OpenStack Development Mailing List
>
> -Sean
>
>On 01/30/2014 09:07 AM, Macdonald-Wallace, Matthew wrote:
>> No idea, I only really work on Nova, but as this is in Oslo I expect so!
>>
>> Matt
>>
>>> -Original Message-
>>> From: Sanchez, Cristian A [mailto:cristian.
Hi,
I’m planning to use oslo.notify mechanisms to implement a climate blueprint:
https://blueprints.launchpad.net/climate/+spec/notifications. Ideally, the
notifications sent by climate should be received by multiple services
subscribed to the same topic. Is that possible with oslo.notify? And m
Hi,
We’ve modified the openstack-commons.conf file for climate remove rpc and
notifier modules. But when the update.py is executed, the notifier and rpc
modules are still copied. Do you know what could be wrong?
Here you can see a log showing this situation:
http://paste.openstack.org/show/6467
I¹m kind of new in Openstack.
+1 to this
On 12/02/14 15:00, "Sandy Walsh" wrote:
>At the Nova mid-cycle meetup we've been talking about the problem of
>helping new contributors. It got into a discussion of karma, code
>reviews, bug fixes and establishing a name for yourself before screaming
>i
I agree with Bauza that the main purpose of Climate is to reserve resources,
and in the case of keystone it should reserve tenant, users, domains, etc.
So, it could be possible that climate is not the module in which the tenant
“lease” information should be saved. As stated in the use case, the
Hi,
I’m thinking about creating a blueprint to allow the creating of tenants
defining start-date and end-date of that tenant. These dates will define a time
window in which the tenant is considered ‘enabled’ and auth tokens will be
given only when current time is between those dates.
This can be
Provided we consider some projects as 'reservable', we could say this should be
a Climate API endpoint like CRUD /project/ and up to the admin responsability
to populate it.
If we say that new projects should automatically be 'reservable', that's only
policy from Climate to whiteboard these.
S
+1 to Dina on the workflow
From: Dina Belova mailto:dbel...@mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: martes, 25 de febrero de 2014 13:42
To: "OpenStack Development Mailing List (not for usage questions
One question to clarify: the project will be marked as reservable by calling
Keystone API (from Climate) to store that info in the project extra specs in
Keystone DB.
Is this correct?
From: Sylvain Bauza mailto:sylvain.ba...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usag
hanks,
Dina
On Mon, Feb 24, 2014 at 5:25 PM, Sanchez, Cristian A
mailto:cristian.a.sanc...@intel.com>> wrote:
Hi,
I’m thinking about creating a blueprint to allow the creating of tenants
defining start-date and end-date of that tenant. These dates will define a time
window in which the t
l user
in future. But to work with projects we still need admin's rights.
Any ideas?
On Wednesday, February 26, 2014, Dina Belova
mailto:dbel...@mirantis.com>> wrote:
Don't think it's needed in this case. We may store this info in Climate not to
intersect with Keystone
Congratulations Pablo!
From: Sylvain Bauza mailto:sylvain.ba...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: jueves, 24 de abril de 2014 10:16
To: "OpenStack Development Mailing List (not for usage questions)
Hi Rob,
Could you please point me where the spec repo is?
Thanks
--Cristian
On 19/05/14 22:46, "Robert Collins" wrote:
>Hey everyone, it was great to see many of you at the summit - if you
>were there and we didn't get time to say hello, then hopefully in
>Paris we can do that ;)
>
>I'd like e
Thanks
On 20/05/14 12:43, "Chris Jones" wrote:
>Hi
>
>On 20 May 2014, at 16:25, Sanchez, Cristian A
> wrote:
>
>> Could you please point me where the spec repo is?
>
>http://git.openstack.org/cgit/opensta
Hi,
In our team we’re planning to make some contributions to TripleO, after we met
with Robert Collins in an Intel hosted meeting during Summit.
As our first step we want to use TripleO to deploy the under-cloud and
over-cloud. Is there some instructions of how to start with this?
Thanks
Cristi
Excellent, thank you
On 21/05/14 17:31, "Jason Rist" wrote:
>On 05/21/2014 02:22 PM, Sanchez, Cristian A wrote:
>> Hi,
>> In our team we¹re planning to make some contributions to TripleO, after
>>we met with Robert Collins in an Intel hosted meeting during Summi
Hi Clint,
Please count me in.
Cristian
On 22/05/14 19:24, "Clint Byrum" wrote:
>Ahoy there, TripleO interested parties. In the last few months, we've
>gotten a relatively robust, though not nearly complete, CI system for
>TripleO. It is a bit unorthodox, as we have a strong desire to ensure
>P
Hi,
Going back to the original message, how do you think we should proceed
with this bug? (https://review.openstack.org/#/c/55588/). Shall a new one
be created to remove the deprecated environment variables in all clients?
Thanks
Cristian
On 11/11/13 16:56, "Kevin L. Mitchell"
wrote:
>On Mon
20 matches
Mail list logo
