All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Watts <mwatts@redhat.com>
To: ceph-devel@vger.kernel.org
Subject: civetweb, sts work
Date: Wed, 9 Mar 2016 03:35:04 -0500	[thread overview]
Message-ID: <20160309083504.GA1862@degu.b.linuxbox.com> (raw)

I've just pushed out two new ceph branches, and I pushed out
a revised copy of civetweb that these both use.

I've pushed my git branches to git@github.com:ceph/ceph.git
They are:
wip-openssl-2
	( based on recentish master. )
	ssl patches (should be the same as what's already in master)
	+ "build out of tree" am changes (as described previously)
	+ civetweb "ng" changes.
		I've managed to build this with both cmake and configure.
		I haven't had time to do any testing past that yet.
		It "should" all work of course...
wip-rgw-sts-3
	everything that's in wip-openssl-2
	+ rgw-sts work.
	includes polymorphic rgw error object
	split out of some parts of rgw rest interface into objstore
		+ "generic" bits. (sts isn't an object store)
	basic sts encode/decode stuff.
		I've managed to build this with both cmake and configure.
		I haven't had time to do any testing past that yet.
		All the basic bits should work.
		The radosgw parts should work if I haven't broken them.
		The sts parts are still missing a lot of functionality.

I pushed my civitweb stuff to https://github.com/mdw-at-linuxbox/civetweb
Probably should should go to ceph/civetweb but I haven't had time
to follow up on that yet.
wip-easy1
	( based on recent upstream civetweb release)
	+ cmake build changes (builds w/ cmake on linux)
	+ modifications to support all of the functionality used by ceph,
		hopefully in a form that can be accepted by the civetweb
		folks upstream.
		I've built this standalone, and gotten it to pass all
		of its self-test logic.  I haven't done any other testing yet.

I imagine I'll find out "tomorrow" what gitbuilder thought
of all this.
	{ Hm.  rocksdb might catch me up.  I'm building with "rocksdb-devel",
		but I haven't touched ceph.spec.in ... }

Next steps on the roadmap,
fix whatever gitbuilder finds
auth_mellon-like functionality for sts
radosgw token changes
radosgw userdb changes

other bits along the side,
push rocksdb changes to rocksdb upstream
push civetweb changes to civetweb upstream
document using openssl w/ civetweb
{ and figure out how to hack gitbuilder rocksdb rpm/deb stuff... }

						-Marcus Watts

             reply	other threads:[~2016-03-09  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  8:35 Marcus Watts [this message]
2016-03-09 15:32 ` civetweb, sts work Matt Benjamin
2016-03-09 19:53   ` Marcus Watts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160309083504.GA1862@degu.b.linuxbox.com \
    --to=mwatts@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.