Open Stack

Denis Makogon writes:

> On Mon, Jul 7, 2014 at 3:40 PM, Amrith Kumar <amrith at tesora.com> wrote:
>
>> Denis Makogon (dmakogon at mirantis.com) writes:
>>
> [...]
>>
>> I think it is totally ludicrous (and to all the technical writers who work
>> on OpenStack, downright offensive) to say the “docs are useless”. Not only
>> have I been able to install and successfully operate a OpenStack
>> installation by (largely) following the documentation, but
>> “trove-integration” and “redstack” are useful for developers but I would
>> highly doubt that a production deployment of Trove would use ‘redstack’.
>>
>
> Amrith, those doc doesn't reflect any post-deployment steps, even more, doc
> still suggesting to use trove-cli that was deprecated long time ago. I do
> agree that trove-integration project can't be used as production deployment
> system, but first try-outs - more than enough.
>

I think we're doing ourselves a great disservice here by calling our own
docs "useless", and yet not taking any steps to correct the issue at
hand. If the docs are missing certain key steps we need to ensure that
they are updated and improved as we go along. I, for one, am pretty
certain that the image building and post-deploy steps for trove do work,
since that's what we currently use in the image build job and the
integration tests, and they've been passing pretty consistently.

I'm going to add a "Scrub the Docs" agenda item to this week's Trove
meeting. I'd really like those of us who have a few cycles to clean-up
the docs we have, and make sure that information in them is
up-to-date. I can help lead this effort.


> FYI, Trove is not fully integrated with devstack, so, personally i'd
> suggest to use https://github.com/openstack/trove-integration[3]  simple (3
> clicks) Trove + DevStack deployment.

This is no longer true. We've recently done a lot of work here to get
Trove fully integrated with devstack. A trove guest-image is now
uploaded into glance as part of the trove install in devstack.
Appropriate default datastores, and versions are also created, making
the trove install fully usable.

If you're running trove functional tests, you probably want to stick
with trove-integration for now, since it sets up some test conf values
that are needed for the functional tests. But if all you need to do is
to take trove for an end-to-end test-run, a devstack install with the
trove services enabled should be sufficient.


Syed, if you're still having trouble with any of this, pleas feel free
to reach out to me or anyone else on #openstack-trove. We'd be happy
to assist you with any issues you might have encountered.

Hope this helps,

Thanks,
Nikhil