cloud November 2011

cloud@lists.fedoraproject.org

36 participants
33 discussions

Running horizon/dashboard from git
by Cole Robinson 17 Jan '12

17 Jan '12

Below are some steps to get openstack horizon (aka dashboard) kinda running. I'm still having issues with talking to nova, hopefully its just a small config problem. Assumes we are starting from a setup similar to http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova # Not sure if it's required, but this is how I was running sudo setenforce 0 sudo service iptables stop # First we need to set up keystone, since horizon requires it. sudo yum install -y openstack-keystone # Clear any previous keystone config sudo rm /var/lib/keystone/keystone.sqlite sudo systemctl start openstack-keystone.service # These steps are derived from # http://keystone.openstack.org/configuringservices.html # Assumes that openstack, keystone, and dashboard are all on localhost sudo keystone-manage service add nova compute "Nova Compute Service" sudo keystone-manage service add glance image "Glance Image Service" sudo keystone-manage service add keystone identity "Keystone Identity Service" sudo keystone-manage endpointTemplates add RegionOne nova \ http://localhost:8774/v1.1/ \ http://localhost:8774/v1.1/ \ http://localhost:8774/v1.1/ \ 1 1 sudo keystone-manage endpointTemplates add RegionOne glance \ http://localhost:9292/v1.1/ \ http://localhost:9292/v1.1/ \ http://localhost:9292/v1.1/ \ 1 1 sudo keystone-manage endpointTemplates add RegionOne keystone \ http://localhost:5000/v2.0 \ http://localhost:35357/v2.0 \ http://localhost:5000/v2.0 \ 1 1 sudo keystone-manage user add admin admin sudo keystone-manage user add demo demo sudo keystone-manage tenant add admin sudo keystone-manage tenant add demo sudo keystone-manage role add Admin sudo keystone-manage role grant Admin admin admin sudo keystone-manage token add 999888777666 admin admin 2015-02-05T00:00 sudo keystone-manage role add Member sudo keystone-manage role grant Member demo demo sudo keystone-manage role grant Admin admin demo sudo keystone-manage endpoint add demo nova sudo keystone-manage endpoint add demo glance sudo keystone-manage endpoint add demo identity sudo keystone-manage endpoint add admin nova sudo keystone-manage endpoint add admin glance sudo keystone-manage endpoint add admin identity # Checkout horizon (aka dashboard) git clone git://github.com/openstack/horizon.git horizon.git cd horizon.git git branch --track diablo remotes/origin/stable/diablo git checkout diablo # Now we set up a local environment with all the required dashboard # dependencies, without polluting our system configuration. dashboard # supplies tools for this but some tweaks are needed. sudo yum install -y bzr python-coverage cd openstack-dashboard edit tools/pip-requires, comment out the quantum git URL (reason: https://bugs.launchpad.net/horizon/+bug/888385) python tools/install_venv.py # Manually install quantum into the virtual environment git clone https://github.com/openstack/quantum.git quantum.git cd quantum.git/common ../../tools/with_venv.sh python setup.py install cd ../client ../../tools/with_venv.sh python setup.py install cd ../.. # Run unit tests. Currently looks like 2 tests are failing with a glance # import issue: 'module' object has no attribute 'Error' ./run_tests.sh # No unexpected failures, great! Let's configure the dashboard cd openstack-dashboard # needed by glance imports but wasn't installed automatically ./tools/with_venv.sh pip --verbose install --environment .dashboard-venv/ pycrypto # Actually run the dashboard ./tools/with_venv.sh python dashboard/manage.py runserver syncdb ./tools/with_venv.sh python dashboard/manage.py runserver 127.0.0.1:9000 firefox 127.0.0.1:9000 # should see a login page, accounts are demo:demo or admin:admin log in with admin:admin, it should work! # If openstack-nova-api isn't running, you will see and error like: Unable to get usage info: [Errno 111] Connection refused # If nova-api is running, on log in there will be an error like: Unable to get usage info: This error may be caused by a misconfigured nova url in keystone's service catalog, or by missing openstackx extensions in nova. See the dashboard README. # Not required, but easy to setup the django debugging toolbar ./tools/with_venv.sh pip --verbose install --environment .dashboard-venv/ django-debug-toolbar add the following to local/local_settings.py INTERNAL_IPS = ('127.0.0.1',) DEBUG_TOOLBAR_CONFIG = { "INTERCEPT_REDIRECTS" : False, } # Configure nova to use openstackx admin extension # According to README at: https://github.com/openstack/horizon/blob/stable/diablo/openstack-dashboard… git clone git://github.com/cloudbuilders/openstackx.git /tmp/openstackx cd /tmp/openstackx git branch --track diablo remotes/origin/diablo git checkout diablo Set --osapi_extensions_path=/tmp/openstackx/extensions in /etc/nova/nova.conf sudo systemctl restart openstack-nova-api.service restart dashboard, login # Hmm, didn't change anything? Let's try and configure nova to use # keystone according to instructions at # http://keystone.openstack.org/configuringservices.html#setting-up-openstack… git clone git://github.com/openstack/keystone.git /tmp/keystone Add --api_paste_config=/tmp/keystone/examples/paste/nova-api-paste.ini to /etc/nova/nova.conf sudo systemctl restart openstack-nova-api.service restart dashboard, login # Something changed... error is now: Unable to get usage info: 401 Unauthorized This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required. And that's all I've got for now. The error messages don't prevent poking at some of the UI, but nothing useful like instances are listed. I'd like to find some simple way to test that nova and keystone are working together, so if anyone has ideas that would be appreciated. Thanks, Cole

5 14

openstack-nova update
by Russell Bryant 06 Dec '11

06 Dec '11

Greetings, I just pushed out an update to openstack-nova: https://admin.fedoraproject.org/updates/openstack-nova-2011.3-8.fc16 https://admin.fedoraproject.org/updates/openstack-nova-2011.3-9.el6 It resolves the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=735012 openstack-nova is now set up to use MySQL by default instead of SQLite. To help make the setup a bit easier, there is a script that will set up MySQL for you: openstack-nova-db-setup. Please give it a try and let me know if you have any trouble. If everything looks good, give it some karma. Thanks, -- Russell Bryant

4 7

openstack-nova default database
by Russell Bryant 29 Nov '11

29 Nov '11

Greetings, A few weeks ago I spent some time looking into a bug [1] that came up back when we had the test day. The bug showed a "database locked" error when sqlite was used. In short, using sqlite with nova is not a reliable combination. I'd like to get some consensus on a good way to address that. Some options ... 1) Update the docs to strongly recommend switching to MySQL as a part of the setup process. 2) Don't even bother having the packages set up for sqlite at all. Switch to mysql by default. I'd like to take path #2 here. It seems like a bad idea to provide a default configuration that we know will fail at times. If we do take this path, what's the best way to go about it? We can have nova set up to use MySQL and point it at localhost with some default credentials. Should we do more? Provide a trivial script for creating the nova database and user? Have an optional openstack-nova-db package that pulls in MySQL and automatically creates the db? I don't want to try to make things too smart and then end up causing pain for administrators. Thoughts? Thanks, [1] https://bugzilla.redhat.com/show_bug.cgi?id=735012 -- Russell Bryant

3 4

Submitted two hackfest proposals to FUDCon around Aeolus
by Mo Morsi 28 Nov '11

28 Nov '11

As you can read on my blog [1], I've submitted two proposals around developing Aeolus tooling to FUDCon Blacksburg, coming up this upcoming January. These usually take some time to prepare so I'm planning on doing some work on this front come this upcoming December. But if all goes as planned (and if the proposals are accepted) it'll be a good way to get people familiar w/ the Aeolus components, and how to use them to deploy, monitor, and migrate instances on the cloud from Fedora. Take care! -Mo [1] http://mo.morsi.org/blog/node/351

1 0

Re: OpenStack status
by Mark McLoughlin 28 Nov '11

28 Nov '11

Hey, And updates specifically from the past week or so: - We had some discussion about how to improve communication between everyone working on OpenStack in Fedora and encourage more folks to help out: http://lists.fedoraproject.org/pipermail/cloud/2011-November/000956.html - An "Open Source Cloud and Virtualization" dev room has been announced for FOSDEM in Brussels on Feb 4-5th: http://lists.fedoraproject.org/pipermail/cloud/2011-November/000954.html - A big openstack-nova update was pushed with ~20 significant updates from the upstream stable branch: https://admin.fedoraproject.org/updates/FEDORA-2011-15887 - Pádraig has continued the work on EPEL6 and posted an update: http://lists.fedoraproject.org/pipermail/cloud/2011-November/000970.html The current status is that I have nova and glance services running and passing very basic tests. I'm using 2 packages not yet in EPEL though. python-webob: 0.9.6 in RHEL6.2, 1.0.8 in F1[56] python-sqlalchemy: 0.5.5 in RHEL6.2, 0.6.8 in F15 - Bob Kukura has been working on packaging Diablo's Quantum and will post a package for review soon. This has been complicated by the fact that Quantum in Essex has undergone major changes to make it easier to package. - Russell Bryant has been looking into how we might go about running OpenStack with Apache Qpid rather than RabbitMQ. - Alan Pevec is preparing a keystone update based on the latest upstream stable branch. He has also been debugging various issues with keystone. - Cole Robinson has been working on getting Dashboard running on Fedora and has also run into keystone issues. - I hit an issue with attaching a volume to an instance running on a remote compute node: https://bugzilla.redhat.com/752709 There's a fix proposed in gerrit which can be pulled into Fedora. - There's been a little bit more progress on making Nova use libguestfs: https://bugzilla.redhat.com/734727 Rich and Pádraig are working up a plan. Also, Andrey from Grid Dynamics pointed out that we actually really need this for EPEL6 since the nbd kernel driver isn't supported on RHEL6. - Rich also posted an analysis of Nova's file injection code: https://www.redhat.com/archives/libguestfs/2011-November/msg00027.html - Derek Higgins got a fix merged upstream to have an instance's "managed save" image removed when the VM is undefined: https://bugzilla.redhat.com/740456 - The weird AMQP issue we saw once or twice during the test day has undergone serious debugging by folks upstream, but the root cause hasn't been identified yet: https://bugzilla.redhat.com/747568 - Russell took a look at the "database is locked" errors we see with sqlite and concluded that using SQLite is probably hopeless and we should switch to MySQL by default: https://bugzilla.redhat.com/735012 Cheers, Mark.

4 3

openstack in EPEL status
by Pádraig Brady 24 Nov '11

24 Nov '11

I've been looking recently at getting the diablo release of openstack running on RHEL6.2 beta with support from EPEL. The current status is that I have nova and glance services running and passing very basic tests. I'm using 2 packages not yet in EPEL though. python-webob: 0.9.6 in RHEL6.2, 1.0.8 in F1[56] python-sqlalchemy: 0.5.5 in RHEL6.2, 0.6.8 in F15 The RHEL6.2 versions of these packages are too old to support openstack. Now it's not practical to update those for RHEL6.2 and I've requested consideration for RHEL6.3. In the meantime I think it's probably best to have parallel installable versions of those packages in EPEL, given EPEL's mandate of not updating RHEL packages: http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies So we might have a python-webob10 package in EPEL, and adjust the openstack packages accordingly. There is precedent for this in packages like python-sphinx10 I will consider again adjusting openstack to be directly compatible with the RHEL6.2 versions of these packages, but on first look, that approach seems quite invasive. Another outstanding task which should be completed soon is to support libguestfs as a means to update guest images. openstack uses NBD currently but that is unavailable in RHEL6 as it was supplanted by iSCSI. NBD is a little hacky anyway so this should be a better approach: https://bugs.launchpad.net/nova/+bug/719325 To test these changes I'm using the instructions from: https://fedoraproject.org/wiki/Test_Day:2011-10-20_OpenStack_Test_Day Some config changes were required over that done for Fedora 16: SELinux This works in F16 but I'm not worrying about it for the moment in RHEL # setenforce 0 # sed -i 's/^SELINUX=enforcing/SELINUX=permissive/' /etc/selinux/config qpidd and matahari These services may be enabled by default in some RHEL6.2 releases, and conflict at the TCP port level at least. I guess we could put rabbitmq on a different port, and there was talk about qpidd being used over amqpd, but for now I did: for svc in matahari-broker matahari-host matahari-network \ matahari-service matahari-sysconfig qpidd; do service $svc stop chkconfig $svc off done nova-manage db sync I needed to run the above before I could start openstack-nova-* services. TODO: check whether that needs to be run at install time. There are issues with RHEL6 running VM running VMs themselves, which was one of the test modes for the F16 test day above. For now all testing is done on bare metal. cheers, Pádraig.

5 18

Swift traceback on Rawhide F17
by Pete Zaitcev 23 Nov '11

23 Nov '11

Hi, Alan: Does the following look familiar to you by any chance (after swift-init main start): Traceback (most recent call last): File "/usr/bin/swift-proxy-server", line 22, in <module> run_wsgi(conf_file, 'proxy-server', default_port=8080, **options) .................. File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 659, in find_egg_entry_point for prot in protocol_options] or '(no entry points)')))) LookupError: Entry point 'tempauth' not found in egg 'swift' (dir: /usr/lib/python2.7/site-packages; protocols: paste.filter_factory, paste.filter_app_factory; entry_points: ) Thanks, -- Pete

5 11

Snap! Update
by Mo Morsi 22 Nov '11

22 Nov '11

Just an update on progress w/ Snap [1], the cross-platform system snapshot / restoration tool that I've been working on. I've added windows support to the project, thus it is now possible to use Snap to migrate windows instances across cloud providers / vm hypervisors. The nifty thing about this is I was able to retrieve the list of software installed locally on a system, and do a restore on the program files which those are based off of. Expanding upon this, I should be able to combine this w/ registry snapshots / restorations (this is well documented) and use native automated service installation mechanisms (see relevant articles about doing this with postgres [2], and msiexec [3]) to enable full system backups and recovery using the same tooling for windows as with linux In addition to all of this, I've submitted Snap to Fedora [4] and Ubuntu [5], any package reviews would be more than appreciated. In any case, stay tuned for more updates! -Mo [1] https://github.com/movitto/snap [2] http://pginstaller.projects.postgresql.org/silent.html [3] http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en… [4] https://bugzilla.redhat.com/show_bug.cgi?id=755890 [5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649585

1 0

OpenStack status
by Mark McLoughlin 22 Nov '11

22 Nov '11

Hey, Happenings in OpenStack/Fedora/EPEL this week: * Pádraig Brady has continued his efforts to get OpenStack working in EPEL. The wiki page has all the details: https://fedoraproject.org/wiki/OpenStack#OpenStack_in_EPEL After some discussion on the list, and some experimentation by Pádraig to make Nova work with older versions, it was decided to package newer versions of webob and sqlalchemy using this approach: https://fedoraproject.org/wiki/Packaging:Python_Eggs#Multiple_Versions Pádraig, Toshio and Steve Traylen proceeded to kick ass by fixing an issue in python-migrate: https://bugzilla.redhat.com/748784 missing python-tempita Requires: in python-migrate and packaging python-webob1.0, python-sqlalchemy0.7 and python-nose1.1: https://bugzilla.redhat.com/754848 Review Request: python-webob1.0 - WSGI request and response object https://bugzilla.redhat.com/755065 Review Request: python-sqlalchemy0.7 - compat package epel 6 https://bugzilla.redhat.com/755139 Review Request: python-nose1.1 - Discovery-based unittest extension for Python * Bob Kukura did an excellent job of packaging Quantum: https://bugzilla.redhat.com/755033 Review Request: openstack-quantum - Virtual network service for OpenStack * David Nalley has pushed openstack-swift-1.4.3 into rawhide: http://pkgs.fedoraproject.org/gitweb/?p=openstack-swift.git;a=commitdiff;h=… and Pete Zaitcev has been testing it: http://lists.fedoraproject.org/pipermail/cloud/2011-November/thread.html#982 Alan Pevec has also been attempting to commit permissions to update openstack-swift in F-16/EPEL6 and fix some of the packaging issues in bugzilla. * Alan has also been preparing to update keystone to 2011.3.1 when it is released upstream soon. This has a bunch of fixes and should work a lot better with Nova, Glance, Swift, etc. http://pkgs.fedoraproject.org/gitweb/?p=openstack-keystone.git;a=commitdiff… * Cole Robinson has been making good progress getting Dashboard/Horizon running and is starting to work on packaging it. * Russell Bryant has started investigating switching Nova to use MySQL by default: http://lists.fedoraproject.org/pipermail/cloud/2011-November/000996.html * Alan Pevec has start looking into getting Nova's VNC console support working: https://bugzilla.redhat.com/734348 Figure out what to do about ajaxterm * There's been a bunch more progress on the Nova stable branch with ~20 patches pushed in the last week. The stable branch for Glance has also opened this week with ~15 patches backported from master. All of these will be pulled into Fedora soon. * Boris Filippov from Grid Dynamics has been sponsored and intends helping out with OpenStack on Fedora/EPEL: https://admin.fedoraproject.org/accounts/user/view/bfilippov * On a slightly random note, eatmydata is apparently useful for speeding up the running of Nova's unit tests, but it's not in Fedora yet. If anyone wanted to pick up the abandoned package review, that would be cool: https://bugzilla.redhat.com/592500 Review Request: libeatmydata - Disable fsync() and friends Cheers, Mark.

1 0

Couple notes to get Aeolus to work in F16
by Steven Dake 21 Nov '11

21 Nov '11

Hi, I recently installed aeolus-all after reinstalling my laptop to F16. Here are a couple points that you should keep in mind when installing if you want the software to work: 1. deltacloud-core-0.4.1-6.fc16.noarch is DOA The Aeolus software will not work with this version of deltacloud-core. Michal Fojtik has done an update to this package to fix the init script problems and I have acked it in Bohdi. It may take a few days before it hits the official release repositories. In the meantime, you can download the rpms from here: http://koji.fedoraproject.org/koji/buildinfo?buildID=274611 2. when running aeolus-configure, do not forget the -p ec2 command line option. If you do, Amazon will return invalid credentials and deltacloud does some wierdness by reading your local webserver (instead of Amazons). If you have already run aeolus-configure without -p and find this email via a search engine, aeolus-cleanup will reset the aeolus config and you can start fresh with the proper commands. Regards -steve

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud November 2011