2:54 p.m.
Guys,
Since I found that our documentation is full of obsolete information,
I tried to reach to people responsible for RDO privately. The response
wasn't particularly helpful, circling back to the same useless docs:
> Yes, that's the right one and you can find some other info
in:
>
> https://www.rdoproject.org/documentation/rdo-packaging-guidelines/
>
> RDO project just migrated to https://review.rdoproject.org/dashboard/
> and we are still working to update the documentation to reflect these
> changes.
> Best regards,
> Alfredo
*headdesk*
Dashboard is not even the repo! It's for reviews only!
Meanwhile, all the documents we have continue to state things like:
RDO packages currently use Fedora dist-git and fedpkg is used to obtain it,
for example:
$> fedpkg clone openstack-nova
......
With all the prerequisites met, it's time to clone the package dist-git
using fedpkg.
$> fedpkg clone openstack-$PROJECT
(in https://www.rdoproject.org/documentation/rdo-packaging/)
Naturally, anyone doing "fedpkg clone openstack-swift" gets a
"dead.pacakge"
stub.
So, what do everyone clone? If someone could do this, it would be helpful:
grep url openstack-nova/.git/config
Greetings,
-- Pete
5:44 p.m.
2016-05-29 21:54 GMT+02:00 Pete Zaitcev <zaitcev(a)redhat.com>:
Guys,
Since I found that our documentation is full of obsolete information,
I tried to reach to people responsible for RDO privately. The response
wasn't particularly helpful, circling back to the same useless docs:
> > Yes, that's the right one and you can find some other info in:
> >
> > https://www.rdoproject.org/documentation/rdo-packaging-guidelines/
> >
> > RDO project just migrated to https://review.rdoproject.org/dashboard/
> > and we are still working to update the documentation to reflect these
> > changes.
> > Best regards,
> > Alfredo
*headdesk*
Dashboard is not even the repo! It's for reviews only!
Meanwhile, all the documents we have continue to state things like:
RDO packages currently use Fedora dist-git and fedpkg is used to obtain it,
for example:
$> fedpkg clone openstack-nova
......
With all the prerequisites met, it's time to clone the package dist-git
using fedpkg.
$> fedpkg clone openstack-$PROJECT
(in https://www.rdoproject.org/documentation/rdo-packaging/)
Naturally, anyone doing "fedpkg clone openstack-swift" gets a
"dead.pacakge"
stub.
So, what do everyone clone? If someone could do this, it would be helpful:
rdopkg clone openstack-swift
and then git review on rpm-master.
Jakub and Alfredo are working on refreshing the docs, meanwhile; if
you have anything urgent
on stable branches, ping me directly.
I'm currently focusing in shortening the delay between upstream
releases and RDO releases.
The next step will be automating stable branches builds.
H:
grep url openstack-nova/.git/config
Greetings,
-- Pete
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
6:17 p.m.
On Mon, 30 May 2016 00:44:29 +0200
Haïkel <hguemar(a)fedoraproject.org> wrote:
> So, what do everyone clone? If someone could do this, it would
be helpful:
rdopkg clone openstack-swift
and then git review on rpm-master.
Thanks a lot, that worked!
BTW, it would be great if we could do "rdopkg clone rdopkg" perhaps?
-- Pete
4:09 a.m.
2016-05-30 1:17 GMT+02:00 Pete Zaitcev <zaitcev(a)redhat.com>:
On Mon, 30 May 2016 00:44:29 +0200
Haïkel <hguemar(a)fedoraproject.org> wrote:
> > So, what do everyone clone? If someone could do this, it would be helpful:
> rdopkg clone openstack-swift
> and then git review on rpm-master.
Thanks a lot, that worked!
BTW, it would be great if we could do "rdopkg clone rdopkg" perhaps?
-- Pete
rdopkg clone uses rdoinfo database, that's why it doesn't work (only
openstack projects are registered)
But that's something we could fix.
H.
5:46 p.m.
On 05/30/2016 05:09 AM, Haïkel wrote:
2016-05-30 1:17 GMT+02:00 Pete Zaitcev <zaitcev(a)redhat.com>:
> On Mon, 30 May 2016 00:44:29 +0200
> Haïkel <hguemar(a)fedoraproject.org> wrote:
>
>>> So, what do everyone clone? If someone could do this, it would be helpful:
>> rdopkg clone openstack-swift
>> and then git review on rpm-master.
> Thanks a lot, that worked!
>
> BTW, it would be great if we could do "rdopkg clone rdopkg" perhaps?
>
> -- Pete
rdopkg clone uses rdoinfo database, that's why it doesn't work (only
openstack projects are registered)
But that's something we could fix.
My quick write up
http://adam.younglogic.com/2016/05/reviews-for-rdo-packages/
H.
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
On 05/25/2016 11:52 PM, Adam Young wrote:
I confirmed today that Kerberos still works for both WebSSO and CLI
operations on a Rippowam provisioned server. However, I think we need
to chase down the Kerberos Auth plugin. As things moved from
keystonclient to Keystone Auth, I don;'t remember what the final
decision was for Kerberos. To be strictly correct, it should
probablty move to python-keystoneauth-kerberos.
Trying ECP seems to be close, but not quite set up right. I am using
the following rc file:
$ cat keycloak-accrc
export OS_AUTH_TYPE=v3unscopedsaml
export OS_AUTH_URL=https://openstack.ayoung.oslab.test:5000/v3
export OS_IDENTITY_PROVIDER=keycloak
export
OS_IDENTITY_PROVIDER_URL=https://ipa.ayoung.oslab.test/auth/saml2/SSO/SOAP
export OS_PROTOCOL=saml2
export OS_PROJECT_NAME=demo
export OS_PROJECT_DOMAIN_ID=default
export OS_IDENTITY_API_VERSION=3
(prompts for password and userid ellided)
The post to https://ipa.ayoung.oslab.test/auth/saml2/SSO/SOAP seems to
be failing with:
DEBUG: requests.packages.urllib3.connectionpool "POST
/auth/saml2/SSO/SOAP HTTP/1.1" 404 0
DEBUG: keystoneclient.session Request returned failure status: 404
ERROR: openstack Not Found (HTTP 404)
Do I have the OS_IDENTITY_PROVIDER_URL right? The remote ID for this
server is
remote_ids | [u'https://ipa.ayoung.oslab.test/auth/realms/openstack']
Which works with WebSSO. If I mess around with the PROVIDER_URL I
still get the same response. The tests
https://github.com/keycloak/keycloak/blob/master/testsuite/integration/sr...
seem to indicate that it should be /ecp-sp/ but that does not work,
either.
3141
days inactive
3143
days old
4 comments
3 participants
participants (3)
-
Adam Young -
Haïkel -
Pete Zaitcev