[openstack-dev] [swift] Failed to restore swift from file backup

Hi all, I try to make a backup of swift cluster by stopping server and backup all files. Then I create one more cluster with absolutely the same settings and restore all files from backup on it. As result swift is working and 'swift glance list' gives the same correct list as before, but 'swift

Re: [openstack-dev] [Fuel][FFE] Use RGW as a default object store instead of Swift

and we usually do not accept any features to stable branch. > > Or your meant that patch for master branch? > > Thanks, > Igor > > [1]: https://review.openstack.org/#/c/286100/ > > On Tue, Mar 1, 2016 at 4:44 PM, Konstantin Danilov > <kdani...@mirantis.com> wrote:

[openstack-dev] [Fuel][FFE] Use RGW as a default object store instead of Swift

Colleagues, I would like to request a feature freeze exception for 'Use RGW as a default object store instead of Swift' [1]. To merge the changes we need at most one week of time. ​[1]: https://review.openstack.org/#/c/286100/ Thanks

Re: [openstack-dev] [fuel] OS_SERVICE_TOKEN usage in Fuel

Would send ceph estimation tomorrow. Yet estimation != ETTA On Wed, Jul 29, 2015 at 12:27 AM, Sergii Golovatiuk sgolovat...@mirantis.com wrote: Hi, Let's ask our Ceph developers how much time/resources they need to implement such functionality. -- Best regards, Sergii Golovatiuk, Skype

Re: [openstack-dev] [fuel] Fuel plugin as docker containers images

putting it into a container all together as you will end up with 150-300mb container mostly just because of python. On Tue, Jul 28, 2015 at 7:26 AM Konstantin Danilov kdani...@mirantis.com wrote: Evgene, I'm sure you understand this, but just to be clear - now FUEL uses containers on master node

Re: [openstack-dev] [fuel] Fuel plugin as docker containers images

specific containers, so they don't intersect and don't break Fuel master dependencies. Do you have some specific use case for that? Thanks, On Mon, Jul 27, 2015 at 4:58 PM, Konstantin Danilov kdani...@mirantis.com wrote: Hi, Is there a plans to allow plugin to be delivered as docker container

[openstack-dev] [fuel] Fuel plugin as docker containers images

Hi, Is there a plans to allow plugin to be delivered as docker container images? Thanks -- Kostiantyn Danilov aka koder.ua Principal software engineer, Mirantis skype:koder.ua http://koder-ua.blogspot.com/ http://mirantis.com

[openstack-dev] [fuel] FF Exception for LP-1464656 fix (update ceph PG calculation algorithm)

Team, I would like to request an exception from the Feature Freeze for [1] fix. It requires changes in fuel-web [2], fuel-library [3] and in UI. [2] and [3] are already tested, I'm fixing UT now. BP - [4] Code has backward-compatibility mode. I need one more week to finish it. Also I'm asking

Re: [openstack-dev] [fuel][client] new client implementation ideas

Hi all, I have created etherpad page https://etherpad.openstack.org/p/fuelclient-implementation-ideas On Wed, Jan 14, 2015 at 12:38 PM, Konstantin Danilov kdani...@mirantis.com wrote: Igor, Yep, I knew that you start to rewrite fuel-client, but it seemd for me that this ideas

[openstack-dev] [fuel][client] new client implementation ideas

Hi all, We are working on fuel certification script https://github.com/stgleb/fuel-web and have yet-one-more implementation of fuel-client, which cover very small of Fuel API, yet we have some ideas, which you might be interesting in. 1) high-level primitives for REST operations. a)

Re: [openstack-dev] [fuel][client] new client implementation ideas

On Wed, Jan 14, 2015 at 12:38 PM, Konstantin Danilov kdani...@mirantis.com wrote: Hi all, We are working on fuel certification script https://github.com/stgleb/fuel-web and have yet-one-more implementation of fuel-client, which cover very small of Fuel API, yet we have some ideas

Re: [openstack-dev] Future-based api for openstack clients calls, that starts background tasks

On Mon, Jan 12, 2015 at 3:33 PM, Angus Salkeld asalk...@mirantis.com wrote: On Mon, Jan 12, 2015 at 10:17 PM, Konstantin Danilov kdani...@mirantis.com wrote: Boris, Move from sync http to something like websocket requires a lot of work and not directly connected with API issue. When

[openstack-dev] Future-based api for openstack clients calls, that starts background tasks

Hi all. There a set of openstack api functions which starts background actions and return preliminary results - like 'novaclient.create'. Those functions requires periodically check results and handle timeouts/errors (and often cleanup + restart help to fix an error). Check/retry/cleanup code

Re: [openstack-dev] Future-based api for openstack clients calls, that starts background tasks

, Konstantin Danilov kdani...@mirantis.com wrote: Hi all. There a set of openstack api functions which starts background actions and return preliminary results - like 'novaclient.create'. Those functions requires periodically check results and handle timeouts/errors (and often cleanup + restart