Has anyone been able to successfully integrate the S3 api with Swift?
I'm working on this in my lab, and finding a number of issues:
1) I've found that when I enable the S3 API, my swift proxy doesn't
bind to it's port. I'm guessing that it's failing to start for some
reason, but the logs don't s
I moved from mikata to Liberty and now i can see stability its using
4G on controller now. Happy!..
What big stuff i am going to miss if i run my production on liberty?
On Fri, Aug 19, 2016 at 2:43 AM, Jose Manuel Ferrer Mosteiro
wrote:
> Same memory problems with Ubuntu 16.04 and Mitaka package
>
> Yes, and that was what I was alluding to in order to make packets go out the
> correct interface based on the source IP in the packets.
>
You can configure it to send the packets out the interface the original packet
came in on. That solves this problem. You don’t have to use source IP.
J
Hi Folks,
I've been playing with IDv3 and domains in the Mitaka branch bits. I'm
able to correctly get the cloud_admin user working in a cloud_admin_domain
with ID updated to policyv3.json, however am running into usability
issues. They're not working as I'd expect.
For instance, I create a def
On Fri, Aug 19, 2016 at 9:25 PM John Belamaric
wrote:
> >
> > Yes, and that was what I was alluding to in order to make packets go out
> the correct interface based on the source IP in the packets.
> >
>
> You can configure it to send the packets out the interface the original
> packet came in on
Hi John,
Probably the first thing to do is get a reasonable error display. The
service init scripts sometime throw away the output so try starting the
proxy with the command:
$ sudo /usr/bin/swift-init proxy-server start
(or whatever variant your platform uses - see your system's service ini
