[Openstack] How to purge old meter data of Ceilometer

2013-04-04 Thread Harri Pyy 
With the default 1 minute interval, Ceilometer collects quite large amounts of 
meter data.

Does Ceilometer provide a TTL configuration option for the meter data, or some 
other functionality or API for purging old meter data?
 
Thanks for any help,
Harri


___
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] How to purge old meter data of Ceilometer

2013-04-04 Thread Julien Danjou 
On Thu, Apr 04 2013, Harri Pyy wrote:

> With the default 1 minute interval, Ceilometer collects quite large amounts 
> of meter data.
>
> Does Ceilometer provide a TTL configuration option for the meter data, or
> some other functionality or API for purging old meter data?

Not yet unfortunately.

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


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

[Openstack] Could not connect to VM

2013-04-04 Thread Avi Bashan 
Hello,

I'm having some issues with ping or connecting with SSH to A vm after
creation.

My setup is
- 1 controller node + networking node
- 2 compute nodes

all are running ubuntu 12.04

when trying to ping a vm after creation i get the following output:

ping 50.50.1.3
PING 50.50.1.3 (50.50.1.3) 56(84) bytes of data.
>From 109.226.32.198 icmp_seq=1 Destination Host Unreachable

I can see from the horizon console log that the vm is not getting an ip
address from the metaserver:

wget: can't connect to remote host (169.254.169.254): Network is unreachable

Any help would be very appreciated.

i'm attaching the ifconfig and ovs-vsctl show of the controller
node+network and 1 of the computer nodes.

Thanks,
Avi


controller node+network:

br-ex Link encap:Ethernet  HWaddr ac:16:2d:76:03:b8
  inet6 addr: fe80::c494:14ff:fee2:ff34/64 Scope:Link
  UP BROADCAST RUNNING  MTU:1500  Metric:1
  RX packets:351438 errors:0 dropped:83332 overruns:0 frame:0
  TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:21670232 (21.6 MB)  TX bytes:888 (888.0 B)

br-intLink encap:Ethernet  HWaddr 42:98:14:5a:c7:45
  inet6 addr: fe80::852:35ff:fef8:c0d/64 Scope:Link
  UP BROADCAST RUNNING  MTU:1500  Metric:1
  RX packets:266 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:12828 (12.8 KB)  TX bytes:468 (468.0 B)

br-tunLink encap:Ethernet  HWaddr 3e:6f:76:b8:33:4d
  inet6 addr: fe80::e4be:9ff:fecd:3d69/64 Scope:Link
  UP BROADCAST RUNNING  MTU:1500  Metric:1
  RX packets:115 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:5706 (5.7 KB)  TX bytes:468 (468.0 B)

eth0  Link encap:Ethernet  HWaddr ac:16:2d:76:03:b8
  inet6 addr: fe80::ae16:2dff:fe76:3b8/64 Scope:Link
  UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
  RX packets:355057 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1481 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:23583676 (23.5 MB)  TX bytes:109191 (109.1 KB)
  Interrupt:32

eth1  Link encap:Ethernet  HWaddr ac:16:2d:76:03:b9
  inet addr:172.16.20.1  Bcast:172.16.20.255  Mask:255.255.255.0
  inet6 addr: fe80::ae16:2dff:fe76:3b9/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1217937 errors:0 dropped:0 overruns:0 frame:0
  TX packets:965032 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:348242626 (348.2 MB)  TX bytes:741457958 (741.4 MB)
  Interrupt:36

eth3  Link encap:Ethernet  HWaddr ac:16:2d:76:03:bb
  inet addr:109.226.32.196  Bcast:109.226.32.223
 Mask:255.255.255.224
  inet6 addr: fe80::ae16:2dff:fe76:3bb/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:641690 errors:0 dropped:0 overruns:0 frame:0
  TX packets:153774 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:338543594 (338.5 MB)  TX bytes:31423041 (31.4 MB)
  Interrupt:36

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:39225048 errors:0 dropped:0 overruns:0 frame:0
  TX packets:39225048 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:8572204782 (8.5 GB)  TX bytes:8572204782 (8.5 GB)

tapb6bae46b-75 Link encap:Ethernet  HWaddr fa:16:3e:04:79:73
  inet addr:50.50.1.2  Bcast:50.50.1.255  Mask:255.255.255.0
  inet6 addr: fe80::9004:22ff:fee3:6bc1/64 Scope:Link
  UP BROADCAST RUNNING  MTU:1500  Metric:1
  RX packets:18 errors:0 dropped:0 overruns:0 frame:0
  TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:1056 (1.0 KB)  TX bytes:1098 (1.0 KB)


ovs-vsctl show
1f989ce1-998a-45a7-8eef-e0bda6d8ecc8
Bridge br-int
Port "qr-721fe4cd-9d"
Interface "qr-721fe4cd-9d"
type: internal
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "tapb6bae46b-75"
tag: 2
Interface "tapb6bae46b-75"
type: internal
Bridge br-tun
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "gre-4"
Interface "gre-4"

[Openstack] Swift proxy and swift-informant

2013-04-04 Thread Giovanni Colapinto 
Hi to all.

I try to configure swift proxy to work with swift-informant.

I've installed swift-informant and add/modify the following section to
/etc/swift/proxy-server.conf:

[pipeline:main]
pipeline = informant healthcheck cache swift3 authtoken keystone
proxy-server

[filter:informant]
use = egg:informant#informant
statsd_host = 10.0.1.154
metric_name_prepend = inndig.

When I start proxy-server it returns the following error:

Traceback (most recent call last):
  File "/usr/bin/swift-proxy-server", line 22, in 
run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 138,
in run_wsgi
loadapp('config:%s' % conf_file, global_conf={'log_name': log_name})
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
247, in loadapp
return loadobj(APP, uri, name=name, **kw)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
271, in loadobj
global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
296, in loadcontext
global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
320, in _loadconfig
return loader.get_context(object_type, name, global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
450, in get_context
global_additions=global_additions)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
562, in _pipeline_app_context
for name in pipeline[:-1]]
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
454, in get_context
section)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
476, in _context_from_use
object_type, name=use, global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
406, in get_context
global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
296, in loadcontext
global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
328, in _loadegg
return loader.get_context(object_type, name, global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
620, in get_context
object_type, name=name)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
646, in find_egg_entry_point
possible.append((entry.load(), protocol, entry.name))
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2017, in
load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File
"/usr/local/lib/python2.7/dist-packages/informant-0.0.10-py2.7.egg/informant/middleware.py",
line 16, in 
from swift.common.swob import Request
ImportError: No module named swob

Searching on google I understand that swob is a module of swift >= 1.7.5,
but on my ubuntu 12.10 swift is 1.7.4

How can I resolv this situation? Is there a way to upgrade swift?

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

[Openstack] New schema for LDAP + Keystone Grizzly?

2013-04-04 Thread Marcelo Mariano Miziara 

Hello to all!Before the release of version grizzly 3, the suggested schema in the openstack documentation (http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-keystone-for-ldap-backend.html) worked fine. This is the suggested schema:dn: cn=openstack,cn=org
dc: openstack
objectClass: dcObject
objectClass: organizationalUnit
ou: openstack

dn: ou=Groups,cn=openstack,cn=org
objectClass: top
objectClass: organizationalUnit
ou: groups

dn: ou=Users,cn=openstack,cn=org
objectClass: top
objectClass: organizationalUnit
ou: users

dn: ou=Roles,cn=openstack,cn=org
objectClass: top
objectClass: organizationalUnit
ou: rolesBut after the release of the version grizzly 3 I think that's not enough anymore, mainly because of the "domain" concept.I'm kind of lost trying to make LDAP work with keystone now...does anyone succeed in this? I created a new dn, something like:dn: ou=Domains,cn=openstack,cn=org
objectClass: top
objectClass: organizationalUnit
ou: Domains
But when I run the "keystone-manage db_sync" the "default" domain isn't created in the LDAP...When I manually create the domain in there, I have a problem with authentication...I think I must be doing something wrong, does anyone have a light?Thanks in advance,Marcelo M. Miziara
marcelo.mizi...@serpro.gov.br


-


"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada exclusivamente a seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."

"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."




___
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 proxy and swift-informant

2013-04-04 Thread Tong Li 

swob is not a separate package, it is part of the swift core. You may
either get older version of informant which does not use swob or upgrade
swift.

Tong Li
Emerging Technologies & Standards
Building 501/B205
liton...@us.ibm.com



From:   Giovanni Colapinto 
To: openstack@lists.launchpad.net,
Date:   04/04/2013 04:26 AM
Subject:[Openstack] Swift proxy and swift-informant
Sent by:openstack-bounces+litong01=us.ibm@lists.launchpad.net



Hi to all.

I try to configure swift proxy to work with swift-informant.

I've installed swift-informant and add/modify the following section
to /etc/swift/proxy-server.conf:

[pipeline:main]
pipeline = informant healthcheck cache swift3 authtoken keystone
proxy-server

[filter:informant]
use = egg:informant#informant
statsd_host = 10.0.1.154
metric_name_prepend = inndig.

When I start proxy-server it returns the following error:

Traceback (most recent call last):
  File "/usr/bin/swift-proxy-server", line 22, in 
    run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 138,
in run_wsgi
    loadapp('config:%s' % conf_file, global_conf={'log_name': log_name})
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
247, in loadapp
    return loadobj(APP, uri, name=name, **kw)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
271, in loadobj
    global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
296, in loadcontext
    global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
320, in _loadconfig
    return loader.get_context(object_type, name, global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
450, in get_context
    global_additions=global_additions)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
562, in _pipeline_app_context
    for name in pipeline[:-1]]
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
454, in get_context
    section)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
476, in _context_from_use
    object_type, name=use, global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
406, in get_context
    global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
296, in loadcontext
    global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
328, in _loadegg
    return loader.get_context(object_type, name, global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
620, in get_context
    object_type, name=name)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
646, in find_egg_entry_point
    possible.append((entry.load(), protocol, entry.name))
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2017, in
load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File
"/usr/local/lib/python2.7/dist-packages/informant-0.0.10-py2.7.egg/informant/middleware.py",
 line 16, in 
    from swift.common.swob import Request
ImportError: No module named swob

Searching on google I understand that swob is a module of swift >= 1.7.5,
but on my ubuntu 12.10 swift is 1.7.4

How can I resolv this situation? Is there a way to upgrade swift?

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

Re: [Openstack] Swift proxy and swift-informant

2013-04-04 Thread Giovanni Colapinto 
Thank you for the reply. How I can upgrade swift?


On Thu, Apr 4, 2013 at 3:12 PM, Tong Li  wrote:

> swob is not a separate package, it is part of the swift core. You may
> either get older version of informant which does not use swob or upgrade
> swift.
>
> Tong Li
> Emerging Technologies & Standards
> Building 501/B205
> liton...@us.ibm.com
>
> [image: Inactive hide details for Giovanni Colapinto ---04/04/2013
> 04:26:57 AM---Hi to all. I try to configure swift proxy to work with]Giovanni
> Colapinto ---04/04/2013 04:26:57 AM---Hi to all. I try to configure swift
> proxy to work with swift-informant.
>
> From: Giovanni Colapinto 
> To: openstack@lists.launchpad.net,
> Date: 04/04/2013 04:26 AM
> Subject: [Openstack] Swift proxy and swift-informant
> Sent by: openstack-bounces+litong01=us.ibm@lists.launchpad.net
> --
>
>
>
> Hi to all.
>
> I try to configure swift proxy to work with swift-informant.
>
> I've installed swift-informant and add/modify the following section to
> /etc/swift/proxy-server.conf:
>
> [pipeline:main]
> pipeline = informant healthcheck cache swift3 authtoken keystone
> proxy-server
>
> [filter:informant]
> use = egg:informant#informant
> statsd_host = 10.0.1.154
> metric_name_prepend = inndig.
>
> When I start proxy-server it returns the following error:
>
> Traceback (most recent call last):
>   File "/usr/bin/swift-proxy-server", line 22, in 
> run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
>   File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 138,
> in run_wsgi
> loadapp('config:%s' % conf_file, global_conf={'log_name': log_name})
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 247, in loadapp
> return loadobj(APP, uri, name=name, **kw)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 271, in loadobj
> global_conf=global_conf)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 296, in loadcontext
> global_conf=global_conf)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 320, in _loadconfig
> return loader.get_context(object_type, name, global_conf)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 450, in get_context
> global_additions=global_additions)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 562, in _pipeline_app_context
> for name in pipeline[:-1]]
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 454, in get_context
> section)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 476, in _context_from_use
> object_type, name=use, global_conf=global_conf)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 406, in get_context
> global_conf=global_conf)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 296, in loadcontext
> global_conf=global_conf)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 328, in _loadegg
> return loader.get_context(object_type, name, global_conf)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 620, in get_context
> object_type, name=name)
>   File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
> 646, in find_egg_entry_point
> possible.append((entry.load(), protocol, *entry.name*
> ))
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2017, in
> load
> entry = __import__(self.module_name, globals(),globals(), ['__name__'])
>   File
> "/usr/local/lib/python2.7/dist-packages/informant-0.0.10-py2.7.egg/informant/middleware.py",
> line 16, in 
> from swift.common.swob import Request
> ImportError: No module named swob
>
> Searching on google I understand that swob is a module of swift >= 1.7.5,
> but on my ubuntu 12.10 swift is 1.7.4
>
> How can I resolv this situation? Is there a way to upgrade swift?
>
> 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] OpenStack on two physical servers - devstack

2013-04-04 Thread Andy Holt 
Hello all.

For getting a 'full' OpenStack environment up and running for testing and
semi-serious use, with two physical servers (to enable redundancy), is
devstack still the way to go?

thanks,Andy
___
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 proxy and swift-informant

2013-04-04 Thread Tong Li 

on ubuntu, you can try the following.

apt-get install python-software-properties
add-apt-repository ppa:swift-core/release
apt-get update
apt-get install swift python-swiftclient

Also look into the doc at this link.
http://docs.openstack.org/developer/swift/howto_installmultinode.html

If you want to use the latest swift code, you can get the code from github
and build it yourself but I would not recommend to do it for the production
system.

Hope that helps.

Tong Li
Emerging Technologies & Standards
Building 501/B205
liton...@us.ibm.com



From:   Giovanni Colapinto 
To: Tong Li/Raleigh/IBM@IBMUS,
Cc: openstack@lists.launchpad.net, openstack-bounces
+litong01=us.ibm@lists.launchpad.net
Date:   04/04/2013 09:20 AM
Subject:Re: [Openstack] Swift proxy and swift-informant



Thank you for the reply. How I can upgrade swift?


On Thu, Apr 4, 2013 at 3:12 PM, Tong Li  wrote:
  swob is not a separate package, it is part of the swift core. You may
  either get older version of informant which does not use swob or upgrade
  swift.

  Tong Li
  Emerging Technologies & Standards
  Building 501/B205
  liton...@us.ibm.com

  Inactive hide details for Giovanni Colapinto ---04/04/2013 04:26:57
  AM---Hi to all. I try to configure swift proxy to work withGiovanni
  Colapinto ---04/04/2013 04:26:57 AM---Hi to all. I try to configure swift
  proxy to work with swift-informant.

  From: Giovanni Colapinto 
  To: openstack@lists.launchpad.net,
  Date: 04/04/2013 04:26 AM
  Subject: [Openstack] Swift proxy and swift-informant
  Sent by: openstack-bounces+litong01=us.ibm@lists.launchpad.net




  Hi to all.

  I try to configure swift proxy to work with swift-informant.

  I've installed swift-informant and add/modify the following section
  to /etc/swift/proxy-server.conf:

  [pipeline:main]
  pipeline = informant healthcheck cache swift3 authtoken keystone
  proxy-server

  [filter:informant]
  use = egg:informant#informant
  statsd_host = 10.0.1.154
  metric_name_prepend = inndig.

  When I start proxy-server it returns the following error:

  Traceback (most recent call last):
    File "/usr/bin/swift-proxy-server", line 22, in 
      run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
    File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 138,
  in run_wsgi
      loadapp('config:%s' % conf_file, global_conf={'log_name': log_name})
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  247, in loadapp
      return loadobj(APP, uri, name=name, **kw)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  271, in loadobj
      global_conf=global_conf)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  296, in loadcontext
      global_conf=global_conf)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  320, in _loadconfig
      return loader.get_context(object_type, name, global_conf)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  450, in get_context
      global_additions=global_additions)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  562, in _pipeline_app_context
      for name in pipeline[:-1]]
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  454, in get_context
      section)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  476, in _context_from_use
      object_type, name=use, global_conf=global_conf)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  406, in get_context
      global_conf=global_conf)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  296, in loadcontext
      global_conf=global_conf)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  328, in _loadegg
      return loader.get_context(object_type, name, global_conf)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  620, in get_context
      object_type, name=name)
    File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line
  646, in find_egg_entry_point
      possible.append((entry.load(), protocol, entry.name))
    File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2017, in
  load
      entry = __import__(self.module_name, globals(),globals(),
  ['__name__'])
    File
  
"/usr/local/lib/python2.7/dist-packages/informant-0.0.10-py2.7.egg/informant/middleware.py",
 line 16, in 
      from swift.common.swob import Request
  ImportError: No module named swob

  Searching on google I understand that swob is a module of swift >= 1.7.5,
  but on my ubuntu 12.10 swift is 1.7.4

  How can I resolv this situation? Is there a way to upgrade swift?

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

[Openstack] OpenStack 2013.1 ("Grizzly") is released !

2013-04-04 Thread Thierry Carrez 
Hello everyone,

The "Grizzly" development cycle, started 6 months ago, ends today with
the immediate release of OpenStack 2013.1. It is the result of the work
of 550 different people who contributed code, documentation, or
infrastructure configurations. This amazing journey saw the
implementation of 232 blueprints and the fixing of 1900 bugs within the
7 integrated projects alone.

You can find source tarballs for each integrated project, together with
lists of features and bugfixes, at:

OpenStack Compute:https://launchpad.net/nova/grizzly/2013.1
OpenStack Object Storage: https://launchpad.net/swift/grizzly/1.8.0
OpenStack Image Service:  https://launchpad.net/glance/grizzly/2013.1
OpenStack Networking: https://launchpad.net/quantum/grizzly/2013.1
OpenStack Block Storage:  https://launchpad.net/cinder/grizzly/2013.1
OpenStack Identity:   https://launchpad.net/keystone/grizzly/2013.1
OpenStack Dashboard:  https://launchpad.net/horizon/grizzly/2013.1

The Grizzly Release Notes contain an overview of the key features, as
well as upgrade notes and current lists of known issues. You can access
them at: https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly

In 11 days our community will gather in Portland, OR for the OpenStack
Summit: 4 days of conference to discuss the state of OpenStack and a
Design Summit to plan the next 6-month development cycle, codenamed
"Havana". See https://www.openstack.org/summit/portland-2013/ for more
details.

Congratulations everyone on this awesome release !

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
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-announce] OpenStack 2013.1 ("Grizzly") is released !

2013-04-04 Thread Mark Collier 

Amazing accomplishment everyone!  I just posted a blog post with a few 
highlights and included a link to your message, Thierry.
 
http://www.openstack.org/blog/2013/04/openstack-grizzly/
 


 
On Thursday, April 4, 2013 9:47am, "Thierry Carrez"  
said:



> Hello everyone,
> 
> The "Grizzly" development cycle, started 6 months ago, ends today with
> the immediate release of OpenStack 2013.1. It is the result of the work
> of 550 different people who contributed code, documentation, or
> infrastructure configurations. This amazing journey saw the
> implementation of 232 blueprints and the fixing of 1900 bugs within the
> 7 integrated projects alone.
> 
> You can find source tarballs for each integrated project, together with
> lists of features and bugfixes, at:
> 
> OpenStack Compute:https://launchpad.net/nova/grizzly/2013.1
> OpenStack Object Storage: https://launchpad.net/swift/grizzly/1.8.0
> OpenStack Image Service:  https://launchpad.net/glance/grizzly/2013.1
> OpenStack Networking: https://launchpad.net/quantum/grizzly/2013.1
> OpenStack Block Storage:  https://launchpad.net/cinder/grizzly/2013.1
> OpenStack Identity:   https://launchpad.net/keystone/grizzly/2013.1
> OpenStack Dashboard:  https://launchpad.net/horizon/grizzly/2013.1
> 
> The Grizzly Release Notes contain an overview of the key features, as
> well as upgrade notes and current lists of known issues. You can access
> them at: https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly
> 
> In 11 days our community will gather in Portland, OR for the OpenStack
> Summit: 4 days of conference to discuss the state of OpenStack and a
> Design Summit to plan the next 6-month development cycle, codenamed
> "Havana". See https://www.openstack.org/summit/portland-2013/ for more
> details.
> 
> Congratulations everyone on this awesome release !
> 
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
> 
> ___
> OpenStack-announce mailing list
> openstack-annou...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce
>___
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] Ceilometer 2013.1 released

2013-04-04 Thread Julien Danjou 
Hello,

Ceilometer 2013.1 has been released, ending the Grizzly development
cycle where we were an incubated project, and became an integrated one
for the Havana cycle.

The tarball can be found with the list of features and bugfixes here:

https://launchpad.net/ceilometer/grizzly/2013.1

Congratulations to everyone for this!

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


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

Re: [Openstack] How to purge old meter data of Ceilometer

2013-04-04 Thread Doug Hellmann 
I created a blueprint for this:
https://blueprints.launchpad.net/ceilometer/+spec/purge-data


On Thu, Apr 4, 2013 at 4:06 AM, Julien Danjou  wrote:

> On Thu, Apr 04 2013, Harri Pyy wrote:
>
> > With the default 1 minute interval, Ceilometer collects quite large
> amounts of meter data.
> >
> > Does Ceilometer provide a TTL configuration option for the meter data, or
> > some other functionality or API for purging old meter data?
>
> Not yet unfortunately.
>
> --
> Julien Danjou
> ;; Free Software hacker ; freelance consultant
> ;; http://julien.danjou.info
>
> ___
> 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] [Nova] Creating instances with custom UUIDs

2013-04-04 Thread Joe Gordon 
On Wed, Apr 3, 2013 at 7:05 PM, Chris Behrens  wrote:

> I'm having a hard time understanding the original problem.  nova boot
> should return in milliseconds.  There's no blocking on provisioning.
>
>
The only thing that could block is DB access, as AFAIK the RPC to the
scheduler is still pass by reference.

- Chris
>
> On Apr 3, 2013, at 8:32 PM, Rafael Rosa  wrote:
>
> API wise I was thinking about something like "nova boot
> --custom-instance-uuid ABC..." or something like that. To avoid problems
> with any current implementation I would set it to disabled by default and
> add a config option to enable it.
>
> As for collisions, my take is that if you're passing a custom UUID you
> know what you're doing and is generating them in a way that won't be
> duplicated. Just by using standard UUID generators the possibility of
> collisions are really really small.
>
> Thanks for the feeback :)
>
> Rafael Rosa Fu
>
>
> 2013/4/3 Michael Still 
>
>> On Thu, Apr 4, 2013 at 9:16 AM, Rafael Rosa 
>> wrote:
>> > Hi,
>> >
>> > In our OpenStack installation we have an issue when creating new
>> instances,
>> > we need to execute some long running processes before calling "nova
>> boot"
>> > and the call blocks for the end user for a while. We would like to
>> return
>> > "immediately" to the caller with a final instance UUID and do the work
>> on
>> > the background, but it's only generated when during actual instance
>> > creation, which is a no go in our situation.
>>
>> The instance_create database call already accepts an instance UUID as
>> an argument, so that bit looks like it should work out well for you.
>> So, I guess this is mostly a case of working out how you want the API
>> to work.
>>
>> Personally, I would have no problem with something like this, so long
>> as we could somehow "reserve" the instance UUID so that another caller
>> doesn't try and create an instance with the same UUID while you're
>> doing your slow thing.
>>
>> Cheers,
>> Michael
>>
>
> ___
> 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] [Quantum] Anybody implemented DMZ?

2013-04-04 Thread Aaron Rosen 
Hi David,

The quantum network node would route traffic between the non-DMZ-DMZ
network if both of those subnets are uplinked to the same quantum router. I
believe if you create another router for your dmz hosts then traffic in/out
of that network should route our to your physical infrastructure which will
go through your router to do filtering.

Thanks,

Aaron


On Wed, Apr 3, 2013 at 8:26 AM, David Kang  wrote:

>
>  Hi,
>
>  We are trying to set up Quantum network for non-DMZ and DMZ networks.
> The cloud has both non-DMZ networks and a DMZ network.
> We need to route traffic from DMZ network to a specific router before it
> reaches
> anywhere else in non-DMZ networks.
> However, Quantum Network Node routes the traffic between DMZ network and
> non-DMZ network within itself by default.
> Have anybody configured Quantum for this case?
> Any help will be appreciated.
> We are using Quantum linuxbridge-agent.
>
>  Thanks,
>  David
>
> --
> --
> Dr. Dong-In "David" Kang
> Computer Scientist
> USC/ISI
>
> ___
> 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] [Quantum] Anybody implemented DMZ?

2013-04-04 Thread David Kang 

 
 Hi Aron,

 Thank you for your reply.

 We deploy one (quantum) subnet as a DMZ network and the other (quantum) subnet
as a non-DMZ network.
They are routed to the network node where quantum services (dhcp, l3, 
linuxbridge)
are running.
They can talk each other through network node, now.

 However, we do not want to the network node to route the traffic between them 
directly.
Instead we want them to be routed to different (external) routers such that
we can apply filtering/firewall/etc. on the traffic from DMZ network.

 Do you think is it possible using two l3-agents or any other way?
Currently, I manually set up routings for those two subnets.

 Thanks,
 David

- Original Message -
> Hi David,
> 
> 
> The quantum network node would route traffic between the non-DMZ-DMZ
> network if both of those subnets are uplinked to the same quantum
> router. I believe if you create another router for your dmz hosts then
> traffic in/out of that network should route our to your physical
> infrastructure which will go through your router to do filtering.
> 
> 
> Thanks,
> 
> 
> Aaron
> 
> 
> 
> On Wed, Apr 3, 2013 at 8:26 AM, David Kang < dk...@isi.edu > wrote:
> 
> 
> 
> Hi,
> 
> We are trying to set up Quantum network for non-DMZ and DMZ networks.
> The cloud has both non-DMZ networks and a DMZ network.
> We need to route traffic from DMZ network to a specific router before
> it reaches
> anywhere else in non-DMZ networks.
> However, Quantum Network Node routes the traffic between DMZ network
> and
> non-DMZ network within itself by default.
> Have anybody configured Quantum for this case?
> Any help will be appreciated.
> We are using Quantum linuxbridge-agent.
> 
> Thanks,
> David
> 
> --
> --
> Dr. Dong-In "David" Kang
> Computer Scientist
> USC/ISI
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp

-- 
--
Dr. Dong-In "David" Kang
Computer Scientist
USC/ISI

___
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] Gerrit Review + SSH

2013-04-04 Thread Ronak Shah 
Hi,

As OS dev cycle involves Gerrit review tool which requires ssh into the
gerrit server, I was wondering if any of you guys face problems where your
company/org does not allow ssh to external hosts.

In general, what is the best practice in terms of environment for
generating code review?

I appreciate the response in advance.

Thanks,
Ronak
___
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] Anybody implemented DMZ?

2013-04-04 Thread Aaron Rosen 
In my reply I suggested you to create two quantum routers which I believe
should solve this for you.


quantum net-create DMZ-net --external=True
quantum subnet-create --name DMZ-Subnet1 DMZ-net # Public ip
pool
quantum net-create non-DMZ  --external=True
quantum subnet-create --name nonDMZ-Subnet1 non-DMZ  #
Public ip pool


quantum router-create DMZ-router
quantum router-create non-DMZ-router
quantum router-interface-add DMZ-router DMZ DMZ-Subnet1
quantum router-interface-add non-DMZ-router  nonDMZ-Subnet1

quantum router-gateway-set  DMZ-router DMZ-net
quantum router-gateway-set   non-DMZ-router  non-DMZ


On Thu, Apr 4, 2013 at 10:51 AM, David Kang  wrote:

>
>
>  Hi Aron,
>
>  Thank you for your reply.
>
>  We deploy one (quantum) subnet as a DMZ network and the other (quantum)
> subnet
> as a non-DMZ network.
> They are routed to the network node where quantum services (dhcp, l3,
> linuxbridge)
> are running.
> They can talk each other through network node, now.
>
>  However, we do not want to the network node to route the traffic between
> them directly.
> Instead we want them to be routed to different (external) routers such that
> we can apply filtering/firewall/etc. on the traffic from DMZ network.
>
>  Do you think is it possible using two l3-agents or any other way?
> Currently, I manually set up routings for those two subnets.
>
>  Thanks,
>  David
>
> - Original Message -
> > Hi David,
> >
> >
> > The quantum network node would route traffic between the non-DMZ-DMZ
> > network if both of those subnets are uplinked to the same quantum
> > router. I believe if you create another router for your dmz hosts then
> > traffic in/out of that network should route our to your physical
> > infrastructure which will go through your router to do filtering.
> >
> >
> > Thanks,
> >
> >
> > Aaron
> >
> >
> >
> > On Wed, Apr 3, 2013 at 8:26 AM, David Kang < dk...@isi.edu > wrote:
> >
> >
> >
> > Hi,
> >
> > We are trying to set up Quantum network for non-DMZ and DMZ networks.
> > The cloud has both non-DMZ networks and a DMZ network.
> > We need to route traffic from DMZ network to a specific router before
> > it reaches
> > anywhere else in non-DMZ networks.
> > However, Quantum Network Node routes the traffic between DMZ network
> > and
> > non-DMZ network within itself by default.
> > Have anybody configured Quantum for this case?
> > Any help will be appreciated.
> > We are using Quantum linuxbridge-agent.
> >
> > Thanks,
> > David
> >
> > --
> > --
> > Dr. Dong-In "David" Kang
> > Computer Scientist
> > USC/ISI
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help : https://help.launchpad.net/ListHelp
>
> --
> --
> Dr. Dong-In "David" Kang
> Computer Scientist
> USC/ISI
>
___
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] Gerrit Review + SSH

2013-04-04 Thread Jeremy Stanley 
On 2013-04-04 10:51:20 -0700 (-0700), Ronak Shah wrote:
> As OS dev cycle involves Gerrit review tool which requires ssh
> into the gerrit server, I was wondering if any of you guys face
> problems where your company/org does not allow ssh to external
> hosts.
[...]

It usually involves the uphill battle of convincing whoever manages
network security/firewalls/proxies for your employer that the
Internet is more than just a bunch of Web pages. Companies which
exclusively limit their employees to only browsing the Web are
basically cutting themselves off from innovations which rely on a
myriad of other protocols. For non-technology companies that might
be fine, but for a technology company that's often a sign that it's
going out of business pretty soon.
-- 
Jeremy Stanley

___
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] Gerrit Review + SSH

2013-04-04 Thread Jay Pipes 
On 04/04/2013 02:23 PM, Jeremy Stanley wrote:
> On 2013-04-04 10:51:20 -0700 (-0700), Ronak Shah wrote:
>> As OS dev cycle involves Gerrit review tool which requires ssh
>> into the gerrit server, I was wondering if any of you guys face
>> problems where your company/org does not allow ssh to external
>> hosts.
> [...]
> 
> It usually involves the uphill battle of convincing whoever manages
> network security/firewalls/proxies for your employer that the
> Internet is more than just a bunch of Web pages. Companies which
> exclusively limit their employees to only browsing the Web are
> basically cutting themselves off from innovations which rely on a
> myriad of other protocols. For non-technology companies that might
> be fine, but for a technology company that's often a sign that it's
> going out of business pretty soon.

+1000

___
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] Gerrit Review + SSH

2013-04-04 Thread Pranav 
+1

Regards,
Pranav


On Fri, Apr 5, 2013 at 12:07 AM, Jay Pipes  wrote:

> On 04/04/2013 02:23 PM, Jeremy Stanley wrote:
> > On 2013-04-04 10:51:20 -0700 (-0700), Ronak Shah wrote:
> >> As OS dev cycle involves Gerrit review tool which requires ssh
> >> into the gerrit server, I was wondering if any of you guys face
> >> problems where your company/org does not allow ssh to external
> >> hosts.
> > [...]
> >
> > It usually involves the uphill battle of convincing whoever manages
> > network security/firewalls/proxies for your employer that the
> > Internet is more than just a bunch of Web pages. Companies which
> > exclusively limit their employees to only browsing the Web are
> > basically cutting themselves off from innovations which rely on a
> > myriad of other protocols. For non-technology companies that might
> > be fine, but for a technology company that's often a sign that it's
> > going out of business pretty soon.
>
> +1000
>
> ___
> 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] "multi-host" mode in quantum

2013-04-04 Thread Xin Zhao 

Hello,

As Grizzly is released today, can anybody confirm that the multi-host 
network mode is supported by Quantum in this new release?


Thanks,
Xin

On 12/13/2012 6:04 AM, Heiko Krämer wrote:

Hey Guys,

it's a good point. I hope this option will include in Grizzly. We get 
now (since the switch to Quantum) network I/O bottlenecks without 
using all NIC's of our nodes.

So I'm looking forward to Grizzly 

Greetings
Heiko

Am 12.12.2012 17:11, schrieb Gary Kotton:

On 12/12/2012 05:58 PM, Xin Zhao wrote:

Hello,

If I understand it correctly, multi-host network mode is not 
supported (yet) in quantum in Folsom.
I wonder what's the recommended way of running multiple network 
nodes (for load balancing and
bandwidth concerns) in quantum?  Any documentation links will be 
appreciated.


At the moment this is in discussion upstream. It is currently not 
supported but we are hoping to have support for this in grizzly.


Thanks,
Xin



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





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




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


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

Re: [Openstack] "multi-host" mode in quantum

2013-04-04 Thread Anne Gentle 
Hi Xin,
This is in the release notes at
https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly#OpenStack_Network_Service_.28Quantum.29


   - Multiple Network support for multiple network nodes running L3-agents
   and DHCP-agents
  - provides better scale + high-available for quantum deployments.


Anne


On Thu, Apr 4, 2013 at 2:04 PM, Xin Zhao  wrote:

>  Hello,
>
> As Grizzly is released today, can anybody confirm that the multi-host
> network mode is supported by Quantum in this new release?
>
> Thanks,
> Xin
>
>
> On 12/13/2012 6:04 AM, Heiko Krämer wrote:
>
> Hey Guys,
>
> it's a good point. I hope this option will include in Grizzly. We get now
> (since the switch to Quantum) network I/O bottlenecks without using all
> NIC's of our nodes.
> So I'm looking forward to Grizzly 
>
> Greetings
> Heiko
>
> Am 12.12.2012 17:11, schrieb Gary Kotton:
>
> On 12/12/2012 05:58 PM, Xin Zhao wrote:
>
> Hello,
>
> If I understand it correctly, multi-host network mode is not supported
> (yet) in quantum in Folsom.
> I wonder what's the recommended way of running multiple network nodes (for
> load balancing and
> bandwidth concerns) in quantum?  Any documentation links will be
> appreciated.
>
>
> At the moment this is in discussion upstream. It is currently not
> supported but we are hoping to have support for this in grizzly.
>
>
> Thanks,
> Xin
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
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] "multi-host" mode in quantum

2013-04-04 Thread Henry Gessau 
Unfortunately, I don't think "multiple network nodes" is the same
"multi-host network mode" that Xin is asking about.

The following did not make it into grizzly and is now targeted for havana:
https://blueprints.launchpad.net/quantum/+spec/quantum-multihost

-- Henry

On Thu, Apr 04, at 3:11 pm Anne Gentle (a...@openstack.org) wrote:
> Hi Xin,
> This is in the release notes at
> https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly#OpenStack_Network_Service_.28Quantum.29
>
>   * Multiple Network support for multiple network nodes running L3-agents
> and DHCP-agents
>   o provides better scale + high-available for quantum deployments.
>
>
> Anne
>
>
> On Thu, Apr 4, 2013 at 2:04 PM, Xin Zhao  > wrote:
>
> Hello,
>
> As Grizzly is released today, can anybody confirm that the multi-host
> network mode is supported by Quantum in this new release?
>
> Thanks,
> Xin
>
>
> On 12/13/2012 6:04 AM, Heiko Krämer wrote:
>> Hey Guys,
>>
>> it's a good point. I hope this option will include in Grizzly. We get
>> now (since the switch to Quantum) network I/O bottlenecks without
>> using all NIC's of our nodes.
>> So I'm looking forward to Grizzly 
>>
>> Greetings
>> Heiko
>>
>> Am 12.12.2012 17:11, schrieb Gary Kotton:
>>> On 12/12/2012 05:58 PM, Xin Zhao wrote:
 Hello,

 If I understand it correctly, multi-host network mode is not
 supported (yet) in quantum in Folsom.
 I wonder what's the recommended way of running multiple network
 nodes (for load balancing and
 bandwidth concerns) in quantum?  Any documentation links will be
 appreciated.
>>>
>>> At the moment this is in discussion upstream. It is currently not
>>> supported but we are hoping to have support for this in grizzly.

 Thanks,
 Xin



 ___
 Mailing list: https://launchpad.net/~openstack
 
 Post to : openstack@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~openstack
 
 More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack 
>>> 
>>> Post to : openstack@lists.launchpad.net 
>>> 
>>> Unsubscribe : https://launchpad.net/~openstack 
>>> 
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack 
>> 
>> Post to : openstack@lists.launchpad.net 
>> 
>> Unsubscribe : https://launchpad.net/~openstack 
>> 
>> More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> 
> Post to : openstack@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~openstack
> 
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> ___
> 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] "multi-host" mode in quantum

2013-04-04 Thread Anne Gentle 
Henry, thank you for clarifying! I was just posting what was in the release
notes. Perhaps someone on the Quantum core team can add to the release
notes for clarity.

Anne


On Thu, Apr 4, 2013 at 2:23 PM, Henry Gessau  wrote:

>  Unfortunately, I don't think "multiple network nodes" is the same
> "multi-host network mode" that Xin is asking about.
>
> The following did not make it into grizzly and is now targeted for havana:
> https://blueprints.launchpad.net/quantum/+spec/quantum-multihost
>
> -- Henry
>
>
> On Thu, Apr 04, at 3:11 pm Anne Gentle (a...@openstack.org) wrote:
>
> Hi Xin,
> This is in the release notes at
>
> https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly#OpenStack_Network_Service_.28Quantum.29
>
>
>- Multiple Network support for multiple network nodes running
>L3-agents and DHCP-agents
>   - provides better scale + high-available for quantum deployments.
>
>
>  Anne
>
>
> On Thu, Apr 4, 2013 at 2:04 PM, Xin Zhao  wrote:
>
>>  Hello,
>>
>> As Grizzly is released today, can anybody confirm that the multi-host
>> network mode is supported by Quantum in this new release?
>>
>> Thanks,
>> Xin
>>
>>
>> On 12/13/2012 6:04 AM, Heiko Krämer wrote:
>>
>> Hey Guys,
>>
>> it's a good point. I hope this option will include in Grizzly. We get now
>> (since the switch to Quantum) network I/O bottlenecks without using all
>> NIC's of our nodes.
>> So I'm looking forward to Grizzly 
>>
>> Greetings
>> Heiko
>>
>> Am 12.12.2012 17:11, schrieb Gary Kotton:
>>
>> On 12/12/2012 05:58 PM, Xin Zhao wrote:
>>
>> Hello,
>>
>> If I understand it correctly, multi-host network mode is not supported
>> (yet) in quantum in Folsom.
>> I wonder what's the recommended way of running multiple network nodes
>> (for load balancing and
>> bandwidth concerns) in quantum?  Any documentation links will be
>> appreciated.
>>
>>
>> At the moment this is in discussion upstream. It is currently not
>> supported but we are hoping to have support for this in grizzly.
>>
>>
>> Thanks,
>> Xin
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> ___
> 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] "multi-host" mode in quantum

2013-04-04 Thread Jonathan Proulx 
Hi All,

On Thu, Apr 4, 2013 at 3:23 PM, Henry Gessau  wrote:
>Unfortunately, I don't think "multiple network nodes" is the same
"multi-host network mode" that Xin is asking about.

>The following did not make it into grizzly and is now targeted for havana:
>https://blueprints.launchpad.net/quantum/+spec/quantum-multihost

I'm hoping that means there still needs to be a central dhcp server but the
multiple L3 agents mean actual traffic from VMs can be managed directly on
the compute note they are running on and doesn't need to be sent back to a
different network node before being nat'ed or tagged?

Multi-host was the single most important feature for me in the quantum blue
prints, if nat'ed networks need to be piped through a gateway box other
than the physical host the instance is on quantum remains a no go for me.
Having a central (but redundant) dhcp with distributed NAT may actually be
an improvement over having to run dnsmasq literally everywhere.

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

[Openstack] AUTO: I am out of the office. (returning 2013/04/06)

2013-04-04 Thread Hai Quan Chen 


I am out of the office until 2013/04/06.

I will respond to your message when I return.


Note: This is an automated response to your message  "[Openstack] OpenStack
2013.1 ("Grizzly") is released !" sent on 04/04/2013 22:47:45.

This is the only notification you will receive while this person is away.___
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] Grizzly release notes and the never-ending image-cache-manager issue

2013-04-04 Thread Lorin Hochstein 
Michael (et al):

The Grizzly release notes <
https://wiki.openstack.org/wiki/ReleaseNotes/Grizzly> say:

"The image-cache-manager has been turned on by default. This may have
potential issues for users who are using a shared filesystem for their
instances_path. Set remove_unused_base_images=false in your nova.conf file
on your compute nodes to revert this behaviour."


My understanding was that in Grizzly, this wasn't an issue since shared
storage was automatically detected (e.g.
https://bugs.launchpad.net/nova/+bug/1075018)

Is it safe to zap this from the release notes?

Lorin

-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.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] Grizzly release notes and the never-ending image-cache-manager issue

2013-04-04 Thread Michael Still 
On Fri, Apr 5, 2013 at 7:20 AM, Lorin Hochstein
 wrote:
> Michael (et al):
>
> The Grizzly release notes
>  say:
>
> "The image-cache-manager has been turned on by default. This may have
> potential issues for users who are using a shared filesystem for their
> instances_path. Set remove_unused_base_images=false in your nova.conf file
> on your compute nodes to revert this behaviour."
>
> My understanding was that in Grizzly, this wasn't an issue since shared
> storage was automatically detected (e.g.
> https://bugs.launchpad.net/nova/+bug/1075018)

This is my understanding as well -- that we now detect shared storage
and do the right thing. I don't have any data on how much real world
testing that code has experienced though.

> Is it safe to zap this from the release notes?

Safe is a relative thing. I'd be more comfortable if I knew that
someone had deployed the code and had a good experience, but when I
ask on the operators list I get puzzled stares...

Michael

___
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] Gerrit Review + SSH

2013-04-04 Thread Daniel P. Berrange 
On Thu, Apr 04, 2013 at 10:51:20AM -0700, Ronak Shah wrote:
> Hi,
> 
> As OS dev cycle involves Gerrit review tool which requires ssh into the
> gerrit server, I was wondering if any of you guys face problems where your
> company/org does not allow ssh to external hosts.
> 
> In general, what is the best practice in terms of environment for
> generating code review?

The traditional workaround when companies have insane firewalls blocking
SSH, is to run an SSH server on port 443, since firewalls typically
allow through any traffic on the HTTPS port, even if it isn't using the
HTTPS protocol :-) This workaround only fails if your company is also
doing a man-in-the-middle attack on HTTPS traffic[1]

GitHub actually have an SSH server on port 443 for exactly this reason

   https://help.github.com/articles/using-ssh-over-the-https-port

I don't know how hard it would be for OpenStack Infrastructure team
to officially make Gerrit available via port 443, in addition to the
normal SSH port.

Regards,
Daniel

[1] Yes some companies really do MITM attack all HTTPS connections
their employees make :-(
-- 
|: 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] Gerrit Review + SSH

2013-04-04 Thread Jeremy Stanley 
On 2013-04-04 22:11:10 +0100 (+0100), Daniel P. Berrange wrote:
[...]
> I don't know how hard it would be for OpenStack Infrastructure team
> to officially make Gerrit available via port 443, in addition to the
> normal SSH port.

We'd need to use different hostnames mapped to different IP
addresses since 443/tcp is already in use on review.openstack.org
for, well, HTTPS (the availability of fancy proxies which can
differentiate SSH from SSL/TLS notwithstanding--do those exist?).

The bigger question is whether it's worth the effort to maintain a
workaround like that... are there companies who want their employees
contributing to OpenStack development but won't grant those same
developers access to our code review system over the Internet? If
so, maybe some brave soul will take pity on them and set up a TCP
bounce proxy somewhere on port 443 to forward to port 29418 on our
Gerrit server for Git+SSH access on an alternate address and port. I
don't think that would need any sort of buy-off from our
Infrastructure Team (we can discuss if someone's actually interested
in setting it up), but probably wouldn't be "official" all the same.
-- 
Jeremy Stanley

___
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 proxy and swift-informant

2013-04-04 Thread Giovanni Colapinto 
Yes, I read that documentation on upgrade, but unfortunately in that
repository quantal distribution doesn't exists. Is it safe to use precise
packages even if I got quantal?

Thank you


On Thu, Apr 4, 2013 at 4:29 PM, Tong Li  wrote:

> on ubuntu, you can try the following.
>
> apt-get install python-software-properties
> add-apt-repository ppa:swift-core/release
> apt-get update
> apt-get install swift python-swiftclient
>
> Also look into the doc at this link.
> http://docs.openstack.org/developer/swift/howto_installmultinode.html
>
> If you want to use the latest swift code, you can get the code from github
> and build it yourself but I would not recommend to do it for the production
> system.
>
> Hope that helps.
>
>
> Tong Li
> Emerging Technologies & Standards
> Building 501/B205
> liton...@us.ibm.com
>
> [image: Inactive hide details for Giovanni Colapinto ---04/04/2013
> 09:20:50 AM---Thank you for the reply. How I can upgrade swift? On T]Giovanni
> Colapinto ---04/04/2013 09:20:50 AM---Thank you for the reply. How I can
> upgrade swift? On Thu, Apr 4, 2013 at 3:12 PM, Tong Li 
> From: Giovanni Colapinto 
> To: Tong Li/Raleigh/IBM@IBMUS,
> Cc: openstack@lists.launchpad.net, openstack-bounces+litong01=
> us.ibm@lists.launchpad.net
> Date: 04/04/2013 09:20 AM
> Subject: Re: [Openstack] Swift proxy and swift-informant
> --
>
>
>
> Thank you for the reply. How I can upgrade swift?
>
>
> On Thu, Apr 4, 2013 at 3:12 PM, Tong Li 
> <*liton...@us.ibm.com*>
> wrote:
>
>swob is not a separate package, it is part of the swift core. You may
>either get older version of informant which does not use swob or upgrade
>swift.
>
>Tong Li
>Emerging Technologies & Standards
>Building 501/B205*
>**liton...@us.ibm.com* 
>
>[image: Inactive hide details for Giovanni Colapinto ---04/04/2013
>04:26:57 AM---Hi to all. I try to configure swift proxy to work 
> with]Giovanni
>Colapinto ---04/04/2013 04:26:57 AM---Hi to all. I try to configure swift
>proxy to work with swift-informant.
>
>From: Giovanni Colapinto 
> <*giovanni.colapi...@gmail.com*
>>
>To: *openstack@lists.launchpad.net* ,
>Date: 04/04/2013 04:26 AM
>Subject: [Openstack] Swift proxy and swift-informant
>Sent by: 
> openstack-bounces+litong01=*us.ibm@lists.launchpad.net*
>--
>
>
>
>
>Hi to all.
>
>I try to configure swift proxy to work with swift-informant.
>
>I've installed swift-informant and add/modify the following section to
>/etc/swift/proxy-server.conf:
>
>[pipeline:main]
>pipeline = informant healthcheck cache swift3 authtoken keystone
>proxy-server
>
>[filter:informant]
>use = egg:informant#informant
>statsd_host = 10.0.1.154
>metric_name_prepend = inndig.
>
>When I start proxy-server it returns the following error:
>
>Traceback (most recent call last):
>  File "/usr/bin/swift-proxy-server", line 22, in 
>run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
>  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line
>138, in run_wsgi
>loadapp('config:%s' % conf_file, global_conf={'log_name':
>log_name})
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 247, in loadapp
>return loadobj(APP, uri, name=name, **kw)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 271, in loadobj
>global_conf=global_conf)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 296, in loadcontext
>global_conf=global_conf)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 320, in _loadconfig
>return loader.get_context(object_type, name, global_conf)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 450, in get_context
>global_additions=global_additions)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 562, in _pipeline_app_context
>for name in pipeline[:-1]]
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 454, in get_context
>section)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 476, in _context_from_use
>object_type, name=use, global_conf=global_conf)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 406, in get_context
>global_conf=global_conf)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 296, in loadcontext
>global_conf=global_conf)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 328, in _loadegg
>return loader.get_context(object_type, name, global_conf)
>  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py",
>line 620, in get_context
>object_type, name