Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hi, I'd like to ask what's the current state of Shotgun and what are the plans for the future? Is there any alternative chosen for Fuel diagnostic snapshot functionality and being worked on? On Mon, Apr 18, 2016 at 3:39 PM, Igor Kalnitsky wrote: > Evgeniy L. wrote: > >

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

>> Btw, one of the ideas was to use Fuel task capabilities to gather diagnostic snapshot. I think such kind of tools should use as less as possible existing infrastructure, because in case if something went wrong, you should be able to easily get diagnostic information, even with broken RabbitMQ,

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Colleagues, Whether we are going to continue using Shotgun or substitute it with something else, we still need to decouple it from Fuel because Shotgun is a generic tool. Please review these [1], [2]. [1] https://review.openstack.org/#/c/298603 [2] https://review.openstack.org/#/c/298615 Btw,

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hi, Problems which I see with current Shotgun are: 1. Luck of parallelism, so it's not going to fetch data fast enough from medium/big clouds. 2. There should be an easy way to run it manually (it's possible, but there is no ready-to-use config), it would be really helpful in case if

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hi, Do we have any requirements for the new tool? Do we know what we don’t like about current implementation, what should be avoided, etc.? Before that we can only speculate. From my ops experience, shotgun like tools will not work conveniently on medium to big environments. Even on medium env

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Osquery [1] could also be considered as providing a lot of useful informations in a convenient way. [1] https://osquery.io/ On Wed, Mar 30, 2016 at 3:20 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > ​Igor, > > I can not agree more. Wherever possible we should > use existent

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

​Igor, I can not agree more. Wherever possible we should use existent mature solutions. Ansible is really convenient and well known solution, let's try to use it. Yet another thing should be taken into account. One of Shotgun features is diagnostic report that could then be attached to bugs to

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

On 30/03/16 13:35, Igor Kalnitsky wrote: > Neil Jerram wrote: >> But isn't Ansible also over-complicated for just running commands over SSH? > > It may be not so "simple" to ignore that. Ansible has a lot of modules > which might be very helpful. For instance, Shotgun makes a database > dump and

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Neil Jerram wrote: > But isn't Ansible also over-complicated for just running commands over SSH? It may be not so "simple" to ignore that. Ansible has a lot of modules which might be very helpful. For instance, Shotgun makes a database dump and there're Ansible modules with the same functionality

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

+1 to discarding shotgun. Should we register a BP for that? > 30 бер. 2016 р. о 12:03 Igor Kalnitsky написав(ла): > > Hey Fuelers, > > I know that you probably wouldn't like to hear that, but in my opinion > Fuel has to stop using Shotgun. It's nothing more but a

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

FWIW, as a naive bystander: On 30/03/16 11:06, Igor Kalnitsky wrote: > Hey Fuelers, > > I know that you probably wouldn't like to hear that, but in my opinion > Fuel has to stop using Shotgun. It's nothing more but a command runner > over SSH. Besides, it has well known issues such as retrieving

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hey Fuelers, I know that you probably wouldn't like to hear that, but in my opinion Fuel has to stop using Shotgun. It's nothing more but a command runner over SSH. Besides, it has well known issues such as retrieving remote directories with broken symlinks inside. So I propose to find a modern

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Please, propose your options here then: https://etherpad.openstack.org/p/shotgun-rename > 29 бер. 2016 р. о 18:15 Jay Pipes написав(ла): > > On 03/29/2016 08:41 AM, Roman Prykhodchenko wrote: >> Should we propose options and then arrange a poll? > > Yup, ++ :) > >>> 29

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

On 03/29/2016 08:41 AM, Roman Prykhodchenko wrote: Should we propose options and then arrange a poll? Yup, ++ :) 29 бер. 2016 р. о 16:40 Neil Jerram написав(ла): On 29/03/16 15:17, Jay Pipes wrote: Hi! Once Shotgun is pulled out of Fuel, may I suggest renaming

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Should we propose options and then arrange a poll? > 29 бер. 2016 р. о 16:40 Neil Jerram написав(ла): > > On 29/03/16 15:17, Jay Pipes wrote: >> Hi! >> >> Once Shotgun is pulled out of Fuel, may I suggest renaming it to >> something different? I know in the past

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

On 29/03/16 15:17, Jay Pipes wrote: > Hi! > > Once Shotgun is pulled out of Fuel, may I suggest renaming it to > something different? I know in the past that Anita and a few others > thought the name was not something we should really be encouraging in > the OpenStack ecosystem. > > Just something

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hi! Once Shotgun is pulled out of Fuel, may I suggest renaming it to something different? I know in the past that Anita and a few others thought the name was not something we should really be encouraging in the OpenStack ecosystem. Just something to consider since it's being decoupled