1 |
Konstantinos Agouros <elwood <at> agouros.de> writes: |
2 |
|
3 |
|
4 |
> I tried to install sys-cluster/nova but this gives me a 'block' as some |
5 |
> of the python modules it wants do not work in one install. Anybody had |
6 |
> success in getting a Gentoo Box to be a compute node for OpenStack? |
7 |
|
8 |
|
9 |
Looking at /usr/portage/sys-cluster/openstack-meta/ |
10 |
openstack-meta-2014.1.9999.ebuild |
11 |
I see: |
12 |
|
13 |
|
14 |
|
15 |
EAPI=5 |
16 |
|
17 |
DESCRIPTION="A openstack meta-package for installing the various openstack |
18 |
pieces" |
19 |
HOMEPAGE="https://openstack.org" |
20 |
|
21 |
LICENSE="Apache-2.0" |
22 |
SLOT="0" |
23 |
KEYWORDS="" |
24 |
IUSE="keystone swift neutron glance cinder nova horizon" |
25 |
|
26 |
DEPEND="" |
27 |
RDEPEND="keystone? ( ~sys-auth/keystone-2014.1.9999 ) |
28 |
swift? ( ~sys-cluster/swift-2014.1.9999 ) |
29 |
neutron? ( ~sys-cluster/neutron-2014.1.9999 ) |
30 |
glance? ( ~app-admin/glance-2014.1.9999 ) |
31 |
cinder? ( ~sys-cluster/cinder-2014.1.9999 ) |
32 |
nova? ( ~sys-cluster/nova-2014.1.9999 ) |
33 |
horizon? ( ~www-apps/horizon-2014.1.9999 )" |
34 |
|
35 |
|
36 |
|
37 |
So all are using the latest release (*.9999) of these packages. |
38 |
I'd go and look in BGO for bugs related to nova. |
39 |
|
40 |
sys-cluster/nova is not maintained by the gentoo cluster herd: |
41 |
http://gentoobrowse.randomdan.homeip.net/herd/cluster |
42 |
|
43 |
The gentoo cluster project is similar but not the same as the |
44 |
cluster herd: |
45 |
https://www.gentoo.org/proj/en/cluster/ |
46 |
|
47 |
Some devs (hi Rich) are working on consolidation of herds and projects. |
48 |
|
49 |
The herd lists what they maintain, although it may not be current. |
50 |
BGO Bug 494026 says the security team has masked this package |
51 |
for vulnerabilities. It's not straightforward to tell who exactly |
52 |
is maintaining nova. It may by "up for grabs" for a (proxy) maintainter. |
53 |
Just search out "nova" on BGO. |
54 |
|
55 |
|
56 |
|
57 |
Also, after the herd decprecation is complete, and some other things |
58 |
are finalized, it shlould be clear who is maintaining what codes, |
59 |
Who is on what project team and if a code (package) is not claimed |
60 |
by a team, then the individual (dev or proxy) that is maintaining the |
61 |
code. Or this is my understanding/speculation on how it's gonna work. |
62 |
|
63 |
Ok, so from here all you gotta do is *dig* a bit. |
64 |
|
65 |
Also look for overlays on nova and the other "Depends" in the openstack |
66 |
ebuild to work around your issues. Also, often there is a way to get |
67 |
around hard masks if you choose to go that path. |
68 |
|
69 |
Goodhunting! |
70 |
James |