Re: [Openstack-operators] How to force Heat to use v2.0 Keystone
Hi Chris, provided that I'm not a great expert of python, I tried to install it without success: [root@controller-01 heat]# ls -l total 16 drwxr-xr-x 2 root root 4096 Feb 18 09:00 heat_keystoneclient_v2 -rw-r--r-- 1 root root 801 Feb 18 08:58 README.md -rw-r--r-- 1 root root 789 Feb 18 08:59 setup.cfg -rw-r--r-- 1 root root 1045 Feb 18 08:59 setup.py [root@controller-01 heat]# python ./setup.py install error in setup command: Error parsing /root/heat/setup.cfg: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. Are you sure that git is installed? [root@controller-01 heat]# git --version git version 1.7.1 Do you suggest to simply substitute the stock heat file with the new one heat_keystoneclient_v2/client.py ? Is this, /usr/lib/python2.6/site-packages/heat/common/heat_keystoneclient.py, the stock file, isn't it ? thanks, Alvise On 02/17/2015 07:46 PM, Chris Buccella wrote: For Icehouse and Juno, you'll want to use the Keystone v2 plugin for heat: https://git.openstack.org/cgit/openstack/heat/tree/contrib/heat_keystoneclient_v2 -Chris On Tue, Feb 17, 2015 at 10:51 AM, Alvise Dorigo alvise.dor...@pd.infn.it mailto:alvise.dor...@pd.infn.it wrote: Hi Christian; here the info you've requested: [root@controller-01 ~]# grep auth_uri /etc/heat/heat.conf /etc/glance/glance-api.conf /etc/heat/heat.conf:# Allowed keystone endpoints for auth_uri when multi_cloud is /etc/heat/heat.conf:#allowed_auth_uris= /etc/heat/heat.conf:auth_uri = https://cloud-areapd-test.pd.infn.it:5000/v2.0 /etc/heat/heat.conf:#auth_uri=http://127.0.0.1:5000/v2.0 /etc/heat/heat.conf:# Allowed keystone endpoints for auth_uri when multi_cloud is /etc/heat/heat.conf:#allowed_auth_uris= /etc/heat/heat.conf:auth_uri = https://cloud-areapd-test.pd.infn.it:5000/v2.0 /etc/heat/heat.conf:#auth_uri=None /etc/glance/glance-api.conf:auth_uri = https://cloud-areapd-test.pd.infn.it:35357/v2.0 is the problem in the TCP port mismatch ? A. On 02/17/2015 04:38 PM, Christian Berendt wrote: On 02/17/2015 04:11 PM, Alvise Dorigo wrote: [dorigoa@lxadorigo ~]$ heat -k stack-create -f test-stack.yml -P ImageID=cirros;NetID=$NET_ID testStac ERROR: Property error : server1: image Authorization failed: SSL exception connecting to https://cloud-areapd-test.pd.infn.it:5000/v3/auth/tokens What value do you have for the auth_uri parameter in the /etc/heat/heat.conf file? Same for the /etc/glance/glance-api.conf file. Christian. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org mailto:OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org mailto:OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] How to force Heat to use v2.0 Keystone
I had an error in the repository clone. Now I've successfully installed the plugin (python setup.py install). The backend is correctly configured in the heat.conf: [root@controller-02 ~]# grep keystone_backend /etc/heat/heat.conf #keystone_backend=heat.common.heat_keystoneclient.KeystoneClientV3 keystone_backend=heat.engine.plugins.heat_keystoneclient_v2.client.KeystoneClientV2 as descibed in the README.md But heat engine dies just after start: [root@controller-02 ~]# tail /var/log/heat/heat-engine.log 2015-02-18 10:23:30.513 27308 WARNING heat.common.config [-] The instance_user option in heat.conf is deprecated and will be removed in the Juno release. 2015-02-18 10:23:31.018 27308 ERROR heat.common.plugin_loader [-] Failed to import module heat.engine.plugins.heat_keystoneclient_v2.client 2015-02-18 10:23:31.019 27308 CRITICAL heat [-] ImportError: No module named utils Any idea ? Alvise On 02/18/2015 09:06 AM, Alvise Dorigo wrote: Hi Chris, provided that I'm not a great expert of python, I tried to install it without success: [root@controller-01 heat]# ls -l total 16 drwxr-xr-x 2 root root 4096 Feb 18 09:00 heat_keystoneclient_v2 -rw-r--r-- 1 root root 801 Feb 18 08:58 README.md -rw-r--r-- 1 root root 789 Feb 18 08:59 setup.cfg -rw-r--r-- 1 root root 1045 Feb 18 08:59 setup.py [root@controller-01 heat]# python ./setup.py install error in setup command: Error parsing /root/heat/setup.cfg: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. Are you sure that git is installed? [root@controller-01 heat]# git --version git version 1.7.1 Do you suggest to simply substitute the stock heat file with the new one heat_keystoneclient_v2/client.py ? Is this, /usr/lib/python2.6/site-packages/heat/common/heat_keystoneclient.py, the stock file, isn't it ? thanks, Alvise On 02/17/2015 07:46 PM, Chris Buccella wrote: For Icehouse and Juno, you'll want to use the Keystone v2 plugin for heat: https://git.openstack.org/cgit/openstack/heat/tree/contrib/heat_keystoneclient_v2 -Chris On Tue, Feb 17, 2015 at 10:51 AM, Alvise Dorigo alvise.dor...@pd.infn.it mailto:alvise.dor...@pd.infn.it wrote: Hi Christian; here the info you've requested: [root@controller-01 ~]# grep auth_uri /etc/heat/heat.conf /etc/glance/glance-api.conf /etc/heat/heat.conf:# Allowed keystone endpoints for auth_uri when multi_cloud is /etc/heat/heat.conf:#allowed_auth_uris= /etc/heat/heat.conf:auth_uri = https://cloud-areapd-test.pd.infn.it:5000/v2.0 /etc/heat/heat.conf:#auth_uri=http://127.0.0.1:5000/v2.0 /etc/heat/heat.conf:# Allowed keystone endpoints for auth_uri when multi_cloud is /etc/heat/heat.conf:#allowed_auth_uris= /etc/heat/heat.conf:auth_uri = https://cloud-areapd-test.pd.infn.it:5000/v2.0 /etc/heat/heat.conf:#auth_uri=None /etc/glance/glance-api.conf:auth_uri = https://cloud-areapd-test.pd.infn.it:35357/v2.0 is the problem in the TCP port mismatch ? A. On 02/17/2015 04:38 PM, Christian Berendt wrote: On 02/17/2015 04:11 PM, Alvise Dorigo wrote: [dorigoa@lxadorigo ~]$ heat -k stack-create -f test-stack.yml -P ImageID=cirros;NetID=$NET_ID testStac ERROR: Property error : server1: image Authorization failed: SSL exception connecting to https://cloud-areapd-test.pd.infn.it:5000/v3/auth/tokens What value do you have for the auth_uri parameter in the /etc/heat/heat.conf file? Same for the /etc/glance/glance-api.conf file. Christian. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org mailto:OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org mailto:OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Flat network with linux bridge plugin
Hello, I’m trying to configure a very simple Neutron setup. On the compute nodes I want a linux bridge connected to a physical interface on one side and the VMs on the other side. This I have, by using the linux bridge agent and a physnet1:em1 mapping in the config file. On the controller side I need the dhcp and metadata agents. I installed and configured them. They start, no errors in logs. I see a namespace with a ns-* interface in it for dhcp. Outside the namespace I see a tap* interface without IP address, not connected to anything. I installed the linux bridge agent also on the controller node, hoping it would create the bridge between the physnet interface and the dhcp namespace tap interface, but it just sits there and does nothing. So: I have VMs sending DHCP requests. I see the requests on the controller node, but the dhcp namespace is not connected to anything. I can provide logs and config files, but probably I just need a hint in the right direction. On the network controller: Do I need a bridge to connect the namespace to the physical interface? Should this bridge be created by me by hand, or by the linuxbridge agent? Should I run the linuxbridge agent on the network controller? I do not want/have a l3 agent. I want to have just one shared network for all tenants, very simple. Thanks, Daniele ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Unable to delete few instances from dashboard
It's really tough to know without any additional information. Was there an error on the dashboard? Are you using the same credentials? Did these instances have volumes attached? On Feb 18, 2015, at 12:47 PM, raju raju.r...@gmail.com wrote: Hi, am unable to delete few instances from dashboard(Havana) but able to delete from nova cmd line is there any way to resolve the issue? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] How to force Heat to use v2.0 Keystone
Am 18/02/15 um 10:27 schrieb Alvise Dorigo: I had an error in the repository clone. Now I've successfully installed the plugin (python setup.py install). The backend is correctly configured in the heat.conf: [root@controller-02 ~]# grep keystone_backend /etc/heat/heat.conf #keystone_backend=heat.common.heat_keystoneclient.KeystoneClientV3 keystone_backend=heat.engine.plugins.heat_keystoneclient_v2.client.KeystoneClientV2 as descibed in the README.md But heat engine dies just after start: [root@controller-02 ~]# tail /var/log/heat/heat-engine.log 2015-02-18 10:23:30.513 27308 WARNING heat.common.config [-] The instance_user option in heat.conf is deprecated and will be removed in the Juno release. 2015-02-18 10:23:31.018 27308 ERROR heat.common.plugin_loader [-] Failed to import module heat.engine.plugins.heat_keystoneclient_v2.client 2015-02-18 10:23:31.019 27308 CRITICAL heat [-] ImportError: No module named utils Any idea ? This looks to be related to the recent namespace changes, can you try this patch? diff --git a/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py b/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py index 783231b..ad128ff 100644 --- a/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py +++ b/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py @@ -15,7 +15,7 @@ from keystoneclient.v2_0 import client as kc from oslo.config import cfg -from oslo.utils import importutils +from oslo_utils import importutils from oslo_log import log as logging from heat.common import exception ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases
On 02/18/2015 02:31 AM, Marc Koderer wrote: Hello everyone, We already got good feedback on my sandbox test review. So I would like to move forward. With review [1] we will get a stackforge repo called „telcowg-usecases“. Submitting a usecase will then follow the process of OpenStack development (see [2]). Excellent. :) The is one thing currently open: Anita suggested to rename our IRC channel from #openstack-nfv to #openstack-telcowg which seems logical to me. If we agree to this I will register the channel and we can move forward. ++ Best, -jay ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] How to force Heat to use v2.0 Keystone
Hi Jens, If the correct one is oslo_utils (instead of oslo.utils) then the related package is not found: [root@controller-02 ~]# tail /var/log/heat/heat-engine.log [...] 2015-02-18 14:56:29.978 5282 CRITICAL heat [-] ImportError: No module named oslo_utils [root@controller-02 ~]# rpm -qa|grep oslo python-oslo-messaging-1.3.0.2-4.el6.noarch python-oslo-config-1.2.1-1.el6.noarch python-oslo-rootwrap-1.0.0-1.el6.noarch [root@controller-02 ~]# grep oslo /usr/lib/heat/heat_keystoneclient_v2/client.py from oslo.config import cfg from oslo_utils import importutils from oslo_log import log as logging Alvise On 02/18/2015 02:15 PM, Dr. Jens Rosenboom wrote: Am 18/02/15 um 10:27 schrieb Alvise Dorigo: I had an error in the repository clone. Now I've successfully installed the plugin (python setup.py install). The backend is correctly configured in the heat.conf: [root@controller-02 ~]# grep keystone_backend /etc/heat/heat.conf #keystone_backend=heat.common.heat_keystoneclient.KeystoneClientV3 keystone_backend=heat.engine.plugins.heat_keystoneclient_v2.client.KeystoneClientV2 as descibed in the README.md But heat engine dies just after start: [root@controller-02 ~]# tail /var/log/heat/heat-engine.log 2015-02-18 10:23:30.513 27308 WARNING heat.common.config [-] The instance_user option in heat.conf is deprecated and will be removed in the Juno release. 2015-02-18 10:23:31.018 27308 ERROR heat.common.plugin_loader [-] Failed to import module heat.engine.plugins.heat_keystoneclient_v2.client 2015-02-18 10:23:31.019 27308 CRITICAL heat [-] ImportError: No module named utils Any idea ? This looks to be related to the recent namespace changes, can you try this patch? diff --git a/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py b/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py index 783231b..ad128ff 100644 --- a/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py +++ b/contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py @@ -15,7 +15,7 @@ from keystoneclient.v2_0 import client as kc from oslo.config import cfg -from oslo.utils import importutils +from oslo_utils import importutils from oslo_log import log as logging from heat.common import exception ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Unable to delete few instances from dashboard
There was no error seems the delete action is not getting triggered, am trying with admin credentials still no luck some with volumes and some are not As Basil mentioned VM's which are in second page On Wed, Feb 18, 2015 at 5:39 PM, Abel Lopez alopg...@gmail.com wrote: It's really tough to know without any additional information. Was there an error on the dashboard? Are you using the same credentials? Did these instances have volumes attached? On Feb 18, 2015, at 12:47 PM, raju raju.r...@gmail.com wrote: Hi, am unable to delete few instances from dashboard(Havana) but able to delete from nova cmd line is there any way to resolve the issue? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Unable to delete few instances from dashboard
For the vms which are NOT on the first page of dashboard, I have noticed a similar problem. I had to change to number of VM listed per page to a higher number to get it deleted through horizon dashboard. https://bugs.launchpad.net/horizon/+bug/1287093 -Basil On Wed, Feb 18, 2015 at 3:47 PM, raju raju.r...@gmail.com wrote: Hi, am unable to delete few instances from dashboard(Havana) but able to delete from nova cmd line is there any way to resolve the issue? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
