Re: [Openstack] Improving meetbot reports
Stefano Maffulli wrote: One thing that seems clear is that the #info tag is not always used by the moderator, resulting in summaries that are way too dry to be meaningful. Some of the summaries have only a list of topic. Note that anyone can use #info, #action, #idea, #help and #link. I should definitely use them more, but it always feels funny when I'm the only one to use them. See http://wiki.debian.org/MeetBot On the other thand when #info is used more often, summaries seem to be much more intelligible. Do you think that adding a brief #info summary before changing topic would be a good habit? I think it's more efficient to just have everyone use the above commands more often. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] tenants or project
HI: when use dashboard man ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] tenants and project
Hi: There is something confuse. Original，manage resource with project,i can limit an project's resouce. now ,i use dashboard,there is no project,but have a tenant In nova database,the user and project table is blank when i create a user with 'nova-manage user admin test',dashboard can't identification it and the tenant's resouces limit is still use quotas tables which is in nova databases. what i want to know is why use tenant instead of project? is there some thing is superfluous, such as nova's user and project ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Does work glance-manage?
I am trying to glance-manage db_sync # glance-manage db_sync Traceback (most recent call last): File /usr/bin/glance-manage, line 144, in module main() File /usr/bin/glance-manage, line 140, in main dispatch_cmd(options, args) File /usr/bin/glance-manage, line 112, in dispatch_cmd cmd_func(options, args) File /usr/bin/glance-manage, line 100, in do_db_sync glance.registry.db.migration.db_sync(options, version=db_version) File /usr/lib/python2.7/site-packages/glance/registry/db/migration.py, line 119, in db_sync _version_control(options) File /usr/lib/python2.7/site-packages/glance/registry/db/migration.py, line 108, in _version_control return versioning_api.version_control(sql_connection, repo_path) File string, line 2, in version_control File /usr/lib/python2.7/site-packages/migrate/versioning/util/__init__.py, line 160, in with_engine return f(*a, **kw) File /usr/lib/python2.7/site-packages/migrate/versioning/api.py, line 248, in version_control ControlledSchema.create(engine, repository, version) File /usr/lib/python2.7/site-packages/migrate/versioning/schema.py, line 130, in create table = cls._create_table_version(engine, repository, version) File /usr/lib/python2.7/site-packages/migrate/versioning/schema.py, line 171, in _create_table_version if not table.exists(): File /usr/lib64/python2.7/site-packages/sqlalchemy/schema.py, line 466, in exists self.name, schema=self.schema) File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 1765, in run_callable conn = self.contextual_connect() File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py, line 1829, in contextual_connect self.pool.connect(), File /usr/lib64/python2.7/site-packages/sqlalchemy/pool.py, line 191, in connect agent = _ConnectionFairy(self) File /usr/lib64/python2.7/site-packages/sqlalchemy/pool.py, line 369, in __init__ rec = self._connection_record = pool.get() File /usr/lib64/python2.7/site-packages/sqlalchemy/pool.py, line 213, in get return self.do_get() File /usr/lib64/python2.7/site-packages/sqlalchemy/pool.py, line 600, in do_get c = self.create_connection() File /usr/lib64/python2.7/site-packages/sqlalchemy/pool.py, line 147, in create_connection return _ConnectionRecord(self) File /usr/lib64/python2.7/site-packages/sqlalchemy/pool.py, line 253, in __init__ self.connection = self.__connect() File /usr/lib64/python2.7/site-packages/sqlalchemy/pool.py, line 319, in __connect connection = self.__pool._creator() File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/strategies.py, line 82, in connect return dialect.connect(*cargs, **cparams) File /usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py, line 249, in connect return self.dbapi.connect(*cargs, **cparams) sqlalchemy.exc.OperationalError: (OperationalError) unable to open database file None None Try to # glance-manage db_version ERROR: database 'sqlite:///var/lib/glance/glance.sqlite' is not under migration control but in glance-registry.conf: sql_connection = sqlite:var/lib/glance/glance.sqlite When I try to add new image all works fine. I use diablo release packages from http://koji.fedoraproject.org/koji/buildinfo?buildID=265640 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] tenants and project
Alle venerdì 30 settembre 2011, l jv ha scritto: Hi: There is something confuse. Original，manage resource with project,i can limit an project's resouce. now ,i use dashboard,there is no project,but have a tenant In nova database,the user and project table is blank when i create a user with 'nova-manage user admin test',dashboard can't identification it and the tenant's resouces limit is still use quotas tables which is in nova databases. what i want to know is why use tenant instead of project? is there some thing is superfluous, such as nova's user and projects. so... you have a working version of the stack nova/keystone/dashboard, isn't it? Can you post revision number ( or branches used ) to have a working system ? :) thanks a lot! Carlo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] tenants and project
From: Jesse Andrews anotherje...@gmail.com Date: 2011/9/28 Subject: Re: [Openstack] dashaboard+keystone+nova+ glance work well？ To: shake chen shake.c...@gmail.com Cc: openstack@lists.launchpad.net at various points in time they have worked together. We (cloudbuilders) keep a list of repositories that work well together. # compute service NOVA_REPO=https://github.com/openstack/nova.git NOVA_BRANCH=2011.3 # image catalog service GLANCE_REPO=https://github.com/cloudbuilders/glance.git GLANCE_BRANCH=diablo # unified auth system (manages accounts/tokens) KEYSTONE_REPO=https://github.com/cloudbuilders/keystone.git KEYSTONE_BRANCH=diablo # a websockets/html5 or flash powered VNC console for vm instances NOVNC_REPO=https://github.com/cloudbuilders/noVNC.git NOVNC_BRANCH=master # django powered web control panel for openstack DASH_REPO=https://github.com/cloudbuilders/openstack-dashboard.git DASH_BRANCH=master # python client library to nova that dashboard (and others) use NOVACLIENT_REPO=https://github.com/cloudbuilders/python-novaclient.git NOVACLIENT_BRANCH=master # openstackx is a collection of extensions to openstack.compute nova # that is *deprecated*. The code is being moved into python-novaclient nova. OPENSTACKX_REPO=https://github.com/cloudbuilders/openstackx.git OPENSTACKX_BRANCH=diablo 2011/9/30 Carlo Impagliazzo truij...@crs4.it Alle venerdì 30 settembre 2011, l jv ha scritto: Hi: There is something confuse. Original，manage resource with project,i can limit an project's resouce. now ,i use dashboard,there is no project,but have a tenant In nova database,the user and project table is blank when i create a user with 'nova-manage user admin test',dashboard can't identification it and the tenant's resouces limit is still use quotas tables which is in nova databases. what i want to know is why use tenant instead of project? is there some thing is superfluous, such as nova's user and projects. so... you have a working version of the stack nova/keystone/dashboard, isn't it? Can you post revision number ( or branches used ) to have a working system ? :) thanks a lot! Carlo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [libvirt] [RFC PATCH] lxc: don't return error on GetInfo when cgroups not yet set up
Quoting Serge E. Hallyn (serge.hal...@canonical.com): Quoting Daniel P. Berrange (berra...@redhat.com): On Wed, Sep 28, 2011 at 02:14:52PM -0500, Serge E. Hallyn wrote: Nova (openstack) calls libvirt to create a container, then periodically checks using GetInfo to see whether the container is up. If it does this too quickly, then libvirt returns an error, which in libvirt.py causes an exception to be raised, the same type as if the container was bad. lxcDomainGetInfo(), holds a mutex on 'dom' for the duration of its execution. It checks for virDomainObjIsActive() before trying to use the cgroups. Yes, it does, but lxcDomainStart(), holds the mutex on 'dom' for the duration of its execution, and does not return until the container is running and cgroups are present. No. It calls the lxc_controller with --background. The controller main task in turn exits before the cgroups have been set up. There is the race. So what is the right fix here? Should the controller write out another file when it is past the part which should be locked, and the driver waits for that file to exist before it drops the driver mutex? If we do that, do we risk having the driver hang when the controller has hung? -serge ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Design Summit schedule
Hello everyone, A first version of the mobile-friendly design summit schedule is now up at: http://essexdesignsummit.sched.org It is still subject to change, and won't be final until Monday morning. Even then, small adjustments may be made, like room changes. Refresh early, refresh often :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Diablo 4 dashboard error missing openstackx extensions in nova.
Alle lunedì 12 settembre 2011, Anthony Young ha scritto: Another thing to check - the os1.1 keystone endpoints have been modified in d4 to include a tenant prefix. If you are upgrading an existing install, you may need to update your keystone service catalog accordingly: keystone-manage $* endpointTemplates add RegionOne nova http://%= api_vip %:8774/v1.1/%tenant_id% http://%= api_vip %:8774/v1.1/%tenant_id% http://%= api_vip %:8774/v1.1/%tenant_id% 1 1 Anthony Is this patch still needed? Since last mail of this thread, this patch doesn't appear in last keystone branches. Thanks! Carlo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] tenants and project
I've tried with following suggested releases but something in keystone ( with nova ) doesn't work properly. I've followed installing steps but in dashboard I've obtained service not found - compute, after I've fixed this ( setting each endpointTemplate global ) I've had something like user not authorized ... looking deeper I saw that users created in keystone didn't have propagated in nova ( this was the behaviour with shim ). just another issue... Using sampledata.py we can see the db filled with odd data, something like 1234 in tenant_id ( 1234 is the tenant name not the ref ). I posted previous mail just to understand which patches are valid in specific release. According to meeting summary, today ( maybe tomorrow for my timezone ) will be released a working version of keystone compliant with diablo, I look forward to this release :) Carlo Alle venerdì 30 settembre 2011, Rafael Durán Castañeda ha scritto: From: Jesse Andrews anotherje...@gmail.com Date: 2011/9/28 Subject: Re: [Openstack] dashaboard+keystone+nova+ glance work well？ To: shake chen shake.c...@gmail.com Cc: openstack@lists.launchpad.net at various points in time they have worked together. We (cloudbuilders) keep a list of repositories that work well together. # compute service NOVA_REPO=https://github.com/openstack/nova.git NOVA_BRANCH=2011.3 # image catalog service GLANCE_REPO=https://github.com/cloudbuilders/glance.git GLANCE_BRANCH=diablo # unified auth system (manages accounts/tokens) KEYSTONE_REPO=https://github.com/cloudbuilders/keystone.git KEYSTONE_BRANCH=diablo # a websockets/html5 or flash powered VNC console for vm instances NOVNC_REPO=https://github.com/cloudbuilders/noVNC.git NOVNC_BRANCH=master # django powered web control panel for openstack DASH_REPO=https://github.com/cloudbuilders/openstack-dashboard.git DASH_BRANCH=master # python client library to nova that dashboard (and others) use NOVACLIENT_REPO=https://github.com/cloudbuilders/python-novaclient.git NOVACLIENT_BRANCH=master # openstackx is a collection of extensions to openstack.compute nova # that is *deprecated*. The code is being moved into python-novaclient nova. OPENSTACKX_REPO=https://github.com/cloudbuilders/openstackx.git OPENSTACKX_BRANCH=diablo 2011/9/30 Carlo Impagliazzo truij...@crs4.it Alle venerdì 30 settembre 2011, l jv ha scritto: Hi: There is something confuse. Original，manage resource with project,i can limit an project's resouce. now ,i use dashboard,there is no project,but have a tenant In nova database,the user and project table is blank when i create a user with 'nova-manage user admin test',dashboard can't identification it and the tenant's resouces limit is still use quotas tables which is in nova databases. what i want to know is why use tenant instead of project? is there some thing is superfluous, such as nova's user and projects. so... you have a working version of the stack nova/keystone/dashboard, isn't it? Can you post revision number ( or branches used ) to have a working system ? :) thanks a lot! Carlo ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [libvirt] [RFC PATCH] lxc: don't return error on GetInfo when cgroups not yet set up
Quoting Daniel P. Berrange (berra...@redhat.com): On Thu, Sep 29, 2011 at 10:12:17PM -0500, Serge E. Hallyn wrote: Quoting Daniel P. Berrange (berra...@redhat.com): On Wed, Sep 28, 2011 at 02:14:52PM -0500, Serge E. Hallyn wrote: Nova (openstack) calls libvirt to create a container, then periodically checks using GetInfo to see whether the container is up. If it does this too quickly, then libvirt returns an error, which in libvirt.py causes an exception to be raised, the same type as if the container was bad. lxcDomainGetInfo(), holds a mutex on 'dom' for the duration of its execution. It checks for virDomainObjIsActive() before trying to use the cgroups. Yes, it does, but lxcDomainStart(), holds the mutex on 'dom' for the duration of its execution, and does not return until the container is running and cgroups are present. No. It calls the lxc_controller with --background. The controller main task in turn exits before the cgroups have been set up. There is the race. The lxcDomainStart() method isn't actually waiting on the child pid directly, so the --background flag ought not to matter. We have a pipe that we pass into the controller, which we wait on for a notification after running the process. The controller does not notify the 'handshake' FD until after cgroups have been setup, unless I'm mis-interpreting our code That's the call to lxcContainerWaitForContinue(), right? If so, that's done by lxcContainerChild(), which is called by the lxc_controller. AFAICS there is nothing in the lxc_driver which will wait on that before dropping the driver-lock mutex. -serge ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Improving meetbot reports
On Fri, 2011-09-30 at 09:56 +0200, Thierry Carrez wrote: I think it's more efficient to just have everyone use the above commands more often. Indeed. I believe that it's everybody responsibility to add relevant information to the discussion. The reason for empowering the participants instead of relying on an external reporter is that nobody is more knowledgeable about the items being discussed than the people debating. If I'm saying something meaningful during the discussion, adding the #info or #idea tag should be my responsibility. I understand that sometime you don't realize what you say is important until later: but repeating the line is easy, with the tag this time. The main role I see for the moderator is to leave enough time for everybody to add #info, #idea, #link ecc before switching topic. I know you already do it: just repeating what I think is a best practice. /stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Community Weekly Review (September 23-30)
OpenStack Community Newsletter – September 30, 2011 “Have you packed yet?” Edition This weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please email stef...@openstack.org. HIGHLIGHTS * Essex Design Summit and Conference is next week! Have you packed everything? * Design Summit preliminary agenda http://essexdesignsummit.sched.org/ * OpenStack Conference preliminary agenda http://openstackconference2011.sched.org/ Assume that the schedules will change. Hint: subscribe to the web calendars to keep up with any last minute changes. EVENTS * OpenStack Conference – October 5-7, Boston, MA * OpenStack Meetup - October 13, New York City - http://www.doodle.com/m9cki3wt3sdqhwk8 * OpenStack Hackaton, Wikimedia Foundation – October 14-16, New Orleans, LA http://www.mediawiki.org/wiki/NOLA_Hackathon DEVELOPER COMMUNITY * Debating about how to improve meetbot summaries; add your suggestions https://lists.launchpad.net/openstack/msg04379.html * Developer Team Meeting Minutes – September 20 * http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-21.03.html GENERAL COMMUNITY * OpenStack Wiki Recent Changes – http://wiki.openstack.org/RecentChanges * Melange API Specifications http://wiki.openstack.org/MelangeAPIBase * Upgrade with minimal downtime http://wiki.openstack.org/upgrade-with-minimal-downtime * Trusted Computing Pools http://wiki.openstack.org/TrustedComputingPools * Quantum Packaging Proposal http://wiki.openstack.org/QuantumPackaging COMMUNITY STATISTICS (9/16-9/23) * OpenStack Compute (NOVA) Impact * https://github.com/openstack/nova/graphs/impact * OpenStack Object Storage (SWIFT) Impact * https://github.com/openstack/swift/graphs/impact * OpenStack Image Registry (GLANCE) Impact * https://github.com/openstack/glance/graphs/impact * OpenStack Website Stats for Week: 23,510 Visits, 59,350 Pageviews, 57.84 % New Visits * Top 5 Pages: Home 40.01%; Compute 16.78%; Projects 14.53%; Storage 10.50%; Glance 5.8% ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [PATCH] don't disconnect a mounted device
I'm sure the patch should be tweaked (helpers moved elsewhere, whatever)
but running euca-terminate-instances twice on an lxc container can cause
oopses on the host without this.
Signed-off-by: Serge Hallyn serge.hal...@canonical.com
--
Index: nova-2011.3/nova/virt/disk.py
===
--- nova-2011.3.orig/nova/virt/disk.py 2011-09-30 16:29:43.806061035 -0500
+++ nova-2011.3/nova/virt/disk.py 2011-09-30 16:29:56.490061147 -0500
@@ -224,9 +224,30 @@
return out.strip()
+def is_mounted(device):
+f=open(/proc/mounts, r)
+for l in f.readlines():
+fields = l.split()
+if fields[0] == device:
+f.close()
+return true
+f.close()
+return false
+
+def is_stuck_mounted(device):
+if is_mounted(device):
+utils.execute('umount', device, run_as_root=True)
+if is_mounted(device):
+return true
+return false
+
+
def _unlink_device(device, nbd):
Unlink image from device using loopback or nbd
if nbd:
+if is_stuck_mounted(device):
+raise exception.Error(_('Could not unmount device %s') % device)
+
utils.execute('qemu-nbd', '-d', device, run_as_root=True)
_free_device(device)
else:
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
