S3 compatibility layer not working

Bug #1420354 reported by Bjoern
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Opinion
Medium
Steve Lewis
Juno
Won't Fix
Medium
Steve Lewis
Trunk
Won't Fix
Medium
Steve Lewis

Bug Description

Currently we have a S3 endpoint added to keystone but there is actually no port 3333 listening on the nova_api_ec2_container and the F5 generator script does not generate VIPS/Pools either.

Please checkout what's missing in our configuration

Bjoern (bjoern-t)
description: updated
Changed in openstack-ansible:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Kevin Carter (kevin-carter) wrote :

In order to resolve this issue we need to also enable the associated tempest tests for commit AIO or Multi node tests. While this feature has been in the stack for a while tests will be required to close this issue.

no longer affects: openstack-ansible/icehouse
Revision history for this message
Steve Lewis (steve-lewis) wrote :

key missing component appears to be https://github.com/stackforge/swift3
with no discoverable package releases, or meaningful tags, it's not clear yet how/what exactly we want to install this middleware.

Revision history for this message
Bjoern (bjoern-t) wrote :

That’s fine,not to fix it now, but I would have added this ticket to the wish list.
Some customers might want to use I, especially in a homogenous environment or hybrid cloud.

Changed in openstack-ansible:
status: Triaged → Opinion
Revision history for this message
Sean Carlisle (sean-carlisle) wrote :

Bjoern, ,we have at least one customer who is trying to use it.

Revision history for this message
Bjoern (bjoern-t) wrote : Re: COMMERCIAL:[Bug 1420354] Re: S3 compatibility layer not working

Yeah the devs said it¹s way too complex to implement right nowŠ.

Which customer was it ?

On 4/4/15, 6:16 PM, "Sean Carlisle" <email address hidden> wrote:

>Bjoern, ,we have at least one customer who is trying to use it.
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1420354
>
>Title:
> S3 compatibility layer not working
>
>Status in Ansible playbooks for deploying OpenStack:
> Opinion
>Status in openstack-ansible juno series:
> Won't Fix
>Status in openstack-ansible trunk series:
> Won't Fix
>
>Bug description:
> Currently we have a S3 endpoint added to keystone but there is
> actually no port 3333 listening on the nova_api_ec2_container and the
> F5 generator script does not generate VIPS/Pools either.
>
> Please checkout what's missing in our configuration
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/openstack-ansible/+bug/1420354/+subscriptions

Revision history for this message
Bjoern (bjoern-t) wrote :

Steve, I don't think it is the swift3 project alone. We are currently missing the S3 api for all mayor APIs like nova, glance etc.
Since we are getting a customer request now, we have to look at this more seriously in getting the base function working.

Sean, let's talk offline about the customer needing this.

Changed in openstack-ansible:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.