[rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file?

Boris Derzhavets bderzhavets at hotmail.com
Wed Aug 31 18:03:10 UTC 2016


Please, see detailed instructions here :-

Backport upstream commits to stable RDO Mitaka release && Deployments with Keystone API V3

http://bderzhavets.blogspot.ru/2016/05/backport-upstream-commits-to-stable-rdo.html

[https://4.bp.blogspot.com/-8KYSnMrQGmo/V0LYnpQFOkI/AAAAAAAAGrE/0WGJJh8kLeQfmCh4QsLnGKgJ7WfN_4-EQCLcB/w1200-h630-p-nu/Screenshot%2Bfrom%2B2016-05-23%2B12-48-25.png]<http://bderzhavets.blogspot.ru/2016/05/backport-upstream-commits-to-stable-rdo.html>

Xen Virtualization on Linux and Solaris: Backport upstream commits to stable RDO Mitaka release && Deployments with Keystone API V3<http://bderzhavets.blogspot.ru/2016/05/backport-upstream-commits-to-stable-rdo.html>
bderzhavets.blogspot.ru



Boris.

________________________________
From: rdo-list-bounces at redhat.com <rdo-list-bounces at redhat.com> on behalf of Taisto Qvist <taisto.qvist at gmail.com>
Sent: Wednesday, August 31, 2016 6:51:55 PM
To: Javier Pena
Cc: rdo-list
Subject: Re: [rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file?

Thanks for the tips everyone.

I found https://www.linux.com/blog/attempt-set-rdo-mitaka-any-given-time-delorean-trunks, and but that also failed with idv3, but on heat issues instead.

I am unfortunately completely lost/confused/overwhelmed with all the different git/repository information found in different places, and building my own RPMs feels way to complicated as someone linked to.

So I'll just clearly demonstrate my NooB-ness, by asking:

If I follow the instructions on "https://www.rdoproject.org/install/quickstart/", how do I modify them to update my packstack-* to use the newer modules mentioned below?

Regards
Taisto



2016-08-26 18:32 GMT+02:00 Javier Pena <javier.pena at redhat.com<mailto:javier.pena at redhat.com>>:


----- Original Message -----
> Fairly certain Cinder is a known problem against v3 in Packstack [1]
> but I don't have the details.
>
> [1]:
> https://github.com/openstack/packstack/blob/master/releasenotes/notes/keystone-v3-note-065b6302b49285f3.yaml
>

We had a patch to fix that merged in Mitaka some time ago [1], which depended on a puppet-cinder patch [2]. We have not yet released a new package to the CBS repos, but you could try updating your openstack-packstack, openstack-packstack-puppet and openstack-puppet-modules using the packages from RDO stable/mitaka Trunk [3].

Regards,
Javier

[1] - https://review.openstack.org/323690
[2] - https://review.openstack.org/320956
[3] - http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-mitaka-tested/


> David Moreau Simard
> Senior Software Engineer | Openstack RDO
>
> dmsimard = [irc, github, twitter]
>
>
> On Fri, Aug 26, 2016 at 11:57 AM, Taisto Qvist <taisto.qvist at gmail.com<mailto:taisto.qvist at gmail.com>>
> wrote:
> > Hi folks,
> >
> > I've managed to create a fairly well working packstack-answer file, that I
> > used for liberty installations, with a 4-multi-node setup, eventually
> > handling nested kvm, live-migration, LBAAS, etc, so I am quite happy with
> > that.
> >
> > Now, my aim is Identity v3. From the packstack answer-file, it seems
> > supported, but I cant get it to work. I couldnt get it to work with
> > liberty,
> > and now testing with Mitaka, it still doesnt work, failing on:
> >
> > ERROR : Error appeared during Puppet run: 10.9.24.100_cinder.pp
> > Error: Could not prefetch cinder_type provider 'openstack': Execution of
> > '/usr/bin/openstack volume type list --quiet --format csv --long' returned
> > 1: Expecting to find domain in project - the server could not comply with
> > the request since it is either malformed or otherwise incorrect. The client
> > is assumed to be in error. (HTTP 400) (Request-ID:
> > req-d8cccfb9-c060-4cdd-867d-603bf70ebf24)
> >
> >

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160831/5c02048c/attachment.html>


More information about the dev mailing list