Re: [Openstack] [Netstack] Openstack Folsom - 3 Installation
inline On Thu, Aug 23, 2012 at 1:34 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- Any inputs for understanding and resolving the issue... Kindly help me in this regard. -- Trinath On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. *Keystone $* python setup.py build *Keystone $* python setup.py install. Will these two steps install the respective component and all its necessary components. Probably only need sudo python setup.py install With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Yes, this is just a different method of installation. Kindly guide me on this... Thanking you all. -- Regards, -- Trinath Somanchi, +91 9866 235 130 -- Regards, -- Trinath Somanchi, +91 9866 235 130 -- Mailing list: https://launchpad.net/~netstack Post to : netst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack 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] [Netstack] Openstack Folsom - 3 Installation
Hi - Rather than using this installation for every different package can I use devstack's stack.sh script to install the Openstack latest milestone release? Can any one comment on this. Thanking you, - Trinath On Thu, Aug 23, 2012 at 11:45 AM, Aaron Rosen aro...@nicira.com wrote: inline On Thu, Aug 23, 2012 at 1:34 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- Any inputs for understanding and resolving the issue... Kindly help me in this regard. -- Trinath On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. *Keystone $* python setup.py build *Keystone $* python setup.py install. Will these two steps install the respective component and all its necessary components. Probably only need sudo python setup.py install With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Yes, this is just a different method of installation. Kindly guide me on this... Thanking you all. -- Regards, -- Trinath Somanchi, +91 9866 235 130 -- Regards, -- Trinath Somanchi, +91 9866 235 130 -- Mailing list: https://launchpad.net/~netstack Post to : netst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp -- 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] [Netstack] Openstack Folsom - 3 Installation
On 08/23/2012 10:16 AM, Trinath Somanchi wrote: Hi - Rather than using this installation for every different package can I use devstack's stack.sh script to install the Openstack latest milestone release? devstack does not use the installation packages. This uses the git repositories. By looking at devstack you can see how to invoke and run the various openstack services. Can any one comment on this. Thanking you, - Trinath On Thu, Aug 23, 2012 at 11:45 AM, Aaron Rosen aro...@nicira.com mailto:aro...@nicira.com wrote: inline On Thu, Aug 23, 2012 at 1:34 AM, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi- Any inputs for understanding and resolving the issue... Kindly help me in this regard. -- Trinath On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. *Keystone $* python setup.py build *Keystone $* python setup.py install. Will these two steps install the respective component and all its necessary components. Probably only need sudo python setup.py install With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Yes, this is just a different method of installation. Kindly guide me on this... Thanking you all. -- Regards, -- Trinath Somanchi, +91 9866 235 130 tel:%2B91%209866%20235%20130 -- Regards, -- Trinath Somanchi, +91 9866 235 130 tel:%2B91%209866%20235%20130 -- Mailing list: https://launchpad.net/~netstack https://launchpad.net/%7Enetstack Post to : netst...@lists.launchpad.net mailto:netst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack https://launchpad.net/%7Enetstack More help : https://help.launchpad.net/ListHelp -- 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 ___ 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 - 3 Installation
Hi Trinath, snip On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi trinath.soman...@gmail.commailto:trinath.soman...@gmail.com wrote: Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. Keystone $ python setup.py build Keystone $ python setup.py install. Will these two steps install the respective component and all its necessary components. With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Kindly guide me on this... /snip You are trying to install Folsom from the development version and that is why you are doing source code based installation. I am sure it comes with a README file which explains details about the source file. Now when you are talking about apt-get best install, it means you are trying to download the package which is bundled by one of the Linux distribution providers repository. Now here is the thing, since Folsom is still in development phase thats why the package based installation is still in process of baking/bake, so folks from Ubuntu are best to answer your question when it will be available. Lastly source based install is not suggested for Production Environment. I will hope this solves all your confusion and questions. Thanks, Atul Jha http://www.csscorp.com/common/email-disclaimer.php ___ 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 service is not responding while installing thorough DevStack !!
Guys, I am installing DevStack script. I stucked here. + screen -S stack -p key -X stuff 'cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug echo 'Waiting for keystone to start...' Waiting for keystone to start... + timeout 60 sh -c 'while ! http_proxy= curl -s http://192.168.1.100:5000/v2.0/ /dev/null; do sleep 1; done' + echo 'keystone did not start' keystone did not start By looking at message, it is sure that KeyStone service has not been responding. I installed it manually but no luck still seen the same issue. Any suggestion or pointers for this? Thanks, Hitesh Wadekar ___ 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 - 3 Installation
As I recall localrc had a setting in the past for picking releases to install. Not sure what the status of that is. On Thu, Aug 23, 2012 at 12:45 AM, Atul Jha atul@csscorp.com wrote: Hi Trinath, snip On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi trinath.soman...@gmail.commailto:trinath.soman...@gmail.com wrote: Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. Keystone $ python setup.py build Keystone $ python setup.py install. Will these two steps install the respective component and all its necessary components. With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Kindly guide me on this... /snip You are trying to install Folsom from the development version and that is why you are doing source code based installation. I am sure it comes with a README file which explains details about the source file. Now when you are talking about apt-get best install, it means you are trying to download the package which is bundled by one of the Linux distribution providers repository. Now here is the thing, since Folsom is still in development phase thats why the package based installation is still in process of baking/bake, so folks from Ubuntu are best to answer your question when it will be available. Lastly source based install is not suggested for Production Environment. I will hope this solves all your confusion and questions. Thanks, Atul Jha http://www.csscorp.com/common/email-disclaimer.php ___ 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 - 3 Installation
Hi- I'm currently testing the capabilities of Openstack. Not going for any production deployment. So want to go with the folsom-3 milestone release. In the ReadMe file, for example, Nova-2012.2, no Installation information is given. The same file can be found here... https://github.com/openstack/nova I'm unable to install Folsom-3 Mile stone of the Openstack. Finally. Any Guidance would help me a lot... -- Trinath On Thu, Aug 23, 2012 at 1:49 PM, Matt Joyce matt.jo...@cloudscaling.comwrote: As I recall localrc had a setting in the past for picking releases to install. Not sure what the status of that is. On Thu, Aug 23, 2012 at 12:45 AM, Atul Jha atul@csscorp.com wrote: Hi Trinath, snip On Wed, Aug 22, 2012 at 4:43 PM, Trinath Somanchi trinath.soman...@gmail.commailto:trinath.soman...@gmail.com wrote: Hi All- I'm installing Openstack Components of Folsom-3 milestone from the Tar files available from launchpad. Can any one guide me on the installation of the these components like the Essex component installation and configuration. I'm upto this level of Installation. For instance, Keystone component, I have untar the file and executed the following commands. Keystone $ python setup.py build Keystone $ python setup.py install. Will these two steps install the respective component and all its necessary components. With this type of Install can I use the Openstack components as I use them in the 'apt-get' based Essex installation. Kindly guide me on this... /snip You are trying to install Folsom from the development version and that is why you are doing source code based installation. I am sure it comes with a README file which explains details about the source file. Now when you are talking about apt-get best install, it means you are trying to download the package which is bundled by one of the Linux distribution providers repository. Now here is the thing, since Folsom is still in development phase thats why the package based installation is still in process of baking/bake, so folks from Ubuntu are best to answer your question when it will be available. Lastly source based install is not suggested for Production Environment. I will hope this solves all your confusion and questions. Thanks, Atul Jha http://www.csscorp.com/common/email-disclaimer.php ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 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] KeyStone service is not responding while installing thorough DevStack !!
Hi, That may means your internet connection is too slow and it's still downloading and didn't finish yet, at least thats what I have experienced in the past. Maybe your HTTP request sometimes get malformed and your download isn't continuing then you may need to just try again. Are you behind a firewall like me(Chinese Firewall)? Maybe the resource is being blocked? You may just have to wait longer or try a VPN to download everything. Sam On Thu, Aug 23, 2012 at 4:39 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- Me too experiencing the same. I was struck at this point. Downloading/unpacking prettytable (from -r python_keystoneclient.egg.info/requires.txt (line 2)) It was just struck here... and not moving forward. Can any one guide me troubleshooting the issue. - Trinath On Thu, Aug 23, 2012 at 1:45 PM, hitesh wadekar hitesh.wade...@gmail.comwrote: Guys, I am installing DevStack script. I stucked here. + screen -S stack -p key -X stuff 'cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug echo 'Waiting for keystone to start...' Waiting for keystone to start... + timeout 60 sh -c 'while ! http_proxy= curl -s http://192.168.1.100:5000/v2.0/ /dev/null; do sleep 1; done' + echo 'keystone did not start' keystone did not start By looking at message, it is sure that KeyStone service has not been responding. I installed it manually but no luck still seen the same issue. Any suggestion or pointers for this? Thanks, Hitesh Wadekar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 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 ___ 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 - 3 Installation
Installing the milestone release likely doesn't make as much sense as getting the latest using devstack at this point. Have you had difficulties installing http://devstack.org/ ? Best regards, Lloyd ___ 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] [Netstack] Openstack Folsom - 3 Installation
Trinath, snip Hi - Rather than using this installation for every different package can I use devstack's stack.sh script to install the Openstack latest milestone release? Can any one comment on this. /snip Yes you can. Thanks, Atul Jha http://www.csscorp.com/common/email-disclaimer.php ___ 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 service is not responding while installing thorough DevStack !!
What exactly happens when you try to start it directly? cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug What happens when you curl http://localhost:5000/v2.0/ on that machine? And with port 35357? -Dolph On Thu, Aug 23, 2012 at 3:15 AM, hitesh wadekar hitesh.wade...@gmail.comwrote: Guys, I am installing DevStack script. I stucked here. + screen -S stack -p key -X stuff 'cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug echo 'Waiting for keystone to start...' Waiting for keystone to start... + timeout 60 sh -c 'while ! http_proxy= curl -s http://192.168.1.100:5000/v2.0/ /dev/null; do sleep 1; done' + echo 'keystone did not start' keystone did not start By looking at message, it is sure that KeyStone service has not been responding. I installed it manually but no luck still seen the same issue. Any suggestion or pointers for this? Thanks, Hitesh Wadekar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- -Dolph ___ 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 service is not responding while installing thorough DevStack !!
That potentially a different issue; likely a pypi mirror not responding? You can download/install prettytable directly if you need to: http://pypi.python.org/pypi/PrettyTable/ -Dolph On Thu, Aug 23, 2012 at 3:39 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- Me too experiencing the same. I was struck at this point. Downloading/unpacking prettytable (from -r python_keystoneclient.egg.info/requires.txt (line 2)) It was just struck here... and not moving forward. Can any one guide me troubleshooting the issue. - Trinath On Thu, Aug 23, 2012 at 1:45 PM, hitesh wadekar hitesh.wade...@gmail.comwrote: Guys, I am installing DevStack script. I stucked here. + screen -S stack -p key -X stuff 'cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug echo 'Waiting for keystone to start...' Waiting for keystone to start... + timeout 60 sh -c 'while ! http_proxy= curl -s http://192.168.1.100:5000/v2.0/ /dev/null; do sleep 1; done' + echo 'keystone did not start' keystone did not start By looking at message, it is sure that KeyStone service has not been responding. I installed it manually but no luck still seen the same issue. Any suggestion or pointers for this? Thanks, Hitesh Wadekar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 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 -- -Dolph ___ 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] Default rules for the 'default' security group
Hi all, Could I ask how to set the default rules for the 'default' security group for all the users in openstack? Currently, the 'default' security group has no rule by default, thus newly created instances could only be accessed by instances from the same group. Is there any method to set default rules(such as ssh or icmp) for the 'default' security group for all users in openstack, so that I don't have to remind the new users to modify security group setting the fist time they logged into openstack and create instances? I have ever tried HP could which is built on openstack, they permit ssh or ping to the instances in the 'default' security group. Best Regards. Yufang ___ 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] Keyring support in openstack
On Sat, 28 Jul 2012, Bhuvaneswaran A wrote: Team, As per patch https://review.openstack.org/#/c/9497/ we are adding keyring support for openstack client. If password is not specified in command line or environment variable, the user is prompted to enter password. During this time, the password is stored in keyring. During next time, the password is read from keyring, instead of prompt. It is true, if password is not specified in command line or environment variable. This behavior is documented in this wiki page: http://wiki.openstack.org/KeyringSupport I haven' tried this specifically for the openstack client, but when this went into nova, it annoyed me, as I started having to give a password on remote systems every time. For the devstack instances I was working on, I honestly couldn't care less about security, and wanted to not be bothered. For others looking for something similar, here is the 'keyringrc.cfg' file that you need. Put it either in ~/ or in the current working directory (strange). --- keyringrc.cfg --- # This is an example keyringrc.cfg file that allows python-keyring # to use the UncryptedFileKeyring. # See /usr/share/doc/python-keyring/README.gz for more info. # Note, this works, but I see the following significant issues with it: # * python-keyring goes looking for 'keyringrc.cfg' in the current working # directory and user's home directory. Note, specifically it does *not* # look for ~/.keyringrc.cfg (which would be more common) # * no environment variable can affect the path read for ~/keyringrc.cfg # this means you're stuck with one of the following options if you # wanted to somehow maintain that one app (that you do not care about) # use UncryptedFileKeyring while all other apps use a different: #* keep 'HOME' environment variable set when that app is used to # something other than your home. and maintain $HOME/keyringrc.cfg #* keep the current working directory when that app is used to a given # working directory. # I think it'd be much nicer if I could affect this with # 'PYTHON_KEYRING_CFG' # or if the config file had some apt specific stuff. # * UncryptedFileKeyring writes its data to a file named keyring_pass.cfg # in the home directory, and does not pay attention to 'keyring-path' # * UncryptedFileKeyring laughably creates keyring_pass.cfg its password # file with default umask meaning in most cases it is world readable # I've opened bug http://pad.lv/1023433 to track these. [backend] default-keyring=keyring.backend.UncryptedFileKeyring keyring-path=/home/ubuntu/xxx # this is ignored ___ 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] inter-tenant and VM-to-bare-metal communication policies/restrictions.
On Wed, Aug 15, 2012 at 4:16 AM, Lorin Hochstein lo...@nimbisservices.comwrote: On Jul 5, 2012, at 11:47 AM, Christian Parpart tra...@gmail.com wrote: Hi all, I am running multiple compute nodes and a single nova-network node, that is to act as a central gateway for the tenant's VMs. However, since this nova-network node (of course) knows all routes, every VM of any tenant can talk to each other, including to the physical nodes, which I highly disagree with and would like to restrict that. :-) If you add this to nova.conf: allow_same_net_traffic=false It should prevent the VMs from communicating with each other. From http://docs.openstack.org/essex/openstack-compute/admin/content/compute-options-reference.html#d6e3133 Hey Lorin, according to this rather short documentation for that flag, it is unfortunately very unclear what they meant with from same network - I hope to misread that line :-) That is, it sounds like it does prevent communication with ANY of the other VMs, but I just want to disallow communication from one tenant to another. Like, having a production tenant and a staging tenant, they should not be able to talk to each other but a VM from the production tenant should be able to talk to another VM within the same tenant. It might be helpful, if one may want to find some more clear words to this flag within the flag reference :-) I would also like to know on what physical hosts I need this flag to be applied, too. I mean, is it just the nova-network node(s) or all compute nodes, that this flag takes affect? Many thanks in advance, Christian Parpart. ___ 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] Process for targetting blueprint for RC1
Hi, I have submitted implementation of https://blueprints.launchpad.net/openstack-common/+spec/http-notification-driver blueprint (review request https://review.openstack.org/#/c/11016/) and it is currently under review. I intend this implementation to get released in RC1. Can someone please let me know the process to propose it for getting added in RC1. Thanks Regards, Unmesh Gurjar | Lead Engineer | NTT DATA Global Technology Services Private Limited | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 | unmesh.gur...@nttdata.commailto:unmesh.gur...@nttdata.com | Learn more at nttdata.com/americas __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ 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 service is not responding while installing thorough DevStack !!
Trinath - it sounds like PyPi was slow and/or hung. That happens upon occasion (and has caused much grief). I'm guessing by the time I'm responding to this, it's cleared up for you. Are you able to run through devstack now without issue? - joe On Aug 23, 2012, at 1:39 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- Me too experiencing the same. I was struck at this point. Downloading/unpacking prettytable (from -r python_keystoneclient.egg.info/requires.txt (line 2)) It was just struck here... and not moving forward. Can any one guide me troubleshooting the issue. - 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] Default rules for the 'default' security group
I'm very interested in this, we run essex and have a very bad workaround for this currently, but it would be great to be able to do this (set default rules for the default security group). Boris De : openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net [mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net] De la part de Yufang Zhang Envoyé : 23 août 2012 08:43 À : openstack@lists.launchpad.net Objet : [Openstack] Default rules for the 'default' security group Hi all, Could I ask how to set the default rules for the 'default' security group for all the users in openstack? Currently, the 'default' security group has no rule by default, thus newly created instances could only be accessed by instances from the same group. Is there any method to set default rules(such as ssh or icmp) for the 'default' security group for all users in openstack, so that I don't have to remind the new users to modify security group setting the fist time they logged into openstack and create instances? I have ever tried HP could which is built on openstack, they permit ssh or ping to the instances in the 'default' security group. Best Regards. Yufang ___ 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 service is not responding while installing thorough DevStack !!
Thanks Dolph and Joseph for a quick answers. I tried through command though,.. *cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/kestone/logging.conf -d --debug *The output of this - * * Traceback (most recent call last): File /opt/stack/keystone/bin/keystone-all, line 83, in module config.setup_logging(CONF) File /opt/stack/keystone/keystone/config.py, line 45, in setup_logging 'config file: %s' % conf.log_config) RuntimeError: Unable to locate specified logging config file: /etc/kestone/logging.conf It seems some problem with logging.conf file.. any idea? location issue?. Thanks, Hitesh On Thu, Aug 23, 2012 at 5:21 PM, Dolph Mathews dolph.math...@gmail.comwrote: What exactly happens when you try to start it directly? cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug What happens when you curl http://localhost:5000/v2.0/ on that machine? And with port 35357? -Dolph On Thu, Aug 23, 2012 at 3:15 AM, hitesh wadekar hitesh.wade...@gmail.comwrote: Guys, I am installing DevStack script. I stucked here. + screen -S stack -p key -X stuff 'cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug echo 'Waiting for keystone to start...' Waiting for keystone to start... + timeout 60 sh -c 'while ! http_proxy= curl -s http://192.168.1.100:5000/v2.0/ /dev/null; do sleep 1; done' + echo 'keystone did not start' keystone did not start By looking at message, it is sure that KeyStone service has not been responding. I installed it manually but no luck still seen the same issue. Any suggestion or pointers for this? Thanks, Hitesh Wadekar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- -Dolph ___ 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 service is not responding while installing thorough DevStack !!
One of two things - either the file doesn't exist in that location, or the process running it doesn't have permissions to see the file. Does the file exist at /etc/keystone/logging.conf? Devstack tries to set that up in the right location in stack.sh at line 2038 - did that fail when you ran it? -joe On Aug 23, 2012, at 8:28 AM, hitesh wadekar hitesh.wade...@gmail.com wrote: Thanks Dolph and Joseph for a quick answers. I tried through command though,.. cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/kestone/logging.conf -d --debug The output of this - Traceback (most recent call last): File /opt/stack/keystone/bin/keystone-all, line 83, in module config.setup_logging(CONF) File /opt/stack/keystone/keystone/config.py, line 45, in setup_logging 'config file: %s' % conf.log_config) RuntimeError: Unable to locate specified logging config file: /etc/kestone/logging.conf It seems some problem with logging.conf file.. any idea? location issue?. Thanks, Hitesh On Thu, Aug 23, 2012 at 5:21 PM, Dolph Mathews dolph.math...@gmail.com wrote: What exactly happens when you try to start it directly? cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug What happens when you curl http://localhost:5000/v2.0/ on that machine? And with port 35357? -Dolph On Thu, Aug 23, 2012 at 3:15 AM, hitesh wadekar hitesh.wade...@gmail.com wrote: Guys, I am installing DevStack script. I stucked here. + screen -S stack -p key -X stuff 'cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/ke'stone/logging.conf -d --debug echo 'Waiting for keystone to start...' Waiting for keystone to start... + timeout 60 sh -c 'while ! http_proxy= curl -s http://192.168.1.100:5000/v2.0/ /dev/null; do sleep 1; done' + echo 'keystone did not start' keystone did not start By looking at message, it is sure that KeyStone service has not been responding. I installed it manually but no luck still seen the same issue. Any suggestion or pointers for this? Thanks, Hitesh Wadekar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- -Dolph ___ 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] VM can't ping self floating IP after a snapshot is taken
Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.comwrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: I ran into some similar issues with the _*enable*_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. ** ** Just thought I’d share my similar pain. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 19, 2012 11:50 AM *To:* Brian Haley *Cc:* openstack *Subject:* Re: [Openstack] VM can't ping self floating IP after a snapshot is taken ** ** Thank you for your support. ** ** I checked the file nova/virt/libvirt/connection.py, the sentence self._enable_hairpin(instance) is already added to the function _hard_reboot(). It looks like there are some difference between taking snapshot and reboot instance. I tried to figure out how to fix this bug but failed. * *** ** ** It will be much appreciated if anyone can give some hints. ** ** Thanks, Sam ** ** On Thu, Jul 19, 2012 at 8:37 AM, Brian Haley brian.ha...@hp.com wrote: On 07/17/2012 05:56 PM, Sam Su wrote: Hi, Just This always happens in Essex release. After I take a snapshot of my VM ( I tried Ubuntu 12.04 or CentOS 5.8), VM can't ping its self floating IP; before I take a snapshot though, VM can ping its self floating IP. This looks closely related to https://bugs.launchpad.net/nova/+bug/933640, but still a little different. In 933640, it sounds like VM can't ping its self floating IP regardless whether we take a snapshot or not. Any suggestion to make an easy fix? And what is the root cause of the problem? It might be because there's a missing _enable_hairpin() call in the reboot() function. Try something like this... nova/virt/libvirt/connection.py, _hard_reboot(): self._create_new_domain(xml) +self._enable_hairpin(instance) self.firewall_driver.apply_instance_filter(instance, network_info) At least that's what I remember doing myself recently when testing after a reboot, don't know about snapshot. Folsom has changed enough that something different would need to be done there. -Brian ** ** ___ 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] Metering meeting agenda for Thursday at 16:00 UTC (Aug 23rd, 2012)
On 08/23/2012 05:18 AM, Nick Barcet wrote: Hi, The metering project team holds a meeting in #openstack-meeting, Thursdays at 1600 UTC http://www.timeanddate.com/worldclock/fixedtime.html?hour=16min=0sec=0. Everyone is welcome. Agenda: http://wiki.openstack.org/Meetings/MeteringAgenda * Review last week's actions - jaypipes to create ceilometer cookbook - nijaba to write description of component responsibility - dhellmann and nijaba to work on sessions for summit via email - dhellmann to ask jtrans about interest in reviewer status - nijaba to give core reviewer rights to gmb * Open discussion If you are not able to attend or have additional topic you would like to cover, please update the agenda on the wiki. The meeting took place, here are the minutes: == #openstack-meeting: Ceilometer == Meeting started by nijaba at 16:00:33 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-08-23-16.00.log.html . Meeting summary --- * LINK: http://wiki.openstack.org/Meetings/MeteringAgenda (nijaba, 16:00:49) * actions from previous meeting (nijaba, 16:01:55) * jaypipes to create ceilometer cookbook (nijaba, 16:02:13) * ACTION: jaypipes to create ceilometer cookbook (nijaba, 16:02:41) * nijaba to write description of component responsibility (nijaba, 16:03:44) * ACTION: nijaba to link schema in the doc (nijaba, 16:05:44) * LINK: https://docs.google.com/drawings/pub?id=1_cIFir6HS6jSkPw7chrmyu8DGE2ZgXk79Kbj8nw-Hqow=960h=720 (nijaba, 16:06:24) * dhellmann and nijaba to work on sessions for summit via email (nijaba, 16:06:56) * ACTION: dhellmann and nijaba to work on sessions for summit via email (nijaba, 16:07:32) * dhellmann to ask jtrans about interest in reviewer status (nijaba, 16:08:01) * nijaba to give core reviewer rights to gmb (nijaba, 16:08:52) * Open Discussion (nijaba, 16:11:33) * ACTION: nijaba to start a thread on meeting time (nijaba, 16:34:26) Meeting ended at 16:35:40 UTC. Action items, by person --- * dhellmann * dhellmann and nijaba to work on sessions for summit via email * nijaba * nijaba to link schema in the doc * dhellmann and nijaba to work on sessions for summit via email * nijaba to start a thread on meeting time People present (lines said) --- * nijaba (68) * dhellmann (53) * openstack (4) * gmb (3) * heckj (1) * _surya_ (1) -- Nick Barcet nick.bar...@canonical.com aka: nijaba, nicolas signature.asc Description: OpenPGP digital 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] Cannot create snapshots of instances running not on the controller
Hi all, i've a controller which is running all service and a secondary controller which is un multi_host so it's running compute network and api-metadata. From the dashboard i can successfully create snapshots of instances running on the controller but when i try to create a snapshot of an instance on a compute node i get in its logs: == /var/log/nova/nova-compute.log == 2012-08-23 19:08:14 ERROR nova.rpc.amqp [req-66389a04-b071-4641-949b-3df04da85d08 a63f5293c5454a979bddff1415a216f6 e8c3367ff91d44b1ab1b14eb63f48bf7] Exception during message handling 2012-08-23 19:08:14 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 253, in _process_data 2012-08-23 19:08:14 TRACE nova.rpc.amqp rval = node_func(context=ctxt, **node_args) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return f(*args, **kw) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 183, in decorated_function 2012-08-23 19:08:14 TRACE nova.rpc.amqp sys.exc_info()) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ 2012-08-23 19:08:14 TRACE nova.rpc.amqp self.gen.next() 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 177, in decorated_function 2012-08-23 19:08:14 TRACE nova.rpc.amqp return function(self, context, instance_uuid, *args, **kwargs) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 952, in snapshot_instance 2012-08-23 19:08:14 TRACE nova.rpc.amqp self.driver.snapshot(context, instance_ref, image_id) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return f(*args, **kw) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 714, in snapshot 2012-08-23 19:08:14 TRACE nova.rpc.amqp image_file) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/image/glance.py, line 306, in update 2012-08-23 19:08:14 TRACE nova.rpc.amqp _reraise_translated_image_exception(image_id) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/image/glance.py, line 304, in update 2012-08-23 19:08:14 TRACE nova.rpc.amqp image_meta = client.update_image(image_id, image_meta, data) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/client.py, line 195, in update_image 2012-08-23 19:08:14 TRACE nova.rpc.amqp res = self.do_request(PUT, /images/%s % image_id, body, headers) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 58, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return func(self, *args, **kwargs) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 420, in do_request 2012-08-23 19:08:14 TRACE nova.rpc.amqp headers=headers) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 75, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return func(self, method, url, body, headers) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 547, in _do_request 2012-08-23 19:08:14 TRACE nova.rpc.amqp raise exception.Invalid(res.read()) 2012-08-23 19:08:14 TRACE nova.rpc.amqp Invalid: Data supplied was not valid. 2012-08-23 19:08:14 TRACE nova.rpc.amqp Details: 400 Bad Request 2012-08-23 19:08:14 TRACE nova.rpc.amqp 2012-08-23 19:08:14 TRACE nova.rpc.amqp The server could not comply with the request since it is either malformed or otherwise incorrect. 2012-08-23 19:08:14 TRACE nova.rpc.amqp 2012-08-23 19:08:14 TRACE nova.rpc.amqp Failed to update image metadata. Got error: Data supplied was not valid. Details: 400 Bad Request The server could not comply with the request since it is either malformed or otherwise incorrect. Failed to update image metadata. Got error: Data supplied was not valid. Details: Invalid container format 'None' for image. 2012-08-23 19:08:14 TRACE nova.rpc.amqp any idea? Using nova create-image works but it creates a new image, not a snapshot (as the dashboard shows) Best Regards Alessandro ___ 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] Default rules for the 'default' security group
I traced this through the code at one point looking for the same thing. As it stands, right now there is *not* a mechanism for customizing the default security group's rules. It's created programmatically the first time the rules for a project are retrieved with no hook to add or change its characteristics. I'd love to see this be possible, but it's definitely a feature request. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Boris-Michel Deschenes Sent: Thursday, August 23, 2012 7:59 AM To: Yufang Zhang; openstack@lists.launchpad.net Subject: Re: [Openstack] Default rules for the 'default' security group I'm very interested in this, we run essex and have a very bad workaround for this currently, but it would be great to be able to do this (set default rules for the default security group). Boris De : openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.netmailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net [mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net]mailto:[mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net] De la part de Yufang Zhang Envoyé : 23 août 2012 08:43 À : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Objet : [Openstack] Default rules for the 'default' security group Hi all, Could I ask how to set the default rules for the 'default' security group for all the users in openstack? Currently, the 'default' security group has no rule by default, thus newly created instances could only be accessed by instances from the same group. Is there any method to set default rules(such as ssh or icmp) for the 'default' security group for all users in openstack, so that I don't have to remind the new users to modify security group setting the fist time they logged into openstack and create instances? I have ever tried HP could which is built on openstack, they permit ssh or ping to the instances in the 'default' security group. Best Regards. Yufang ___ 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] Cannot create snapshots of instances running not on the controller
looks like the compute node has a bad setting for glance_api_servers on the second node. because glance_api_servers defaults to $glance_host:$glance_port, you should be able to fix it by setting: glance_host = ip where glance is running in your nova.conf on the second node. Vish On Aug 23, 2012, at 10:15 AM, Alessandro Tagliapietra tagliapietra.alessan...@gmail.com wrote: Hi all, i've a controller which is running all service and a secondary controller which is un multi_host so it's running compute network and api-metadata. From the dashboard i can successfully create snapshots of instances running on the controller but when i try to create a snapshot of an instance on a compute node i get in its logs: == /var/log/nova/nova-compute.log == 2012-08-23 19:08:14 ERROR nova.rpc.amqp [req-66389a04-b071-4641-949b-3df04da85d08 a63f5293c5454a979bddff1415a216f6 e8c3367ff91d44b1ab1b14eb63f48bf7] Exception during message handling 2012-08-23 19:08:14 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 253, in _process_data 2012-08-23 19:08:14 TRACE nova.rpc.amqp rval = node_func(context=ctxt, **node_args) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return f(*args, **kw) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 183, in decorated_function 2012-08-23 19:08:14 TRACE nova.rpc.amqp sys.exc_info()) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ 2012-08-23 19:08:14 TRACE nova.rpc.amqp self.gen.next() 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 177, in decorated_function 2012-08-23 19:08:14 TRACE nova.rpc.amqp return function(self, context, instance_uuid, *args, **kwargs) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 952, in snapshot_instance 2012-08-23 19:08:14 TRACE nova.rpc.amqp self.driver.snapshot(context, instance_ref, image_id) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return f(*args, **kw) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 714, in snapshot 2012-08-23 19:08:14 TRACE nova.rpc.amqp image_file) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/image/glance.py, line 306, in update 2012-08-23 19:08:14 TRACE nova.rpc.amqp _reraise_translated_image_exception(image_id) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/image/glance.py, line 304, in update 2012-08-23 19:08:14 TRACE nova.rpc.amqp image_meta = client.update_image(image_id, image_meta, data) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/client.py, line 195, in update_image 2012-08-23 19:08:14 TRACE nova.rpc.amqp res = self.do_request(PUT, /images/%s % image_id, body, headers) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 58, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return func(self, *args, **kwargs) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 420, in do_request 2012-08-23 19:08:14 TRACE nova.rpc.amqp headers=headers) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 75, in wrapped 2012-08-23 19:08:14 TRACE nova.rpc.amqp return func(self, method, url, body, headers) 2012-08-23 19:08:14 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 547, in _do_request 2012-08-23 19:08:14 TRACE nova.rpc.amqp raise exception.Invalid(res.read()) 2012-08-23 19:08:14 TRACE nova.rpc.amqp Invalid: Data supplied was not valid. 2012-08-23 19:08:14 TRACE nova.rpc.amqp Details: 400 Bad Request 2012-08-23 19:08:14 TRACE nova.rpc.amqp 2012-08-23 19:08:14 TRACE nova.rpc.amqp The server could not comply with the request since it is either malformed or otherwise incorrect. 2012-08-23 19:08:14 TRACE nova.rpc.amqp 2012-08-23 19:08:14 TRACE nova.rpc.amqp Failed to update image metadata. Got error: Data supplied was not valid. Details: 400 Bad Request The server could not comply with the request since it is either malformed or otherwise incorrect. Failed to update image metadata. Got error: Data supplied was not valid. Details: Invalid container format 'None' for image. 2012-08-23
Re: [Openstack] Keyring support in openstack
On Thu, Aug 23, 2012 at 7:10 AM, Scott Moser smo...@ubuntu.com wrote: . [backend] default-keyring=keyring.backend.UncryptedFileKeyring keyring-path=/home/ubuntu/xxx # this is ignored As you might already know, the keyring.backend.UncryptedFileKeyring will store the password as in base64 format. If you are concerned about security, but wouldn't wish to enter keyring password, you might use openstackclient.common.openstackkeyring backend. As part of this patch, we have written a keyring backend for openstack to store encrypted password in keyring, withouth prompting for keyring password. -- Regards, Bhuvaneswaran A www.livecipher.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] VM can't ping self floating IP after a snapshot is taken
Hello all! I'm the original author of the hairpin patch, and things have changed a little bit in Essex and Folsom from the original Diablo target. I believe I can shed some light on what should be done here to solve the issue in either case. --- For Essex (stable/essex), in nova/virt/libvirt/connection.py: --- Currently _enable_hairpin() is only being called from spawn(). However, spawn() is not the only place that vifs (veth#) get added to a bridge (which is when we need to enable hairpin_mode on them). The more relevant function is _create_new_domain(), which is called from spawn() and other places. Without changing the information that gets passed to _create_new_domain() (which is just 'xml' from to_xml()), we can easily rewrite the first 2 lines in _enable_hairpin(), as follows: def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) Then, we can move the self._enable_hairpin(instance) call from spawn() up into _create_new_domain(), and pass it xml as follows: [...] self._enable_hairpin(xml) return domain This will run the hairpin code every time a domain gets created, which is also when the domain's vif(s) gets inserted into the bridge with the default of hairpin_mode=0. --- For Folsom (trunk), in nova/virt/libvirt/driver.py: --- There've been a lot more changes made here, but the same strategy as above should work. Here, _create_new_domain() has been split into _create_domain() and _create_domain_and_network(), and _enable_hairpin() was moved from spawn() to _create_domain_and_network(), which seems like it'd be the right thing to do, but doesn't quite cover all of the cases of vif reinsertion, since _create_domain() is the only function which actually creates the domain (_create_domain_and_network() just calls it after doing some pre-work). The solution here is likewise fairly simple; make the same 2 changes to _enable_hairpin(): def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) And move it from _create_domain_and_network() to _create_domain(), like before: [...] self._enable_hairpin(xml) return domain I haven't yet tested this on my Essex clusters and I don't have a Folsom cluster handy at present, but the change is simple and makes sense. Looking at to_xml() and _prepare_xml_info(), it appears that the 'xml' variable _create_[new_]domain() gets is just a python dictionary, and xml['name'] = instance['name'], exactly what _enable_hairpin() was using the 'instance' variable for previously. Let me know if this works, or doesn't work, or doesn't make sense, or if you need an address to send gifts, etc. Hope it's solved! -Evan On Thu, Aug 23, 2012 at 11:20 AM, Sam Su susltd...@gmail.com wrote: Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.comwrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: I ran into some similar issues with the _*enable*_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. ** ** Just thought I’d share my similar pain. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 19, 2012 11:50 AM *To:* Brian Haley *Cc:* openstack *Subject:* Re: [Openstack] VM can't ping self floating IP after a snapshot is taken ** ** Thank you for your support. ** ** I checked the file nova/virt/libvirt/connection.py, the sentence self._enable_hairpin(instance) is already added to the function _hard_reboot(). It looks like there are some difference between taking snapshot and reboot
Re: [Openstack] Default rules for the 'default' security group
Now in HPcloud, have this feature. all the new user, the default security group would open 80,22, 443 and icmp. On Fri, Aug 24, 2012 at 2:02 AM, Gabriel Hurley gabriel.hur...@nebula.comwrote: I traced this through the code at one point looking for the same thing. As it stands, right now there is **not** a mechanism for customizing the default security group’s rules. It’s created programmatically the first time the rules for a project are retrieved with no hook to add or change its characteristics. ** ** I’d love to see this be possible, but it’s definitely a feature request.** ** ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Boris-Michel Deschenes *Sent:* Thursday, August 23, 2012 7:59 AM *To:* Yufang Zhang; openstack@lists.launchpad.net *Subject:* Re: [Openstack] Default rules for the 'default' security group* *** ** ** I’m very interested in this, we run essex and have a very bad workaround for this currently, but it would be great to be able to do this (set default rules for the default security group). ** ** Boris ** ** *De :* openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net [mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net] *De la part de* Yufang Zhang *Envoyé :* 23 août 2012 08:43 *À :* openstack@lists.launchpad.net *Objet :* [Openstack] Default rules for the 'default' security group ** ** Hi all, ** ** Could I ask how to set the default rules for the 'default' security group for all the users in openstack? Currently, the 'default' security group has no rule by default, thus newly created instances could only be accessed by instances from the same group. ** ** Is there any method to set default rules(such as ssh or icmp) for the 'default' security group for all users in openstack, so that I don't have to remind the new users to modify security group setting the fist time they logged into openstack and create instances? I have ever tried HP could which is built on openstack, they permit ssh or ping to the instances in the 'default' security group. ** ** Best Regards. ** ** Yufang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Shake Chen ___ 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] VM can't ping self floating IP after a snapshot is taken
+1 to this. Evan, can you report a bug (if one hasn't been reported yet) and propose the fix? Or else I can find someone else to propose it. Vish On Aug 23, 2012, at 1:38 PM, Evan Callicoat diop...@gmail.com wrote: Hello all! I'm the original author of the hairpin patch, and things have changed a little bit in Essex and Folsom from the original Diablo target. I believe I can shed some light on what should be done here to solve the issue in either case. --- For Essex (stable/essex), in nova/virt/libvirt/connection.py: --- Currently _enable_hairpin() is only being called from spawn(). However, spawn() is not the only place that vifs (veth#) get added to a bridge (which is when we need to enable hairpin_mode on them). The more relevant function is _create_new_domain(), which is called from spawn() and other places. Without changing the information that gets passed to _create_new_domain() (which is just 'xml' from to_xml()), we can easily rewrite the first 2 lines in _enable_hairpin(), as follows: def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) Then, we can move the self._enable_hairpin(instance) call from spawn() up into _create_new_domain(), and pass it xml as follows: [...] self._enable_hairpin(xml) return domain This will run the hairpin code every time a domain gets created, which is also when the domain's vif(s) gets inserted into the bridge with the default of hairpin_mode=0. --- For Folsom (trunk), in nova/virt/libvirt/driver.py: --- There've been a lot more changes made here, but the same strategy as above should work. Here, _create_new_domain() has been split into _create_domain() and _create_domain_and_network(), and _enable_hairpin() was moved from spawn() to _create_domain_and_network(), which seems like it'd be the right thing to do, but doesn't quite cover all of the cases of vif reinsertion, since _create_domain() is the only function which actually creates the domain (_create_domain_and_network() just calls it after doing some pre-work). The solution here is likewise fairly simple; make the same 2 changes to _enable_hairpin(): def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) And move it from _create_domain_and_network() to _create_domain(), like before: [...] self._enable_hairpin(xml) return domain I haven't yet tested this on my Essex clusters and I don't have a Folsom cluster handy at present, but the change is simple and makes sense. Looking at to_xml() and _prepare_xml_info(), it appears that the 'xml' variable _create_[new_]domain() gets is just a python dictionary, and xml['name'] = instance['name'], exactly what _enable_hairpin() was using the 'instance' variable for previously. Let me know if this works, or doesn't work, or doesn't make sense, or if you need an address to send gifts, etc. Hope it's solved! -Evan On Thu, Aug 23, 2012 at 11:20 AM, Sam Su susltd...@gmail.com wrote: Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.com wrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: I ran into some similar issues with the _enable_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. Just thought I’d share my similar pain. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Sam Su Sent: Thursday, July 19, 2012 11:50 AM To: Brian Haley Cc: openstack Subject: Re: [Openstack] VM can't ping self floating IP after a snapshot is
Re: [Openstack] how to configure network on controller with 2 nics ?
Say, you have two nic on the host: eth0(public network) and eth1(private network), and you use FlatDHCP for network configuration. All the instances are in the private subnet. Then you should just add networks like: nova-manage network create demonet 10.0.0.0/24 1 256 --bridge=demonetbr1 --bridge_interface=eth1 When nova create instances, a bridge called 'demoethbr1' is created and a dhcp server is bind on it. The outbound network traffic of instances go out via eth0(public network) of the host. 2012/8/23 Xin Zhao xz...@bnl.gov 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.htmlhttp://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 ___ 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] VM can't ping self floating IP after a snapshot is taken
this bug has been filed here https://bugs.launchpad.net/nova/+bug/1040537 2012/8/24 Vishvananda Ishaya vishvana...@gmail.com: +1 to this. Evan, can you report a bug (if one hasn't been reported yet) and propose the fix? Or else I can find someone else to propose it. Vish On Aug 23, 2012, at 1:38 PM, Evan Callicoat diop...@gmail.com wrote: Hello all! I'm the original author of the hairpin patch, and things have changed a little bit in Essex and Folsom from the original Diablo target. I believe I can shed some light on what should be done here to solve the issue in either case. --- For Essex (stable/essex), in nova/virt/libvirt/connection.py: --- Currently _enable_hairpin() is only being called from spawn(). However, spawn() is not the only place that vifs (veth#) get added to a bridge (which is when we need to enable hairpin_mode on them). The more relevant function is _create_new_domain(), which is called from spawn() and other places. Without changing the information that gets passed to _create_new_domain() (which is just 'xml' from to_xml()), we can easily rewrite the first 2 lines in _enable_hairpin(), as follows: def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) Then, we can move the self._enable_hairpin(instance) call from spawn() up into _create_new_domain(), and pass it xml as follows: [...] self._enable_hairpin(xml) return domain This will run the hairpin code every time a domain gets created, which is also when the domain's vif(s) gets inserted into the bridge with the default of hairpin_mode=0. --- For Folsom (trunk), in nova/virt/libvirt/driver.py: --- There've been a lot more changes made here, but the same strategy as above should work. Here, _create_new_domain() has been split into _create_domain() and _create_domain_and_network(), and _enable_hairpin() was moved from spawn() to _create_domain_and_network(), which seems like it'd be the right thing to do, but doesn't quite cover all of the cases of vif reinsertion, since _create_domain() is the only function which actually creates the domain (_create_domain_and_network() just calls it after doing some pre-work). The solution here is likewise fairly simple; make the same 2 changes to _enable_hairpin(): def _enable_hairpin(self, xml): interfaces = self.get_interfaces(xml['name']) And move it from _create_domain_and_network() to _create_domain(), like before: [...] self._enable_hairpin(xml) return domain I haven't yet tested this on my Essex clusters and I don't have a Folsom cluster handy at present, but the change is simple and makes sense. Looking at to_xml() and _prepare_xml_info(), it appears that the 'xml' variable _create_[new_]domain() gets is just a python dictionary, and xml['name'] = instance['name'], exactly what _enable_hairpin() was using the 'instance' variable for previously. Let me know if this works, or doesn't work, or doesn't make sense, or if you need an address to send gifts, etc. Hope it's solved! -Evan On Thu, Aug 23, 2012 at 11:20 AM, Sam Su susltd...@gmail.com wrote: Hi Oleg, Thank you for your investigation. Good lucky! Can you let me know if find how to fix the bug? Thanks, Sam On Wed, Aug 22, 2012 at 12:50 PM, Oleg Gelbukh ogelb...@mirantis.com wrote: Hello, Is it possible that, during snapshotting, libvirt just tears down virtual interface at some point, and then re-creates it, with hairpin_mode disabled again? This bugfix [https://bugs.launchpad.net/nova/+bug/933640] implies that fix works on spawn of instance. This means that upon resume after snapshot, hairpin is not restored. May be if we insert the _enable_hairpin() call in snapshot procedure, it helps. We're currently investigating this issue in one of our environments, hope to come up with answer by tomorrow. -- Best regards, Oleg On Wed, Aug 22, 2012 at 11:29 PM, Sam Su susltd...@gmail.com wrote: My friend has found a way to enable ping itself, when this problem happened. But not found why this happen. sudo echo 1 /sys/class/net/br1000/brif/virtual-interface-name/hairpin_mode I file a ticket to report this problem: https://bugs.launchpad.net/nova/+bug/1040255 hopefully someone can find why this happen and solve it. Thanks, Sam On Fri, Jul 20, 2012 at 3:50 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: I ran into some similar issues with the _enable_hairpin() call. The call is allowed to fail silently and (in my case) was failing. I couldn’t for the life of me figure out why, though, and since I’m really not a networking person I didn’t trace it along too far. Just thought I’d share my similar pain. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Sam Su Sent: Thursday, July 19, 2012 11:50 AM To: Brian Haley Cc: openstack Subject: Re: