Hey Brad,
Many thanks for the explanation...
> ~~~
> WARNING: the following dangerous and experimental features are enabled:
> ~~~
> Can I ask why you want to disable this warning?
We using bluestore with kraken, we are aware that this is in tech preview.
To hide these warning compiled like
On Fri, Mar 24, 2017 at 6:49 PM, nokia ceph wrote:
> Brad, cool now we are on the same track :)
>
> So whatever change we made after this location src/* as it mapped to
> respective rpm correct?
>
> For eg:-
> src/osd/* -- ceph-osd
> src/common - ceph-common
> src/mon
Piotr, thanks for the info.
Yea this method is time saving, but we are not started testing with build
from source method. We will consider this for our next part of testing :)
On Fri, Mar 24, 2017 at 1:17 PM, Piotr Dałek
wrote:
> On 03/23/2017 06:10 PM, nokia ceph
Brad, cool now we are on the same track :)
So whatever change we made after this location src/* as it mapped to
respective rpm correct?
For eg:-
src/osd/* -- ceph-osd
src/common - ceph-common
src/mon - ceph-mon
src/mgr - ceph-mgr
Since we are using bluestore with kraken, I though to disable
On 03/23/2017 06:10 PM, nokia ceph wrote:
Hello Piotr,
I didn't understand, could you please elaborate about this procedure as
mentioned in the last update. It would be really helpful if you share any
useful link/doc to understand what you actually meant. Yea correct, normally
we do this
Oh wow, I completely misunderstood your question.
Yes, src/osd/PG.cc and src/osd/PG.h are compiled into the ceph-osd binary which
is included in the ceph-osd rpm as you said in your OP.
On Fri, Mar 24, 2017 at 3:10 AM, nokia ceph wrote:
> Hello Piotr,
>
> I didn't
Hello Piotr,
I didn't understand, could you please elaborate about this procedure as
mentioned in the last update. It would be really helpful if you share any
useful link/doc to understand what you actually meant. Yea correct,
normally we do this procedure but it takes more time. But here my
On 03/23/2017 02:02 PM, nokia ceph wrote:
Hello Piotr,
We do customizing ceph code for our testing purpose. It's a part of our R :)
Recompiling source code will create 38 rpm's out of these I need to find
which one is the correct rpm which I made change in the source code. That's
what I'm try
Hello Piotr,
We do customizing ceph code for our testing purpose. It's a part of our R
:)
Recompiling source code will create 38 rpm's out of these I need to find
which one is the correct rpm which I made change in the source code. That's
what I'm try to figure out.
Thanks
On Thu, Mar 23, 2017
On 03/23/2017 01:41 PM, nokia ceph wrote:
Hey brad,
Thanks for the info.
Yea we know that these are test rpm's.
The idea behind my question is if I made any changes in the ceph source
code, then I recompile it. Then I need to find which is the appropriate rpm
mapped to that changed file. If I
Hey brad,
Thanks for the info.
Yea we know that these are test rpm's.
The idea behind my question is if I made any changes in the ceph source
code, then I recompile it. Then I need to find which is the appropriate rpm
mapped to that changed file. If I find the exact RPM, then apply that RPM
in
Based solely on the information given the only rpms with this specific commit in
them would be here
https://shaman.ceph.com/builds/ceph/wip-prune-past-intervals-kraken/
(specifically
Hello,
I made some changes in the below file on ceph kraken v11.2.0 source code as
per this article
https://github.com/ceph/ceph-ci/commit/wip-prune-past-intervals-kraken
..src/osd/PG.cc
..src/osd/PG.h
Is there any way to find which rpm got affected by these two files. I
believe it should be
13 matches
Mail list logo