tarball for 10.0.0

[Deneau, Tom]

I did not see the source tarball for 10.0.0 at 
http://download.ceph.com/tarballs/ceph-10.0.0.tar.gz

-- Tom Deneau

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

How to open clog debug

[Wukongming]

Hi, All

Does anyone know how to open clog debug?

-
wukongming ID: 12019
Tel：0571-86760239
Dept：2014 UIS2 OneStor

-
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email immediately and delete it!

ceph branch status

[ceph branch robot]

-- All Branches --

Abhishek Varshney 
2015-11-23 11:45:29 +0530   infernalis-backports

Adam C. Emerson 
2015-10-16 13:49:09 -0400   wip-cxx11time
2015-10-17 13:20:15 -0400   wip-cxx11concurrency

Adam Crume 
2014-12-01 20:45:58 -0800   wip-doc-rbd-replay

Alfredo Deza 
2015-03-23 16:39:48 -0400   wip-11212

Alfredo Deza 
2014-07-08 13:58:35 -0400   wip-8679
2014-09-04 13:58:14 -0400   wip-8366
2014-10-13 11:10:10 -0400   wip-9730

Ali Maredia 
2015-11-23 19:17:44 -0500   wip-cmake
2015-11-25 13:45:29 -0500   wip-10587-split-servers

Barbora Ančincová 
2015-11-04 16:43:45 +0100   wip-doc-RGW

Boris Ranto 
2015-09-04 15:19:11 +0200   wip-bash-completion

Casey Bodley 
2015-09-28 17:09:11 -0400   wip-cxx14-test
2015-09-29 15:18:17 -0400   wip-fio-objectstore

Daniel Gryniewicz 
2015-11-11 09:06:00 -0500   wip-rgw-storage-class

Danny Al-Gaaf 
2015-04-23 16:32:00 +0200   wip-da-SCA-20150421
2015-04-23 17:18:57 +0200   wip-nosetests
2015-04-23 18:20:16 +0200   wip-unify-num_objects_degraded
2015-11-03 14:10:47 +0100   wip-da-SCA-20151029
2015-11-03 14:40:44 +0100   wip-da-SCA-20150910

David Zafman 
2014-08-29 10:41:23 -0700   wip-libcommon-rebase
2015-04-24 13:14:23 -0700   wip-cot-giant
2015-08-04 07:39:00 -0700   wip-12577-hammer
2015-09-28 11:33:11 -0700   wip-12983
2015-11-24 14:40:10 -0800   wip-zafman-testing

Dongmao Zhang 
2014-11-14 19:14:34 +0800   thesues-master

Greg Farnum 
2015-04-29 21:44:11 -0700   wip-init-names
2015-07-16 09:28:24 -0700   hammer-12297
2015-10-02 13:00:59 -0700   greg-infernalis-lock-testing
2015-10-02 13:09:05 -0700   greg-infernalis-lock-testing-cacher
2015-10-07 00:45:24 -0700   greg-infernalis-fs
2015-10-21 17:43:07 -0700   client-pagecache-norevoke
2015-10-27 11:32:46 -0700   hammer-pg-replay
2015-11-24 07:17:33 -0800   greg-fs-verify
2015-11-24 08:10:17 -0800   greg-fs-testing

Greg Farnum 
2014-10-23 13:33:44 -0700   wip-forward-scrub

Guang G Yang 
2015-06-26 20:31:44 +   wip-ec-readall
2015-07-23 16:13:19 +   wip-12316

Guang Yang 
2014-08-08 10:41:12 +   wip-guangyy-pg-splitting
2014-09-25 00:47:46 +   wip-9008
2014-09-30 10:36:39 +   guangyy-wip-9614

Haomai Wang 
2015-10-26 00:02:04 +0800   wip-13521

Haomai Wang 
2014-07-27 13:37:49 +0800   wip-flush-set
2015-04-20 00:47:59 +0800   update-organization
2015-07-21 19:33:56 +0800   fio-objectstore
2015-08-26 09:57:27 +0800   wip-recovery-attr
2015-10-24 23:39:07 +0800   fix-compile-warning

Hector Martin 
2015-11-26 21:52:04 +0900   wip-cython-rbd

Ilya Dryomov 
2014-09-05 16:15:10 +0400   wip-rbd-notify-errors

Ivo Jimenez 
2015-08-24 23:12:45 -0700   hammer-with-new-workunit-for-wip-12551

James Page 
2015-11-04 11:08:42 +   javacruft-wip-ec-modules

Jason Dillaman 
2015-08-31 23:17:53 -0400   wip-12698
2015-11-13 02:00:21 -0500   wip-11287-rebased

Jenkins 
2015-11-04 14:31:13 -0800   rhcs-v0.94.3-ubuntu

Jenkins 
2014-07-29 05:24:39 -0700   wip-nhm-hang
2014-10-14 12:10:38 -0700   wip-2
2015-02-02 10:35:28 -0800   wip-sam-v0.92
2015-08-21 12:46:32 -0700   last
2015-08-21 12:46:32 -0700   loic-v9.0.3
2015-09-15 10:23:18 -0700   rhcs-v0.80.8
2015-09-21 16:48:32 -0700   rhcs-v0.94.1-ubuntu

Jenkins Build Slave User 
2015-11-17 18:57:48 +   firefly

Joao Eduardo Luis 
2014-09-10 09:39:23 +0100   wip-leveldb-get.dumpling

Joao Eduardo Luis 
2014-07-22 15:41:42 +0100   wip-leveldb-misc

Joao Eduardo Luis 
2014-09-02 17:19:52 +0100   wip-leveldb-get
2014-10-17 16:20:11 +0100   wip-paxos-fix
2014-10-21 21:32:46 +0100   wip-9675.dumpling
2015-07-27 21:56:42 +0100   wip-11470.hammer
2015-09-09 15:45:45 +0100   wip-11786.hammer

Joao Eduardo Luis 
2014-11-17 16:43:53 +   wip-mon-osdmap-cleanup
2014-12-15 16:18:56 +   

Re: RFC: teuthology field in commit messages

[Gregory Farnum]

On Sun, Nov 29, 2015 at 6:15 PM, Loic Dachary  wrote:
>
>
> On 29/11/2015 23:55, John Spray wrote:
>> On Sun, Nov 29, 2015 at 9:25 PM, Loic Dachary  wrote:
>>>
>>>
>>> On 29/11/2015 21:47, John Spray wrote:
 On Sun, Nov 29, 2015 at 8:25 PM, Loic Dachary  wrote:
>
>
> On 29/11/2015 21:08, John Spray wrote:
>> On Sat, Nov 28, 2015 at 3:56 PM, Loic Dachary  wrote:
>>> Hi Ceph,
>>>
>>> An optional teuthology field could be added to a commit message like so:
>>>
>>> teuthology: --suite rbd
>>>
>>> to state that this commit should be tested with the rbd suite. It could 
>>> be parsed by bots and humans.
>>>
>>> It would make it easy and cost effective to run partial teuthology 
>>> suites automatically on pull requests.
>>>
>>> What do you think ?
>>
>> Hmm, we are usually testing things at the branch/PR level rather than
>> on the per-commit level, so it feels a bit strange to have this in the
>> commit message.
>
> Indeed. But what is a branch if not the HEAD commit ?

 It's the HEAD commit, and its ancestors.  So in a typical PR (or
 branch) there are several commits since the base (i.e. since master),
 and perhaps only one of them has a test suite marked on it, or maybe
 they have different test suites marked on different commits in the
 branch.

 It's not necessarily a problem, just something that would need to have
 a defined behaviour (maybe when testing a PR collect the "teuthology:"
 tags from all commits in PR, and run all the suites mentioned?).
>>>
>>> That's an interesting idea :-) My understanding is that we currently test a 
>>> PR by scheduling suites on its HEAD. But maybe you sometime schedule suites 
>>> using a commit that's in the middle of a PR ?
>>
>> I think I've made this too complicated...
>>
>> What I meant was that while one would schedule suites against the HEAD
>> of the PR, that might not be the same commit that has the logical
>> testing information in.  For example, I might have main commit that
>> has the "Fixes: " and "teuthology: " tags, and then a second commit
>> (that would be HEAD) which e.g. tweaks a unit test.  It would be weird
>> if I had to put the teuthology: tag on the unit test commit rather
>> than the functional test, so I guess it would make sense to look at
>> the teuthology: tags from all the commits in a PR when scheduling it.
>
> Thanks for explaining, it's cristal clear.
>
> My initial idea of having a teuthology: tag on the top level commit was 
> indeed naive and wrong. And looking through all commits and scheduling the 
> suites found on the HEAD as you suggest reflect what we manually do and sound 
> right :-)

