Re: [Openstack] [Swift] Composite ring building

2018-03-11 Thread Matthew Oliver
I've just rebased and pushed the above patch and now is passing against
current master.. so have started the blowing dust off phase ;)

Matt

On Mon, Mar 12, 2018 at 3:31 PM, Mark Kirkwood <
mark.kirkw...@catalyst.net.nz> wrote:

> On 10/03/18 07:21, Clay Gerrard wrote:
>
>
>>
>> On Thu, Mar 8, 2018 at 8:07 PM, Mark Kirkwood <
>> mark.kirkw...@catalyst.net.nz >
>> wrote:
>>
>> Are we supposed to do a bit of python for ourselves to use these?
>> (rubs hands ready to hack...)...
>>
>>
>> Maybe you could dust of this? https://review.openstack.org/#/c/451507/
>>
>> I now kota & acoles would feel great about seeing that merge - maybe
>> cschwede too
>>
>> Jump in #openstack-swift on Freenode if you have any questions...
>>
>>
>>
> Righty! I'm keen to brush off some dust. However we might focus 1st on
> doing some EC with per-region policies (currently using only a replicated
> one). I'll look at this patch in any downtime I manage to find :-) Thanks
> for clarifying.
>
> regards
>
> Mark
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] disable object-auditor for swift

2018-02-15 Thread Matthew Oliver
Hi Zorro,

The object auditor is protecting you from bit rot. And is the service that
will find corrupted files and quarantine them. So is rather important to
the health of your cluster. It isn't just there because of XFS.

We usually recommend XFS as when we store object metadata we store it as
extended attributes (xattrs) with the object. Ext4 only limits xattr space
to block size (at least be default) XFS isn't limited in xattr space. Just
a warning as you may have problems if a user attaches too much metadata to
an object.

Back to the auditor, there are auditor options you could make use of if you
wanted to "turn it down" a bit. Like changing the `interval` or tuning the
`files_per_second`, `bytes_per_second` or `zero_byte_files_per_second`.
If the main problem is it taking all your iops you can also use the
`nice_priority`, `ionice_class` and `ionice_priority` options to tell the
auditor to play nicer.
See the sample config file for configuration options and some description.
The commented out options and values are the defaults:
https://github.com/openstack/swift/blob/stable/pike/etc/object-server.conf-sample#L388-L430

Regards,
Matt

On Fri, Feb 16, 2018 at 12:03 AM, зоррыч  wrote:

> hi
>
> I have a swift cluster installed (without using an openstack)
>
> I ran into the problem of a high high disk utilization
>
>
> I found out that the main load is given to the server
> /usr/bin/swift-object-auditor
> From the documentation, I learned that this process checks the files on
> disks (xfs can spoil files during a cold restart)
>
> My cluster is working on ext4.
>
> I can disable the swift-object-auditor, so that I have no problems with
> files in the future?
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Not able to upload files to openstack swift

2018-02-12 Thread Matthew Oliver
Hi Aravind,

There only seems to be container-server logs in your reply. So you have any
from the object server?
Also what ports are your object-server and container-servers listening on?
Your ring is saying the object-servers are listening on 6201. Just making
sure the port numbers aren't confused and the proxy isn't tryng to send the
object PUTs to the container servers. Because it's interesting that there
is no objects subfolder.

Matt

On Mon, Feb 12, 2018 at 10:12 PM, aRaviNd  wrote:

> Hi Clay, Hi All,
>
> Configured my cluster from ground up with one proxy node and one storage
> node.
>
>
> ​
> Now I am getting two types of errors.
>
> Large files:
>
> Feb  3 18:12:33 centos7-swift-proxy1 swift-proxy-server: ERROR with Object
> server 192.168.47.128:6201/sda re: Trying to write to
> /AUTH_admin/ara1/abc: #012Traceback (most recent call last):#012  File
> "/usr/lib/python2.7/site-packages/swift/proxy/controllers/obj.py", line
> 1617, in _send_file#012self.conn.send(to_send)#012  File
> "/usr/lib64/python2.7/httplib.py", line 840, in send#012
> self.sock.sendall(data)#012  File "/usr/lib/python2.7/site-
> packages/eventlet/greenio/base.py", line 393, in sendall#012tail +=
> self.send(data[tail:], flags)#012  File "/usr/lib/python2.7/site-
> packages/eventlet/greenio/base.py", line 384, in send#012return
> self._send_loop(self.fd.send, data, flags)#012  File
> "/usr/lib/python2.7/site-packages/eventlet/greenio/base.py", line 371, in
> _send_loop#012return send_method(data, *args)#012error: [Errno 32]
> Broken pipe
> Feb  3 18:12:33 centos7-swift-proxy1 swift-proxy-server: Object 1 PUT
> exceptions during send, 0/1 required connections (txn:
> tx0b01a226078f47b4b3593-005a7641e1) (client_ip: 192.168.47.132)
>
> Large file error on storage node:
>
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR: (112666)
> accepted ('192.168.47.132', 35624)
> Feb  4 19:15:51 centos7-swift-node1 container-server: 192.168.47.132 - -
> [05/Feb/2018:00:15:51 +] "PUT /sda/89/AUTH_admin/ara1" 202 - "PUT
> http://192.168.47.132:8080/v1/AUTH_admin/ara1"; 
> "tx158875c238214209bdfc3-005a7646ab"
> "proxy-server 44255" 0.0063 "-" 112666 0
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR:
> 192.168.47.132 - - [05/Feb/2018 00:15:51] "PUT /sda/89/AUTH_admin/ara1
> HTTP/1.1" 202 252 0.006706 (txn: tx158875c238214209bdfc3-005a7646ab)
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR: (112666)
> accepted ('192.168.47.132', 35630)
> Feb  4 19:15:51 centos7-swift-node1 container-server: 192.168.47.132 - -
> [05/Feb/2018:00:15:51 +] "HEAD /sda/89/AUTH_admin/ara1" 204 - "HEAD
> http://192.168.47.132:8080/v1/AUTH_admin/ara1"; 
> "txc23a59c70e8940bf85101-005a7646ab"
> "proxy-server 44253" 0.0011 "-" 112666 0
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR:
> 192.168.47.132 - - [05/Feb/2018 00:15:51] "HEAD /sda/89/AUTH_admin/ara1
> HTTP/1.1" 204 521 0.001422 (txn: txc23a59c70e8940bf85101-005a7646ab)
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR: (112666)
> accepted ('192.168.47.132', 35632)
> Feb  4 19:15:51 centos7-swift-node1 container-server: 192.168.47.132 - -
> [05/Feb/2018:00:15:51 +] "HEAD /sda/75/AUTH_admin/ara1/abc" 404 - "HEAD
> http://192.168.47.132:8080/v1/AUTH_admin/ara1/abc";
> "txc23a59c70e8940bf85101-005a7646ab" "proxy-server 44253" 0.0003 "-"
> 112666 0
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR:
> 192.168.47.132 - - [05/Feb/2018 00:15:51] "HEAD /sda/75/AUTH_admin/ara1/abc
> HTTP/1.1" 404 351 0.000549 (txn: txc23a59c70e8940bf85101-005a7646ab)
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR: (112666)
> accepted ('192.168.47.132', 35634)
> Feb  4 19:15:51 centos7-swift-node1 container-server: 192.168.47.132 - -
> [05/Feb/2018:00:15:51 +] "PUT /sda/75/AUTH_admin/ara1/abc" 404 - "PUT
> http://192.168.47.132:8080/v1/AUTH_admin/ara1/abc";
> "tx5138df5cf1f840808d2b2-005a7646ab" "proxy-server 44253" 0.0002 "-"
> 112666 0
> Feb  4 19:15:51 centos7-swift-node1 container-server: STDERR:
> 192.168.47.132 - - [05/Feb/2018 00:15:51] "PUT /sda/75/AUTH_admin/ara1/abc
> HTTP/1.1" 404 212 0.000506 (txn: tx5138df5cf1f840808d2b2-005a7646ab)
> Feb  4 19:15:52 centos7-swift-node1 container-server: STDERR: (112666)
> accepted ('192.168.47.132', 35636)
> Feb  4 19:15:52 centos7-swift-node1 container-server: 192.168.47.132 - -
> [05/Feb/2018:00:15:52 +] "PUT /sda/75/AUTH_admin/ara1/abc" 404 - "PUT
> http://192.168.47.132:8080/v1/AUTH_admin/ara1/abc";
> "txeb1c76b896854e4885009-005a7646ac" "proxy-server 44253" 0.0002 "-"
> 112666 0
> Feb  4 19:15:52 centos7-swift-node1 container-server: STDERR:
> 192.168.47.132 - - [05/Feb/2018 00:15:52] "PUT /sda/75/AUTH_admin/ara1/abc
> HTTP/1.1" 404 212 0.000589 (txn: txeb1c76b896854e4885009-005a7646ac)
> Feb  4 19:15:54 centos7-swift-node1 container-server: STDERR: (112666)
> accepted ('192.168.47.132', 35638)
> Feb  4 19:15:54 centos7-swift-node1 container-server: 192.168.4

Re: [Openstack] how to use swift in another container

2017-10-24 Thread Matthew Oliver
Interesting. I'm not a docker expert, but it's an interesting idea. But is
only a 1 replica, 1 device system. maybe if it was extended you so you add
more devices or more containers to grow the cluster, that could be cool.
The ring management would be the interesting part. And if you want to grow
it you may want to give it some real disks so how do they plumb.
But like the author said, it's a good POC, and could be expanded.

Now how can you access it from another container. The -p command says to
publish the docker container's port 8080 to your hosts 12345 port on all
interfaces. So pointing at the host machine on port 12345 will actually
connect to port 8080 on the docker container. This means if you want the
other container to talk to the swift one, just hit up either the host's IP
on 12345 or the swift container's IP on port 8080. Noting I don't know if
you need to look at iptables or routing on the host to do the latter.

Matt

On Wed, Oct 25, 2017 at 8:30 AM, Jaln  wrote:

> Hello,
>
> I have installed swift in a docker container, and opened another
> container, where I want to use swift.
>
> Here is how I configured swift container:
> I followed https://hub.docker.com/r/morrisjobke/docker-swift-onlyone/
>
> and launched this swift container with:
>
> docker run -d -p 12345:8080 --volumes-from SWIFT_DATA -t 
> morrisjobke/docker-swift-onlyone
>
>
> Then, I can connect to swift from host, but not from another container,
> e.g.,
>
>
> swift -A http://127.0.0.1:12345/auth/v1.0 -U test:tester -K testing stat
>
>
>
> While in another container:
> docker run -it ubuntu bash
>
> How can I use swift?
>
> Best,
> Jialin
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] [OpenStack] [Swift] How to set maximum size of the log file?

2017-02-07 Thread Matthew Oliver
The logs should be manged via syslog, so you can just use log rotate to
rotate on time or size, keep x number of copies and compress rotated
versions.

On Wed, Feb 8, 2017 at 6:49 AM, Alexandr Porunov  wrote:

> Hello,
>
> I found out that my log file is almost 3GB. How to set a size limit?
>
> Best regards,
> Alexandr
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Fwd: [Swift] : Dataset or Workload

2017-02-07 Thread Matthew Oliver
I'm not sure what you mean, exactly.. you can adapt your Swift cluster to
manage different workloads. So what you mean by "standard" isn't obvious.

If you just want to do some bench marking then ssbench, cosbench, getput
and/or swift-bench are maybe what you're looking for.

Regards,
Matt

On Sun, Feb 5, 2017 at 4:26 AM, Sameer Kulkarni 
wrote:

> Hi All,
>
> I was searching for some standard workload for Openstack Swift. Are there
> any readily available workload for the same?
>
> Sameer Kulkarni
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] [Swift] How to get a list of devices from the ring in Java / Bash?

2017-01-30 Thread Matthew Oliver
Hey Alexandr,

If you wanted to do it using python, and you didn't have swift installed
you can use pickle and unpickle the builder. something like:

  import pickle
  builder = pickle.load(open('')

Then you'd have a python dict structure, where I think you can
'builder['devs']'

or with swift installed you can use the RingBuilder class:

  from swift.common.ring.builder import RingBuilder
  builder = RingBuilder.load('')
  builder.devs

Where builder.devs will be a list of dictionary objects. You could then
json-ify and output for java to read or put it into an easier to pass list.

There could be a much simpler way, but I'm a Python dev, so this is what
I'd do ;)

Regards,
Matt

On Sat, Jan 28, 2017 at 6:21 AM, Alexandr Porunov <
alexandr.poru...@gmail.com> wrote:

> Hello,
>
> I need to get a list / array of devices in Java or Bash. Is it possible to
> get? Are there any API or something like that?
>
> I know we can obtain a list with the next command:
> swift-ring-builder object.builder
>
> But it return a string with the list of devices which are quite hard to
> parse. In the documentation there is an example how to get a list of
> devices with python:
> devices = list(self._iter_devs())
>
> But it doesn't show which library to use to get a list of devices and how
> to use that library.
>
> Sincerely,
> Alexandr
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] [Swift] Bug: swift-ring-builder set_weight doesn't work

2017-01-30 Thread Matthew Oliver
You welcome, and thank you for bringing it to our attention. Thanks to you,
the next release will have the set_weight usage corrected:

  https://bugs.launchpad.net/swift/+bug/1660214

Regards,
Matt

On Mon, Jan 30, 2017 at 7:25 PM, Alexandr Porunov <
alexandr.poru...@gmail.com> wrote:

> Hello Matt,
>
> Thank you very much for your help! It's awesome. Now everything works!
>
> Best regards,
> Alexandr
>
> On Mon, Jan 30, 2017 at 12:48 AM, Matthew Oliver 
> wrote:
>
>> Hey Alexandr,
>>
>> Thanks for the email. I can help you in this instance, and I'll push up a
>> patch to correct the usage documentation for the long version of the
>> set_weight command.
>>
>>
>> On Sun, Jan 29, 2017 at 8:33 AM, Alexandr Porunov <
>> alexandr.poru...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I can't change a weight of the device.
>>> Here is a list of my devices:
>>>
>>> Devices:id  region  zone  ip address  port  replication ip
>>>  replication port  name weight partitions balance meta
>>>  0   1 1   host1  6000   host1
>>>6000d1 1000.00   10240.00 bla bla1 bla2
>>>  1   1 1   host1  6000   host1
>>>6000d2 1000.00   10240.00 bla bla1 bla2
>>>  2   1 1   host1  6000   host1
>>>6000d3 1000.00   10240.00 bla bla1 bla2
>>>
>>> Here is what I tried to change a weight:
>>> swift-ring-builder object.builder set_weight --region 1 --zone 1 --ip
>>> host1 --port 6000 --replication-ip host1 --replication-port 6000 --device
>>> d1 --meta "bla bla1 bla2" --weight 1000
>>>
>>
>> There is a problem with the command as you've sent it. But I agree it
>> isn't obvious from the usage error. Using the long form (--region,
>> --device, etc) is just defining search criteria for what you want to
>> change. Not specifying what you want to change.
>>
>> So in your case above your looking for a device that already has a weight
>> of 1000, and your not specifying what the change it to. To fix your
>> command, you'd need to:
>>
>>   swift-ring-builder object.builder set_weight --region 1 --zone 1 --ip
>> host1 --port 6000 --replication-ip host1 --replication-port 6000 --device
>> d1 --meta "bla bla1 bla2" --weight 1024 1000
>>
>> NOTE: I am sending in the 1000 as the last option. Obviously as these are
>> search terms you don't actually have to send them all in, only the ones
>> that identify the devices or device you want to change.
>>
>>
>>> swift-ring-builder object.builder set_weight r1z1-host1:6000Rhost1:6000
>>> d1_"bla bla1 bla2" 2000
>>>
>>
>> The short version above is failing, as you forgot to add the '/'
>> seperator between the port and the device, given your example it should
>> have been:
>>
>> swift-ring-builder object.builder set_weight
>> r1z1-host1:6000Rhost1:6000/d1_"bla bla1 bla2" 2000
>>
>> NOTE: the '/' before the d1.
>>
>> What your putting in there is just a search for devices to change. You
>> don't have to put the full string in. I guess if you have a tool that will
>> use the full definition then fine. I find when wanting to update just 1
>> host it's easier to do so via the device id:
>>
>>   swift-ring-builder set_weight d1 2000
>>
>> In both cases it doesn't work and shows the next information:
>>>
>>> swift-ring-builder  set_weight  
>>>
>>> [ >>
>>> [--yes]
>>>
>>>
>>>
>>> or
>>>
>>>
>>>
>>> swift-ring-builder  set_weight
>>>
>>> --region  --zone  --ip  --port 
>>>
>>> --replication-ip  --replication-port 
>>>
>>> --device  --meta  --weight 
>>>
>>> [--yes]
>>>
>>>
>>
>> This usage isn't been very useful here, as it's missing the actual adding
>> the weight. I'll raise a bug and patch to address this.
>>
>>
>>>
>>>
>>> Where ,  and  are replication ip, hostname
>>>
>>> and port.
>>>
>>> Any of the options are optional in both cases.
>>>
>>>
>>>
>>> Resets the devices' weights. No partitions will be reassigned to or
>>> from
>>> the device until after running 'rebalance'. This is so you can make
>>>
>>> multiple device changes and rebalance them all just once.
>>>
>>>
>>>
>>> Option --yes assume a yes response to all questions.
>>>
>>>
>>> Please, correct me if it is my fault.
>>>
>>> Best regards,
>>> Alexandr
>>>
>>> ___
>>> Mailing list: http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe : http://lists.openstack.org/cgi
>>> -bin/mailman/listinfo/openstack
>>>
>>>
>> regards,
>> Matt
>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] [Swift] Bug: swift-ring-builder set_weight doesn't work

2017-01-29 Thread Matthew Oliver
Hey Alexandr,

Thanks for the email. I can help you in this instance, and I'll push up a
patch to correct the usage documentation for the long version of the
set_weight command.


On Sun, Jan 29, 2017 at 8:33 AM, Alexandr Porunov <
alexandr.poru...@gmail.com> wrote:

> Hello,
>
> I can't change a weight of the device.
> Here is a list of my devices:
>
> Devices:id  region  zone  ip address  port  replication ip
>  replication port  name weight partitions balance meta
>  0   1 1   host1  6000   host1
>  6000d1 1000.00   10240.00 bla bla1 bla2
>  1   1 1   host1  6000   host1
>  6000d2 1000.00   10240.00 bla bla1 bla2
>  2   1 1   host1  6000   host1
>  6000d3 1000.00   10240.00 bla bla1 bla2
>
> Here is what I tried to change a weight:
> swift-ring-builder object.builder set_weight --region 1 --zone 1 --ip
> host1 --port 6000 --replication-ip host1 --replication-port 6000 --device
> d1 --meta "bla bla1 bla2" --weight 1000
>

There is a problem with the command as you've sent it. But I agree it isn't
obvious from the usage error. Using the long form (--region, --device, etc)
is just defining search criteria for what you want to change. Not
specifying what you want to change.

So in your case above your looking for a device that already has a weight
of 1000, and your not specifying what the change it to. To fix your
command, you'd need to:

  swift-ring-builder object.builder set_weight --region 1 --zone 1 --ip
host1 --port 6000 --replication-ip host1 --replication-port 6000 --device
d1 --meta "bla bla1 bla2" --weight 1024 1000

NOTE: I am sending in the 1000 as the last option. Obviously as these are
search terms you don't actually have to send them all in, only the ones
that identify the devices or device you want to change.


> swift-ring-builder object.builder set_weight r1z1-host1:6000Rhost1:6000
> d1_"bla bla1 bla2" 2000
>

The short version above is failing, as you forgot to add the '/' seperator
between the port and the device, given your example it should have been:

swift-ring-builder object.builder set_weight
r1z1-host1:6000Rhost1:6000/d1_"bla bla1 bla2" 2000

NOTE: the '/' before the d1.

What your putting in there is just a search for devices to change. You
don't have to put the full string in. I guess if you have a tool that will
use the full definition then fine. I find when wanting to update just 1
host it's easier to do so via the device id:

  swift-ring-builder set_weight d1 2000

In both cases it doesn't work and shows the next information:
>
> swift-ring-builder  set_weight  
>
> [ 
> [--yes]
>
>
>
> or
>
>
>
> swift-ring-builder  set_weight
>
> --region  --zone  --ip  --port 
>
> --replication-ip  --replication-port 
>
> --device  --meta  --weight 
>
> [--yes]
>
>

This usage isn't been very useful here, as it's missing the actual adding
the weight. I'll raise a bug and patch to address this.


>
>
> Where ,  and  are replication ip, hostname
>
> and port.
>
> Any of the options are optional in both cases.
>
>
>
> Resets the devices' weights. No partitions will be reassigned to or
> from
> the device until after running 'rebalance'. This is so you can make
>
> multiple device changes and rebalance them all just once.
>
>
>
> Option --yes assume a yes response to all questions.
>
>
> Please, correct me if it is my fault.
>
> Best regards,
> Alexandr
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
regards,
Matt
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] OpenStack sponsorship for OPW - Dec-Mar 2015 internship

2014-08-11 Thread Matthew Oliver
I think this is awesome, thanks Mahati for you interest :)

I'm still relatively new to the Swift project, but am happy to help out in
any way I can. I might not be the right candidate for mentor (notmyname or
a core would be better for that), but am always online (as we found out on
the weekend we share a similar timezone, Oz vs India) so will be around at
least most of your days :)

Matt


On Tue, Aug 12, 2014 at 9:56 AM, John Dickinson  wrote:

> Mahati,
>
> I chatted with Anita (anteaya) in IRC this afternoon about the OPW. I'd be
> happy to continue working with you and either be a mentor for Swift in
> OpenStack or help find one.
>
> --John
>
>
>
>
>
>
> On Aug 8, 2014, at 8:13 PM, John Dickinson  wrote:
>
> > I honestly have no idea how this works (the actual logistics), but
> speaking from the Swift perspective within OpenStack, I'd love to help out
> in any way I can.
> >
> >
> > --John
> >
> >
> >
> >
> >
> > On Aug 8, 2014, at 7:41 PM, Mahati C  wrote:
> >
> >> Hi,
> >>
> >> I'm interested in participating in OPW (Outreach Program for Women)
> 2014 for Dec 2014 -Mar 2015 internship. Would OpenStack be a  participating
> organization this time around too? (I see that it was for May-Aug:
> https://wiki.gnome.org/OutreachProgramForWomen/2014/MayAugust#Participating_Organizations
> ).
> >>
> >> I'm currently trying to understand Swift program of OpenStack and
> interested in exploring that. I wanted to know how relevant is Swift for
> this round of OPW. Is Swift looking to be a part of it?
> >>
> >> How relevant would it be for OPW if i continue to explore and learn
> Swift?
> >>
> >> Thank you in advance.
> >>
> >> -Mahati
> >> ___
> >> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >> Post to : openstack@lists.openstack.org
> >> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
> > ___
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack