[Openstack] GPG passphrase

[Jobin Raju George]

Hey!

I am trying to get the meters from ceilometer programmatically using java
with the help of the SDK's provided by openstack.

While trying to execute the command mvn clean install or mvn clean install
assembly:assembly, it is asking me for a gpg passphrase. Which passphrase
is it talking about?

If I just press an enter, it gives me the following error message:
[ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-gpg-plugin:1.4:sig
n (sign-artifacts) on project openstack-java-sdk: Exit code: 1 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException



Here are my specifications:


Apache Maven 3.0.5
Java version: 1.6.0_51, vendor: Sun Microsystems Inc.
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

-- 

Thanks and regards,

Jobin Raju George

Third Year, Information Technology

College of Engineering Pune

Alternate e-mail: georgejr10...@coep.ac.in
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Quantum (Grizzly) setup on Fedora18 - VM doesnot receive an IP address

[Gopi Krishna B]

We are unable to get an IP address when a VM gets launched and the below
DHCP error is observed in the Dashboard logs

The setup in done on Fedora 18 using Openstack Grizzly. Its a 2 node setup,
with Network+ Controller node having 3 NIC's, and Compute node having 2
NIC's. Tried configuring networking in vlan mode.

em1 - mgmt network,
em2 - external/public network (br-ex is created on top of this iface)
eth1 - internal/data network (br-eth1 is created on top of this iface)
** *
plugin.ini
-
enable_tunneling = False
tenant_network_type = vlan
network_vlan_ranges = eth1:100:1000
integration_bridge = br-int
bridge_mappings = eth1:br-eth1,em2:br-ex
** *

The console log from the dashboards is as below.

Initializing random number generator... done.

Starting network...

udhcpc (v1.18.5) started

Sending discover...

Sending select for 192.168.120.2...

Sending select for 192.168.120.2...

Sending select for 192.168.120.2...

No lease, failing

WARN: /etc/rc3.d/S40network failed

cirrosds 'net' up at 182.11

checking http://169.254.169.254/20090404/instanceid

failed 1/20: up 182.13. request failed

failed 2/20: up 184.34. request failed

failed 3/20: up 186.36. request failed


Could anyone help us in resolving this issue, we have tried following
different links and options available on internet, but couldnot resolve
this error. Let us know if further information is required to identify the
root cause.

Some more info, and if someone could possibly identify the root cause then
it would be of great help to me.

from the tcpdump output , I could track the DHCP discover packet at the
tapXXX , qbrXXX , qvbXXX, qvoXX, int-br-eth0, phy-br-eth0 interface, but
not after that

As per my understanding the flow of packets should be from tapXX -> qbrXX
-> qvbXX -> qvoXX --> br-int -> int-br-eth0 -> phy-br-eth0 -> br-eth0 ->
eth0

So in this case is there a missing security group rules, which possibly
drop the packet.
I am not familiar with the iptables rules, so if I need to add any rules
could you please help me in adding the rule.
-- 
Regards
Gopi Krishna
___
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] Swift tempurl

[Morten Møller Riis]

I'm having trouble getting tempurl to work.

I set the "X-Account-Meta-Temp-Url-Key" metadata on the account. And a GET 
request shows it's set correctly.

I've enabled it on the proxy server in /etc/swift/proxy-server.conf:

[DEFAULT]
bind_port = 8080
workers = 8
user = swift

[pipeline:main]
pipeline = healthcheck cache tempurl swauth proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

[filter:tempurl]
use = egg:swift#tempurl

[filter:swauth]
use = egg:swauth#swauth
set log_name = swauth
super_admin_key = 
default_swift_cluster = gigahost#https:///v1#http://localhost:8080/v1

[filter:healthcheck]
use = egg:swift#healthcheck

[filter:cache]
use = egg:swift#memcache
memcache_servers = 127.0.0.1:11211

When creating the tempurl's, even using the swift-temp-url program I get:

~ $ curl -i 
"https:///v1/AUTH_224b1001-2c75-444c-aaef-30af13b9154c/000/206.pdf?temp_url_sig=387d79120a591e1cf6f4d4356f5c0a96fb49d202&temp_url_expires=1373438360"
HTTP/1.1 401 Unauthorized
Server: nginx
Date: Wed, 10 Jul 2013 08:21:32 GMT
Content-Type: text/plain
Content-Length: 35
Connection: keep-alive

401 Unauthorized: Temp URL invalid

I've even tried running it locally on the proxy-server to localhost:8080, so 
I'm sure it's not nginx doing any funny stuff.

Does anybody have any suggestions? I'm pretty lost :(


Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk




___
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] email notification in openstack

[val john]

Hi guys ,

Im new to openstack , i have setuped the  cloud setup with two compute and
one controller nodes , is there any way to  send e-mail notification to
project admin , when users launching a instance .

Please advice

Thank you
___
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] I need your help to install Quantum Rest Proxy.

[Julio Carlos Barrera Juez]

Hi lyonggyu.

We are integrating our OpenNaaS project [1] with OpenStack in i2cat
Foundation [2] in the the context of Mantychore project [3]. We want
OpenNaaS to be the network provider of OpenStack to deploy dynamic cloud
environments easily. To achieve this goal, we use 'Big Switch, Floodlight
REST Proxy Plugin' as Quantum proxy to OpenNaaS.

We use OpenStack Grizzly instead of Folsom, but the configuration should be
similar. You can found information in the OpenStack official documentation
[4] and in the Project Floodlight documentation [5]. Basically configuring
the Quantum plugin needs to be done in the controller node providing an
endpoint that offers REST endpoints. Normally it is a FloodLight Openflow
Controller, but can be others.

I have added this thread to OpenStack general and to OpenNaaS users mailing
lists.

I hope it can help you.

Best Regards, Julio C. Barrera.

[1] OpenNaaS project: http://www.opennaas.org/
[2] i2cat Foundation: http://www.i2cat.net/en
[3] Mantychore project: http://www.mantychore.eu/
[4] The OpenStack project, Configuring Big Switch, Floodlight REST Proxy
Plugin:
http://docs.openstack.org/trunk/openstack-network/admin/content/bigswitch_floodlight_plugin.html
[5] Big Switch Networks, Project floodlight, Quantum REST Proxy Plugin :
http://docs.projectfloodlight.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin

On 10 July 2013 09:41,  wrote:

> Hi Julio,
> Recently, I installed OpenStack Folsom with Quantum. However, I could not
> install Quantum Rest Proxy plugin.
> How could you install the plugin? Could you give me a help?
>
> Thank you.
>
>
>
> _
> Sent from http://openstack.10931.n7.nabble.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

[Openstack] OpenStack I18n team meeting tomorrow

[Ying Chun Guo]

Hi,


There is OpenStack I18n team meeting at 0700UTC on Thursday in IRC channel
#openstack-meeting.
The time, we use Europe/India/Asia friendly time. Welcome to join the
meeting.


We will cover following topics this time:

   Action items from the last meeting
   Release of document translation
   How to enroll more developers
   How to track issues and blueprints
   How to track contributors
   Open discussion


For more details, please look into
https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting.


Again, if you are interested in I18n or OpenStack, welcome to join us.
We need developers, translators and some management roles too.
Please contact us through IRC channel #openstack-translation, or mailing
address: openstack-i...@list.openstack.org.
Please refer to our wiki page for more details:
https://wiki.openstack.org/wiki/I18nTeam


Best regards
Daisy___
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] ring building absolut drive names

[Axel Christiansen]

Hello List,


does one has to use the real device names in ring-building, like:
swift-ring-builder account.builder add z5-10.0.6.204:6002/sda4 100
Here it is sda4.

Can one use the partition UUID value or the mount point?


What if a drive has a fialure and a reboot of the system is done with
this failing drive. The subsequente drives after the failing drive will
move up with there drive letters, right? Won't this get the relations
between ring and drives mixed up?


Thank you for hints, Axel





___
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] email notification in openstack

[val john]

Hi guys

is this feature available in Folsom

Thank You
John


On 10 July 2013 14:53, Razique Mahroua wrote:

