openstack-doc-core team mailing list archive
-
openstack-doc-core team
-
Mailing list archive
-
Message #00028
Re: euca2ools in the docs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have to stay I'm still a fan of using <procedure> for lists of
steps. The semantics can come in handy and in DocBook, procedure isn't
so constrained like it is in DITA, so you don't have to put on a
straight jacket to use it.
I'm also a fan of titles on procedures (and generating a "List of
Procedures"), but I understand there are some cases where you need to
skip the title.
David
On 04/02/2012 01:15 PM, Lorin Hochstein wrote:
> I added some text in
> http://wiki.openstack.org/Documentation/Conventions
> <http://wiki.openstack.org/Documentation/Conventions#preview> to
> capture the outcome ofthis email thread.
>
> Take care,
>
> Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis
> Services, Inc. www.nimbisservices.com
> <https://www.nimbisservices.com/>
>
>
>
> On Mar 31, 2012, at 4:44 PM, Razique Mahroua wrote:
>
>> Hi, in fact there are still some features nova cli doesn't have -
>> for instance euca-get-console-output. I started a big transition
>> euca -> nova cli few months ago, but I surely would have missed
>> some. Feel free to fill a bug when you catch euca commands.
>>
>> On Sat, 31 Mar 2012 00:25:13 +0200, Anne Gentle
>> <anne@xxxxxxxxxxxxx <mailto:anne@xxxxxxxxxxxxx>> wrote:
>>
>>> I agree with this approach - one topic on how to get
>>> credentials to work with euca2ools, and another that describes
>>> the differences should suffice. It'll save us a lot of
>>> maintenance in the long term. Some pain in the cleanup but for
>>> good gains, I believe.
>>>
>>> Thanks Lorin for bringing it up and proposing a solution.
>>>
>>> Anne
>>>
>>> On Fri, Mar 30, 2012 at 3:27 PM, Lorin Hochstein
>>> <lorin@xxxxxxxxxxxxxxxxxx <mailto:lorin@xxxxxxxxxxxxxxxxxx>>
>>> wrote:
>>>> Do we still need to document euca2ools commands in the docs
>>>> if there's an equivalent nova command? The admin docs look
>>>> inconsistent right now, sometimes documenting the euca2ool
>>>> equivalent, and sometimes not.
>>>>
>>>> I'd be happier if we just removed all euca2ools equivalent
>>>> commands, and only document euca2ool-related stuff like: -
>>>> How do I get credentials to work with euca2ools? - What are
>>>> the differences between how Amazon's EC2 endpoint behaves and
>>>> how an OpenStack endpoint behaves when accessing via EC2.
>>>>
>>>>
>>>> Take care,
>>>>
>>>> Lorin -- Lorin Hochstein Lead Architect - Cloud Services
>>>> Nimbis Services, Inc. www.nimbisservices.com
>>>> <http://www.nimbisservices.com>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -- Mailing list: https://launchpad.net/~openstack-doc-core
>>>> Post to : openstack-doc-core@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:openstack-doc-core@xxxxxxxxxxxxxxxxxxx> Unsubscribe :
>>>> https://launchpad.net/~openstack-doc-core More help :
>>>> https://help.launchpad.net/ListHelp
>>>>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPef5YAAoJEMHeSXG7afUhWqwH/A5BBy7oxKwkNQ8r96r07phl
RbhvMHFvkDWOvPBFTc3I0EUXVJ6fI4tBwFl4XoJyQ21DX7gOydUyZYr5PBYbG6cO
7cuGISUlBFvrMEQwavwhK9K3tojjFSgFrfXpT96wtNi9+PSYsU235B0y67X3+T+h
fQGCpzkYkAQ9ZLcQ92O2epYsY7eYn6Mb/WVwm4X5kwEsTRVHgRfkvlE38AiHAmTz
IMvhpNRmCOPL6mQB7BgAlPD3sJK1vk9HwDoXiS+N1UOF8evkaFMF+Wuh57+hTJKw
xNr2ZkkMYRlZiIjRnc0og6AtdHrFSWsSyP1LT7XBcFpf9QR8G3LtvwroM/62UAY=
=YCr0
-----END PGP SIGNATURE-----
Follow ups
References