Not that I can tell or get working. I was able to use the rbd container to
create images but couldn't use map from that container or the rbd-volume
container. Both failed with 'libkmod' and 'modprobe' errors trying to load
the rbd kernel module.
I'm not sure if this is my setup since I'm not
On Fri, Mar 4, 2016, at 06:59 PM, Josh Berkus wrote:
> One of the reasons I'm asking is that if most things are markdown, we
> can consider using ReadTheDocs. But if we've got a lot of ASCIIDocs, we
> can't.
I'd say there is two levels here: Global docs and per-project docs. We
should cross
On 11/03/16, Nick Coghlan wrote:
> Where Sphinx/reStructuredText is most powerful is in documenting
> software APIs, especially for low overhead documentation that is
> autogenerated from the Python docstrings, but there unfortunately
> aren't any DocbookXML converters that are aware of the
On 03/08/2016 10:47 AM, Matt Micene wrote:
>
> It sounds like we can if only because there's tooling issues with all of
> the various markups. What's the least amount of friction to getting new
> docs written? AsciiDoc?
I would think either AsciiDoc or Markdown. TBH, I've let myself get
behind
Nice preso, I saw the ceph-ansible repo the other day but hadn't gotten
around to trying it. I did poke at the ceph-rbd docker container in the
Hub, and that worked from an Atomic Host into the Ceph cluster I'd been
using to test the storage clients.
The repo for the docker images is here:
On Fri, Mar 4, 2016, at 02:24 PM, Josh Berkus wrote:
> Out of all the Atomic projects, what are people using for docs? Is it
> all ASCIIdoc, or do we have other formats?
rpm-ostree/ostree are Markdown via mkdocs:
I liked this blog:
http://www.sebastien-han.fr/blog/2016/02/29/mobile-world-congress-containerizing-ceph/