And at that point I'm not sure what the point is of having the
"teuthology:" tags in the commit instead of in the PR body. I like
automating things but I think testing will always require enough user
discretion that having to look at the original PR and think about what
changes are being made, rather than just scraping some text out of a
commit, is the appropriate thing to do.
-Greg
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling for FreeBSD

[Willem Jan Withagen]

On 30-11-2015 15:40, Willem Jan Withagen wrote:
> On 30-11-2015 15:13, Mykola Golub wrote:
>> On Mon, Nov 30, 2015 at 12:53:54PM +0100, Willem Jan Withagen wrote:
>>
 git clone --recursive -b wip-freebsd https://github.com/trociny/ceph.git
 cd ceph
 ./install-deps.sh
 ./do_autogen.sh
 gmake
 cd src
 ./vstart.sh # start dev cluster
 ./ceph -s # check it works

>>>
>>> So what backend for the OSDs are you using here?
>>
>> The default one, which is FileStore. I have not done much testing
>> though...
>>
> 
> Well,
> Cherry-picked a few of you diffs.
> Compilation is now slugging thru the tests in my tree.
> Running gmake in serial mode, so it is slow with clang.

Installed the results:
gmake install

And looked at what it delivered:
zfs diff 

And I have to be honest that I'm not really enjoying all the ceph-test
stuff in my /usr/local/bin
Would prefer it to go into something like:
/usr/local/libexec/ceph/tests
or
/usr/local/share/ceph/tests

Not sure if this is possible without disrupting the automated testing.

--WjW

+   /sbin/mount.fuse.ceph
zfsroot/tmp
M   /tmp/
+   /tmp/fses
zfsroot/usr
M   /usr/local/sbin
M   /usr/local/bin
M   /usr/local/etc
M   /usr/local/include
M   /usr/local/lib
M   /usr/local/libexec
M   /usr/local/share
M   /usr/local/share/doc
M   /usr/local/lib/python2.7/site-packages
M   /usr/srcs/Ceph/src/ceph/src/.libs/libradosstriper.so.1
M   /usr/srcs/Ceph/src/ceph/src/.libs/librbd.so.1
+   /usr/local/share/ceph
+   /usr/local/share/ceph/known_hosts_drop.ceph.com
+   /usr/local/share/ceph/id_dsa_drop.ceph.com
+   /usr/local/share/ceph/id_dsa_drop.ceph.com.pub
+   /usr/local/lib/librados.so.2
+   /usr/local/lib/librados.so
+   /usr/local/lib/librados.la
+   /usr/srcs/Ceph/src/ceph/src/.libs/libradosstriper.so.1T
+   /usr/local/lib/libradosstriper.so.1
+   /usr/local/lib/libradosstriper.so
+   /usr/local/lib/libradosstriper.la
+   /usr/srcs/Ceph/src/ceph/src/.libs/librbd.so.1T
+   /usr/local/lib/librbd.so.1
+   /usr/local/lib/librbd.so
+   /usr/local/lib/librbd.la
+   /usr/local/lib/libcephfs.so.1
+   /usr/local/lib/libcephfs.so
+   /usr/local/lib/libcephfs.la
+   /usr/local/lib/librados.a
+   /usr/local/lib/libradosstriper.a
+   /usr/local/lib/librbd.a
+   /usr/local/lib/libcephfs.a
+   /usr/local/bin/ceph_test_ioctls
+   /usr/local/bin/ceph_erasure_code_benchmark
+   /usr/local/bin/ceph_erasure_code
+   /usr/local/bin/ceph_test_rados
+   /usr/local/bin/ceph_test_mutate
+   /usr/local/bin/ceph_smalliobench
+   /usr/local/bin/ceph_omapbench
+   /usr/local/bin/ceph_objectstore_bench
+   /usr/local/bin/ceph_multi_stress_watch
+   /usr/local/bin/ceph_test_cls_rbd
+   /usr/local/bin/ceph_test_cls_refcount
+   /usr/local/bin/ceph_test_cls_version
+   /usr/local/bin/ceph_test_cls_log
+   /usr/local/bin/ceph_test_cls_statelog
+   /usr/local/bin/ceph_test_cls_replica_log
+   /usr/local/bin/ceph_test_cls_lock
+   /usr/local/bin/ceph_test_cls_hello
+   /usr/local/bin/ceph_test_cls_numops
+   /usr/local/bin/ceph_test_cls_journal
+   /usr/local/bin/ceph_test_rados_api_cmd
+   /usr/local/bin/ceph_test_rados_api_io
+   /usr/local/bin/ceph_test_rados_api_c_write_operations
+   /usr/local/bin/ceph_test_rados_api_c_read_operations
+   /usr/local/bin/ceph_test_rados_api_aio
+   /usr/local/bin/ceph_test_rados_api_list
+   /usr/local/bin/ceph_test_rados_api_nlist
+   /usr/local/bin/ceph_test_rados_api_pool
+   /usr/local/bin/ceph_test_rados_api_stat
+   /usr/local/bin/ceph_test_rados_api_watch_notify
+   /usr/local/bin/ceph_test_rados_api_snapshots
+   /usr/local/bin/ceph_test_rados_api_cls
+   /usr/local/bin/ceph_test_rados_api_misc
+   /usr/local/bin/ceph_test_rados_api_tier
+   /usr/local/bin/ceph_test_rados_api_lock
+   /usr/local/bin/ceph_test_stress_watch
+   /usr/local/bin/ceph_smalliobenchrbd
+   /usr/local/bin/ceph_test_librbd
+   /usr/local/bin/ceph_test_librbd_api
+   /usr/local/bin/ceph_test_rados_striper_api_io
+   /usr/local/bin/ceph_test_rados_striper_api_aio
+   /usr/local/bin/ceph_test_rados_striper_api_striping
+   /usr/local/bin/ceph_test_libcephfs
+   /usr/local/bin/ceph_test_c_headers
+   /usr/local/bin/ceph_test_async_driver
+   /usr/local/bin/ceph_test_msgr
+   /usr/local/bin/ceph_streamtest
+   /usr/local/bin/ceph_test_trans
+   /usr/local/bin/ceph_test_mon_workloadgen
+   /usr/local/bin/ceph_test_mon_msg
+   /usr/local/bin/ceph_perf_objectstore
+   /usr/local/bin/ceph_perf_local
+   /usr/local/bin/ceph_perf_msgr_server
+   /usr/local/bin/ceph_perf_msgr_client
+   /usr/local/bin/ceph_test_objectstore_workloadgen
+   /usr/local/bin/ceph_test_filestore_idempotent
+   

Re: Compiling for FreeBSD

[Gregory Farnum]

On Mon, Nov 30, 2015 at 11:04 AM, Willem Jan Withagen  wrote:
> On 30-11-2015 15:40, Willem Jan Withagen wrote:
>> On 30-11-2015 15:13, Mykola Golub wrote:
>>> On Mon, Nov 30, 2015 at 12:53:54PM +0100, Willem Jan Withagen wrote:
>>>
> git clone --recursive -b wip-freebsd https://github.com/trociny/ceph.git
> cd ceph
> ./install-deps.sh
> ./do_autogen.sh
> gmake
> cd src
> ./vstart.sh # start dev cluster
> ./ceph -s # check it works
>

 So what backend for the OSDs are you using here?
>>>
>>> The default one, which is FileStore. I have not done much testing
>>> though...
>>>
>>
>> Well,
>> Cherry-picked a few of you diffs.
>> Compilation is now slugging thru the tests in my tree.
>> Running gmake in serial mode, so it is slow with clang.
>
> Installed the results:
> gmake install
>
> And looked at what it delivered:
> zfs diff 
>
> And I have to be honest that I'm not really enjoying all the ceph-test
> stuff in my /usr/local/bin
> Would prefer it to go into something like:
> /usr/local/libexec/ceph/tests
> or
> /usr/local/share/ceph/tests
>
> Not sure if this is possible without disrupting the automated testing.

As far as I know, none of what we do upstream relies on "make install"
and I don't think it's very well-maintained. You could make some
changes and submit a PR — if it does break something it should show up
in the autobuilder bot.
-Greg
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling for FreeBSD

[Willem Jan Withagen]

On 30-11-2015 15:13, Mykola Golub wrote:
> On Mon, Nov 30, 2015 at 12:53:54PM +0100, Willem Jan Withagen wrote:
> 
>>> git clone --recursive -b wip-freebsd https://github.com/trociny/ceph.git
>>> cd ceph
>>> ./install-deps.sh
>>> ./do_autogen.sh
>>> gmake
>>> cd src
>>> ./vstart.sh # start dev cluster
>>> ./ceph -s # check it works
>>>
>>
>> So what backend for the OSDs are you using here?
> 
> The default one, which is FileStore. I have not done much testing
> though...
> 

