Re: [Openstack] Packaging changes based on discussions at ODS
Monty Taylor wrote: Totally in terms of the decisions and re-visiting it. I think you're totally right, of course, in terms of that. Your initial email used terms like we are going to, we will or I'll follow up with implementation details as they happen which certainly sounds like it's an already-made decision. I'm a bit surprised that you come up with these conclusions based on last week's discussions, and that the existing release team (which is ultimately responsible for those release deliverables) wasn't asked for comments before coming up with such a strong direction. Here's the problem in a nutshell... I can continue to cut packages ... but we don't have anybody dedicated to maintaining the contents of the packages that we create post-release. (we only just now even got branches for maintenance of the branches post-release, and those are really mainly a place for the distros to coordinate) I think you are conflating two problems, and decide to throw out the baby with the bath water. One issue is the release packages, the other is the release cycle PPAs. We don't really want to do post-release maintenance on packages in the release PPAs, and therefore they are not really usable long-term as a production install option. One option is definitely to stop producing them. I just don't see how you jump from that to let's stop producing any packages. We have been producing packages in PPAs for trunk, milestone-proposed and last-milestone, and those packages are useful. They are used daily by testers, developers and integrators. They are by no means an end product, but they have their own value. Replacing *all of them* by a single trunk pip repository is just wrong. Where will we call for testing on milestone-proposed ? Where will integrators be able to easily get the last milestone ? Those packages *are* used. PPA stats show more than 33k uses for nova-core/trunk, 350 uses of milestone-proposed and 480 uses of the milestone PPA. In summary, I agree we should now question the release PPAs. I don't see why we should remove all the other ones in the process. And I disagree with your presentation of the general consensus and your already-decided plan. -- 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] Reminder: OpenStack team meeting - 21:00 UTC
Hello everyone, Our general meeting will take place at 21:00 UTC this Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it, please name a substitute on [2]. With essex-1 being 3 weeks away, we will discuss plans and features for every core project. Check out how that meeting time translates for *your* timezone: [1] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20111018T21 See the meeting agenda, edit the wiki to add new topics for discussion: [2] http://wiki.openstack.org/Meetings/TeamMeeting Cheers, -- 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] error when glance command
I use apt-get install nova, glance use git to install keystone now I use glance via keystone, for example upload image or delete image error show: Failed to show details. Got error: Internal Server error: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 336, in handle_one_response result = self.application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 113, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1053, in get_response application, catch_exc_info=False) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1022, in call_application app_iter = application(self.environ, start_response) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 186, in __call__ return self._forward_request(env, start_response, proxy_headers) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 312, in _forward_request return self.app(env, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 113, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1053, in get_response application, catch_exc_info=False) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1022, in call_application app_iter = application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 159, in __call__ return resp(environ, start_response) File /usr/lib/pymodules/python2.7/routes/middleware.py, line 131, in __call__ response = self.app(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 159, in __call__ return resp(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 311, in __call__ request, **action_args) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 328, in dispatch return method(*args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/api/v1/images.py, line 147, in detail **params) File /usr/lib/python2.7/dist-packages/glance/registry/__init__.py, line 42, in get_images_detail return c.get_images_detailed(**kwargs) File /usr/lib/python2.7/dist-packages/glance/registry/client.py, line 62, in get_images_detailed res = self.do_request(GET, /images/detail, params=params) File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 140, in do_request method, action, body=body, headers=headers, params=params) File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 232, in _do_request raise Exception(Internal Server error: %s % res.read()) Exception: Internal Server error: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 336, in handle_one_response result = self.application(self.environ, start_response) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 186, in __call__ return self._forward_request(env, start_response, proxy_headers) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 312, in _forward_request return self.app(env, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 113, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1053, in get_response application, catch_exc_info=False) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1022, in call_application app_iter = application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 159, in __call__ return resp(environ, start_response) File /usr/lib/pymodules/python2.7/routes/middleware.py, line 131, in __call__ response = self.app(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 159, in __call__ return resp(environ,
Re: [Openstack] Announcing Nova subteams
Vishvananda Ishaya wrote: I've been assimilating the plans from the design summit into blueprints. In the process i've noticed that we have a lot planned for the next few months. Some of these changes are quite large and involve people from many different companies that are working on openstack. In order to facilitate feature work over the next few months, I've decided to create a number of subteams. [...] I turned that list into a wikipage (easier to maintain than an email thread) at: http://wiki.openstack.org/Teams Please edit it directly when you have updates. It's not Nova-specific, so please add any team or workgroup that you want. *Nova Security Improvements Team* Planning for security improvements to nova. Due to the large number of code changes being worked on in essex, we aren't planning on locking things down completely in the next six months. This will likely be mostly planning in the essex time frame, with actual implementations to hit in F. https://launchpad.net/~nova-security-improvements Security lead - rjh We (the security-minded dudes) might refactor that one a bit to be a more horizontal OpenStack Security audit and improvements team. More on this this week (promised!) -- 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] error when glance command
Hi! In the future, please use Launchpad's bug reporting area to report bugs :) https://bugs.launchpad.net/glance/+filebug It looks like from below, you have not set up your glance-registry.conf correctly. Please see here for information on setting up Glance servers with Keystone support: http://glance.openstack.org/authentication.html#configuring-glance-registry-to-use-keystone Cheers! -jay 2011/10/18 DeadSun mwjpi...@gmail.com: I use apt-get install nova, glance use git to install keystone now I use glance via keystone, for example upload image or delete image error show: Failed to show details. Got error: Internal Server error: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 336, in handle_one_response result = self.application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 113, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1053, in get_response application, catch_exc_info=False) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1022, in call_application app_iter = application(self.environ, start_response) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 186, in __call__ return self._forward_request(env, start_response, proxy_headers) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 312, in _forward_request return self.app(env, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 113, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1053, in get_response application, catch_exc_info=False) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1022, in call_application app_iter = application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 159, in __call__ return resp(environ, start_response) File /usr/lib/pymodules/python2.7/routes/middleware.py, line 131, in __call__ response = self.app(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 159, in __call__ return resp(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 311, in __call__ request, **action_args) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 328, in dispatch return method(*args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/api/v1/images.py, line 147, in detail **params) File /usr/lib/python2.7/dist-packages/glance/registry/__init__.py, line 42, in get_images_detail return c.get_images_detailed(**kwargs) File /usr/lib/python2.7/dist-packages/glance/registry/client.py, line 62, in get_images_detailed res = self.do_request(GET, /images/detail, params=params) File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 140, in do_request method, action, body=body, headers=headers, params=params) File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 232, in _do_request raise Exception(Internal Server error: %s % res.read()) Exception: Internal Server error: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 336, in handle_one_response result = self.application(self.environ, start_response) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 186, in __call__ return self._forward_request(env, start_response, proxy_headers) File /usr/local/lib/python2.7/dist-packages/keystone-1.0-py2.7.egg/keystone/middleware/auth_token.py, line 312, in _forward_request return self.app(env, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 208, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 113, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py,
Re: [Openstack] Announcing Nova subteams
Hi all - Working groups are a great idea and I would love to add one for documentation. Specifically for nova, I think it would be best if we identify folks like you (Razique) or Kevin Bringard to head up the nova working group since my attention needs to remain one level up. If you're willing, I am happy to help. Also, if other projects want a docs working group, please raise your hand and update the wiki page. I'm also especially interested in the API working group as well since there is doc work needed there, but I'd like to ensure my coverage is fair for all projects as coordinator. Thanks, Anne *Anne Gentle* a...@openstack.org my blog http://justwriteclick.com/ | my bookhttp://xmlpress.net/publications/conversation-community/| LinkedIn http://www.linkedin.com/in/annegentle | Delicioushttp://del.icio.us/annegentle| Twitter http://twitter.com/annegentle On Mon, Oct 17, 2011 at 2:23 AM, Razique Mahroua razique.mahr...@gmail.comwrote: Hi All, I thnik it's a great starting point. What about a Nova Documentation Team also ? Since more and more content seems to come, and as Anne pointed, more new contributors. Best regards, Razique Le 17 oct. 2011 à 07:56, Vishvananda Ishaya a écrit : Hello Everyone, I've been assimilating the plans from the design summit into blueprints. In the process i've noticed that we have a lot planned for the next few months. Some of these changes are quite large and involve people from many different companies that are working on openstack. In order to facilitate feature work over the next few months, I've decided to create a number of subteams. There is too much work going on in nova to manage everything in one large group, so for sanity's sake, I'm attempting to break the work up into manageable chunks. The subteam idea is experimental. We will try it for the first two milestones and re-evaluate after e2 whether we need to make some further changes. My vision is that each subteam is an open group where interested parties can communicate and plan features. Some of the teams will initially be more research oriented, but ultimately these teams will be focused on implementation. Each team will have a 'lead' which will function as a point of contact for the nova PTL. I'm currently on all of the teams, and I will do my best to keep track of work going on in all parts, but I may need to depend on the lead for help with scheduling and planning. A rough outline of the teams responsibilities are: * Planning new features related to the specific area of focus * Congealing plans into specific blueprints * Targeting blueprints to milestones * Assigning blueprints to specific individuals or groups * Triaging bugs related to the specific area of focus * Reviewing any code submissions related to the specific area of focus I want to keep these teams very lightweight; we don't need more unnecessary process and overhead. I've created launchpad teams for all of the major areas, and each of these teams has a mailing list. I'm not sure that communication over these mailing lists is the best option, but we need a way to get things started. The launchpad teams are all open, so if any of the areas interest you, please join the team and subscribe to the mailing list. I'm going to start by assigning all related blueprints to each team. The teams will then re-assign blueprints to individuals as needed. I will work with all of the teams to target these blueprints to specific milestones. Any blueprints that don't fit under a particular team I will manage separately. I'm also going to attempt to do the same with bugs as they come in. Help triaging bugs is of course always appreciated. Here is a list of teams, including a link to the launchpad page and a short description: *Nova API Team* https://launchpad.net/~nova-api All things api related, with special focus on additional features and cleanup of the openstack api. lead - bcwaldon *Nova Database Team* https://launchpad.net/~nova-database Cleanup of the db layer, DB testing, alternative backends lead - _0x44 (unconfirmed) *Nova Scaling Team* https://launchpad.net/~nova-scaling Distributed zones, aggregation, geographically diverse zones. lead - comstud *Nova Orchestration Team* https://launchpad.net/~nova-orchestration Orchestration, workflow management for requests, state machine for recovery lead - sandywalsh *Nova Upgrades Team* https://launchpad.net/~nova-upgrades Seamless upgrades for nova. Some research and planning still needs to be done here. lead -rjh *Nova Feature Parity Team* Full feature parity for xenapi and libvirt/kvm. Includes user facing parity issues like common images. https://launchpad.net/~nova-feature-parity lead - sleepsonthefloor *Openstack Volumes Team* https://launchpad.net/~openstack-volume Volumes api, drivers, scheduling, zone support. lead - renuka *Nova Auth Team* https://launchpad.net/~nova-auth Code for
[Openstack] Release team
Hi everyone, It is team creation season, so let's just create another one. There is no reason why the release management job should be a one-person thing. If you're interested in ensuring the global delivery of a common OpenStack release (with core projects that work well together) every 6 months, feel free to apply for the openstack-release team: https://launchpad.net/~openstack-release Duties include: being a pain to project PTLs and people coding features so that they announce their plans and keep their status up to date, running a weekly meeting to ensure synchronization between core projects and get status updates, apply release process for every milestone and every release, educate core and incubated projects on release-oriented best practices, anticipate issues that would prevent the successful delivery of the common OpenStack releases. The team is currently composed of two active members: Soren Hansen and myself. The PTLs used to be automatically part of the team for launchpad branch management reasons, but that is no longer the case (feel free to reapply though, if you enjoy enough free time :)) Cheers, -- Thierry Carrez (ttx) ___ 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] Solved ( was Re: Object PUT failed)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am using ext4 instead of xfs. After remounting with extended user attributes, I was able to upload my files. # mount -o remount,user_xattr -t ext4 /dev/sda3 /srv/node/sda3 # swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload myfiles small.txt small.txt # swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass stat Account: AUTH_system Containers: 2 Objects: 1 Bytes: 104857600 Accept-Ranges: bytes # swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass stat myfiles Account: AUTH_system Container: myfiles Objects: 1 Bytes: 104857600 Read ACL: Write ACL: Sync To: Sync Key: Accept-Ranges: bytes Here's the relevant log: Oct 18 10:48:16 b002 proxy-server ERROR 500 Traceback (most recent call last):#012 File /usr/lib/python2.6/site-packages/swift/obj/server.py, line 715, in __call__#012res = getattr(self, req.method)(req)#012 File /usr/lib/python2.6/site-packages/swift/obj/server.py, line 520, in PUT#012file.put(fd, tmppath, metadata)#012 File /usr/lib64/python2.6/contextlib.py, line 34, in __exit__#012 self.gen.throw(type, value, traceback)#012 File /usr/lib/python2.6/site-packages/swift/obj/server.py, line 251, in mkstemp#012yield fd, tmppath#012 File /usr/lib/python2.6/site-packages/swift/obj/server.py, line 520, in PUT#012file.put(fd, tmppath, metadata)#012 File /usr/lib/python2.6/site-packages/swift/obj/server.py, line 275, in put#012write_metadata(fd, metadata)#012 File /usr/lib/python2.6/site-packages/swift/obj/server.py, line 89, in write_metadata#012setxattr(fd, '%s%s' % (METADATA_KEY, key or ''), metastr[:254])#012 File /usr/lib64/python2.6/site-packages/xattr/__init__.py, line 200, in setxattr#012return xattr(f).set(attr, value, options=options)#012 File From Object Server re: /v1/AUTH_system/builders/etc/swift/object.builder xxx.xx.xxx.xx:6000 (client_ip: xxx.xx.xxx.xx) - --sharif On 10/17/2011 04:24 PM, Sharif Islam wrote: I just finished setting up the swift nodes. I tried the following command from the proxy nodes: # swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass stat Account: AUTH_system Containers: 1 Objects: 0 Bytes: 0 Accept-Ranges: bytes but this failed: # swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload myfiles test.txt I got: Object PUT failed: https://172.29.202.12:8080/v1/AUTH_system/myfiles/test.txt 503 Internal Server Error tail -n100 /var/log/messages here: http://paste.openstack.org/show/2745/ And these are services running in that proxy node: http://paste.openstack.org/show/2746/ Any idea what could be wrong? --sharif -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOnZWaAAoJEACffes9SivFz9gIAInQotE1pJkaIIsKbtDpzcEe TjOm1tGEyQMMKQi4FATnRWZMUB7levpoLCbb8KCCkL1RRlp+IGSUcPBeK86inf7+ 4n2hWCzt7JJFZOpNOaKmB6kJ0be+Yh7D4cY2E1gpSQCLeAenkqQvAfost/MGHRMh o0tGv27sDS4Wz+tG4pg//AA8EXHfDwo2IilLRpZZ5ftOGdJTDiYlKVNq3Kjkm5YW 6H4n94V8ACZEp2MqBCvgzn1MNxxtaanIcgzplybqPIIjB5kwtZxN2WPwaL3IAZEt Ku6xgbLB4ceuEP8Jr9MSSPfJSfrGC71m3IMlS3FgqyEQRihGOLh0DnPguqBQOMI= =tERz -END PGP SIGNATURE- ___ 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] Swift test plan test cases , need recommends
Hello folks , We r hard working on Swift development and test now . And there's only a NOVA QA team , I'm wondering to know that if there has any test plan around SWIFT . Also , you can share you using case and issues . We'll have a test on various swift deploying archi. The most valuable recommends are problems. Problems and questions will make this project stronger / valuable / useful etc.. Anything would be nice , I'll give u an result of each recommends. Feel free to drop any suggestions ...I'll appreciate Cloudena Swift team @ Taiwan -- +Hugo Kuo+ tonyt...@gmail.com hugo@cloudena.com +886-935-004-793 www.cloudena.com ___ 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] User separation in nova (w/o keystone)
Does nova (without keystone) provide any isolation across users' instances? In our deployment (which is based on code merged from trunk from about two weeks ago), we've found that one user can see another user's instances, terminate another user's instances, etc. Keypairs do seem to be isolated, though. On the other hand, I tried out devstack, which uses keystone and the demo user wasn't able to see instances launched by the admin user. Is this isolation a feature of keystone, or is this some issue in our setup (e.g., set up users incorrectly, wrong flag somewhere). Here's what we saw when testing this out: Root: # nova-manage user create test_user1 # nova-manage project create test_user1 admin # nova-manage project add test_user1 test_user1 # nova-manage project environment test_user1 test_user1 novarc-user1 # nova-manage user create test_user2 # nova-manage project create test_user2 admin # nova-manage project add test_user2 test_user2 # nova-manage project environment test_user2 test_user2 novarc-user2 test_user1: test_user1@cluster ~ $ source novarc-user1 test_user1@cluster ~ $ euca-describe-keypairs KEYPAIR user1 d0:56:69:08:9b:60:e3:82:b2:7d:ee:e6:57:84:dd:65 test_user1@cluster ~ $ euca-run-instances -t m1.tiny -k user1 ami-000b RESERVATION r-4a722y62 test_user1 default INSTANCEi-0009 ami-000bpending user1 (test_user1, gpu1)1 m1.tiny 2011-10-18T15:09:54Znova ami-ami- test_user1@cluster ~ $ euca-describe-instances RESERVATION r-4a722y62 test_user1 default INSTANCEi-0009 ami-000b10.99.1.3 10.99.1.3 pending user1 (test_user1, gpu1)1 m1.tiny 2011-10-18T15:09:54Znovaami-ami- test_user2: test_user2@cluster ~ $ source novarc-user2 test_user2@cluster ~ $ euca-describe-keypairs test_user2@cluster ~ $ euca-describe-instances RESERVATION r-4a722y62 test_user1 default INSTANCEi-0009 ami-000b10.99.1.3 10.99.1.3 running user1 (test_user1, gpu1)1 m1.tiny 2011-10-18T15:09:54Znovaami-ami- Lorin -- Lorin Hochstein, Computer Scientist USC Information Sciences Institute 703.812.3710 http://www.east.isi.edu/~lorin ___ 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] [RFC] Stable branch
Hey, On Mon, 2011-10-17 at 14:22 -0700, Vishvananda Ishaya wrote: Lets get this going asap. We don't really have a place to point people who are deploying diablo and running into bugs. I've pushed the first small batch of commits: https://review.openstack.org/#q,status:open+project:openstack/nova+branch:stable/diablo,n,z Feel free to +1 :) Cheers, Mark. ___ 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] Metrics around code
Hello folks, I made more progress using CVSanaly to dig into our git repositories, build a database from the git logs and extract information from it. CVSanaly is a tool developed under a EU sponsored project (FLOSSmetrics) and currently maintained by a few universities. More about it on https://projects.libresoft.es/projects/cvsanaly/wiki For the curious among us, I documented the steps to populate the CVSanaly database with data from OpenStack git repos on a new wiki page: http://wiki.openstack.org/CommunityMetrics/Code You'll find there also the implementation details to answer the question: Who commited to an OpenStack repo, how many times in the past 30 days? and a demo report built with Pentaho Reporting representing the total number commits per repository in past 30 days http://wiki.openstack.org/CommunityMetrics/Code?action=AttachFiledo=gettarget=2011-11-commits30daysallrepo-obfuscated.pdf [note: the email addresses are hidden on purpose] First of all: do the numbers seem correct to you? In other words, does the SQL query seem correct? Does the demo report look interesting to you? What/how would you change? Then, I would like your feedback to refine the other questions we want to see answered regularly, regarding code (we'll move on to bugs, docs, etc later). Are the following reports interesting? Do we want to have them run monthly or weekly? Is this too much information or too little? What else would you like to see regarding code? * Total number of commits across all repos aggregated per month * Total number of commits per repository aggregated per month * Total number of commits per author per repository * Total number of commits per author per repository in past 30 days * Average number of Lines of Code changed per commit per repository * Average number of Lines of Code changed per commit per repository per author Also, from the list of repositories on https://github.com/openstack/, which ones should I keep tracking? cheers, 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] OpenStack Dashboard Update
Hello all, Milestones and feature roadmaps are now available at: https://blueprints.launchpad.net/openstack-dashboard Also we have chosen the official project codename, Horizon. We will be moving the official repo to the OpenStack GitHub account. In the interim, we have renamed the currently official repo. This is temporary while we make the transition. https://github.com/4P/horizon In the next few days we will be migrating to the Gerrit workflow as well. More updates soon as we make this migration. Thanks, Devin ___ 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] Openatack vector logo
I am looking of openstack vector logo. Anyone can help? We will launch openstack community indonesian chapter ___ 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] Can anyone install dashboard on windows?
Hi,everyone, I had install the dashboard of the catus version on windows,very easy for debug.when I install the dashboard of The diablo version,there are some problems: I can't install glance client on windows,because xattr can't install on windows,so I commentted the code in relation to glance in the dashboard,others in the dashboard are ok in windows except image list. 此致 敬礼 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
