Open Stack

I'm also using OSC whenever possible, but lack of documentation at least
containing common examples likely isn't helping overall adoption of OSC. We
can't expect the documentation team to deploy a cloud containing all
services that OSC supports, determine the most common operations for each
service, and contribute/test/maintain examples for them. Rather, each
project should contribute/test/maintain OSC examples.

On Mon, Jul 11, 2016 at 12:32 PM, Anne Gentle <annegentle at justwriteclick.com
> wrote:

> On Mon, Jul 11, 2016 at 1:12 PM, Matt Kassawara <mkassawara at gmail.com>
> wrote:
> > While working on some content for the networking guide, I wanted to link
> to
> > the user guide if the audience requires additional help with OpenStack
> > client commands. However, the user guide only seems to include the legacy
> > clients. What's the plan for updating it with OpenStack client content?
> The
> > CLI reference isn't particularly useful by itself.
>
> I've had recent patches where I've made sure commands are openstack
> commands. I think we should generally always require openstack on new
> content and any edits as well. Seems like we are in reviews lately.
>
> There isn't a known change effort at this point however. If someone
> wants to take it on, it's a fairly straightforward task. Pre-reqs
> would be a working cloud and the latest clients, so you can test
> before updating.
>
> Anne
>
> >
> > _______________________________________________
> > OpenStack-docs mailing list
> > OpenStack-docs at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> >
>
>
>
> --
> Anne Gentle
> www.justwriteclick.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20160711/24b880da/attachment.html>