+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 08 Sep 2016, at 12:05, Georgy Kibardin wrote:
>
> +1
>
> On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky <mailto:i...@kalnitsky.org>> wrote:
> Hey Fuelers,
>
> I'd like to nominate Ilya for joining
+1, I think it is good idea.
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 05 Sep 2016, at 20:17, Maksim Malchuk wrote:
>
> I want to clarify my previous reply
> +1
> but the new fuel-core would be a small group of the cores who are fully
> involved in the whole Fuel proje
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 15 Jul 2016, at 16:08, Anastasia Urlapova wrote:
>
> +1
>
> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy
> mailto:asledzins...@mirantis.com>> wrote:
> Hi,
> I'd like to nominate Alexey Stepanov for f
Totally agree with this decision.
Vladimir, thank you for driving this activity.
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 23 Jun 2016, at 13:31, Vladimir Kozhukalov
> wrote:
>
> Dear colleagues.
>
> I'd like to announce that fuel-mirror tool is not going to b
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 22 Jun 2016, at 13:18, Sergey Kulanov wrote:
>
> Hi All,
>
> I'd like to nominate Dmitry Burmistrov for core reviewers of fuel-mirror.
> Dmitry is one of the top
> contributors to the project [1, 2]. One of his la
Well, the agreement is reached. I added Ilya to fuel-web-core group.
Ilya, congratulations! Will be happy to see even more thorough reviews from you!
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 08 Jun 2016, at 20:52, Bulat Gaifullin wrote:
>
> Hey Fuelers,
>
> I'd l
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 09 Jun 2016, at 12:25, Aleksey Kasatkin wrote:
>
> Hey Fuelers,
>
> I'd like to nominate Artur Svechnikov to the fuel-web-core team.
>
> Artur is doing thorough reviews [1], he produces high-quality code.
> Artur
lease reply back with +1/-1.
[1] http://stackalytics.com/report/contribution/fuel-web/90
<http://stackalytics.com/report/contribution/fuel-web/90>
Regards,
Bulat Gaifullin
Mirantis Inc.
__
OpenStack Development Mailing Li
this is not correct way, because the first deployment may fail,
the cluster will be in ‘error state’, but it does not have last successfully
deployed configuration.
Regards,at
Bulat Gaifullin
Mirantis Inc.
> On 25 May 2016, at 15:05, Roman Prykhodchenko wrote:
>
> Folks,
>
&
What about GPT[1] disks?
As I know we have plans to support UEFI boot and GPT disks.
[1] https://en.wikipedia.org/wiki/GUID_Partition_Table
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 22 Mar 2016, at 13:46, Dmitry Guryanov wrote:
>
> On Tue, 2016-03-22 at 13:07 +0300, Dmitry
es
instance.volumes_metadata.changed()
[1] https://review.openstack.org/#/c/289600/
PS:
Added missing link
Regards,
Bulat Gaifullin
Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsu
.
Example:
# instance.roles_metadata is instance of MutableDict.
instance.roles_metadata[role['name']] = role['meta']
instance.volumes_metadata['volumes_roles_mapping'][role['name']] =
role.get('volumes_roles_mapping', [])
# notify about changes
in
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 03 Mar 2016, at 17:03, Dmitry Klenov wrote:
>
> Maksim, good job! +1 from my side though I am not a core.
>
> On Thu, Mar 3, 2016 at 4:10 PM, Aleksey Zvyagintsev
> mailto:azvyagint...@mirantis.com>> wrote:
> +1
>
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 24 Feb 2016, at 16:02, Aleksandr Didenko wrote:
>
> +1
>
> On Wed, Feb 24, 2016 at 1:50 PM, Vladimir Kuklin <mailto:vkuk...@mirantis.com>> wrote:
> Fellow Fuelers
>
> I would like to kindly ask you to consid
le, 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
banch of task for configure network, configure repositories etc.
How can we manage new node if netwo
+1 to use wildcards for common tasks like netconfig and setup repositories.
This tasks should run on all nodes and it does not matter, the node has role
from plugin or core-role.
In my opinion we should one approach for basic configuration of node.
Regards,
Bulat Gaifullin
Mirantis Inc.
>
. Can we drop this feature? or
should we finish implementation of this feature.
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 11 Feb 2016, at 02:41, Andrew Woodward wrote:
>
>
>
> On Wed, Feb 10, 2016 at 2:23 PM Dmitry Borodaenko <mailto:dborodae...@mirantis.com>
/Packetary
Regards,
Bulat Gaifullin
Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
+1.
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 08 Feb 2016, at 19:05, Igor Kalnitsky wrote:
>
> Hey Fuelers,
>
> When we are going to enable it? I think since HCF is passed for
> stable/8.0, it's time to enable task-based deployment for master
> branch.
>
&
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 08 Feb 2016, at 12:57, Evgeniy L wrote:
>
> +1
>
> On Mon, Feb 8, 2016 at 12:54 PM, Igor Kalnitsky <mailto:ikalnit...@mirantis.com>> wrote:
> Hey Fuelers,
>
> I'd like to nominate Fedor Zhadaev for th
gt; Any plan to have a nicer experience in future Fuel releases?
Yes, we are working on this.
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 05 Feb 2016, at 15:54, Igor Kalnitsky wrote:
>
> Simon,
>
>> Nope, it doesn't work for me since it should run for *all* the no
managing packages/repositories in
one place.
* We want to have a common interface only, which will be based on the existing
utilities for building packages. for example: sbuild[1] or Mock[2]
[1] https://wiki.debian.org/sbuild
[2] https://fedoraproject.org/wiki/Mock
Regards,
Bulat Gaifullin
We are happy to introduce Packetary [0], which was separated from fuel-mirror
[1].
Packetary provides flexible and data driven interface to manage (clone/build)
rpm/deb repos and packages (not implemented yet).
Packetary provides object model and API.
One can use this framework to implement oper
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 23 Dec 2015, at 17:29, Aleksey Kasatkin wrote:
>
> +1
>
> Aleksey Kasatkin
>
>
> On Wed, Dec 23, 2015 at 3:57 PM, Aleksandr Didenko <mailto:adide...@mirantis.com>> wrote:
> +1
>
> On Wed, D
Thank you.
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 21 Dec 2015, at 13:11, Igor Kalnitsky wrote:
>
> Well, the agreement is reached. I added Bulat to both fuel-web-core
> and fuel-mirror-core groups.
>
> Bulat, congratulations! Will be happy to see even more thorough
+1
Regards,
Bulat Gaifullin
Mirantis Inc.
> On 15 Dec 2015, at 22:19, Andrew Maksimov wrote:
>
> +1
>
> Regards,
> Andrey Maximov
> Fuel Project Manager
>
> On Tue, Dec 15, 2015 at 9:41 PM, Vladimir Kuklin <mailto:vkuk...@mirantis.com>> wrote:
> Folk
+1
> On 24 Sep 2015, at 10:45, Tetiana Lashchova wrote:
>
> Hi folks!
>
> Some tests in murano code use incorrect order of arguments in assertEqual.
> The correct order expected by the testtools is
>
> def assertEqual(self, expected, observed, message=''):
> """Assert that
27 matches
Mail list logo