> +1 I'd like to know that as well :)
> interesting feature
>
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 10 juil. 2013 à 10:59, val john  a écrit :
>
> Hi guys ,
>
> Im new to openstack , i have setuped the  cloud setup with two compute and
> one controller nodes , is there any way to  send e-mail notification to
> project admin , when users launching a instance .
>
> Please advice
>
> Thank you
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
<>___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Exception during message handling on Cinder

[Mahardhika]

Hi, i've got this Error message in cinder-volume.log

ERROR [cinder.volume.iscsi] Failed to create iscsi target for volume 
id:volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd.
ERROR [cinder.volume.manager] volume 
volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd: create failed

ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling

i have check on cinder.conf, api-paste.ini files, let me know if you 
guys need my config file

please help me out of this
thanks
--
Regards,
Mahardhika Gilang

*PT. Andalabs Technology *
Gedung Gravira
Jl. Cideng Barat no. 54
Jakarta Pusat 10150

HP : 0852 139 55861
Email : mahardika.gil...@andalabs.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] I need your help to install Quantum Rest Proxy.

[Julio Carlos Barrera Juez]

Hi Yonggyu.

In OpenStack Grizzly release, the Quantum Rest Proxy plugin is bundled in
the installation packages. We use OpenStack Ubuntu packages as described
OpenStack documentation [1]. In our machine, the plugin is located in
'/usr/share/pyshared/quantum/plugins/bigswitch/plugin.py'.

Please, reply to all this thread to have valuable information tracked and
accessible to the whole community. Thank you.

Pleased to help you.

Regards, Julio C. Barrera.

[1] OpenStack Installation Guide for Ubuntu 12.04 (LTS):
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/


On 10 July 2013 11:22, 이용규  wrote:

>  Thank you for your kind response.
>
>
>
> Yes, I have already read those documents, The OpenStack project,
> Configuring Big Switch, Floodlight REST Proxy Plugin and Big Switch
> Networks, Project floodlight, Quantum REST Proxy Plugin, but I cound not
> download Quantum Rest Proxy plugin package(s). Where and how can I download
> those packages?
>
>
>
> Best Regards,
>
> Yonggyu Lee
>
>
>
>
>
> ---원본메일---
> 보낸사람 : Julio Carlos Barrera Juez 
> 받는사람: lyong...@kaist.ac.kr
> 참 조: us...@lists.opennaas.org,openstack@lists.launchpad.net
> 보낸날짜: 2013-07-10 18:10:47 GMT +0900 (ROK)
> 제목: Re: I need your help to install Quantum Rest Proxy.
>
>
> Hi lyonggyu.
>
> We are integrating our OpenNaaS project [1] with OpenStack in i2cat
> Foundation [2] in the the context of Mantychore project [3]. We want
> OpenNaaS to be the network provider of OpenStack to deploy dynamic cloud
> environments easily. To achieve this goal, we use 'Big Switch, Floodlight
> REST Proxy Plugin' as Quantum proxy to OpenNaaS.
>
> We use OpenStack Grizzly instead of Folsom, but the configuration should
> be similar. You can found information in the OpenStack official
> documentation [4] and in the Project Floodlight documentation [5].
> Basically configuring the Quantum plugin needs to be done in the controller
> node providing an endpoint that offers REST endpoints. Normally it is
> a FloodLight Openflow Controller, but can be others.
>
> I have added this thread to OpenStack general and to OpenNaaS users
> mailing lists.
>
> I hope it can help you.
>
> Best Regards, Julio C. Barrera.
>
> [1] OpenNaaS project: http://www.opennaas.org/
> [2] i2cat Foundation: http://www.i2cat.net/en
> [3] Mantychore project: http://www.mantychore.eu/
> [4] The OpenStack project, Configuring Big Switch, Floodlight REST Proxy
> Plugin:
> http://docs.openstack.org/trunk/openstack-network/admin/content/bigswitch_floodlight_plugin.html
> [5] Big Switch Networks, Project floodlight, Quantum REST Proxy Plugin :
> http://docs.projectfloodlight.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin
>
> On 10 July 2013 09:41,  wrote:
>
>> Hi Julio,
>> Recently, I installed OpenStack Folsom with Quantum. However, I could not
>> install Quantum Rest Proxy plugin.
>> How could you install the plugin? Could you give me a help?
>>
>> Thank you.
>>
>>
>>
>> _
>> Sent from http://openstack.10931.n7.nabble.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] email notification in openstack

[Julien Danjou]

On Wed, Jul 10 2013, val john wrote:

> Im new to openstack , i have setuped the  cloud setup with two compute and
> one controller nodes , is there any way to  send e-mail notification to
> project admin , when users launching a instance .

There's no such feature, but you could rely on Nova notifications sent
to build such a tool.

-- 
Julien Danjou
/* Free Software hacker * freelance consultant
   http://julien.danjou.info */


signature.asc
Description: PGP signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Exception during message handling on Cinder

[claudio marques]

Hi
I also found a problem a while a go with creating or managing volumes. After 
some research I could solve it by doing the following:
vim /usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py
remove line 388
385 self.tgtadm.create_iscsi_target(iscsi_name, iscsi_target,386
 0, volume_path, chap_auth,387  
   check_exit_code=False) <-- close here the method388  
   old_name=old_name) --> (remove this line)
restart all cinder services
cd /etc/init.d/; for i in $( ls cinder-* ); do sudo service $i restart; done
If that doesn't help, try to see your iscsitarget is up and running. See the 
logs.
Hope it help's
Cheer's
Claudio Marques
claudio@onesource.pthttp://www.onesource.pt/


Date: Wed, 10 Jul 2013 16:36:49 +0700
From: mahardika.gil...@andalabs.com
To: openstack@lists.launchpad.net
Subject: [Openstack] Exception during message handling on Cinder


  


  
  
Hi, i've got this Error message in cinder-volume.log



ERROR [cinder.volume.iscsi] Failed to create iscsi target for volume
id:volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd.

ERROR [cinder.volume.manager] volume
volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd: create failed

ERROR [cinder.openstack.common.rpc.amqp] Exception during message
handling



i have check on cinder.conf, api-paste.ini files, let me know if you
guys need my config file

please help me out of this

thanks

-- 

  Regards,

  Mahardhika Gilang

  

  PT. Andalabs Technology
  

  Gedung Gravira

  Jl. Cideng Barat no. 54

  Jakarta Pusat 10150

  

  HP : 0852 139 55861

  Email : mahardika.gil...@andalabs.com 
  


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp   
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Can grizzly quantum usinig in Folsom openstack

[冯凯]

  Hi,

  Does the grizzly version quantum can use in the folsom  openstack.




  Thank you


  Best regards! 
 
  Tristran.

  


___
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] Can grizzly quantum usinig in Folsom openstack

[冯凯]

Hi,Gray


Thanks for your reply , in the folsom , the nova.conf should set the 
firewall_driver='firewall=nova.virt.libvirt.firewall.IptablesFirewallDriver' , 
but in grizzly the nova.conf need set the firewall_driver='NoopfirewallDriver' 
to use quantum. 


I will tryed it again.




Regards


Tristran.




-原始邮件-
发件人: "Gary Kotton" 
发送时间: 2013年7月10日 星期三
收件人: "冯凯" 
抄送:
主题: RE: [Openstack] Can grizzly quantum usinig in Folsom openstack



Hi,

I am not 100% sure that it will work. You will need to run the database 
migration scripts and then make sure that you start to use the relevant grizzly 
services.

Thanks

Gary

 

From: Openstack 
[mailto:openstack-bounces+gkotton=vmware@lists.launchpad.net] On Behalf Of 
??
Sent: Wednesday, July 10, 2013 1:15 PM
To:openstack-...@lists.openstack.org; openstack@lists.launchpad.net
Subject: [Openstack] Can grizzly quantum usinig in Folsom openstack

 


  Hi,



  Does the grizzly version quantum can use in the folsom  openstack.

 

 

  Thank you

 

  Best regards! 

 

  Tristran.

  









___
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] Swift tempurl

[Morten Møller Riis]

I've been looking at tempurl.py and found that the problem occurs here:

def _get_key(self, env, account):
"""
Returns the X-Account-Meta-Temp-URL-Key header value for the
account, or None if none is set.

:param env: The WSGI environment for the request.
:param account: Account str.
:returns: X-Account-Meta-Temp-URL-Key str value, or None.
"""
key = None
memcache = env.get('swift.cache')
if memcache:
key = memcache.get('temp-url-key/%s' % account)
if not key:
newenv = make_pre_authed_env(env, 'HEAD', '/v1/' + account,
 self.agent)
newenv['CONTENT_LENGTH'] = '0'
newenv['wsgi.input'] = StringIO('')
key = [None]

def _start_response(status, response_headers, exc_info=None):
for h, v in response_headers:
if h.lower() == 'x-account-meta-temp-url-key':
key[0] = v

i = iter(self.app(newenv, _start_response))
self.logger.info()
try:
i.next()
except StopIteration:
pass
key = key[0]
if key and memcache:
memcache.set('temp-url-key/%s' % account, key, timeout=60)
return key

The request get 403 forbidden and thus never gets the key in the first place. 
I'm looking at the github repo and the implementation there seems to have 
changed.


Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk




On Jul 10, 2013, at 6:24 PM, Morten Møller Riis  wrote:

> I'm having trouble getting tempurl to work.
> 
> I set the "X-Account-Meta-Temp-Url-Key" metadata on the account. And a GET 
> request shows it's set correctly.
> 
> I've enabled it on the proxy server in /etc/swift/proxy-server.conf:
> 
> [DEFAULT]
> bind_port = 8080
> workers = 8
> user = swift
> 
> [pipeline:main]
> pipeline = healthcheck cache tempurl swauth proxy-server
> 
> [app:proxy-server]
> use = egg:swift#proxy
> allow_account_management = true
> account_autocreate = true
> 
> [filter:tempurl]
> use = egg:swift#tempurl
> 
> [filter:swauth]
> use = egg:swauth#swauth
> set log_name = swauth
> super_admin_key = 
> default_swift_cluster = gigahost#https:///v1#http://localhost:8080/v1
> 
> [filter:healthcheck]
> use = egg:swift#healthcheck
> 
> [filter:cache]
> use = egg:swift#memcache
> memcache_servers = 127.0.0.1:11211
> 
> When creating the tempurl's, even using the swift-temp-url program I get:
> 
> ~ $ curl -i 
> "https:///v1/AUTH_224b1001-2c75-444c-aaef-30af13b9154c/000/206.pdf?temp_url_sig=387d79120a591e1cf6f4d4356f5c0a96fb49d202&temp_url_expires=1373438360"
> HTTP/1.1 401 Unauthorized
> Server: nginx
> Date: Wed, 10 Jul 2013 08:21:32 GMT
> Content-Type: text/plain
> Content-Length: 35
> Connection: keep-alive
> 
> 401 Unauthorized: Temp URL invalid
> 
> I've even tried running it locally on the proxy-server to localhost:8080, so 
> I'm sure it's not nginx doing any funny stuff.
> 
> Does anybody have any suggestions? I'm pretty lost :(
> 
> 
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
> 
> 
> 
> 
> ___
> 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] Ansible playbooks for OpenStack

[Daniel P. Berrange]

On Mon, Jul 08, 2013 at 10:02:59AM -0500, Timothy Gerla wrote:
> Hi everyone,
> 
> I wanted to share this with the group in the hopes that we could get
> some feedback. We've built a set of Ansible playbooks to install &
> configure a "full" OpenStack deployment based on the Red Hat packaging
> on CentOS 6.
> 
> (Ansible is a configuration management and software deployment
> automation tool: http://www.ansibleworks.com/)
> 
> Here are the playbooks and some basic documentation:
> 
> https://github.com/ansible/ansible-redhat-openstack
> 
> I'm interested to know what folks think and if anyone finds this
> useful. I think it might be useful for quick deployments (you can go
> from a group of minimally installed CentOS boxes to OpenStack in 20-30
> minutes), and I think this could serve as the basis for a more
> sophisticated production deployment mechanism.

FWIW, there is a tool called PackStack which uses Puppet to fully
automate deployments of OpenStack in a matter of minutes. It is
the tool that Red Hat currently recommend for deployment on Fedora,
RHEL & CentOS, etc

  https://wiki.openstack.org/wiki/Packstack

Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Ansible playbooks for OpenStack

[Jay Pipes]

On 07/10/2013 08:09 AM, Daniel P. Berrange wrote:

On Mon, Jul 08, 2013 at 10:02:59AM -0500, Timothy Gerla wrote:

Hi everyone,

I wanted to share this with the group in the hopes that we could get
some feedback. We've built a set of Ansible playbooks to install &
configure a "full" OpenStack deployment based on the Red Hat packaging
on CentOS 6.

(Ansible is a configuration management and software deployment
automation tool: http://www.ansibleworks.com/)

Here are the playbooks and some basic documentation:

https://github.com/ansible/ansible-redhat-openstack

I'm interested to know what folks think and if anyone finds this
useful. I think it might be useful for quick deployments (you can go
from a group of minimally installed CentOS boxes to OpenStack in 20-30
minutes), and I think this could serve as the basis for a more
sophisticated production deployment mechanism.


FWIW, there is a tool called PackStack which uses Puppet to fully
automate deployments of OpenStack in a matter of minutes. It is
the tool that Red Hat currently recommend for deployment on Fedora,
RHEL & CentOS, etc

   https://wiki.openstack.org/wiki/Packstack


And for completeness, for folks using Chef, there is an OpenStack + Chef 
mailing list [1], an example Chef repo, and a set of OpenStack-specific 
cookbooks housed on Stackforge [2]. Currently everything is under very 
active development, with a focus on getting turnkey installation like 
PackStack done by the Havana release.


[1] 
https://groups.google.com/forum/?fromgroups=#!forum/opscode-chef-openstack

[2] https://github.com/stackforge/openstack-chef-repo
and https://github.com/stackforge/cookbook-openstack-XXX

where XXX in (common, compute, block-storage, image, identity, network, 
object-storage, metering, orchestration, ops-messaging, ops-database)


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

Re: [Openstack] [Nova] CPU Scalling, Quota for Disk I/O

[Yaguang Tang]

Here is a wiki  about this feature,
https://wiki.openstack.org/wiki/InstanceResourceQuota
you can set CPU, disk IO consume policy, network traffic bandwidth for
specified flavor. so the instance of that flavor can only consume under
controlled physical resource.

2013/7/10 Shake Chen 

> https://blueprints.launchpad.net/nova/+spec/quota-instance-resource
>
> In my view the instance recourse  like cpu, network, disk io quota feature
> have in Grizzly. we just need to add the feature to Horizon.
>
>
> On Wed, Jul 10, 2013 at 3:53 AM, Bruno Oliveira ~lychinus <
> brunnop.olive...@gmail.com> wrote:
>
>> Hello, any thoughts on this ?
>>
>> Thank you
>> --
>>
>> Bruno Oliveira
>> Developer, Software Engineer
>> irc: lychinus | skype: brunnop.oliveira
>> brunnop.olive...@gmail.com
>>
>>
>>
>>
>>
>> On Mon, Jul 1, 2013 at 4:22 PM, Bruno Oliveira ~lychinus
>>  wrote:
>> > Hello Stackers,
>> >
>> > Today morning I saw an interesting question regarding CPU Scaling
>> > in the list, which got me to ask the following:
>> >
>> > Currently (or in the roadmap) do we have any feature on Nova
>> > (regardless of the hypervisor underneath) to set maximum disk I/O
>> > throughput a VM can have ?
>> >
>> > I mean, let's say we have hundreds of VMs under the same host as
>> > in production, and for some reason we're lacking performance due to
>> > one (or a few of them) being too hungry/greedy for disk reads/writes.
>> >
>> > Question 1) Is there a way we can set quotas for disk I/O for a (group
>> of)
>> > instances ? Like: for this one (or this group), don't exceed the
>> threshold
>> > of 50 MB/seg
>> >
>> > Question 2) Also, do we have anything like vertical scalling ?
>> > I mean, like defining CPU and Memory Balloons as extra resources
>> > that a set of VMs can make use of (temporarily), if they're demanding
>> to ?
>> >
>> > Note: I've seen some of the videos of "Heat" talking about increasing
>> > horizontally  the number of instances behind a load balancer to attend
>> > an increasing number of user requests, for instances...
>> >
>> > Thank you so much.
>> >
>> > --
>> >
>> > Bruno Oliveira
>> > Developer, Software Engineer
>> > irc: lychinus | skype: brunnop.oliveira
>> > brunnop.olive...@gmail.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
>>
>
>
>
> --
> 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
>
>


-- 
Tang Yaguang

Canonical Ltd. | www.ubuntu.com | www.canonical.com
Mobile:  +86 152 1094 6968
gpg key: 0x187F664F
___
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] Quantum (Grizzly) setup on Fedora18 - VM doesnot receive an IP address

[Gopi Krishna B]

Resending the mail, as wrong dashboard logs were posted in the prev
question...

We are unable to get an IP address when a VM gets launched and the below
DHCP error is observed in the Dashboard logs

The setup in done on Fedora 18 using Openstack Grizzly. Its a 2 node setup,
with Network+ Controller node having 3 NIC's, and Compute node having 2
NIC's. Tried configuring networking in vlan mode.

em1 - mgmt network,
em2 - external/public network (br-ex is created on top of this iface)
eth1 - internal/data network (br-eth1 is created on top of this iface)
** *
plugin.ini
-
enable_tunneling = False
tenant_network_type = vlan
network_vlan_ranges = eth1:100:1000
integration_bridge = br-int
bridge_mappings = eth1:br-eth1,em2:br-ex
** *

Starting logging: OK
Initializing random number generator... done.
Starting acpid: OK
cirrosds 'local' up at 1.48
no results found for mode=local. up 1.53. searched: nocloud configdrive ec2
Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40network failed
cirrosds 'net' up at 181.79
checking http://169.254.169.254/20090404/instanceid
failed 1/20: up 181.83. request failed
failed 2/20: up 184.04. request failed

failed to read iid from metadata. tried 20
no results found for mode=net. up 222.36. searched: nocloud configdrive ec2
failed to get instanceid of datasource
Starting dropbear sshd: generating rsa key... generating dsa key... OK
=== network info ===
ifinfo: lo,up,127.0.0.1,8,::1
ifinfo: eth0,up,,8,fe80::f816:3eff:fede:dbc8
=== datasource: None None ===
=== cirros: current=0.3.1 uptime=222.60 ===
route: fscanf
=== pinging gateway failed, debugging connection ===

### route n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
route: fscanf
### cat /etc/resolv.conf
cat: can't open '/etc/resolv.conf': No such file or directory
### gateway not found
/sbin/cirrosstatus: line 1: can't open /etc/resolv.conf: no such file
### pinging nameservers
### uname a
Linux cirros 3.2.037virtual #58Ubuntu SMP Thu Jan 24 15:48:03 UTC 2013
x86_64 GNU/Linux

Could anyone help us in resolving this issue, we have tried following
different links and options available on internet, but couldnot resolve
this error. Let us know if further information is required to identify the
root cause.

Some more info, and if someone could possibly identify the root cause then
it would be of great help to me.

from the tcpdump output , I could track the DHCP discover packet at the
tapXXX , qbrXXX , qvbXXX, qvoXX, int-br-eth0, phy-br-eth0 interface, but
not after that

As per my understanding the flow of packets should be from tapXX -> qbrXX
-> qvbXX -> qvoXX --> br-int -> int-br-eth0 -> phy-br-eth0 -> br-eth0 ->
eth0

So in this case is there a missing security group rules, which possibly
drop the packet.
I am not familiar with the iptables rules, so if I need to add any rules
could you please help me in adding the rule.
-- 
Regards
Gopi Krishna


On Wed, Jul 10, 2013 at 10:21 AM, Gopi Krishna B wrote:

> We are unable to get an IP address when a VM gets launched and the below
> DHCP error is observed in the Dashboard logs
>
> The setup in done on Fedora 18 using Openstack Grizzly. Its a 2 node
> setup, with Network+ Controller node having 3 NIC's, and Compute node
> having 2 NIC's. Tried configuring networking in vlan mode.
>
> em1 - mgmt network,
> em2 - external/public network (br-ex is created on top of this iface)
> eth1 - internal/data network (br-eth1 is created on top of this iface)
> ** *
> plugin.ini
> -
> enable_tunneling = False
> tenant_network_type = vlan
> network_vlan_ranges = eth1:100:1000
> integration_bridge = br-int
> bridge_mappings = eth1:br-eth1,em2:br-ex
> ** *
>
> The console log from the dashboards is as below.
>
> Initializing random number generator... done.
>
> Starting network...
>
> udhcpc (v1.18.5) started
>
> Sending discover...
>
> Sending select for 192.168.120.2...
>
> Sending select for 192.168.120.2...
>
> Sending select for 192.168.120.2...
>
> No lease, failing
>
> WARN: /etc/rc3.d/S40network failed
>
> cirrosds 'net' up at 182.11
>
> checking http://169.254.169.254/20090404/instanceid
>
> failed 1/20: up 182.13. request failed
>
> failed 2/20: up 184.34. request failed
>
> failed 3/20: up 186.36. request failed
>
>
> Could anyone help us in resolving this issue, we have tried following
> different links and options available on internet, but couldnot resolve
> this error. Let us know if further information is required to identify the
> root cause.
>
> Some more info, and if someone could possibly identify the root cause then
> it would be of great help to me.
>
> from the tcpdump output , I could track the DHCP discover packet at the
> tapXXX , qbrXXX , qvb

[Openstack] [ANN] Caimito 0.11 - WebDAV frontend for OpenStack Swift Cloud Storage

[Gabe Wong]

Re: Caimito 0.11 - WebDAV frontend for OpenStack Swift Cloud Storage

Hi all,
Lots of work has been done to Caimito. In addition to bug fixes:
- Faster request handling.
- Better handling of files with spaces and other characters.

Thanks to everyone who have contributed. Of course the community's valuable 
feedback is much welcomed.
Feel free to download Caimito here:
http://caimito.ngasi.com

Cheers.___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] ring building absolut drive names

[Samuel Merritt]

On 7/10/13 2:25 AM, Axel Christiansen wrote:

Hello List,


does one has to use the real device names in ring-building, like:
swift-ring-builder account.builder add z5-10.0.6.204:6002/sda4 100
Here it is sda4.

Can one use the partition UUID value or the mount point?


It's really a mount point, not a device name. You can use whatever thing 
you want, so long as /srv/node/<$thing> is where the filesystem is mounted.


___
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] Grizzly GRE tunneling network set up problems

[Haitao Jiang]

Aaron

I followed instructions in
http://n40lab.wordpress.com/2013/06/03/centos-6-4-openvswitch-installation/
on my compute node as a test. Restarted OVS, but still see the same
error in the ovs-vswitchd.log. This is what I have

kmod-openvswitch.x86_64  1.10.0-1.el6
 @/kmod-openvswitch-1.10.0-1.el6.x86_64
openstack-quantum-openvswitch.noarch2013.1.2-1.el6
@openstack-grizzly
openvswitch.x86_641.10.0-1.el6
  @openstack-grizzly

filename:
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
version:1.10.0
license:GPL
description:Open vSwitch switching datapath
srcversion: 480D55A9BB0E8B000E32010
depends:
vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
modversions
parm:   vlan_tso:Enable TSO for VLAN packets (int)

# find / -name openvswitch.ko | xargs ls -l
-rw-r--r-- 1 ovswitch ovswitch 4948350 Jul  9 21:41
/home/ovswitch/rpmbuild/BUILD/openvswitch-1.10.0/_default/datapath/linux/openvswitch.ko
-rw-r--r-- 1 root root 4948350 Jul  9 21:41
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
-rwxr--r-- 1 root root   77936 Jun 12 20:19
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
-rwxr--r-- 1 root root   72912 Jun 12 04:36
/lib/modules/2.6.32-358.11.1.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
lrwxrwxrwx 1 root root  83 Jul  9 21:42
/lib/modules/2.6.32-358.11.1.el6.x86_64/weak-updates/openvswitch/openvswitch.ko
-> 
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko

anything else I need to check? Does above looks right to you?

Thanks

Haitao

On Tue, Jul 9, 2013 at 10:29 PM, Aaron Rosen  wrote:
> You should be able to compile openvswitch from source here :
> http://openvswitch.org/download/ and then you'll get tunnel support.
>
> Aaron
>
>
> On Tue, Jul 9, 2013 at 10:21 PM, Haitao Jiang  wrote:
>>
>> Aaron & Chandler
>>
>> Thanks a lot for the help. I should have mentioned that the host OS is
>> CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
>> found that it may not have gre tunneling support. Is there anyone who
>> has successfully set up gre with RDO's kernel or it is just can not be
>> done and I should use the VLAN.
>>
>> As Aaron suspected, there are errprs in the OVS agent log:
>>
>> system@ovs-system: failed to add gre-3 as port: Address family not
>> supported by protocol
>>
>> More details below
>>
>> Any pointer will be highly appreciated!
>>
>> Haitao
>> ==
>> Here are some outputs on my compute node (.46, .42 is the control node
>> and .44 is the network node):
>>
>>
>> # ovs-vsctl show
>> 1d554b19-2a2b-493d-a123-0efb0aabc7d1
>> Bridge br-int
>> Port br-int
>> Interface br-int
>> type: internal
>> Port "qvo8108425f-ef"
>> tag: 1
>> Interface "qvo8108425f-ef"
>> Port patch-tun
>> Interface patch-tun
>> type: patch
>> options: {peer=patch-int}
>> Bridge br-tun
>> Port br-tun
>> Interface br-tun
>> type: internal
>> Port "gre-3"
>> Interface "gre-3"
>> type: gre
>> options: {in_key=flow, out_key=flow,
>> remote_ip="10.18.250.44"}
>> Port "gre-4"
>> Interface "gre-4"
>> type: gre
>> options: {in_key=flow, out_key=flow,
>> remote_ip="10.18.250.42"}
>> Port patch-int
>> Interface patch-int
>> type: patch
>> options: {peer=patch-tun}
>> ovs_version: "1.10.0"
>>
>> # ovs-ofctl dump-ports br-tun
>> OFPST_PORT reply (xid=0x2): 2 ports
>>   port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0, crc=0
>>tx pkts=0, bytes=0, drop=0, errs=0, coll=0
>>   port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
>>tx pkts=140, bytes=9800, drop=0, errs=0, coll=0
>>
>> # uname -r
>> 2.6.32-358.111.1.openstack.el6.x86_64
>>
>> # modinfo openvswitch
>> filename:
>>
>> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
>> version:1.10.0
>> license:GPL
>> description:Open vSwitch switching datapath
>> srcversion: 480D55A9BB0E8B000E32010
>> depends:
>> vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
>> modversions
>> parm:   vlan_tso:Enable TSO for VLAN packets (int)
>>
>> # tail ovs-vswitchd.log
>>
>> 2013-07-09T23:28:18Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connecting...
>>
>> 2013-07-09T23:28:18Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
>> connected
>> 2013-07-09T23:28:18Z|4|bridge|INFO|bridge br-int: added interface
>> patch-tun on port 1
>> 2013-07-09T23:28:18

Re: [Openstack] Grizzly GRE tunneling network set up problems

[Aaron Rosen]

You should follow the instructions here:
http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob;f=INSTALL;h=5589fe7dd7203308bbec27a562cb9899d218577a;hb=a4fff9cc390b69bde1257b414212505a72c4b450


On Wed, Jul 10, 2013 at 10:27 AM, Haitao Jiang wrote:

> Aaron
>
> I followed instructions in
> http://n40lab.wordpress.com/2013/06/03/centos-6-4-openvswitch-installation/
> on my compute node as a test. Restarted OVS, but still see the same
> error in the ovs-vswitchd.log. This is what I have
>
> kmod-openvswitch.x86_64  1.10.0-1.el6
>  @/kmod-openvswitch-1.10.0-1.el6.x86_64
> openstack-quantum-openvswitch.noarch2013.1.2-1.el6
> @openstack-grizzly
> openvswitch.x86_641.10.0-1.el6
>   @openstack-grizzly
>
> filename:
>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
> version:1.10.0
> license:GPL
> description:Open vSwitch switching datapath
> srcversion: 480D55A9BB0E8B000E32010
> depends:
> vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
> modversions
> parm:   vlan_tso:Enable TSO for VLAN packets (int)
>
> # find / -name openvswitch.ko | xargs ls -l
> -rw-r--r-- 1 ovswitch ovswitch 4948350 Jul  9 21:41
>
> /home/ovswitch/rpmbuild/BUILD/openvswitch-1.10.0/_default/datapath/linux/openvswitch.ko
> -rw-r--r-- 1 root root 4948350 Jul  9 21:41
>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
> -rwxr--r-- 1 root root   77936 Jun 12 20:19
>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
> -rwxr--r-- 1 root root   72912 Jun 12 04:36
>
> /lib/modules/2.6.32-358.11.1.el6.x86_64/kernel/net/openvswitch/openvswitch.ko
> lrwxrwxrwx 1 root root  83 Jul  9 21:42
>
> /lib/modules/2.6.32-358.11.1.el6.x86_64/weak-updates/openvswitch/openvswitch.ko
> ->
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
>
> anything else I need to check? Does above looks right to you?
>
> Thanks
>
> Haitao
>
> On Tue, Jul 9, 2013 at 10:29 PM, Aaron Rosen  wrote:
> > You should be able to compile openvswitch from source here :
> > http://openvswitch.org/download/ and then you'll get tunnel support.
> >
> > Aaron
> >
> >
> > On Tue, Jul 9, 2013 at 10:21 PM, Haitao Jiang 
> wrote:
> >>
> >> Aaron & Chandler
> >>
> >> Thanks a lot for the help. I should have mentioned that the host OS is
> >> CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
> >> found that it may not have gre tunneling support. Is there anyone who
> >> has successfully set up gre with RDO's kernel or it is just can not be
> >> done and I should use the VLAN.
> >>
> >> As Aaron suspected, there are errprs in the OVS agent log:
> >>
> >> system@ovs-system: failed to add gre-3 as port: Address family not
> >> supported by protocol
> >>
> >> More details below
> >>
> >> Any pointer will be highly appreciated!
> >>
> >> Haitao
> >> ==
> >> Here are some outputs on my compute node (.46, .42 is the control node
> >> and .44 is the network node):
> >>
> >>
> >> # ovs-vsctl show
> >> 1d554b19-2a2b-493d-a123-0efb0aabc7d1
> >> Bridge br-int
> >> Port br-int
> >> Interface br-int
> >> type: internal
> >> Port "qvo8108425f-ef"
> >> tag: 1
> >> Interface "qvo8108425f-ef"
> >> Port patch-tun
> >> Interface patch-tun
> >> type: patch
> >> options: {peer=patch-int}
> >> Bridge br-tun
> >> Port br-tun
> >> Interface br-tun
> >> type: internal
> >> Port "gre-3"
> >> Interface "gre-3"
> >> type: gre
> >> options: {in_key=flow, out_key=flow,
> >> remote_ip="10.18.250.44"}
> >> Port "gre-4"
> >> Interface "gre-4"
> >> type: gre
> >> options: {in_key=flow, out_key=flow,
> >> remote_ip="10.18.250.42"}
> >> Port patch-int
> >> Interface patch-int
> >> type: patch
> >> options: {peer=patch-tun}
> >> ovs_version: "1.10.0"
> >>
> >> # ovs-ofctl dump-ports br-tun
> >> OFPST_PORT reply (xid=0x2): 2 ports
> >>   port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0,
> crc=0
> >>tx pkts=0, bytes=0, drop=0, errs=0, coll=0
> >>   port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
> >>tx pkts=140, bytes=9800, drop=0, errs=0, coll=0
> >>
> >> # uname -r
> >> 2.6.32-358.111.1.openstack.el6.x86_64
> >>
> >> # modinfo openvswitch
> >> filename:
> >>
> >>
> /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
> >> version:1.10.0
> >> license:GPL
> >> description:Open vSwitch switching datapath
> >> srcversion: 48

Re: [Openstack] Swift tempurl

[Shrinand Javadekar]

I had a similar problem. See [1]. The fix was to add delay_auth_decision =
1 in the proxy-server.conf

[filter:authtoken]
...
delay_auth_decision = 1

-Shri
[1] https://answers.launchpad.net/swift/+question/225614


On Wed, Jul 10, 2013 at 4:43 AM, Morten Møller Riis  wrote:

> I've been looking at tempurl.py and found that the problem occurs here:
>
> def _get_key(self, env, account):
> """
> Returns the X-Account-Meta-Temp-URL-Key header value for the
> account, or None if none is set.
>
> :param env: The WSGI environment for the request.
> :param account: Account str.
> :returns: X-Account-Meta-Temp-URL-Key str value, or None.
> """
> key = None
> memcache = env.get('swift.cache')
> if memcache:
> key = memcache.get('temp-url-key/%s' % account)
> if not key:
> newenv = make_pre_authed_env(env, 'HEAD', '/v1/' + account,
>  self.agent)
> newenv['CONTENT_LENGTH'] = '0'
> newenv['wsgi.input'] = StringIO('')
> key = [None]
>
> def _start_response(status, response_headers, exc_info=None):
> for h, v in response_headers:
> if h.lower() == 'x-account-meta-temp-url-key':
> key[0] = v
>
> i = iter(self.app(newenv, _start_response))
> self.logger.info()
> try:
> i.next()
> except StopIteration:
> pass
> key = key[0]
> if key and memcache:
> memcache.set('temp-url-key/%s' % account, key, timeout=60)
> return key
>
> The request get 403 forbidden and thus never gets the key in the first
> place. I'm looking at the github repo and the implementation there seems to
> have changed.
>
>
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
>
>
>
>
> On Jul 10, 2013, at 6:24 PM, Morten Møller Riis  wrote:
>
> I'm having trouble getting tempurl to work.
>
> I set the "X-Account-Meta-Temp-Url-Key" metadata on the account. And a GET
> request shows it's set correctly.
>
> I've enabled it on the proxy server in /etc/swift/proxy-server.conf:
>
> [DEFAULT]
> bind_port = 8080
> workers = 8
> user = swift
>
> [pipeline:main]
> pipeline = healthcheck cache tempurl swauth proxy-server
>
> [app:proxy-server]
> use = egg:swift#proxy
> allow_account_management = true
> account_autocreate = true
>
> [filter:tempurl]
> use = egg:swift#tempurl
>
> [filter:swauth]
> use = egg:swauth#swauth
> set log_name = swauth
> super_admin_key = 
> default_swift_cluster = gigahost#https:///v1#http://localhost:8080/v1
>
> [filter:healthcheck]
> use = egg:swift#healthcheck
>
> [filter:cache]
> use = egg:swift#memcache
> memcache_servers = 127.0.0.1:11211
>
> When creating the tempurl's, even using the swift-temp-url program I get:
>
> ~ $ curl -i "https://
> /v1/AUTH_224b1001-2c75-444c-aaef-30af13b9154c/000/206.pdf?temp_url_sig=387d79120a591e1cf6f4d4356f5c0a96fb49d202&temp_url_expires=1373438360"
> HTTP/1.1 401 Unauthorized
> Server: nginx
> Date: Wed, 10 Jul 2013 08:21:32 GMT
> Content-Type: text/plain
> Content-Length: 35
> Connection: keep-alive
>
> 401 Unauthorized: Temp URL invalid
>
> I've even tried running it locally on the proxy-server to localhost:8080,
> so I'm sure it's not nginx doing any funny stuff.
>
> Does anybody have any suggestions? I'm pretty lost :(
>
>
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [openstack][Neutron] Allocating fixed and floating IPs from the same subnet

[Cristian Tomoiaga]

Hello everyone,

I was wondering if it is a "good" idea to allocate IPs either fixed or
floating from the same subnet (external , routable IPs).

My use case is something like this:

A tenant needs to have direct access to the external network (no NAT) and
if he chooses to use a load balancer he should be able to also use floating
IPs.
I don't really want to allocate more than one subnet for routable IPs, at
least I don't see a reason why.
A tenant should be able to have access to a limited number of routable IPs
that would remain allocated to him no matter what happens to instances and
he should be able to either allocate an IP directly to an instance or set
that IP as a floating IP for other services like LBaaS.

I see that right now I can just create a floating IP from a subnet that can
also be used for fixed IPs (flat provider use case).

Mainly I want floating IPs but with the possibility of allocating a
floating IP to an instance directly (no nat )

There is some coding to be done here, however first I would like to ask the
community if this is a sound idea or I am missing something.

-- 
Regards,
Cristian Tomoiaga
___
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] New mailing lists in Italian, Spanish, Vietnamese

[Stefano Maffulli]

Hello there,

We've setup three new mailing lists in non-English languages. You can
discuss OpenStack-related issues in Spanish, Vietnamese, Italian
subscribing at the addresses below:

Spanish
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-es

Vietnamese
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-vi

Italian
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-it

Other resources for international groups are on the wiki

http://wiki.openstack.org/OpenStackUserGroups

Regards,
Stef

-- 
Ask and answer questions on https://ask.openstack.org

___
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] Nova API to get VMs belonging to other users / tenants

[Narayanan, Krishnaprasad]

Hi Brent,

I am running OpenStack ESSEX in my cloud. If it is possible, can you tell me 
the steps to assign an admin role to a user in keystone.

Do I have to change anything in the policy.json related to the servers API?

Currently I use this API for getting the servers details - 
"compute_extension:extended_server_attributes": []

Thanks
Krishnaprasad
From: Brent Roskos [mailto:brent.ros...@solinea.com]
Sent: Dienstag, 25. Juni 2013 23:16
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Nova API to get VMs belonging to other users / tenants

No - you need a token with admin creds for that (user must have admin role in 
keystone).
Once you have the correct creds, you can use the nova cli:

nova list  --all-tenants

If you wanted to see how this looks in the raw API, just pass the debug flag in 
the cli and it will show you the correct post.

Brent

On Tue, Jun 25, 2013 at 11:59 AM, Narayanan, Krishnaprasad 
mailto:naray...@uni-mainz.de>> wrote:
Hallo All,

Is it possible using the Nova API for a normal user / tenant to get all VMs 
belonging to other users / tenants?

If yes, can I get to know how to achieve this?

Thanks
Krishnaprasad

___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] qemu in Grizzly Ubuntu Cloud Archive?

[Samuel Winchenbach]

Hi All,

Does anyone know if there is a reason that qemu >= 1.3.0 is not in the
Grizzly Ubuntu Cloud Archive?

Do you see any reason that I shouldn't install the qemu 1.5.0 packages (for
havana) manually for a grizzly install?

I would really like to have the zero-downtime snapshot capability afforded
by qemu >= 1.3.0


Thanks,
Sam
___
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] Swift tempurl

[Morten Møller Riis]

I use swauth, and thus authtoken is not present in my pipeline. This might be 
why I'm seeing the problem actually.

Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk




On Jul 11, 2013, at 4:04 AM, Shrinand Javadekar  wrote:

> I had a similar problem. See [1]. The fix was to add delay_auth_decision = 1 
> in the proxy-server.conf
> 
> [filter:authtoken]
> ...
> delay_auth_decision = 1
> 
> -Shri
> [1] https://answers.launchpad.net/swift/+question/225614
> 
> 
> On Wed, Jul 10, 2013 at 4:43 AM, Morten Møller Riis  wrote:
> I've been looking at tempurl.py and found that the problem occurs here:
> 
> def _get_key(self, env, account):
> """
> Returns the X-Account-Meta-Temp-URL-Key header value for the
> account, or None if none is set.
> 
> :param env: The WSGI environment for the request.
> :param account: Account str.
> :returns: X-Account-Meta-Temp-URL-Key str value, or None.
> """
> key = None
> memcache = env.get('swift.cache')
> if memcache:
> key = memcache.get('temp-url-key/%s' % account)
> if not key:
> newenv = make_pre_authed_env(env, 'HEAD', '/v1/' + account,
>  self.agent)
> newenv['CONTENT_LENGTH'] = '0'
> newenv['wsgi.input'] = StringIO('')
> key = [None]
> 
> def _start_response(status, response_headers, exc_info=None):
> for h, v in response_headers:
> if h.lower() == 'x-account-meta-temp-url-key':
> key[0] = v
> 
> i = iter(self.app(newenv, _start_response))
> self.logger.info()
> try:
> i.next()
> except StopIteration:
> pass
> key = key[0]
> if key and memcache:
> memcache.set('temp-url-key/%s' % account, key, timeout=60)
> return key
> 
> The request get 403 forbidden and thus never gets the key in the first place. 
> I'm looking at the github repo and the implementation there seems to have 
> changed.
> 
> 
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
> 
> 
> 
> 
> On Jul 10, 2013, at 6:24 PM, Morten Møller Riis  wrote:
> 
>> I'm having trouble getting tempurl to work.
>> 
>> I set the "X-Account-Meta-Temp-Url-Key" metadata on the account. And a GET 
>> request shows it's set correctly.
>> 
>> I've enabled it on the proxy server in /etc/swift/proxy-server.conf:
>> 
>> [DEFAULT]
>> bind_port = 8080
>> workers = 8
>> user = swift
>> 
>> [pipeline:main]
>> pipeline = healthcheck cache tempurl swauth proxy-server
>> 
>> [app:proxy-server]
>> use = egg:swift#proxy
>> allow_account_management = true
>> account_autocreate = true
>> 
>> [filter:tempurl]
>> use = egg:swift#tempurl
>> 
>> [filter:swauth]
>> use = egg:swauth#swauth
>> set log_name = swauth
>> super_admin_key = 
>> default_swift_cluster = gigahost#https:///v1#http://localhost:8080/v1
>> 
>> [filter:healthcheck]
>> use = egg:swift#healthcheck
>> 
>> [filter:cache]
>> use = egg:swift#memcache
>> memcache_servers = 127.0.0.1:11211
>> 
>> When creating the tempurl's, even using the swift-temp-url program I get:
>> 
>> ~ $ curl -i 
>> "https:///v1/AUTH_224b1001-2c75-444c-aaef-30af13b9154c/000/206.pdf?temp_url_sig=387d79120a591e1cf6f4d4356f5c0a96fb49d202&temp_url_expires=1373438360"
>> HTTP/1.1 401 Unauthorized
>> Server: nginx
>> Date: Wed, 10 Jul 2013 08:21:32 GMT
>> Content-Type: text/plain
>> Content-Length: 35
>> Connection: keep-alive
>> 
>> 401 Unauthorized: Temp URL invalid
>> 
>> I've even tried running it locally on the proxy-server to localhost:8080, so 
>> I'm sure it's not nginx doing any funny stuff.
>> 
>> Does anybody have any suggestions? I'm pretty lost :(
>> 
>> 
>> Mvh / Best regards
>> Morten Møller Riis
>> Gigahost ApS
>> m...@gigahost.dk
>> 
>> 
>> 
>> 
>> ___
>> 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] Swift tempurl

[Morten Møller Riis]

This turned out to be a known issue with swath.

I upgraded to a newer version and the problem was resolved :)

Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk




On Jul 11, 2013, at 10:52 AM, Morten Møller Riis  wrote:

> I use swauth, and thus authtoken is not present in my pipeline. This might be 
> why I'm seeing the problem actually.
> 
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
> 
> 
> 
> 
> On Jul 11, 2013, at 4:04 AM, Shrinand Javadekar  
> wrote:
> 
>> I had a similar problem. See [1]. The fix was to add delay_auth_decision = 1 
>> in the proxy-server.conf
>> 
>> [filter:authtoken]
>> ...
>> delay_auth_decision = 1
>> 
>> -Shri
>> [1] https://answers.launchpad.net/swift/+question/225614
>> 
>> 
>> On Wed, Jul 10, 2013 at 4:43 AM, Morten Møller Riis  wrote:
>> I've been looking at tempurl.py and found that the problem occurs here:
>> 
>> def _get_key(self, env, account):
>> """
>> Returns the X-Account-Meta-Temp-URL-Key header value for the
>> account, or None if none is set.
>> 
>> :param env: The WSGI environment for the request.
>> :param account: Account str.
>> :returns: X-Account-Meta-Temp-URL-Key str value, or None.
>> """
>> key = None
>> memcache = env.get('swift.cache')
>> if memcache:
>> key = memcache.get('temp-url-key/%s' % account)
>> if not key:
>> newenv = make_pre_authed_env(env, 'HEAD', '/v1/' + account,
>>  self.agent)
>> newenv['CONTENT_LENGTH'] = '0'
>> newenv['wsgi.input'] = StringIO('')
>> key = [None]
>> 
>> def _start_response(status, response_headers, exc_info=None):
>> for h, v in response_headers:
>> if h.lower() == 'x-account-meta-temp-url-key':
>> key[0] = v
>> 
>> i = iter(self.app(newenv, _start_response))
>> self.logger.info()
>> try:
>> i.next()
>> except StopIteration:
>> pass
>> key = key[0]
>> if key and memcache:
>> memcache.set('temp-url-key/%s' % account, key, timeout=60)
>> return key
>> 
>> The request get 403 forbidden and thus never gets the key in the first 
>> place. I'm looking at the github repo and the implementation there seems to 
>> have changed.
>> 
>> 
>> Mvh / Best regards
>> Morten Møller Riis
>> Gigahost ApS
>> m...@gigahost.dk
>> 
>> 
>> 
>> 
>> On Jul 10, 2013, at 6:24 PM, Morten Møller Riis  wrote:
>> 
>>> I'm having trouble getting tempurl to work.
>>> 
>>> I set the "X-Account-Meta-Temp-Url-Key" metadata on the account. And a GET 
>>> request shows it's set correctly.
>>> 
>>> I've enabled it on the proxy server in /etc/swift/proxy-server.conf:
>>> 
>>> [DEFAULT]
>>> bind_port = 8080
>>> workers = 8
>>> user = swift
>>> 
>>> [pipeline:main]
>>> pipeline = healthcheck cache tempurl swauth proxy-server
>>> 
>>> [app:proxy-server]
>>> use = egg:swift#proxy
>>> allow_account_management = true
>>> account_autocreate = true
>>> 
>>> [filter:tempurl]
>>> use = egg:swift#tempurl
>>> 
>>> [filter:swauth]
>>> use = egg:swauth#swauth
>>> set log_name = swauth
>>> super_admin_key = 
>>> default_swift_cluster = gigahost#https:///v1#http://localhost:8080/v1
>>> 
>>> [filter:healthcheck]
>>> use = egg:swift#healthcheck
>>> 
>>> [filter:cache]
>>> use = egg:swift#memcache
>>> memcache_servers = 127.0.0.1:11211
>>> 
>>> When creating the tempurl's, even using the swift-temp-url program I get:
>>> 
>>> ~ $ curl -i 
>>> "https:///v1/AUTH_224b1001-2c75-444c-aaef-30af13b9154c/000/206.pdf?temp_url_sig=387d79120a591e1cf6f4d4356f5c0a96fb49d202&temp_url_expires=1373438360"
>>> HTTP/1.1 401 Unauthorized
>>> Server: nginx
>>> Date: Wed, 10 Jul 2013 08:21:32 GMT
>>> Content-Type: text/plain
>>> Content-Length: 35
>>> Connection: keep-alive
>>> 
>>> 401 Unauthorized: Temp URL invalid
>>> 
>>> I've even tried running it locally on the proxy-server to localhost:8080, 
>>> so I'm sure it's not nginx doing any funny stuff.
>>> 
>>> Does anybody have any suggestions? I'm pretty lost :(
>>> 
>>> 
>>> Mvh / Best regards
>>> Morten Møller Riis
>>> Gigahost ApS
>>> m...@gigahost.dk
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> 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@li

[Openstack] VM do not get ip when use quantum

[jt628910]

hi all:
OS : rhel6.4
openstack version:Gizzly

install quantum with doc  
:http://docs.openstack.org/grizzly/openstack-network/admin/content/

service  quantum-l3-agent  status
quantum-l3-agent dead，but pid exit

In dashboard ,when i add a instance  ,  it show that this instance  have added 
a ip such as 192.168.10.2

but   in vm  ,I do not see eth0  have this IP

tailf /var/log/quantum/dhcp-agent.log 

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/quantum/agent/dhcp_agent.py", line 
131, in call_driver
getattr(driver, action)()
  File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 
124, in enable
reuse_existing=True)
  File "/usr/lib/python2.6/site-packages/quantum/agent/dhcp_agent.py", line 
554, in setup
namespace=namespace)
  File "/usr/lib/python2.6/site-packages/quantum/agent/linux/interface.py", 
line 181, in plug
ns_dev.link.set_address(mac_address)
  File "/usr/lib/python2.6/site-packages/quantum/agent/linux/ip_lib.py", line 
180, in set_address
self._as_root('set', self.name, 'address', mac_address)
  File "/usr/lib/python2.6/site-packages/quantum/agent/linux/ip_lib.py", line 
167, in _as_root
kwargs.get('use_root_namespace', False))
  File "/usr/lib/python2.6/site-packages/quantum/agent/linux/ip_lib.py", line 
47, in _as_root
namespace)
  File "/usr/lib/python2.6/site-packages/quantum/agent/linux/ip_lib.py", line 
58, in _execute
root_helper=root_helper)
  File "/usr/lib/python2.6/site-packages/quantum/agent/linux/utils.py", line 
61, in execute
raise RuntimeError(m)
RuntimeError: 
Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 
'link', 'set', 'tapbf9a2991-33', 'address', 'fa:16:3e:a7:ea:91']
Exit code: 2
Stdout: ''
Stderr: 'RTNETLINK answers: Device or resource busy\n'


what happen about this?  



ttjiang___
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] [Swift] Breakpoint resume with tempurl

[Jonathan Lu]

Hi, all stackers,

I have realized downloading large object with tempurl 
middle-wareand want to support break-point resume. Has anyone got the 
experience of fulfilling break-point resume with tempurl in Swift?


Thanks,
Jonathan Lu
___
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] user cannot change there own password

[val john]

Hi.. guys

im running simple openstack cloud with 2 compute nodes im manually
creating  user accounts for users. but seems like users cant change there
own password .

im using Openstack folsom release , Please advice

Thank You
John
___
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] user cannot change there own password

[Ray Sun]

Yes, but there's already implemented in latest code.

See here:
http://www.sebastien-han.fr/blog/2013/06/17/some-horizon-enhancements/

Best Regards
-- Ray


On Thu, Jul 11, 2013 at 12:25 PM, val john  wrote:

> Hi.. guys
>
> im running simple openstack cloud with 2 compute nodes im manually
> creating  user accounts for users. but seems like users cant change there
> own password .
>
> im using Openstack folsom release , Please advice
>
> Thank You
> John
>
> ___
> 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] Exception during message handling on Cinder

[Mahardhika]

Hi, i've got it work when creating volume, but i can't attach to 
instance. error log from nova-compute :


/Stderr: 'iscsiadm: No session found.\n'/

i have run : iscsiadm -m node -o show
and it show it's values
On 7/10/2013 6:08 PM, claudio marques wrote:

Hi

I also found a problem a while a go with creating or managing volumes. 
After some research I could solve it by doing the following:


/vim /usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py/


remove line 388


385 self.tgtadm.create_iscsi_target(iscsi_name, iscsi_target,

386 0, volume_path, chap_auth,

387 check_exit_code=False*) <-- 
close here the method*


388 * old_name=old_name) --> (remove this line)*


restart all cinder services
/
/
/cd /etc/init.d/; for i in $( ls cinder-* ); do sudo service $i 
restart; done/


If that doesn't help, try to see your iscsitarget is up and running. 
See the logs.


Hope it help's

Cheer's

Claudio Marques

clau...@onesource.pt 
http://www.onesource.pt/



Date: Wed, 10 Jul 2013 16:36:49 +0700
From: mahardika.gil...@andalabs.com
To: openstack@lists.launchpad.net
Subject: [Openstack] Exception during message handling on Cinder

Hi, i've got this Error message in cinder-volume.log

ERROR [cinder.volume.iscsi] Failed to create iscsi target for volume 
id:volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd.
ERROR [cinder.volume.manager] volume 
volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd: create failed

ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling

i have check on cinder.conf, api-paste.ini files, let me know if you 
guys need my config file

please help me out of this
thanks
--
Regards,
Mahardhika Gilang

*PT. Andalabs Technology *
Gedung Gravira
Jl. Cideng Barat no. 54
Jakarta Pusat 10150

HP : 0852 139 55861
Email : mahardika.gil...@andalabs.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



--
Regards,
Mahardhika Gilang

*PT. Andalabs Technology *
Gedung Gravira
Jl. Cideng Barat no. 54
Jakarta Pusat 10150

HP : 0852 139 55861
Email : mahardika.gil...@andalabs.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] Exception during message handling on Cinder

[Hameedullah Khan]

Please check your iscsi_ip_address.

If that is not the issue can you please share more information? What iscsi
implementation are you using? Are you using tgt or iscsitarget? Can you
show your cinder.conf


On Thu, Jul 11, 2013 at 8:57 AM, Mahardhika
wrote:

>  Hi, i've got it work when creating volume, but i can't attach to
> instance. error log from nova-compute :
>
> *Stderr: 'iscsiadm: No session found.\n'*
>
> i have run : iscsiadm -m node -o show
> and it show it's values
>
> On 7/10/2013 6:08 PM, claudio marques wrote:
>
> Hi
>
>  I also found a problem a while a go with creating or managing volumes.
> After some research I could solve it by doing the following:
>
>  *vim /usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py*
>
>
>  remove line 388
>
>
>  385 self.tgtadm.create_iscsi_target(iscsi_name, iscsi_target,
>
> 386 0, volume_path, chap_auth,
>
> 387 check_exit_code=False*) <--
> close here the method*
>
> 388   *  old_name=old_name) -->
> (remove this line)*
>
>  restart all cinder services
> *
> *
> *cd /etc/init.d/; for i in $( ls cinder-* ); do sudo service $i restart;
> done*
>
>  If that doesn't help, try to see your iscsitarget is up and running. See
> the logs.
>
>  Hope it help's
>
>  Cheer's
>
>  Claudio Marques
>
>   clau...@onesource.pt
> http://www.onesource.pt/
>
>
>  --
> Date: Wed, 10 Jul 2013 16:36:49 +0700
> From: mahardika.gil...@andalabs.com
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Exception during message handling on Cinder
>
> Hi, i've got this Error message in cinder-volume.log
>
> ERROR [cinder.volume.iscsi] Failed to create iscsi target for volume
> id:volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd.
> ERROR [cinder.volume.manager] volume
> volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd: create failed
> ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling
>
> i have check on cinder.conf, api-paste.ini files, let me know if you guys
> need my config file
> please help me out of this
> thanks
> --
> Regards,
> Mahardhika Gilang
>
> *PT. Andalabs Technology *
> Gedung Gravira
> Jl. Cideng Barat no. 54
> Jakarta Pusat 10150
>
> HP : 0852 139 55861
> Email : mahardika.gil...@andalabs.com
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
>
>
> --
> Regards,
> Mahardhika Gilang
>
> *PT. Andalabs Technology *
> Gedung Gravira
> Jl. Cideng Barat no. 54
> Jakarta Pusat 10150
>
> HP : 0852 139 55861
> Email : mahardika.gil...@andalabs.com
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp