On 04/25/2012 11:04 PM, Brown, David M JR wrote: > Fedora Devs, > > I just spent the last couple of days fighting with Essex on RHEL6 and its > been entertaining and I'd like to share some of the oddities and experiences.
Thanks a lot for taking the time to write this up, and test these packages. > System configuration is the following. > > Two nodes on their own /24 connected by cross over to each other on the > second interface. > The first node is the cloud controller and has tons of storage (11T) and 32Gb > ram and 16 cores > The second node I would like to make an extra compute node and it has 24Gb > ram and 8 cores (still in a work in progress) > > Originally the cloud controller was running Diablo on RHEL6 and was working > fine. > > I couldn't find any 'upgrade' instructions for going between Diablo and Essex > and I wasn't too worried because the usage of the cloud was limited to just a > couple of guys. So I was satisfied with backing up manually all the data and > rebuild the cluster. I noticed when I did the update that things stopped > working and following the install instructions blew away all local data in > the cloud. > > I was following the instructions found at the following URL. > > http://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL > > I got the packages from > > http://pbrady.fedorapeople.org/openstack-el6/ > > First issue. Wow, this is long, its almost long enough that making an uber > script in a common package somewhere to run would strip out of most of the > manual commands to run. > I'd suggest first pulling out all the openstack-config-set commands and put > them in a script to run. Good idea :) We're working on something very much like that: https://github.com/fedora-openstack/openstack-utils/blob/master/utils/openstack-demo-install That file should already be on your system, but it's very early stage, and still being finalized. > Not sure what to do about the swift documentation bits, that seems like a > very manual set of configurations why aren't they part of the swift rpm? > Another suggestion would be to split it out into a couple of documents one > describing installation and configuration then the next describing putting > data/users into it and starting stuff? thoughts? > > After I got everything setup and working I noticed an issue with the > dashboard, most of the static stuff wasn't showing up I had to add a symlink. > /usr/share/openstack-dashboard/static -> openstack_dashboard/static > Then the dashboard picked up the right stuff and it worked. Were you using django 1.3 from epel-testing? That particular issue was solved with that I think. I presume you've seen http://pbrady.fedorapeople.org/openstack-el6/README, which contains instructions that should install django 1.3, though you may have been unlucky with a slow mirror serving you Django 1.2? > > There's some consistency issues and I'm not sure if this is an openstack > issue in general. The euca tools and how you configure them with keystone > only seem to work with your personal instances and configuration. However, > the dashboard seems to show users everything associated with the project > instead. For example when I allocate floating IPs from the website those > won't show up when I run euca-describe-addresses and respectively > euca-allocate-address won't show up the IP allocated in the dashboard. I've > looked at the database and the project ids are used when using the dashboard > and user ids are used when using the euca tools. I think the euca tools could > be setup to see everything that the dashboard sees however the documentation > doesn't point to how to do that. Noted. BTW we've been looking at migrating instructions away from euca tools to the equivalent openstack tools (nova-manage etc.) > There also seems to be some serious functionality faults that I can't seem to > make work. I can't make a user attached to multiple projects, not sure how to > do that. Also, seems like there's a lot of, "huh, that doesn't seem > implemented yet." However, this seems like a general openstack issue, > documentation says X but that doesn't work yet or anymore. > > I'm having a serious issue not getting a the second compute node working > `nova-manage service list' doesn't show ':-)' for the compute and network > services running on that node. I've followed the instructions to the letter > and tried getting things working but its not going. For debugging issues I find looking in /var/log/nova/*.log informative, especially with verbose = True in nova.conf cheers, Pádraig. _______________________________________________ cloud mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/cloud