Seems we have passed the first hurdle...
It compiles...

Onto the next phase: Testing.
Lets see what the developers site has to tell about that.

--WjW

chmod +x ceph-coverage.tmp
chmod a-w ceph-coverage.tmp
mv ceph-coverage.tmp ceph-coverage
cd ./ceph-detect-init ; python setup.py build
running build
running build_py
gmake[3]: Leaving directory '/usr/srcs/Ceph/src/ceph/src'
gmake[2]: Leaving directory '/usr/srcs/Ceph/src/ceph/src'
gmake[1]: Leaving directory '/usr/srcs/Ceph/src/ceph/src'
Making all in man
gmake[1]: Entering directory '/usr/srcs/Ceph/src/ceph/man'
gmake[1]: Nothing to be done for 'all'.
gmake[1]: Leaving directory '/usr/srcs/Ceph/src/ceph/man'
Making all in doc
gmake[1]: Entering directory '/usr/srcs/Ceph/src/ceph/doc'
gmake[1]: Nothing to be done for 'all'.
gmake[1]: Leaving directory '/usr/srcs/Ceph/src/ceph/doc'
Making all in systemd
gmake[1]: Entering directory '/usr/srcs/Ceph/src/ceph/systemd'
gmake[1]: Nothing to be done for 'all'.
gmake[1]: Leaving directory '/usr/srcs/Ceph/src/ceph/systemd'
Making all in selinux
gmake[1]: Entering directory '/usr/srcs/Ceph/src/ceph/selinux'
gmake[1]: Nothing to be done for 'all'.
gmake[1]: Leaving directory '/usr/srcs/Ceph/src/ceph/selinux'

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

updates to the fio objectstore engine

[Casey Bodley]

Hi folks,

I made another pass at the fio objectstore engine over the long weekend. Some 
of the major changes:

* added support for multiple jobs at a time by splitting global/ObjectStore 
initialization into a new Engine class

* when run with nr_files > 1, the objects are spread over multiple collections 
to model the concurrency we get from placement groups

* replaced other options with a 'conf' option to read in a ceph.conf

* moved into src/test/fio and added a README and example job/config files

You can find the pull request at https://github.com/ceph/ceph/pull/5943. 
Testing and feedback is appreciated!

Casey
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

nightlies moved to ovh (openstack)

[Yuri Weinstein]

In preparation to sepia lab move, nightlies' schedules were moved to
the ovh (openstack) lab.

See details here - http://tracker.ceph.com/projects/ceph-releases/wiki/ovh

Please let me know if you see any problems.

PS: I will optimize times/frequencies in next several days/weeks

Thx
YuriW
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling for FreeBSD

[Willem Jan Withagen]

On 30-11-2015 07:58, Mykola Golub wrote:
> On Mon, Nov 30, 2015 at 11:46:27AM +0800, Yan, Zheng wrote:
>> On Mon, Nov 30, 2015 at 2:57 AM, Willem Jan Withagen  
>> wrote:
...

Hi Mykola,

> I have a branch in my repo that contains patches to make compilation
> on FreeBSD easier:
> 
> https://github.com/trociny/ceph/commits/wip-freebsd

Right, I'll and see what you've all got worked out.
First get done with my daytime job that pays the rent.


> The branch have not been rebased against master since March though,
> still I hope to find time in future to update and pull some bits
> upstream.
> 
> Particularly, this patch contains packages dependencies list:
> 
> https://github.com/trociny/ceph/commit/2307706461ae09922c087065a8b50a04a61159b1

Right, I had most of those already figured out, but some much less obvious.

And the humor is on the first line... bash <> sh.
In just about all linux oriented software that is one of the things to
start with. FreePBX is also loaded with those.

I've sort of given up on this one, resistance is futile.
And I install bash in /bin.

> And this one configuration options I used
> 
> https://github.com/trociny/ceph/commit/dcee0c0635d37f2b36257c55a3cc69d05b5afe5e
>
> I have seen several commits since that time in master aimed to improve
> FreeBSD compilation, so I suppose some of my patches are not needed
> any more.
> 
> Still, if you experince issues building upstream Ceph on FreeBSD, and
> just want to try it on FreeBSD, you could try my branch:
> 
> git clone --recursive -b wip-freebsd https://github.com/trociny/ceph.git
> cd ceph
> ./install-deps.sh
> ./do_autogen.sh
> gmake
> cd src
> ./vstart.sh # start dev cluster
> ./ceph -s # check it works
> 

So what backend for the OSDs are you using here?

--WjW

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Does anyone know how to open clog debug?

[Wukongming]

Hi, All

Does anyone know how to open clog debug?

-
wukongming ID: 12019
Tel：0571-86760239
Dept：2014 UIS2 OneStor

-
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email immediately and delete it!

How to open clog debug?

[Wukongming]

Hi, All

Does anyone know how to open clog debug?

Thanks!

 Kongming wu
-
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email immediately and delete it!

Re: Compiling for FreeBSD

[Willem Jan Withagen]

On 30-11-2015 14:21, Sage Weil wrote:
> The problem with all of the porting code in general is that it is doomed 
> to break later on if we don't have (at least) ongoing build tests.  In 
> order for a FreeBSD or OSX port to continue working we need VMs that run 
> either gitbuilder or a jenkins job or similar so that we can tell when it 
> breaks.
> 
> If someone is willing to run a VM somewhere to do this we can pretty 
> easily stick it on the gitbuilder page at
> 
>   http://ceph.com/gitbuilder.cgi

Hi Sage,

Cool page that gitbuilder
Would be nice to have a FreeBSD builder in there as well. :)

Once I get things up and running, I will be able to supply either VMs
and/or actual hardware to do building and testing.

My personal problem is that I'm a longtime FreeBSD user (since 1993) and
now I'm sort of forced into (the) other OS. Because we like Ceph. So we
are building currently on Linux, but would like to have a FreeBSD
possibility as well.

But first I need to get the code to compile, and then actually run.
Long term goal is to use ZFS as basis, since this is a rock solid FS on
FreeBSD. And then integrate it with another nice FreeBSD thingy: bhyve.

Now I'm taking small baby steps at the moment, and do have other chores
as well. So progress might be slow, but I think I found some of the
issues I did not get to yet in the git of Mykola.

Thanx for the feedback.

Regards,
--Willem Jan


--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling for FreeBSD

[Mykola Golub]

On Mon, Nov 30, 2015 at 12:53:54PM +0100, Willem Jan Withagen wrote:

> > git clone --recursive -b wip-freebsd https://github.com/trociny/ceph.git
> > cd ceph
> > ./install-deps.sh
> > ./do_autogen.sh
> > gmake
> > cd src
> > ./vstart.sh # start dev cluster
> > ./ceph -s # check it works
> > 
> 
> So what backend for the OSDs are you using here?

The default one, which is FileStore. I have not done much testing
though...

-- 
Mykola Golub
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling for FreeBSD

[Sage Weil]

The problem with all of the porting code in general is that it is doomed 
to break later on if we don't have (at least) ongoing build tests.  In 
order for a FreeBSD or OSX port to continue working we need VMs that run 
either gitbuilder or a jenkins job or similar so that we can tell when it 
breaks.

If someone is willing to run a VM somewhere to do this we can pretty 
easily stick it on the gitbuilder page at

http://ceph.com/gitbuilder.cgi

sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: How to open clog debug

[Sage Weil]

On Mon, 30 Nov 2015, Wukongming wrote:
> Hi, All
> 
> Does anyone know how to open clog debug?

It's usually something like

monc->clog.debug() << "hi there\n";

sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Compiling for FreeBSD

[Willem Jan Withagen]

On 30-11-2015 15:13, Mykola Golub wrote:
> On Mon, Nov 30, 2015 at 12:53:54PM +0100, Willem Jan Withagen wrote:
> 
>>> git clone --recursive -b wip-freebsd https://github.com/trociny/ceph.git
>>> cd ceph
>>> ./install-deps.sh
>>> ./do_autogen.sh
>>> gmake
>>> cd src
>>> ./vstart.sh # start dev cluster
>>> ./ceph -s # check it works
>>>
>>
>> So what backend for the OSDs are you using here?
> 
> The default one, which is FileStore. I have not done much testing
> though...
> 

Well,
Cherry-picked a few of you diffs.
Compilation is now slugging thru the tests in my tree.
Running gmake in serial mode, so it is slow with clang.

--WjW


--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html