Re: [Openstack] multi-host mode in quantum
Hello, As Grizzly is released today, can anybody confirm that the multi-host network mode is supported by Quantum in this new release? Thanks, Xin On 12/13/2012 6:04 AM, Heiko Krämer wrote: Hey Guys, it's a good point. I hope this option will include in Grizzly. We get now (since the switch to Quantum) network I/O bottlenecks without using all NIC's of our nodes. So I'm looking forward to Grizzly Greetings Heiko Am 12.12.2012 17:11, schrieb Gary Kotton: On 12/12/2012 05:58 PM, Xin Zhao wrote: Hello, If I understand it correctly, multi-host network mode is not supported (yet) in quantum in Folsom. I wonder what's the recommended way of running multiple network nodes (for load balancing and bandwidth concerns) in quantum? Any documentation links will be appreciated. At the moment this is in discussion upstream. It is currently not supported but we are hoping to have support for this in grizzly. Thanks, Xin ___ 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 ___ 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] floating ip takes a long time to be accessible
Hi Nate, Thanks for your reply. But I am not running in multi-host mode now. The cluster uses one nova-networking service on the controller node. Xin On 12/17/2012 9:31 PM, Nathanael Burton wrote: On Dec 17, 2012 2:05 PM, Xin Zhao xz...@bnl.gov mailto:xz...@bnl.gov wrote: Hello, I allocate 2 public ips to instances, the first one becomes accessible almost immediately, but the second one always take a long time to be pingable. It doesn't matter which specific IP is assigned first or second, it's always the second one that is slow to be reachable, although the corresponding iptable rules are all set on the controller node almost immediately. Has anyone seen similar behavior? I am using essex (2012.1) on RHEL6. Thanks, Xin ___ 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 Xin, You may need to use send_arp_for_ha=true to send a gratuitous ARP if you're using multi-host networking. Nate smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] floating ip takes a long time to be accessible
Hello, I allocate 2 public ips to instances, the first one becomes accessible almost immediately, but the second one always take a long time to be pingable. It doesn't matter which specific IP is assigned first or second, it's always the second one that is slow to be reachable, although the corresponding iptable rules are all set on the controller node almost immediately. Has anyone seen similar behavior? I am using essex (2012.1) on RHEL6. Thanks, Xin smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] multi-host mode in quantum
Hello, If I understand it correctly, multi-host network mode is not supported (yet) in quantum in Folsom. I wonder what's the recommended way of running multiple network nodes (for load balancing and bandwidth concerns) in quantum? Any documentation links will be appreciated. Thanks, Xin smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] clean up zombie instances ?
Hello, I have to shut down some running instances from worker nodes, as the physical machine suffer disk errors. After I remove them from worker nodes, nova still thinks the instances are in shutoff state, although they are completely disappeared already on worker nodes. I tried nova delete and euca-terminate-instance commands, try to clean them off the list as shown from euca-describe-instances, without success. How can I clean up these zombie instances? I am using essex release 2012.1.1-15 on RHEL6. Thanks, Xin smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] instance can't start?
Hello, While most of the instances are running fine in my openstack cluster, but there are few that are stuck in either build, networking or scheduling state, and can't even be deleted. On the compute nodes, I see in the log: 2012-10-11 10:26:46 WARNING nova.compute.manager [-] Found 5 in the database and 1 on the hypervisor. 2012-10-11 10:26:47 WARNING nova.compute.manager [-] [instance: da5106f4-deb2-4827-952e-7cb19388ea8d] Instance found in database but not known by hypervisor. Setting power state to NOSTATE 2012-10-11 10:26:47 WARNING nova.compute.manager [-] [instance: c2dfb29c-af78-42b3-9811-c72d00f1995e] Instance found in database but not known by hypervisor. Setting power state to NOSTATE 2012-10-11 10:26:48 WARNING nova.compute.manager [-] [instance: 92febd69-ddc4-489f-8120-1b272d788856] Instance found in database but not known by hypervisor. Setting power state to NOSTATE 2012-10-11 10:26:48 WARNING nova.compute.manager [-] [instance: 3ff3bd7c-87ef-4425-83c3-d27103c52ee0] Instance found in database but not known by hypervisor. Setting power state to NOSTATE Any wisdom what is happening here? Thanks, Xin smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] question about multi-host network configuration
Hello, Our openstack cluster has 2 racks of physical nodes, I want to set up two openstack network service hosts, each serving one rack. Can I do that? Thanks, Xin smime.p7s Description: S/MIME Cryptographic 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] question about multi-host network configuration
Sorry I should have made it more clear: among the hosts in one rack, only one of them have 2 nics, one being internet facing, all other nodes have only one internal nic. So I can't run nova-network on *every* compute node. Xin On 9/17/2012 10:55 AM, Razique Mahroua wrote: Sure, just install nova-network on every node and enable the multi_host=true flag on every nova.conf file :) Nuage Co - Razique Mahroua razique.mahr...@gmail.com Le 17 sept. 2012 16:38, Xin Zhao xz...@bnl.gov a crit : Hello, Our openstack cluster has 2 racks of physical nodes, I want to set up two openstack network service hosts, each serving one rack. Can I do that? Thanks, Xin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME Cryptographic 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] question about multi-host network configuration
I have been using flatdhcp mode in a single-host network configuration. Will flatdhcp also work in this 2 nova-network setting, or a vlan mode is preferred here? Thanks, Xin On 9/17/2012 11:05 AM, Razique Mahroua wrote: ok in such case, install nova-network on both servers having the two nics, which network mode do you intend to use ? Nuage Co - Razique Mahroua razique.mahr...@gmail.com Le 17 sept. 2012 16:59, Xin Zhao xz...@bnl.gov a crit : Sorry I should have made it more clear: among the hosts in one rack, only one of them have 2 nics, one being internet facing, all other nodes have only one internal nic. So I can't run nova-network on *every* compute node. Xin On 9/17/2012 10:55 AM, Razique Mahroua wrote: Sure, just install nova-network on every node and enable the multi_host=true flag on every nova.conf file :) Nuage Co - Razique Mahroua razique.mahr...@gmail.com Pice jointe.jpeg Le 17 sept. 2012 16:38, Xin Zhao xz...@bnl.gov a crit : Hello, Our openstack cluster has 2 racks of physical nodes, I want to set up two openstack network service hosts, each serving one rack. Can I do that? Thanks, Xin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] how to configure network on controller with 2 nics ?
Hello, I follow the instruction below to install openstack on RHEL6, but it only shows how to configure network with one NIC. Where can I find the doc about configuring openstack network with both public facing and private facing NICs, on RHEL6? http://docs.openstack.org/essex/openstack-compute/install/yum/content/compute-configuring-guest-network.html By the way, the official doc in the above link is for ubuntu. Please correct it for RHEL6 usage. Thanks, Xin smime.p7s Description: S/MIME Cryptographic 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] keystone initialization problem
Thanks all for the suggestions, it helped to trace to the real problem: our own proxy server is misconfigured, nothing to do with openstack. After fixing proxy server, it works. Thanks, Xin On 8/17/2012 6:28 PM, Adam Young wrote: OK, SERVICE_TOKEN is the same as --token You can follow the steps here: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_OpenStack_Preview/ Specifically: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_OpenStack_Preview/1/html/Getting_Started_Guide/ch02.html#id3165390 || *|export SERVICE_TOKEN=$(openssl rand -hex 10)|* || *|export SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0|* || *|echo $SERVICE_TOKEN /tmp/ks_admin_token|* || *|sudo openstack-config --set /etc/keystone/keystone.conf \|* *|DEFAULT admin_token $SERVICE_TOKEN|* and that should be the admin_token value that you have. If nothing is in the log, it probably means you have not actually hit the right server. On 08/17/2012 05:47 PM, Dolph Mathews wrote: The admin_token value from keystone.conf is not a real token; it exists as a string in memory and has no context, user or actual roles associated with it (hence it does not appear in your token table). As for your actual issue, I don't see anything obviously wrong with what's below. Is logging enabled working, otherwise? Have you tried verbose = True and debug = True? Have you tried running that command from the compute node itself, rather than over the internet IP? What happens when you curl / GET / whatever http://internet_ip of the controller node:35357/v2.0 and/or http://127.0.0.1:35357/v2.0 ? -Dolph On Fri, Aug 17, 2012 at 3:26 PM, Xin Zhao xz...@bnl.gov mailto:xz...@bnl.gov wrote: Hello, I newly install keystone on the RHEL6 machine, but it is not working. The following command fails: $ keystone --token admin_token string from keystone.conf --endpoint http://internet_ip of the controller node:35357/v2.0 tenant-create --name openstackDemo --description Default Tenant --enabled true Unable to communicate with identity service: (403, 'Forbidden'). (HTTP 400) There is no relevant log in the keystone.log file. Here is the instruction I follow: http://docs.openstack.org/essex/openstack-compute/install/yum/content/setting-up-tenants-users-and-roles.html This is done on the controller node itself. I can telnet to internet_ip of the controller node:35357. I can also log into mysql DB as keystone user, although there is no admin_token entry in any of the keystone tables. Any idea what is going wrong here? Thanks, Xin ___ 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] keystone initialization problem
Hello, I newly install keystone on the RHEL6 machine, but it is not working. The following command fails: $ keystone --token admin_token string from keystone.conf --endpoint http://internet_ip of the controller node:35357/v2.0 tenant-create --name openstackDemo --description Default Tenant --enabled true Unable to communicate with identity service: (403, 'Forbidden'). (HTTP 400) There is no relevant log in the keystone.log file. Here is the instruction I follow: http://docs.openstack.org/essex/openstack-compute/install/yum/content/setting-up-tenants-users-and-roles.html This is done on the controller node itself. I can telnet to internet_ip of the controller node:35357. I can also log into mysql DB as keystone user, although there is no admin_token entry in any of the keystone tables. Any idea what is going wrong here? Thanks, Xin smime.p7s Description: S/MIME Cryptographic 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] metadata service problem
Hello, How can I check the value of $my_ip? I notice that in the arp table on the instance, the entry for ip 169.254.169.254 has a wrong mac address, which I don't see existent on both the controller node and the worker node. After I change the entry for ip 169.254.169.254 to map to the real mac address of the controller host(metadata host as well), the curl command works. But, I don't know why the initial wrong mac address gets entered into the arp table in the first place? Thanks, Xin On 8/10/2012 3:47 AM, tacy lee wrote: Suggest check iptables-save output,Metadata_host default set to $my_ip. if you often switch network,your $my_ip maybe set wrong On Fri, Aug 10, 2012 at 10:31 AM, Xin Zhao xz...@bnl.gov mailto:xz...@bnl.gov wrote: Hello, In my essex install on RHEL6, there is a problem with the metadata service. The metadata service works for instances running on the controller node, where the nova-api(metadata service) is running. But for the other worker nodes, the metadata service is intermittent, ie. the instances sometimes can get its metadata, sometime it fails with errors like: $ curl -v http://169.254.169.254:8775/ * About to connect() to 169.254.169.254 port 8775 (#0) * Trying 169.254.169.254... Connection timed out * couldn't connect to host * Closing connection #0 curl: (7) couldn't connect to host Any idea where should I start investigating this? Thanks, Xin ___ 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 smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] metadata service problem
Hello, In my essex install on RHEL6, there is a problem with the metadata service. The metadata service works for instances running on the controller node, where the nova-api(metadata service) is running. But for the other worker nodes, the metadata service is intermittent, ie. the instances sometimes can get its metadata, sometime it fails with errors like: $ curl -v http://169.254.169.254:8775/ * About to connect() to 169.254.169.254 port 8775 (#0) * Trying 169.254.169.254... Connection timed out * couldn't connect to host * Closing connection #0 curl: (7) couldn't connect to host Any idea where should I start investigating this? Thanks, Xin ___ 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 access error from remote client
Hello, I have an Essex install of openstack on RHEL6. The controller node has all openstack services running, and there are several separate compute nodes. Now I have a problem using glance. If I issue glance index --host=XXX --port=9292 on the controller node, it works fine. If I issue the same command from a remote client node, where I have all the relevant openstack rpms installed, it fails with the following error message: Failed to show index. Got error: There was an error connecting to a server Details: [Errno 111] Connection refused On the same client node, I can query images and instances using euca2ools, they just work fine. And I also can telnet to the 9292 port on the controller node from the client side. In both cases, I use the credentials of the admin account. Any wisdom on what could cause this problem? Thanks, Xin smime.p7s Description: S/MIME Cryptographic 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] glance access error from remote client
Hi Jay, I thought about that, and changed the client environment variables to use the FQDN of the controller, I even restarted glance/swift services with the controller FQDN in the config files (127.0.0.1/localhost are the original values). I compared the OS_XXX env between the controller node and remote client, they are the same. What's interesting is that, even if I give a wrong hostname or port number in the command glance index --host=XXX --port=XXX, it still works if run on the controller node. And, strace shows, from the remote client node, that 127.0.0.1:9292 is connected instead of the hostname:9292 specified in the command line. So how can I make sure the client does talk to THE hostname, instead of 127.0.0.1 ? Thanks, Xin On 6/27/2012 11:40 AM, Jay Pipes wrote: On 06/27/2012 10:04 AM, Xin Zhao wrote: Hello, I have an Essex install of openstack on RHEL6. The controller node has all openstack services running, and there are several separate compute nodes. Now I have a problem using glance. If I issue glance index --host=XXX --port=9292 on the controller node, it works fine. If I issue the same command from a remote client node, where I have all the relevant openstack rpms installed, it fails with the following error message: Failed to show index. Got error: There was an error connecting to a server Details: [Errno 111] Connection refused This usually because the glance CLI tool is trying to connect to the localhost (which obviously isn't running the Glance API server). Have you looked at the difference between your OS_XXX environment variables between the controller node and the remote client node? It may be that when you are doing a glance index --host=XXX --port=9292 on the controller node that the glance CLI tool is actually connecting to localhost/127.0.0.1, but I'm not completely sure.. Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] diablo release rpms
Hello, I have a diablo testbed, for which I have to add more compute nodes. We use RHEL6. But the current EL6 repo looks already upgraded to Essex release. So I wonder if there is any way I can get back to the diablo rpms? Thanks, Xin ___ 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] [Doc] Documentation releases
Hi Anne, That sounds great! I would like to try out Essex on RHEL6, and wondering if the EL6 repo and doc are ready for that? Thanks, Xin On 5/2/2012 11:16 AM, Anne Gentle wrote: Hi all - I've written down the steps I've discovered while doing the Essex branch for the docs: http://wiki.openstack.org/Documentation/Release Please review and let me know if you have questions. Thanks to the CI team (James Blair rocks!) for the assistance in creating parameters so that this process is even easier. After today, we should have a stable/essex branch for the openstack-manuals repository, and the docs.openstack.org http://docs.openstack.org home page will point to Essex documentation plus trunk, and the /essex pages will have Disqus comments opened. Also, the /bexar and /cactus areas will redirect to /trunk. Thanks, Anne ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME Cryptographic Signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] question about configuring FlatDHCPManager
Hello, I run nova compute (diablo) on RHEL6. Following the instruction, I configured the network as following, and it works: $nova-manage network create ostester 10.0.0.0/24 1 256 --bridge=br0 --bridge_interface=em1 Now I want to change it to use a new fixed_range, like 10.1.1.0/24, so I delete the network, then redefine it following the same command format. But it doesn't work, the instance starts still with the 10.0.0.X ip, and of course, network doesn't work in the instances. What do I miss here? Thanks, Xin ___ 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] question about configuring FlatDHCPManager
OK, thanks for the info. BTW, what's the nova-manage project scrub projectname do? Does it have the same effect as the manual steps you just mentioned do? Xin On 4/19/2012 1:01 PM, Vishvananda Ishaya wrote: unfortunately there is a bug where deleting a network does not delete associated fixed ips: https://bugs.launchpad.net/nova/+bug/754900 The fix has landed in trunk and is proposed for backport into stable/essex https://review.openstack.org/6664 To work around this issue, you will have to delete the fixed ips manually from the database or drop and recreate the database. Vish On Apr 19, 2012, at 9:00 AM, Xin Zhao wrote: Hello, I run nova compute (diablo) on RHEL6. Following the instruction, I configured the network as following, and it works: $nova-manage network create ostester 10.0.0.0/24 1 256 --bridge=br0 --bridge_interface=em1 Now I want to change it to use a new fixed_range, like 10.1.1.0/24, so I delete the network, then redefine it following the same command format. But it doesn't work, the instance starts still with the 10.0.0.X ip, and of course, network doesn't work in the instances. What do I miss here? Thanks, Xin ___ 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] control user quota
Hello, I try to assign quota to individual users, to control how many instances each user can run concurrently. But I don't see a doc describing how to do that. I use diablo release. Any help or doc pointer will be greatly appreciated. Xin ___ 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] question about keystone and dashboard on RHEL6
Hello, I am new to OpenStack and trying to install the diablo release on a RHEL6 cluster. I follow instructions here: http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova The instruction doesn't mention how to install and configure Keystone and dashboard services, I wonder: 1) are these two services available for RHEL6, in diablo release? 2) do I need to go to the latest Essex release, and where the instructions is? Thanks, Xin ___ 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] question about keystone and dashboard on RHEL6
On 4/2/2012 6:35 PM, Russell Bryant wrote: On 04/02/2012 03:09 PM, Xin Zhao wrote: Hello, I am new to OpenStack and trying to install the diablo release on a RHEL6 cluster. I follow instructions here: http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova The instruction doesn't mention how to install and configure Keystone and dashboard services, I wonder: 1) are these two services available for RHEL6, in diablo release? 2) do I need to go to the latest Essex release, and where the instructions is? The dashboard, horizon, is not included with the Diablo packages that you find in EPEL6 right now. When we update EPEL6 to Essex, which should be within the next few weeks, horizon will be included as well. How about keystone, the instructions here (http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova) doesn't mention how to install and configure keystone, although it tells how to clean up keystone, which makes me think there is something missing in the earlier sections of this instruction. Xin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
