Re: [Openstack] ceilometer-agent-central starting fail

[Liu Wenmao]

I solve this problem by two steps:

1 modify /etc/init/ceilometer-agent-central.conf
exec start-stop-daemon --start --chuid ceilometer --exec
/usr/local/bin/ceilometer-agent-central --
--config-file=/etc/ceilometer/ceilometer.conf
2 add some lines to /etc/ceilometer/ceilometer.conf:
os-username=ceilometer
os-password=nsfocus
os-tenant-name=service
os-auth-url=http://controller:5000/v2.0



On Wed, Apr 10, 2013 at 1:36 PM, Liu Wenmao  wrote:

> Hi all:
>
> I have just install ceilometer grizzly github version, but fail to
> start ceilometer-agent-central service. I think it is due to that I didn't
> set up the keystone user/password like other projects. but I follow the
> instructions(
> http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
> but it does not include the ceilometer configuration.
>
> # service ceilometer-agent-central start
> ceilometer-agent-central start/running, process 5679
>
> # cat /etc/init/ceilometer-agent-central.conf
> description "ceilometer-agent-compute"
> author "Chuck Short "
>
> start on runlevel [2345]
> stop on runlelvel [!2345]
>
> chdir /var/run
>
> pre-start script
> mkdir -p /var/run/ceilometer
> chown ceilometer:ceilometer /var/run/ceilometer
>
> mkdir -p /var/lock/ceilometer
> chown ceilometer:ceilometer /var/lock/ceilometer
> end script
>
> exec start-stop-daemon --start --chuid ceilometer --exec
> /usr/local/bin/ceilometer-agent-central
>
>
> /var/log/ceilometer/ceilometer-agent-central.log
> 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall] in
> looping call
> Traceback (most recent call last):
>   File
> "/usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py",
> line 67, in _inner
> self.f(*self.args, **self.kw)
>   File
> "/usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py",
> line 76, in interval_task
> auth_url=cfg.CONF.os_auth_url)
>   File
> "/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py",
> line 134, in __init__
> self.authenticate()
>   File
> "/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py",
> line 205, in authenticate
> token)
>   File
> "/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py",
> line 174, in get_raw_token_from_identity_servicetoken=token)
>   File
> "/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py",
> line 202, in _base_authN
> resp, body = self.request(url, 'POST', body=params, headers=headers)
>   File
> "/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py",
> line 366, in request
> raise exceptions.from_response(resp, resp.text)
> Unauthorized: Unable to communicate with identity service: {"error":
> {"message": "Invalid user / password", "code": 401, "title": "Not
> Authorized"}}. (HTTP 401)
> 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.threadgroup]
> Unable to communicate with identity service: {"error": {"message": "Invalid
> user / password", "code": 401, "title": "Not Authorized"}}. (HTTP 401)
>
___
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-agent-central starting fail

[Liu Wenmao]

Hi all:

I have just install ceilometer grizzly github version, but fail to
start ceilometer-agent-central service. I think it is due to that I didn't
set up the keystone user/password like other projects. but I follow the
instructions(
http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
but it does not include the ceilometer configuration.

# service ceilometer-agent-central start
ceilometer-agent-central start/running, process 5679

# cat /etc/init/ceilometer-agent-central.conf
description "ceilometer-agent-compute"
author "Chuck Short "

start on runlevel [2345]
stop on runlelvel [!2345]

chdir /var/run

pre-start script
mkdir -p /var/run/ceilometer
chown ceilometer:ceilometer /var/run/ceilometer

mkdir -p /var/lock/ceilometer
chown ceilometer:ceilometer /var/lock/ceilometer
end script

exec start-stop-daemon --start --chuid ceilometer --exec
/usr/local/bin/ceilometer-agent-central


/var/log/ceilometer/ceilometer-agent-central.log
2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall] in
looping call
Traceback (most recent call last):
  File
"/usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py",
line 67, in _inner
self.f(*self.args, **self.kw)
  File
"/usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py",
line 76, in interval_task
auth_url=cfg.CONF.os_auth_url)
  File
"/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py",
line 134, in __init__
self.authenticate()
  File
"/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py",
line 205, in authenticate
token)
  File
"/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py",
line 174, in get_raw_token_from_identity_servicetoken=token)
  File
"/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py",
line 202, in _base_authN
resp, body = self.request(url, 'POST', body=params, headers=headers)
  File
"/usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py",
line 366, in request
raise exceptions.from_response(resp, resp.text)
Unauthorized: Unable to communicate with identity service: {"error":
{"message": "Invalid user / password", "code": 401, "title": "Not
Authorized"}}. (HTTP 401)
2013-04-10 13:01:39ERROR [ceilometer.openstack.common.threadgroup]
Unable to communicate with identity service: {"error": {"message": "Invalid
user / password", "code": 401, "title": "Not Authorized"}}. (HTTP 401)
___
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] root_helper deprecated?

[Liu Wenmao]

Thanks Thierry, it seems to make sense.


On Tue, Apr 9, 2013 at 4:53 PM, Thierry Carrez wrote:

> Rahul Upadhyaya wrote:
> > I think you should use : rootwrap_config=/etc/quantum/rootwrap.conf
> >
> > Found this at below mentioned wiki page. I think this should hold true
> > for Quantum too.
>
> No, Quantum still uses root_helper and has not transitioned to using
> rootwrap_config yet.
>
> Looking at the code, the message seems to point to configuration
> sections. The [DEFAULT] root_helper configuration option is now
> deprecated, it needs to be specified in the [AGENT] section of
> quantum.conf.
>
> See https://github.com/openstack/quantum/blob/master/etc/quantum.conf
> for an example.
>
> --
> 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
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] vm unable to reach 169.254.169.254

[Liu Wenmao]

Thanks Mouad

After I install the latest grizzly quantum and remove metadata_port  from
l3_agent.ini, I can connect 169.254.169.254:80, but the server return a 404
NOT Found error:


Starting dropbear sshd: generating rsa key... generating dsa key... OK
= cloudfinal: system completely up in 5.03 seconds 
  instanceid: i005b
  publicipv4:
  localipv4 : 100.0.0.4
wget: server returned error: HTTP/1.1 404 Not Found
clouduserdata: failed to read user data url:
http://169.254.169.254/20090404/userdata
WARN: /etc/rc3.d/S99clouduserdata failed

I use cirros-0.3.0-x86_64-disk.img, is it a problem of cirros-image, or
quantum?



On Tue, Apr 9, 2013 at 6:18 PM, Mouad Benchchaoui  wrote:

> Hi,
>
> Are you using namespaces ? b/c i think this is related to
> https://bugs.launchpad.net/quantum/+bug/1160955, if so a fix was just
> commited in the stable grizzly branch, so upgrade if you want to use
> another port than the default one, or i think removing the option 
> metadata_port
> from l3_agent.ini should also make it work for you.
>
>
> HTH,
>
> --
> Mouad
>
>
> On Tue, Apr 9, 2013 at 11:48 AM, Liu Wenmao  wrote:
>
>> hi all:
>>
>> I setup quantum and nova grizzly, but vms can not get public key from
>> 169.254.169.254:
>>
>>
>>
>>  debug end   ##
>> cloudsetup: failed to read iid from metadata. tried 30
>> WARN: /etc/rc3.d/S45cloudsetup failed
>> Starting dropbear sshd: generating rsa key... generating dsa key... OK
>> = cloudfinal: system completely up in 39.98 seconds 
>> wget: can't connect to remote host (169.254.169.254): Connection refused
>> wget: can't connect to remote host (169.254.169.254): Connection refused
>> wget: can't connect to remote host (169.254.169.254): Connection refused
>>   instanceid:
>>   publicipv4:
>>
>> I have configured nova.conf
>> enabled_apis=ec2,osapi_compute,metadata
>> metadata_manager=nova.api.manager.MetadataManager
>> metadata_listen=0.0.0.0
>> metadata_listen_port=8775
>> service_quantum_metadata_proxy=true
>> metadata_host=20.0.0.1
>> metadata_port=8775
>>
>> quantum l3_agent.ini
>> metadata_ip = 20.0.0.1
>> metadata_port = 8775
>>
>> metadata_agent.ini
>> nova_metadata_ip = 20.0.0.1
>> nova_metadata_port = 8775
>>
>> 20.0.0.1 is my controller ip.
>>
>> p.s. I can not see any things like "169.254.169.254" in the iptables of
>> controller or compute nodes.
>>
>>
>> ___
>> 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] Grizzly release notes and the never-ending image-cache-manager issue

[Lorin Hochstein]

On Thu, Apr 4, 2013 at 4:45 PM, Michael Still  wrote:

> 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
>

I reworded the release note as follows:

Grizzly should now be able to detect when a shared filesystem is being used
for instances path, eliminating a bug in previous versions where the image
cache manager erroneously deleted images that were in use on shared
filesystems. However, this bugfix has not been extensively tested in
production environments. If you wish to be conservative, you may set
image_cache_manager_interval=0 in your nova.conf file on your compute nodes
to prevent the image cache manager from deleting any images.


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] What's the package flow in vlan mode when ping the floating ip between vms.

[Narayan Desai]

This will depend on whether the VMs are in the same tenant network or
not. Assuming they are on the same L2 and L3 network, then the packets
will transit either the linux bridge, or openvswitch, depending on how
you have things configured. Note that network filtering rules will be
processed on this path in some cases.

If you are talking about flows between VMs that are on different
tenant networks (both ends using RFC1918 addresses), nova-network
would setup gateways for each network in the host, and it should be
routing, i think. (this is supposition on my part -- we've only done
some basic experiments with multi-host)
 -nld

On Tue, Apr 9, 2013 at 7:41 PM, Lei Zhang  wrote:
> Hi JuanFra,
>
> I read this article. But It doesn't explain what I concern.
> What I want to know is that what's the packet flow when ping the floating ip
> between the VMs which located in the same physical machine?
>
>
> On Tue, Apr 9, 2013 at 9:56 PM, JuanFra Rodriguez Cardoso
>  wrote:
>>
>> Could this Mirantis' post help you?
>>
>> http://www.mirantis.com/blog/vlanmanager-network-flow-analysis/
>>
>> ---
>> JuanFra
>>
>>
>> 2013/4/9 Lei Zhang 
>>>
>>> I am using: Folsom, nova-network, vlanManage, multi_host=ture
>>>
>>> I want to know what's the package flow between the vms which located in
>>> the same physical machine.
>>>
>>> Here is the typology. I want to know want happen if I ping 192.168.3.47
>>> in vm7.
>>>
>>> When the NAT is applied?
>>>
>>>|vm: fixed: 10.0.104.5, floating:
>>> 192.168.3.56|-|vnet15||br104||vnet14|| vm7: fixed:
>>> 10.0.104.6, floating: 192.168.3.57|
>>>
>>> if the net.bridge.bridge-nf-call-iptables=0, I can not see the NAT
>>> properly.
>>>
>>> [root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
>>> tcpdump: WARNING: vnet14: no IPv4 address assigned
>>> tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture size
>>> 65535 bytes
>>> 17:11:10.275818 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4
>>> (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
>>> ICMP (1), length 84)
>>> 10.0.104.6 > 192.168.3.56: ICMP echo request, id 31090, seq 1, length
>>> 64
>>> 17:11:10.277546 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4
>>> (0x0800), length 98: (tos 0x0, ttl 64, id 64703, offset 0, flags [none],
>>> proto ICMP (1), length 84)
>>> 10.0.104.5 > 10.0.104.6: ICMP echo reply, id 31090, seq 1, length 64
>>>
>>> When net.bridge.bridge-nf-call-iptables=1, I found the NAT properly. But
>>> I also found it is said the bridge filter should be disabled in
>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/network-troubleshooting.html.
>>> Is this true?
>>>
>>> [root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
>>> tcpdump: WARNING: vnet14: no IPv4 address assigned
>>> tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture size
>>> 65535 bytes
>>> 17:13:40.507577 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4
>>> (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
>>> ICMP (1), length 84)
>>> 10.0.104.6 > 192.168.3.56: ICMP echo request, id 42098, seq 1, length
>>> 64
>>> 17:13:40.508034 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4
>>> (0x0800), length 98: (tos 0x0, ttl 64, id 64704, offset 0, flags [none],
>>> proto ICMP (1), length 84)
>>> 192.168.3.56 > 10.0.104.6: ICMP echo reply, id 42098, seq 1, length
>>> 64
>>>
>>> --
>>> Lei Zhang
>>>
>>> Blog: http://jeffrey4l.github.com
>>> twitter/weibo: @jeffrey4l
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>
>
>
> --
> Lei Zhang
>
> Blog: http://jeffrey4l.github.com
> twitter/weibo: @jeffrey4l
>
> ___
> 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] What's the package flow in vlan mode when ping the floating ip between vms.

[Lei Zhang]

Hi JuanFra,

I read this article. But It doesn't explain what I concern.
What I want to know is that what's the packet flow when ping the floating
ip between the VMs which located in the same physical machine?


On Tue, Apr 9, 2013 at 9:56 PM, JuanFra Rodriguez Cardoso <
juanfra.rodriguez.card...@gmail.com> wrote:

> Could this Mirantis' post help you?
>
> http://www.mirantis.com/blog/vlanmanager-network-flow-analysis/
>
> ---
> JuanFra
>
>
> 2013/4/9 Lei Zhang 
>
>>  I am using: Folsom, nova-network, vlanManage, multi_host=ture
>>
>> I want to know what's the package flow between the vms which located in
>> the same physical machine.
>>
>> Here is the typology. I want to know want happen if I ping 192.168.3.47
>> in vm7.
>>
>> When the NAT is applied?
>>
>>|vm: fixed: 10.0.104.5, floating: 
>> 192.168.3.56|-|vnet15||br104||vnet14|| vm7: fixed: 
>> 10.0.104.6, floating: 192.168.3.57|
>>
>> if the net.bridge.bridge-nf-call-iptables=0, I can not see the NAT
>> properly.
>>
>> [root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
>> tcpdump: WARNING: vnet14: no IPv4 address assigned
>> tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture size 
>> 65535 bytes
>> 17:11:10.275818 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4 
>> (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 
>> ICMP (1), length 84)
>> 10.0.104.6 > 192.168.3.56: ICMP echo request, id 31090, seq 1, length 64
>> 17:11:10.277546 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4 
>> (0x0800), length 98: (tos 0x0, ttl 64, id 64703, offset 0, flags [none], 
>> proto ICMP (1), length 84)
>> 10.0.104.5 > 10.0.104.6: ICMP echo reply, id 31090, seq 1, length 64
>>
>> When net.bridge.bridge-nf-call-iptables=1, I found the NAT properly. But
>> I also found it is said the bridge filter should be disabled in
>> http://docs.openstack.org/trunk/openstack-compute/admin/content/network-troubleshooting.html.
>> Is this true?
>>
>>
>> [root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
>> tcpdump: WARNING: vnet14: no IPv4 address assigned
>> tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture size 
>> 65535 bytes
>> 17:13:40.507577 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4 
>> (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 
>> ICMP (1), length 84)
>> 10.0.104.6 > 192.168.3.56: ICMP echo request, id 42098, seq 1, length 64
>> 17:13:40.508034 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4 
>> (0x0800), length 98: (tos 0x0, ttl 64, id 64704, offset 0, flags [none], 
>> proto ICMP (1), length 84)
>> 192.168.3.56 > 10.0.104.6: ICMP echo reply, id 42098, seq 1, length 64
>>
>> --
>> Lei Zhang
>>
>> Blog: http://jeffrey4l.github.com
>> twitter/weibo: @jeffrey4l
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 
Lei Zhang

Blog: http://jeffrey4l.github.com
twitter/weibo: @jeffrey4l
___
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] Libvirt iSCSI client: duplicit connection_info data

[Joe Topjian]

Hi Brano,

I apologize for reviving an old thread.


On Wed, Mar 20, 2013 at 4:39 AM, Brano Zarnovican wrote:

> Hi devs,
>
> we are using backend iSCSI provider (Netapp) which is mapping
> Openstack volumes to iSCSI LUNs. This mapping is not static and
> changes over time. For example when the volume is detached then his
> LUN id becomes unused. After a while a _different_ volume may get the
> same LUN id, as Netapp is recycling them. This is expected behavior..
>
> As a result, there may be entries in "block_device_mapping" with
> identical connection_info..
> connection_info: {"driver_volume_type": "iscsi", "data":
> {"target_lun": "5", .. "target_iqn":
> "iqn.1992-08.com.netapp:node.netapp02", volume_id": 1806}}
> connection_info: {"driver_volume_type": "iscsi", "data":
> {"target_lun": "5", .. "target_iqn":
> "iqn.1992-08.com.netapp:node.netapp02", volume_id": 2227}}
> Zero or one of them may be attached, the rest is in detached state.
>
> As a fix to address #1112483, I'm deleting the device when it is being
> disconnected (echo 1 > /sys/block/sdg/device/delete).
>
> Trouble is that OpenStack seems to expect the disconnect_volume to be
> idempotent (_cleanup() method). That is, calling disconnect_volume on
> detached volume will do nothing. However, because of the LUN reuse,
> the id may now be mapped to a different volume. Caller is asking me to
> disconnect volume with LUN5. From just looking at the device name
> there is no way of telling which openstack volume it is.
>
>
> /dev/disk/by-path/ip-172.30.128.3:3260-iscsi-iqn.1992-08.com.netapp:node.netapp02-lun-5
> -> ../../sdg
>
> How to get out of this .. ?
>
> 1) Do not call 'disconnect_volume' for volumes that were successfully
> disconnected before. In other words, disconnect_volume is not
> idempotent anymore.
>
> 2) Wipeout connection_info after disconnect. At least for Netapp
> provider it makes no sense to retain the info which is no longer valid
> anyway.
>
> 3) do not reuse LUN ids - this would require major driver change to
> keep track of all currently used LUNs for both attached and detached
> volumes
>
> 4) store "somewhere" on the host system mapping between LUNs and
> openstack volumes. You could check against it, before disconnecting a
> LUN device
>
> None of the options is too pleasant. Any suggestions how to address
> the problem ?
>
> Regards,
>
> Brano Zarnovican
>
> PS: We are using Essex. LUN reusing is a feature of Netapp that exists
> in all versions of the driver (IMO). By a quick glance I think the
> same problem with disconnect_volume exists on Folsom and master
> branch.
>

I'm using Folsom with a NetApp appliance and can confirm the problem exists.



-- 
Joe Topjian
Systems Administrator
Cybera Inc.

www.cybera.ca

Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.
___
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] what would be the best wat to get security notifications for openstack

[Thierry Carrez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Matthew Thode wrote:
> I've been packaging openstack in Gentoo but have been relying on
> others to watch you guys for security bugs.  What would be the best
> way for me to get notification when a security bug is fixed (when a
> security patch is accepted), so that I may update the packages.

Cross-posting is evil!
Answers went to the openstack-security list.

Cheers,

- -- 
Thierry Carrez (ttx)
Release Manager, OpenStack
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBCAAGBQJRZDTWAAoJEFB6+JAlsQQj4xAQAIGursAKMIgv7EsoZR508uWq
O0n5LPW56YByOuuc1DbpnNt1gOSJHWWlBrQEILYvYsVTiQF5UeVwXl66I6ohJaFG
LQrWRSx+TJXmlMzgt0JgVF7/TlG0Z5BBQXOPv/t3Y4wgmsJTwlEcHthNDP5IMYzR
OZ6AXjFakTJn5UIir3MlehJm6dAyVIxJTqkHN458nDoOGF9JhXFerrsP9uQtnrHX
ug3xh1lkjmFqEX50PS2xS8jvb3LuOF6H+H6f+9WQV3+WMpqfkTVOo3uhNG6q5Qpe
vtNx2x2QkuTyNMxu7gXxYev/KNLiGVyOcDJ38PTX/0khgMJ+D6ncv++/4U82tNqU
zvo/go9m6UaR1sI2rL55Ly2AXHzPcuG09HZ+/Wpzw2HgrmkRHSknJUZfm8Sh9wZf
prYum8Ivty1ejuhbSX1e4UDS6bq9dVdBAGiMMtOsK/qrfbOewOQgedog+kJ0QPmG
NYhgWbc+1Dqyq/xuGuI8KeqzjJ7qFGcqHzsev2bgl+RAcJqY5++KU/RHlbG7PtFF
1GMC/UJLEkFCR0wOIWTrhvRSZ31IPlok9SVRnAyXwk15NrLy2mwXVj1qQFtkamTh
nNt5jz0MWopj2s3bZUkO3vldzsphmb0i3Hvdm6GssbVbSdC2iX0rCwcn9vd5uwVZ
ogUB7IzoWf6yQTg0cqjr
=qpJ5
-END 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] Grizzly official packages

[Filipe Manco]

Ok. Thank you.

Best regards

Filipe Manco
http://about.me/fmanco


2013/4/9 Mark Lehrer 

>
>
>  Is it safe to downgrade to a previous Ubuntu version? Can someone point a
>> good tutorial on how to do it properly?
>>
>
> Theoretically possible, but probably not worth the effort.  I would
> suggest reinstalling
> with 12.04 and then move over the configs and data.
>
> Mark
>
___
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 official packages

[Mark Lehrer]

Is it safe to downgrade to a previous Ubuntu version? Can someone point a
good tutorial on how to do it properly?


Theoretically possible, but probably not worth the effort.  I would suggest 
reinstalling
with 12.04 and then move over the configs and data.

Mark

___
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] what would be the best wat to get security notifications for openstack

[Matthew Thode]

I've been packaging openstack in Gentoo but have been relying on others
to watch you guys for security bugs.  What would be the best way for me
to get notification when a security bug is fixed (when a security patch
is accepted), so that I may update the packages.

-- 
-- Matthew Thode (prometheanfire)



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

Re: [Openstack] Grizzly official packages

[Martinx - ジェームズ]

`Ultimate OpenStack Grizzly Guide' (updating it today to make use of new
Ubuntu Cloud Archive for Grizzly):

https://gist.github.com/tmartinx/d36536b7b62a48f859c2

;-)


On 9 April 2013 10:42, Filipe Manco  wrote:

> Is it safe to downgrade to a previous Ubuntu version? Can someone point a
> good tutorial on how to do it properly?
>
> Thanks
>
> Filipe Manco
> http://about.me/fmanco
>
>
> 2013/4/9 Brad Knowles 
>
>> On Apr 9, 2013, at 1:43 AM, skible.openst...@gmail.coma <
>> skible.openst...@gmail.com> wrote:
>>
>> > Thanks for your reply.
>> > In that case, i will upgrade my ubuntu server to 13.04 and download the
>> grizzly packages from there. Is this the best you to get grizzly ?
>>
>> Quoting "Mac Innes, Kiall" :
>>
>> > 12.04 will get packages for OpenStack Grizzly, Havana and "I", 13.04 on
>> > the other hand will get Grizzly and that's it. If you want Havana,
>> > you'll need to upgrade to 13.10, or downgrade to 12.04 when the time
>> comes.
>>
>> So, it all depends on what you want to do with those systems.  Do you
>> want to keep upgrading the OS on them to each new release, maybe because
>> there are other things being released that you want to play with which
>> won't be made available for 12.04?  In that case, going with 13.04 should
>> be fine.
>>
>> --
>> Brad Knowles 
>> Senior Consultant
>>
>>
>> ___
>> 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] What's the package flow in vlan mode when ping the floating ip between vms.

[JuanFra Rodriguez Cardoso]

Could this Mirantis' post help you?

http://www.mirantis.com/blog/vlanmanager-network-flow-analysis/

---
JuanFra


2013/4/9 Lei Zhang 

>  I am using: Folsom, nova-network, vlanManage, multi_host=ture
>
> I want to know what's the package flow between the vms which located in
> the same physical machine.
>
> Here is the typology. I want to know want happen if I ping 192.168.3.47 in
> vm7.
>
> When the NAT is applied?
>
>|vm: fixed: 10.0.104.5, floating: 
> 192.168.3.56|-|vnet15||br104||vnet14|| vm7: fixed: 
> 10.0.104.6, floating: 192.168.3.57|
>
> if the net.bridge.bridge-nf-call-iptables=0, I can not see the NAT
> properly.
>
> [root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
> tcpdump: WARNING: vnet14: no IPv4 address assigned
> tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture size 65535 
> bytes
> 17:11:10.275818 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4 
> (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto ICMP 
> (1), length 84)
> 10.0.104.6 > 192.168.3.56: ICMP echo request, id 31090, seq 1, length 64
> 17:11:10.277546 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4 
> (0x0800), length 98: (tos 0x0, ttl 64, id 64703, offset 0, flags [none], 
> proto ICMP (1), length 84)
> 10.0.104.5 > 10.0.104.6: ICMP echo reply, id 31090, seq 1, length 64
>
> When net.bridge.bridge-nf-call-iptables=1, I found the NAT properly. But I
> also found it is said the bridge filter should be disabled in
> http://docs.openstack.org/trunk/openstack-compute/admin/content/network-troubleshooting.html.
> Is this true?
>
>
> [root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
> tcpdump: WARNING: vnet14: no IPv4 address assigned
> tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture size 65535 
> bytes
> 17:13:40.507577 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4 
> (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto ICMP 
> (1), length 84)
> 10.0.104.6 > 192.168.3.56: ICMP echo request, id 42098, seq 1, length 64
> 17:13:40.508034 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4 
> (0x0800), length 98: (tos 0x0, ttl 64, id 64704, offset 0, flags [none], 
> proto ICMP (1), length 84)
> 192.168.3.56 > 10.0.104.6: ICMP echo reply, id 42098, seq 1, length 64
>
> --
> Lei Zhang
>
> Blog: http://jeffrey4l.github.com
> twitter/weibo: @jeffrey4l
>
> ___
> 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] Grizzly release packages available in the Ubuntu Cloud Archive

[Martinx - ジェームズ]

YAY!!! Thank you guys!!!


On 9 April 2013 10:20, James Page  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi All
>
> OpenStack Grizzly release packages are now available in the Ubuntu
> Cloud Archive for Ubuntu 12.04 - see
> https://wiki.ubuntu.com/ServerTeam/CloudArchive for details on how to
> enable and use these packages on Ubuntu 12.04.
>
> Please note that further Ubuntu related updates may land into the
> Cloud Archive for Grizzly between now and the final release of Ubuntu
> 13.04 in a couple of weeks time; 13.04 is now feature frozen so these
> should be bug fixes only.
>
> Enjoy
>
> James
>
> - --
> James Page
> Technical Lead
> Ubuntu Server Team
> james.p...@canonical.com
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJRZBWSAAoJEL/srsug59jDasAQALXgHF2OfrAySBGdati0GImP
> gKJ7gHs5uNgOHi99m4XX/LUsRWMYrYhmswKTGpFvnIhgy4nxsvvQPc5+9k9Om/lz
> ArGDivKmf7idInGfRTdp7hGm/llgNa7WLaU+GwVACuj0utBkF5RcTTE0kES1kFX2
> CAvHMQMDqLfVBpDWunsarVyE9VBMJdVHJQZWpdzDhiTForhawcZXxB9fh2qHpKhS
> nX6AqP77JZ6XARw4fTLI30n6gQritwPsbK1J93QwXFtNqu5W5TUc+GAukQSVcoAy
> frkYSkJX+4MawkhI7PJ919O0y9q9O3UAn6sH+q4xk8Mpak/xJ0KUxHZX81MUw0Q5
> 5BmdRsJwCkRPYiz1Qc0sqqT5ROlr/WnDiHUIEwjs8IYAf2/hjTUD+KjOz7ycPWqg
> V/asjzqtgTuLDCESWv5yG4vF/CWHTf00e6nqTgfoORHHVBnTnImFsq7CryLzUxes
> nSRvTAALoa/71+1qMpUoUS61bCcKhY2fBsCn2uqMM1nHiot2MUH1wVEajKiX332N
> X2IWSyHvNzr7/UP3BS5A5LKj3ck5NTdr46ft0HfLeknu5jcjOb7cltDH2wkFSunU
> 9t7p2Z3yBPw5tK5c8Fmt5gAscw9YfYhjE4Dufd12nOCD3Go2Xw8gbzjCkSQYtiY7
> RoxivOeqbSwAJu0Q6Zm4
> =kvSY
> -END 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
>
___
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 official packages

[Filipe Manco]

Is it safe to downgrade to a previous Ubuntu version? Can someone point a
good tutorial on how to do it properly?

Thanks

Filipe Manco
http://about.me/fmanco


2013/4/9 Brad Knowles 

> On Apr 9, 2013, at 1:43 AM, skible.openst...@gmail.coma <
> skible.openst...@gmail.com> wrote:
>
> > Thanks for your reply.
> > In that case, i will upgrade my ubuntu server to 13.04 and download the
> grizzly packages from there. Is this the best you to get grizzly ?
>
> Quoting "Mac Innes, Kiall" :
>
> > 12.04 will get packages for OpenStack Grizzly, Havana and "I", 13.04 on
> > the other hand will get Grizzly and that's it. If you want Havana,
> > you'll need to upgrade to 13.10, or downgrade to 12.04 when the time
> comes.
>
> So, it all depends on what you want to do with those systems.  Do you want
> to keep upgrading the OS on them to each new release, maybe because there
> are other things being released that you want to play with which won't be
> made available for 12.04?  In that case, going with 13.04 should be fine.
>
> --
> Brad Knowles 
> Senior Consultant
>
>
> ___
> 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] Grizzly release packages available in the Ubuntu Cloud Archive

[James Page]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi All

OpenStack Grizzly release packages are now available in the Ubuntu
Cloud Archive for Ubuntu 12.04 - see
https://wiki.ubuntu.com/ServerTeam/CloudArchive for details on how to
enable and use these packages on Ubuntu 12.04.

Please note that further Ubuntu related updates may land into the
Cloud Archive for Grizzly between now and the final release of Ubuntu
13.04 in a couple of weeks time; 13.04 is now feature frozen so these
should be bug fixes only.

Enjoy

James

- -- 
James Page
Technical Lead
Ubuntu Server Team
james.p...@canonical.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBCAAGBQJRZBWSAAoJEL/srsug59jDasAQALXgHF2OfrAySBGdati0GImP
gKJ7gHs5uNgOHi99m4XX/LUsRWMYrYhmswKTGpFvnIhgy4nxsvvQPc5+9k9Om/lz
ArGDivKmf7idInGfRTdp7hGm/llgNa7WLaU+GwVACuj0utBkF5RcTTE0kES1kFX2
CAvHMQMDqLfVBpDWunsarVyE9VBMJdVHJQZWpdzDhiTForhawcZXxB9fh2qHpKhS
nX6AqP77JZ6XARw4fTLI30n6gQritwPsbK1J93QwXFtNqu5W5TUc+GAukQSVcoAy
frkYSkJX+4MawkhI7PJ919O0y9q9O3UAn6sH+q4xk8Mpak/xJ0KUxHZX81MUw0Q5
5BmdRsJwCkRPYiz1Qc0sqqT5ROlr/WnDiHUIEwjs8IYAf2/hjTUD+KjOz7ycPWqg
V/asjzqtgTuLDCESWv5yG4vF/CWHTf00e6nqTgfoORHHVBnTnImFsq7CryLzUxes
nSRvTAALoa/71+1qMpUoUS61bCcKhY2fBsCn2uqMM1nHiot2MUH1wVEajKiX332N
X2IWSyHvNzr7/UP3BS5A5LKj3ck5NTdr46ft0HfLeknu5jcjOb7cltDH2wkFSunU
9t7p2Z3yBPw5tK5c8Fmt5gAscw9YfYhjE4Dufd12nOCD3Go2Xw8gbzjCkSQYtiY7
RoxivOeqbSwAJu0Q6Zm4
=kvSY
-END 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] Openstack daemons in Multi node configurations

[Mouad Benchchaoui]

Hi,

Check the scripts
nova-api-os-compute
 and 
nova-api-metadata
in
the bin  folder.

HTH,



On Tue, Apr 9, 2013 at 2:54 PM, Arindam Choudhury  wrote:

> Hi,
>
> Thanks for your reply.
>
> How to do the splitting of nova-api?
>
>
>
> --
> Date: Tue, 9 Apr 2013 14:12:19 +0200
> Subject: Re: [Openstack] Openstack daemons in Multi node configurations
> From: m.benchcha...@cloudbau.de
> To: arin...@live.com
> CC: openstack@lists.launchpad.net
>
>
> Bummer, forget about the first point the nova-api will include the
> nova-api-metadata and nova-api-os-compute, it's just than in my case i
> prefer to split them os-compute in controller and metadata in compute node.
>
> HTH,
>
> --
> Mouad
>
>
> On Tue, Apr 9, 2013 at 2:05 PM, Mouad Benchchaoui <
> m.benchcha...@cloudbau.de> wrote:
>
> Hi Arindan,
>
> Almost, well i am still new to OpenStack myself but allow me to try to
> help you:
>
> - You 're just missing the nova-metadata which you should preferably run
> in the compute node
> - There is no quantum-openvswitch service if you mean 
> quantum-openvswitch-agent
> then this later should be available only in compute nodes.
> - libvirtd should run in the compute node.
>
>
> HTH,
>
> --
> Mouad
>
>
>
> On Tue, Apr 9, 2013 at 1:24 PM, Arindam Choudhury wrote:
>
> Hi,
>
> I am very new and trying to make a small openstack private cloud. I also
> want to deploy quantum networking.
>
> I am overwhelmed by the number of available daemons and want to make sure
> that I am doing it right.
>
> so, controller node daemons are :
>
> == Nova services ==
> openstack-nova-api
> openstack-nova-cert
> openstack-nova-scheduler
> openstack-nova-conductor
> == Glance services ==
> openstack-glance-api
> openstack-glance-registry
> == Keystone service ==
> openstack-keystone
> == Horizon service ==
> openstack-dashboard
> == Quantum services ==
> quantum-server
> quantum-openvswitch
> == Cinder services ==
> openstack-cinder-api
> openstack-cinder-scheduler
> openstack-cinder-volume
> == Support services ==
> httpd
> libvirtd
> tgtd
> qpidd
>
> and the compute node daemons are:
>
> == Nova services ==
> openstack-nova-compute
> == Quantum services ==
> quantum-openvswitch
> quantum-openvswitch-agent
> quantum-openvswitch-cleanup
> quantum-dhcp-agent
> quantum-l3-agent
>
>
> Any feedback will be highly appreciated.
>
>
> ___
> 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] Openstack daemons in Multi node configurations

[Arindam Choudhury]

Hi,

Thanks for your reply. 

How to do the splitting of nova-api?



Date: Tue, 9 Apr 2013 14:12:19 +0200
Subject: Re: [Openstack] Openstack daemons in Multi node configurations
From: m.benchcha...@cloudbau.de
To: arin...@live.com
CC: openstack@lists.launchpad.net

Bummer, forget about the first point the nova-api will include the 
nova-api-metadata and nova-api-os-compute, it's just than in my case i prefer 
to split them os-compute in controller and metadata in compute node.


HTH,
--Mouad

On Tue, Apr 9, 2013 at 2:05 PM, Mouad Benchchaoui  
wrote:

Hi Arindan,
Almost, well i am still new to OpenStack myself but allow me to try to help you:

- You 're just missing the nova-metadata which you should preferably run in the 
compute node
- There is no quantum-openvswitch service if you mean quantum-openvswitch-agent 
then this later should be available only in compute nodes.

- libvirtd should run in the compute node.


HTH,


--Mouad




On Tue, Apr 9, 2013 at 1:24 PM, Arindam Choudhury  wrote:





Hi,

I am very new and trying to make a small openstack private cloud. I also want 
to deploy quantum networking.

I am overwhelmed by the number of available daemons and want to make sure that 
I am doing it right.



so, controller node daemons are :

== Nova services ==
openstack-nova-api
openstack-nova-cert
openstack-nova-scheduler
openstack-nova-conductor
== Glance services ==
openstack-glance-api
openstack-glance-registry


== Keystone service ==
openstack-keystone
== Horizon service ==
openstack-dashboard
== Quantum services ==
quantum-server
quantum-openvswitch
== Cinder services ==
openstack-cinder-api
openstack-cinder-scheduler


openstack-cinder-volume
== Support services ==
httpd
libvirtd
tgtd
qpidd

and the compute node daemons are:

== Nova services ==
openstack-nova-compute
== Quantum services ==
quantum-openvswitch


quantum-openvswitch-agent
quantum-openvswitch-cleanup
quantum-dhcp-agent
quantum-l3-agent


Any feedback will be highly appreciated.

  

___

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] Grizzly official packages

[Brad Knowles]

On Apr 9, 2013, at 1:43 AM, skible.openst...@gmail.coma 
 wrote:

> Thanks for your reply.
> In that case, i will upgrade my ubuntu server to 13.04 and download the 
> grizzly packages from there. Is this the best you to get grizzly ?

Quoting "Mac Innes, Kiall" :

> 12.04 will get packages for OpenStack Grizzly, Havana and "I", 13.04 on 
> the other hand will get Grizzly and that's it. If you want Havana, 
> you'll need to upgrade to 13.10, or downgrade to 12.04 when the time comes.

So, it all depends on what you want to do with those systems.  Do you want to 
keep upgrading the OS on them to each new release, maybe because there are 
other things being released that you want to play with which won't be made 
available for 12.04?  In that case, going with 13.04 should be fine.

--
Brad Knowles 
Senior Consultant


___
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 daemons in Multi node configurations

[Mouad Benchchaoui]

Bummer, forget about the first point the nova-api will include the
nova-api-metadata and nova-api-os-compute, it's just than in my case i
prefer to split them os-compute in controller and metadata in compute node.

HTH,

--
Mouad


On Tue, Apr 9, 2013 at 2:05 PM, Mouad Benchchaoui  wrote:

> Hi Arindan,
>
> Almost, well i am still new to OpenStack myself but allow me to try to
> help you:
>
> - You 're just missing the nova-metadata which you should preferably run
> in the compute node
> - There is no quantum-openvswitch service if you mean 
> quantum-openvswitch-agent
> then this later should be available only in compute nodes.
> - libvirtd should run in the compute node.
>
>
> HTH,
>
> --
> Mouad
>
>
>
> On Tue, Apr 9, 2013 at 1:24 PM, Arindam Choudhury wrote:
>
>> Hi,
>>
>> I am very new and trying to make a small openstack private cloud. I also
>> want to deploy quantum networking.
>>
>> I am overwhelmed by the number of available daemons and want to make sure
>> that I am doing it right.
>>
>> so, controller node daemons are :
>>
>> == Nova services ==
>> openstack-nova-api
>> openstack-nova-cert
>> openstack-nova-scheduler
>> openstack-nova-conductor
>> == Glance services ==
>> openstack-glance-api
>> openstack-glance-registry
>> == Keystone service ==
>> openstack-keystone
>> == Horizon service ==
>> openstack-dashboard
>> == Quantum services ==
>> quantum-server
>> quantum-openvswitch
>> == Cinder services ==
>> openstack-cinder-api
>> openstack-cinder-scheduler
>> openstack-cinder-volume
>> == Support services ==
>> httpd
>> libvirtd
>> tgtd
>> qpidd
>>
>> and the compute node daemons are:
>>
>> == Nova services ==
>> openstack-nova-compute
>> == Quantum services ==
>> quantum-openvswitch
>> quantum-openvswitch-agent
>> quantum-openvswitch-cleanup
>> quantum-dhcp-agent
>> quantum-l3-agent
>>
>>
>> Any feedback will be highly appreciated.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack daemons in Multi node configurations

[Mouad Benchchaoui]

Hi Arindan,

Almost, well i am still new to OpenStack myself but allow me to try to help
you:

- You 're just missing the nova-metadata which you should preferably run in
the compute node
- There is no quantum-openvswitch service if you mean quantum-openvswitch-agent
then this later should be available only in compute nodes.
- libvirtd should run in the compute node.


HTH,

--
Mouad



On Tue, Apr 9, 2013 at 1:24 PM, Arindam Choudhury  wrote:

> Hi,
>
> I am very new and trying to make a small openstack private cloud. I also
> want to deploy quantum networking.
>
> I am overwhelmed by the number of available daemons and want to make sure
> that I am doing it right.
>
> so, controller node daemons are :
>
> == Nova services ==
> openstack-nova-api
> openstack-nova-cert
> openstack-nova-scheduler
> openstack-nova-conductor
> == Glance services ==
> openstack-glance-api
> openstack-glance-registry
> == Keystone service ==
> openstack-keystone
> == Horizon service ==
> openstack-dashboard
> == Quantum services ==
> quantum-server
> quantum-openvswitch
> == Cinder services ==
> openstack-cinder-api
> openstack-cinder-scheduler
> openstack-cinder-volume
> == Support services ==
> httpd
> libvirtd
> tgtd
> qpidd
>
> and the compute node daemons are:
>
> == Nova services ==
> openstack-nova-compute
> == Quantum services ==
> quantum-openvswitch
> quantum-openvswitch-agent
> quantum-openvswitch-cleanup
> quantum-dhcp-agent
> quantum-l3-agent
>
>
> Any feedback will be highly appreciated.
>
>
> ___
> 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 daemons in Multi node configurations

[Arindam Choudhury]

Hi,

I am very new and trying to make a small openstack private cloud. I also want 
to deploy quantum networking.

I am overwhelmed by the number of available daemons and want to make sure that 
I am doing it right.

so, controller node daemons are :

== Nova services ==
openstack-nova-api
openstack-nova-cert
openstack-nova-scheduler
openstack-nova-conductor
== Glance services ==
openstack-glance-api
openstack-glance-registry
== Keystone service ==
openstack-keystone
== Horizon service ==
openstack-dashboard
== Quantum services ==
quantum-server
quantum-openvswitch
== Cinder services ==
openstack-cinder-api
openstack-cinder-scheduler
openstack-cinder-volume
== Support services ==
httpd
libvirtd
tgtd
qpidd

and the compute node daemons are:

== Nova services ==
openstack-nova-compute
== Quantum services ==
quantum-openvswitch
quantum-openvswitch-agent
quantum-openvswitch-cleanup
quantum-dhcp-agent
quantum-l3-agent


Any feedback will be highly appreciated.

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

Re: [Openstack] vm unable to reach 169.254.169.254

[Mouad Benchchaoui]

Hi,

Are you using namespaces ? b/c i think this is related to
https://bugs.launchpad.net/quantum/+bug/1160955, if so a fix was just
commited in the stable grizzly branch, so upgrade if you want to use
another port than the default one, or i think removing the option metadata_port
from l3_agent.ini should also make it work for you.


HTH,

--
Mouad


On Tue, Apr 9, 2013 at 11:48 AM, Liu Wenmao  wrote:

> hi all:
>
> I setup quantum and nova grizzly, but vms can not get public key from
> 169.254.169.254:
>
>
>  debug end   ##
> cloudsetup: failed to read iid from metadata. tried 30
> WARN: /etc/rc3.d/S45cloudsetup failed
> Starting dropbear sshd: generating rsa key... generating dsa key... OK
> = cloudfinal: system completely up in 39.98 seconds 
> wget: can't connect to remote host (169.254.169.254): Connection refused
> wget: can't connect to remote host (169.254.169.254): Connection refused
> wget: can't connect to remote host (169.254.169.254): Connection refused
>   instanceid:
>   publicipv4:
>
> I have configured nova.conf
> enabled_apis=ec2,osapi_compute,metadata
> metadata_manager=nova.api.manager.MetadataManager
> metadata_listen=0.0.0.0
> metadata_listen_port=8775
> service_quantum_metadata_proxy=true
> metadata_host=20.0.0.1
> metadata_port=8775
>
> quantum l3_agent.ini
> metadata_ip = 20.0.0.1
> metadata_port = 8775
>
> metadata_agent.ini
> nova_metadata_ip = 20.0.0.1
> nova_metadata_port = 8775
>
> 20.0.0.1 is my controller ip.
>
> p.s. I can not see any things like "169.254.169.254" in the iptables of
> controller or compute nodes.
>
>
> ___
> 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] vm unable to reach 169.254.169.254

[Liu Wenmao]

hi all:

I setup quantum and nova grizzly, but vms can not get public key from
169.254.169.254:


 debug end   ##
cloudsetup: failed to read iid from metadata. tried 30
WARN: /etc/rc3.d/S45cloudsetup failed
Starting dropbear sshd: generating rsa key... generating dsa key... OK
= cloudfinal: system completely up in 39.98 seconds 
wget: can't connect to remote host (169.254.169.254): Connection refused
wget: can't connect to remote host (169.254.169.254): Connection refused
wget: can't connect to remote host (169.254.169.254): Connection refused
  instanceid:
  publicipv4:

I have configured nova.conf
enabled_apis=ec2,osapi_compute,metadata
metadata_manager=nova.api.manager.MetadataManager
metadata_listen=0.0.0.0
metadata_listen_port=8775
service_quantum_metadata_proxy=true
metadata_host=20.0.0.1
metadata_port=8775

quantum l3_agent.ini
metadata_ip = 20.0.0.1
metadata_port = 8775

metadata_agent.ini
nova_metadata_ip = 20.0.0.1
nova_metadata_port = 8775

20.0.0.1 is my controller ip.

p.s. I can not see any things like "169.254.169.254" in the iptables of
controller or compute nodes.
___
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] What's the package flow in vlan mode when ping the floating ip between vms.

[Lei Zhang]

I am using: Folsom, nova-network, vlanManage, multi_host=ture

I want to know what's the package flow between the vms which located in the
same physical machine.

Here is the typology. I want to know want happen if I ping 192.168.3.47 in
vm7.

When the NAT is applied?

   |vm: fixed: 10.0.104.5, floating:
192.168.3.56|-|vnet15||br104||vnet14|| vm7: fixed:
10.0.104.6, floating: 192.168.3.57|

if the net.bridge.bridge-nf-call-iptables=0, I can not see the NAT
properly.

[root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
tcpdump: WARNING: vnet14: no IPv4 address assigned
tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture
size 65535 bytes
17:11:10.275818 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4
(0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF],
proto ICMP (1), length 84)
10.0.104.6 > 192.168.3.56: ICMP echo request, id 31090, seq 1, length 64
17:11:10.277546 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4
(0x0800), length 98: (tos 0x0, ttl 64, id 64703, offset 0, flags
[none], proto ICMP (1), length 84)
10.0.104.5 > 10.0.104.6: ICMP echo reply, id 31090, seq 1, length 64

When net.bridge.bridge-nf-call-iptables=1, I found the NAT properly. But I
also found it is said the bridge filter should be disabled in
http://docs.openstack.org/trunk/openstack-compute/admin/content/network-troubleshooting.html.
Is this true?


[root@openstack-node1 ~]# tcpdump -i vnet14 -l -ne icmp -v
tcpdump: WARNING: vnet14: no IPv4 address assigned
tcpdump: listening on vnet14, link-type EN10MB (Ethernet), capture
size 65535 bytes
17:13:40.507577 fa:16:3e:3e:ab:8f > fa:16:3e:72:8f:b4, ethertype IPv4
(0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags [DF],
proto ICMP (1), length 84)
10.0.104.6 > 192.168.3.56: ICMP echo request, id 42098, seq 1, length 64
17:13:40.508034 fa:16:3e:22:31:09 > fa:16:3e:3e:ab:8f, ethertype IPv4
(0x0800), length 98: (tos 0x0, ttl 64, id 64704, offset 0, flags
[none], proto ICMP (1), length 84)
192.168.3.56 > 10.0.104.6: ICMP echo reply, id 42098, seq 1, length 64

-- 
Lei Zhang

Blog: http://jeffrey4l.github.com
twitter/weibo: @jeffrey4l
___
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] root_helper deprecated?

[Thierry Carrez]

Rahul Upadhyaya wrote:
> I think you should use : rootwrap_config=/etc/quantum/rootwrap.conf
> 
> Found this at below mentioned wiki page. I think this should hold true
> for Quantum too.

No, Quantum still uses root_helper and has not transitioned to using
rootwrap_config yet.

Looking at the code, the message seems to point to configuration
sections. The [DEFAULT] root_helper configuration option is now
deprecated, it needs to be specified in the [AGENT] section of quantum.conf.

See https://github.com/openstack/quantum/blob/master/etc/quantum.conf
for an example.

-- 
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] How to make HA between VMs in the openstack

[Steven Hardy]

On Mon, Apr 08, 2013 at 07:23:08PM +0800, Lei Zhang wrote:
> Hi Syed,
> Thanks for you quickly reply. But What I want is HA between VMs not HA
> between Physical Machine(Openstack Node/ Services)

You may be interested in the Heat HA features since we implement a simple HA
capability:

https://wiki.openstack.org/wiki/Heat/Using-HA

Steve

___
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: Account not found[grizzly]

[Liu Wenmao]

thanks Kuo
setting the two option to true really solve my problem:-)


On Tue, Apr 9, 2013 at 3:36 PM, Kuo Hugo  wrote:

> 1) No minimal limitation currently .
> 2) Did you set the above option to true ?
> allow_account_management
>
> https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L61
>
> account_autocreate
>
> https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L69
>
>
> +Hugo Kuo+
> h...@swiftstack.com
> tonyt...@gmail.com
> +886 935004793
>
>
> 2013/4/9 Liu Wenmao 
>
>>  Hi all:
>>
>> I just installed swift from github, after I configure a proxy node and a
>> storage node, and run the stat command, it fails:
>> # swift -v -V 2.0 -A http://controller:5000/v2.0 -U service:swift -K
>> nsfocus stat
>> Account not found
>>
>> Keystone and disk configuation seem OK, syslog gives:
>> Apr  9 13:45:21 node1 account-server
>> AUTH_2755db390fcd4c9bb504242617d5f6a0 (txn:
>> tx6919d8c66d454e50a9b03deded9b2ec8)
>> Apr  9 13:45:21 node1 account-server 20.0.0.1 - - [09/Apr/2013:05:45:21
>> +] "HEAD /swr/27113/AUTH_2755db390fcd4c9bb504242617d5f6a0" 404 -
>> "tx6919d8c66d454e50a9b03deded9b2ec8" "-" "-" 0.0020 ""
>>
>> I read the code and find that the server try to visit db file:
>> /srv/node/swr/accounts/27113/e03/1a7a753448a645fdf2b6bcc7223e5e03, but my
>> directory  /srv/node/swr/accounts/ is empty, so server return a 404 error.
>>
>> I find that the db file is only created when the server receives a
>> REPLICATE request, but I do not know how to generate such a request, or why
>> does it not generate automatically.
>>
>> Moreover, what is the minimal amount of storage nodes?
>>
>> Thanks
>> Wenmao Liu
>>
>>
>> ___
>> 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] building customized packages

[Atul Jha]

Hi,



Hi,

Is the a wiki explaining the process to create my own deb packages?

Thanks,

Edgar



This might help http://wiki.debian.org/HowToPackageForDebian

Also if you are looking for answers related to packaging best place would be 
debian mailing list.

hope it helps~~

Cheers!!

Atul
http://www.csscorp.com/common/email-disclaimer.php

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

[Openstack] building customized packages

[Edgar Magana]

Hi,

Is the a wiki explaining the process to create my own deb packages?

Thanks,

Edgar
___
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 official packages

[skible.openst...@gmail.coma]

Hi Chuck,

Thanks for your reply.
In that case, i will upgrade my ubuntu server to 13.04 and download the 
grizzly packages from there. Is this the best you to get grizzly ?


regards,
Bilel
On 04/05/2013 07:21 PM, Chuck Short wrote:

Hi

They will not be backported to 12.10 only for 12.04.


chuck

On 13-04-05 03:32 AM, skible.openst...@gmail.coma wrote:

Hi there,

How can i add the official grizzly packages to ubuntu 12.10 ?

This seems to work fine on ubuntu 12.04 but not sure it does on 12.10 !
deb http://ubuntu-cloud.archive.canonical.com/ubuntu 
precise-updates/grizzly main


regards,
Stacker


___
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: Account not found[grizzly]

[Kuo Hugo]

1) No minimal limitation currently .
2) Did you set the above option to true ?
allow_account_management
https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L61

account_autocreate
https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L69


+Hugo Kuo+
h...@swiftstack.com
tonyt...@gmail.com
+886 935004793


2013/4/9 Liu Wenmao 

> Hi all:
>
> I just installed swift from github, after I configure a proxy node and a
> storage node, and run the stat command, it fails:
> # swift -v -V 2.0 -A http://controller:5000/v2.0 -U service:swift -K
> nsfocus stat
> Account not found
>
> Keystone and disk configuation seem OK, syslog gives:
> Apr  9 13:45:21 node1 account-server AUTH_2755db390fcd4c9bb504242617d5f6a0
> (txn: tx6919d8c66d454e50a9b03deded9b2ec8)
> Apr  9 13:45:21 node1 account-server 20.0.0.1 - - [09/Apr/2013:05:45:21
> +] "HEAD /swr/27113/AUTH_2755db390fcd4c9bb504242617d5f6a0" 404 -
> "tx6919d8c66d454e50a9b03deded9b2ec8" "-" "-" 0.0020 ""
>
> I read the code and find that the server try to visit db file:
> /srv/node/swr/accounts/27113/e03/1a7a753448a645fdf2b6bcc7223e5e03, but my
> directory  /srv/node/swr/accounts/ is empty, so server return a 404 error.
>
> I find that the db file is only created when the server receives a
> REPLICATE request, but I do not know how to generate such a request, or why
> does it not generate automatically.
>
> Moreover, what is the minimal amount of storage nodes?
>
> Thanks
> Wenmao Liu
>
>
> ___
> 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] root_helper deprecated?

[Rahul Upadhyaya]

Hi Liu, I think you should use : rootwrap_config=/etc/quantum/rootwrap.conf
Found this at below mentioned wiki page. I think this should hold true for
Quantum too.
https://wiki.openstack.org/wiki/Nova/Rootwrap
Refer to the section : Nova configuration

You must provide the location of the rootwrap configuration file to Nova,
by setting the following in *nova.conf*:



rootwrap_config=/etc/nova/rootwrap.conf


The configuration file used here must match the one defined in the
*sudoers* entry
(see below), otherwise the commands will be rejected ! There is no need to
specify the *root_helper* parameter anymore.


Regards,

Rahul.


On Tue, Apr 9, 2013 at 12:45 PM, Liu Wenmao  wrote:

> Hi all:
>
> In quantum dhcp grizzly log, I find the following warnings:
> 2013-04-09 15:12:48  WARNING [quantum.agent.common.config] Deprecated:
> DEFAULT.root_helper is deprecated!
>
> I do set root_helper in the ini file:
>  root_helper = sudo /usr/local/bin/quantum-rootwrap
> /etc/quantum/rootwrap.conf
>
> After I remove this line, it gives the following error:
> Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: 3 incorrect password attempts\n'
> 2013-04-09 15:07:56DEBUG [quantum.agent.linux.utils] Running command:
> ['sudo', 'cat', '/proc/5609/cmdline']
> 2013-04-09 15:07:56DEBUG [quantum.agent.linux.utils]
> Command: ['sudo', 'cat', '/proc/5609/cmdline']
>
>
> So it seems that I still have to use root_helper, then how can I get the
> warning removed?
>
> ___
> 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,
Rahul
===
___
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] root_helper deprecated?

[Liu Wenmao]

Hi all:

In quantum dhcp grizzly log, I find the following warnings:
2013-04-09 15:12:48  WARNING [quantum.agent.common.config] Deprecated:
DEFAULT.root_helper is deprecated!

I do set root_helper in the ini file:
 root_helper = sudo /usr/local/bin/quantum-rootwrap
/etc/quantum/rootwrap.conf

After I remove this line, it gives the following error:
Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try
again.\nsudo: no tty present and no askpass program specified\nSorry, try
again.\nsudo: no tty present and no askpass program specified\nSorry, try
again.\nsudo: 3 incorrect password attempts\n'
2013-04-09 15:07:56DEBUG [quantum.agent.linux.utils] Running command:
['sudo', 'cat', '/proc/5609/cmdline']
2013-04-09 15:07:56DEBUG [quantum.agent.linux.utils]
Command: ['sudo', 'cat', '/proc/5609/cmdline']


So it seems that I still have to use root_helper, then how can I get the
warning removed?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp