vkmc's profile - activity

2019-05-22 02:46:44 -0600 received badge  Famous Question (source)
2018-02-26 09:02:05 -0600 received badge  Popular Question (source)
2016-07-28 13:01:38 -0600 received badge  Notable Question (source)
2016-07-28 13:01:38 -0600 received badge  Popular Question (source)
2013-10-29 12:27:19 -0600 received badge  Great Answer (source)
2013-10-03 19:04:16 -0600 commented answer Spice Client

Here is the working link :) http://docs.openstack.org/grizzly/openstack-compute/admin/content/remote-console-access.html Great answer fifieldt, just what I was looking for!

2013-06-13 07:48:39 -0600 received badge  Supporter (source)
2013-06-12 22:23:15 -0600 received badge  Editor (source)
2013-06-12 22:22:56 -0600 answered a question Can you install OpenStack on RaspberryPi's?

If it's just for fun... yeah, it's possible. If not, Pi's specs are not enough for a decent OpenStack cloud deployment.

I tried it a few months ago with the most basic deployment over Raspbian.

It would nice to see how it behaves in a cluster though :)

2013-06-11 10:29:16 -0600 received badge  Good Answer (source)
2013-04-09 03:59:37 -0600 received badge  Nice Answer (source)
2013-04-07 13:57:39 -0600 received badge  Teacher (source)
2013-04-05 19:27:03 -0600 answered a question How do I debug OpenStack?

Debugging a piece of code is an activity as important as writing it. The importance of debugging is much more noticeable on large projects like OpenStack, which require both developers and common users contribute and report when something is not going well.

Here are some pointers to collect useful logs and debugging processes.

Logging

Looking through the logs can be tricky... not if you know how to use regular expressions!

The first thing to do when we see a strange behavior that is repeated with the same input data, is to look at logs.

Logs are files, usually plain text and arranged chronologically, that contain information about the code that is executed to perform an action.

Analyzing the information found there, you may be able to detect what the problem is or, at least, where the error occurs.

The location of the logs in the system may vary depending on the implementation, but in GNU/Linux they usually are stored in /var/log.

In OpenStack the location of these logs varies according how have you deployed it: using DevStack or by hand, whether with the distribution repository packages you are using or from source.

If you're using DevStack keep in mind that by default, DevStack doesn’t log. To enable this option you will need to add the following lines to the localrc file.

LOGFILE=$DEST/stack.sh.log

– Name and location of the stack.sh script logs. Without this line the output of this script will appear in the terminal where you run it, without being stored in any location.

SCREEN_LOGDIR=$DEST/logs/screen

– Location of the screen logs. DevStack runs OpenStack services under GNU Screen, thus providing the facility to view its current execution status. The logs simply store the output of these screens..

LOGDAYS=1

– Number of days to be logged. The old logs are replaced with the latest runs.

$DEST is the location in which the logs will be located. You can set this value as you wish.

Screen logs are just a record of the screens initiated by DevStack but you can check them anytime during the execution. The information provided is very useful to debug any OpenStack service.

GNU Screen provides the same functions as the DEC VT100 terminal, plus other aggregates. If you have no experience with this terminal, make sure to write down the following shortcuts.

 Attach to a screen      screen -r stack
 Switch screens          ctrl+a <screen no.>  (e.g. ctrl+a 1) 
 Scroll in a screen      ctrl+a esc and up/down arrows to scroll
 List screens        ctrl+a " and select the screen with up/down arrows
 Next screen         ctrl+a n 
 Detach from the screen  ctrl+a d

Manual deployment

Here you will find most services logs in /var/log/service, where service is the name of the desired service. For example, in /var/log/keystone you will find Keystone logs.

In my experience, the only service that differs from this default location is Horizon. You can find ... (more)

2013-03-11 01:26:03 -0600 answered a question Listing containers per tenant

Thanks Chmouel! It sounds feasible, I will try that approach :)

2013-03-05 07:21:33 -0600 commented answer How do I achieve functionality similar to nova-network's multi_host with Quantum?

I'm sorry, I missed the fact that there is no much information there about multihost support. If I'm not wrong, that feature is under deployment. Here you can see some details about that https://blueprints.launchpad.net/quantum/+spec/quantum-multihost.

2013-03-05 07:09:58 -0600 answered a question How do I achieve functionality similar to nova-network's multi_host with Quantum?

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst (https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStackFolsomInstallGuideWebVersion.rst) - 2.8 is the Quantum section :)

That's the official guide, so I guess is the best source!

Cheers!

2013-03-04 17:29:21 -0600 answered a question ''module' object has no attribute 'quantum'' when trying to login to Dashboard

Bug fixed by commit http://github.com/openstack/horizon/commit/63203ab1069999f81b9518c11da29eb8ca537077 (http://github.com/openstack/horizon/c...)

2013-03-04 14:44:08 -0600 answered a question Listing containers per tenant

#2 provides more information for this question

2013-03-03 20:28:02 -0600 answered a question Listing containers per tenant

Hi Chmouel,

Oh you're right, I missed an important detail. I wanted to list all the containers within a tenant with the admin user. As mentioned, this is to implement the tenant deletion workflow on Horizon :)

Do you know if there is a similar feature I could use to access all the containers within a tenant?

Thanks,

Victoria

2013-03-02 13:39:17 -0600 asked a question Listing containers per tenant

Hi,

I was wondering if listing containers per tenant is an available feature. I checked the client and the current code, and it doesn't look like it.

I know that the --os-tenant-name option is available but is not a viable replacement in the current implementation I'm working on [0] because it only works for projects of which the admin is a member.

In case that this functionality is indeed not available, do you think that filing a blueprint is a good idea?

I'd like to hear your suggestions, thanks a lot!

[0] https://blueprints.launchpad.net/horizon/+spec/tenant-deletion (https://blueprints.launchpad.net/hori...)

2013-02-25 10:42:34 -0600 answered a question 'ERROR: Unable to write privatekey' on current DevStack version

Already fixed indeed! Thanks :)

2013-02-15 10:13:36 -0600 answered a question 'ERROR: Unable to write privatekey' on current DevStack version

Hi Jason! Same behaviour :/ After initial run it produces the same output

2013-02-14 23:06:00 -0600 asked a question ''module' object has no attribute 'quantum'' when trying to login to Dashboard

Hi all,

I just cloned and deployed the last version of DevStack and when trying to login to Dashboard I get the following trace

####

Environment:

Request Method: GET Request URL: http://127.0.0.1/admin/

Django Version: 1.4.3 Python Version: 2.7.3 Installed Applications: ['openstack_dashboard', 'django.contrib.contenttypes', 'django.contrib.auth', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', 'django.contrib.humanize', 'compressor', 'horizon', 'openstack_dashboard.dashboards.project', 'openstack_dashboard.dashboards.admin', 'openstack_dashboard.dashboards.settings', 'openstack_auth'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'horizon.middleware.HorizonMiddleware', 'django.middleware.doc.XViewMiddleware', 'django.middleware.locale.LocaleMiddleware')

Traceback: File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py" in get_response 111. response = callback(request, callback_args, *callback_kwargs) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec 38. return view_func(request, args, *kwargs) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec 86. return view_func(request, args, *kwargs) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec 54. return view_func(request, args, *kwargs) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec 38. return view_func(request, args, *kwargs) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec 86. return view_func(request, args, *kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py" in view 48. return self.dispatch(request, args, *kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py" in dispatch 69. return handler(request, args, *kwargs) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tables/views.py" in get 155. handled = self.construct_tables() File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tables/views.py" in construct_tables 146. handled = self.handle_table(table) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tables/views.py" in handle_table 118. data = self._get_data_dict() File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tables/views.py" in _get_data_dict 182. self._data = {self.table_class._meta.name: self.get_data()} File "/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/overview/views.py" in get_data 38. data = super(GlobalOverview, self).get_data() File "/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/usage/views.py" in get_data 34. self.usage.get_quotas() File "/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py" in get_quotas 115. _("Unable to retrieve quota information.")) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py" in get_quotas 112. self.quotas = quotas.tenant_quota_usages(self.request) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/utils/memoized.py" in __call__ 33. value = self.func(*args) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py" in tenant_quota_usages 88. floating_ips = network.tenant_floating_ip_list(request) File "/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/api/network.py" in tenant_floating_ip_list 140. return NetworkClient(request).floating_ips.list() File "/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/api/network.py" in __init__ 31. self.floating_ips = api.quantum.FloatingIpManager(request)

Exception Type: AttributeError at /admin/ Exception Value: 'module' object has no attribute 'quantum'

####

As you may already guessed, I have setted up Quantum ... (more)

2013-02-14 17:57:31 -0600 asked a question 'ERROR: Unable to write privatekey' on current DevStack version

Hi everybody,

I just cloned and deployed the last version of DevStack and when running stack.sh the following output appears when creating certificates and sourcable rc files per tenant/user - that's it, when create_userrc.sh gets called.

####

2013-02-14 14:34:27 + /home/vkmc/devstack/tools/create_userrc.sh -PA --target-dir /home/vkmc/devstack/accrc 2013-02-14 14:34:31 Wrote x509 root cert to /home/vkmc/devstack/accrc/cacert.pem 2013-02-14 14:34:33 +-----------+----------------------------------+ 2013-02-14 14:34:33 | Property | Value | 2013-02-14 14:34:33 +-----------+----------------------------------+ 2013-02-14 14:34:33 | access | eb04a19837cf4b3fbd4d1d3187d8fe9d | 2013-02-14 14:34:33 | secret | 4c45bd5db55f42fd8db23414bb9e64b2 | 2013-02-14 14:34:33 | tenant_id | 568d27a9dced489aacdd49f088292788 | 2013-02-14 14:34:33 | user_id | 296ac22edb154250a8c25ff953863e10 | 2013-02-14 14:34:33 +-----------+----------------------------------+ 2013-02-14 14:34:58 ERROR: Unable to write privatekey - /home/vkmc/devstack/accrc/admin/admin-pk.pem exists. 2013-02-14 14:35:08 +-----------+----------------------------------+ 2013-02-14 14:35:08 | Property | Value | 2013-02-14 14:35:08 +-----------+----------------------------------+ 2013-02-14 14:35:08 | access | 7f4d46499fe544acb857f4dc430eb906 | 2013-02-14 14:35:08 | secret | 5c0229c133634ed7adb97429e0fe03c9 | 2013-02-14 14:35:08 | tenant_id | abdb53053b3d4ee79bd22a2493d049c1 | 2013-02-14 14:35:08 | user_id | a153019de129451ba4c47e62e8c1bd58 | 2013-02-14 14:35:08 +-----------+----------------------------------+ 2013-02-14 14:35:31 ERROR: Unable to write privatekey - /home/vkmc/devstack/accrc/alt_demo/alt_demo-pk.pem exists. 2013-02-14 14:35:43 +-----------+----------------------------------+ 2013-02-14 14:35:43 | Property | Value | 2013-02-14 14:35:43 +-----------+----------------------------------+ 2013-02-14 14:35:43 | access | 6b74622a39e7482c99d5708dc85e6603 | 2013-02-14 14:35:43 | secret | 95de97b4e37e4bbf884b65b3eb8d3bc2 | 2013-02-14 14:35:43 | tenant_id | 8466f9dc072844199860d3dfe69d3b01 | 2013-02-14 14:35:43 | user_id | 296ac22edb154250a8c25ff953863e10 | 2013-02-14 14:35:43 +-----------+----------------------------------+ 2013-02-14 14:35:45 ERROR: Unable to write privatekey - /home/vkmc/devstack/accrc/demo/admin-pk.pem exists. 2013-02-14 14:36:07 +-----------+----------------------------------+ 2013-02-14 14:36:07 | Property | Value | 2013-02-14 14:36:07 +-----------+----------------------------------+ 2013-02-14 14:36:07 | access | 4be4804a0b584adaa63b66c6dfdb6e14 | 2013-02-14 14:36:07 | secret | cd96ac31b4ff4946937db43a83475ef6 | 2013-02-14 14:36:07 | tenant_id | 8466f9dc072844199860d3dfe69d3b01 | 2013-02-14 14:36:07 | user_id | 0c4308cbeb1c4c859fb0511f33dc28ef | 2013-02-14 14:36:07 +-----------+----------------------------------+ 2013-02-14 14:36:10 ERROR: Unable to write privatekey - /home/vkmc/devstack/accrc/demo/demo-pk.pem exists. 2013-02-14 14:36:15 +-----------+----------------------------------+ 2013-02-14 14:36:15 | Property | Value | 2013-02-14 14:36:15 +-----------+----------------------------------+ 2013-02-14 14:36:15 | access | 1a5a5b53f0304da79828e9823aed9fc1 | 2013-02-14 14:36:15 | secret | c1767fbe28b44b52b238573f2ecbfddc | 2013-02-14 14:36:15 | tenant_id | bd9728034b7b4d688cb51d918e9a501a | 2013-02-14 14:36:15 | user_id | 0c4308cbeb1c4c859fb0511f33dc28ef | 2013-02-14 14:36:15 +-----------+----------------------------------+ 2013-02-14 14:36:19 ERROR: Unable to write privatekey - /home/vkmc/devstack/accrc/invisible_to_admin/demo-pk.pem exists. 2013-02-14 14:36:22 + is_service_enabled g-reg 2013-02-14 14:36:22 + services=g-reg 2013-02-14 14:36:22 + for service in '${services}' 2013-02-14 14:36:22 + [[ ,g-api,g-reg,key,n-api,n-crt,n-obj,n-cpu,n-cond,cinder,c-sch,c-api,c-vol,n-sch,n-novnc,n-xvnc,n-cauth,horizon,rabbit,tempest,mysql,q-svc,q-agt,q-dhcp,q-l3,q-meta,swift, =~ ,g-reg, ]]

####

This situation is noticeable because the scripts pauses waiting for an input (or at least I didn't give it enough time), and when pressing enter it proceeds to next .pem.

A non-elegant solution is removing certificates directory, devstack/accrc, before running stack.sh.

I checked the script but nothing caught my attention.

Does someone have an idea of why is this happening?

Thanks a lot in advance