Re: [Openstack-operators] Designate keystone auth issue

[raju]

Thanks Kris appreciate your help, added the below lines
under [keystone_authtoken] now it is connecting to keystone

[keystone_authtoken]
auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357/
admin_tenant_name = service
admin_user = designate
admin_password = ATTlabs1!




On Tue, May 10, 2016 at 1:57 PM, Kris G. Lindgren 
wrote:

> Which section of the config did you add that to? The [keystone_authtoken]
> section?
>
> Also that section seems to want auth_host:
> https://github.com/openstack/designate/blob/master/etc/designate/designate.conf.sample#L158
> ___
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> From: raju 
> Date: Tuesday, May 10, 2016 at 11:52 AM
> To: "openstack-operators@lists.openstack.org" <
> openstack-operators@lists.openstack.org>
> Subject: [Openstack-operators] Designate keystone auth issue
>
> Hi All,
>
> I am trying to integrate designate(Dnaas) with my existing kilo
> environment and deployed designate in a separate node where I specified to
> connect to keystone(controller) server but still it is hitting on localhost
> while am trying to do api calls.
>
> designate conf:
>
> auth_uri = http://controller:5000/v2.0
> identity_uri = http://controller:35357/
> admin_tenant_name = service
> admin_user = designate
> admin_password = 
>
>
> error log:
>
> DEBUG keystoneclient.session [-] REQ: curl -g -i -X GET 
> *https://127.0.0.1:35357
> <https://127.0.0.1:35357> *-H "Accept: application/json" -H "User-Agent:
> python-keystoneclient" _http_log_request
> /usr/lib/python2.7/site-packages/keystoneclient/session.py:195
> 2016-05-10 13:39:38.175 27473 INFO
> requests.packages.urllib3.connectionpool [-] Starting new HTTPS connection
> (5): 127.0.0.1
> 2016-05-10 13:39:38.176 27473 WARNING keystonemiddleware.auth_token [-]
> Authorization failed for token
> 2016-05-10 13:39:38.177 27473 INFO keystonemiddleware.auth_token [-]
> Invalid user token - rejecting request
> 2016-05-10 13:39:38.177 27473 INFO eventlet.wsgi [-] 127.0.0.1 - -
> [10/May/2016 13:39:38] "GET /v1/servers HTTP/1.1" 401 283 0.005058
> 2016-05-10 13:39:38.363 27473 DEBUG keystoneclient.session [-] REQ: curl
> -g -i -X GET https://127.0.0.1:35357 -H "Accept: application/json" -H
> "User-Agent: python-keystoneclient" _http_log_request
> /usr/lib/python2.7/site-packages/keystoneclient/session.py:195
> 2016-05-10 13:39:38.365 27473 INFO
> requests.packages.urllib3.connectionpool [-] Starting new HTTPS connection
> (6): 127.0.0.1
> 2016-05-10 13:39:38.366 27473 WARNING keystonemiddleware.auth_token [-]
> Authorization failed for token
> 2016-05-10 13:39:38.366 27473 INFO keystonemiddleware.auth_token [-]
> Invalid user token - rejecting request
> 2016-05-10 13:39:38.367 27473 INFO eventlet.wsgi [-] 127.0.0.1 - -
> [10/May/2016 13:39:38] "GET /v1/servers HTTP/1.1" 401 283 0.004249
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Designate keystone auth issue

[raju]

Hi All,

I am trying to integrate designate(Dnaas) with my existing kilo environment
and deployed designate in a separate node where I specified to connect to
keystone(controller) server but still it is hitting on localhost while am
trying to do api calls.

designate conf:

auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357/
admin_tenant_name = service
admin_user = designate
admin_password = 


error log:

DEBUG keystoneclient.session [-] REQ: curl -g -i -X GET
*https://127.0.0.1:35357
 *-H "Accept: application/json" -H "User-Agent:
python-keystoneclient" _http_log_request
/usr/lib/python2.7/site-packages/keystoneclient/session.py:195
2016-05-10 13:39:38.175 27473 INFO requests.packages.urllib3.connectionpool
[-] Starting new HTTPS connection (5): 127.0.0.1
2016-05-10 13:39:38.176 27473 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token
2016-05-10 13:39:38.177 27473 INFO keystonemiddleware.auth_token [-]
Invalid user token - rejecting request
2016-05-10 13:39:38.177 27473 INFO eventlet.wsgi [-] 127.0.0.1 - -
[10/May/2016 13:39:38] "GET /v1/servers HTTP/1.1" 401 283 0.005058
2016-05-10 13:39:38.363 27473 DEBUG keystoneclient.session [-] REQ: curl -g
-i -X GET https://127.0.0.1:35357 -H "Accept: application/json" -H
"User-Agent: python-keystoneclient" _http_log_request
/usr/lib/python2.7/site-packages/keystoneclient/session.py:195
2016-05-10 13:39:38.365 27473 INFO requests.packages.urllib3.connectionpool
[-] Starting new HTTPS connection (6): 127.0.0.1
2016-05-10 13:39:38.366 27473 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token
2016-05-10 13:39:38.366 27473 INFO keystonemiddleware.auth_token [-]
Invalid user token - rejecting request
2016-05-10 13:39:38.367 27473 INFO eventlet.wsgi [-] 127.0.0.1 - -
[10/May/2016 13:39:38] "GET /v1/servers HTTP/1.1" 401 283 0.004249
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Security group rules not working on instances kilo

[raju]

Thanks Kris, issue resolved after adding below lines to sysctl.conf

net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-arptables = 1
net.bridge.bridge-nf-call-ip6tables = 1


appreciate your help, thanks a lot again.




On Thu, Apr 21, 2016 at 8:25 PM, Kris G. Lindgren 
wrote:

> Make sure that the bridges are being created (1 bridge per vm) they should
> be named close to the vm tap device name.  Then make sure that you have
> bridge nf-call-* files enabled:
>
> http://wiki.libvirt.org/page/Net.bridge.bridge-nf-call_and_sysctl.conf
>
> Under hybrid mode what happens is a linux bridge (not an ovs bridge
> (brctl)) is created per vm.  The vm's tap device is plugged into this
> bridge.  A veth is created that spans from the vm's linux bridge to br-int
> and is plugged at both ends.  This is done because older versions of OVS
> did not have support (or efficient support) for doing firewalling.  The
> problem is that in the kernel, packets traversing the Openvswitch code
> paths are unable to be hooked into by netfilter.  So the linux bridge is
> created solely to allow the VM traffic to pass through a netfilter
> hookable location, so security groups work.
>
> You need at a minimum to make sure
> /proc/sys/net/bridge/bridge-nf-call-iptables is set to 1.  If its not then
> when you look at the iptables rules that are created – you will see that
> none of the security group chains are seeing traffic.
> ___
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> From: raju 
> Date: Thursday, April 21, 2016 at 5:26 PM
> To: "openstack-operators@lists.openstack.org" <
> openstack-operators@lists.openstack.org>
> Subject: [Openstack-operators] Security group rules not working on
> instances kilo
>
> Hi,
>
> I am running into a issue where security group rules are not applying to
> instances when I create a new security group with default rules it should
> reject all incoming traffic but it is allowing everything without blocking
>
> here is my config for nova :
>
> security_group_api = neutron
> firewall_driver = nova.virt.firewall.NoopFirewallDriver
>
> and in ml2.con.ini
>
> firewall_driver =
> neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
>
> iptables service is running on all the nodes, please suggest me if  I miss
> anything.
>
>
> Thanks.
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Security group rules not working on instances kilo

[raju]

Hi,

I am running into a issue where security group rules are not applying to
instances when I create a new security group with default rules it should
reject all incoming traffic but it is allowing everything without blocking

here is my config for nova :

security_group_api = neutron
firewall_driver = nova.virt.firewall.NoopFirewallDriver

and in ml2.con.ini

firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver

iptables service is running on all the nodes, please suggest me if  I miss
anything.


Thanks.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Cinder-backup to swift

[raju]

Kevin/Swami,

Now it is working fine, created new volume after changing the services to
same host resolved the issue.

appreciate your help

On Tue, Jan 26, 2016 at 2:04 PM, Fox, Kevin M  wrote:

> crank up debugging and look in the logs? anything interesting?
>
> Thanks,
> Kevin
> --
> *From:* raju [raju.r...@gmail.com]
> *Sent:* Tuesday, January 26, 2016 9:55 AM
> *To:* Fox, Kevin M
> *Cc:* openstack-operators@lists.openstack.org
> *Subject:* Re: [Openstack-operators] Cinder-backup to swift
>
> now both services running on same host still same issue
>
>  cinder service-list
>
> +--+-+--+-+---++-+
> |  Binary  |   Host  | Zone |  Status |
> State | Updated_at | Disabled Reason |
>
> +--+-+--+-+---++-+
> |  cinder-backup   |node-7..stack   | nova | enabled |   up  |
> 2016-01-26T17:53:44.00 |   None  |
> | cinder-scheduler |node-7..stack   | nova | enabled |   up  |
> 2016-01-26T17:53:47.00 |   None  |
> |  cinder-volume   | node-7..stack@pure | nova | enabled |   up  |
> 2016-01-26T17:53:43.00 |   None  |
>
> +--+-+--+-+---++-+
> root@node-7:~# cinder backup-create --container Cinder_Backup
> 0d2eb15f-77b9-408b-86c3-e80fb24948cf
> ERROR: Service cinder-backup could not be found. (HTTP 500) (Request-ID:
> req-c7e7555a-4fe0-4d09-9a3b-3a71e3c7d962)
>
>
> On Tue, Jan 26, 2016 at 11:37 AM, Fox, Kevin M  wrote:
>
>> There is a "feature" where cinder-backup and cinder-volume must be
>> running on the same node. If they are not, you get an error like that. I
>> tripped over it myself.
>>
>> Thanks,
>> Kevin
>> --
>> *From:* raju [raju.r...@gmail.com]
>> *Sent:* Tuesday, January 26, 2016 8:16 AM
>> *To:* openstack-operators@lists.openstack.org
>> *Subject:* [Openstack-operators] Cinder-backup to swift
>>
>>
>> Hi,
>>
>>
>> I am trying to backup cinder volumes to swift and enabled backup driver
>> in cinder conf and startred cinder-backup service, when am trying to create
>> a backup it is failing with below error
>>
>>
>>
>> Error:
>>
>> cinder backup-create --container Cinder_Backup
>> 0d2eb15f-77b9-408b-86c3-e80fb24948cf
>>
>>
>> ERROR: Service cinder-backup could not be found. (HTTP 500) (Request-ID:
>> req-2ce2bee4-d237-4191-b9ea-48a72ccbb579)
>>
>>
>> # cinder service-list
>>
>>
>> +--+-+--+--+---++-+
>>
>> |  Binary  | Host| Zone |  Status  |
>> State | Updated_at | Disabled Reason |
>>
>>
>> +--+-+--+--+---++-+
>>
>> |  cinder-backup   |  node-7..stack | nova | enabled  |   up  |
>> 2016-01-25T22:03:09.00 |   None  |
>>
>> | cinder-scheduler |  node-7..stack | nova | enabled  |   up  |
>> 2016-01-25T22:03:06.00 |   None  |
>>
>>  |
>>
>> |  cinder-volume   |  pure@pure  | nova | enabled  |
>> up  | 2016-01-25T22:03:09.00 |   None  |
>>
>>
>> +--+-+--+--+---++-+
>>
>>
>> service cinder-backup status
>>
>> cinder-backup start/running, process 21223
>>
>>
>> LOG:
>>
>>
>> INFO cinder.api.openstack.wsgi [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3
>> 7bc0cb1d6c394eb598b4612b49b6b891 56083ff01d5d42848f3c8d227ed70006 - - -]
>> GET
>> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
>>
>> 2016-01-26 16:15:23.012 11301 INFO cinder.api.openstack.wsgi
>> [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0cb1d6c394eb598b4612b49b6b891
>> 56083ff01d5d42848f3c8d227ed70006 - - -]
>> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
>> returned with HTTP 200
>>
>> 2016-01-26 16:15:23.014 11301 INFO eventlet.wsgi.server
>> [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0

Re: [Openstack-operators] Cinder-backup to swift

[raju]

now both services running on same host still same issue

 cinder service-list
+--+-+--+-+---++-+
|  Binary  |   Host  | Zone |  Status |
State | Updated_at | Disabled Reason |
+--+-+--+-+---++-+
|  cinder-backup   |node-7..stack   | nova | enabled |   up  |
2016-01-26T17:53:44.00 |   None  |
| cinder-scheduler |node-7..stack   | nova | enabled |   up  |
2016-01-26T17:53:47.00 |   None  |
|  cinder-volume   | node-7..stack@pure | nova | enabled |   up  |
2016-01-26T17:53:43.00 |   None  |
+--+-+--+-+---++-+
root@node-7:~# cinder backup-create --container Cinder_Backup
0d2eb15f-77b9-408b-86c3-e80fb24948cf
ERROR: Service cinder-backup could not be found. (HTTP 500) (Request-ID:
req-c7e7555a-4fe0-4d09-9a3b-3a71e3c7d962)


On Tue, Jan 26, 2016 at 11:37 AM, Fox, Kevin M  wrote:

> There is a "feature" where cinder-backup and cinder-volume must be running
> on the same node. If they are not, you get an error like that. I tripped
> over it myself.
>
> Thanks,
> Kevin
> --
> *From:* raju [raju.r...@gmail.com]
> *Sent:* Tuesday, January 26, 2016 8:16 AM
> *To:* openstack-operators@lists.openstack.org
> *Subject:* [Openstack-operators] Cinder-backup to swift
>
>
> Hi,
>
>
> I am trying to backup cinder volumes to swift and enabled backup driver in
> cinder conf and startred cinder-backup service, when am trying to create a
> backup it is failing with below error
>
>
>
> Error:
>
> cinder backup-create --container Cinder_Backup
> 0d2eb15f-77b9-408b-86c3-e80fb24948cf
>
>
> ERROR: Service cinder-backup could not be found. (HTTP 500) (Request-ID:
> req-2ce2bee4-d237-4191-b9ea-48a72ccbb579)
>
>
> # cinder service-list
>
>
> +--+-+--+--+---++-+
>
> |  Binary  | Host| Zone |  Status  | State
> | Updated_at | Disabled Reason |
>
>
> +--+-+--+--+---++-+
>
> |  cinder-backup   |  node-7..stack | nova | enabled  |   up  |
> 2016-01-25T22:03:09.00 |   None  |
>
> | cinder-scheduler |  node-7..stack | nova | enabled  |   up  |
> 2016-01-25T22:03:06.00 |   None  |
>
>  |
>
> |  cinder-volume   |  pure@pure  | nova | enabled  |   up
>  | 2016-01-25T22:03:09.00 |   None  |
>
>
> +--+-+--+--+---++-+
>
>
> service cinder-backup status
>
> cinder-backup start/running, process 21223
>
>
> LOG:
>
>
> INFO cinder.api.openstack.wsgi [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3
> 7bc0cb1d6c394eb598b4612b49b6b891 56083ff01d5d42848f3c8d227ed70006 - - -]
> GET
> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
>
> 2016-01-26 16:15:23.012 11301 INFO cinder.api.openstack.wsgi
> [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -]
> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
> returned with HTTP 200
>
> 2016-01-26 16:15:23.014 11301 INFO eventlet.wsgi.server
> [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -] 10.24.4.2 - - [26/Jan/2016
> 16:15:23] "GET
> /v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
> HTTP/1.1" 200 963 0.417786
>
> 2016-01-26 16:15:23.030 11299 INFO eventlet.wsgi.server [-] (11299)
> accepted ('10.24.4.2', 37650)
>
> 2016-01-26 16:15:23.123 11299 INFO cinder.api.openstack.wsgi
> [req-b1d4c37a-70e7-40d0-ac39-e5f109d4f62f 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -] POST
> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/backups
>
> 2016-01-26 16:15:23.125 11299 INFO cinder.api.contrib.backups
> [req-b1d4c37a-70e7-40d0-ac39-e5f109d4f62f 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -] Creating backup of volume
> 0d2eb15f-77b9-408b-86c3-e80fb24948cf in container Cinder_Backup
>
> 2016-01-26 16:15:23.193 11299 INFO cinder.api.

Re: [Openstack-operators] Cinder-backup to swift

[raju]

Thanks Kevin.

On Tue, Jan 26, 2016 at 11:37 AM, Fox, Kevin M  wrote:

> There is a "feature" where cinder-backup and cinder-volume must be running
> on the same node. If they are not, you get an error like that. I tripped
> over it myself.
>
> Thanks,
> Kevin
> --
> *From:* raju [raju.r...@gmail.com]
> *Sent:* Tuesday, January 26, 2016 8:16 AM
> *To:* openstack-operators@lists.openstack.org
> *Subject:* [Openstack-operators] Cinder-backup to swift
>
>
> Hi,
>
>
> I am trying to backup cinder volumes to swift and enabled backup driver in
> cinder conf and startred cinder-backup service, when am trying to create a
> backup it is failing with below error
>
>
>
> Error:
>
> cinder backup-create --container Cinder_Backup
> 0d2eb15f-77b9-408b-86c3-e80fb24948cf
>
>
> ERROR: Service cinder-backup could not be found. (HTTP 500) (Request-ID:
> req-2ce2bee4-d237-4191-b9ea-48a72ccbb579)
>
>
> # cinder service-list
>
>
> +--+-+--+--+---++-+
>
> |  Binary  | Host| Zone |  Status  | State
> | Updated_at | Disabled Reason |
>
>
> +--+-+--+--+---++-+
>
> |  cinder-backup   |  node-7..stack | nova | enabled  |   up  |
> 2016-01-25T22:03:09.00 |   None  |
>
> | cinder-scheduler |  node-7..stack | nova | enabled  |   up  |
> 2016-01-25T22:03:06.00 |   None  |
>
>  |
>
> |  cinder-volume   |  pure@pure  | nova | enabled  |   up
>  | 2016-01-25T22:03:09.00 |   None  |
>
>
> +--+-+--+--+---++-+
>
>
> service cinder-backup status
>
> cinder-backup start/running, process 21223
>
>
> LOG:
>
>
> INFO cinder.api.openstack.wsgi [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3
> 7bc0cb1d6c394eb598b4612b49b6b891 56083ff01d5d42848f3c8d227ed70006 - - -]
> GET
> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
>
> 2016-01-26 16:15:23.012 11301 INFO cinder.api.openstack.wsgi
> [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -]
> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
> returned with HTTP 200
>
> 2016-01-26 16:15:23.014 11301 INFO eventlet.wsgi.server
> [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -] 10.24.4.2 - - [26/Jan/2016
> 16:15:23] "GET
> /v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
> HTTP/1.1" 200 963 0.417786
>
> 2016-01-26 16:15:23.030 11299 INFO eventlet.wsgi.server [-] (11299)
> accepted ('10.24.4.2', 37650)
>
> 2016-01-26 16:15:23.123 11299 INFO cinder.api.openstack.wsgi
> [req-b1d4c37a-70e7-40d0-ac39-e5f109d4f62f 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -] POST
> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/backups
>
> 2016-01-26 16:15:23.125 11299 INFO cinder.api.contrib.backups
> [req-b1d4c37a-70e7-40d0-ac39-e5f109d4f62f 7bc0cb1d6c394eb598b4612b49b6b891
> 56083ff01d5d42848f3c8d227ed70006 - - -] Creating backup of volume
> 0d2eb15f-77b9-408b-86c3-e80fb24948cf in container Cinder_Backup
>
> 2016-01-26 16:15:23.193 11299 INFO cinder.api.openstack.wsgi
> [req-f698019f-d0cf-4057-857e-37aef6c40bbe - - - - -] HTTP exception thrown:
> Service cinder-backup could not be found.
>
> 2016-01-26 16:15:23.196 11299 INFO cinder.api.openstack.wsgi
> [req-f698019f-d0cf-4057-857e-37aef6c40bbe - - - - -]
> http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/backups
> returned with HTTP 500
>
> 2016-01-26 16:15:23.199 11299 INFO eventlet.wsgi.server
> [req-f698019f-d0cf-4057-857e-37aef6c40bbe - - - - -] 10.24.4.2 - -
> [26/Jan/2016 16:15:23] "POST /v1/56083ff01d5d42848f3c8d227ed70006/backups
> HTTP/1.1" 500 378 0.158105
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Cinder-backup to swift

[raju]

Hi,


I am trying to backup cinder volumes to swift and enabled backup driver in
cinder conf and startred cinder-backup service, when am trying to create a
backup it is failing with below error



Error:

cinder backup-create --container Cinder_Backup
0d2eb15f-77b9-408b-86c3-e80fb24948cf


ERROR: Service cinder-backup could not be found. (HTTP 500) (Request-ID:
req-2ce2bee4-d237-4191-b9ea-48a72ccbb579)


# cinder service-list

+--+-+--+--+---++-+

|  Binary  | Host| Zone |  Status  | State
| Updated_at | Disabled Reason |

+--+-+--+--+---++-+

|  cinder-backup   |  node-7..stack | nova | enabled  |   up  |
2016-01-25T22:03:09.00 |   None  |

| cinder-scheduler |  node-7..stack | nova | enabled  |   up  |
2016-01-25T22:03:06.00 |   None  |

 |

|  cinder-volume   |  pure@pure  | nova | enabled  |   up
 | 2016-01-25T22:03:09.00 |   None  |

+--+-+--+--+---++-+


service cinder-backup status

cinder-backup start/running, process 21223


LOG:


INFO cinder.api.openstack.wsgi [req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3
7bc0cb1d6c394eb598b4612b49b6b891 56083ff01d5d42848f3c8d227ed70006 - - -]
GET
http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf

2016-01-26 16:15:23.012 11301 INFO cinder.api.openstack.wsgi
[req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0cb1d6c394eb598b4612b49b6b891
56083ff01d5d42848f3c8d227ed70006 - - -]
http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
returned with HTTP 200

2016-01-26 16:15:23.014 11301 INFO eventlet.wsgi.server
[req-6ea85659-aa48-4dfd-8ca4-bf21c34537f3 7bc0cb1d6c394eb598b4612b49b6b891
56083ff01d5d42848f3c8d227ed70006 - - -] 10.24.4.2 - - [26/Jan/2016
16:15:23] "GET
/v1/56083ff01d5d42848f3c8d227ed70006/volumes/0d2eb15f-77b9-408b-86c3-e80fb24948cf
HTTP/1.1" 200 963 0.417786

2016-01-26 16:15:23.030 11299 INFO eventlet.wsgi.server [-] (11299)
accepted ('10.24.4.2', 37650)

2016-01-26 16:15:23.123 11299 INFO cinder.api.openstack.wsgi
[req-b1d4c37a-70e7-40d0-ac39-e5f109d4f62f 7bc0cb1d6c394eb598b4612b49b6b891
56083ff01d5d42848f3c8d227ed70006 - - -] POST
http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/backups

2016-01-26 16:15:23.125 11299 INFO cinder.api.contrib.backups
[req-b1d4c37a-70e7-40d0-ac39-e5f109d4f62f 7bc0cb1d6c394eb598b4612b49b6b891
56083ff01d5d42848f3c8d227ed70006 - - -] Creating backup of volume
0d2eb15f-77b9-408b-86c3-e80fb24948cf in container Cinder_Backup

2016-01-26 16:15:23.193 11299 INFO cinder.api.openstack.wsgi
[req-f698019f-d0cf-4057-857e-37aef6c40bbe - - - - -] HTTP exception thrown:
Service cinder-backup could not be found.

2016-01-26 16:15:23.196 11299 INFO cinder.api.openstack.wsgi
[req-f698019f-d0cf-4057-857e-37aef6c40bbe - - - - -]
http://10.24.4.2:8776/v1/56083ff01d5d42848f3c8d227ed70006/backups returned
with HTTP 500

2016-01-26 16:15:23.199 11299 INFO eventlet.wsgi.server
[req-f698019f-d0cf-4057-857e-37aef6c40bbe - - - - -] 10.24.4.2 - -
[26/Jan/2016 16:15:23] "POST /v1/56083ff01d5d42848f3c8d227ed70006/backups
HTTP/1.1" 500 378 0.158105
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Liberty neutron issues

[raju]

Hi,

I have done all the configuration in ml2 plugin here is my  ml2_conf.ini
config file


http://paste.ubuntu.com/14567407/

On Sat, Jan 16, 2016 at 8:29 PM, Joseph Bajin  wrote:

> Your entire configuration for VLAN, VXLAN, etc should be done within the
> ml2 configuration and not really through ovs.  All OVS needs to know about
> are the bridges that you setup and what they are called and going to be
> used for.  Any specific configurations will happen on the system side and
> not the ovs side of things.
>
> On Fri, Jan 15, 2016 at 4:52 PM, raju  wrote:
>
>> Hi,
>>
>> I have done 3 node deployment of openstack liberty on cent os 7 and
>> configured neutron with ml2 and ovs. when am trying to spin up instances
>> getting neutron error unable to bind port to  host am pasting logs files
>> and ml2 conf file below
>>
>> These are the steps followed to create ovs bridges
>>
>> I have 2 physical interface eth0 is management and eth1 is trunk for all
>> public/vlan/vxlan traffic
>>  ovs-vsctl add-br br-uplink
>> ovs-vsctl add-br br-vlan
>>  ovs-vsctl add-br br-int
>>  ovs-vsctl add-port br-uplink eth1 -- set port eth1 vlan_mode=trunk
>> trunk=100,101,200,201,4000
>>  ovs-vsctl add-port br-vlan patch-to-uplink -- set Interface
>> patch-to-uplink type=patch options:peer=patch-to-vlan
>>  ovs-vsctl add-port br-uplink patch-to-vlan -- set Interface
>> patch-to-vlan type=patch options:peer=patch-to-uplink
>>  #
>> vs-vsctl add-port br-uplink l3vxlan tag=4000 -- set Interface l3vxlan
>> type=internal
>>  ip addr add 10.255.255.XXX/24 dev l3vxlan
>> ip link set dev l3vxlan up
>>  ip link set dev l3vxlan mtu 1600
>>
>> Neutron log: http://paste.ubuntu.com/14508309/
>>
>> OVS log network node:  http://paste.ubuntu.com/14508422/
>>
>> ovs-vsctl show output: http://paste.ubuntu.com/14508685/
>>
>>
>> Thanks
>>
>>
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Liberty neutron issues

[raju]

Hi,

I have done 3 node deployment of openstack liberty on cent os 7 and
configured neutron with ml2 and ovs. when am trying to spin up instances
getting neutron error unable to bind port to  host am pasting logs files
and ml2 conf file below

These are the steps followed to create ovs bridges

I have 2 physical interface eth0 is management and eth1 is trunk for all
public/vlan/vxlan traffic
 ovs-vsctl add-br br-uplink
ovs-vsctl add-br br-vlan
 ovs-vsctl add-br br-int
 ovs-vsctl add-port br-uplink eth1 -- set port eth1 vlan_mode=trunk
trunk=100,101,200,201,4000
 ovs-vsctl add-port br-vlan patch-to-uplink -- set Interface
patch-to-uplink type=patch options:peer=patch-to-vlan
 ovs-vsctl add-port br-uplink patch-to-vlan -- set Interface patch-to-vlan
type=patch options:peer=patch-to-uplink
 #
vs-vsctl add-port br-uplink l3vxlan tag=4000 -- set Interface l3vxlan
type=internal
 ip addr add 10.255.255.XXX/24 dev l3vxlan
ip link set dev l3vxlan up
 ip link set dev l3vxlan mtu 1600

Neutron log: http://paste.ubuntu.com/14508309/

OVS log network node:  http://paste.ubuntu.com/14508422/

ovs-vsctl show output: http://paste.ubuntu.com/14508685/


Thanks
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] kilo/nfv-vlan-trunks

[raju]

Hi Team,

I need to create trunk ports inside neutron where instances will receive
traffic from multiple vlans.

Do I need to apply any patch to my current openstack version(kilo) to get
this feature?


Thanks
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Fwd: Patching openstack

[raju]

Exactly Ben, lets say I have issues with nova in my environment how to fix
those bugs by manually getting it from git and packaging are there any
steps how to follow and backup the current version to roll back?

On Wed, Sep 16, 2015 at 3:04 PM, Ben Hines  wrote:

> It sounds like he's talking about bugs which are already fixed, on
> github or elsewhere. You can't always wait until the next openstack
> release to apply a critical fix.
>
> I use Puppet to apply any custom patches, which keeps them carefully
> tracked and source controlled.
>
> -Ben
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Neutron Lbaas Issues Icehouse

[raju]

Anyone came across this issue?

On Tue, Sep 1, 2015 at 8:17 PM, raju  wrote:

> Hi All,
>
> I have configured lbaas in my Icehouse environment and able to start the
> lbaas agent without any issues. When I create a pool it creates sussfully
> without any errors but in log file it shows
>
>  WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver
> [-] Stats socket not found for pool 3b9eb090-1d57-466e-b83e-552ead86a677
>
> it is not creating namespace while adding pool but when adding VIP it
> creates a ns and vtep interfaces with error state and I need to delete
> those vtep interfaes manualy using ip netns delete
>
>
> Neutron.conf
>
>
> service_provider=LOADBALANCER:Haproxy:neutron.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
>
> service_plugins =neutron.services.loadbalancer.plugin.LoadBalancerPlugin
>
> lbaas_agent.ini
>
> interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
> device_driver =
> neutron.services.loadbalancer.drivers.haproxy.namespace_driver.HaproxyNSDriver
> user_group = haproxy
>
> Thanks in advance
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Neutron Lbaas Issues Icehouse

[raju]

Hi All,

I have configured lbaas in my Icehouse environment and able to start the
lbaas agent without any issues. When I create a pool it creates sussfully
without any errors but in log file it shows

 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-]
Stats socket not found for pool 3b9eb090-1d57-466e-b83e-552ead86a677

it is not creating namespace while adding pool but when adding VIP it
creates a ns and vtep interfaces with error state and I need to delete
those vtep interfaes manualy using ip netns delete


Neutron.conf

service_provider=LOADBALANCER:Haproxy:neutron.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default

service_plugins =neutron.services.loadbalancer.plugin.LoadBalancerPlugin

lbaas_agent.ini

interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
device_driver =
neutron.services.loadbalancer.drivers.haproxy.namespace_driver.HaproxyNSDriver
user_group = haproxy

Thanks in advance
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] How to restrict AvZones to Tenants

[raju]

Tried the below way, still able to access other AVzones also

nova aggregate-set-metadata  filter_tenant_id=

Thanks for all your replies, appreciate it.


On Wed, Aug 26, 2015 at 9:55 PM, gustavo panizzo  
wrote:

> On Thu, Aug 27, 2015 at 11:26:42 +1000, Marcus Furlong wrote:
> > On 27 August 2015 at 06:48, raju  wrote:
> > > Hi,
> > >
> > > I want to restrict Avzones to particular Tenant so that users in the
> Tenant
> > > can only see the particular Avzone from drop down while provisioning
> > > instances.
>
> you can add a *filter_tenant_id* key on the aggregate which makes the AZ
> and configure AggregateMultiTenancyIsolation filter, that will exclude
> other tenants from those hypervisors, AZ will still be visible by other
> tenants but they won't be able to use it
>
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
>
> keybase: http://keybase.io/gfa
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] How to restrict AvZones to Tenants

[raju]

Hi,

I want to restrict Avzones to particular Tenant so that users in the Tenant
can only see the particular Avzone from drop down while provisioning
instances.


Thanks
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Failed to start Initial cloud-init job (metadata service crawler)

[raju]

Hi All,

I have created Ubuntu 15.4 cloud image in my openstack Icehouse, whenever I
deploy instance using 15.04 image it does not get default route added

Same image is working fine in Juno environment and and all the other images
are working fine in Icehouse


I see the below error in logs

[1;31mFAILED[0m] Failed to start Initial cloud-init job (metadata
service crawler).
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Juno Lost connectivity to instance and new instances not getting IP

[raju]

I have lost connectivity to all my instances and new instances does not get
IP from DHCP, I am getting  below errors from ovs-agent


ov-agent log

http://paste.openstack.org/show/196902/

ovs-vsct output for both compute nodes

http://paste.openstack.org/show/196903/

TCP dump for br-int ex and eno2 for computenodes

http://paste.openstack.org/show/196905/

Thanks
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Unable to delete few instances from dashboard

[raju]

Detached volumes and tried deleting the instances from dashboard not working

On Wed, Feb 18, 2015 at 9:57 PM, raju  wrote:

> There was no error seems the delete action is not getting triggered, am
> trying with admin credentials still no luck some with volumes and some are
> not As Basil mentioned VM's which are in second page
>
>
>
>
> On Wed, Feb 18, 2015 at 5:39 PM, Abel Lopez  wrote:
>
>> It's really tough to know without any additional information.
>> Was there an error on the dashboard? Are you using the same credentials?
>> Did these instances have volumes attached?
>>
>> > On Feb 18, 2015, at 12:47 PM, raju  wrote:
>> >
>> > Hi,
>> >
>> > am unable to delete few instances from dashboard(Havana) but able to
>> delete from nova cmd line is there any way to resolve the issue?
>> > ___
>> > OpenStack-operators mailing list
>> > OpenStack-operators@lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Unable to delete few instances from dashboard

[raju]

There was no error seems the delete action is not getting triggered, am
trying with admin credentials still no luck some with volumes and some are
not As Basil mentioned VM's which are in second page




On Wed, Feb 18, 2015 at 5:39 PM, Abel Lopez  wrote:

> It's really tough to know without any additional information.
> Was there an error on the dashboard? Are you using the same credentials?
> Did these instances have volumes attached?
>
> > On Feb 18, 2015, at 12:47 PM, raju  wrote:
> >
> > Hi,
> >
> > am unable to delete few instances from dashboard(Havana) but able to
> delete from nova cmd line is there any way to resolve the issue?
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Unable to delete few instances from dashboard

[raju]

Hi,

am unable to delete few instances from dashboard(Havana) but able to delete
from nova cmd line is there any way to resolve the issue?
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] conductor.log spiking up

[raju]

Hi Team,

in my openstack(Havana) controller node conductor.log is spiking very
fastly and eating all my disk space not sure what is wrong in Nova here is
the below message looping in the log


2015-01-23 16:17:40.248 27615 DEBUG qpid.messaging [-] RACK[5e56a70]:
Message({'oslo.message': '{"_unique_id":
"28f19d56399441348811e1f582c34e81", "failure": null, "_msg_id":
"5985125dc7454c2480a9ed4ef3c7843a", "result": null, "ending": true}',
'oslo.version': '2.0'}) msg_acked
/usr/lib/python2.6/site-packages/qpid/messaging/driver.py:1271


Thanks in Advance
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] extend the ip address of subnet in Havana?

[raju]

Appreciate your response, it was very clear explanation, will try this and
let you know the result.

Thanks much

On Thu, Oct 9, 2014 at 4:16 PM, Mathieu Gagné  wrote:

> On 2014-10-09 3:08 PM, raju wrote:
>
>> I tried changing in DB but doesn't work, I see that Havana Neutron
>> doesn't   have option to expand subnet allocation pools
>>
>>
> Neutron does not allow you to shrink or expand an existing allocation
> pool, nor add allocation pools to an existing subnet.
>
>
> From memory, there is more than one entry to update in Neutron database:
>
> 1) neutron.subnets.cidr
>This is the subnet definition.
>
> 2) neutron.ipallocationpools
>This is the allocation pool definition.
>
> 3) neutron.ipavailabilityranges
>This is the ranges of IPs FREE in the allocation pool.
>
>
> A. Update the subnet definition (if needed)
>
> If the subnet netmask changes, you need to update the 'cidr' field in the
> 'neutron.subnets' table with the new subnet definition.
>
> This change won't:
> - expand the existing subnet's allocation pool
> - give you new IPs to use in instances
> - change netmask already configured in existing instances.
>
> This will only update the subnet definition.
>
>
> B. Extending an allocation pool
>
> You need to update the 'neutron.ipallocationpools' table to expand the
> definition of the existing allocation pool.
>
> Find the entry associated to the subnet and update the 'last_ip' field
> with the new allocation range.
>
> This won't give you new IPs but only update the allocation pool
> definition. Makes sure the 'last_ip' does not go beyond the subnet
> definition range.
>
> Now, to add new free IPs, you need to insert new entries in the
> 'neutron.ipavailabilityranges' table. This table contains *ranges* of FREE
> IPs. Therefore you have to add a new range entry corresponding to the
> existing subnet allocation pool (allocation_pool_id).
>
> The 'first_ip' field corresponds to the first free ip of the new range and
> 'last_ip' to the last free ip. This will give you new IPs available.
>
>
> C. Add an allocation pool
>
> Add a new entry in the 'neutron.ipallocationpools' table corresponding to
> your new allocation pool definition. The 'id' field should be a NEW
> *unique* uuid and 'subnet_id' the subnet to which you wish to add an
> allocation pool. Make sure allocation pools don't overlap.
>
> Then add a new entry in the 'neutron.ipavailabilityranges' table. Use the
> previous uuid for the 'allocation_pool_id' field and the same values in
> 'first_ip' and 'last_ip' fields as the ones put in
> 'neutron.ipallocationpools'.
>
> You will then have new IPs available.
>
>
> Always *backup* your data and *test* in a development environment first.
>
>
> --
> Mathieu
>
>
>
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] extend the ip address of subnet in Havana?

[raju]

I tried changing in DB but doesn't work, I see that Havana Neutron doesn't
  have option to expand subnet allocation pools

On Thu, Oct 9, 2014 at 1:00 PM, raju  wrote:

> Neutron
>
> On Thu, Oct 9, 2014 at 12:57 PM, Abel Lopez  wrote:
>
>> Using neutron or nova-network?
>>
>> On Oct 9, 2014, at 9:47 AM, raju  wrote:
>>
>> > Hi All,
>> >
>> > Is there any way to extend the ip address of subnet Havana?
>> > ___
>> > OpenStack-operators mailing list
>> > OpenStack-operators@lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] extend the ip address of subnet in Havana?

[raju]

Neutron

On Thu, Oct 9, 2014 at 12:57 PM, Abel Lopez  wrote:

> Using neutron or nova-network?
>
> On Oct 9, 2014, at 9:47 AM, raju  wrote:
>
> > Hi All,
> >
> > Is there any way to extend the ip address of subnet Havana?
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] extend the ip address of subnet in Havana?

[raju]

Hi All,

Is there any way to extend the ip address of subnet Havana?
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Lbaas and Fwaas on prod environment

[raju]

Hi Team,

I am having running Havana environment on RHEL I want to add Lbaas and
Fwaas now, can anyone guide me through the configuration or good
documentation?
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators