| *** psachin has joined #openstack-swift | 02:59 | |
| *** baojg has joined #openstack-swift | 03:21 | |
| *** baojg has quit IRC | 03:51 | |
| *** baojg has joined #openstack-swift | 03:56 | |
| *** itlinux has quit IRC | 03:59 | |
| *** baojg has quit IRC | 04:26 | |
| *** itlinux has joined #openstack-swift | 04:29 | |
| *** itlinux has quit IRC | 04:30 | |
| *** itlinux has joined #openstack-swift | 05:32 | |
| *** rcernin has joined #openstack-swift | 05:46 | |
| *** rcernin has quit IRC | 05:47 | |
| *** rcernin has joined #openstack-swift | 06:09 | |
| *** rcernin has quit IRC | 06:09 | |
| *** rcernin has joined #openstack-swift | 06:09 | |
| *** rcernin has quit IRC | 06:09 | |
| *** threestrands has quit IRC | 06:21 | |
| *** itlinux has quit IRC | 07:09 | |
| *** itlinux has joined #openstack-swift | 07:23 | |
| *** e0ne has joined #openstack-swift | 07:35 | |
| *** e0ne has quit IRC | 07:39 | |
| *** pcaruana has joined #openstack-swift | 08:18 | |
| *** gkadam has joined #openstack-swift | 08:35 | |
| *** gkadam has quit IRC | 08:35 | |
| *** ccamacho has quit IRC | 08:42 | |
| *** mikecmpbll has joined #openstack-swift | 08:51 | |
| *** mikecmpbll has quit IRC | 08:56 | |
| *** ccamacho has joined #openstack-swift | 09:31 | |
| *** e0ne has joined #openstack-swift | 10:02 | |
| *** e0ne has quit IRC | 11:31 | |
| *** e0ne has joined #openstack-swift | 12:47 | |
| *** e0ne has quit IRC | 13:11 | |
| *** e0ne has joined #openstack-swift | 13:14 | |
| *** e0ne has quit IRC | 13:42 | |
| *** e0ne has joined #openstack-swift | 13:45 | |
| *** mvkr has quit IRC | 13:46 | |
| *** pcaruana has quit IRC | 13:50 | |
| *** pcaruana has joined #openstack-swift | 14:05 | |
| *** psachin has quit IRC | 14:17 | |
| *** mvkr has joined #openstack-swift | 14:22 | |
| *** e0ne has quit IRC | 15:02 | |
| *** e0ne has joined #openstack-swift | 15:06 | |
| tdasilva | DHE: were you also looking to be able to sync data between two clusters? if you have a chance to play with 1space i'd be curious to hear your thoughts on it... | 15:10 |
|---|---|---|
| *** zaitcev has joined #openstack-swift | 15:15 | |
| *** ChanServ sets mode: +v zaitcev | 15:15 | |
| *** pcaruana has quit IRC | 15:29 | |
| *** itlinux has quit IRC | 15:40 | |
| notmyname | good morning | 15:41 |
| notmyname | swift 2.20.0 tag request made. https://review.openstack.org/#/c/625483/ | 15:42 |
| patchbot | patch 625483 - releases - swift 2.20.0 release - 2 patch sets | 15:42 |
| *** pcaruana has joined #openstack-swift | 15:51 | |
| DHE | tdasilva: not quite. I'm looking at moving a lot of data into swift from an existing HTTP source and was wondering if this could be leveraged as a generic feature with multiple applications | 15:56 |
| tdasilva | DHE: ack. 1space has a migration feature, but it currently uses only other object storage system as source (either using Swift or S3 api). We are also working on migrating from a filesystem. | 16:00 |
| DHE | tdasilva: I don't need inter-platform replication, and the migration will be a one-time thing. my big issue is that it hasn't happened yet and I want to have swift take over the hardware currently used by said HTTP source. gonna be an interesting pivot.. | 16:08 |
| *** gyee has joined #openstack-swift | 16:10 | |
| *** ccamacho has quit IRC | 16:19 | |
| *** ccamacho has joined #openstack-swift | 16:21 | |
| *** pcaruana has quit IRC | 16:28 | |
| *** itlinux has joined #openstack-swift | 16:40 | |
| *** e0ne has quit IRC | 17:46 | |
| *** e0ne has joined #openstack-swift | 18:42 | |
| *** mvkr has quit IRC | 18:44 | |
| *** e0ne has quit IRC | 18:46 | |
| *** e0ne has joined #openstack-swift | 19:01 | |
| *** mvkr has joined #openstack-swift | 19:20 | |
| cwright | Hi everyone, we have some firmware updates that need to be applied to our swift storage nodes. It should take less than 15 minutes. | 19:59 |
| cwright | What is the recommended way to handle this? Is it simply a matter of stopping the Swift services on that node, upgrading, and rebooting? | 19:59 |
| cwright | Apologies for the simple question, but I haven't found clear documentation on how to handle this scenario. | 19:59 |
| notmyname | cwright: yeah, it's no different than rebooting a machine for an os patch. do it in a rolling way, ie not everything at once. if you do multiple servers at once, do it in a single failure domain at a time so swift can work around it | 20:04 |
| cwright | notmyname: great, thanks so much. as soon as I wrote that question I found the documentation I was looking for. :) | 20:05 |
| notmyname | great :-) | 20:05 |
| openstackgerrit | Tim Burke proposed openstack/swift master: s3api: Stop relying on container listings during multipart uploads https://review.openstack.org/610747 | 20:21 |
| notmyname | 2.20.0 tag has landed. we've got a release! | 21:01 |
| cwright | notmyname: congrats! | 21:18 |
| cwright | I'm particularly happy to see all the attention the s3api middleware got in this release | 21:19 |
| notmyname | yeah, me too. timburke especially has done a lot of great work there | 21:19 |
| cwright | thanks timburke! | 21:20 |
| *** rcernin has joined #openstack-swift | 21:28 | |
| *** e0ne has quit IRC | 22:25 | |
| *** itlinux has quit IRC | 22:42 | |
| *** itlinux has joined #openstack-swift | 23:34 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!