Re: [openstack-dev] Nominate Vladimir Khlyunev for fuel-qa core

+1 Best regards, Svechnikov Artur On Tue, Aug 2, 2016 at 12:40 PM, Andrey Sledzinskiy < asledzins...@mirantis.com> wrote: > Hi, > I'd like to nominate Vladimir Khlyunev for fuel-qa [0] core. > > Vladimir has become a valuable member of fuel-qa project in quite short > period of time. His solid

Re: [openstack-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

+1 Best regards, Svechnikov Artur On Thu, Jul 21, 2016 at 12:10 AM, Ilya Kharin wrote: > Hello, > > I would like to nominate Sergey Abramov to fuel-octane core due to his > significant contribution to the project [1] and [2]. > > Best regards, > Ilya Kharin. > > [1]

Re: [openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm

Hi. Very good documentation. For Integer Solution you can use bytes instead of megabytes. Hence N bytes will be unallocated in the worst case. I didn't find solution for problem: - Don’t allocate a single volume on ssd and hdd Best regards, Svechnikov Artur On Tue, Jan 12, 2016 at 9:37

Re: [openstack-dev] [Fuel] Wipe of the nodes' disks

H fallback must be deprecated at all. >> > > As I noted, I've see several 6.1 deployments where it was needed, I'd > consider it still very much in use. In other cases it might be necessary to > attempt to deal with a node who's MCO agent is dead, IMO they should be > kept. > >

Re: [openstack-dev] [Fuel] Wipe of the nodes' disks

ngly randomly. So with the SSH fallback I nearly never see the failure >> in node reboot. >> > > If we talk about 6.1-7.0 release there shouldn't be any problems with mco > reboot. SSH fallback must be deprecated at all. > > >> >> > >> > >> > >&g

Re: [openstack-dev] [Fuel] Wipe of the nodes' disks

ntis.com> wrote: > On Thu, Dec 24, 2015 at 1:29 AM, Artur Svechnikov > <asvechni...@mirantis.com> wrote: > > Hi, > > We have faced the issue that nodes' disks are wiped after stop > deployment. > > It occurs due to the logic of nodes removing (this is old logi

[openstack-dev] [Fuel] Wipe of the nodes' disks

Hi, We have faced the issue that nodes' disks are wiped after stop deployment. It occurs due to the logic of nodes removing (this is old logic and it's not actual already as I understand). This logic contains step which calls erase_node[0], also there is another method with wipe of disks [1].

Re: [openstack-dev] [Fuel] Wipe of the nodes' disks

ote: > I guess that the original idea behind the wipe were security reasons so > the decommissioned node didn't contain any information of the cloud, > including configuration files and such. > > -- > Best regards, > Oleg Gelbukh > > On Thu, Dec 24, 2015 at 11:

Re: [openstack-dev] [Fuel][Ubuntu bootstrap] WebUI notification

> vkramsk...@mirantis.com> > > wrote: > >> > >> Hi, > >> > >> I really don't like setting the error message as the default one in the > DB > >> schema and consider it as a last resort solution. If possible update the > >> message to

Re: [openstack-dev] [Fuel][Ubuntu bootstrap] WebUI notification

ilgun itself). Moreover, > it's a good practice to separate areas of responsibility, and it's > building script who's responsible to show and hide error message if > necessary. > > - Igor > > > On Wed, Dec 16, 2015 at 3:31 PM, Artur Svechnikov > <asvechni.

[openstack-dev] [Fuel][Ubuntu bootstrap] WebUI notification

Hi folks, Recently was introduced special notification about absented bootstrap image. Currently this notification is sent from fuel-bootstrap-cli. It means that error message will not be sent when failure occurs before first building (like in [1]). I think it will be better to set error message