+1
On Tue, Jun 28, 2016 at 1:16 AM, Matthew Mosesohn
wrote:
> +1. Maksim is an excellent reviewer.
>
> On Mon, Jun 27, 2016 at 6:06 PM, Alex Schultz
> wrote:
> > +1
> >
> > On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrelya >
> > wrote:
> >>
> >> On 06/27/2016 04:54 PM, Sergii Golovatiuk wrote:
Hi team,
An issue with rsync was recently reported [0].
We have a symlink 'liberty-9.0/modules/osnailyfacter/modular/master' to
examples directory in a fuel master node. However, rsync does not copy the
symlink to slave nodes. Being easy to fix (by adding -l flag) this issue
raises a question: do
re
> too late in the release cycle to change keys to '{uid}'.
>
> Regards,
> Alex
>
> [0] https://review.openstack.org/#/c/284046/
>
> On Tue, Mar 15, 2016 at 11:22 AM, Kyrylo Galanov
> wrote:
>
>> Hi,
>>
>> Currently nailgun and puppet pro
Hi,
Currently nailgun and puppet process network_metadata hash slightly
different.
Nailgun uses short hostname as a hash key for each node, while library code
assumes that key is always 'node-{uid}'. Sometimes it can result in a
deployment failure.
During code review[0] it turned out that there a
+1
On Thu, Mar 3, 2016 at 2:53 AM, Roman Vyalov wrote:
> +1
>
> On Wed, Mar 2, 2016 at 5:47 PM, Sergey Kulanov
> wrote:
>
>> Hey Fuelers,
>>
>> Since we've successfully moved [1] virtual-box scripts from fuel-main [2]
>> to
>> separate fuel-virtualbox [3] git repo, I propose to update
>> fuel-v
Finally! +2 !
On Fri, Feb 26, 2016 at 9:08 PM, Roman Vyalov wrote:
> +1
>
> On Fri, Feb 26, 2016 at 12:31 PM, Aleksey Kasatkin > wrote:
>
>> +1
>>
>>
>> Aleksey Kasatkin
>>
>>
>> On Thu, Feb 25, 2016 at 11:59 PM, Sergey Vasilenko <
>> svasile...@mirantis.com> wrote:
>>
>>> +1
>>>
>>>
>>> /sv
>>
Adding this to future features.
On Mon, Feb 22, 2016 at 8:33 PM, Bogdan Dobrelya
wrote:
> On 22.02.2016 10:28, Kyrylo Galanov wrote:
> > Would namespaces be compatible with existing plugins?
>
> It should be, if the default namespace will be "core"
>
> >
&
lear as possible, and decide what to install
> in my
> > > own way.
> >
> > IMO: The plugin developer wants to install additional
> > applications to extend functionality, It do not want configure
> > low-level things, like specify some
x27;re talking
> about. We don't support it now, and, anyway, there should be no
> difference between roles defined by plugins and core roles.
>
> - Igor
>
> On Thu, Feb 18, 2016 at 12:53 PM, Kyrylo Galanov
> wrote:
> > Hello,
> >
> > We are about to sw
Hello,
We are about to switch to wildcards instead of listing all groups in tasks
explicitly [0].
This change must make deployment process more obvious for developers.
However, it might lead to confusion when new groups are added either by
plugin or fuel team in future.
As mention by Bogdan, it i
Hello Bogdan,
I hope I am not the one of the context. Why do we separate fixtures for Noop
tests from the repo?
I can understand if while noop test block was carried out to a separate repo
.
On Tue, Jan 26, 2016 at 1:54 PM, Bogdan Dobrelya
wrote:
> We are going to switch [0] to external astute
Hello,
Why don't we introduce additional state for nodes like 're-deploying'. If
deployment was stopped we don't erase nodes with this state, but change the
status to 'error' or 'ready' , for example.
Or we can add warning message that 'stop' button would destroy every and
each node.
On Fri, Jan
Hi,
I am not QA engineer at all, but it is always a pleasure to work with
Artem. I would vote +1.
--
Kyrylo
On Wed, Dec 23, 2015 at 7:20 PM, Igor Marnat wrote:
> Folks,
> I'm not a fuel-qa core, but if I was, I'd vote with +1:)
>
> I'm really impressed with quality of analysis which Artem prov
Hello,
I would like to start discussion regarding the issue we have discovered
recently [1].
In a nutshell, if RabbitMQ is configured to run in separate mgmt/messaging
network it fails on building cluster.
While RabbitMQ is managed by Pacemaker and OCF script, the cluster is built
using FQDN. App
Looks great. What is the estimated date / release for this feature to be
delivered?
On Thu, Dec 3, 2015 at 4:40 PM, Timur Sufiev wrote:
> Please take a look at
> https://blueprints.launchpad.net/horizon/+spec/horizon-glance-large-image-upload
>
> On Thu, Dec 3, 2015 at 5:21 PM Ky
Hello,
When a file is uploaded to Glance, Swift through Horizon it is stored
locally in a temporary directory in Horizon server. This is inefficient
approach especially for big files.
I would suggest to implement 'proxy' upload to Glance, Swift using chunk
buffer instead of storing a file locally
Hi Team,
I have been testing fail-over after free disk space is less than 512 mb. (
https://review.openstack.org/#/c/240951/)
Affected node is stopped correctly and services migrate to a healthy node.
However, after free disk space is more than 512 mb again the node does not
recover it's state to
17 matches
Mail list logo
