[Openstack] OpenStack Folsom Deploy Bash Script
Hi I am developing 'OpenStack Folsom Deploy Script', and Today I release to github. If you have some stress with installing openstack folsom, please use this script :D http://jedipunkz.github.com/openstack_folsom_deploy/ Now, I tested 'all in one' on 1 node, and I keep to develop for sepalated compornent mode, and additional compute nodes. If you know how to install additional compute node with Ubuntu Cloud Archive packages, please tell me or give 'pull request' :) best regards from cloudy Tokyo. Tomokazu Hirai @jedipunkz ___ 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] [Openstack :: Folsom] Quantum Network Node setup
On 10/31/2012 01:08 PM, balaji patnala wrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to un derstand what will be the advantages we are thinking of by doing so. TO have multiple l3 agent nodes, we can distribute traffic from VMs among l3 agent nodes. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.com mailto:sorla...@nicira.com wrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 tel:%2B91%209866%20235%20130 ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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
[Openstack] Verification of Keystone Installation fails
Hello, I followed the steps in the OpenStack Install Deploy for Ubuntu manual to install Keystone. However, when I issue the commands in section Verifying the Identity Service Installation ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/verifying-identity-install.html ), I am getting the following error: # keystone --os-username=admin --os-password=admin --os-auth-url=http://10.176.20.158:35357/v2.0 token-get 'Client' object has no attribute 'service_catalog' I don't see any additional info in keystone.log. Can someone please help me. Thank you, Ahmed. ___ 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-dev] Writing Plug-ins to Quantum
Hi Stackers-
I'm testing a dummy plugin which does and RPC based communication with
Quantum.
I have done this following:
[1] I have written dummy agent like DHCP agent - Present in HOST
[2] I have written dummy_rpc_base like the db/dhcp_rpc_base.py - Present in
Controller
[3] I have written an testing method to the db/db_base_plugin_v2.py -
Present in Controller
But when I restart the quantum-server, I get this error:
root@user-P2020Build:/usr/lib/python2.7/dist-packages/quantum/db# python
/usr/bin/quantum-server -- --config-file /etc/quantum/quantum.conf
--log-file /var/log/quantum/server.log --config-file
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
2012-10-31 14:20:30DEBUG [quantum.service]
2012-10-31 14:20:30DEBUG [quantum.service] Configuration options
gathered from config file:
2012-10-31 14:20:30DEBUG [quantum.service]
2012-10-31 14:20:30DEBUG [quantum.service] allow_bulk
True
2012-10-31 14:20:30DEBUG [quantum.service] allow_overlapping_ips
False
2012-10-31 14:20:30DEBUG [quantum.service] api_extensions_path
2012-10-31 14:20:30DEBUG [quantum.service] api_paste_config
/etc/quantum/api-paste.ini
2012-10-31 14:20:30DEBUG [quantum.service] auth_strategy
keystone
2012-10-31 14:20:30DEBUG [quantum.service] base_mac
fa:16:3e:00:00:00
2012-10-31 14:20:30DEBUG [quantum.service] bind_host
0.0.0.0
2012-10-31 14:20:30DEBUG [quantum.service] bind_port
9696
2012-10-31 14:20:30DEBUG [quantum.service] config_dir
None
2012-10-31 14:20:30DEBUG [quantum.service] config_file
['/etc/quantum/quantum.conf']
2012-10-31 14:20:30DEBUG [quantum.service] core_plugin
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
2012-10-31 14:20:30DEBUG [quantum.service] debug
True
2012-10-31 14:20:30DEBUG [quantum.service] dhcp_lease_duration
120
2012-10-31 14:20:30DEBUG [quantum.service] log_config
None
2012-10-31 14:20:30DEBUG [quantum.service] log_date_format
%Y-%m-%d %H:%M:%S
2012-10-31 14:20:30DEBUG [quantum.service] log_dir
None
2012-10-31 14:20:30DEBUG [quantum.service] log_file
None
2012-10-31 14:20:30DEBUG [quantum.service] log_format
%(asctime)s %(levelname)8s [%(name)s] %(message)s
2012-10-31 14:20:30DEBUG [quantum.service] mac_generation_retries
16
2012-10-31 14:20:30DEBUG [quantum.service] max_dns_nameservers
5
2012-10-31 14:20:30DEBUG [quantum.service] max_subnet_host_routes
20
2012-10-31 14:20:30DEBUG [quantum.service] policy_file
policy.json
2012-10-31 14:20:30DEBUG [quantum.service] state_path
.
2012-10-31 14:20:30DEBUG [quantum.service] syslog_log_facility
LOG_USER
2012-10-31 14:20:30DEBUG [quantum.service] use_syslog
False
2012-10-31 14:20:30DEBUG [quantum.service] verbose
True
2012-10-31 14:20:30DEBUG [quantum.service]
2012-10-31 14:20:30 INFO [quantum.common.config] Config paste file:
/etc/quantum/api-paste.ini
2012-10-31 14:20:30DEBUG [quantum.manager] Plugin
location:quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
2012-10-31 14:20:30 INFO [quantum.manager] Loading Plugin:
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
Traceback (most recent call last):
File /usr/bin/quantum-server, line 26, in module
server()
File /usr/lib/python2.7/dist-packages/quantum/server/__init__.py, line
40, in main
quantum_service = service.serve_wsgi(service.QuantumApiService)
File /usr/lib/python2.7/dist-packages/quantum/service.py, line 83, in
serve_wsgi
service.start()
File /usr/lib/python2.7/dist-packages/quantum/service.py, line 42, in
start
self.wsgi_app = _run_wsgi(self.app_name)
File /usr/lib/python2.7/dist-packages/quantum/service.py, line 89, in
_run_wsgi
app = config.load_paste_app(app_name)
File /usr/lib/python2.7/dist-packages/quantum/common/config.py, line
133, in load_paste_app
app = deploy.loadapp(config:%s % config_path, name=app_name)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
247, in loadapp
return loadobj(APP, uri, name=name, **kw)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
272, in loadobj
return context.create()
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
710, in create
return self.object_type.invoke(self)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
144, in invoke
**context.local_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 59, in
fix_call
reraise(*exc_info)
File /usr/lib/python2.7/dist-packages/paste/deploy/compat.py, line 22,
in reraise
exec('raise t, e, tb', dict(t=t, e=e, tb=tb))
File /usr/lib/python2.7/dist-packages/paste/deploy/util.py, line
Re: [Openstack] [openstack-dev] Writing Plug-ins to Quantum
On 10/31/2012 05:00 PM, Trinath Somanchi wrote: Hi Stackers- I'm testing a dummy plugin which does and RPC based communication with Quantum. I have done this following: [1] I have written dummy agent like DHCP agent - Present in HOST [2] I have written dummy_rpc_base like the db/dhcp_rpc_base.py - Present in Controller [3] I have written an testing method to the db/db_base_plugin_v2.py - Present in Controller But when I restart the quantum-server, I get this error: root@user-P2020Build:/usr/lib/python2.7/dist-packages/quantum/db# python /usr/bin/quantum-server -- --config-file /etc/quantum/quantum.conf --log-file /var/log/quantum/server.log --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini 2012-10-31 14:20:30DEBUG [quantum.service] 2012-10-31 14:20:30DEBUG [quantum.service] Configuration options gathered from config file: 2012-10-31 14:20:30DEBUG [quantum.service] 2012-10-31 14:20:30DEBUG [quantum.service] allow_bulk True 2012-10-31 14:20:30DEBUG [quantum.service] allow_overlapping_ips False 2012-10-31 14:20:30DEBUG [quantum.service] api_extensions_path 2012-10-31 14:20:30DEBUG [quantum.service] api_paste_config /etc/quantum/api-paste.ini 2012-10-31 14:20:30DEBUG [quantum.service] auth_strategy keystone 2012-10-31 14:20:30DEBUG [quantum.service] base_mac fa:16:3e:00:00:00 2012-10-31 14:20:30DEBUG [quantum.service] bind_host 0.0.0.0 2012-10-31 14:20:30DEBUG [quantum.service] bind_port 9696 2012-10-31 14:20:30DEBUG [quantum.service] config_dir None 2012-10-31 14:20:30DEBUG [quantum.service] config_file ['/etc/quantum/quantum.conf'] 2012-10-31 14:20:30DEBUG [quantum.service] core_plugin quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 2012-10-31 14:20:30DEBUG [quantum.service] debug True 2012-10-31 14:20:30DEBUG [quantum.service] dhcp_lease_duration 120 2012-10-31 14:20:30DEBUG [quantum.service] log_config None 2012-10-31 14:20:30DEBUG [quantum.service] log_date_format %Y-%m-%d %H:%M:%S 2012-10-31 14:20:30DEBUG [quantum.service] log_dir None 2012-10-31 14:20:30DEBUG [quantum.service] log_file None 2012-10-31 14:20:30DEBUG [quantum.service] log_format %(asctime)s %(levelname)8s [%(name)s] %(message)s 2012-10-31 14:20:30DEBUG [quantum.service] mac_generation_retries 16 2012-10-31 14:20:30DEBUG [quantum.service] max_dns_nameservers 5 2012-10-31 14:20:30DEBUG [quantum.service] max_subnet_host_routes 20 2012-10-31 14:20:30DEBUG [quantum.service] policy_file policy.json 2012-10-31 14:20:30DEBUG [quantum.service] state_path . 2012-10-31 14:20:30DEBUG [quantum.service] syslog_log_facility LOG_USER 2012-10-31 14:20:30DEBUG [quantum.service] use_syslog False 2012-10-31 14:20:30DEBUG [quantum.service] verbose True 2012-10-31 14:20:30DEBUG [quantum.service] 2012-10-31 14:20:30 INFO [quantum.common.config] Config paste file: /etc/quantum/api-paste.ini 2012-10-31 14:20:30DEBUG [quantum.manager] Plugin location:quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 2012-10-31 14:20:30 INFO [quantum.manager] Loading Plugin: quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 Traceback (most recent call last): File /usr/bin/quantum-server, line 26, in module server() File /usr/lib/python2.7/dist-packages/quantum/server/__init__.py, line 40, in main quantum_service = service.serve_wsgi(service.QuantumApiService) File /usr/lib/python2.7/dist-packages/quantum/service.py, line 83, in serve_wsgi service.start() File /usr/lib/python2.7/dist-packages/quantum/service.py, line 42, in start self.wsgi_app = _run_wsgi(self.app_name) File /usr/lib/python2.7/dist-packages/quantum/service.py, line 89, in _run_wsgi app = config.load_paste_app(app_name) File /usr/lib/python2.7/dist-packages/quantum/common/config.py, line 133, in load_paste_app app = deploy.loadapp(config:%s % config_path, name=app_name) File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247, in loadapp return loadobj(APP, uri, name=name, **kw) File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 272, in loadobj return context.create() File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 710, in create return
[Openstack] [ceilometer] meter data volume
Hi Julien, Sorry to bother you. I am still testing ceilometer now. I am confused about the meter volume in the mongodb. Let's talk about cpu usage. After I create and boot a vm named vm_1, meter data record about cpu usage will be inserted into db in cycle(default 10 minutes). For example,the 'counter_volume' of the first record is '5206000',and the second one is '12389000'. 1) '12389000' nanoseconds means '123.89' seconds or two minutes,it seem like to be 1238.9 seconds actually, is there something wrong ? 2) If I never reboot or suspend vm_1, will the 'counter_volume' of cpu usage record increase all the time ? Just like '8 minutes' - '18 minutes' - '28 minutes' ? 3) If I reboot or suspend vm_1, I find that the 'counter_volume' of cpu usage record will count from zero. Just like '8 minutes' - '18 minutes' - '28 minutes' [- '0 minutes'] -'5 minutes' - '15 minutes'. Does it mean that 'counter_volume' just represents how long has vm_1 been booted up ? 4) This one is about Web API. I find that GET /v1/resources/(resource)/meters/(meter)/volume/sum just return the sum value of all the cpu 'counter_volume', like '8 minutes' + '18 minutes'. Is it reduplicate ? 5) If I want to know how long has vm_1's cpu been used yesterday, how can I do ? It seems like that I have too many questions.. Thank you very much ! --- Yawei Wu Dalian Hi-Think Computer Technology,Corp. ___ 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] Fwd: Openstack
On 31 October 2012 00:42, Curtis C. serverasc...@gmail.com wrote:
On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
Hi guys,
Can someone point me in the direction of a guide to get Openstack
working with two nodes, one as controller and the second as a compute
node, please?
I've tried the CSS corp PDF and the hastexo one, but I can't get them
to work. All I get are virts booting straight into error.
I want a controller node to run all keystone, glance and nova db
functions then a compute node to run the virtuals with vlans bridging
using 8021q. I've tried so many permutations and configs. I can't
believe I'm doing something that outrageous, but I've hacked away at
this for hours and hours with no joy.
Is virtualization turned on in the BIOS?
I think nova show ID will show an error message if the instance fails to
Virtualization is enabled. All the instances end up as follows:
+-+--+
| Property |Value |
+-+--+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-SRV-ATTR:host| None |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
| OS-EXT-SRV-ATTR:instance_name | instance-0002|
| OS-EXT-STS:power_state | 0|
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | error|
| accessIPv4 | |
| accessIPv6 | |
| config_drive| |
| created | 2012-10-30T22:23:57Z |
| flavor | m1.small |
| hostId | |
| id | fae6adf8-2314-4096-ab0c-531dce090c34 |
| image | Cirros Test |
| key_name| joe |
| metadata| {} |
| name| test3|
| status | ERROR|
| tenant_id | b38c7e05403542ea91a3cb69e25e63de |
| updated | 2012-10-30T22:23:57Z |
| user_id | b6d25008d81a456888e92dd3ffaf9cc5 |
+-+--+
nova-compute.log contains:
CRITICAL nova [-] Unable to read from monitor: Connection reset by peer
and
libvirtError: Unable to read from monitor: Connection reset by peer
I've made sure the vnc IP addresses are correct in nova.conf
Any pointers?
___
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] Scheduler issues in folsom
On Wed, Oct 31, 2012 at 10:40:57AM +0800, Huang Zhiteng wrote: On Wed, Oct 31, 2012 at 10:07 AM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Oct 30, 2012, at 7:01 PM, Huang Zhiteng winsto...@gmail.com wrote: I'd suggest the same ratio too. But besides memory overcommitment, I suspect this issue is also related to how KVM do memory allocation (it doesn't do actual allocation of the entire memory for guest when booting). I've seen compute node reported more memory than it should have (e.g. 4G node has two 1GB instances running but still report 3GB free memory) because libvirt driver calculates free memory simply based on /proc/meminfo, which doesn't reflect how many memory guests are intended to use. Ah interesting, if this is true then this is a bug we should try to fix. I was under the impression that it allocated all of the memory unless you were using virtio_balloon, but I haven't verified. I'm pretty sure about this. Can anyone from RedHat confirm this is how KVM works? Yes, that is correct. KVM only allocates memory when the guest actually touches each page. For Linux guests this means that when the guest boots up very little memory is actally allocated on the host. For Windows guests you would typically see all memory allocated imediately, since the Windows kernel will memset() the entire of RAM to zero on startup. Also if you are using explicit huge pages for KVM it will allocate all RAM upfront, but this is not the default - we use transparant/automatic huge pages normally which still allocates on demand. Finally if you have passed any PCI devices through to the guest, all guest RAM will be mlock()d on the host so it can't even overcommit to swap. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ 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] Quantum Agent Error - Help!
Hi Stackers-
I have written a fake agent with the study from the dhcp agent.
The rpc agent daemon is running with the below errors.
But I have missed some bits of information with respect to the rpc
communication.
In the log, I have the following errors.
2012-10-31 16:14:38 INFO [quantum.agent.fsl_compute_agent]
Synchronizing state
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID is
28887aedcb4a469199950992e92e5710
2012-10-31 16:14:38DEBUG [amqplib] Closed channel #1
2012-10-31 16:14:38DEBUG [amqplib] using channel_id: 1
2012-10-31 16:14:38DEBUG [amqplib] Channel open
2012-10-31 16:14:38ERROR [quantum.agent.fsl_compute_agent]
[FslComputeAgent] Unable to sync network state.
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fsl_compute_agent.py,
line 91, in sync_state
get_host_instances_info = set(self.plugin_rpc.get_host_instances_info())
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fsl_compute_agent.py,
line 131, in get_host_instances_info
topic=self.topic)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/proxy.py,
line 83, in call
return rpc.call(context, self._get_topic(topic), msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/__init__.py,
line 102, in call
return _get_impl().call(cfg.CONF, context, topic, msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/impl_kombu.py,
line 712, in call
rpc_amqp.get_connection_pool(conf, Connection))
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 380, in call
rv = list(rv)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 336, in __iter__
raise result
RemoteError: Remote error: AttributeError No such RPC function
'get_host_instances_info'
[u'Traceback (most recent call last):\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py,
line 275, in _process_data\nrval = self.proxy.dispatch(ctxt, version,
method, **args)\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/dispatcher.py,
line 148, in dispatch\nraise AttributeError(No such RPC function
\'%s\' % method)\n', uAttributeError: No such RPC function
'get_host_instances_info'\n].
The error is AttributeError No such RPC function
'get_host_instances_info'
I have written the method to support the agents method, by following the
DHCP agent method get_active_networks.
The following files are modified by adding the RPC function method.
db/db_base_plugin_v2.py:1268:def
_get_host_instances_info(self,context,filters=None,fields=None):
db/fslcompute_rpc_base.py:47:def get_host_instances_info(self, context,
**kwargs):
db/fslcompute_rpc_base.py:50:LOG.debug('[FslComputeCallbackMixin]
get_host_instances_info :: Getting instances info for host %s.', host)
db/fslcompute_rpc_base.py:55:return
plugin.get_host_instances_info(context, filters=filters)
Being a newbee for this code base, Unable to plot what is the BIT that is
missing in this rpc communication.
Please help me to troubleshoot this issue.
Thanks in advance...
--
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
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 Folsom Install Guide
Hi Stackers, i am currently seeing a lot of people having trouble deploying OpenStack Folsom si i humbly present this guide for those who are experimented and even those who are still taking their first steps into the cloud world. The guide has been updated from the last version to support: * Multi Node install * ubuntu server 12.10 * Quatum Configuration * No Quantum is you are not interrested Test it to see for yourself how simple and fun has OpenStack deployment has became ! OpenStack Folsom Install Guide https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst Cheers ___ 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] OpenStack Folsom Install Guide
Hi Skibie, If we can have installation guide for demo setup like Network Node, Compute Node and Controller Node that would be great as it will help to create deployment setup.. If any body has installation guide as per demo setup, Please share regards, Balaji On Wed, Oct 31, 2012 at 6:16 PM, Skible OpenStack skible.openst...@gmail.com wrote: Hi Stackers, i am currently seeing a lot of people having trouble deploying OpenStack Folsom si i humbly present this guide for those who are experimented and even those who are still taking their first steps into the cloud world. The guide has been updated from the last version to support: * Multi Node install * ubuntu server 12.10 * Quatum Configuration * No Quantum is you are not interrested Test it to see for yourself how simple and fun has OpenStack deployment has became ! OpenStack Folsom Install Guidehttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst Cheers ___ 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] OpenStack Folsom Install Guide
Hi Balaji, My guide is inspired from the demo setup. What i have done is fused the network node and the controller node ;) to a single node (mother node) while leaving the compute node unharmed ! i probably should post a picture for my deployment architecture regards, Le 31/10/2012 14:02, balaji patnala a écrit : Hi Skibie, If we can have installation guide for demo setup like Network Node, Compute Node and Controller Node that would be great as it will help to create deployment setup.. If any body has installation guide as per demo setup, Please share regards, Balaji On Wed, Oct 31, 2012 at 6:16 PM, Skible OpenStack skible.openst...@gmail.com mailto:skible.openst...@gmail.com wrote: Hi Stackers, i am currently seeing a lot of people having trouble deploying OpenStack Folsom si i humbly present this guide for those who are experimented and even those who are still taking their first steps into the cloud world. The guide has been updated from the last version to support: * Multi Node install * ubuntu server 12.10 * Quatum Configuration * No Quantum is you are not interrested Test it to see for yourself how simple and fun has OpenStack deployment has became ! OpenStack Folsom Install Guide https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst Cheers ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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] [ceilometer] meter data volume
On Wed, Oct 31 2012, 吴亚伟 wrote: 1) '12389000' nanoseconds means '123.89' seconds or two minutes,it seem like to be 1238.9 seconds actually, is there something wrong ? Why do you think it's 1238.9 seconds? 2) If I never reboot or suspend vm_1, will the 'counter_volume' of cpu usage record increase all the time ? Just like '8 minutes' - '18 minutes' - '28 minutes' ? It's a CPU time, not an uptime. http://en.wikipedia.org/wiki/CPU_time 3) If I reboot or suspend vm_1, I find that the 'counter_volume' of cpu usage record will count from zero. Just like '8 minutes' - '18 minutes' - '28 minutes' [- '0 minutes'] -'5 minutes' - '15 minutes'. Does it mean that 'counter_volume' just represents how long has vm_1 been booted up ? Not at all. It means the CPU time consumed is reset to 0, but that's not an issue in itself, the API should be capable to deal with that if you ask for the total usage. 4) This one is about Web API. I find that GET /v1/resources/(resource)/meters/(meter)/volume/sum just return the sum value of all the cpu 'counter_volume', like '8 minutes' + '18 minutes'. Is it reduplicate ? Don't understand what you mean, but the CPU counter is a cumulative one, and asking for its sum is a non-sense. You want to ask for (max - min) to get the used value, something which is not in the API yet. 5) If I want to know how long has vm_1's cpu been used yesterday, how can I do ? Just like I wrote above. :) -- Julien Danjou ;; Free Software hacker freelance ;; http://julien.danjou.info pgpLlWTwzAZGK.pgp Description: 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
Re: [Openstack] [ceilometer] meter data volume
Hi Yawei Wu, The root of the confusion is the fact the cpu meter is reporting the cumlative cpu_time stat from libvirt. This libvirt counter is reset when the associated qemu process is restarted (an artifact of how cpuacct works). So when you stop/start or suspend/resume, a fresh qemu process is sparked up, then the cumulative time is reset. Thanks for bringing this up, as it has implications as to how we meter CPU time and utilization[1]. We may need to start metering the delta between CPU times on subsequent polling cycles, instead of using a cumulative meter (dealing with the edge case where the instance has been restarted within a polling period). Cheers, Eoghan [1] https://review.openstack.org/14921 I am still testing ceilometer now. I am confused about the meter volume in the mongodb. Let's talk about cpu usage. After I create and boot a vm named vm_1, meter data record about cpu usage will be inserted into db in cycle(default 10 minutes). For example,the 'counter_volume' of the first record is '5206000',and the second one is '12389000'. 1) '12389000' nanoseconds means '123.89' seconds or two minutes,it seem like to be 1238.9 seconds actually, is there something wrong ? 2) If I never reboot or suspend vm_1, will the 'counter_volume' of cpu usage record increase all the time ? Just like '8 minutes' - '18 minutes' - '28 minutes' ? 3) If I reboot or suspend vm_1, I find that the 'counter_volume' of cpu usage record will count from zero. Just like '8 minutes' - '18 minutes' - '28 minutes' [- '0 minutes'] -'5 minutes' - '15 minutes'. Does it mean that 'counter_volume' just represents how long has vm_1 been booted up ? 4) This one is about Web API. I find that GET /v1/resources/(resource)/meters/(meter)/volume/sum just return the sum value of all the cpu 'counter_volume', like '8 minutes' + '18 minutes'. Is it reduplicate ? 5) If I want to know how long has vm_1's cpu been used yesterday, how can I do ? It seems like that I have too many questions.. Thank you very much ! --- Yawei Wu Dalian Hi-Think Computer Technology,Corp. ___ 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] [ceilometer] meter data volume
Not at all. It means the CPU time consumed is reset to 0, but that's not an issue in itself, the API should be capable to deal with that if you ask for the total usage. Would that total usage be much more apparent if we started metering the delta between CPU times on subsequent polling periods as a gauge measure? (As opposed to treating it as a cumulative measure) /v1/resources/(resource)/meters/(meter)/volume/sum just return the sum value of all the cpu 'counter_volume', like '8 minutes' + '18 minutes'. Is it reduplicate ? Don't understand what you mean, but the CPU counter is a cumulative one, and asking for its sum is a non-sense. You want to ask for (max - min) to get the used value, something which is not in the API yet. I don't think (max - min) would suffice to give an accurate measure of the actual CPU time used, as the counter may have reset multiple times in the course of the requested duration. Cheers, Eoghan ___ 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] [ceilometer] meter data volume
On Wed, Oct 31 2012, Eoghan Glynn wrote: Would that total usage be much more apparent if we started metering the delta between CPU times on subsequent polling periods as a gauge measure? (As opposed to treating it as a cumulative measure) I'm rather against the idea of transforming all cumulative counters to delta, for the simple reason that this imply to lose information if your system is not launched to compute delta, or that you have to maintaint a previous value accross restart. The API will be capable to do the operation you need, no matter what the type of counter is (delta or cumulative). I don't think (max - min) would suffice to give an accurate measure of the actual CPU time used, as the counter may have reset multiple times in the course of the requested duration. It is, because /max in the API should be aware of the fact a reset can occur and computes accordingly. We started to discuss this a bit in: https://bugs.launchpad.net/ceilometer/+bug/1061817 -- Julien Danjou # Free Software hacker freelance # http://julien.danjou.info pgpRVR7qdZlI9.pgp Description: 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
Re: [Openstack] [ceilometer] meter data volume
I don't think (max - min) would suffice to give an accurate measure of the actual CPU time used, as the counter may have reset multiple times in the course of the requested duration. It is, because /max in the API should be aware of the fact a reset can occur and computes accordingly. We started to discuss this a bit in: https://bugs.launchpad.net/ceilometer/+bug/1061817 A-ha, OK, so not so much (max - min) as: (\Sigma local maxima) - first Sounds computationally expensive to produce on the fly, but maybe the local maxima can be efficiently recorded as the data is being ingested. Cheers, Eoghan ___ 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] [ceilometer] meter data volume
On Wed, Oct 31 2012, Eoghan Glynn wrote: A-ha, OK, so not so much (max - min) as: (\Sigma local maxima) - first Yeah, excuse my math. :) Sounds computationally expensive to produce on the fly, but maybe the local maxima can be efficiently recorded as the data is being ingested. Yes it's more expense in theory, but in practice I'm rather than with a good back-end it's not a problem (either pre-compute or have the right toolslike PostgreSQL). -- Julien Danjou ;; Free Software hacker freelance ;; http://julien.danjou.info pgp32opSBDDAj.pgp Description: 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
Re: [Openstack] Scheduler issues in folsom
Hi All While the RetryScheduler may not have been designed specifically to fix this issue https://bugs.launchpad.net/nova/+bug/1011852 suggests that it is meant to fix it, well if it is a scheduler race condition which is my suspicion. This is my current scheduler config which gives the failure mode I describe: scheduler_available_filters=nova.scheduler.filters.standard_filters scheduler_default_filters=AvailabilityZoneFilter,RamFilter,CoreFilter,ComputeFilte r,RetryFilter scheduler_max_attempts=30 least_cost_functions=nova.scheduler.least_cost.compute_fill_first_cost_fn compute_fill_first_cost_fn_weight=1.0 cpu_allocation_ratio=1.0 ram_allocation_ratio=1.0 I'm running the scheduler and api server on a single controller host and it's pretty consistent about scheduling hundred instances per node at first then iteratively rescheduling them elsewhere when presented with either an single API request to start many instances (using euca2ools) or a shell loop around nova boot to generate one api request per server. the cpu_allocation ratio should limit the scheduler to 24 instances per compute node regardless how how it's calculating memory, so while I talked a lot about memory allocation as a motivation it is more frequent for cpu to actually be the limiting factor in my deployment and it certainly should. And yet after attempting to launch 200 m1.tiny instances: root@nimbus-0:~# nova-manage service describe_resource nova-23 2012-10-31 11:17:56 HOST PROJECT cpu mem(mb) hdd nova-23 (total)24 48295 882 nova-23 (used_now)107 56832 30 nova-23 (used_max)107 56320 30 nova-23 98333a1a28e746fa8c629c83a818ad57 106 54272 0 nova-23 3008a142e9524f7295b06ea811908f93 1 2048 30 eventually those bleed off to other systems though not entirely 2012-10-31 11:29:41 HOST PROJECT cpu mem(mb) hdd nova-23 (total)24 48295 882 nova-23 (used_now) 43 24064 30 nova-23 (used_max) 43 23552 30 nova-23 98333a1a28e746fa8c629c83a818ad57 42 21504 0 nova-23 3008a142e9524f7295b06ea811908f93 1 2048 30 at this point 12min later out of 200 instances 168 are active 22 are errored and 10 are still building. Notably only 23 actual VMs are running on nova-23: root@nova-23:~# virsh list|grep instance |wc -l 23 So that's what I see perhaps my assumptions about why I'm seeing it are incorrect Thanks, -Jon ___ 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] OpenStack Folsom Install Guide
Hi All Here is my openstack folsom + quantum chef automation code. It has controller, compute, network configuration and quantum + ovs plugin. Please refer this works ^^; Because it's a personal spike works. It has lack of documentation and some comments are korean. It can be your starting point. 2012. 10. 31., 오후 10:06, Skible OpenStack skible.openst...@gmail.com 작성: Hi Balaji, My guide is inspired from the demo setup. What i have done is fused the network node and the controller node ;) to a single node (mother node) while leaving the compute node unharmed ! i probably should post a picture for my deployment architecture regards, Le 31/10/2012 14:02, balaji patnala a écrit : Hi Skibie, If we can have installation guide for demo setup like Network Node, Compute Node and Controller Node that would be great as it will help to create deployment setup.. If any body has installation guide as per demo setup, Please share regards, Balaji On Wed, Oct 31, 2012 at 6:16 PM, Skible OpenStack skible.openst...@gmail.com wrote: Hi Stackers, i am currently seeing a lot of people having trouble deploying OpenStack Folsom si i humbly present this guide for those who are experimented and even those who are still taking their first steps into the cloud world. The guide has been updated from the last version to support: * Multi Node install * ubuntu server 12.10 * Quatum Configuration * No Quantum is you are not interrested Test it to see for yourself how simple and fun has OpenStack deployment has became ! OpenStack Folsom Install Guide Cheers ___ 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 ___ 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-dev] Folsom Quantum Agent :: No such RPC function
Hi-
Please help troubleshoot the issue
I have written a fake agent with the study from the dhcp agent.
The rpc agent daemon is running with the below errors.
But I have missed some bits of information with respect to the rpc
communication.
In the log, I have the following errors.
2012-10-31 16:14:38 INFO [quantum.agent.fake_compute_agent]
Synchronizing state
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID is
28887aedcb4a469199950992e92e5710
2012-10-31 16:14:38DEBUG [amqplib] Closed channel #1
2012-10-31 16:14:38DEBUG [amqplib] using channel_id: 1
2012-10-31 16:14:38DEBUG [amqplib] Channel open
2012-10-31 16:14:38ERROR [quantum.agent.fake_compute_agent]
[FakeComputeAgent] Unable to sync network state.
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fake_compute_agent.py,
line 91, in sync_state
get_host_instances_info = set(self.plugin_rpc.get_host_instances_info())
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fake_compute_agent.py,
line 131, in get_host_instances_info
topic=self.topic)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/proxy.py,
line 83, in call
return rpc.call(context, self._get_topic(topic), msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/__init__.py,
line 102, in call
return _get_impl().call(cfg.CONF, context, topic, msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/impl_kombu.py,
line 712, in call
rpc_amqp.get_connection_pool(conf, Connection))
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 380, in call
rv = list(rv)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 336, in __iter__
raise result
RemoteError: Remote error: AttributeError No such RPC function
'get_host_instances_info'
[u'Traceback (most recent call last):\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py,
line 275, in _process_data\nrval = self.proxy.dispatch(ctxt, version,
method, **args)\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/dispatcher.py,
line 148, in dispatch\nraise AttributeError(No such RPC function
\'%s\' % method)\n', uAttributeError: No such RPC function
'get_host_instances_info'\n].
The error is AttributeError No such RPC function
'get_host_instances_info'
I have written the method to support the agents method, by following the
DHCP agent method get_active_networks.
The following files are modified by adding the RPC function method.
db/db_base_plugin_v2.py:1268:def
_get_host_instances_info(self,context,filters=None,fields=None):
db/fakecompute_rpc_base.py:47:def get_host_instances_info(self,
context, **kwargs):
db/fakecompute_rpc_base.py:50:LOG.debug('[FakeComputeCallbackMixin]
get_host_instances_info :: Getting instances info for host %s.', host)
db/fakecompute_rpc_base.py:55:return
plugin.get_host_instances_info(context, filters=filters)
Being a newbee for this code base, Unable to plot what is the BIT that is
missing in this rpc communication.
Please help me to troubleshoot this issue.
Thanks in advance...
-
Trinath
___
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] OpenStack + Instances stuck in build state
In my case... - Glance image fetching error - Quantum ip address allocation error these case are make similar building state. please review nova-compute, quantum logs. 2012. 10. 31., 오후 6:01, Desta Haileselassie Hagos desta161...@gmail.com 작성: Hi All, VM instances are stuck in build state for three days as you can see it from the attached figure. What do you think is the reason for this? Any help would be appreciated. With best regards, Desta Instance_BUILD.png___ 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] Fwd: Openstack
Is libvirt actually running?
Does `virsh list` exit with an error?
Doesn't sounds VNC related to me.
Thanks,
Kiall
Sent from my phone.
On Oct 31, 2012 10:04 AM, Joe Warren-Meeks joe.warren.me...@gmail.com
wrote:
On 31 October 2012 00:42, Curtis C. serverasc...@gmail.com wrote:
On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
Hi guys,
Can someone point me in the direction of a guide to get Openstack
working with two nodes, one as controller and the second as a compute
node, please?
I've tried the CSS corp PDF and the hastexo one, but I can't get them
to work. All I get are virts booting straight into error.
I want a controller node to run all keystone, glance and nova db
functions then a compute node to run the virtuals with vlans bridging
using 8021q. I've tried so many permutations and configs. I can't
believe I'm doing something that outrageous, but I've hacked away at
this for hours and hours with no joy.
Is virtualization turned on in the BIOS?
I think nova show ID will show an error message if the instance fails
to
Virtualization is enabled. All the instances end up as follows:
+-+--+
| Property |Value
|
+-+--+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-SRV-ATTR:host| None
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
| OS-EXT-SRV-ATTR:instance_name | instance-0002
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | scheduling
|
| OS-EXT-STS:vm_state | error
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive|
|
| created | 2012-10-30T22:23:57Z
|
| flavor | m1.small
|
| hostId |
|
| id |
fae6adf8-2314-4096-ab0c-531dce090c34 |
| image | Cirros Test
|
| key_name| joe
|
| metadata| {}
|
| name| test3
|
| status | ERROR
|
| tenant_id | b38c7e05403542ea91a3cb69e25e63de
|
| updated | 2012-10-30T22:23:57Z
|
| user_id | b6d25008d81a456888e92dd3ffaf9cc5
|
+-+--+
nova-compute.log contains:
CRITICAL nova [-] Unable to read from monitor: Connection reset by peer
and
libvirtError: Unable to read from monitor: Connection reset by peer
I've made sure the vnc IP addresses are correct in nova.conf
Any pointers?
___
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] Fwd: Openstack
And - what does `nova-manage service list` show.
Thanks,
Kiall
Sent from my phone.
On Oct 31, 2012 3:56 PM, Kiall Mac Innes ki...@managedit.ie wrote:
Is libvirt actually running?
Does `virsh list` exit with an error?
Doesn't sounds VNC related to me.
Thanks,
Kiall
Sent from my phone.
On Oct 31, 2012 10:04 AM, Joe Warren-Meeks joe.warren.me...@gmail.com
wrote:
On 31 October 2012 00:42, Curtis C. serverasc...@gmail.com wrote:
On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
Hi guys,
Can someone point me in the direction of a guide to get Openstack
working with two nodes, one as controller and the second as a compute
node, please?
I've tried the CSS corp PDF and the hastexo one, but I can't get them
to work. All I get are virts booting straight into error.
I want a controller node to run all keystone, glance and nova db
functions then a compute node to run the virtuals with vlans bridging
using 8021q. I've tried so many permutations and configs. I can't
believe I'm doing something that outrageous, but I've hacked away at
this for hours and hours with no joy.
Is virtualization turned on in the BIOS?
I think nova show ID will show an error message if the instance
fails to
Virtualization is enabled. All the instances end up as follows:
+-+--+
| Property |Value
|
+-+--+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-SRV-ATTR:host| None
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
| OS-EXT-SRV-ATTR:instance_name | instance-0002
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | scheduling
|
| OS-EXT-STS:vm_state | error
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive|
|
| created | 2012-10-30T22:23:57Z
|
| flavor | m1.small
|
| hostId |
|
| id |
fae6adf8-2314-4096-ab0c-531dce090c34 |
| image | Cirros Test
|
| key_name| joe
|
| metadata| {}
|
| name| test3
|
| status | ERROR
|
| tenant_id | b38c7e05403542ea91a3cb69e25e63de
|
| updated | 2012-10-30T22:23:57Z
|
| user_id | b6d25008d81a456888e92dd3ffaf9cc5
|
+-+--+
nova-compute.log contains:
CRITICAL nova [-] Unable to read from monitor: Connection reset by peer
and
libvirtError: Unable to read from monitor: Connection reset by peer
I've made sure the vnc IP addresses are correct in nova.conf
Any pointers?
___
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] OpenStack Folsom Install Guide
Hi Cheng-Dae Choe, I would love to add your work to my guide for richer user choices ;) if you may allow me. however, i can't see to find a link ! P.S: don't worry about korean comments, everyone likes GanGnam style now :) Le 31/10/2012 16:41, Cheng-Dae Choe a écrit : Hi All Here is my openstack folsom + quantum chef automation code. It has controller, compute, network configuration and quantum + ovs plugin. Please refer this works ^^; Because it's a personal spike works. It has lack of documentation and some comments are korean. It can be your starting point. 2012. 10. 31., 오후 10:06, Skible OpenStack skible.openst...@gmail.com mailto:skible.openst...@gmail.com 작성: Hi Balaji, My guide is inspired from the demo setup. What i have done is fused the network node and the controller node ;) to a single node (mother node) while leaving the compute node unharmed ! i probably should post a picture for my deployment architecture regards, Le 31/10/2012 14:02, balaji patnala a écrit : Hi Skibie, If we can have installation guide for demo setup like Network Node, Compute Node and Controller Node that would be great as it will help to create deployment setup.. If any body has installation guide as per demo setup, Please share regards, Balaji On Wed, Oct 31, 2012 at 6:16 PM, Skible OpenStack skible.openst...@gmail.com mailto:skible.openst...@gmail.com wrote: Hi Stackers, i am currently seeing a lot of people having trouble deploying OpenStack Folsom si i humbly present this guide for those who are experimented and even those who are still taking their first steps into the cloud world. The guide has been updated from the last version to support: * Multi Node install * ubuntu server 12.10 * Quatum Configuration * No Quantum is you are not interrested Test it to see for yourself how simple and fun has OpenStack deployment has became ! OpenStack Folsom Install Guide https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst Cheers ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack 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] OpenStack Folsom Install Guide
2012. 11. 1., 오전 1:02, Skible OpenStack skible.openst...@gmail.com 작성: Hi Cheng-Dae Choe, Hi Skible! I would love to add your work to my guide for richer user choices ;) if you may allow me. Sure! however, i can't see to find a link ! Oh.. I missed.. here is https://github.com/whitekid/openstack-chef P.S: don't worry about korean comments, everyone likes GanGnam style now :) I love too. GangNam Style! Le 31/10/2012 16:41, Cheng-Dae Choe a écrit : Hi All Here is my openstack folsom + quantum chef automation code. It has controller, compute, network configuration and quantum + ovs plugin. Please refer this works ^^; Because it's a personal spike works. It has lack of documentation and some comments are korean. It can be your starting point. 2012. 10. 31., 오후 10:06, Skible OpenStack skible.openst...@gmail.com 작성: Hi Balaji, My guide is inspired from the demo setup. What i have done is fused the network node and the controller node ;) to a single node (mother node) while leaving the compute node unharmed ! i probably should post a picture for my deployment architecture regards, Le 31/10/2012 14:02, balaji patnala a écrit : Hi Skibie, If we can have installation guide for demo setup like Network Node, Compute Node and Controller Node that would be great as it will help to create deployment setup.. If any body has installation guide as per demo setup, Please share regards, Balaji On Wed, Oct 31, 2012 at 6:16 PM, Skible OpenStack skible.openst...@gmail.com wrote: Hi Stackers, i am currently seeing a lot of people having trouble deploying OpenStack Folsom si i humbly present this guide for those who are experimented and even those who are still taking their first steps into the cloud world. The guide has been updated from the last version to support: * Multi Node install * ubuntu server 12.10 * Quatum Configuration * No Quantum is you are not interrested Test it to see for yourself how simple and fun has OpenStack deployment has became ! OpenStack Folsom Install Guide Cheers ___ 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 ___ 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] [ceilometer] meter data volume
On Wed, Oct 31, 2012 at 10:23 AM, Eoghan Glynn egl...@redhat.com wrote: Hi Yawei Wu, The root of the confusion is the fact the cpu meter is reporting the cumlative cpu_time stat from libvirt. This libvirt counter is reset when the associated qemu process is restarted (an artifact of how cpuacct works). So when you stop/start or suspend/resume, a fresh qemu process is sparked up, then the cumulative time is reset. Thanks for bringing this up, as it has implications as to how we meter CPU time and utilization[1]. We may need to start metering the delta between CPU times on subsequent polling cycles, instead of using a cumulative meter (dealing with the edge case where the instance has been restarted within a polling period). Good idea. We need to capture this issue to make sure we get it onto the roadmap for this cycle. Is there a bug or blueprint for it yet? Doug Cheers, Eoghan [1] https://review.openstack.org/14921 I am still testing ceilometer now. I am confused about the meter volume in the mongodb. Let's talk about cpu usage. After I create and boot a vm named vm_1, meter data record about cpu usage will be inserted into db in cycle(default 10 minutes). For example,the 'counter_volume' of the first record is '5206000',and the second one is '12389000'. 1) '12389000' nanoseconds means '123.89' seconds or two minutes,it seem like to be 1238.9 seconds actually, is there something wrong ? 2) If I never reboot or suspend vm_1, will the 'counter_volume' of cpu usage record increase all the time ? Just like '8 minutes' - '18 minutes' - '28 minutes' ? 3) If I reboot or suspend vm_1, I find that the 'counter_volume' of cpu usage record will count from zero. Just like '8 minutes' - '18 minutes' - '28 minutes' [- '0 minutes'] -'5 minutes' - '15 minutes'. Does it mean that 'counter_volume' just represents how long has vm_1 been booted up ? 4) This one is about Web API. I find that GET /v1/resources/(resource)/meters/(meter)/volume/sum just return the sum value of all the cpu 'counter_volume', like '8 minutes' + '18 minutes'. Is it reduplicate ? 5) If I want to know how long has vm_1's cpu been used yesterday, how can I do ? It seems like that I have too many questions.. Thank you very much ! --- Yawei Wu Dalian Hi-Think Computer Technology,Corp. ___ 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 ___ 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] [ceilometer] meter data volume
On Wed, Oct 31, 2012 at 11:25 AM, Eoghan Glynn egl...@redhat.com wrote: I don't think (max - min) would suffice to give an accurate measure of the actual CPU time used, as the counter may have reset multiple times in the course of the requested duration. It is, because /max in the API should be aware of the fact a reset can occur and computes accordingly. We started to discuss this a bit in: https://bugs.launchpad.net/ceilometer/+bug/1061817 A-ha, OK, so not so much (max - min) as: (\Sigma local maxima) - first Sounds computationally expensive to produce on the fly, but maybe the local maxima can be efficiently recorded as the data is being ingested. Is that better than just reporting the data in a more easily digested format in the first place? Julien, I don't understand your comment about losing data if your system is not launched to compute delta. Can you clarify what you mean there? I do understand that the agent would need to store state about the counter locally in order to track the delta value, but I think we could provide a convenient way for pollsters to do that without complicating them excessively. Doug Cheers, Eoghan ___ 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] [ceilometer] meter data volume
On Wed, Oct 31 2012, Doug Hellmann wrote: Is that better than just reporting the data in a more easily digested format in the first place? IMHO yes. Julien, I don't understand your comment about losing data if your system is not launched to compute delta. Can you clarify what you mean there? I do understand that the agent would need to store state about the counter locally in order to track the delta value, but I think we could provide a convenient way for pollsters to do that without complicating them excessively. Yes, actually I think you got what I meant, I just wrote it badly. By system, I meant pollster. If your pollster is not running to compute delta and you have no state stored, you'll miss a part of what has been used. Now, I don't think trying to circumvente that at the pollster level is a good idea either, because it complicates the pollster for no good reason. Ultimately, if you reaaay want to compute delta instead of using the real values of the counter for whatever (bad) reaason, doing it at the storage back-end lavel might be an option if you want. But as I said, for now there's now reason it should be needed. (And you know what they say, early optimization is the root of all evil :) -- Julien Danjou // Free Software hacker freelance // http://julien.danjou.info pgpy2t7myJXp4.pgp Description: 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
Re: [Openstack] Verification of Keystone Installation fails
Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12760203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203944 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1044985224 (1.0 GB) TX bytes:22642912 (22.6 MB) Interrupt:16 Memory:b200-b202 root@bodega:~# I am attaching keystone.conf file. Would you happen to know if there is a high level document document on keystone (more than just a user guide, but a architectural/functional doc, but not a API doc). Something similar to http://docs.openstack.org/trunk/openstack-identity/admin/os-identity-starter-guide-trunk.pdf but updated. Does my current issue prohibit me from progressing forward with the next steps in the install document, setting up glance, nova, etc.? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 9:44 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails The error you're seeing is actually client-side, so there won't be anything in keystone's logs. It indicates that you're not actually authenticating with keystone (and instead bypassing authentication using --token and --endpoint, for example) ... however, that's obviously not the case, as you're explicitly providing --os-username, etc. Unfortunately, I'm not able to reproduce this issue. Can you share your OS_* environment variables? I suspect something there is unexpectedly overriding what you're providing on the CLI... which would be a legitimate bug. Thanks, -Dolph On Wed, Oct 31, 2012 at 2:08 AM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hello, I followed the steps in the OpenStack Install Deploy for Ubuntu manual to install Keystone. However, when I issue the commands in section Verifying the Identity Service Installation ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/verifying-identity-install.html ), I am getting the following error: # keystone --os-username=admin --os-password=admin --os-auth-url=http://10.176.20.158:35357/v2.0 token-get 'Client' object has no attribute 'service_catalog' I don't see any additional info in keystone.log. Can someone please help me. Thank you, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp keystone.conf Description: keystone.conf ___ 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] [ceilometer] meter data volume
If your pollster is not running to compute delta and you have no state stored, you'll miss a part of what has been used. Would we have also have some 'misses' with the cumulative approach when the ceilometer agent was down? If I understood the (\Sigma local maxima)-first idea correctly, the usage up to the first polling cycle would always be discounted from any duration. Similarly, calculating the time delta as a gauge measure would discount only the usage up to the first libvirt poll after each ceilo agent restart. As long as the ceilo compute agent was restarted only rarely, I'm not sure the under-reporting would be a huge issue in either case. A more pernicious problem would occur if the instance was being regularly restarted with a higher frequency than the polling period. Cheers, Eoghan ___ 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] [ceilometer] meter data volume
On Wed, Oct 31 2012, Eoghan Glynn wrote: Would we have also have some 'misses' with the cumulative approach when the ceilometer agent was down? No, unless the counter resets several times while your agent is down. But delta has the same issue. If I understood the (\Sigma local maxima)-first idea correctly, the usage up to the first polling cycle would always be discounted from any duration. No, because if you have: Time | Value 0| 10 1| 30 2| 50 3| 80 4| 100 If your delta-pollster is down at 1 and 2, you restart at 3, therefore at 4 you'll send 20 as usage (100 minus 80). So you miss the delta between 10 (time 0) and 80 (time 3) (therefore 70 for free!). If you send right away 80 at time 3 when restarting, the API will be able to guess that between 0 and 3 the value went from 10 to 80. With delta approach, the API cannot guess that. A more pernicious problem would occur if the instance was being regularly restarted with a higher frequency than the polling period. Yes, but in that case, whatever counting method you use, you're screwed. :) -- Julien Danjou -- Free Software hacker freelance -- http://julien.danjou.info pgpPm0HT9Gwc2.pgp Description: 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
Re: [Openstack] [openstack-dev] Folsom Quantum Agent :: No such RPC function
Hi-
Can any one help me troubleshooting this issue...
Thanks in advance.
-
Trinath
On Wed, Oct 31, 2012 at 9:16 PM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
Please help troubleshoot the issue
I have written a fake agent with the study from the dhcp agent.
The rpc agent daemon is running with the below errors.
But I have missed some bits of information with respect to the rpc
communication.
In the log, I have the following errors.
2012-10-31 16:14:38 INFO [quantum.agent.fake_compute_agent]
Synchronizing state
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID is
28887aedcb4a469199950992e92e5710
2012-10-31 16:14:38DEBUG [amqplib] Closed channel #1
2012-10-31 16:14:38DEBUG [amqplib] using channel_id: 1
2012-10-31 16:14:38DEBUG [amqplib] Channel open
2012-10-31 16:14:38ERROR [quantum.agent.fake_compute_agent]
[FakeComputeAgent] Unable to sync network state.
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fake_compute_agent.py,
line 91, in sync_state
get_host_instances_info =
set(self.plugin_rpc.get_host_instances_info())
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fake_compute_agent.py,
line 131, in get_host_instances_info
topic=self.topic)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/proxy.py,
line 83, in call
return rpc.call(context, self._get_topic(topic), msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/__init__.py,
line 102, in call
return _get_impl().call(cfg.CONF, context, topic, msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/impl_kombu.py,
line 712, in call
rpc_amqp.get_connection_pool(conf, Connection))
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 380, in call
rv = list(rv)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 336, in __iter__
raise result
RemoteError: Remote error: AttributeError No such RPC function
'get_host_instances_info'
[u'Traceback (most recent call last):\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py,
line 275, in _process_data\nrval = self.proxy.dispatch(ctxt, version,
method, **args)\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/dispatcher.py,
line 148, in dispatch\nraise AttributeError(No such RPC function
\'%s\' % method)\n', uAttributeError: No such RPC function
'get_host_instances_info'\n].
The error is AttributeError No such RPC function
'get_host_instances_info'
I have written the method to support the agents method, by following the
DHCP agent method get_active_networks.
The following files are modified by adding the RPC function method.
db/db_base_plugin_v2.py:1268:def
_get_host_instances_info(self,context,filters=None,fields=None):
db/fakecompute_rpc_base.py:47:def get_host_instances_info(self,
context, **kwargs):
db/fakecompute_rpc_base.py:50:
LOG.debug('[FakeComputeCallbackMixin] get_host_instances_info :: Getting
instances info for host %s.', host)
db/fakecompute_rpc_base.py:55:return
plugin.get_host_instances_info(context, filters=filters)
Being a newbee for this code base, Unable to plot what is the BIT that is
missing in this rpc communication.
Please help me to troubleshoot this issue.
Thanks in advance...
-
Trinath
--
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
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] Verification of Keystone Installation fails
I was able to reproduce by defining SERVICE_ENDPOINT and SERVICE_TOKEN in my own environment, which appear to be overriding the credentials provided on the CLI -- I don't think that's the intended behavior. If you unset them, you should be able to verify the install. If you skip verifying keystone and something is wrong with it, you'll likely find out pretty quick when another service calls keystone for the first time :) -Dolph On Wed, Oct 31, 2012 at 12:22 PM, Ahmed Al-Mehdi ah...@coraid.com wrote: Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12760203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203944 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1044985224 (1.0 GB) TX bytes:22642912 (22.6 MB) Interrupt:16 Memory:b200-b202 root@bodega:~# I am attaching keystone.conf file. Would you happen to know if there is a high level document document on keystone (more than just a user guide, but a architectural/functional doc, but not a API doc). Something similar to http://docs.openstack.org/trunk/openstack-identity/admin/os-identity-starter-guide-trunk.pdf but updated. Does my current issue prohibit me from progressing forward with the next steps in the install document, setting up glance, nova, etc.? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.com Date: Wednesday, October 31, 2012 9:44 AM To: Ahmed Al-Mehdi ah...@coraid.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails The error you're seeing is actually client-side, so there won't be anything in keystone's logs. It indicates that you're not actually authenticating with keystone (and instead bypassing authentication using --token and --endpoint, for example) ... however, that's obviously not the case, as you're explicitly providing --os-username, etc. Unfortunately, I'm not able to reproduce this issue. Can you share your OS_* environment variables? I suspect something there is unexpectedly overriding what you're providing on the CLI... which would be a legitimate bug. Thanks, -Dolph On Wed, Oct 31, 2012 at 2:08 AM, Ahmed Al-Mehdi ah...@coraid.com wrote: Hello, I followed the steps in the OpenStack Install Deploy for Ubuntu manual to install Keystone. However, when I issue the commands in section Verifying the Identity Service Installation ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/verifying-identity-install.html ), I am getting the following error: # keystone --os-username=admin --os-password=admin --os-auth-url= http://10.176.20.158:35357/v2.0 token-get 'Client' object has no attribute 'service_catalog' I don't see any additional info in keystone.log. Can someone please help me. Thank you, Ahmed. ___ 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] Scheduler issues in folsom
Hi Jonathan, If I understand correctly, that bug is about multiple scheduler instances(processes) doing scheduler at the same time. When compute node found itself unable to fulfil a create_instance request, it'll resend the request back to scheduler (max_retry is to avoid endless retry). From your description, I only see one scheduler. And you are right, even memory may have some issue but about cpu_allocation_ratio should have limit scheduler to put instances with more vCPUs then pCPUs. What openstack package are you using? On Wed, Oct 31, 2012 at 11:41 PM, Jonathan Proulx j...@jonproulx.com wrote: Hi All While the RetryScheduler may not have been designed specifically to fix this issue https://bugs.launchpad.net/nova/+bug/1011852 suggests that it is meant to fix it, well if it is a scheduler race condition which is my suspicion. This is my current scheduler config which gives the failure mode I describe: scheduler_available_filters=nova.scheduler.filters.standard_filters scheduler_default_filters=AvailabilityZoneFilter,RamFilter,CoreFilter,ComputeFilte r,RetryFilter scheduler_max_attempts=30 least_cost_functions=nova.scheduler.least_cost.compute_fill_first_cost_fn compute_fill_first_cost_fn_weight=1.0 cpu_allocation_ratio=1.0 ram_allocation_ratio=1.0 I'm running the scheduler and api server on a single controller host and it's pretty consistent about scheduling hundred instances per node at first then iteratively rescheduling them elsewhere when presented with either an single API request to start many instances (using euca2ools) or a shell loop around nova boot to generate one api request per server. the cpu_allocation ratio should limit the scheduler to 24 instances per compute node regardless how how it's calculating memory, so while I talked a lot about memory allocation as a motivation it is more frequent for cpu to actually be the limiting factor in my deployment and it certainly should. And yet after attempting to launch 200 m1.tiny instances: root@nimbus-0:~# nova-manage service describe_resource nova-23 2012-10-31 11:17:56 HOST PROJECT cpu mem(mb) hdd nova-23 (total)24 48295 882 nova-23 (used_now)107 56832 30 nova-23 (used_max)107 56320 30 nova-23 98333a1a28e746fa8c629c83a818ad57 106 54272 0 nova-23 3008a142e9524f7295b06ea811908f93 1 2048 30 eventually those bleed off to other systems though not entirely 2012-10-31 11:29:41 HOST PROJECT cpu mem(mb) hdd nova-23 (total)24 48295 882 nova-23 (used_now) 43 24064 30 nova-23 (used_max) 43 23552 30 nova-23 98333a1a28e746fa8c629c83a818ad57 42 21504 0 nova-23 3008a142e9524f7295b06ea811908f93 1 2048 30 at this point 12min later out of 200 instances 168 are active 22 are errored and 10 are still building. Notably only 23 actual VMs are running on nova-23: root@nova-23:~# virsh list|grep instance |wc -l 23 So that's what I see perhaps my assumptions about why I'm seeing it are incorrect Thanks, -Jon -- Regards Huang Zhiteng ___ 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] Fwd: Openstack
nova-manage service list showed all smiley faces, with the relevant service
running on the correct servers.
I've decided to not split it out now. I'm going to use what was the
controller just as an iscsi target, then run the full stack on what was
going to be the compute nodes.
Thanks for all your help!
On 31 October 2012 15:58, Kiall Mac Innes ki...@managedit.ie wrote:
And - what does `nova-manage service list` show.
Thanks,
Kiall
Sent from my phone.
On Oct 31, 2012 3:56 PM, Kiall Mac Innes ki...@managedit.ie wrote:
Is libvirt actually running?
Does `virsh list` exit with an error?
Doesn't sounds VNC related to me.
Thanks,
Kiall
Sent from my phone.
On Oct 31, 2012 10:04 AM, Joe Warren-Meeks joe.warren.me...@gmail.com
wrote:
On 31 October 2012 00:42, Curtis C. serverasc...@gmail.com wrote:
On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
Hi guys,
Can someone point me in the direction of a guide to get Openstack
working with two nodes, one as controller and the second as a compute
node, please?
I've tried the CSS corp PDF and the hastexo one, but I can't get them
to work. All I get are virts booting straight into error.
I want a controller node to run all keystone, glance and nova db
functions then a compute node to run the virtuals with vlans bridging
using 8021q. I've tried so many permutations and configs. I can't
believe I'm doing something that outrageous, but I've hacked away at
this for hours and hours with no joy.
Is virtualization turned on in the BIOS?
I think nova show ID will show an error message if the instance
fails to
Virtualization is enabled. All the instances end up as follows:
+-+--+
| Property |Value
|
+-+--+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-SRV-ATTR:host| None
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
| OS-EXT-SRV-ATTR:instance_name | instance-0002
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | scheduling
|
| OS-EXT-STS:vm_state | error
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive|
|
| created | 2012-10-30T22:23:57Z
|
| flavor | m1.small
|
| hostId |
|
| id |
fae6adf8-2314-4096-ab0c-531dce090c34 |
| image | Cirros Test
|
| key_name| joe
|
| metadata| {}
|
| name| test3
|
| status | ERROR
|
| tenant_id |
b38c7e05403542ea91a3cb69e25e63de |
| updated | 2012-10-30T22:23:57Z
|
| user_id |
b6d25008d81a456888e92dd3ffaf9cc5 |
+-+--+
nova-compute.log contains:
CRITICAL nova [-] Unable to read from monitor: Connection reset by peer
and
libvirtError: Unable to read from monitor: Connection reset by peer
I've made sure the vnc IP addresses are correct in nova.conf
Any pointers?
___
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] Fwd: Openstack
I did try that with no joy..
On 31 October 2012 15:50, Gui Maluf guimal...@gmail.com wrote:
have you tried to disable vnc and check if is working?
I followed official doc using multi_host. This is my vnc configs
#VNC CONSOLE
--vnc_enabled=true
--vncproxy_url=http://cloud-controller-ip:6080
--vnc_console_proxy_url=http://cloud-controller-ip:6080
--novnc_enabled=true
--novncproxy_base_url=http://cloud-controller-ip:6080/vnc_auto.html
--vncserver_proxyclient_address=$my_ip
--vncserver_listen=$my_ip
if you are using a shared file system make sure all user have the same
permission, same UID and same GID
On Wed, Oct 31, 2012 at 8:03 AM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
On 31 October 2012 00:42, Curtis C. serverasc...@gmail.com wrote:
On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
Hi guys,
Can someone point me in the direction of a guide to get Openstack
working with two nodes, one as controller and the second as a compute
node, please?
I've tried the CSS corp PDF and the hastexo one, but I can't get them
to work. All I get are virts booting straight into error.
I want a controller node to run all keystone, glance and nova db
functions then a compute node to run the virtuals with vlans bridging
using 8021q. I've tried so many permutations and configs. I can't
believe I'm doing something that outrageous, but I've hacked away at
this for hours and hours with no joy.
Is virtualization turned on in the BIOS?
I think nova show ID will show an error message if the instance fails
to
Virtualization is enabled. All the instances end up as follows:
+-+--+
| Property |Value
|
+-+--+
| OS-DCF:diskConfig | MANUAL
|
| OS-EXT-SRV-ATTR:host| None
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
| OS-EXT-SRV-ATTR:instance_name | instance-0002
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state | scheduling
|
| OS-EXT-STS:vm_state | error
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive|
|
| created | 2012-10-30T22:23:57Z
|
| flavor | m1.small
|
| hostId |
|
| id |
fae6adf8-2314-4096-ab0c-531dce090c34 |
| image | Cirros Test
|
| key_name| joe
|
| metadata| {}
|
| name| test3
|
| status | ERROR
|
| tenant_id | b38c7e05403542ea91a3cb69e25e63de
|
| updated | 2012-10-30T22:23:57Z
|
| user_id | b6d25008d81a456888e92dd3ffaf9cc5
|
+-+--+
nova-compute.log contains:
CRITICAL nova [-] Unable to read from monitor: Connection reset by peer
and
libvirtError: Unable to read from monitor: Connection reset by peer
I've made sure the vnc IP addresses are correct in nova.conf
Any pointers?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
guilherme \n
\tab maluf
___
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] [openstack-dev] Folsom Quantum Agent :: No such RPC function
I'd suggest posting a diff or pushing your changes to a publicly accessible
repo to help people understand the changes you made.
On Wed, Oct 31, 2012 at 10:43 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
Can any one help me troubleshooting this issue...
Thanks in advance.
-
Trinath
On Wed, Oct 31, 2012 at 9:16 PM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
Please help troubleshoot the issue
I have written a fake agent with the study from the dhcp agent.
The rpc agent daemon is running with the below errors.
But I have missed some bits of information with respect to the rpc
communication.
In the log, I have the following errors.
2012-10-31 16:14:38 INFO [quantum.agent.fake_compute_agent]
Synchronizing state
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2012-10-31 16:14:38DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID
is 28887aedcb4a469199950992e92e5710
2012-10-31 16:14:38DEBUG [amqplib] Closed channel #1
2012-10-31 16:14:38DEBUG [amqplib] using channel_id: 1
2012-10-31 16:14:38DEBUG [amqplib] Channel open
2012-10-31 16:14:38ERROR [quantum.agent.fake_compute_agent]
[FakeComputeAgent] Unable to sync network state.
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fake_compute_agent.py,
line 91, in sync_state
get_host_instances_info =
set(self.plugin_rpc.get_host_instances_info())
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/agent/fake_compute_agent.py,
line 131, in get_host_instances_info
topic=self.topic)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/proxy.py,
line 83, in call
return rpc.call(context, self._get_topic(topic), msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/__init__.py,
line 102, in call
return _get_impl().call(cfg.CONF, context, topic, msg, timeout)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/impl_kombu.py,
line 712, in call
rpc_amqp.get_connection_pool(conf, Connection))
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 380, in call
rv = list(rv)
File
/usr/local/lib/python2.7/dist-packages/quantum-2012.2-py2.7.egg/quantum/openstack/common/rpc/amqp.py,
line 336, in __iter__
raise result
RemoteError: Remote error: AttributeError No such RPC function
'get_host_instances_info'
[u'Traceback (most recent call last):\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py,
line 275, in _process_data\nrval = self.proxy.dispatch(ctxt, version,
method, **args)\n', u' File
/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/dispatcher.py,
line 148, in dispatch\nraise AttributeError(No such RPC function
\'%s\' % method)\n', uAttributeError: No such RPC function
'get_host_instances_info'\n].
The error is AttributeError No such RPC function
'get_host_instances_info'
I have written the method to support the agents method, by following the
DHCP agent method get_active_networks.
The following files are modified by adding the RPC function method.
db/db_base_plugin_v2.py:1268:def
_get_host_instances_info(self,context,filters=None,fields=None):
db/fakecompute_rpc_base.py:47:def get_host_instances_info(self,
context, **kwargs):
db/fakecompute_rpc_base.py:50:
LOG.debug('[FakeComputeCallbackMixin] get_host_instances_info :: Getting
instances info for host %s.', host)
db/fakecompute_rpc_base.py:55:return
plugin.get_host_instances_info(context, filters=filters)
Being a newbee for this code base, Unable to plot what is the BIT that is
missing in this rpc communication.
Please help me to troubleshoot this issue.
Thanks in advance...
-
Trinath
--
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~
___
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] Debugging OpenStack - Video on StackTach v2 and Stacky
Hey! As promised at the summit the latest changes to StackTach are up on github. This is a major change from the original StackTach I introduced earlier this year (and left to wither). Also, I'm including Stacky, which is a new command line tool for StackTach. Here's a video that explains what it's all about, how to install and use it. http://youtu.be/pZgwDHZ3wm0 The repos: https://github.com/rackspace/stacktach https://github.com/rackspace/stacky What we need: + packaging + docs Where we're going: + worker and db improvement ... everything breaks at scale and stacktach is no exception. + Key Performance Indicators (kpi's). Useful for SLA's and other shirt stuff. There is some support in there now (via stacky), but it's busted and inefficient. I'm going to be getting this working again immediately. + Integration with ceilometer. We're duplicating effort here, and are planning to fix that. Please: install, experiment, report bugs, submit pull requests. Look forward to your feedback! -S ___ 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] Scheduler issues in folsom
On Wed, Oct 31, 2012 at 1:47 PM, Huang Zhiteng winsto...@gmail.com wrote: Hi Jonathan, If I understand correctly, that bug is about multiple scheduler There is only a single process, I was reading it as relating to include threads within a single process, but they should clearly be able to serialize this withing a single process, so hoping my reading is not correct. What openstack package are you using? 2012.2-0ubuntu5~cloud0 on Ubuntu 12.04 from Ubuntu cloud-archive. With further testing it appears the allocation ratios are simply being ignored as the ChanceScheduler also violates my resource allocation limits I just hadn't been testing at large enough scale to reliably see it. I am seeing memory allocations 1.5 default ram_allocation_ratio which is somewhat curious. So it's almost as if the RamFilter isn't filtering rather than falling back to the default allocation ration (the compute nodes would melt before I got to the 16:1 default cpu allocation ration so not surprised I'm not getting near that more like 2:1) again despite: scheduler_available_filters=nova.scheduler.filters.standard_filters scheduler_default_filters=AvailabilityZoneFilter,RamFilter,CoreFilter,ComputeFilter,RetryFilter cpu_allocation_ratio=1.0 ram_allocation_ratio=1.0 Thanks, -Jon ___ 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] nova boot errors while attaching a volume to an instance
Hi, I am running GA bits of Folsom. I am running a two node setup where the first node is the controller+compute node that has Cinder running as well. The second node is merely a compute node. I am seeing an issue while booting an instance from Cinder volume on both the nodes. The nova boot operation fails while spawning the instance with the following error. [00mProcessExecutionError: Unexpected error while running command. [00mCommand: sudo nova-rootwrap /etc/nova/rootwrap.conf iscsiadm -m node -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p 192.168.150.96:3260 --rescan [00mExit code: 255 [00mStdout: '' [00mStderr: 'iscsiadm: No portal found.\n' [00m I had successfully created a Cinder volume with a valid image on it. +--+---+--+--+-+-+ | ID | Status | Display Name | Size | Volume Type | Attached to | +--+---+--+--+-+-+ | 3ac4b027-905e-4318-a74e-2bdf94f5d887 | available | Volume1| 2 | None| | +--+---+--+--+-+-+ I even tried to discover the iSCSI targets. But it returns with no records found. I then looked into to MySQL database for Cinder and looked at the entries, specifically provider_location and it looked just fine. 192.168.150.96 is the node where I have controller and cinder running. +---+ | provider_location | +---+ | NULL | | 192.168.150.96:3260,1 iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 1 | I manually tried to discover the iSCSI targets and it couldn't find any. stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m discovery -t sendtargets -p 192.168.150.96:3260 192.168.150.96:3260,1 iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 iscsiadm: Connection to Discovery Address 192.168.150.96 closed iscsiadm: Login I/O error, failed to receive a PDU iscsiadm: retrying discovery login to 192.168.150.96 stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p 192.168.150.96:3260iscsiadm: no records found! stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p 192.168.150.96:3260 --rescan iscsiadm: No portal found. stack@esg-dell-c4-s08:/etc/cinder$ I am not sure what's wrong with my setup. Any help is greatly appreciated. Thanks Vibhu ___ 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] Verification of Keystone Installation fails
Hi Dolph, Awesome, that worked. Thank you very much. Just out of curiosity, what was the exact conflict? Between which environment variable and option passed to the CLI? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 10:46 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net, Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com Subject: Re: [Openstack] Verification of Keystone Installation fails I was able to reproduce by defining SERVICE_ENDPOINT and SERVICE_TOKEN in my own environment, which appear to be overriding the credentials provided on the CLI -- I don't think that's the intended behavior. If you unset them, you should be able to verify the install. If you skip verifying keystone and something is wrong with it, you'll likely find out pretty quick when another service calls keystone for the first time :) -Dolph On Wed, Oct 31, 2012 at 12:22 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12760203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203944 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1044985224 (1.0 GB) TX bytes:22642912 (22.6 MB) Interrupt:16 Memory:b200-b202 root@bodega:~# I am attaching keystone.conf file. Would you happen to know if there is a high level document document on keystone (more than just a user guide, but a architectural/functional doc, but not a API doc). Something similar to http://docs.openstack.org/trunk/openstack-identity/admin/os-identity-starter-guide-trunk.pdf but updated. Does my current issue prohibit me from progressing forward with the next steps in the install document, setting up glance, nova, etc.? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 9:44 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails The error you're seeing is actually client-side, so there won't be anything in keystone's logs. It indicates that you're not actually authenticating with keystone (and instead bypassing authentication using --token and --endpoint, for example) ... however, that's obviously not the case, as you're explicitly providing --os-username, etc. Unfortunately, I'm not able to reproduce this issue. Can you share your OS_* environment variables? I suspect something there is unexpectedly overriding what you're providing on the CLI... which would be a legitimate bug. Thanks, -Dolph On Wed, Oct 31, 2012 at 2:08 AM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hello, I followed the steps in the OpenStack Install Deploy for Ubuntu manual to install Keystone. However, when I issue the commands in section Verifying the Identity Service Installation ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/verifying-identity-install.html ), I am getting the following error: # keystone --os-username=admin --os-password=admin --os-auth-url=http://10.176.20.158:35357/v2.0 token-get 'Client' object has no attribute 'service_catalog' I don't see any additional info in keystone.log. Can someone please help me. Thank you, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto: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] Verification of Keystone Installation fails
I think the overall issue is connected to https://bugs.launchpad.net/keystone/+bug/962600 Right? Seems like that is still happening :-( From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Wednesday, October 31, 2012 1:15 PM To: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails Hi Dolph, Awesome, that worked. Thank you very much. Just out of curiosity, what was the exact conflict? Between which environment variable and option passed to the CLI? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 10:46 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net, Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com Subject: Re: [Openstack] Verification of Keystone Installation fails I was able to reproduce by defining SERVICE_ENDPOINT and SERVICE_TOKEN in my own environment, which appear to be overriding the credentials provided on the CLI -- I don't think that's the intended behavior. If you unset them, you should be able to verify the install. If you skip verifying keystone and something is wrong with it, you'll likely find out pretty quick when another service calls keystone for the first time :) -Dolph On Wed, Oct 31, 2012 at 12:22 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12760203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203944 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1044985224 (1.0 GB) TX bytes:22642912 (22.6 MB) Interrupt:16 Memory:b200-b202 root@bodega:~# I am attaching keystone.conf file. Would you happen to know if there is a high level document document on keystone (more than just a user guide, but a architectural/functional doc, but not a API doc). Something similar to http://docs.openstack.org/trunk/openstack-identity/admin/os-identity-starter-guide-trunk.pdf but updated. Does my current issue prohibit me from progressing forward with the next steps in the install document, setting up glance, nova, etc.? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 9:44 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails The error you're seeing is actually client-side, so there won't be anything in keystone's logs. It indicates that you're not actually authenticating with keystone (and instead bypassing authentication using --token and --endpoint, for example) ... however, that's obviously not the case, as you're explicitly providing --os-username, etc. Unfortunately, I'm not able to reproduce this issue. Can you share your OS_* environment variables? I suspect something there is unexpectedly overriding what you're providing on the CLI... which would be a legitimate bug. Thanks, -Dolph On Wed, Oct 31, 2012 at 2:08 AM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hello, I followed the steps in the OpenStack Install Deploy for Ubuntu manual to install Keystone. However, when I issue the commands in section Verifying the Identity Service Installation ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/verifying-identity-install.html ), I am getting the following error: # keystone --os-username=admin --os-password=admin --os-auth-url=http://10.176.20.158:35357/v2.0 token-get 'Client' object has no attribute 'service_catalog' I don't see any additional info in keystone.log. Can someone please help me. Thank you, Ahmed. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help :
Re: [Openstack] [OpenStack] Limiting new roles
With regard to keystone, the current policy implementation is entirely binary in that a role may either have total control over keystone or none. The implementation in Grizzly is much more granular. -Dolph On Wed, Oct 31, 2012 at 2:35 PM, Guillermo Alvarado guillermoalvarad...@gmail.com wrote: Hi everyboy, I want to create a new role, named another-admin, so this role only can create tentants and roles but cannnot change quotas or modify images and all other actions that admin role can do. I read about create rules in the policy.json of each service (nova, keystone, glance, swift) but my doubt is: How can I limit the views/templates/urls of Horizon, I mean, I want that the role another-admin can not see templates related to glance and can not see that menu. Thanks in advance, Best Regards. ___ 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
[Openstack] Commong Page for IRC meeting schedules
Is there a central location where project meeting schedules are tracked. Even if not, could you please help build one by adding to this threa or at http://wiki.openstack.org/IRC *#openstack* (general discussion, support) *:* *#openstack-cinder* (cinder team discussions) *:* *#openstack-swift* (swift team discussions) *:* *#openstack-nova* (nova team discussions) *:* *#openstack-dev*(development discussion) *:* *#openstack-infra *(infrastructure team discussion, ci, and other infrastructure) *:* *#openstack-meeting* (team meetings) *:* *#openstack-metering* (ceilometer team discussions) *:* *#openstack-packaging* (packaging discussions) *:* *#openstack-chef* (deployment and operating OpenStackhttp://wiki.openstack.org/OpenStackwith Chef) *:* *Hyper-V :* ** *CeiloMeter :* ** *Heat :* ** I will update the page appropriately. ** Thanks, -Sriram ** ___ 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] Commong Page for IRC meeting schedules
http://wiki.openstack.org/Meetings lists all the scheduled meetings. Thanks, Kiall On Wed, Oct 31, 2012 at 9:09 PM, Sriram Subramanian sri...@sriramhere.comwrote: Is there a central location where project meeting schedules are tracked. Even if not, could you please help build one by adding to this threa or at http://wiki.openstack.org/IRC *#openstack* (general discussion, support) *:* *#openstack-cinder* (cinder team discussions) *:* *#openstack-swift* (swift team discussions) *:* *#openstack-nova* (nova team discussions) *:* *#openstack-dev*(development discussion) *:* *#openstack-infra *(infrastructure team discussion, ci, and other infrastructure) *:* *#openstack-meeting* (team meetings) *:* *#openstack-metering* (ceilometer team discussions) *:* *#openstack-packaging* (packaging discussions) *:* *#openstack-chef* (deployment and operating OpenStackhttp://wiki.openstack.org/OpenStackwith Chef) *:* *Hyper-V :* ** *CeiloMeter :* ** *Heat :* ** I will update the page appropriately. ** Thanks, -Sriram ** ___ 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] Verification of Keystone Installation fails
There are basically two rules at work: 1) an existing token takes precedence over username+password credentials. 2) CLI options take precedence over configuration from the environment. In Folsom, these options look like: (existing token) --os-token / OS_SERVICE_TOKEN --os-endpoint / OS_SERVICE_ENDPOINT (credentials) --os-username / OS_USERNAME --os-password / OS_PASSWORD --os-tenant-name / OS_TENANT_NAME --os-auth-url / OS_AUTH_URL (there are also a few other options like region, api version, etc) Rule 1 is universally applied before rule 2, which means the token + endpoint from the environment is taking precedence over username + password from the CLI. IMO, it's a bug that rule 2 isn't applied before rule 1. -Dolph On Wed, Oct 31, 2012 at 3:32 PM, Joshua Harlow harlo...@yahoo-inc.comwrote: I think the overall issue is connected to https://bugs.launchpad.net/keystone/+bug/962600 Right? Seems like that is still happening :-( From: Ahmed Al-Mehdi ah...@coraid.com Date: Wednesday, October 31, 2012 1:15 PM To: Dolph Mathews dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.com, openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails Hi Dolph, Awesome, that worked. Thank you very much. Just out of curiosity, what was the exact conflict? Between which environment variable and option passed to the CLI? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.com Date: Wednesday, October 31, 2012 10:46 AM To: Ahmed Al-Mehdi ah...@coraid.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net, Joseph Heck joe.h...@nebula.com Subject: Re: [Openstack] Verification of Keystone Installation fails I was able to reproduce by defining SERVICE_ENDPOINT and SERVICE_TOKEN in my own environment, which appear to be overriding the credentials provided on the CLI -- I don't think that's the intended behavior. If you unset them, you should be able to verify the install. If you skip verifying keystone and something is wrong with it, you'll likely find out pretty quick when another service calls keystone for the first time :) -Dolph On Wed, Oct 31, 2012 at 12:22 PM, Ahmed Al-Mehdi ah...@coraid.com wrote: Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12760203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203944 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1044985224 (1.0 GB) TX bytes:22642912 (22.6 MB) Interrupt:16 Memory:b200-b202 root@bodega:~# I am attaching keystone.conf file. Would you happen to know if there is a high level document document on keystone (more than just a user guide, but a architectural/functional doc, but not a API doc). Something similar to http://docs.openstack.org/trunk/openstack-identity/admin/os-identity-starter-guide-trunk.pdf but updated. Does my current issue prohibit me from progressing forward with the next steps in the install document, setting up glance, nova, etc.? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.com Date: Wednesday, October 31, 2012 9:44 AM To: Ahmed Al-Mehdi ah...@coraid.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails The error you're seeing is actually client-side, so there won't be anything in keystone's logs. It indicates that you're not actually authenticating with keystone (and instead bypassing authentication using --token and --endpoint, for example) ... however, that's obviously not the case, as you're explicitly providing --os-username, etc. Unfortunately, I'm not able to reproduce this issue. Can you share your OS_* environment variables? I suspect something there is unexpectedly overriding what you're providing on the CLI... which would be a legitimate bug. Thanks, -Dolph On Wed, Oct 31, 2012 at 2:08 AM, Ahmed Al-Mehdi ah...@coraid.com wrote: Hello, I followed the steps in the OpenStack Install Deploy for Ubuntu manual to install Keystone. However, when I issue the commands in section Verifying the Identity Service Installation ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/verifying-identity-install.html ), I am getting the following error: # keystone --os-username=admin --os-password=admin --os-auth-url= http://10.176.20.158:35357/v2.0
Re: [Openstack] Verification of Keystone Installation fails
I think I figured out the issue (as far as what env. variables I should have defined), and this is my fault for …mixing steps stated in Section 5 of Openstack Install for Ubuntu and Appendix B in the same doc. It seems defining the env. variable SERVICE_ENDPOINT causes the failure (not sure if this a bug or user misunderstanding/error). root@bodega:~# env | egrep OS_|SERVICE_ OS_PASSWORD=admin OS_AUTH_URL=http://10.176.20.158:5000/v2.0/ OS_USERNAME=admin OS_TENANT_NAME=openstackDemo SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ root@bodega:~# root@bodega:~# keystone user-list Expecting a token provided via either --token or env[SERVICE_TOKEN] root@bodega:~# However, root@bodega:~# env | egrep OS_|SERVICE_ OS_PASSWORD=admin OS_AUTH_URL=http://10.176.20.158:5000/v2.0/ OS_USERNAME=admin OS_TENANT_NAME=openstackDemo root@bodega:~# root@bodega:~# keystone user-list +--++-+---+ |id| name | enabled | email | +--++-+---+ | 32cc7b40147c46539212870b371c43f0 | swift | True | | | 4eb5d55edb4141aa9950fc25196bd669 | nova | True | | | 6744c4637ea64a1e9ce53ea8e945fc0d | ec2 | True | | | aa5449939470460bb21d391c89327b67 | glance | True | | | ce016bb05df949ebbafcc7c165359d7c | admin | True | | +--++-+---+ root@bodega:~# I apologize for wasting people's time. For now, I will move onto next step. Regards, Ahmed. From: Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com Date: Wednesday, October 31, 2012 1:32 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com, Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails I think the overall issue is connected to https://bugs.launchpad.net/keystone/+bug/962600 Right? Seems like that is still happening :-( From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Wednesday, October 31, 2012 1:15 PM To: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails Hi Dolph, Awesome, that worked. Thank you very much. Just out of curiosity, what was the exact conflict? Between which environment variable and option passed to the CLI? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 10:46 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net, Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com Subject: Re: [Openstack] Verification of Keystone Installation fails I was able to reproduce by defining SERVICE_ENDPOINT and SERVICE_TOKEN in my own environment, which appear to be overriding the credentials provided on the CLI -- I don't think that's the intended behavior. If you unset them, you should be able to verify the install. If you skip verifying keystone and something is wrong with it, you'll likely find out pretty quick when another service calls keystone for the first time :) -Dolph On Wed, Oct 31, 2012 at 12:22 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12760203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203944 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1044985224 (1.0 GB) TX bytes:22642912 (22.6 MB) Interrupt:16 Memory:b200-b202 root@bodega:~# I am attaching keystone.conf file. Would you happen to know if there is a high level document document on keystone (more than just a user guide, but a architectural/functional doc, but not a API doc). Something similar to
Re: [Openstack] Nova different sr
Good night, Could anyone know if it's possible to use different nfs servers or different storages for launching instances in Openstack? Anyone knows about this please? Best regards, Egoirz Aurrekoetxea Aurre ego...@ramattack.net Sent from my smartphone El 29/10/2012, a las 16:13, Egoitz Aurrekoetxea Aurre ego...@ramattack.net escribió: Good afternoon, Is it possible for Nova to deploy vm in different storages?? rather than just use the storage which matches sr_matching_filter parameter?? Best regards, ___ 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] Verification of Keystone Installation fails
Thank you very much for the explanation. After some further tinkering with keystone.conf file, what you explained below is exactly what is happening. Thank you again for bearing with my questions. Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 2:16 PM To: Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com Cc: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com, Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails There are basically two rules at work: 1) an existing token takes precedence over username+password credentials. 2) CLI options take precedence over configuration from the environment. In Folsom, these options look like: (existing token) --os-token / OS_SERVICE_TOKEN --os-endpoint / OS_SERVICE_ENDPOINT (credentials) --os-username / OS_USERNAME --os-password / OS_PASSWORD --os-tenant-name / OS_TENANT_NAME --os-auth-url / OS_AUTH_URL (there are also a few other options like region, api version, etc) Rule 1 is universally applied before rule 2, which means the token + endpoint from the environment is taking precedence over username + password from the CLI. IMO, it's a bug that rule 2 isn't applied before rule 1. -Dolph On Wed, Oct 31, 2012 at 3:32 PM, Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com wrote: I think the overall issue is connected to https://bugs.launchpad.net/keystone/+bug/962600 Right? Seems like that is still happening :-( From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Wednesday, October 31, 2012 1:15 PM To: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails Hi Dolph, Awesome, that worked. Thank you very much. Just out of curiosity, what was the exact conflict? Between which environment variable and option passed to the CLI? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 10:46 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net, Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com Subject: Re: [Openstack] Verification of Keystone Installation fails I was able to reproduce by defining SERVICE_ENDPOINT and SERVICE_TOKEN in my own environment, which appear to be overriding the credentials provided on the CLI -- I don't think that's the intended behavior. If you unset them, you should be able to verify the install. If you skip verifying keystone and something is wrong with it, you'll likely find out pretty quick when another service calls keystone for the first time :) -Dolph On Wed, Oct 31, 2012 at 12:22 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12760203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203944 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1044985224 (1.0 GB) TX bytes:22642912 (22.6 MB) Interrupt:16 Memory:b200-b202 root@bodega:~# I am attaching keystone.conf file. Would you happen to know if there is a high level document document on keystone (more than just a user guide, but a architectural/functional doc, but not a API doc). Something similar to http://docs.openstack.org/trunk/openstack-identity/admin/os-identity-starter-guide-trunk.pdf but updated. Does my current issue prohibit me from progressing forward with the next steps in the install document, setting up glance, nova, etc.? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 9:44 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re:
Re: [Openstack] Verification of Keystone Installation fails
Please ignore my email below, and further testing revealed my findings below to be false. Regards, Ahmed. From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Wednesday, October 31, 2012 2:18 PM To: Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com, Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails I think I figured out the issue (as far as what env. variables I should have defined), and this is my fault for …mixing steps stated in Section 5 of Openstack Install for Ubuntu and Appendix B in the same doc. It seems defining the env. variable SERVICE_ENDPOINT causes the failure (not sure if this a bug or user misunderstanding/error). root@bodega:~# env | egrep OS_|SERVICE_ OS_PASSWORD=admin OS_AUTH_URL=http://10.176.20.158:5000/v2.0/ OS_USERNAME=admin OS_TENANT_NAME=openstackDemo SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ root@bodega:~# root@bodega:~# keystone user-list Expecting a token provided via either --token or env[SERVICE_TOKEN] root@bodega:~# However, root@bodega:~# env | egrep OS_|SERVICE_ OS_PASSWORD=admin OS_AUTH_URL=http://10.176.20.158:5000/v2.0/ OS_USERNAME=admin OS_TENANT_NAME=openstackDemo root@bodega:~# root@bodega:~# keystone user-list +--++-+---+ |id| name | enabled | email | +--++-+---+ | 32cc7b40147c46539212870b371c43f0 | swift | True | | | 4eb5d55edb4141aa9950fc25196bd669 | nova | True | | | 6744c4637ea64a1e9ce53ea8e945fc0d | ec2 | True | | | aa5449939470460bb21d391c89327b67 | glance | True | | | ce016bb05df949ebbafcc7c165359d7c | admin | True | | +--++-+---+ root@bodega:~# I apologize for wasting people's time. For now, I will move onto next step. Regards, Ahmed. From: Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com Date: Wednesday, October 31, 2012 1:32 PM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com, Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails I think the overall issue is connected to https://bugs.launchpad.net/keystone/+bug/962600 Right? Seems like that is still happening :-( From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Date: Wednesday, October 31, 2012 1:15 PM To: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Cc: Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Verification of Keystone Installation fails Hi Dolph, Awesome, that worked. Thank you very much. Just out of curiosity, what was the exact conflict? Between which environment variable and option passed to the CLI? Regards, Ahmed. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 31, 2012 10:46 AM To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net, Joseph Heck joe.h...@nebula.commailto:joe.h...@nebula.com Subject: Re: [Openstack] Verification of Keystone Installation fails I was able to reproduce by defining SERVICE_ENDPOINT and SERVICE_TOKEN in my own environment, which appear to be overriding the credentials provided on the CLI -- I don't think that's the intended behavior. If you unset them, you should be able to verify the install. If you skip verifying keystone and something is wrong with it, you'll likely find out pretty quick when another service calls keystone for the first time :) -Dolph On Wed, Oct 31, 2012 at 12:22 PM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hi Dolph, Thank you very much for helping me on this issue. Following is the environment variables related to openstack: root@bodega:~# env | egrep OS_|SERVICE_ SERVICE_ENDPOINT=http://10.176.20.158:35357/v2.0/ SERVICE_TOKEN=012345SECRET99TOKEN012345 root@bodega:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1e:67:06:1b:67 inet addr:10.176.20.158 Bcast:10.176.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:67ff:fe06:1b67/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Openstack] [Glance] config_file parameter in glance-registry.conf file
Hi, I am following the steps in Openstack install manual for Ubuntu. Section 6 ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/configure-glance-files.html ) states to set the config_file parameter in glance-registry.conf file as follows: [paste_deploy] # Name of the paste configuration file that defines the available pipelines config_file = /etc/glance/glance-api-paste.ini However, based on the commented line in the file (in the unmodified file after install), should config_file be set as follows: config_file = /etc/glance/glance-registry-paste.ini Just verifying if there is a typo in the doc. Thank you, Ahmed. ___ 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] [Glance] config_file parameter in glance-registry.conf file
On Wed, 2012-10-31 at 16:46 -0500, Ahmed Al-Mehdi wrote: I am following the steps in Openstack install manual for Ubuntu. Section 6 ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/configure-glance-files.html ) states to set the config_file parameter in glance-registry.conf file as follows: [snip] However, based on the commented line in the file (in the unmodified file after install), should config_file be set as follows: config_file = /etc/glance/glance-registry-paste.ini You are correct, it should be glance-registry-paste.ini when you're discussing glance-registry.conf. Just verifying if there is a typo in the doc. Looks like it is a typo. Would you mind logging a doc bug on that? -- Kevin L. Mitchell kevin.mitch...@rackspace.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
Re: [Openstack] [ceilometer] meter data volume
Would we have also have some 'misses' with the cumulative approach when the ceilometer agent was down? No, unless the counter resets several times while your agent is down. But delta has the same issue. If I understood the (\Sigma local maxima)-first idea correctly, the usage up to the first polling cycle would always be discounted from any duration. No, because if you have: Time | Value 0| 10 1| 30 2| 50 3| 80 4| 100 If your delta-pollster is down at 1 and 2, you restart at 3, therefore at 4 you'll send 20 as usage (100 minus 80). So you miss the delta between 10 (time 0) and 80 (time 3) (therefore 70 for free!). If you send right away 80 at time 3 when restarting, the API will be able to guess that between 0 and 3 the value went from 10 to 80. With delta approach, the API cannot guess that. Yep the sum of local maxima is not lossy as long as the requested duration completely encapsulates the compute agent outage (and the instance doesn't restart during the outage). However I was more thinking of the scenario where the duration requested via the API is say t1..t4 in your example above. In any case, do we need a new measurement type, in addition to the existing CUMULATIVE type, that captures the non-monotonic nature of the measure and alerts the API that special handling is required to compute say max-min? Something like TRANSIENT_CUMULATIVE, if that's not too much of a mouthful. A more pernicious problem would occur if the instance was being regularly restarted with a higher frequency than the polling period. Yes, but in that case, whatever counting method you use, you're screwed. :) True that. Cheers, Eoghan ___ 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] [OpenStack] Limiting new roles
I'm specifically referring to keystone, because you mention ...this role only can create tentants and roles... If you can create tenants and roles in keystone, you also have the power to create new users and grant yourself additional roles in keystone, due to the binary nature of the policy implementation in keystone today (thereby -- and unfortunately -- defeating the rest of your statement: ... but cannnot change quotas or modify images). -Dolph On Wed, Oct 31, 2012 at 5:29 PM, Guillermo Alvarado guillermoalvarad...@gmail.com wrote: I know the implementation is not binay, you can modify the permissions related with nova/glance/swifth of the differents roles. I doubt is if horizon know wich template can view each user... 2012/10/31 Dolph Mathews dolph.math...@gmail.com With regard to keystone, the current policy implementation is entirely binary in that a role may either have total control over keystone or none. The implementation in Grizzly is much more granular. -Dolph On Wed, Oct 31, 2012 at 2:35 PM, Guillermo Alvarado guillermoalvarad...@gmail.com wrote: Hi everyboy, I want to create a new role, named another-admin, so this role only can create tentants and roles but cannnot change quotas or modify images and all other actions that admin role can do. I read about create rules in the policy.json of each service (nova, keystone, glance, swift) but my doubt is: How can I limit the views/templates/urls of Horizon, I mean, I want that the role another-admin can not see templates related to glance and can not see that menu. Thanks in advance, Best Regards. ___ 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] [OpenStack] Limiting new roles
With respect to the comments on Horizon, as soon as Keystone implements the policy rollup and exposes it in the v3 API Horizon will fully honor the policies specified by the various projects. That blueprint for Keystone was targeted for Folsom but got bumped to Grizzly. Hopefully it'll make it in this time so we can get that done. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Dolph Mathews Sent: Wednesday, October 31, 2012 3:39 PM To: Guillermo Alvarado Cc: openstack Subject: Re: [Openstack] [OpenStack] Limiting new roles I'm specifically referring to keystone, because you mention ...this role only can create tentants and roles... If you can create tenants and roles in keystone, you also have the power to create new users and grant yourself additional roles in keystone, due to the binary nature of the policy implementation in keystone today (thereby -- and unfortunately -- defeating the rest of your statement: ... but cannnot change quotas or modify images). -Dolph On Wed, Oct 31, 2012 at 5:29 PM, Guillermo Alvarado guillermoalvarad...@gmail.commailto:guillermoalvarad...@gmail.com wrote: I know the implementation is not binay, you can modify the permissions related with nova/glance/swifth of the differents roles. I doubt is if horizon know wich template can view each user... 2012/10/31 Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com With regard to keystone, the current policy implementation is entirely binary in that a role may either have total control over keystone or none. The implementation in Grizzly is much more granular. -Dolph On Wed, Oct 31, 2012 at 2:35 PM, Guillermo Alvarado guillermoalvarad...@gmail.commailto:guillermoalvarad...@gmail.com wrote: Hi everyboy, I want to create a new role, named another-admin, so this role only can create tentants and roles but cannnot change quotas or modify images and all other actions that admin role can do. I read about create rules in the policy.json of each service (nova, keystone, glance, swift) but my doubt is: How can I limit the views/templates/urls of Horizon, I mean, I want that the role another-admin can not see templates related to glance and can not see that menu. Thanks in advance, Best Regards. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto: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] [Glance] config_file parameter in glance-registry.conf file
Bug filed - https://bugs.launchpad.net/openstack-manuals/+bug/1073744 Regards, Ahmed. On 10/31/12 3:12 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Wed, 2012-10-31 at 16:46 -0500, Ahmed Al-Mehdi wrote: I am following the steps in Openstack install manual for Ubuntu. Section 6 ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/con figure-glance-files.html ) states to set the config_file parameter in glance-registry.conf file as follows: [snip] However, based on the commented line in the file (in the unmodified file after install), should config_file be set as follows: config_file = /etc/glance/glance-registry-paste.ini You are correct, it should be glance-registry-paste.ini when you're discussing glance-registry.conf. Just verifying if there is a typo in the doc. Looks like it is a typo. Would you mind logging a doc bug on that? -- Kevin L. Mitchell kevin.mitch...@rackspace.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 ___ 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] [Glance] glance index failing with Request returned failure status
Hello,
I followed the steps in OpenStack Install and Deploy Manual – Ubuntu. After
following the steps to install Glance, I issued the command glance index to
test my setup. I am getting an error. Can someone please help.
root@bodega:~/ahmed/temp# glance index
ID Name Disk Format
Container Format Size
--
--
Request returned failure status.
None
HTTPInternalServerError (HTTP 500)
root@bodega:~/ahmed/temp#
/var/log/api.log:
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
Determining version of request: GET /v1/images/detail Accept: process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:45
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
Using url versioning process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:58
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
Matched version: v1 process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:70
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
new uri /v1/images/detail process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:71
2012-10-31 16:16:50 DEBUG glance.api.policy
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Loaded policy rules: {u'default': [],
u'manage_image_cache': [[u'role:admin']]} load_rules
/usr/lib/python2.7/dist-packages/glance/api/policy.py:63
2012-10-31 16:16:50 DEBUG glance.common.client
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Constructed URL:
http://0.0.0.0:9191/images/detail?limit=10 _construct_url
/usr/lib/python2.7/dist-packages/glance/common/client.py:464
2012-10-31 16:16:50 DEBUG glance.common.client
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Constructed URL:
http://0.0.0.0:9191/images/detail?limit=10 _construct_url
/usr/lib/python2.7/dist-packages/glance/common/client.py:464
2012-10-31 16:16:50 ERROR glance.registry.client
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Registry request GET /images/detail Exception
2012-10-31 16:16:50 4140 TRACE glance.registry.client Traceback (most recent
call last):
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/registry/client.py, line 89, in
do_request
2012-10-31 16:16:50 4140 TRACE glance.registry.client action, **kwargs)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 66, in wrapped
2012-10-31 16:16:50 4140 TRACE glance.registry.client return func(self,
*args, **kwargs)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 444, in
do_request
2012-10-31 16:16:50 4140 TRACE glance.registry.client headers=headers)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 80, in wrapped
2012-10-31 16:16:50 4140 TRACE glance.registry.client return func(self,
method, url, body, headers)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 566, in
_do_request
2012-10-31 16:16:50 4140 TRACE glance.registry.client raise
exception.NotAuthenticated(res.read())
2012-10-31 16:16:50 4140 TRACE glance.registry.client NotAuthenticated: 401
Unauthorized
2012-10-31 16:16:50 4140 TRACE glance.registry.client
2012-10-31 16:16:50 4140 TRACE glance.registry.client 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.
2012-10-31 16:16:50 4140 TRACE glance.registry.client
2012-10-31 16:16:50 4140 TRACE glance.registry.client Authentication required
2012-10-31 16:16:50 4140 TRACE glance.registry.client
/var/log/registry.log:
2012-10-31 16:16:50 4120 WARNING keystone.middleware.auth_token [-] Unexpected
response from keystone service: {u'error': {u'message': u'Invalid tenant',
u'code': 401, u'title': u'Not Authorized'}}
2012-10-31 16:16:50 4120 WARNING keystone.middleware.auth_token [-]
Authorization failed for token f9b08f547be24e77a903bcdfa11ad1ac
2012-10-31 16:16:50 4120 INFO keystone.middleware.auth_token [-] Invalid user
token - rejecting request
2012-10-31 16:16:50 4120 WARNING keystone.middleware.auth_token [-] Unable to
find authentication
Re: [Openstack] [Glance] glance index failing with Request returned failure status
My immediate thought is that you configured glance-registry to use keystone
authentication but you didn't do the same for glance-api. Make sure you add the
following to glance-registry.conf:
[paste_deploy]
flavor=keystone
On Oct 31, 2012, at 4:46 PM, Ahmed Al-Mehdi wrote:
Hello,
I followed the steps in OpenStack Install and Deploy Manual – Ubuntu.
After following the steps to install Glance, I issued the command glance
index to test my setup. I am getting an error. Can someone please help.
root@bodega:~/ahmed/temp# glance index
ID Name Disk
Format Container Format Size
--
--
Request returned failure status.
None
HTTPInternalServerError (HTTP 500)
root@bodega:~/ahmed/temp#
/var/log/api.log:
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
Determining version of request: GET /v1/images/detail Accept:
process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:45
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
Using url versioning process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:58
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
Matched version: v1 process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:70
2012-10-31 16:16:49 4140 DEBUG glance.api.middleware.version_negotiation [-]
new uri /v1/images/detail process_request
/usr/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:71
2012-10-31 16:16:50 DEBUG glance.api.policy
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Loaded policy rules: {u'default': [],
u'manage_image_cache': [[u'role:admin']]} load_rules
/usr/lib/python2.7/dist-packages/glance/api/policy.py:63
2012-10-31 16:16:50 DEBUG glance.common.client
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Constructed URL:
http://0.0.0.0:9191/images/detail?limit=10 _construct_url
/usr/lib/python2.7/dist-packages/glance/common/client.py:464
2012-10-31 16:16:50 DEBUG glance.common.client
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Constructed URL:
http://0.0.0.0:9191/images/detail?limit=10 _construct_url
/usr/lib/python2.7/dist-packages/glance/common/client.py:464
2012-10-31 16:16:50 ERROR glance.registry.client
[0946431c-90d7-4063-8593-8d02ea89513a ce016bb05df949ebbafcc7c165359d7c
ce1e819636744dc680fa5515f6475e87] Registry request GET /images/detail
Exception
2012-10-31 16:16:50 4140 TRACE glance.registry.client Traceback (most recent
call last):
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/registry/client.py, line 89, in
do_request
2012-10-31 16:16:50 4140 TRACE glance.registry.client action, **kwargs)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 66, in
wrapped
2012-10-31 16:16:50 4140 TRACE glance.registry.client return func(self,
*args, **kwargs)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 444, in
do_request
2012-10-31 16:16:50 4140 TRACE glance.registry.client headers=headers)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 80, in
wrapped
2012-10-31 16:16:50 4140 TRACE glance.registry.client return func(self,
method, url, body, headers)
2012-10-31 16:16:50 4140 TRACE glance.registry.client File
/usr/lib/python2.7/dist-packages/glance/common/client.py, line 566, in
_do_request
2012-10-31 16:16:50 4140 TRACE glance.registry.client raise
exception.NotAuthenticated(res.read())
2012-10-31 16:16:50 4140 TRACE glance.registry.client NotAuthenticated: 401
Unauthorized
2012-10-31 16:16:50 4140 TRACE glance.registry.client
2012-10-31 16:16:50 4140 TRACE glance.registry.client 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.
2012-10-31 16:16:50 4140 TRACE glance.registry.client
2012-10-31 16:16:50 4140 TRACE glance.registry.client Authentication
required
2012-10-31 16:16:50 4140 TRACE glance.registry.client
/var/log/registry.log:
2012-10-31 16:16:50 4120 WARNING keystone.middleware.auth_token [-]
Unexpected response from keystone service: {u'error': {u'message': u'Invalid
Re: [Openstack] Scheduler issues in folsom
On Oct 31, 2012, at 1:44 PM, Jonathan Proulx j...@jonproulx.com wrote: I'd only been pushing these options to the host the scheduler runs on, is it that simple? I'm delight if I'm an an idiot and just need a few line in a config file, but puzzled why this was (seemingly at least) working with Essex, certainly my users didn't start screaming till I dropped Folsom on them… Looking at the code it appears that the relevent info is being sent down to the compute node. That said I can't seem to repro your issue with even just the ram filter. I can't get it to overallocate on one node unless I specifically change the ratio, regardless of fill-first or spread-first. Vish ___ 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] Handling of adminPass is arguably broken (essex)
TL;DR: The way OpenStack handles the adminPass attribute during metadata injection is not useful on operating systems without an /etc/passwd and /etc/shadow. I would like to make the adminPass value available on a Windows instance, and this is my proposal for how to do it. I've been putting together a Windows 2008 server image for deploying in our OpenStack environment. I started by setting it up to act just like our Linux images: - It has sshd running as a service via Cygwin - It runs a script at startup to pull an ssh key from the metadata server for the Administrator account. This works great! But I've had some push-back from folks who argue that this process won't be familiar to a typical Windows administrator, so I started trying to figure how to get an administrator password either (a) into the instance from the person creating it, or (b) back to the person creating the instance after generating the password. (a) is relatively easy to do via the user-data attribute, and I have a prototype of that working. However... One of my colleagues mention that there was some mechanism for injecting passwords into instances -- which sounds perfect. Based on my efforts in #openstack, it appears that very few people take advantage of this feature or even know how it operates, so I went diving through the code and eventually found myself in nova/virt/disk/api.py, where I discovered that even with config_drive=True, nova will attempt to copy /etc/passwd and /etc/shadow (which don't exist) off the config drive to modify them locally. This obviously fails, leaving the admin password inaccessible. I would like to propose that if config_drive=True, that the admin password simply get written into a file, where it could be used by operating systems without an /etc/passwd or /etc/shadow file. If this sounds like a good idea, I'll work up a patch. It seems that for this to work, inject_data needs to know whether or not it's targeting a config_drive or an actual partition...and so does inject_data_into_fs. Maybe something like: In virt/libvirt/connection.py: disk.inject_data(injection_path, key, net, metadata, admin_pass, files, partition=target_partition, use_cow=FLAGS.use_cow_images, config_drive=config_drive) And in virt/disk/api.py: def inject_data(image, key=None, net=None, metadata=None, admin_password=None, files=None, partition=None, use_cow=False, config_drive=False): ... inject_data_into_fs(img.mount_dir, key, net, metadata, admin_password, files, config_drive=False) ... def inject_data_into_fs(fs, key, net, metadata, admin_password, files, config_drive=False): ... if admin_password: if config_drive: _inject_admin_password_as_file_into_fs(admin_password, fs) else: _inject_admin_password_into_fs(admin_password, fs) Thoughts? -- Lars Kellogg-Stedman l...@seas.harvard.edu | Senior Technologist | http://ac.seas.harvard.edu/ Academic Computing| http://code.seas.harvard.edu/ Harvard School of Engineering | and Applied Sciences| ___ 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] Handling of adminPass is arguably broken (essex)
Just fyi, the cloud-init format 'spec' has something similar that bypasses the file injection (which is a bad/insecure/incompatible concept that needs to be gotten rid of imho) by having the following syntax it understands: http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc /examples/cloud-config-user-groups.txt Is there anyway a windows version of cloud-init could be done, either ported, or patched, or a service like cloud-init could be added to windows images (using a startup program in the windows image that could just be a call-out to a python interpreter or something different...). In the linux image world it is pretty common to have a version of cloud-init be bootstrapped into the image so it would seem like windows could be similar. On 10/31/12 6:09 PM, Lars Kellogg-Stedman l...@seas.harvard.edu wrote: TL;DR: The way OpenStack handles the adminPass attribute during metadata injection is not useful on operating systems without an /etc/passwd and /etc/shadow. I would like to make the adminPass value available on a Windows instance, and this is my proposal for how to do it. I've been putting together a Windows 2008 server image for deploying in our OpenStack environment. I started by setting it up to act just like our Linux images: - It has sshd running as a service via Cygwin - It runs a script at startup to pull an ssh key from the metadata server for the Administrator account. This works great! But I've had some push-back from folks who argue that this process won't be familiar to a typical Windows administrator, so I started trying to figure how to get an administrator password either (a) into the instance from the person creating it, or (b) back to the person creating the instance after generating the password. (a) is relatively easy to do via the user-data attribute, and I have a prototype of that working. However... One of my colleagues mention that there was some mechanism for injecting passwords into instances -- which sounds perfect. Based on my efforts in #openstack, it appears that very few people take advantage of this feature or even know how it operates, so I went diving through the code and eventually found myself in nova/virt/disk/api.py, where I discovered that even with config_drive=True, nova will attempt to copy /etc/passwd and /etc/shadow (which don't exist) off the config drive to modify them locally. This obviously fails, leaving the admin password inaccessible. I would like to propose that if config_drive=True, that the admin password simply get written into a file, where it could be used by operating systems without an /etc/passwd or /etc/shadow file. If this sounds like a good idea, I'll work up a patch. It seems that for this to work, inject_data needs to know whether or not it's targeting a config_drive or an actual partition...and so does inject_data_into_fs. Maybe something like: In virt/libvirt/connection.py: disk.inject_data(injection_path, key, net, metadata, admin_pass, files, partition=target_partition, use_cow=FLAGS.use_cow_images, config_drive=config_drive) And in virt/disk/api.py: def inject_data(image, key=None, net=None, metadata=None, admin_password=None, files=None, partition=None, use_cow=False, config_drive=False): ... inject_data_into_fs(img.mount_dir, key, net, metadata, admin_password, files, config_drive=False) ... def inject_data_into_fs(fs, key, net, metadata, admin_password, files, config_drive=False): ... if admin_password: if config_drive: _inject_admin_password_as_file_into_fs(admin_password, fs) else: _inject_admin_password_into_fs(admin_password, fs) Thoughts? -- Lars Kellogg-Stedman l...@seas.harvard.edu | Senior Technologist | http://ac.seas.harvard.edu/ Academic Computing| http://code.seas.harvard.edu/ Harvard School of Engineering | and Applied Sciences| ___ 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] Handling of adminPass is arguably broken (essex)
On Oct 31, 2012, at 7:04 PM, Lars Kellogg-Stedman l...@seas.harvard.edu wrote: Injection via files on a configuration disk seems to me the best way to handle security credentials like this, because disks in many cases require privileges to mount on a system and the configuration script can delete the credentials file after processing it. Honestly I think the entire idea of passing a password in to the instance at boot time is insecure and flawed. The best idea I've heard for a secure windows password is the following: a) put a public key on the instance via metadata or config drive (for ease of use this could actually just be the ssh public key you normally use for logging into the vm). b) have a daemon in the windows instance that: * generates a random password * sets the administrator password to the random password * encrypts it with the public key * serves the encrypted password over https on a known port (say ) c) open up port () in the instance's security group d) retrieve the encrypted password and decrypt it e) close port () in the instances security group for extra security you could use make daemon run for a certain amount of time on initial boot or have a a specific url on the port that stops the daemon. If we could collaborate on a daemon that does this on the guest side then we could actually create a nova command that would do all of the above and display the password to the user. In fact this would work for non-windows vms as well. nova get-password uuid Vish ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
