Re: [openstack-dev] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

Not sure what snippet you mean but here are all the logs for the failed
test run:
http://packages.cloudfounders.com/ci_logs/01/213501/3/check/dsvm-tempest-full/37aa6fe/
(console.html and c-vol.txt show more details).

Thanks,
Eduard
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [third-party-ci]Tests randomly failing because of lvm

[Abhishek Shrivastava]

Hi Eduard,

Can you please send the snippet of failed tests along with their error
cause from your Build Logs.

On Mon, Aug 17, 2015 at 12:02 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi,
>
> I'm working on getting our CI working again, and i left it running over
> the weekend.
> Of the 50 jobs it ran. 6 of them failed because of different tests failed,
> but all with the same cause
> "tempest.exceptions.VolumeBuildErrorException"
>
> Looking in c-vol log i see "Volume group "stack-volumes-lvmdriver-1" has
> insufficient free space (1023 extents): 1024 required.\n'" (for that test)
>
> I have VOLUME_BACKING_FILE_SIZE=32G
> and i checked vgdisplay and it shows:
>
> sudo vgdisplay
>
> --- Volume group ---
>
> VG Name   stack-volumes-lvmdriver-1
>
> ...
>
> VG Size   32.00 GiB
>
> Total PE  8191
>
>
> How can i fix this?
>
>
> Thanks,
>
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 


*Thanks & Regards,*
*Abhishek*
*Cloudbyte Inc. *
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

I'm working on getting our CI working again, and i left it running over the
weekend.
Of the 50 jobs it ran. 6 of them failed because of different tests failed,
but all with the same cause
"tempest.exceptions.VolumeBuildErrorException"

Looking in c-vol log i see "Volume group "stack-volumes-lvmdriver-1" has
insufficient free space (1023 extents): 1024 required.\n'" (for that test)

I have VOLUME_BACKING_FILE_SIZE=32G
and i checked vgdisplay and it shows:

sudo vgdisplay

--- Volume group ---

VG Name   stack-volumes-lvmdriver-1

...

VG Size   32.00 GiB

Total PE  8191


How can i fix this?


Thanks,


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

[Gandhi, Kunal]

Hi all 

I have included the architecture diagram and an er diagram in the pull request 
below. It would great if you all could provide some feedback on it.

https://github.com/gslb/gslb-specs/pull/4 


Regards
Kunal



> On Aug 4, 2015, at 5:40 AM, Hayes, Graham  wrote:
> 
> Sure, we need the other cores to merge it - I cannot merge my own change.
> 
> If you are OK with the current version, you can leave a comment on the
> pull request, which helps cores decide if the PR is ready.
> 
> Thanks,
> 
> Graham
> 
> On 03/08/15 18:10, Gandhi, Kunal wrote:
>> Hi Graham,
>> 
>> Can we have your GSLB pull request merged to the
>> repo https://github.com/gslb/gslb-specs/pull/1/files ? I would like to
>> send another pull request based on these changes.
>> 
>> Regards
>> Kunal
>> 
>> 
>>> On Jun 30, 2015, at 8:38 AM, Hayes, Graham >> > wrote:
>>> 
>>> I have started to put together a working draft of an API here:
>>> 
>>> https://docs.google.com/document/d/1nw5jVn0hjmhlhkZJAohx-gqRkkbVhMMJ79Pogd0ysEk/edit?usp=sharing
>>> 
>>> I would suggest we skip this weeks meeting, and review this doc, and
>>> circle back next week?
>>> 
>>> I have opened it for comment, and I will add anyone who sends on their
>>> email to the editors list.
>>> 
>>> Thanks,
>>> 
>>> Graham
>>> 
>>> On 24/06/15 15:16, Samuel Bercovici wrote:
 Great!
 
 Thanks you. I have missed this one.
 
 *From:*Gandhi, Kunal [mailto:kunalhgan...@gmail.com]
 *Sent:* Wednesday, June 24, 2015 12:21 PM
 *To:* OpenStack Development Mailing List (not for usage questions)
 *Subject:* Re: [openstack-dev] [designate] and [lbaas] - GSLB API and
 backend support
 
 Hi Sam
 
 Yes. we discussed the use cases 2 weeks ago on irc. The IRC logs can be
 found here
 http://eavesdrop.openstack.org/meetings/gslb/2015/gslb.2015-06-09-16.00.log.html
 
 and the use case document can be found here
 https://docs.google.com/document/d/1016shVnPaK8l8HxMpjADiYtY2O94p4g7JxjuIA-qv7w/edit?usp=sharing
 
 Regards
 
 Kunal
 
   On Jun 24, 2015, at 12:35 AM, Samuel Bercovici >>>   > wrote:
 
   Hi Kunal,
 
   Did you also include use cases per our last discussion on IRC?
   I prefer to start with use cases before we dive into APIs.
 
   Thanks,
   -Sam.
 
 
   -Original Message-
   From: Gandhi, Kunal [mailto:kunalhgan...@gmail.com]
   Sent: Wednesday, June 24, 2015 6:47 AM
   To: OpenStack Development Mailing List (not for usage questions)
   Subject: Re: [openstack-dev] [designate] and [lbaas] - GSLB API and
   backend support
 
   Hi All,
 
   I have a very draft for the GSLB API and would like to upload it
   somewhere for discussion. What is the best place to upload and
   collaborate the draft ? Since the API docs have a lot of JSON
   payloads in it, I am not sure whether Google Docs will be
   appropriate for that.
 
   Regards
   Kunal
 
 
   On Jun 15, 2015, at 10:03 PM, Doug Wiegley
   mailto:doug...@parksidesoftware.com>>
   wrote:
 
   Hi all,
 
   We don’t have a rough draft API doc yet, so I’m suggesting that we
   postpone tomorrow morning’s meeting until next week. Does anyone
   have any other agenda items, or want the meeting tomorrow?
 
   Thanks,
   doug
 
 
 
   On Jun 2, 2015, at 10:52 AM, Doug Wiegley
   mailto:doug...@parksidesoftware.com>>
   wrote:
 
   Hi all,
 
   The initial meeting logs can be found at
   http://eavesdrop.openstack.org/meetings/gslb/2015/ , and we will be
   having another meeting next week, same time, same channel.
 
   Thanks,
   doug
 
 
 
   On May 31, 2015, at 1:27 AM, Samuel Bercovici >>>   > wrote:
 
   Good for me - Tuesday at 1600UTC
 
 
   -Original Message-
   From: Doug Wiegley [mailto:doug...@parksidesoftware.com]
   Sent: Thursday, May 28, 2015 10:37 PM
   To: OpenStack Development Mailing List (not for usage questions)
   Subject: Re: [openstack-dev] [designate] and [lbaas] - GSLB API and
   backend support
 
 
 
   On May 28, 2015, at 12:47 PM, Hayes, Graham >>>   > wrote:
 
   On 28/05/15 19:38, Adam Harwell wrote:
 
   I haven't seen any responses from my team yet, but I know we'd be
   interested as well - we have done quite a bit of work on this in
   the past, including dealing with the Designate team on this very
   subject.
   We can be available most hours between 9am-6pm Monday-Friday CST.
 
   --Adam
 
   https://keybase.io/rm_you
 
 
   From: Rakesh Saha >>>   

Re: [openstack-dev] [TaskFlow] Cross-run persistence

[Demian Brecht]

> On Aug 12, 2015, at 12:49 PM, Joshua Harlow  wrote:
> 
> possibly submit some kind of oslo-spec or
> blueprint for 'selective persistence' (or other better named thing); if
> u want to work on said code, that's even better :)

Cheers, will do.. Once I get legal approval from work to contribute.

---
GPG Fingerprint: 9530 B4AF 551B F3CD A45C  476C D4E5 662D DB97 69E3




signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] What's the best way to deploy openstack on XenServer for production?

[Young Yang]

Hi,

I'm trying to use openstack to manage Xenserver.
I've read https://wiki.openstack.org/wiki/XenServer/GettingStarted

It says
"This is an opinionated guide to setting up an OpenStack Cloud using
Xen/XenServer. Use this to get started quickly. It is far from the only way
to setup OpenStack using Xen."


And it warns
"Warning
This is still a work in progress."


It recommend devstack to deploy XenServer.
However,  [devstack](
https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md)
says
"The purpose of the code in this directory it to help developers bootstrap
a XenServer 6.2 (older versions may also work) + OpenStack *development
environment*."

So i'm wondering that if there is a better way to deploy openstack on
XenServer for production???

Thanks in advance! :)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [puppet] weekly meeting #47

[Emilien Macchi]

Hello,

Here's an initial agenda for our weekly meeting, Tuesday at 1500 UTC
in #openstack-meeting-4:

https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150818

Please add additional items you'd like to discuss.
If our schedule allows it, we'll make bug triage during the meeting.

Regards,
-- 
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Canada is having a PyCon! Who knew?

[Anita Kuno]

I didn't, otherwise I would have spammed y'all prior to the close of
talk submissions.

However I just submitted a talk and the form didn't close me out, so /me
shrugs.

November 7-8 with the 9th being sprints in Toronto: https://2015.pycon.ca/

Consider it if you have a talk ready to copy paste and an interest in
Toronto.

Hope to see some folks there, (hope to get accepted myself)
Anita.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Tricircle Liberty Midcycle Minisprint on Aug 17th 2015

[Zhipeng Huang]

Hi All,

Joe has suggested to move the meeting earlier to UTC 0800, if there is no
problem then we will have the meeting in about 6 hours :)

On Fri, Aug 14, 2015 at 9:26 AM, Zhipeng Huang 
wrote:

> Hi Team,
>
> As discussed in the last meeting, we will hold a design sprint meeting on
> next Monday starting from UTC 1200 to discuss exclusively design problems
> and ideas. The meeting will happen at #openstack-tricircle so that we could
> discuss as long as we are awake without time limits :P
>
> The meeting info could be found at
> https://wiki.openstack.org/wiki/Meetings/Tricircle, please reply any
> topic you want to add to the agenda
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Prooduct Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] Confused syntax error when inserting rule.

[Rui Chen]

Thanks for your clarification. I think the root reason is hidden variables
that generated by policy engine.

*error(id) :- cinder:volumes(id=id), not avail_cinder_vol(id)*
*avail_cinder_vol(id) :- cinder:volumes(id=id, status="available")*

It's a good idea, keep the rules simple and readable.

It point out a best practice that the negative and positive literal of same
table shouldn't exist in one rule.

Thank you very much.

2015-08-14 21:38 GMT+08:00 Tim Hinrichs :

> Hi Rui,
>
> The problem with the following rule is that there are a bunch of hidden
> variables in the "not cinder:volumes(...)" literal.  The error message
> shows the hidden variables.  The syntax restriction is that every variable
> in a negative literal must appear in a positive literal in the body.  Those
> hidden variables fail to satisfy that restriction, hence the error.
>
>  error(id) :- cinder:volumes(id=id), not cinder:volumes(id=id,
> status="available")
>
> The reason the other rule worked is that you made the hidden variables
> equivalent to the ones in the positive literal, e.g. x_0_1 shows up in both
> the positive and negative literals.
>
> error(x) :- cinder:volumes(x, _x_0_1, _x_0_2, _x_0_3, _x_0_4, _x_0_5,
> _x_0_6, _x_0_7, _x_0_8),not cinder:volumes(x, _x_0_1, _x_0_2,
> \"available\",_x_0_4, _x_0_5, _x_0_6, _x_0_7, _x_0_8)
>
> But in the auto-generated one, the variables in the two literals are
> different e.g. _x_0_1 and _x_1_1
>
> error(id) :- cinder:volumes(id, _x_0_1, _x_0_2, _x_0_3, _x_0_4, _x_0_5,
> _x_0_6, _x_0_7, _x_0_8), not cinder:volumes(id, _x_1_1, _x_1_2,
> "available", _x_1_4, _x_1_5, _x_1_6, _x_1_7, _x_1_8).  Unsafe lits: not
> cinder:volumes(id, _x_1_1, _x_1_2, "available", _x_1_4, _x_1_5, _x_1_6,
> _x_1_7, _x_1_8)
>
> Probably the solution you want is to write 2 rules:
>
> error(id) :- cinder:volumes(id=id), not avail_cinder_vol(id)
> avail_cinder_vol(id) :- cinder:volumes(id=id, status="available")
>
> Tim
>
> On Thu, Aug 13, 2015 at 8:07 PM Rui Chen  wrote:
>
>> Sorry, send the same mail again, please comments at here, the other mail
>> lack title.
>>
>> 2015-08-14 11:03 GMT+08:00 Rui Chen :
>>
>>> Hi folks:
>>>
>>> I face a problem when I insert a rule into Congress. I want to find
>>> out all of the volumes that are not available status, so I draft a rule
>>> like this:
>>>
>>> error(id) :- cinder:volumes(id=id), not cinder:volumes(id=id,
>>> status="available")
>>>
>>> But when I create the rule, a error is raised:
>>>
>>> (openstack) congress policy rule create chenrui_p "error(id) :-
>>> cinder:volumes(id=id),not cinder:volumes(id=id, status=\"available\")"
>>> ERROR: openstack Syntax error for rule::Errors: Could not reorder rule
>>> error(id) :- cinder:volumes(id, _x_0_1, _x_0_2, _x_0_3, _x_0_4, _x_0_5,
>>> _x_0_6, _x_0_7, _x_0_8), not cinder:volumes(id, _x_1_1, _x_1_2,
>>> "available", _x_1_4, _x_1_5, _x_1_6, _x_1_7, _x_1_8).  Unsafe lits: not
>>> cinder:volumes(id, _x_1_1, _x_1_2, "available", _x_1_4, _x_1_5, _x_1_6,
>>> _x_1_7, _x_1_8) (vars set(['_x_1_2', '_x_1_1', '_x_1_6', '_x_1_7',
>>> '_x_1_4', '_x_1_5', '_x_1_8'])) (HTTP 400) (Request-ID:
>>> req-1f4432d6-f869-472b-aa7d-4cf78dd96fa1)
>>>
>>> I check the Congress policy docs [1], looks like that the rule don't
>>> break any syntax restrictions.
>>>
>>> If I modify the rule like this, it works:
>>>
>>> (openstack) congress policy rule create chenrui_p "error(x) :-
>>> cinder:volumes(x, _x_0_1, _x_0_2, _x_0_3, _x_0_4, _x_0_5, _x_0_6, _x_0_7,
>>> _x_0_8),not cinder:volumes(x, _x_0_1, _x_0_2, \"available\",_x_0_4, _x_0_5,
>>> _x_0_6, _x_0_7, _x_0_8)"
>>>
>>> +-++
>>> | Field   | Value
>>>|
>>>
>>> +-++
>>> | comment | None
>>>   |
>>> | id  | ad121e09-ba0a-45d6-bd18-487d975d5bf5
>>>   |
>>> | name| None
>>>   |
>>> | rule| error(x) :-
>>>|
>>> | | cinder:volumes(x, _x_0_1, _x_0_2, _x_0_3, _x_0_4,
>>> _x_0_5, _x_0_6, _x_0_7, _x_0_8), |
>>> | | not cinder:volumes(x, _x_0_1, _x_0_2, "available",
>>> _x_0_4, _x_0_5, _x_0_6, _x_0_7, _x_0_8) |
>>>
>>> +-++
>>>
>>> I'm not sure this is a bug or I miss something from docs, so I need
>>> some feedback from mail list.
>>> Feel free to discuss about it.
>>>
>>>
>>> [1]:
>>> http://congress.readthedocs.org/en/latest/policy.html#datalog-syntax-restrictions
>>>
>>>
>>> Best Regards.
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ.

Re: [openstack-dev] [oslo] debugging the failures in oslo.messaging gate

[Davanum Srinivas]

Doug,

I've filed https://review.openstack.org/213542 to log error messages. Will
work with oslo.messaging folks the next few days.

Thanks,
Dims

On Fri, Aug 14, 2015 at 6:58 PM, Doug Hellmann 
wrote:

> All patches to oslo.messaging are currently failing the
> gate-tempest-dsvm-neutron-src-oslo.messaging job because the neutron
> service dies. amuller, kevinbenton, and I spent a bunch of time looking at
> it today, and I think we have an issue introduced by some asymmetric gating
> between the two projects.
>
> Neutron has 2 different modes for starting the RPC service, depending on
> the number of workers requested. The problem comes up with rpc_workers=0,
> which is the new default. In that mode, rather than using the
> ProcessLauncher, the RPC server is started directly in the current process.
> That results in wait() being called in a way that violates the new
> constraints being enforced within oslo.messaging after [1] landed. That
> patch is unreleased, so the only project seeing the problem is
> oslo.messaging. I’ve proposed a revert in [2], which passes the gate tests.
>
> I have also added [3] to neutron to see if we can get the gate job to show
> the same error messages I was seeing locally (part of the trouble we’ve had
> with debugging this is the process exits quickly enough that some of the
> log messages are never being written). I’m using [4] as a patch in
> oslo.messaging that was failing before to trigger the job to get the
> necessary log. That patch should *not* be landed, since I don’t think the
> change it reverts is related to the problem, it was just handy for
> debugging.
>
> The error message I see locally, “start/stop/wait must be called in the
> same thread”, is visible in this log snippet [5].
>
> It’s not clear what the best path forward is. Obviously neutron is doing
> something with the RPC server that oslo.messaging doesn’t expect/want/like,
> but also obviously we can’t release oslo.messaging in its current state and
> break neutron. Someone with a better understanding of both neutron and
> oslo.messaging may be able to fix neutron’s use of the RPC code to avoid
> this case. There may be other users of oslo.messaging with the same
> ‘broken’ pattern, but IIRC neutron is unique in the way it runs both RPC
> and API services in the same process. To be safe, though, it may be better
> to log error messages instead of doing whatever we’re doing now to cause
> the process to exit. We can then set up a log stash search for the error
> message and find other applications that would be broken, fix them, and
> then switch oslo.messaging back to throwing an exception.
>
> I’m going to be at the Ops summit next week, so I need to hand off
> debugging and fixing the issue to someone else on the Oslo team. We created
> an etherpad to track progress and make notes today, and all of these links
> are referenced there, too [6].
>
> Thanks again to amuller and kevinbenton for the time they spent helping
> with debugging today!
>
> Doug
>
> [1] https://review.openstack.org/#/c/209043/
> [2] https://review.openstack.org/#/c/213299/
> [3] https://review.openstack.org/#/c/213360/
> [4] https://review.openstack.org/#/c/213297/
> [6] http://paste.openstack.org/show/415030/
> [6] https://etherpad.openstack.org/p/wm2D6UGZbf
>
>


-- 
Davanum Srinivas :: https://twitter.com/dims
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [swift] swift memory usage in centos7 devstack jobs

[Alan Pevec]

>> 2) Should this also be sent to centos-devel folks so that they don't
>> upgrade/update the pyopenssl in their distro repos until the issue
>> is resolved ?
>
>
> I think let's give the upstream issues a little while to play-out,
> then we decide our next steps around use of the library based on that
> information.

pyOpenSSL was bumped to 0.14 https://review.openstack.org/197986
does it work now on EL7 ?

Cheers,
Alan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][gnocchi] Source build dependency on postgresql-devel

[Steven Dake (stdake)]

On 8/16/15, 11:58 AM, "Julien Danjou"  wrote:

>On Sun, Aug 16 2015, Steven Dake (stdake) wrote:
>
>Hi Steven,
>
>> In Kolla we are packaging gnocchi in a container. It has a dependency on
>> pg_config as part of the build system. I¹d like to know from a gnocchi
>>expert
>> if this build time dependency relies on postgresql configured in some
>>way, or
>> does it just look for standard library paths?
>
>We rely on pg_config to find where PostgreSQL is installed to setup and
>start postgres on our own in the tests setup script.
>
>> The reason is we run each service as a micro-service meaning each
>>binary runs
>> in a separate container. If gnocchi relies on postgres configuration to
>>do its
>> build operation, it would mean we would have to run postgresql in our
>>container
>> at the same time as gnocchi. I have big concerns with that ­ less
>>concerned
>> about image size bloat (the case of just looking at library paths).
>
>You don't need PostgreSQL to build Gnocchi (I'm not sure what build
>means for Python). You just need it to run unit/integration tests and to
>build the documentation ­ because the doc is built by making real
>requests to a real server and printing the reply in the doc.
>
>I hope it helps, but feel free to ask if not!
Julien,

Thanks for the answers, they do satisfy my need for information.  You do
need the postgresql-devel package to build gnocchi however, because a
dependency called panda (listed in requirements.txt, which is what we
build rather then installing from packages) depends upon it.

Hope that helps

Regards
-steve

>
>Best,
>-- 
>Julien Danjou
>;; Free Software hacker
>;; http://julien.danjou.info


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

[Ildikó Váncsa]

Hi Roland,

As I saw, the wiki says 4pm UTC too, please check it.

Thanks and Best Regards,
Ildikó

> -Original Message-
> From: Hochmuth, Roland M [mailto:roland.hochm...@hp.com]
> Sent: August 16, 2015 17:14
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup
> 
> Ildikó, I think you are correct on the time. The meeting is at 3:00 PM UTC, 
> which is 9:00 AM MDT. Sorry, the time I mentioned was
> incorrect.
> Regards --Roland
> 
> 
> 
> On 8/16/15, 7:42 AM, "Ildikó Váncsa"  wrote:
> 
> >Hi Roland,
> >
> >Thanks for the meeting info.
> >
> >Let me come back to you regarding the attendance of the next Monasca
> >meeting. I messed up with time zones and slots a bit and I realized now
> >that the slot is 4pm UTC as opposed to 3pm UTC as I originally thought.
> >I have a bi-weekly meeting in my calendar colliding with the upcoming
> >slot, but for the past few occurrences it was cancelled, I need to
> >check the next one with the organizer.
> >
> >If I can attend, I can briefly talk about the componentization work.
> >
> >Best Regards,
> >Ildikó
> >
> >> -Original Message-
> >> From: Hochmuth, Roland M [mailto:roland.hochm...@hp.com]
> >> Sent: August 16, 2015 09:37
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle
> >>meetup
> >>
> >> Hi Ildikó, That will be great if you can attend. If you do, would it
> >>be possible for you to present an overview and current status/plans of
> >>the Ceilometer work around the componentization? I was at the
> >>discussion in Vancouver on this, and several others from Monasca  were
> >>there too, but I haven't stayed connected.
> >>
> >> The information for the Monasca Meetings as well as minutes is at,
> >>https://wiki.openstack.org/wiki/Meetings/Monasca. If you have  any
> >>problems connecting in, please let me know. We recently switched to
> >>WebEx, which is hosted by Cisco. Everything should work,  but if there
> >>are any problems we can switch to IRC.
> >>
> >> If Tuesday's at 4:00 PM UTC are problematic, then we would consider
> >>setting up a separate time to cover this topic or move the  Monasca
> >>meeting the following week.
> >>
> >> Regards --Roland
> >>
> >>
> >>
> >> On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:
> >>
> >> >Hi,
> >> >
> >> >I will try to join if I can, I have an overlapping meeting on Tuesdays.
> >> >
> >> >In general I think it would be really good to start a closer
> >> >collaboration, the componentization work in Ceilometer gives a
> >> >really good opportunity as Chris described.
> >> >
> >> >Best Regards,
> >> >Ildikó
> >> >
> >> >> -Original Message-
> >> >> From: Chris Dent [mailto:chd...@redhat.com]
> >> >> Sent: August 12, 2015 15:45
> >> >> To: OpenStack Development Mailing List (not for usage questions)
> >> >> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca
> >> >>mid-cycle meetup
> >> >>
> >> >> On Tue, 11 Aug 2015, Hochmuth, Roland M wrote:
> >> >>
> >> >> > It sounds like we should connect up soon. I could attend a
> >> >> > Ceilometer meeting, or you could attend the Monasca meeting
> >> >> > which is held Tuesday mornings at 9:00 MST.
> >> >>
> >> >> I'm away this coming Tuesday, but perhaps some of the other Ceilo
> >> >>people could show up? I've got it on my schedule to come the  week
> >> >>after.
> >> >>
> >> >> I suspect there's a lot we can do over the long run to avoid
> >> >>duplicating code and effort but that there will be some humps to
> >> >>ride over  to different pieces (and people!) talking to one another.
> >> >> Should be fun. Looking forward to it.
> >> >>
> >> >> --
> >> >> Chris Dent tw:@anticdent freenode:cdent
> >> >> https://tank.peermore.com/tanks/cdent
> >> >>
> >> >>
> >> >>___
> >> >>___
> >> >>___
> >> >>_
> >> >> OpenStack Development Mailing List (not for usage questions)
> >> >> Unsubscribe:
> >> >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >
> >> >
> >> >___ ___ OpenStack Development Mailing List (not for usage questions)
> >> >Unsubscribe:
> >> >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >>
> >>__
> >>___
> >>_
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe:
> >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >___
> >___ OpenStack Development Mailing List (not for usage questions)
> >Unsubscr

Re: [openstack-dev] [sahara] Proposing Ethan Gafford for the core reviewer team

[Telles Nobrega]

For what is worth I got that it was just a joke.

On Fri, Aug 14, 2015 at 2:30 PM Trevor McKay  wrote:

> Flavio,
>
>   thanks, bad joke on my part. I work with Telles on Sahara, just poking
> him in jest.  Apologies, didn't mean to create an issue on the list.
>
> Trev
>
> On Fri, 2015-08-14 at 17:30 +0200, Flavio Percoco wrote:
> > On 14/08/15 09:29 -0400, Trevor McKay wrote:
> > >Hi Telles,
> > >
> > > you technically don't get a vote, but thanks anyway :)
> >
> > Hi Trevor,
> >
> > Technically, everyone gets to vote and speak up. Regardless of whether
> > you're a core-reviewer or not. Most of the time, non-core contributors
> > provide amazing feedback on what their experience has been while
> > receiving reviews from the nominated person.
> >
> > Regardless of the comment, we as a community always welcome
> > contributor's opinions and encourage folks to speak up.
> >
> > I knew your intentions are good but I thought it'd be a good time to
> > share the above so that it would work as a reminder for others as
> > well.
> >
> > Thank you both and +1 for Ethan ;)
> > Flavio
> >
> > >
> > >Trev
> > >
> > >On Fri, 2015-08-14 at 12:14 +, Telles Nobrega wrote:
> > >> +1
> > >>
> > >> On Fri, Aug 14, 2015 at 7:11 AM Alexander Ignatov
> > >>  wrote:
> > >>
> > >> +1
> > >>
> > >> Regards,
> > >> Alexander Ignatov
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> > On 13 Aug 2015, at 18:29, Sergey Reshetnyak
> > >> >  wrote:
> > >> >
> > >> > +2
> > >> >
> > >> > 2015-08-13 18:07 GMT+03:00 Matthew Farrellee
> > >> > :
> > >> > On 08/13/2015 10:56 AM, Sergey Lukjanov wrote:
> > >> > Hi folks,
> > >> >
> > >> > I'd like to propose Ethan Gafford as a
> > >> > member of the Sahara core
> > >> > reviewer team.
> > >> >
> > >> > Ethan contributing to Sahara for a long time
> > >> > and doing a great job on
> > >> > reviewing and improving Sahara. Here are the
> > >> > statistics for reviews
> > >> > [0][1][2] and commits [3]. BTW Ethan is
> > >> > already stable maint team core
> > >> > for Sahara.
> > >> >
> > >> > Existing Sahara core reviewers, please vote
> > >> > +1/-1 for the addition of
> > >> > Ethan to the core reviewer team.
> > >> >
> > >> > Thanks.
> > >> >
> > >> > [0]
> > >> > https://review.openstack.org/#/q/reviewer:%
> > >> > 22Ethan+Gafford+%253Cegafford%
> 2540redhat.com
> > >> > %253E%22,n,z
> > >> > [1]
> > >> >
> http://stackalytics.com/report/contribution/sahara-group/90
> > >> > [2]
> > >> >
> http://stackalytics.com/?user_id=egafford&metric=marks
> > >> > [3]
> > >> > https://review.openstack.org/#/q/owner:%
> > >> > 22Ethan+Gafford+%253Cegafford%
> 2540redhat.com
> > >> > %253E%22+status:merged,n,z
> > >> >
> > >> > --
> > >> > Sincerely yours,
> > >> > Sergey Lukjanov
> > >> > Sahara Technical Lead
> > >> > (OpenStack Data Processing)
> > >> > Principal Software Engineer
> > >> > Mirantis Inc.
> > >> >
> > >> >
> > >> > +1 ethan has really taken to sahara, providing
> > >> > valuable input to both development and deployments
> > >> > as well has taking on the manila integration
> > >> >
> > >> >
> > >> >
> > >> >
>  __
> > >> > OpenStack Development Mailing List (not for usage
> > >> > questions)
> > >> > Unsubscribe:
> > >> >
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > >> >
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >> >
> > >> >
> > >> >
> > >> >
> __
> > >> > OpenStack Development Mailing List (not for usage questions)
> > >> > Unsubscribe:
> > >> >
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > >> >
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >> >
> > >>
> > >>
> > >>
>  

Re: [openstack-dev] [kolla][gnocchi] Source build dependency on postgresql-devel

[Julien Danjou]

On Sun, Aug 16 2015, Steven Dake (stdake) wrote:

Hi Steven,

> In Kolla we are packaging gnocchi in a container. It has a dependency on
> pg_config as part of the build system. I’d like to know from a gnocchi expert
> if this build time dependency relies on postgresql configured in some way, or
> does it just look for standard library paths?

We rely on pg_config to find where PostgreSQL is installed to setup and
start postgres on our own in the tests setup script.

> The reason is we run each service as a micro-service meaning each binary runs
> in a separate container. If gnocchi relies on postgres configuration to do its
> build operation, it would mean we would have to run postgresql in our 
> container
> at the same time as gnocchi. I have big concerns with that – less concerned
> about image size bloat (the case of just looking at library paths).

You don't need PostgreSQL to build Gnocchi (I'm not sure what build
means for Python). You just need it to run unit/integration tests and to
build the documentation – because the doc is built by making real
requests to a real server and printing the reply in the doc.

I hope it helps, but feel free to ask if not!

Best,
-- 
Julien Danjou
;; Free Software hacker
;; http://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [UX] [Keystone] [Horizon] Pagination support for Identity dashboard entities

[Morgan Fainberg]

> On Aug 16, 2015, at 08:02, Michael Krotscheck  wrote:
> 
> 
> 
>> On Sat, Aug 15, 2015 at 11:02 AM Morgan Fainberg  
>> wrote:
>> Please do not construe a major api change as backwards incompatible. This 
>> pagination was never supported in v3 properly/at all. 
> 
> Sure, let's argue semantics! That's a useful path forward :).
> 

By this logic every version of every API must be compatible. This is not 
semantics. 

>> As we move towards tools like FreeIPA Or something similar, we will be 
>> addressing the gap. 
> 
> Is there a cross-project spec with assigned resources? I'd love to comment on 
> it.
> 
>> I also assert horizon should not be managing users in the same way Keystone 
>> should not be managing users. Horizon should show what users have access to 
>> openstack (and this *can* be paginated) and allow for searching for a user 
>> that is visible to keystone but does not have access to openstack so that 
>> they can be grants access. 
> 
> Is there a horizon spec that defines this? I'd love to comment on it.
>  
>> The user management service would be FreeIPA in my previous example (or AD 
>> in the environments that deploy it, etc). 
>> 
>> 1: you do not get to list every user visible to keystone via v3. This is 
>> where the problems lie.
>> 
>> 2: you can search for users that are visible but do not have an active 
>> assignment (this may need some work - and is a reasonable ask). 
>> 
>> 2a: if the list of users is small the filter/search could return all users
>> 
>> 3: you can list users with an active assignment (using the assignment apis) 
>> and this *can* be paginated (if it does not already support pagination)
>> 
>> 4: (future view) leverage an already existing open source solution for user 
>> management such as FreeIPA and remove/deprecate the sql-based data store 
>> that is missing basic user management features
> 
> Hey, all of the above looks like a spec! Neat! You should propose it!
> 
> Michael
> Code Trumps Conversation
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [UX] [Keystone] [Horizon] Pagination support for Identity dashboard entities

[Kruithof, Piet]

I like Michael’s response because it moved the thread towards identifying 
actual user needs before digging into the technical feasibility.  IMHO, it 
would be helpful to have a few people on the list answer his questions:

1 - Do users want to page through search results?


2 - Do users want to page through filter results? (do they use filter results?)


3 - If they want to page, do they want to be able to go back a page and/or know 
their current page?


I understand that even if we answer “yes” to all three questions that there 
could be issues around implementation, but at least we’ll know a gap exists.


Piet Kruithof
Sr UX Architect, HP Helion Cloud
PTL, OpenStack UX project

"For every complex problem, there is a solution that is simple, neat and wrong.”

H L Menken


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

[Hochmuth, Roland M]

Ildikó, I think you are correct on the time. The meeting is at 3:00 PM
UTC, which is 9:00 AM MDT. Sorry, the time I mentioned was incorrect.
Regards --Roland



On 8/16/15, 7:42 AM, "Ildikó Váncsa"  wrote:

>Hi Roland,
>
>Thanks for the meeting info.
>
>Let me come back to you regarding the attendance of the next Monasca
>meeting. I messed up with time zones and slots a bit and I realized now
>that the slot is 4pm UTC as opposed to 3pm UTC as I originally thought. I
>have a bi-weekly meeting in my calendar colliding with the upcoming slot,
>but for the past few occurrences it was cancelled, I need to check the
>next one with the organizer.
>
>If I can attend, I can briefly talk about the componentization work.
>
>Best Regards,
>Ildikó
>
>> -Original Message-
>> From: Hochmuth, Roland M [mailto:roland.hochm...@hp.com]
>> Sent: August 16, 2015 09:37
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle
>>meetup
>> 
>> Hi Ildikó, That will be great if you can attend. If you do, would it be
>>possible for you to present an overview and current status/plans of
>> the Ceilometer work around the componentization? I was at the
>>discussion in Vancouver on this, and several others from Monasca
>> were there too, but I haven't stayed connected.
>> 
>> The information for the Monasca Meetings as well as minutes is at,
>>https://wiki.openstack.org/wiki/Meetings/Monasca. If you have
>> any problems connecting in, please let me know. We recently switched to
>>WebEx, which is hosted by Cisco. Everything should work,
>> but if there are any problems we can switch to IRC.
>> 
>> If Tuesday's at 4:00 PM UTC are problematic, then we would consider
>>setting up a separate time to cover this topic or move the
>> Monasca meeting the following week.
>> 
>> Regards --Roland
>> 
>> 
>> 
>> On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:
>> 
>> >Hi,
>> >
>> >I will try to join if I can, I have an overlapping meeting on Tuesdays.
>> >
>> >In general I think it would be really good to start a closer
>> >collaboration, the componentization work in Ceilometer gives a really
>> >good opportunity as Chris described.
>> >
>> >Best Regards,
>> >Ildikó
>> >
>> >> -Original Message-
>> >> From: Chris Dent [mailto:chd...@redhat.com]
>> >> Sent: August 12, 2015 15:45
>> >> To: OpenStack Development Mailing List (not for usage questions)
>> >> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle
>> >>meetup
>> >>
>> >> On Tue, 11 Aug 2015, Hochmuth, Roland M wrote:
>> >>
>> >> > It sounds like we should connect up soon. I could attend a
>> >> > Ceilometer meeting, or you could attend the Monasca meeting which
>> >> > is held Tuesday mornings at 9:00 MST.
>> >>
>> >> I'm away this coming Tuesday, but perhaps some of the other Ceilo
>> >>people could show up? I've got it on my schedule to come the  week
>> >>after.
>> >>
>> >> I suspect there's a lot we can do over the long run to avoid
>> >>duplicating code and effort but that there will be some humps to ride
>> >>over  to different pieces (and people!) talking to one another.
>> >> Should be fun. Looking forward to it.
>> >>
>> >> --
>> >> Chris Dent tw:@anticdent freenode:cdent
>> >> https://tank.peermore.com/tanks/cdent
>> >>
>> >>
>> >>__
>> >>___
>> >>_
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe:
>> >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >___
>> >___ OpenStack Development Mailing List (not for usage questions)
>> >Unsubscribe:
>> >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [UX] [Keystone] [Horizon] Pagination support for Identity dashboard entities

[Michael Krotscheck]

On Sat, Aug 15, 2015 at 11:02 AM Morgan Fainberg 
wrote:

> Please do not construe a major api change as backwards incompatible. This
> pagination was never supported in v3 properly/at all.
>

Sure, let's argue semantics! That's a useful path forward :).

As we move towards tools like FreeIPA Or something similar, we will be
> addressing the gap.
>

Is there a cross-project spec with assigned resources? I'd love to comment
on it.

I also assert horizon should not be managing users in the same way Keystone
> should not be managing users. Horizon should show what users have access to
> openstack (and this *can* be paginated) and allow for searching for a user
> that is visible to keystone but does not have access to openstack so that
> they can be grants access.
>

Is there a horizon spec that defines this? I'd love to comment on it.


> The user management service would be FreeIPA in my previous example (or AD
> in the environments that deploy it, etc).
>

> 1: you do not get to list every user visible to keystone via v3. This is
> where the problems lie.
>

> 2: you can search for users that are visible but do not have an active
> assignment (this may need some work - and is a reasonable ask).
>
> 2a: if the list of users is small the filter/search could return all users
>
> 3: you can list users with an active assignment (using the assignment
> apis) and this *can* be paginated (if it does not already support
> pagination)
>
> 4: (future view) leverage an already existing open source solution for
> user management such as FreeIPA and remove/deprecate the sql-based data
> store that is missing basic user management features
>

Hey, all of the above looks like a spec! Neat! You should propose it!

Michael
Code Trumps Conversation
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kolla][gnocchi] Source build dependency on postgresql-devel

[Steven Dake (stdake)]

Hi,

In Kolla we are packaging gnocchi in a container.  It has a dependency on 
pg_config as part of the build system.  I’d like to know from a gnocchi expert 
if this build time dependency relies on postgresql configured in some way, or 
does it just look for standard library paths?

The reason is we run each service as a micro-service meaning each binary runs 
in a separate container.  If gnocchi relies on postgres configuration to do its 
build operation, it would mean we would have to run postgresql in our container 
at the same time as gnocchi.  I have big concerns with that – less concerned 
about image size bloat (the case of just looking at library paths).

Answers welcome and if my question wasn’t clear please ask.

Thanks!
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

[Ildikó Váncsa]

Hi Roland,

Thanks for the meeting info.

Let me come back to you regarding the attendance of the next Monasca meeting. I 
messed up with time zones and slots a bit and I realized now that the slot is 
4pm UTC as opposed to 3pm UTC as I originally thought. I have a bi-weekly 
meeting in my calendar colliding with the upcoming slot, but for the past few 
occurrences it was cancelled, I need to check the next one with the organizer.

If I can attend, I can briefly talk about the componentization work.

Best Regards,
Ildikó

> -Original Message-
> From: Hochmuth, Roland M [mailto:roland.hochm...@hp.com]
> Sent: August 16, 2015 09:37
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup
> 
> Hi Ildikó, That will be great if you can attend. If you do, would it be 
> possible for you to present an overview and current status/plans of
> the Ceilometer work around the componentization? I was at the discussion in 
> Vancouver on this, and several others from Monasca
> were there too, but I haven't stayed connected.
> 
> The information for the Monasca Meetings as well as minutes is at, 
> https://wiki.openstack.org/wiki/Meetings/Monasca. If you have
> any problems connecting in, please let me know. We recently switched to 
> WebEx, which is hosted by Cisco. Everything should work,
> but if there are any problems we can switch to IRC.
> 
> If Tuesday's at 4:00 PM UTC are problematic, then we would consider setting 
> up a separate time to cover this topic or move the
> Monasca meeting the following week.
> 
> Regards --Roland
> 
> 
> 
> On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:
> 
> >Hi,
> >
> >I will try to join if I can, I have an overlapping meeting on Tuesdays.
> >
> >In general I think it would be really good to start a closer
> >collaboration, the componentization work in Ceilometer gives a really
> >good opportunity as Chris described.
> >
> >Best Regards,
> >Ildikó
> >
> >> -Original Message-
> >> From: Chris Dent [mailto:chd...@redhat.com]
> >> Sent: August 12, 2015 15:45
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle
> >>meetup
> >>
> >> On Tue, 11 Aug 2015, Hochmuth, Roland M wrote:
> >>
> >> > It sounds like we should connect up soon. I could attend a
> >> > Ceilometer meeting, or you could attend the Monasca meeting which
> >> > is held Tuesday mornings at 9:00 MST.
> >>
> >> I'm away this coming Tuesday, but perhaps some of the other Ceilo
> >>people could show up? I've got it on my schedule to come the  week
> >>after.
> >>
> >> I suspect there's a lot we can do over the long run to avoid
> >>duplicating code and effort but that there will be some humps to ride
> >>over  to different pieces (and people!) talking to one another.
> >> Should be fun. Looking forward to it.
> >>
> >> --
> >> Chris Dent tw:@anticdent freenode:cdent
> >> https://tank.peermore.com/tanks/cdent
> >>
> >>
> >>__
> >>___
> >>_
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe:
> >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >___
> >___ OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe:
> >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

[Hochmuth, Roland M]

Hi Ildikó, That will be great if you can attend. If you do, would it be
possible for you to present an overview and current status/plans of the
Ceilometer work around the componentization? I was at the discussion in
Vancouver on this, and several others from Monasca were there too, but I
haven't stayed connected.

The information for the Monasca Meetings as well as minutes is at,
https://wiki.openstack.org/wiki/Meetings/Monasca. If you have any problems
connecting in, please let me know. We recently switched to WebEx, which is
hosted by Cisco. Everything should work, but if there are any problems we
can switch to IRC.

If Tuesday's at 4:00 PM UTC are problematic, then we would consider
setting up a separate time to cover this topic or move the Monasca meeting
the following week.

Regards --Roland



On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:

>Hi,
>
>I will try to join if I can, I have an overlapping meeting on Tuesdays.
>
>In general I think it would be really good to start a closer
>collaboration, the componentization work in Ceilometer gives a really
>good opportunity as Chris described.
>
>Best Regards,
>Ildikó
>
>> -Original Message-
>> From: Chris Dent [mailto:chd...@redhat.com]
>> Sent: August 12, 2015 15:45
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle
>>meetup
>> 
>> On Tue, 11 Aug 2015, Hochmuth, Roland M wrote:
>> 
>> > It sounds like we should connect up soon. I could attend a Ceilometer
>> > meeting, or you could attend the Monasca meeting which is held Tuesday
>> > mornings at 9:00 MST.
>> 
>> I'm away this coming Tuesday, but perhaps some of the other Ceilo
>>people could show up? I've got it on my schedule to come the
>> week after.
>> 
>> I suspect there's a lot we can do over the long run to avoid
>>duplicating code and effort but that there will be some humps to ride
>>over
>> to different pieces (and people!) talking to one another.
>> Should be fun. Looking forward to it.
>> 
>> --
>> Chris Dent tw:@anticdent freenode:cdent
>> https://tank.peermore.com/tanks/cdent
>> 
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev