date:20160126

Re: [Openstack-operators] DVR and public IP consumption

2016-01-26 Thread Carl Baldwin

On Thu, Jan 14, 2016 at 2:45 AM, Tomas Vondra  wrote:
> Hi!
> I have just deployed an OpenStack Kilo installation with DVR and expected
> that it will consume one Public IP per network node as per
> http://assafmuller.com/2015/04/15/distributed-virtual-routing-floating-ips/,
> but it still eats one per virtual Router.
> What is the correct behavior?

Regardless of DVR, a Neutron router burns one IP per virtual router
which it uses to SNAT traffic from instances that do not have floating
IPs.

When you use DVR, an additional IP is consumed for each compute host
running an L3 agent in DVR mode.  There has been some discussion about
how this can be eliminated but no action has been taken to do this.

> Otherwise, it works as a DVR should according to documentation. There are
> router namespaces at both compute and network nodes, snat namespaces at the
> network nodes and fip namespaces at the compute nodes. Every router has a
> router_interface_distributed and a router_centralized_snat with private IPs,
> however the router_gateway has a public IP, which I would like to getr id of
> to increase density.

I'm not sure if it is possible to avoid burning these IPs at this
time.  Maybe someone else can chime in with more detail.

Carl

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

Re: [Openstack-operators] [tc][security] Proposal to change the CVE embargo window

2016-01-26 Thread Doug Hellmann

Excerpts from John Dickinson's message of 2016-01-25 10:58:19 -0800:
> I'd like to lengthen the embargo window on CVE disclosures.
> 
> Currently, the process is this 
> (https://security.openstack.org/vmt-process.html):
> 
>   1. A security bug is reported (and confirmed as valid)
>   2. A patch is developed an reviewed
>   3. After the proposed fix is approved by reviewers, A CVE is filed
>   4. 3-5 business days later, the vulnerability is disclosed publicly and the 
> patches are landed upstream
> 
> The problem as I see it is that the 3 to 5 day embargo is way too short. 
> Specifically, for those supporting OpenStack projects in a product, the short 
> embargo does not allow sufficient time for applying, testing, and staging the 
> fix in time for the disclosure. This leaves end-users and deployers with the 
> situation of having a publicly announced security vulnerability without any 
> hope of having a fix.
> 
> I would like the embargo period to be lengthened to be 2 weeks.
> 
> --John

I wasn't involved in the discussions that set the current embargo
window. Do we have a record of why that length of time was selected?
Was it based on feedback at the time? I don't have a problem with
lengthening the window, if the security team agrees, but I'd like
to understand how the current window was established.

Doug

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

Re: [Openstack-operators] [tc][security] Proposal to change the CVE embargo window

2016-01-26 Thread Tristan Cacqueray

On 01/26/2016 03:18 PM, Doug Hellmann wrote:
> Excerpts from John Dickinson's message of 2016-01-25 10:58:19 -0800:
>> I'd like to lengthen the embargo window on CVE disclosures.
>>
>> Currently, the process is this 
>> (https://security.openstack.org/vmt-process.html):
>>
>>   1. A security bug is reported (and confirmed as valid)
>>   2. A patch is developed an reviewed
>>   3. After the proposed fix is approved by reviewers, A CVE is filed
>>   4. 3-5 business days later, the vulnerability is disclosed publicly and 
>> the patches are landed upstream
>>
>> The problem as I see it is that the 3 to 5 day embargo is way too short. 
>> Specifically, for those supporting OpenStack projects in a product, the 
>> short embargo does not allow sufficient time for applying, testing, and 
>> staging the fix in time for the disclosure. This leaves end-users and 
>> deployers with the situation of having a publicly announced security 
>> vulnerability without any hope of having a fix.
>>
>> I would like the embargo period to be lengthened to be 2 weeks.
>>
>> --John
> 
> I wasn't involved in the discussions that set the current embargo
> window. Do we have a record of why that length of time was selected?
> Was it based on feedback at the time? I don't have a problem with
> lengthening the window, if the security team agrees, but I'd like
> to understand how the current window was established.
> 
> Doug
> 

Thank you for starting this discussion. I wasn't there either when the
current window was set, but the short answer is that this timeframe is a
balancing act between giving significant stakeholders enough warning
that there's a serious fix coming while attempting to control the risk
of it leaking to a public venue before official disclosure. A longer
embargo period then means a greater chance of premature public disclosure.

I'm not against changing the current embargo window, but I'd like to
make sure this satisfy most (if not all) stakeholders. What if an
operator needs one month to "apply, test and stage the fix in time for
the disclosure" ?

Finally keeping the timeframe as short as possible sounds like a good
practice for stakeholders in the event of a premature disclosures when a
fix needs to be pushed out fast.

-Tristan

signature.asc
Description: OpenPGP digital signature
___
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

2016-01-26 Thread 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] Cinder-backup to swift

2016-01-26 Thread Fox, Kevin M

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

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

2016-01-26 Thread 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

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

2016-01-26 Thread 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.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 - - - - -]
>

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

2016-01-26 Thread M Ranga Swami Reddy

can you share the cinder.conf file?

On Tue, Jan 26, 2016 at 11:25 PM, raju  wrote:
> 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.openstack.wsgi
>> [req-f698019f-d0cf-4057-857e-37aef6c40bbe - - - - -] HTTP

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

2016-01-26 Thread Fox, Kevin M

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

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

2016-01-26 Thread 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 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
>>

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

2016-01-26 Thread Fox, Kevin M

great. thanks for letting us know. :)

Kevin

From: raju [raju.r...@gmail.com]
Sent: Tuesday, January 26, 2016 11:25 AM
To: Fox, Kevin M
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] Cinder-backup to swift

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

[Openstack-operators] [osops] 2016-01-27 meeting?

2016-01-26 Thread Christopher Aedo

Judging from the etherpad[1] it looks like there's a meeting
scheduling tomorrow morning, but I haven't seen any other mention of
it, so just wanted to confirm.

I was also wondering if you'd be interested in adding "Finding a place
for Operator bits in the App Catalog" to the agenda?  I can make the
first half of the meeting if it's on tomorrow, and would like to see
if there's interest from the operator community to start talking about
this.

[1]:https://etherpad.openstack.org/p/osops-irc-meeting-20160127

-Christopher

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

Re: [Openstack-operators] DVR and public IP consumption

Re: [Openstack-operators] [tc][security] Proposal to change the CVE embargo window

Re: [Openstack-operators] [tc][security] Proposal to change the CVE embargo window

[Openstack-operators] Cinder-backup to swift

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

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

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

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

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

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

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

[Openstack-operators] [osops] 2016-01-27 meeting?

12 matches

Site Navigation

Mail list logo

Footer information