from:"Serg Melikyan"

Re: [openstack-dev] [murano]An error occured when I executed environment-deploy

2017-02-28 Thread Serg Melikyan

Atsumi,

I've checked the guide you are refering too, make sure your endpoint is
setup properly in Keystone. List endpoints and services in Keystone and
make sure that they mapped to correct region

On Tue, Feb 28, 2017 at 1:07 AM, Kirill Zaitsev 
wrote:

> Well, looks like you don’t have murano-api endpoint in keystone service
> catalog. Have you tried adding it?
>
> --
> Kirill Zaitsev
>
>
> On 28 February 2017 at 09:05:34, 渥美 慶彦 (atsumi.yoshih...@po.ntts.co.jp)
> wrote:
>
> Hi everyone,
>
> I tried to execute "environment-deploy", but failed.
> 2017-02-27 15:40:21.066 13046 ERROR murano.common.engine [-]
> keystoneauth1.exceptions.catalog.EndpointNotFound: Endpoint for
> unknown service
> (Omitted)
>
> auth_uri is equal to that one in nova.conf.
> I refered to
> http://egonzalez.org/murano-in-rdo-openstack-manual-installation/
> after "Import ApacheHttpServer package".
> Do you have information?
>
> My environment:
> CentOS 7
> OpenStack Mitaka(Packstack), including Heat
> Murano[
> openstack-murano-api-2.0.0-2.el7.noarch
> python2-muranoclient-0.8.6-1.el7.noarch
> openstack-murano-common-2.0.0-2.el7.noarch
> openstack-murano-engine-2.0.0-2.el7.noarch
> openstack-murano-doc-2.0.0-2.el7.noarch
> ](yum install)
> Base Murano package:tag2.0.0
>
> Thank you.
> --
> 
> NTTソフトウェア株式会社
> クラウド＆セキュリティ事業部 第一事業ユニット
> 渥美 慶彦（Atsumi Yoshihiko）
> 〒220-0012
> 横浜市西区みなとみらい4-4-5 横浜アイマークプレイス13F
> TEL：045-212-7539
> FAX：045-212-9800
> E-mail：atsumi.yoshih...@po.ntts.co.jp
> 
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Is 'murano-agent' support optional in an OpenStack Murano Deployment ?

2017-02-21 Thread Serg Melikyan

Hi Greg,

>Is the Murano-agent functionality truly optional?
Yes, there is even an option in config file to completely disable this
functionality: [engine]\disable_murano_agent.

You can use Heat Software Configuration to configure VM or just
Cloud-Init. Unfortunately I don't have examples under my hand, but
basically you should use LinuxUDInstance or HeatSWConfigLinuxInstance
instead of LinuxMuranoInstance in your application.

>Is there a way to determine whether a Murano Application requires Murano-agent 
>functionality or not
apps.openstack.org doesn't have any indication regarding if
murano-agent functionality is needed or not. There is no way to deduce
this information without looking into the source code.

>Roughly what % of Murano Applications leverage the Murano-agent functionality ?
100% of murano applications published on apps.openstack.org require
murano-agent.

On Tue, Feb 21, 2017 at 5:39 AM, Waines, Greg  wrote:
> A couple of questions about Murano-agent functionality in an OpenStack
> Murano Deployment:
>
>
>
> 1. Is the Murano-agent functionality truly optional ?
>
>
>
>  I believe answer is yes … although wanted to confirm that the
> optionality wasn’t referring to whether Murano-agent was implemented with
> same or separate rabbit server.
>
>
>
>
>
> 2. Assuming Murano-agent functionality is optional,
>
>
>
>  I am surprised that items in the Murano Community Catalog
> (https://apps.openstack.org/#tab=murano-apps )
>  don’t explicitly indicate whether they require Murano-agent
> functionality or not.
>
>
>
>  a) Is there a way to determine whether a Murano Application requires
> Murano-agent functionality or not ?
>
>  b) Roughly what % of Murano Applications leverage the Murano-agent
> functionality ?
>
>
>
>
>
>
>
> Greg.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] [ptl] PTL Candidacy for Pike

2017-01-25 Thread Serg Melikyan

Felipe,

thank you so much for all your efforts so far, I am sure that you will
be a great leader for the Murano!

On Tue, Jan 24, 2017 at 10:58 AM, MONTEIRO, FELIPE C  wrote:
> Hi,
>
>
>
> My name is Felipe Monteiro. I have decided to run for Murano PTL for the
> Pike
>
> release cycle. I would like to continue to grow Murano in order to make the
>
> project more stable, mature and performant, while exploring avenues to
> evolve
>
> the project.
>
>
>
> I’ve been working on the project for the past couple months. Working with
>
> Murano is probably the most exciting thing I do professionally. When I first
>
> joined OpenStack, I was overwhelmed by the sheer volume of code, as well
>
> as the complexity involved in how the various services interact. Thanks
>
> to the welcoming culture surrounding Murano, I was immediately given help,
>
> advice and guidance, which, after a couple months of persistence and hard
> work,
>
> has enabled me to feel like a solid contributor within OpenStack.
>
>
>
> Over the past couple months, I’ve been heavily invested in improving
> Murano’s
>
> testing framework, in order to make the project more stable and more mature.
>
> This has resulted in Murano and Murano Dashboard’s unit test coverage having
>
> approximately doubled, as well as having various gaps in Murano Dashboard’s
>
> functional testing filled via Selenium tests. I also regularly code review
>
> other developers' work and take on the arduous task of editing Murano's
>
> documentation, because, as a native speaker of English, I really have no
> excuse
>
> but to help out in this regard.
>
>
>
> I’m really excited to work with Murano further, and to grow the community
>
> surrounding it. The more companies that contribute to Murano, the stronger
> the
>
> community around it will be, capable of maintaining and enhancing Murano for
>
> years to come.
>
>
>
> The main goals I’d like to focus on for Murano during Pike are:
>
> * Significantly improve Murano Tempest testing. This includes integrating
>
>Murano with a new OpenStack project called Patrole. Patrole, a Tempest
>
>plugin responsible for testing Role-Based Access Control, was spearheaded
>
>and founded by AT&T developers and contributors. Its purpose is to help
>
>harden the security underpinning various OpenStack services – Murano
>
>included.
>
>  * Significantly improve Murano documentation.
>
> * Improve Murano’s (particularly Murano Dashboard’s) integration with GLARE
> –
>
>there are a number of areas in the UI where GLARE is not supported.
>
>These areas should be fixed to provide users who use Murano and GLARE a
>
>better user experience.
>
> * Focus on addressing a number of outstanding bugs in Murano. These include
>
>adding SIGHUP signal support to Murano, support multiple rabbit hosts in
>
>RabbitMQ for Murano Agent, and addressing other UI bugs, like abandon
>
>environment hanging issues.
>
>
>
> My personal ambition leads me to want to also tackle the following items:
>
> * Possibly integrate Murano with other OpenStack projects, including
>
>Ceilometer, Search Light, or Kolla-Kubernetes.
>
>  * Investigate multi-cloud support for Murano, so that it works with
> different
>
>cloud services including VMWare and Amazon.
>
> * Increase developer contribution in Murano through my own coding efforts,
>
>as well as through AT&T’s resources.
>
>
>
> Thanks for taking the time to read through this roadmap and to consider my
>
> candidacy. Regardless of the outcome, I'm excited to continue contributing
>
> to Murano, be it code or code reviews.
>
>
>
> Thank You,
>
> Felipe Monteiro
>
> Associate-Applications Developer
>
> TDP – Emerging Technologies Program
>
> Centralized Development
>
> Office: +1 (678) 917-1767
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

2017-01-25 Thread Serg Melikyan

I would like to comment a little bit regarding usage of Glare in
Murano and Mirantis OpenStack:

> How much have these projects adopted Glare?
Glare is preferred backend for storing murano packages, which provides
versioning capabilities (they are not available without it)

>Is Glare being deployed already?
Mirantis OpenStack 9.0 by default is deploying Murano with Glare used
as a backend.

>What projects are the main consumers of Glare?
Murano

On Wed, Jan 25, 2017 at 2:56 PM, Mike Perez  wrote:
> On 18:16 Jan 24, Mikhail Fedosin wrote:
>> Hey, Flavio :) Thanks for your questions!
>>
>> As you said currently only Nokia's adopting Glare for its own platform, but
>> if we talk about OpenStack, that I believe Mistral will start to use it
>> soon.
>> In my opinion Glare's adoption is low due to the fact that the project is
>> not included under Big Tent. I think it will be changed soon, because now
>> I'm finishing Glare v1 API proposal, and when it's done we will apply under
>> BT.
>>
>> About Glance v2 API - as I said they are +- the same with several cosmetic
>> differences (in Glance status is called 'queued', in Glare we renamed it to
>> 'drafted', and so on). For this reason I'm going to implement a middleware,
>> that will provide a full Image API v2 for Glare (even with unnecessary
>> '/v2' prefix) and glance clients will be able to communicate with it as
>> with Glance. It's definitely doable and we can discuss it more detailed
>> during the PTG.
>
> Both Flavio and Doug asked you to expand on the issues with the Glance API. 
> Can
> you please expand on that.
>
> --
> Mike Perez
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Congress][Fuel] Fuel plugin for installing Congress

2017-01-16 Thread Serg Melikyan

I'd like to introduce you fuel plugin for installing and configuring
Congress for Fuel [0].

This plugin was developed by Fuel@Opnfv [1] Community in order to be
included to the next release of the Fuel@Opnfv - Danube. We believe
that this plugin might be helpful not only for us but also for general
OpenStack community and decided to continue development of the plugin
in the OpenStack Community.

Please join us in the development of the Congress plugin, your
feedback is greatly appreciated.

P.S. Right now core team includes Fedor Zhadaev - original developer
of the plugin, and couple of developers from Fuel@Opnfv including me.
We considered adding congress-core to the list but decided to see
amount of interest and feedback first from Congress team.

References:
[0] http://git.openstack.org/cgit/openstack/fuel-plugin-congress/
[1] https://wiki.opnfv.org/display/Fuel/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Removing Ekaterina Chernova and Filip Blaha from cores

2016-11-17 Thread Serg Melikyan

no objections

On Thu, Nov 17, 2016 at 7:28 AM, Kirill Zaitsev 
wrote:

> I’m proposing to remove Ekaterina Chernova and Filip Blaha from the list
> of murano cores. They both have been very active in the previous cycles,
> but their focus have shifted and we haven’t seen much activity in Newton
> and Ocata.
> If the situation would change — I would be very happy to welcome back both
> Ekaterina and Filip to murano core team. I would also like to express my
> thanks for all the hard work Ekaterina and Filip has put into murano. Hope
> to see you back in future.
>
> You can find statistics info here 
> *http://stackalytics.com/?module=murano-group&release=all&user_id=filip.bl...@hpe.com
> <http://stackalytics.com/?module=murano-group&release=all&user_id=filip.bl...@hpe.com>*
> and here: http://stackalytics.com/?module=murano-group&release=
> all&user_id=efedorova
> Ekaterina is also core in murano-milestone (i.e. stable branches), so this
> also implies removing her from the group too.
>
> If you have any thoughts or objections to this decision — please voice
> them.
>
> --
> Kirill Zaitsev
> Murano Project Tech Lead
> Software Engineer at
> 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/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Nominating Felipe Monteiro for murano core

2016-11-17 Thread Serg Melikyan

+1

On Thu, Nov 17, 2016 at 5:54 AM, Alexander Tivelkov 
wrote:

> +1
>
> On Thu, Nov 17, 2016 at 4:29 PM Kirill Zaitsev 
> wrote:
>
>> Hello team, I would like to nominate Felipe for murano core.
>> His and his teams work on increasing murano unit test coverage in Newton
>> and Ocata has allowed us to reach astonishing 85%
>> I would like to personally thank Felipe for his dedication to making
>> murano a more mature and stable project!
>> You can view statistics for his work here: http://stackalytics.com/?
>> metric=commits&release=ocata&module=murano-group&user_id=
>> felipe.monte...@att.com
>>
>> Please respond with +1/-1 on the candidate =)
>>
>> --
>> Kirill Zaitsev
>> Sent with Airmail
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> --
> Regards,
> Alexander Tivelkov
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] IRC Meeting time suggestion

2016-10-04 Thread Serg Melikyan

Omar,

time works for me!

On Thu, Sep 29, 2016 at 7:39 AM, aaronzhu1121 
wrote:

> Good news for contributor from China, will attend the meeting.
>
>
> Thanks,
>
> Zhu Rong
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] Separating guides from murano developers documentation

2016-08-16 Thread Serg Melikyan

Hi folks,

at this moment all murano documentation (including admin & user
guides) is published only in one place [0], but actually all other
projects store there only developer documentation and guides are
separated. I propose to follow same model with murano documentation.
What do you think?

References:
[0] docs.openstack.org/developer/murano/

-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Load murano Apps

2016-06-28 Thread Serg Melikyan

Hi Alione,

you need to archive content of the "package" folder, e.g. MySQL [0].
Make sure that manifest.yaml is on the root level.


References:
[0] https://github.com/openstack/murano-apps/tree/master/MySQL/package

On Tue, Jun 28, 2016 at 8:36 AM, Alioune  wrote:
> Hi all,
> I've downloaded murano apps from [1] and I would like to upload them as
> package.
>
> I would like to know which folders into murano-apps to zip and load from
> "Package Definition" ?
>
> How to add these apps with murano package-import ?
>
> Regards,
>
> [1] https://github.com/openstack/murano-apps
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

2016-06-15 Thread Serg Melikyan

+1

Finally!

On Wed, Jun 15, 2016 at 3:33 AM, Ihor Dvoretskyi 
wrote:

> +1 for Alexander Tivelkov.
>
> Good effort.
>
> On Wed, Jun 15, 2016 at 1:08 PM, Artem Silenkov 
> wrote:
>
>> Hello!
>>
>> +1
>>
>> Regards,
>> Artem Silenkov
>> ---
>> paas-team
>>
>> On Wed, Jun 15, 2016 at 12:56 PM, Dmytro Dovbii 
>> wrote:
>>
>>> +1
>>> 15 июня 2016 г. 6:47 пользователь "Yang, Lin A" 
>>> написал:
>>>
>>> +1 both for Alexander Tivelkov and Zhu Rong. Well deserved.
>>>>
>>>> Regards,
>>>> Lin Yang
>>>>
>>>> On Jun 15, 2016, at 3:17 AM, Kirill Zaitsev 
>>>> wrote:
>>>>
>>>> Hello team, I want to annonce the following changes to murano core team:
>>>>
>>>> 1) I’d like to nominate Alexander Tivelkov for murano core. He has been
>>>> part of the project for a very long time and has contributed to almost
>>>> every part of murano. He has been fully committed to murano during mitaka
>>>> cycle and continues doing so during newton [1]. His work on the scalable
>>>> framework architecture is one of the most notable features scheduled for N
>>>> release.
>>>>
>>>> 2) I’d like to nominate Zhu Rong for murano core. Last time he was
>>>> nominated I -1’ed the proposal, because I believed he needed to start
>>>> making more substantial contributions. I’m sure that Zhu Rong showed his
>>>> commitment [2] to murano project and I’m happy to nominate him myself. His
>>>> work on the separating cfapi from murano api and contributions headed at
>>>> addressing murano’s technical debt are much appreciated.
>>>>
>>>> 3) Finally I would like to remove Steve McLellan[3] from murano core
>>>> team. Steve has been part of murano from very early stages of it. However
>>>> his focus has since shifted and he hasn’t been active in murano during last
>>>> couple of cycles. I want to thank Steve for his contributions and express
>>>> hope to see him back in the project in future.
>>>>
>>>>
>>>> Murano team, please respond with +1/-1 to the proposed changes.
>>>>
>>>> [1] http://stackalytics.com/?user_id=ativelkov&metric=marks
>>>> [2] http://stackalytics.com/?metric=marks&user_id=zhu-rong
>>>> [3] http://stackalytics.com/?user_id=sjmc7
>>>> --
>>>> Kirill Zaitsev
>>>> Software Engineer
>>>> 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/listinfo/openstack-dev
>>>>
>>>>
>>>>
>>>>
>>>> __
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best regards,
>
> Ihor Dvoretskyi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

2016-06-06 Thread Serg Melikyan

Regarding openstack/murano-apps, in this repo we use stable/kilo
branch not as a version of the apps, but rather than compatibility
version of the app. Applications which are published in this branch
are compatible with Murano from stable/kilo, given than we have a lag
between upstream release and which release actually our users use and
more over develop applications I would considered leaving stable/kilo
branch in the openstack/murano-apps.

On Mon, Jun 6, 2016 at 8:30 AM, Kirill Zaitsev  wrote:
> I’ve submitted a request to release all the unreleased code we still have
> for murano repositories https://review.openstack.org/#/c/325359/ ; It would
> be really great if we could get one final release before EOL’ing kilo in
> murano, murano-dashboard, murano-agent and python-muranoclient, if that is
> possible. After that I believe kilo branches in those repos are ready to be
> EOL’ed and deleted.
>
> --
> Kirill Zaitsev
> Software Engineer
> Mirantis, Inc
>
> On 3 June 2016 at 09:26:58, Tony Breeds (t...@bakeyournoodle.com) wrote:
>
> On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote:
>> Hi all,
>> In early May we tagged/EOL'd several (13) projects. We'd like to do a
>> final round for a more complete set. We looked for projects meet one or
>> more
>> of the following criteria:
>> - The project is openstack-dev/devstack, openstack-dev/grenade or
>> openstack/requirements
>> - The project has the 'check-requirements' job listed as a template in
>> project-config:zuul/layout.yaml
>> - The project is listed in governance:reference/projects.yaml and is
>> tagged
>> with 'release:managed' or 'stable:follows-policy' (or both).
>
> So We've had a few people opt into EOL'ing which is great.
>
> I've Moved the lists from paste.o.o to a gist. The reason for that is I can
> update them, the URL doesn't change and there is a revision history (or
> sorts).
>
> The 2 lists are now at:
> https://gist.github.com/tbreeds/7de812a5d363fab4bd425beae5084c87
>
> Given that there are now only 39 repos that are not (yet) EOL'ing I'm
> inclined
> to default to EOL'ing everything that that isn't a deployment project.
>
> That is to say I'm suggesting that:
> openstack/cloudkitty cloudkitty 1
> openstack/cloudkitty-dashboard cloudkitty 1
> openstack/cloudpulse BigTent
> openstack/compute-hyperv BigTent
> openstack/fuel-plugin-purestorage-cinder BigTent
> openstack/group-based-policy BigTent 4
> openstack/group-based-policy-automation BigTent
> openstack/group-based-policy-ui BigTent
> openstack/murano-apps murano 3
> openstack/nova-solver-scheduler BigTent
> openstack/openstack-resource-agents BigTent
> openstack/oslo-incubator oslo
> openstack/powervc-driver BigTent 1
> openstack/python-cloudkittyclient cloudkitty 1
> openstack/python-cloudpulseclient BigTent
> openstack/python-group-based-policy-client BigTent
> openstack/swiftonfile BigTent
> openstack/training-labs Documentation
> openstack/yaql BigTent 2
>
> Get added to the EOL list.
>
> With the following hanging back for a while as they might need small tweaks
> based on the kilo-eol tag.
>
> openstack/cookbook-openstack-bare-metal Chef OpenStack
> openstack/cookbook-openstack-block-storage Chef OpenStack
> openstack/cookbook-openstack-client Chef OpenStack
> openstack/cookbook-openstack-common Chef OpenStack
> openstack/cookbook-openstack-compute Chef OpenStack
> openstack/cookbook-openstack-dashboard Chef OpenStack
> openstack/cookbook-openstack-data-processing Chef OpenStack
> openstack/cookbook-openstack-database Chef OpenStack
> openstack/cookbook-openstack-identity Chef OpenStack
> openstack/cookbook-openstack-image Chef OpenStack
> openstack/cookbook-openstack-integration-test Chef OpenStack
> openstack/cookbook-openstack-network Chef OpenStack
> openstack/cookbook-openstack-object-storage Chef OpenStack
> openstack/cookbook-openstack-ops-database Chef OpenStack
> openstack/cookbook-openstack-ops-messaging Chef OpenStack
> openstack/cookbook-openstack-orchestration Chef OpenStack
> openstack/cookbook-openstack-telemetry Chef OpenStack
> openstack/openstack-ansible OpenStackAnsible
> openstack/openstack-chef-repo Chef OpenStack
> openstack/packstack BigTent
>
> Yours Tony.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Developme

Re: [openstack-dev] [horizon][all] How to properly depend on Horizon

2016-04-04 Thread Serg Melikyan

>I agree the simplest way is to publish horizon to PyPI, but the OpenStack does 
>not release server projects to PyPI yet.

Problem is that openstack/horizon is actually two things in one repo:
* OpenStack Dashboard which is server project
* Horizon which is library

In this case I would say that publishing to pypi.openstack.org would
be much more practical.

On Sun, Apr 3, 2016 at 9:49 PM, Akihiro Motoki  wrote:
>
> Hi Serg,
>
> I proposed another way to sahara-dashboard [1].
> This is the way used in neutron sub-projects.
> It also allows us to use constrained environments used in OpenStack gate jobs.
> I believe it works for all horizon related projects.
>
> I agree the simplest way is to publish horizon to PyPI, but
> the OpenStack does not release server projects to PyPI yet.
>
> Akihiro
>
> [1] https://github.com/openstack/sahara-dashboard/blob/master/tox.ini#L8
>
> 2016-04-04 10:37 GMT+09:00 Serg Melikyan :
> > Hi folks,
> >
> > while I was working on bug [0] with incorrect dependency to horizon in
> > stable/mitaka I discovered at least three different ways how people
> > add such dependency:
> >
> > 1. tarball dependency in tox.ini [1]
> > 2. tarball dependency in test-requirements.txt [2]
> > 3. git repo dependency in  test-requirements.txt [3]
> >
> > Question: How to properly depend on horizon?
> >
> > P.S. Looks like update.py in openstack/requirements simply ignores #2
> > and #3 and don't count as extra dependency.
> >
> > P.P.S Why we can't publish horizon to pypi.openstack.org?
> >
> > Reference:
> > [0] https://bugs.launchpad.net/bugs/1565577
> > [1] 
> > https://github.com/openstack/designate-dashboard/blob/dfa2fc6660467da2f1c53e12aeb7d7aab5d7531e/tox.ini#L20
> > [2] 
> > https://github.com/openstack/monasca-ui/blob/8861bede7e06d19b265d3425208b4865c480eb69/test-requirements.txt#L25
> > [3] 
> > https://github.com/openstack/manila-ui/blob/bf382083b281a77f77df9e0bd51376df49d53b2e/test-requirements.txt#L5
> >
> > --
> > Serg Melikyan, Development Manager at Mirantis, Inc.
> > http://mirantis.com | smelik...@mirantis.com
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon][all] How to properly depend on Horizon

2016-04-03 Thread Serg Melikyan

Hi folks,

while I was working on bug [0] with incorrect dependency to horizon in
stable/mitaka I discovered at least three different ways how people
add such dependency:

1. tarball dependency in tox.ini [1]
2. tarball dependency in test-requirements.txt [2]
3. git repo dependency in  test-requirements.txt [3]

Question: How to properly depend on horizon?

P.S. Looks like update.py in openstack/requirements simply ignores #2
and #3 and don't count as extra dependency.

P.P.S Why we can't publish horizon to pypi.openstack.org?

Reference:
[0] https://bugs.launchpad.net/bugs/1565577
[1] 
https://github.com/openstack/designate-dashboard/blob/dfa2fc6660467da2f1c53e12aeb7d7aab5d7531e/tox.ini#L20
[2] 
https://github.com/openstack/monasca-ui/blob/8861bede7e06d19b265d3425208b4865c480eb69/test-requirements.txt#L25
[3] 
https://github.com/openstack/manila-ui/blob/bf382083b281a77f77df9e0bd51376df49d53b2e/test-requirements.txt#L5

-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon][mitaka][all] Update dependency to horizon for stable/mitaka

2016-04-03 Thread Serg Melikyan

Hi folks,

I've noticed that several projects which have dashboard which depend
on horizon reference incorrect version [0]:

* designate-dashboard
* mistral-dashboard
* murano-dashboard (fix proposed)
* manila-ui
* ironic-ui
* searchlight-ui
* magnum-ui
* monasca-ui

all these projects, and some others for sure, still depend on horizon
from master in they stable/mitaka branch. This may lead to broken
stable/mitaka once horizon will merge something incompatible to the
master branch.

Please update you dependency to horizon correspondingly ASAP.

Reference:
[0] https://bugs.launchpad.net/bugs/1565577

-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano][release] missing build artifacts

2016-04-03 Thread Serg Melikyan

Hi Doug,

I +1 your commit with removing build artifacts for
openstack/murano-apps repo, we indeed don't have artifacts for
murano-apps.

>It would be good to understand what your intent is for builds. Can you follow 
>up here on this thread with some details?

openstack/murano-apps contains set of working applications for murano
intended to be used as examples and as well as production working
apps. Using stable branches (stable/liberty, stable/mitaka) we
separate applications working on corresponding version of OpenStack.
Hopefully at some point of time our built artifact is going to be each
application published to apps.openstack.org.

I believe we don't plan to have artifacts in this repo which are part
of the OpenStack release itself. Is there other steps that we need to
take regarding this?

On Fri, Apr 1, 2016 at 12:16 PM, Doug Hellmann  wrote:
> Murano team,
>
> We noticed in our audit of the links on
> http://releases.openstack.org/mitaka/index.html that the links to the
> build artifacts for murano-apps point to missing files. The murano-apps
> repository doesn't seem to have any real build jobs configured in
> openstack-infra/project-config/zuul/layout.yaml, so it's not clear how
> tagging is producing a release for you.
>
> For now, we are disabling links to the artifacts for that repo via
> https://review.openstack.org/300457 but we're also planning to remove
> murano-apps from the official Mitaka page since there don't appear to be
> any actual related deliverables (https://review.openstack.org/300473).
>
> It would be good to understand what your intent is for builds. Can
> you follow up here on this thread with some details?
>
> Thanks,
> Doug

-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Component Leads Elections

2016-03-31 Thread Serg Melikyan

Hi fuelers,

only few hours left until period of self-nomination will be closed, but so
far we don't have neither consensus regarding how to proceed further nor
candidates.

I've increased period of self-nomination for another week (until April 7,
23:59 UTC) and expect to have decision about how we are going to proceed
further if no one nominate himself or candidates for each of the three
projects.

I propose to start with defining steps that we are going to take if no one
nominate himself by April 7 and move forward with separate discussion
regarding governance.

P.S. I strongly believe that declaring Component Leads role as obsolete
require agreement among all members of Fuel team, which may take quite a
lot of time. I think we should propose change-request to existing spec with
governance [0], and have decision by end of Newton cycle.

References:
[0]
https://specs.openstack.org/openstack/fuel-specs/policy/team-structure.html

On Thu, Mar 31, 2016 at 3:22 AM, Evgeniy L  wrote:

> Hi,
>
> I'm not sure if it's a right place to continue this discussion, but if
> there are doubts that such role is needed, we should not wait for another
> half a year to drop it.
>
> Also I'm not sure if a single engineer (or two engineers) can handle
> majority of upcoming patches + specs + meetings around features. Sergii and
> Igor put a lot of efforts to make it work, but does it really scale?
>
> I think it would be better to offload more responsibilities to core
> groups, and if core team (of specific project) wants to see formal or
> informal leader, let them decide.
>
> I would be really interested to see feedback from current component leads.
>
> Thanks,
>
>
> On Wed, Mar 30, 2016 at 2:20 PM, Vladimir Kozhukalov <
> vkozhuka...@mirantis.com> wrote:
>
>> Dmitry,
>>
>> "No need to rush" does not mean we should postpone
>> team structure changes until Ocata. IMO, CL role
>> (when it is exposed to Fuel) contradicts to our
>> modularization activities. Fuel should be an aggregator
>> of components. What if we decide to use Ironic or
>> Neutron as Fuel components? Should we chose also
>> Ironic CL? NO! Ironic is an independent
>> project with its own PTL.
>>
>> I agree with Mike that we could remove this CL
>> role in a month if have consensus. But does it
>> make any sense to chose CLs now and then
>> immediately remove this role? Probably, it is better
>> to make a decision right now. I'd really like to
>> see here in this ML thread opinions of our current
>> CLs and other people.
>>
>>
>>
>> Vladimir Kozhukalov
>>
>> On Tue, Mar 29, 2016 at 11:21 PM, Dmitry Borodaenko <
>> dborodae...@mirantis.com> wrote:
>>
>>> On Tue, Mar 29, 2016 at 03:19:27PM +0300, Vladimir Kozhukalov wrote:
>>> > > I think this call is too late to change a structure for now. I
>>> suggest
>>> > > that we always respect the policy we've accepted, and follow it.
>>> > >
>>> > > If Component Leads role is under a question, then I'd continue the
>>> > > discussion, hear opinion of current component leads, and give this a
>>> time
>>> > > to be discussed. I'd have nothing against removing this role in a
>>> month
>>> > > from now if we reach a consensus on this topic - no need to wait for
>>> the
>>> > > cycle end.
>>> >
>>> > Sure, there is no need to rush. I'd also like to see current CL
>>> opinions.
>>>
>>> Considering that, while there's an ongoing discussion on how to change
>>> Fuel team structure for Ocata, there's also an apparent consensus that
>>> we still want to have component leads for Newton, I'd like to call once
>>> again for volunteers to self-nominate for component leads of
>>> fuel-library, fuel-web, and fuel-ui. We've got 2 days left until
>>> nomination period is over, and no volunteer so far :(
>>>
>>> --
>>> Dmitry Borodaenko
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack

Re: [openstack-dev] Fw:Extending API via Plugins

2016-03-30 Thread Serg Melikyan

Hi wangzhh,

I think this look reasonable, but I would prefer to have a proper spec for
this feature. I generally like to have extendable API in Murano.

On Thu, Mar 24, 2016 at 8:49 PM, 王正浩  wrote:

> I'm sorry that I forgot to tell you murano-paste.ini should be modified to
> ...
> [app:apiv1app]
> paste.app_factory = murano.api.v1.router:APIRouterV1.factory
> ...
> And the file [4] is murano/api/v1/extensions_base.py
>
> -- Original --
> *From: * "王正浩";
> *Date: * Fri, Mar 25, 2016 11:10 AM
> *To: * "List";
> *Cc: * "smelikyan";
> *Subject: * Extending API via Plugins
>
> Hi Serg Melikyan,
> I don't know much about CF Broker API. I'm sorry that I
> have no real use-case. But here is a test one which I plan to
> complete.
>
> I modified murano/common/wsgi.py[0], murano/api/v1/router.py[1],
> added
> ...
> murano.api.v1.extensions =
> test = murano.api.v1.extensions.test:testAPI
> ...
> to the setup.cfg[2]. Imply the class testAPI[3].
> The class testAPI  inherit a base class APIExtensionBase[4].
> I'll show you my code.
> P.S. I copied it from nova. So there are some extra code, hope you don't
> mind.
> [0] http://paste.openstack.org/show/491841/
> [1] http://paste.openstack.org/show/491840/
> [2] http://paste.openstack.org/show/491842/
> [3] http://paste.openstack.org/show/491845/
> [4] http://paste.openstack.org/show/491843/
>



-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [fuel] Component Leads Elections

2016-03-24 Thread Serg Melikyan

Hi folks,

I'd like to announce that we're running the Component Leads elections.
Detailed information is available on wiki [0].

Component Lead: defines architecture of a particular module or
component in Fuel, resolves technical disputes in their area of
responsibility. All design specs that impact a component must be
approved by the corresponding component lead [1].

Fuel has three large sub-teams, with roughly comparable codebases,
that need dedicated component leads:

* fuel-library
* fuel-web
* fuel-ui

Nominees propose their candidacy by sending an email to the
openstack-dev@lists.openstack.org mailing-list, with the subject:
"[fuel]  lead candidacy"
(for example, "[fuel] fuel-library lead candidacy").

Timeline:
* March 25 - March 31: Open candidacy for Component leads positions
* April 1 - April 7: Component leads elections

References
[0] https://wiki.openstack.org/wiki/Fuel/Elections_Spring_2016
[1] https://specs.openstack.org/openstack/fuel-specs/policy/team-structure.html

-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Extending API via Plugins

2016-03-24 Thread Serg Melikyan

Hi wangzhh,

we had several discussions about having plugins for API, for example
we could branch CF Broker API to the plugin instead of having it as
part of murano. Unfortunately we didn't found many use-cases at that
time, so we didn't proceed further from just talking about that.

Can you share your use-case for extending API?

P.S. I think it's better to discuss this topic in separate thread from
discussion about bundles.

On Wed, Mar 23, 2016 at 8:56 PM, 王正浩  wrote:
> Thanks a lot!
> And I have another question.
> When I extend API, I find it's a little inconvenient. Does it a good idea
> to use stevedore? In this way, all the API are considered as plugins.
>
> We can extend API like this:
> 1.Add a namespace like
> murano.api.v1.extensions =
> test = murano.api.v1.extensions.test:testAPI
> to set.cfg.
> 2.Add a file named test.py and imply the class testAPI
>
> ------ Original --
> From:  "Serg Melikyan";
> Date:  Thu, Mar 24, 2016 07:24 AM
> To:  "OpenStack Development Mailing
> List";
> Cc:  "王正浩";
> Subject:  [murano] HowTo: Compose a local bundle file
>
> Hi wangzhh,
>
> You can use python-muranoclient in order to download bundle from
> apps.openstack.org and then use it somewhere else for the import:
>
> murano bundle-save app-servers
>
> you can find more about this option in corresponding spec [0].
>
> Generally local bundle is not different from the remote one, you can
> take a look at the same bundle [1] internals. If you will download
> this file and then will try to execute:
>
> murano bundle-import ./app-servers.bundle
>
> murano will try to find all mentioned packages in the local folder
> before going to apps.openstack.org.
>
> References:
> [0]
> http://specs.openstack.org/openstack/murano-specs/specs/liberty/bundle-save.html
> [1] http://storage.apps.openstack.org/bundles/app-servers.bundle
>
> On Wed, Mar 23, 2016 at 1:48 AM, 王正浩  wrote:
>>
>> Hi Serg Melikyan!
>>   I'm a programmer of China. And I have a question about Application
>> Servers Bundle (bundle)
>> https://apps.openstack.org/#tab=murano-apps&asset=Application%20Servers%20Bundle
>>   I want to import a bundle across a local bundle file. Could you tell me
>> how  to create a bundle file? Is there any doc explain it?
>>   Thanks!
>>
>>
>>
>>
>> --
>> --
>> Best Regards,
>> wangzhh
>
>
>
>
> --
> Serg Melikyan



-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] HowTo: Compose a local bundle file

2016-03-23 Thread Serg Melikyan

Hi wangzhh,

You can use python-muranoclient in order to download bundle from
apps.openstack.org and then use it somewhere else for the import:

murano bundle-save app-servers

you can find more about this option in corresponding spec [0].

Generally local bundle is not different from the remote one, you can
take a look at the same bundle [1] internals. If you will download
this file and then will try to execute:

murano bundle-import ./app-servers.bundle

murano will try to find all mentioned packages in the local folder
before going to apps.openstack.org.

References:
[0] 
http://specs.openstack.org/openstack/murano-specs/specs/liberty/bundle-save.html
[1] http://storage.apps.openstack.org/bundles/app-servers.bundle

On Wed, Mar 23, 2016 at 1:48 AM, 王正浩  wrote:
>
> Hi Serg Melikyan!
>   I'm a programmer of China. And I have a question about Application Servers 
> Bundle (bundle) 
> https://apps.openstack.org/#tab=murano-apps&asset=Application%20Servers%20Bundle
>   I want to import a bundle across a local bundle file. Could you tell me how 
>  to create a bundle file? Is there any doc explain it?
>   Thanks!
>
>
>
>
> ------
> --
> Best Regards,
> wangzhh

-- 
Serg Melikyan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [i18n][horizon][sahara][trove][magnum][murano] dashboard plugin release schedule

2016-03-21 Thread Serg Melikyan

Akihiro,

thank you for your effort with translation, this milestone sounds fine for
murano-dashboard.

On Sat, Mar 19, 2016 at 10:43 AM, Akihiro Motoki  wrote:

> Hi dashboard plugins team
> (sahara-dashboard, trove-dashboard, magnum-ui, murano-dashboard)
>
> As Horizon i18n liaison, I would like to have a consensus on a rough
> schedule
> of translation import for Horizon plugins.
> Several plugins and horizon itself already released RC1.
>
> For Horizon translation, we use the following milestone:
>   Mitaka-3 : Soft string freeze
>   Mitaka-RC1: Hard string freeze
>   Mitaka-RC2: Final translation import
>
> Does this milestone sound good for sahara/trove/magnum/murano dashboard
> plugins?
> This means that each dashboard plugin project needs to release RC2 (or
> some RC)
> even only for translation import. Otherwise, translator efforts after
> hard string freeze
> will not be included in Mitaka release.
>
> If the above idea sounds good, I hope RC2 (or later RC) will be released
> on early of the week Mar 28 for translation import.
> This schedule allows translators to work on translations after "Hard
> string freeze".
>
> Mitaka is the first release for Horizon plugins with translations,
> so I hope this mail helps everyone around translations.
>
> Best Regards,
> Akihiro
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] [FFE] Support for Magnum Plugin

2016-03-14 Thread Serg Melikyan

Granted

On Mon, Mar 14, 2016 at 4:09 AM, Nikolay Starodubtsev <
nstarodubt...@mirantis.com> wrote:

> Hi,
> I don't like when we need to break rules, but in this case I agree with
> Kirill. As far as the plugin is not something which can broke general
> murano functionality, I'm for FFE.
>
>
>
> Nikolay Starodubtsev
>
> Software Engineer
>
> Mirantis Inc.
>
>
> Skype: dark_harlequine1
>
> 2016-03-14 11:58 GMT+03:00 Kirill Zaitsev :
>
>> I’m going to advocate for this FFE. Even though it’s very late to ask for
>> FFE, I believe, that this commit is very low-risk/high reward (the plugin
>> is not enabled by default). I believe that code is in good shape (I
>> remember +2 it at some point) and would very much like to see this in.
>>
>> Serg, do you have any objections?
>>
>> --
>> Kirill Zaitsev
>> Software Engineer
>> Mirantis, Inc
>>
>> On 14 March 2016 at 11:55:46, Madhuri (madhuri.ra...@gmail.com) wrote:
>>
>> Hi All,
>>
>> I would like to request a feature freeze exception for "Magnum/Murano
>> rationalization" [1], Magnum app to deploy Kubernetes/Mesos/Swarm cluster.
>> The patch is on review[2].
>> I am looking for your decision about considering this change for a FFE.
>>
>> [1]
>> https://blueprints.launchpad.net/murano/+spec/magnum-murano-rationalization
>> [2] https://review.openstack.org/#/c/269250/
>>
>> Regards,
>> Madhuri
>> __
>>
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] PTL Noncandidacy

2016-03-11 Thread Serg Melikyan

I would like to announce that I am not going to run for Murano PTL this
release cycle. I was the official Murano PTL for the past two cycles and I
feel that it's time for me to pass this role to someone new and more
energetic.

In this e-mail I want to reflect on some changes in community activity
around Murano project that happened in the last few cycles.

Murano started as a one company contribution and that can be easily seen at
stackalytics.org. But I'm happy that this is changing, the number of
commits from non-Mirantis engineers grew from 15% in Kilo [0], to 25% in
Liberty [1], and to 39% in Mitaka [2]. Which means that since the last year
the relative contribution from other companies has more than doubled.

I am very proud of this numbers but not for myself. Kirill Zaitsev is the
person behind this achievement.

He was very active on IRC, helping people step-by-step in their
contribution and encouraging them along the way. He also was the top
reviewer in this cycle with 754 (22% of total) reviews for Murano [3]. He
was participating as a mentor in Outreachy program, mentoring and helping
people to participate in open source development. He was doing all of that
while contributing considerable amount of changes to Murano and other
projects.

Kirill,

Thank you for everything you did for the team and for helping me to lead
the project more than you can imagine. I am waiting for your
self-nomination ;)

References:
[0] http://stackalytics.com/?module=murano-group&release=kilo&metric=commits
[1]
http://stackalytics.com/?module=murano-group&release=liberty&metric=commits
[2]
http://stackalytics.com/?module=murano-group&release=mitaka&metric=commits
[3] http://stackalytics.com/?module=murano-group&release=mitaka&metric=marks

-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

2016-03-09 Thread Serg Melikyan

>This is exactly my first thought. The plugins *must* depend on Horizon, and 
>they have to use the same versions of XStatic packages anyways, so why specify 
>the dependencies twice?

Plugins may require different xstatic library, which is not even used
by Horizon. Issue raised by Richard exists for plugins too, not only
for Horizon itself.


On Wed, Mar 9, 2016 at 12:24 AM, Radomir Dopieralski
 wrote:
> On 03/08/2016 11:43 PM, David Lyle wrote:
>
>> I'm wondering if since horizon is really the only project consuming
>> these xstatic libraries and none are likely to venture down this path of
>> madness with us that it would be safe to manage the xstatic requirements
>> and upper-constraints locally.
>>
>> Technically the plugins for horizon depend on this, but they depend via
>> horizon. If they require specific versions that are not supported by
>> Horizon, I think all bets are off anyway.
>
>
> This is exactly my first thought. The plugins *must* depend on Horizon,
> and they have to use the same versions of XStatic packages anyways, so
> why specify the dependencies twice? If the changes between versions are
> so big as to be breaking, then the plugins have to be updated to work
> with the new Horizon anyways.
>
> --
> Radomir Dopieralski
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+1 (650) 440-8979

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] Cancelling Team Meeting

2016-03-07 Thread Serg Melikyan

Meeting tomorrow, March 7, is canceled since a number of team members
are on holidays.

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] [FFE] Support TOSCA definitions for applications

2016-03-07 Thread Serg Melikyan

I have no objection regarding granting this FFE.

This feature is developed as a plugin for Murano, placed in contrib
folder and is not going to affect our main codebase in any way, so I
am pretty sure that it's safe to grant this FFE.

If there are not objections, I propose to consider FFE granted.

On Thu, Mar 3, 2016 at 9:46 AM, Tetiana Lashchova
 wrote:
> Hi all,
>
> I would like to request a feature freeze exception for "Support TOSCA
> definitions for applications" [1].
> The spec is already merged [2], patch is on review [3] and the task is
> almost finished.
> I am looking forward for your decision about considering this change for a
> FFE.
>
> [1] https://blueprints.launchpad.net/murano/+spec/support-tosca-format
> [2] https://review.openstack.org/#/c/194422/
> [3] https://review.openstack.org/#/c/243872/
>
> Thanks,
> Tetiana
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][murano][fuel-plugins] Move Murano to plugin from Fuel box

2016-02-26 Thread Serg Melikyan

Igor,

I've discussed this matter with Dmitry Borodaenko, and we agreed that
much better way would be to not remove Murano from Fuel 9.0, but
rather announce it deprecated once we will have a first version of
plugin released. Additionally we can develop plugin in a way that it
will disable checkbox for installing Murano as part of Fuel once
installed on master node.

Aforementioned changes are reflected in corresponding spec:
https://review.openstack.org/275124

>you plan to release Murano plugin between Fuel 9.0 and Fuel 10, so the 
>question is do you plan to support installation of Murano plugin on Fuel 9.0
Yes, we plan to support installation of plugin on Fuel 9.0. Can you
provide more details about what problems do you see with that?

On Thu, Feb 25, 2016 at 3:07 AM, Denis Egorenko  wrote:
> Hey Igor,
>
> We are planing to release Murano plugin with Fuel 9.0. So, after plugin will
> be ready,
> we just disable Murano built in installation. We don't expect to have any
> conflicts, because
> we will use overridden hiera data for plugin and all old serialized Murano
> information will be
> useless.
>
>
> 2016-02-25 13:38 GMT+03:00 Igor Kalnitsky :
>>
>> Hey Denis,
>>
>> I didn't read the spec yet, but want to raise one important question.
>> AFAIU, you plan to release Murano plugin between Fuel 9.0 and Fuel 10,
>> so the question is do you plan to support installation of Murano
>> plugin on Fuel 9.0? If so, that might be a problem.
>>
>> Thanks,
>> - Igor
>>
>> On Wed, Feb 24, 2016 at 6:30 PM, Denis Egorenko 
>> wrote:
>> > Hello folks,
>> >
>> > i would like to notify you, that we are going to remove Murano as built
>> > in
>> > Fuel and move this functionality to fuel-plugin.
>> >
>> > Transition from Fuel built in to Fuel plugin deployment will follow next
>> > way:
>> >
>> > * Murano deployment in Fuel 9.0 will be deprecated: we leave an ability
>> > to
>> > deploy it,
>> >   keeping puppet manifests for Murano in fuel-library, keeping UI
>> > settings
>> >   untill plugin will be prepared and tested;
>> >
>> > * Once plugin is ready, Fuel 9.0 deployment from built in Murano will
>> >   forbidden. All Murano codebase will be removed from Fuel in next
>> > release.
>> >
>> > Since Murano will be a plugin, it will have his own development cycle,
>> > differ from Fuel releases.
>> >
>> > There is specification for this activity [1]. Any feedback is welcome.
>> >
>> > [1] https://review.openstack.org/275124
>> >
>> > --
>> > Best Regards,
>> > Egorenko Denis,
>> > Senior Deployment Engineer
>> > Mirantis
>> >
>> >
>> > __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> Best Regards,
> Egorenko Denis,
> Senior Deployment Engineer
> Mirantis
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Nominate Victor Ryzhenkin to Murano Core

2016-01-28 Thread Serg Melikyan

Victor, welcome!

On Thu, Jan 28, 2016 at 5:57 AM, Kirill Zaitsev  wrote:
>
> +1 from me. Victor’s continued work on keeping our gates green and stable is 
> invaluable. His contribution during M cycle is also very impressive. Looking 
> forward to seeing him one of the cores.
>
> --
> Kirill Zaitsev
> Murano team
> Software Engineer
> Mirantis, Inc
>
> On 27 January 2016 at 01:10:18, Stan Lagun (sla...@mirantis.com) wrote:
>
> +1!
> Well deserved!
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
>
> On Tue, Jan 26, 2016 at 5:20 AM, Yang, Lin A  wrote:
> > Glad to see this happened. :)
> > Well deserved, Victor.
> >
> > Lin Yang
> > @Intel
> >
> >> On Jan 23, 2016, at 01:33, Serg Melikyan  wrote:
> >>
> >> I would like to nominate Victor Ryzhenkin (freerunner on IRC) join to the 
> >> Murano
> >> core-reviewers team. He has been an active member of the Murano team
> >> for some time now. You can check his review activity report here:
> >> http://stackalytics.com/report/contribution/murano-group/90
> >>
> >> Team please vote for this change in reply to this message.
> >> --
> >> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
> >> http://mirantis.com | smelik...@mirantis.com
> >>
> >> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] Nominate Victor Ryzhenkin to Murano Core

2016-01-22 Thread Serg Melikyan

I would like to nominate Victor Ryzhenkin (freerunner on IRC) join to the Murano
core-reviewers team. He has been an active member of the Murano team
for some time now. You can check his review activity report here:
http://stackalytics.com/report/contribution/murano-group/90

Team please vote for this change in reply to this message.
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] Nominate Rong Zhu to Murano Core

2016-01-22 Thread Serg Melikyan

I would like to nominate Rong Zhu (zhurong on IRC) join to the Murano
core-reviewers team. He has been an active member of the Murano team
for some time now. You can check his review activity report here:
http://stackalytics.com/report/contribution/murano-group/90

Team please vote for this change in reply to this message.

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Next two meetings are canceled

2015-12-29 Thread Serg Melikyan

Folks, due to long holidays in Europe, especially in Russia, we
decided to cancel today's and next weekly meeting.

Our next meetings will be held on January 12.

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

2015-11-25 Thread Serg Melikyan

;> attributes = helpers.evaluate(self.application, self.context)
>>   File 
>> "/home/stack/project/murano-dashboard/muranodashboard/dynamic_ui/helpers.py",
>>  line 97, in evaluate
>> value, context)
>>   File 
>> "/home/stack/project/murano-dashboard/muranodashboard/dynamic_ui/helpers.py",
>>  line 90, in recursive_apply
>> return rec(value)
>>   File 
>> "/home/stack/project/murano-dashboard/muranodashboard/dynamic_ui/helpers.py",
>>  line 80, in rec
>> return dict((rec(k), rec(v)) for (k, v) in val.iteritems())
>>   File 
>> "/home/stack/project/murano-dashboard/muranodashboard/dynamic_ui/helpers.py",
>>  line 80, in 
>> return dict((rec(k), rec(v)) for (k, v) in val.iteritems())
>>   File 
>> "/home/stack/project/murano-dashboard/muranodashboard/dynamic_ui/helpers.py",
>>  line 78, in rec
>> return rec(transformer(val, *args))
>>   File 
>> "/home/stack/project/murano-dashboard/muranodashboard/dynamic_ui/helpers.py",
>>  line 96, in 
>> lambda v, _ctx: v.evaluate(context=_ctx),
>>   File 
>> "/home/stack/project/murano-dashboard/muranodashboard/dynamic_ui/yaql_expression.py",
>>  line 61, in evaluate
>> return self._parsed_expression.evaluate(data=data, context=context)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/expressions.py",
>>  line 165, in evaluate
>> return self(utils.NO_VALUE, context, self.engine)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/expressions.py",
>>  line 156, in __call__
>> return super(Statement, self).__call__(receiver, context, engine)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/expressions.py",
>>  line 37, in __call__
>> return context(self.name, engine, receiver, context)(*self.args)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/contexts.py",
>>  line 65, in 
>> data_context, use_convention, function_filter)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/runner.py",
>>  line 49, in call
>> name, all_overloads, engine, receiver, data_context, args, kwargs)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/runner.py",
>>  line 117, in choose_overload
>> args = tuple(arg_evaluator(i, arg) for i, arg in enumerate(args))
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/runner.py",
>>  line 117, in 
>> args = tuple(arg_evaluator(i, arg) for i, arg in enumerate(args))
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/runner.py",
>>  line 113, in 
>> and not isinstance(arg, expressions.Constant))
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/expressions.py",
>>  line 37, in __call__
>> return context(self.name, engine, receiver, context)(*self.args)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/contexts.py",
>>  line 65, in 
>> data_context, use_convention, function_filter)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/runner.py",
>>  line 49, in call
>> name, all_overloads, engine, receiver, data_context, args, kwargs)
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/runner.py",
>>  line 141, in choose_overload
>> raise_not_found()
>>   File 
>> "/home/stack/project/horizon/.tox/venv/local/lib/python2.7/site-packages/yaql/language/runner.py",
>>  line 70, in raise_not_found
>> raise exceptions.NoMatchingFunctionException(name)
>> NoMatchingFunctionException: No function "#operator_." matches supplied 
>> arguments
>> [25/Nov/2015 01:31:17] "POST 
>> /murano/catalog/add/914c2bfd5d504419a94a9affb7af809a/b8d83a0b6fde465ab9de013f084518d4/False/False
>>  HTTP/1.1" 500 119882
>>
>>
>> In order to test this further I tried to make a copy of the hot_package and 
>> create a HOT2 plugin (by renaming Hot to Hot2) to see if the issue is 
>> directly rooted in the CSAR plugin.
>> However, with the HOT2 plugin I am getting the same error as above.
>>
>> Any help on how to resolve the problem is very much appreciated.
>>
>> Regards,
>> --Vahid
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [app-catalog] [glance] [murano] Data Assets API for App Catalog

2015-10-16 Thread Serg Melikyan

ild trees
> of artifact repos in different clouds. The top node of that tree is some
> Global Application Catalog (and the apps.openstack.org may be this global
> catalog - if it is glance-based or at least supports glance v3 federation),
> then there are repositories of particular openstack vendors or distributors,
> then - the catalogs of enterprises operating different openstack clouds. The
> particular glance deployments in that clouds are the leafs of that tree,
> being able to search for data assets in all the upstream repositories,
> download them from there or - if permitted - submit their local assets back
> upstream. This will be the ultimate network for application delivery and
> exchange in openstack world - and this is one of the main reasons we’ve
> began the Artifacts initiative in Glance.
>
> Unlike other aforementioned features this one is not implemented yet, but we
> are planning to add it as soon as we are done with API stabilization goal.
>
>
>
>
>
> There are many other features which are present in V3’s roadmap and may be
> useful for the app catalog, such as ability to sign artifacts with their
> developers’ keys and verify that keys on usage to ensure the authenticity of
> the artifact.
>
>
>
> What we don’t have right now is the ability to associate ratings (“stars”)
> and comments to the artifact, as well as aggregating different usage and
> download statistics: such features are really needed only for the public
> website such as apps.o.o but are not required for Glance’s in particular
> clouds. But we may find some way to solve this, either by wrapping glance
> API with additional middleware which would add appropriate info from a
> different data source, or by having custom plugins which are able to do
> that, or in some other way: I am sure we may find a solution for this.
>
>
>
> So, this was just a brief description of what Glance v3 has to offer as a
> backend for App Catalog API.
>
> It also worths to mention that this API is in “EXPERIMENTAL” state right
> now, which means that it is not fixed and we may modify it significantly if
> there is a need to. So we may work closer together to adopt it for the needs
> of Community App Catalog.
>
>
>
> I would really prefer to not create any overlaps between Glance v3 and the
> community app catalog: if the app catalog builds its own incompatible
> implementation of assets discovery and distribution API then we’ll have a
> huge duplication of efforts for developers and lots of confusion to the
> end-users who will get two entirely different ways to do the same task.
>
>
>
> So, I’d propose to discuss these potential overlaps, look at the features
> need by App Catalog and see how Glance V3 may be of use here. I’ll be more
> than happy to help with that. We can dive deeper into the details here in
> the mailing list or meet in person in Tokyo. I'll try to have a
> demonstratable prototype by that time.
>
>
>
> --
>
> Regards,
> Alexander Tivelkov
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] py26 support in python-muranoclient

2015-10-09 Thread Serg Melikyan

Hi Vahid,

unfortunately we don't plan to remove support for py26 from the
python-muranoclient, most of the python-client support py26
in order to work out of the box on different OS including CentOS 6.5
and so on.

>So the options are:
>1. support py26 in tosca-parser

Support for py26 is pretty easy to implement, there are only few
things which are not available in py26 and available in py27. In our
case it was few places where we used {1, 2, 3} instead of set([1, 2,
3]).

On Thu, Oct 8, 2015 at 11:59 PM, Vahid S Hashemian
 wrote:
> Hello,
>
> I am wondering if there is any near-term plan for removing the py26 support
> from the client project (python-muranoclient).
> For the tosca support blueprint python-muranoclient will become dependent on
> tosca-parser project and expect tosca-parser to support py26 (it currently
> does not support py26).
>
> So the options are:
> 1. support py26 in tosca-parser
> 2. wait until py26 support is phased out in python-muranoclient (only if
> it's happening soon)
>
> Thanks.
> -
> Vahid Hashemian, Ph.D.
> Advisory Software Engineer, IBM Cloud
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] [app-catalog] versions for murano assets in the catalog

2015-09-22 Thread Serg Melikyan

Hi Chris,

concern regarding assets versioning in Community App Catalog indeed
affects Murano because we are constantly improving our language and
adding new features, e.g. we added ability to select existing Neutron
network for particular application in Liberty and if user wants to use
this feature - his application will be incompatible with Kilo. I think
this also valid for Heat because they HOT language is also improving
with each release.

Thank you for proposing workaround, I think this is a good way to
solve immediate blocker while Community App Catalog team is working on
resolving handling versions elegantly from they side. Kirill proposed
two changes in Murano to follow this approach that I've already +2 ed:

* https://review.openstack.org/225251 - openstack/murano-dashboard
* https://review.openstack.org/225249 - openstack/python-muranoclient

Looks like corresponding commit to Community App Catalog is already
merged [0] and our next step is to prepare new version of applications
from openstack/murano-apps and then figure out how to publish them
properly.

P.S. I've also talked with Alexander and Kirill regarding better ways
to handle versioning for assets in Community App Catalog and they
shared that they are starting working on PoC using Glance Artifact
Repository, probably they can share more details regarding this work
here. We would be happy to work on this together given that in Liberty
we implemented experimental support for package versioning inside the
Murano (e.g. having two version of the same app working side-by-side)
[1]

References:
[0] https://review.openstack.org/224869
[1] 
http://murano-specs.readthedocs.org/en/latest/specs/liberty/murano-versioning.html

On Thu, Sep 17, 2015 at 11:00 PM, Christopher Aedo  wrote:
> One big thing missing from the App Catalog right now is the ability to
> version assets.  This is especially obvious with the Murano assets
> which have some version/release dependencies.  Ideally an app-catalog
> user would be able to pick an older version (ie "works with kilo
> rather than liberty"), but we don't have that functionality yet.
>
> We are working on resolving handling versions elegantly from the App
> Catalog side but in the short term we believe Murano is going to need
> a workaround.  In order to support multiple entries with the same name
> (i.e. Apache Tomcat package for both Kilo and Liberty) we are
> proposing the Liberty release of Murano have a new default URL, like:
>
> MURANO_REPO_URL="http://apps.openstack.org/api/v1/murano_repo/liberty/";
>
> We have a patch ready [1] which would redirect traffic hitting that
> URL to http://storage.apps.openstack.org.  If we take this approach,
> we will then retain the ability to manage where Murano fetches things
> from without requiring clients of the Liberty-Murano release to do
> anything.  For instance, if there is a need for Liberty versions of
> Murano packages to be different from Kilo, we could set up a
> Liberty-specific directory and put those versions there, and then
> adjust the redirect appropriately.
>
> What do you think?  We definitely need feedback here, otherwise we are
> likely to break things Murano relies on.  kzaitsev is active on IRC
> and was the one who highlighted this issue, but if there are other
> compatibility or version concerns as Murano continues to grow and
> improve, we could use one or two more people from Murano to stay in
> touch with us wherever you intersect with the App Catalog so we don't
> break something for you :)
>
> [1] https://review.openstack.org/#/c/224869/
>
> -Christopher
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet] monasca,murano,mistral governance

2015-09-15 Thread Serg Melikyan

cribe
>> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> --
>> Thanks, Ivan Berezovskiy
>> MOS Puppet Team Lead
>> at Mirantis <https://www.mirantis.com/>
>>
>> slack: iberezovskiy
>> skype: bouhforever
>> phone: + 7-960-343-42-46
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> --
> Emilien Macchi
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] PTL Candidacy

2015-09-13 Thread Serg Melikyan

I'd like to continue handling PTL responsibilities for Murano [1] in
the Mitaka cycle.

I would like to apologize for not being able to focus on my
responsibilities in Liberty for full-time. In Mitaka being PTL going
to be my full-time job and I feel that it will allow me to finally
archive my dream of building great community around our project.

In Liberty we increased community diversity [2] [3], but it is only
beginning of the journey which I would like to carry on with your
support.

[1] http://wiki.openstack.org/wiki/Murano
[2] http://stackalytics.com/?release=kilo&module=murano-group&metric=commits
[3] http://stackalytics.com/?release=liberty&module=murano-group&metric=commits

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

2015-09-08 Thread Serg Melikyan

Nikolai, my congratulations!

On Tue, Sep 8, 2015 at 5:28 AM, Stan Lagun  wrote:

> +1
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
> 
>
> On Tue, Sep 1, 2015 at 3:03 PM, Alexander Tivelkov  > wrote:
>
>> +1. Well deserved.
>>
>> --
>> Regards,
>> Alexander Tivelkov
>>
>> On Tue, Sep 1, 2015 at 2:47 PM, Victor Ryzhenkin > > wrote:
>>
>>> +1 from me ;)
>>>
>>> --
>>> Victor Ryzhenkin
>>> Junior QA Engeneer
>>> freerunner on #freenode
>>>
>>> Включено 1 сентября 2015 г. в 12:18:19, Ekaterina Chernova (
>>> efedor...@mirantis.com) написал:
>>>
>>> +1
>>>
>>> On Tue, Sep 1, 2015 at 10:03 AM, Dmitro Dovbii 
>>> wrote:
>>>
>>>> +1
>>>>
>>>> 2015-09-01 2:24 GMT+03:00 Serg Melikyan :
>>>>
>>>>> +1
>>>>>
>>>>> On Mon, Aug 31, 2015 at 3:45 PM, Kirill Zaitsev >>>> > wrote:
>>>>>
>>>>>> I’m pleased to nominate Nikolai for Murano core.
>>>>>>
>>>>>> He’s been actively participating in development of murano during
>>>>>> liberty and is among top5 contributors during last 90 days. He’s also
>>>>>> leading the CloudFoundry integration initiative.
>>>>>>
>>>>>> Here are some useful links:
>>>>>>
>>>>>> Overall contribution: http://stackalytics.com/?user_id=starodubcevna
>>>>>> List of reviews:
>>>>>> https://review.openstack.org/#/q/reviewer:%22Nikolay+Starodubtsev%22,n,z
>>>>>> Murano contribution during latest 90 days
>>>>>> http://stackalytics.com/report/contribution/murano/90
>>>>>>
>>>>>> Please vote with +1/-1 for approval/objections
>>>>>>
>>>>>> --
>>>>>> Kirill Zaitsev
>>>>>> Murano team
>>>>>> Software Engineer
>>>>>> 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/listinfo/openstack-dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>>>>> http://mirantis.com | smelik...@mirantis.com
>>>>>
>>>>> +7 (495) 640-4904, 0261
>>>>> +7 (903) 156-0836
>>>>>
>>>>>
>>>>> __
>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>> Unsubscribe:
>>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> __
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>> __
>>>
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

2015-08-31 Thread Serg Melikyan

+1

On Mon, Aug 31, 2015 at 3:45 PM, Kirill Zaitsev 
wrote:

> I’m pleased to nominate Nikolai for Murano core.
>
> He’s been actively participating in development of murano during liberty
> and is among top5 contributors during last 90 days. He’s also leading the
> CloudFoundry integration initiative.
>
> Here are some useful links:
>
> Overall contribution: http://stackalytics.com/?user_id=starodubcevna
> List of reviews:
> https://review.openstack.org/#/q/reviewer:%22Nikolay+Starodubtsev%22,n,z
> Murano contribution during latest 90 days
> http://stackalytics.com/report/contribution/murano/90
>
> Please vote with +1/-1 for approval/objections
>
> --
> Kirill Zaitsev
> Murano team
> Software Engineer
> 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/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Weekly Meeting on Sep 1

2015-08-31 Thread Serg Melikyan

Hi folks,

I want to let you know that I would not be able to chair tomorrow's weekly
meeting, Nikolai Starodubtsev is going to temporary replace me on this
meeting.

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Mistral][Murano] What's the latest/greatest on YAQL?

2015-06-30 Thread Serg Melikyan

Hi Dmitri,

We share your concerns and migration to the new YAQL is our priority too.
Regarding estimates, I would say month in a worst case.

On Tue, Jun 30, 2015 at 8:09 AM, Dmitri Zimine 
wrote:

> Thanks Stan,
>
> This release is few more months. How soon?  Are you planning to support
> 0.2 in the meantime?
>
> We are really pressed on this transition to 1.0.
> For instance. Number 1 user error while dealing with YAQL is using ==
> instead of =.
> We had this discussion and you and Alex and you suggested it’s easy to
> redefine.
>
> But… … The short is we need to move to 1.0 to do it. Because from what I
> figured so far, in 0.2 I can’t naively extend the an operator, as it won’t
> parse. I did make it work on 0.2 but this required a hack in the YAQL
> library itself, need to add ‘==‘ to both lexer.py and parser.py. At least
> what I figured.
>
> I see the tokens are already generalized in 1.0. It doesn’t seem to worth
> backporting it to 0.2, but if this is a way, let us know.
>
> Mistral is betting on YAQL, please help.
>
> DZ.
>
> On Jun 26, 2015, at 2:20 AM, Stan Lagun  wrote:
>
> The plan is to move to yaql 1.0 this release.  Please do not merge yaql
> 1.0 into Mistral yet. Migration is going to happen really soon
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
> 
>
> On Fri, Jun 26, 2015 at 8:17 AM, Renat Akhmerov 
> wrote:
>
>> Yes, it’s a pretty important thing that we’d like to clarify as soon as
>> possible.
>>
>> Any input from Murano team?
>>
>> Renat Akhmerov
>> @ Mirantis Inc.
>>
>>
>>
>> > On 26 Jun 2015, at 06:01, Dmitri Zimine  wrote:
>> >
>> > Folks,
>> >
>> > it’s been some time,what’s the news:
>> >
>> > * Is Murano moving YAQL 1.0 in this cycle?
>> > * What’s your recommendation for this cycle - stay on 0.2.6 or move on?
>> > * Any progress on documentation?
>> >
>> > Thanks, DZ>
>> >
>> >
>> >
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe>
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet][murano] Developing puppet module for Murano

2015-06-17 Thread Serg Melikyan

Emilien,

Thank you for your proposal, I completely agree with it:

> * Move the module under the big tent
Proposed change in infra [1] and corresponding change in governance [2]

> * Adding Puppet OpenStack group part of core permissions
I've added puppet-manager-core to puppet-murano-core

> * Keep Puppet Murano folks part of core permissions for now
I've added Denis Egorenko to puppet-murano-core (group was empty previously).

> * Do not merge a patch without at least one review from both groups
> * Collaborate to make the module compliant
Denis will be responsible for initial review from Murano side in order
to not overburden OpenStack Puppet with helping with Puppet basics. We
will make sure to not merge anything without +2 from someone from
puppet-manager-core. We will start with basic repository structure and
will move existing module bit by bit.

> * When the module is compliant, we only keep Puppet OpenStack
>   group managing the module, like it's done for other modules.
Sure!

Once again thank you for your help and concerns!

References:
[1] https://review.openstack.org/192730
[2] https://review.openstack.org/192727

On Wed, Jun 17, 2015 at 5:03 PM, Emilien Macchi  wrote:
>
>
> On 06/17/2015 09:50 AM, Serg Melikyan wrote:
>> Thank you for sharing link to list of things that new module should
>> satisfy to! It will be really helpful even if list will change over
>> time. At least we have pointers how to start making our module
>> compliant.
>>
>> Regarding figuring out permissions - I don't mind if we will set
>> puppet-core as group responsible for the repository, I believe that
>> through contributing Murano module authors will get enough
>> creditability to be included to the puppet-core. This will help to
>> ensure that module is developed according all rules of Puppet
>> OpenStack Community and nothing will be merged that does not satisfy
>> adopted way of doing things. Emilien, if you agree with this approach
>> I will send appropriate change to review.
>>
>
> I like Monty's proposal.
>
> I propose:
> * Move the module under the big tent
> * Adding Puppet OpenStack group part of core permissions
> * Keep Puppet Murano folks part of core permissions for now
> * Do not merge a patch without at least one review from both groups
> * Collaborate to make the module compliant
> * When the module is compliant, we only keep Puppet OpenStack group
> managing the module, like it's done for other modules.
>
>>
>>
>>
>>
>> On Wed, Jun 17, 2015 at 4:08 PM, Monty Taylor  wrote:
>> On 06/17/2015 08:53 AM, Emilien Macchi wrote:
>>>>> Hi Serg,
>>>>>
>>>>> On 06/17/2015 05:35 AM, Serg Melikyan wrote:
>>>>>> Hi Emilien,
>>>>>>
>>>>>> I would like to answer your question regarding
>>>>>> stackforge/puppet-murano repository asked in different thread:
>>>>>>
>>>>>>> Someone from Fuel team created first the module in Fuel, 6
>>>>>>> months ago [1] and 3 months later someone from Fuel team
>>>>>>> created an empty repository in Stackforge [2]. By the way,
>>>>>>> Puppet OpenStack community does not have core permissions on
>>>>>>> this module and it's own by Murano team.
>>>>>>
>>>>>> Murano was included to Fuel around 2 years ago, our first
>>>>>> official release as part of Fuel was Icehouse - yes, we have
>>>>>> puppet module for Murano for a long time now. But until recently
>>>>>> we didn't had a Big Tent in place and that is why we never
>>>>>> thought that we able to upstream our module.
>>>>>>
>>>>>> Once policy regarding upstream puppet modules in Fuel changed and
>>>>>> Big Tent model was adopted we decided to upstream module for
>>>>>> Murano. I am really sorry that I didn't contact you for more
>>>>>> information how to do that properly and just created
>>>>>> corresponding repository.
>>>>>
>>>>> Well, in fact, I'm sorry for you; you could not benefit of Puppet
>>>>> OpenStack community. Let's fix that.
>>>>>
>>>>>> I didn't give permission to Puppet OpenStack community for this
>>>>>> repository because it would be strange, given I didn't even
>>>>>> contact you. We thought that we would upstream what we have now
>>>>>> and then make sure that this repo will be integr

Re: [openstack-dev] [puppet][murano] Developing puppet module for Murano

2015-06-17 Thread Serg Melikyan

Thank you for sharing link to list of things that new module should
satisfy to! It will be really helpful even if list will change over
time. At least we have pointers how to start making our module
compliant.

Regarding figuring out permissions - I don't mind if we will set
puppet-core as group responsible for the repository, I believe that
through contributing Murano module authors will get enough
creditability to be included to the puppet-core. This will help to
ensure that module is developed according all rules of Puppet
OpenStack Community and nothing will be merged that does not satisfy
adopted way of doing things. Emilien, if you agree with this approach
I will send appropriate change to review.






On Wed, Jun 17, 2015 at 4:08 PM, Monty Taylor  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 06/17/2015 08:53 AM, Emilien Macchi wrote:
>> Hi Serg,
>>
>> On 06/17/2015 05:35 AM, Serg Melikyan wrote:
>>> Hi Emilien,
>>>
>>> I would like to answer your question regarding
>>> stackforge/puppet-murano repository asked in different thread:
>>>
>>>> Someone from Fuel team created first the module in Fuel, 6
>>>> months ago [1] and 3 months later someone from Fuel team
>>>> created an empty repository in Stackforge [2]. By the way,
>>>> Puppet OpenStack community does not have core permissions on
>>>> this module and it's own by Murano team.
>>>
>>> Murano was included to Fuel around 2 years ago, our first
>>> official release as part of Fuel was Icehouse - yes, we have
>>> puppet module for Murano for a long time now. But until recently
>>> we didn't had a Big Tent in place and that is why we never
>>> thought that we able to upstream our module.
>>>
>>> Once policy regarding upstream puppet modules in Fuel changed and
>>> Big Tent model was adopted we decided to upstream module for
>>> Murano. I am really sorry that I didn't contact you for more
>>> information how to do that properly and just created
>>> corresponding repository.
>>
>> Well, in fact, I'm sorry for you; you could not benefit of Puppet
>> OpenStack community. Let's fix that.
>>
>>> I didn't give permission to Puppet OpenStack community for this
>>> repository because it would be strange, given I didn't even
>>> contact you. We thought that we would upstream what we have now
>>> and then make sure that this repo will be integrated with Puppet
>>> OpenStack ecosystem.
>>>
>>> We still have big desire to upstream our puppet module. Fuel is
>>> not only user of this module, there are other projects who would
>>> like to use Murano as part of they solution and use puppet module
>>> from Fuel for deployment.
>>>
>>> Can you advise how we should proceed further?
>>
>> The more recent patch to add a module in OpenStack is zaqar:
>> https://review.openstack.org/#/c/191942/
>>
>> Two things we need to solve is the fact if you move your module to
>> the big tent: * bring the module compliant (I'm working on a
>> blueprint to explain what is that, but you can already read what we
>> said at the Summit:
>> https://etherpad.openstack.org/p/liberty-summit-design-puppet-compliant
>>
>>
> * figure out Gerrit permissions. If the module is official, it has to be
>> maintained by Puppet OpenStack group, but that would mean you won't
>> be core on it, which is weird to me at this stage. We are facing
>> the same situation with puppet-monasca, (except the module lives in
>> Stackforge for day1).
>>
>
> When we suck sub-projects into infra, we often make the person or team
> who was maintainer on it before it came into infra core on just that -
> with the infra-core team on it as well. For instance:
>
> puppet-murano-core:
>   serg melikyan
>   puppet-core
>
> Or something. Not saying it's the right choice- just that it's the
> pattern we've followed before over in our neck of the woods.
>
>>>
>>> References: [1]
>>> https://github.com/stackforge/fuel-library/tree/master/deployment/puppet/murano/
>>>
>>>
> [2] https://review.openstack.org/155688
>>>
>>
>> Thanks for taking care of that!
>>
>>
>>
>> __
>>
>>
> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org

[openstack-dev] [puppet][murano] Developing puppet module for Murano

2015-06-17 Thread Serg Melikyan

Hi Emilien,

I would like to answer your question regarding
stackforge/puppet-murano repository asked in different thread:

> Someone from Fuel team created first the module in Fuel, 6 months ago
> [1] and 3 months later someone from Fuel team  created an empty
> repository in Stackforge [2]. By the way, Puppet OpenStack community
> does not have core permissions on this module and it's own by Murano team.

Murano was included to Fuel around 2 years ago, our first official
release as part of Fuel was Icehouse - yes, we have puppet module for
Murano for a long time now. But until recently we didn't had a Big
Tent in place and that is why we never thought that we able to
upstream our module.

Once policy regarding upstream puppet modules in Fuel changed and Big
Tent model was adopted we decided to upstream module for Murano. I am
really sorry that I didn't contact you for more information how to do
that properly and just created corresponding repository.

I didn't give permission to Puppet OpenStack community for this
repository because it would be strange, given I didn't even contact
you. We thought that we would upstream what we have now and then make
sure that this repo will be integrated with Puppet OpenStack
ecosystem.

We still have big desire to upstream our puppet module. Fuel is not
only user of this module, there are other projects who would like to
use Murano as part of they solution and use puppet module from Fuel
for deployment.

Can you advise how we should proceed further?

References:
[1] 
https://github.com/stackforge/fuel-library/tree/master/deployment/puppet/murano/
[2] https://review.openstack.org/155688

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] python versions

2015-06-16 Thread Serg Melikyan

Stan, +100500

On Fri, Jun 12, 2015 at 3:13 PM, Stan Lagun  wrote:
>
> I'd rather go with Heat approach (job first) because it makes easier to track 
> what is left to port to Py34 and track progress in this area
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
> On Mon, Jun 8, 2015 at 2:46 PM, Kirill Zaitsev  wrote:
>>
>> I’ve looked into several OS projects, and they first seen to implement py3 
>> support and create a job later. (Except for heat. They already have a 
>> non-voting py34, which seem to fail every time =))
>>
>> I suggest we do the same: first make murano work on py34, then make a py34 
>> job. I’ll file a blueprint shortly.
>>
>> --
>> Kirill Zaitsev
>> Murano team
>> Software Engineer
>> Mirantis, Inc
>>
>> On 2 Jun 2015 at 15:58:17, Serg Melikyan (smelik...@mirantis.com) wrote:
>>
>> Hi Kirill,
>>
>> I agree with Alexander that we should not remove support for python
>> 2.6 in python-muranoclient.
>>
>> Regarding adding python-3 jobs - great idea! But we need to migrate
>> python-muranoclient to yaql 1.0 first and then add python-3 jobs,
>> because previous versions of yaql are not compatible with python-3.
>>
>> On Tue, Jun 2, 2015 at 3:33 PM, Alexander Tivelkov
>>  wrote:
>> > Hi Kirill,
>> >
>> > Client libraries usually have wider range of python requirements, as they
>> > may be run on various kinds of legacy environments, including the ones with
>> > python 2.6. only.
>> > Murano is definitely not the only project in Openstack which still 
>> > maintains
>> > py26 compatibility for its client: nova, glance, cinder and other 
>> > integrated
>> > ones do this.
>> >
>> > So, I would not drop py26 support for client code without any good reasons
>> > to. Are there any significant reasons to do it?
>> > Regarding py3.4 - this is definitely a good idea.
>> >
>> >
>> > --
>> > Regards,
>> > Alexander Tivelkov
>> >
>> > On Tue, Jun 2, 2015 at 3:04 PM, Kirill Zaitsev 
>> > wrote:
>> >>
>> >> It seems that python-muranoclient is the last project from murano-official
>> >> group, that still supports python2.6. Other projects do not have a 2.6
>> >> testing job (correct me if I’m wrong).
>> >>
>> >> Personally I think it’s time to drop support for 2.6 completely, and add
>> >> (at least non-voting) jobs with python3.4 support tests.
>> >> It seems to fit the whole process of moving OS projects towards python 3:
>> >> https://etherpad.openstack.org/p/liberty-cross-project-python3
>> >>
>> >> What do you think? Does anyone have any objections?
>> >>
>> >> --
>> >> Kirill Zaitsev
>> >> Murano team
>> >> Software Engineer
>> >> 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/listinfo/openstack-dev
>> >>
>> >
>> >
>> > __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>>
>>
>> --
>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>> http://mirantis.com | smelik...@mirantis.com
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] shellcheck all .sh scripts in murano-deployment

2015-06-10 Thread Serg Melikyan

Hi Kirill,

+1 from my side, shellcheck + bashate can help to increase quality of CI
scripts.

On Wed, Jun 10, 2015 at 2:19 PM, Igor Yozhikov 
wrote:

> Hi, I'm using shellcheck during automation scripts writing as linter and I
> believe that incorporation of this tool for additional verification in CI
> is good idea.
>
>
> Thanks,
> Igor Yozhikov
> Senior Deployment Engineer
> at Mirantis <http://www.mirantis.com>
> skype: igor.yozhikov
> cellular: +7 901 5331200
> slack: iyozhikov
>
> On Tue, Jun 9, 2015 at 11:52 PM, Dean Troyer  wrote:
>
>> On Tue, Jun 9, 2015 at 2:58 PM, Kirill Zaitsev 
>> wrote:
>>
>>> What would you say about adding a job to murano-deployment, that would
>>> launch shellcheck http://www.shellcheck.net/about.html against all .sh
>>> files?
>>>
>>
>> We looked at shellcheck when the idea for bashate was brewing, frankly
>> the Haskell runtime requirement was a bit of a sticking point for DevStack,
>> I've no idea what that situation is these days.
>>
>> dt
>>
>> --
>>
>> Dean Troyer
>> dtro...@gmail.com
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Virtual Mid-Cycle Summit - Overview Day

2015-06-09 Thread Serg Melikyan

Hi folks,

We discussed [0] previously that we need a some kind of mid-cycle
summit in order to discuss blueprints and feature for Liberty that we
were not able to discuss at the OpenStack Summit in Vancouver
partially due to some contributors were not able to attend and
partially because Summit agenda was really packed.

We agreed that best way to do that is to start with one-day virtual
mid-cycle summit using some video-conference software (WebEx? [1]) and
extend it if needed.

I've created doodle [2] - let's choose date/time for our virtual
mid-cycle summit! Please, propose agenda for mid-cycle summit using
etherpad: https://etherpad.openstack.org/p/murano-liberty-virtual-summit

References:

[0] 
http://eavesdrop.openstack.org/meetings/murano/2015/murano.2015-05-26-17.02.log.html
[1] http://www.webex.com/
[2] http://doodle.com/awyqduy5a94x45zz

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] python-openstackclient support

2015-06-09 Thread Serg Melikyan

Hi Kirill,

It's definitely a great idea, it needs to be verified though AFAIK all
openstack projects are moving to support python-openstackclient. I
think we should file a blueprint around that and start looking at that
on background. I think it will be not a big deal to support
python-openstackclient.

On Thu, Apr 23, 2015 at 3:04 AM, Stan Lagun  wrote:
>
> +1 for the idea though not sure on priority of this since we have so many way 
> more important things to implement in Kilo. I'd say that would be a great 
> contribution if we find someone willing to contribute it :)
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
> On Thu, Apr 23, 2015 at 1:55 AM, Kirill Zaitsev  wrote:
>>
>> Since python-openstackclient is now a part of openstack — I guess it would 
>> be a good idea to support it in murano. It has setuptools-based plugin 
>> system, and it should be fairly easy to add murano commands as plugins to it.
>> BTW, It’s based on cliff and has a terrific completion support (which is 
>> basically why I started looking into the issue in the first place =))
>>
>> What do you think, is it a good idea?
>>
>> --
>> Kirill Zaitsev
>> Sent with Airmail
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Tracking bugs in apps on launchpad

2015-06-08 Thread Serg Melikyan

We originally created https://launchpad.net/murano-applications, and I
misspelled address in my first e-mail, but after I was pointed out to
the mistake I've decided to create new project with URL
https://launchpad.net/murano-apps that correspond to the repository
name.

On Mon, Jun 8, 2015 at 4:01 PM, Serg Melikyan  wrote:
> Hi folks,
>
> We used to track bugs that we have in applications published in
> openstack/murano-apps repository directly on launchpad.net/murano but
> sometimes it's really inconvenient:
>
> * applications are not a part of the murano
> * it's hard to properly prioritize bugs, because critical bug for app is not
> critical at all for murano
>
> We had created murano-apps project on launchpad sometimes ago, but never
> truly used this project. I propose to move existing bugs for applications to
> https://launchpad.net/murano-apps and use this project as place for tracking
> bugs in openstack/murano-apps repository. Folks, what do you think about
> that?
> --
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
> http://mirantis.com | smelik...@mirantis.com



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Tracking bugs in apps on launchpad

2015-06-08 Thread Serg Melikyan

Hi folks,

We used to track bugs that we have in applications published in
openstack/murano-apps repository directly on launchpad.net/murano but
sometimes it's really inconvenient:

* applications are not a part of the murano
* it's hard to properly prioritize bugs, because critical bug for app is
not critical at all for murano

We had created murano-apps project on launchpad sometimes ago, but never
truly used this project. I propose to move existing bugs for applications
to https://launchpad.net/murano-apps and use this project as place for
tracking bugs in openstack/murano-apps repository. Folks, what do you think
about that?
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [app-catalog] Updating existing artifacts on storage.apps.openstack.org

2015-06-08 Thread Serg Melikyan

Hi folks,

We found few issues with images used by murano application and we would
like to update them. What is procedure for updating existing images/apps
hosted on storage.apps.openstack.org?
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-08 Thread Serg Melikyan

Hi Vahid,

You diagrams are perfectly describe what we have now and what we want
to have with TOSCA, I think it's time to start working on
specification!

I've updated corresponding blueprint with new status and assignee:
https://blueprints.launchpad.net/murano/+spec/support-tosca-format


On Fri, Jun 5, 2015 at 3:43 AM, Vahid S Hashemian
 wrote:
>
> I'm attaching two sequence diagrams, one for package creation and import; and 
> the other for environment deployment.
> In each case I compare my understanding of how Murano performs the use case 
> for a HOT template, and how it can perform it for a TOSCA template.
> Please let me know what you think.
>
> Thanks.
>
> Regards,
> -
> Vahid Hashemian, Ph.D.
> Advisory Software Engineer, IBM Cloud Labs
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-04 Thread Serg Melikyan

Hi Vahid,

Your analysis is correct, and integration of heat-translator is as
simple as you described that in your document. It would be really
awesome if you would turn this PDF to the proper specification for the
blueprint.

P.S. Regarding several stack for applications - currently HOT-based
packages create stack per application, and we don't support same level
of composition as we have in murano-pl based packages. This is another
question for improvement.

On Wed, Jun 3, 2015 at 12:44 AM, Georgy Okrokvertskhov
 wrote:
> Hi Vahid,
>
> Thank you for sharing your thoughts.
> I have a questions about application life-cycle if we use TOSCA translator.
> In Murano the main advantage of using HOT format is that we can update Het
> stack with resources as soon as we need to deploy additional application. We
> can dynamically create multi-tier applications with using other apps as a
> building blocks. Imagine Java app on tom of Tomcat (VM1) and PostgreDB
> (VM2).  All three components are three different apps in  the catalog.
> Murano allows you to bring them and deploy together.
>
> Do you think it will be possible to use TOSCA translator for Heat stack
> updates? What we will do if we have two apps with two TOSCA templates like
> Tomcat and Postgre. How we can combine them together?
>
> Thanks
> Gosha
>
> On Tue, Jun 2, 2015 at 12:14 PM, Vahid S Hashemian
>  wrote:
>>
>> This is my what I have so far.
>>
>>
>>
>> Would love to hear feedback on it. Thanks.
>>
>> Regards,
>>
>> -
>> Vahid Hashemian, Ph.D.
>> Advisory Software Engineer, IBM Cloud Labs
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Georgy Okrokvertskhov
> Architect,
> OpenStack Platform Products,
> Mirantis
> http://www.mirantis.com
> Tel. +1 650 963 9828
> Mob. +1 650 996 3284
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Nominating Filip Blaha for murano-core

2015-06-02 Thread Serg Melikyan

Filip, my congratulations! Welcome!

On Tue, Jun 2, 2015 at 5:34 PM, Stan Lagun  wrote:

> +1
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
> 
>
> On Tue, Jun 2, 2015 at 9:25 AM, Serg Melikyan 
> wrote:
>
>> Folks, I'd like to propose Filip Blaha to core members of Murano team.
>>
>> Filip is active member of our community and he maintains a good score
>> as contributor:
>> http://stackalytics.com/report/users/filip-blaha
>>
>> Existing Murano cores, please vote +1/-1 for the addition of Filip to
>> the murano-core.
>> --
>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>> http://mirantis.com | smelik...@mirantis.com
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Nominating Kirill Zaitsev for murano-core

2015-06-02 Thread Serg Melikyan

Kirill, welcome!

On Tue, Jun 2, 2015 at 5:32 PM, Stan Lagun  wrote:

> +1 without any doubt
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
> 
>
> On Tue, Jun 2, 2015 at 10:43 AM, Ekaterina Chernova <
> efedor...@mirantis.com> wrote:
>
>> +1
>>
>> Regards,
>> Kate.
>>
>> On Tue, Jun 2, 2015 at 9:32 AM, Serg Melikyan 
>> wrote:
>>
>>> I'd like to propose Kirill Zaitsev to core members of Murano team.
>>>
>>> Kirill Zaitsev is active member of our community, he implemented
>>> <https://launchpad.net/murano/+milestone/2015.1.0> several blueprint in
>>> Kilo and fixed number of bugs, he maintains a really good score as
>>> contributor:
>>> http://stackalytics.com/report/users/kzaitsev
>>>
>>> Existing Murano cores, please vote +1/-1 for the addition
>>> of Kirill to the murano-core.
>>> --
>>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>>> http://mirantis.com | smelik...@mirantis.com
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] python versions

2015-06-02 Thread Serg Melikyan

Hi Kirill,

I agree with Alexander that we should not remove support for python
2.6 in python-muranoclient.

Regarding adding python-3 jobs - great idea! But we need to migrate
python-muranoclient to yaql 1.0 first and then add python-3 jobs,
because previous versions of yaql are not compatible with python-3.

On Tue, Jun 2, 2015 at 3:33 PM, Alexander Tivelkov
 wrote:
> Hi Kirill,
>
> Client libraries usually have wider range of python requirements, as they
> may be run on various kinds of legacy environments, including the ones with
> python 2.6. only.
> Murano is definitely not the only project in Openstack which still maintains
> py26 compatibility for its client: nova, glance, cinder and other integrated
> ones do this.
>
> So, I would not drop py26 support for client code without any good reasons
> to. Are there any significant reasons to do it?
> Regarding py3.4 - this is definitely a good idea.
>
>
> --
> Regards,
> Alexander Tivelkov
>
> On Tue, Jun 2, 2015 at 3:04 PM, Kirill Zaitsev 
> wrote:
>>
>> It seems that python-muranoclient is the last project from murano-official
>> group, that still supports python2.6. Other projects do not have a 2.6
>> testing job (correct me if I’m wrong).
>>
>> Personally I think it’s time to drop support for 2.6 completely, and add
>> (at least non-voting) jobs with python3.4 support tests.
>> It seems to fit the whole process of moving OS projects towards python 3:
>> https://etherpad.openstack.org/p/liberty-cross-project-python3
>>
>> What do you think? Does anyone have any objections?
>>
>> --
>> Kirill Zaitsev
>> Murano team
>> Software Engineer
>> 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/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-02 Thread Serg Melikyan

I would like to ask community for the help to implement support for
TOSCA in Murano:
https://blueprints.launchpad.net/murano/+spec/support-tosca-format

I was driving this feature and during OpenStack Summit in Paris we
spent good amount of time discussing how we can implement support for
TOSCA with folks from IBM working on TOSCA specification and came-up
with following etherpad:
https://etherpad.openstack.org/p/tosca-in-murano

But unfortunately I was not able to spend enough time on this
blueprint to move it forward to the actual implementation.

If you are interested in having support for TOSCA in Murano and ready
to work on the implementation of this feature, I would be happy to
help you to drive this further.
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Nominating Kirill Zaitsev for murano-core

2015-06-01 Thread Serg Melikyan

I'd like to propose Kirill Zaitsev to core members of Murano team.

Kirill Zaitsev is active member of our community, he implemented
<https://launchpad.net/murano/+milestone/2015.1.0> several blueprint in
Kilo and fixed number of bugs, he maintains a really good score as
contributor:
http://stackalytics.com/report/users/kzaitsev

Existing Murano cores, please vote +1/-1 for the addition of Kirill to the
murano-core.
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Nominating Filip Blaha for murano-core

2015-06-01 Thread Serg Melikyan

Folks, I'd like to propose Filip Blaha to core members of Murano team.

Filip is active member of our community and he maintains a good score
as contributor:
http://stackalytics.com/report/users/filip-blaha

Existing Murano cores, please vote +1/-1 for the addition of Filip to
the murano-core.
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] oslo namespace changes and murano-dashboard

2015-06-01 Thread Serg Melikyan

Hi Doug,

sorry for the late response, I was traveling a little bit after the
summit. I've released python-muranoclient 0.6.0 with requirements
changes made by you.

We use new release policy for libraries, so versions >=0.5.6,<0.6.0
correspond to Kilo release, and >=0.6 correspond to the Liberty:
https://launchpad.net/python-muranoclient/+series

Do we need to make changes in Kilo branch?

On Fri, May 29, 2015 at 10:00 PM, Georgy Okrokvertskhov
 wrote:
> Hi,
>
> We do monitor both IRC and openstack-dev. #murano is our IRC channel. Most
> of the time there are someone who can respond quickly.  Mirantis and
> Telefonica guys are located in Europe so they will respond during US morning
> but not during US day time. HP guys are US based so they can respond more
> quickly in US timezones.
>
> As for the releases, murano-dashboard is installed from master on the gates,
> so it should already be compatible with oslo changes, but python-muranoagent
> is release based and we need to release a new version and upload it to pip
> repository as it is installed via pip.
>
> Thanks
> Gosha
>
> On Fri, May 29, 2015 at 9:34 AM, Jeremy Stanley  wrote:
>>
>> On 2015-05-29 12:28:37 -0400 (-0400), Doug Hellmann wrote:
>> > First, where do you hang out on IRC? I couldn’t find a channel
>> > that looked like it had any population, and there’s nothing
>> > mentioned on https://wiki.openstack.org/wiki/Murano
>> [...]
>>
>>
>> https://wiki.openstack.org/wiki/IRC says it's #murano (though I
>> haven't /joined to see if anyone actually uses it, I would assume
>> they do).
>> --
>> Jeremy Stanley
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> Georgy Okrokvertskhov
> Architect,
> OpenStack Platform Products,
> Mirantis
> http://www.mirantis.com
> Tel. +1 650 963 9828
> Mob. +1 650 996 3284
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Liberty Design Summit: Etherpads

2015-05-12 Thread Serg Melikyan

Hi folks,

Please take a look to our agenda for the Liberty Design Summit [1]
You can find etherpads for all proposed sessions on the wiki [2]

Feel free to propose topics for discussion on the Contributors Meetup
under "Proposed Agenda Items" section in the corresponding etherpad
[3].

References:
[1] http://libertydesignsummit.sched.org/type/design+summit/Murano
[2] https://wiki.openstack.org/wiki/Summit/Liberty/Etherpads#Murano
[3] https://etherpad.openstack.org/p/murano-liberty-contributors-meetup

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] [Murano] Congress devstack installation is failing in murano gate job

2015-04-29 Thread Serg Melikyan

Sean, Filip,

Exact versions of installed libraries may be found here:
http://logs.openstack.org/61/178461/1/check/gate-murano-congress-devstack-dsvm/fa01b8f/logs/pip-freeze.txt.gz

>stevedore==1.4.0

On Wed, Apr 29, 2015 at 4:38 PM, Filip Blaha  wrote:
> sorry I sent wrong link
>
> http://logs.openstack.org/61/178461/1/check/gate-murano-congress-devstack-dsvm/fa01b8f/logs/devstacklog.txt.gz
>
> In this log is :
>
> Successfully installed PyYAML-3.11 argparse-1.3.0 jsonpatch-1.9
> jsonpointer-1.7 oslo.config-1.11.0 pyOpenSSL-0.15.1
> python-cloudfoundryclient-1.0.2 requests-2.6.2 stevedore-1.4.0
>
> Filip
>
>
>
> On 04/29/2015 03:21 PM, Sean Dague wrote:
>
> I just looked at this run (linked in this message) -
> http://logs.openstack.org/04/171504/6/check/gate-murano-congress-devstack-dsvm/3b2d7e1/logs/devstacklog.txt.gz
>
>
> stevedore==1.3.0 is installed, never 1.4
>
> The failure is completely unrelated to anything there -
> http://logs.openstack.org/04/171504/6/check/gate-murano-congress-devstack-dsvm/3b2d7e1/logs/devstacklog.txt.gz#_2015-04-12_14_06_25_237
>
>
>
> On 04/29/2015 09:12 AM, Serg Melikyan wrote:
>
> Hi Filip,
>
> In thirdparty-requirements for stable/kilo python-muranoclient should
> have following version: "python-muranoclient>=0.5.6,<0.6.0". But I am
> not sure that this will fix the issue, since we don't clearly know why
> stevedore==1.4.0 is installed.
>
> I see that python-keystoneclient does not have cap for stevedore in
> stable/kilo, but still not 100% that it is a reason why 1.4.0 is installed.
>
> [1]
> https://github.com/openstack/congress/blob/stable/kilo/thirdparty-requirements.txt#L4
>
> On Wed, Apr 29, 2015 at 3:46 PM, Filip Blaha  <mailto:filip.bl...@hp.com>> wrote:
>
> Hello
>
> We are facing an issue with Congress devstack installation in our
> gate job testing murano-congress integration (policy enforcement)
> [1] .  Congress devstack scripts install stevedore==1.4.0 as a
> dependency of python-muranoclient without specified version [2].
> However heat requirement in stable/kilo is stevedore>=1.3.0,<1.4.0
> so heat engine is unable to start.
>
> Is possible to fix by specifying  murano client version not to be in
> confilct with heat requirements?
>
> [1]
>
> https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/murano.yaml#L42
>
> [2]
>
> https://github.com/openstack/congress/blob/stable/kilo/thirdparty-requirements.txt#L4
>
> <http://logs.openstack.org/04/171504/6/check/gate-murano-congress-devstack-dsvm/3b2d7e1/logs/devstacklog.txt.gz>
> [3]
> https://github.com/openstack/heat/blob/stable/kilo/requirements.txt#L47
>
> Filip
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] [Murano] Congress devstack installation is failing in murano gate job

2015-04-29 Thread Serg Melikyan

Hi Filip,

In thirdparty-requirements for stable/kilo python-muranoclient should have
following version: "python-muranoclient>=0.5.6,<0.6.0". But I am not sure
that this will fix the issue, since we don't clearly know why stevedore==1.4.0
is installed.

I see that python-keystoneclient does not have cap for stevedore in
stable/kilo, but still not 100% that it is a reason why 1.4.0 is installed.

[1]
https://github.com/openstack/congress/blob/stable/kilo/thirdparty-requirements.txt#L4

On Wed, Apr 29, 2015 at 3:46 PM, Filip Blaha  wrote:

>  Hello
>
> We are facing an issue with Congress devstack installation in our gate job
> testing murano-congress integration (policy enforcement) [1] .  Congress
> devstack scripts install stevedore==1.4.0 as a dependency of
> python-muranoclient without specified version [2]. However heat requirement
> in stable/kilo is stevedore>=1.3.0,<1.4.0 so heat engine is unable to
> start.
>
> Is possible to fix by specifying  murano client version not to be in
> confilct with heat requirements?
>
> [1]
> https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/murano.yaml#L42
> [2]
> https://github.com/openstack/congress/blob/stable/kilo/thirdparty-requirements.txt#L4
> 
> [3]
> https://github.com/openstack/heat/blob/stable/kilo/requirements.txt#L47
>
> Filip
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Mistral] [Murano] Mistral devstack installation is failing in murano gate job

2015-04-13 Thread Serg Melikyan

Hi Nikolay & Filip,

indeed, root cause of the issue is that Murano & Mistral use different
version of yaql library. Murano installs yaql 0.2.4 and overrides
1.0.0b2 already installed and expected by Mistral.

We decided that we are not going to switch to the yaql 1.0.0 in Kilo
since we already finished Kilo development and working on bug-fixes
and releasing RC. This gate may be fixed if only Mistral will revert
1.0.0 support in Kilo :'(

Nikolay, what do you think about migrating to YAQL 1.0.0 in the next
release? I know that it was me who proposed Mistral team to adopt yaql
1.0.0, and I am sorry, I didn't realize all consequences of moving
Mistral to yaql 1.0.0 and Murano team living with yaql 0.2.4.

We need to work on packaging and supporting yaql in Ubuntu/CentOS in
order to add this library to the global-requirements and to avoid this
kind of issues in the future.

On Mon, Apr 13, 2015 at 3:58 PM, Nikolay Makhotkin
 wrote:
>>
>> We are facing an issue with Mistral devstack installation in our gate job 
>> testing murano-congress-mistral integration (policy enforcement) [1] . 
>> Mistral devstack scripts are failing with following import error [2]
>
>
> Hi, Filip!
>
> Recently Mistral has moved to new YAQL, and it seems this dependency is 
> missed (yaql 1.0, currently yaql 1.0.0b2)
>
> I think the root of problem is that Murano and Mistral have different yaql 
> versions installed.
>
> --
> Best Regards,
> Nikolay
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Feature Freeze Exceptions

2015-04-07 Thread Serg Melikyan

Hi folks,

Only two days left until RC-1, but few features that were marked as
FFE are still not finished:

1. Migrate to YAQL 1.0 [1]
2. Murano Versioning [2]

Both of these features are moved to Liberty.

References:
[1] https://blueprints.launchpad.net/murano/+spec/migrate-to-yaql-vnext
[2] https://blueprints.launchpad.net/murano/+spec/murano-versioning


On Fri, Mar 20, 2015 at 11:37 PM, Serg Melikyan  wrote:
> Hi, folks!
>
> Today we released third milestone of Kilo release - 2015.1.0b3 [1], in
> this milestone we completed 11 blueprints and fixed 13 bugs. We
> finally completed a number of big features that we were working whole
> cycle: Integration with Congress, Environment Templates and so on.
>
> Release of kilo-3 means that our Feature Freeze kicks in, and we still
> have some features that are not completed yet. Following features are
> marked as Feature Freeze exceptions and will be completed during RC
> cycle:
>
> 1. Support for configuration languages (puppet, chef) [2]
> 2. Migrate to YAQL 1.0 [3]
> 3. Murano Versioning [4]
>
> We also need to finish working on our specifications, cause many
> specifications are still on review, even as features are already
> completed. In this cycle we introduced murano-specs [5] repository in
> experimental mode, but starting from the next cycle we are completely
> migrating to murano-specs model.
>
> P.S. Feature Freeze also means that we are shifting focus from feature
> development to testing Murano as much as possible.
>
> References:
> [1] https://launchpad.net/murano/+milestone/kilo-3
> [2] https://blueprints.launchpad.net/murano/+spec/conf-language-support
> [3] https://blueprints.launchpad.net/murano/+spec/migrate-to-yaql-vnext
> [4] https://blueprints.launchpad.net/murano/+spec/murano-versioning
> [5] http://git.openstack.org/cgit/stackforge/murano-specs/
> --
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
> http://mirantis.com | smelik...@mirantis.com



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0

2015-04-07 Thread Serg Melikyan

Hi Renat & Dmitry

Today we released YAQL 1.0.0b2 and release is available on PyPI, I
think it's better to start migration to YAQL 1.0.0 right now, we don't
expect any major changes, only small bug-fixes that should not affect
your integration. And we will release 1.0.0 before end of Kilo cycle.

On Tue, Apr 7, 2015 at 11:50 AM, Renat Akhmerov  wrote:
> Well, we’ve been ready to switch to YAQL-1.0 for a couple of months. We
> researched it, figured out how our integration would change etc. It’s pretty
> easy to do from our side. So let’s wait for the official YAQL-1.0.X release
> on pypi.
>
> Renat Akhmerov
> @ Mirantis Inc.
>
>
>
> On 07 Apr 2015, at 00:56, Stan Lagun  wrote:
>
> The plan was to integrate YAQL 1.0 into Murano so that we could say it is
> battle-proven, remove "beta" from version and release on PyPI. And then
> probably release v1.0.1 that is YAQL with documentation :)
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
> On Mon, Apr 6, 2015 at 9:44 PM, Dmitri Zimine 
> wrote:
>>
>> Renat,
>>
>> following up on the IRC meeting: I recalled one more item, and registered
>> a blueprint - https://blueprints.launchpad.net/mistral/+spec/yaql-v1-0I
>> think it’s good timing to do it in Kilo if YAQL 1.0 is announced; so I
>> propose it for Kilo-rc1;
>>
>> One question is when YAQL 1.0 is going to move to Pypi? we can get it from
>> github link for some time but ideally should use pypi. Alex, Stan, what’s
>> the plan?
>>
>> DZ.
>>
>>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] PTL Candidacy

2015-04-05 Thread Serg Melikyan

Hi folks,

I'd like to announce my candidacy as PTL for Murano [1].

I was handling PTL responsibilities in this release cycle so far,
after Ruslan Kamaldinov (who was handling them in Juno cycle) hand
over them to me on OpenStack Summit in Paris. I am working on Murano
since it's kick-off two years ago [2][3].

As a PTL of Murano I'll continue my work on making Murano better with
each day and become project of choice for building own Application
Catalogs & Marketplaces for private & public clouds on OpenStack. I
will focus on building great environment for contributors and work on
relationships built around the project itself not only around the
features needed by contributors.

[1] http://wiki.openstack.org/wiki/Murano
[2] http://stackalytics.com/report/contribution/murano/90
[3] 
http://stackalytics.com/?release=kilo&metric=commits&project_type=stackforge&module=murano-group

P.S. I understand that it is strange to see same application to same
position just few weeks after being officially elected, but since
Murano is now part of the Big Tent and in order to comply with the
existing processes we are running Murano PTL Election once again for
Liberty.

http://lists.openstack.org/pipermail/openstack-dev/2015-April/060472.html

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Murano projects pylint job

2015-04-01 Thread Serg Melikyan

Hi Filip,

I think adding pylint job to Murano gates is an awesome idea, have you
checked out how to do this?

On Wed, Apr 1, 2015 at 4:03 PM, Filip Blaha  wrote:

> Hello
>
> I have noticed that some openstack projects [1] use pylint gate job. From
> my point of view it could simplify code reviews even as non-voing job and
> generally it could improve code quality. Some code issues like code
> duplication are not easy to discover during code review so automatic job
> would be helpful. Please let me know your opinion about that.  Thanks
>
> [1] https://review.openstack.org/#/c/164772/
>
> Regards
> Filip
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Roadmap for Liberty (specs & blueprints)

2015-03-26 Thread Serg Melikyan

Hi everyone,

Kilo cycle is almost finished, and we are ready to accept specs &
blueprints for Liberty.

I would like to mention that our experiment with murano-specs is
considered fairly successful, therefore starting from Liberty every
blueprint for a new feature should be proposed with a spec submitted
to murano-specs [1].

In case when some feature that you've proposed to Kilo was not
implemented, but spec was approved, please move your spec to
'specs/liberty' directory and mention in commit message that spec was
already approved.

We are going to start reviewing new features from the next weekly
meeting (March 31, 2015, 17:00 UTC, #openstack-meeting-alt on
FreeNode).

P.S. I would like to encourage you to send e-mail to mailing list if
you would like to discuss some particular feature with community.

Reference:
[1] https://github.com/stackforge/murano-specs

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Announcing Bug-Scrub Day on March 27

2015-03-25 Thread Serg Melikyan

Hi folks,

As we agreed on last community meeting we announce this Friday (March
27) as Bug-Scrub Day. This day would be dedicated for cleaning-up our
bugs in launchpad [1]. By cleaning-up we mean triaging bugs and
assigning them on the next milestone - kilo-rc1.

We encourage you to join us in order to take and fix some bugs in
Murano, help to identify & verify issues, and correctly assign
priorities.

P.S. Bug-Scrub Day is 24h event, in order to span across the globe
with all our contributors, but we expect to have most of the
contributors in #murano channel on FreeNode starting from 9 am UTC.

References:
[1] https://bugs.launchpad.net/murano

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] python-muranoclient 0.5.6 released

2015-03-25 Thread Serg Melikyan

Today we released python-muranoclient 0.5.6 [1], this release includes
fixes for 8 bugs, including 5 high bugs. This version also includes
support for number of a new features introduced in Kilo:

* Murano Repository (blueprint [2], spec [3])
* Environment Template Catalog (blueprint [4], spec [5])
* Category Management (blueprint [4], spec [5])

Changes to increase number of python-muranoclient in requirements.txt
are proposed:

* murano: https://review.openstack.org/167583
* murano-dashboard: https://review.openstack.org/167580

Unfortunately not all PyPI mirrors on OpenStack infrastructure are
synced with official PyPI mirrors, once they will be synced jobs will
become green and change-requests ready to merge.

References:
[1] https://launchpad.net/python-muranoclient/kilo/0.5.6
[2] 
https://blueprints.launchpad.net/murano/+spec/muranoclient-marketplace-support
[3] https://review.openstack.org/161471
[4] https://blueprints.launchpad.net/murano/+spec/environment-template
[5] 
http://murano-specs.readthedocs.org/en/latest/specs/kilo/blueprint-template.html
[6] https://blueprints.launchpad.net/murano/+spec/enable-category-management
[7] https://review.openstack.org/139630
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Murano agent development

2015-03-24 Thread Serg Melikyan

Hi Filip,

Sure, murano-agent is just a python application, you can easily run
this application locally (even in IDE like Pycharm with attached
debugger). To send execution plan to the agent you need to publish
execution plan to specified queue, results also will be published to
the queue.

murano-agent require configuration file for executing, you can build
sample configuration file using following instruction: tox -e
genconfig

Please, take a look at example murano-agent configuration file that
can be used to run it locally:

[DEFAULT]
# set location where obtained execution plans will be stored
storage = /tmp/murano/plans
debug = true
verbose = true

# credentials for rabbitmq
[rabbitmq]
host = localhost
port = 5672
login = guest
password = guest
virtual_host = /

# with this routing key execution plans results will be published
result_routing_key = 
# to this exchange execution plans results will be published
result_exchange = 
# from this queue agent will take exection plans
input_queue = 

On Tue, Mar 24, 2015 at 11:59 AM, Filip Blaha  wrote:
> Hello
>
> I would like to test and debug some new features of murano agent like chef
> recipes.
>
> I would like to know how to develop murano agent? How to test and debug new
> changes in agent code? Creating new image with every change and and test
> deployment on devstack is time-consuming and not very comfortable. Is there
> any shortcut for this development cycle?
>
> Thanks
> Filip
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Feature Freeze Exceptions

2015-03-20 Thread Serg Melikyan

Hi, folks!

Today we released third milestone of Kilo release - 2015.1.0b3 [1], in
this milestone we completed 11 blueprints and fixed 13 bugs. We
finally completed a number of big features that we were working whole
cycle: Integration with Congress, Environment Templates and so on.

Release of kilo-3 means that our Feature Freeze kicks in, and we still
have some features that are not completed yet. Following features are
marked as Feature Freeze exceptions and will be completed during RC
cycle:

1. Support for configuration languages (puppet, chef) [2]
2. Migrate to YAQL 1.0 [3]
3. Murano Versioning [4]

We also need to finish working on our specifications, cause many
specifications are still on review, even as features are already
completed. In this cycle we introduced murano-specs [5] repository in
experimental mode, but starting from the next cycle we are completely
migrating to murano-specs model.

P.S. Feature Freeze also means that we are shifting focus from feature
development to testing Murano as much as possible.

References:
[1] https://launchpad.net/murano/+milestone/kilo-3
[2] https://blueprints.launchpad.net/murano/+spec/conf-language-support
[3] https://blueprints.launchpad.net/murano/+spec/migrate-to-yaql-vnext
[4] https://blueprints.launchpad.net/murano/+spec/murano-versioning
[5] http://git.openstack.org/cgit/stackforge/murano-specs/
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] PTL elections

2015-03-18 Thread Serg Melikyan

Thank you!

On Wed, Mar 18, 2015 at 8:28 AM, Sergey Lukjanov 
wrote:

> The PTL candidacy proposal time frame ended and we have only one candidate.
>
> So, Serg Melikyan, my congratulations!
>
> Results documented in
> https://wiki.openstack.org/wiki/Murano/PTL_Elections_Kilo_Liberty#PTL
>
> On Wed, Mar 11, 2015 at 2:04 AM, Sergey Lukjanov 
> wrote:
>
>> Hi folks,
>>
>> due to the requirement to have officially elected PTL, we're running
>> elections for the Murano PTL for Kilo and Liberty cycles. Schedule
>> and policies are fully aligned with official OpenStack PTLs elections.
>>
>> You can find more info in official elections wiki page [0] and the same
>> page for Murano elections [1], additionally some more info in the past
>> official nominations opening email [2].
>>
>> Timeline:
>>
>> till 05:59 UTC March 17, 2015: Open candidacy to PTL positions
>> March 17, 2015 - 1300 UTC March 24, 2015: PTL elections
>>
>> To announce your candidacy please start a new openstack-dev at
>> lists.openstack.org mailing list thread with the following subject:
>> "[murano] PTL Candidacy".
>>
>> [0] https://wiki.openstack.org/wiki/PTL_Elections_March/April_2014
>> [1] https://wiki.openstack.org/wiki/Murano/PTL_Elections_Kilo_Liberty
>> [2]
>> http://lists.openstack.org/pipermail/openstack-dev/2014-March/031239.html
>>
>> Thank you.
>>
>> --
>> Sincerely yours,
>> Sergey Lukjanov
>> Sahara Technical Lead
>> (OpenStack Data Processing)
>> Principal Software Engineer
>> Mirantis Inc.
>>
>
>
>
> --
> Sincerely yours,
> Sergey Lukjanov
> Sahara Technical Lead
> (OpenStack Data Processing)
> Principal Software Engineer
> 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/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] PTL Candidacy

2015-03-12 Thread Serg Melikyan

Hi folks,

I'd like to announce my candidacy as PTL for Murano [1].

I was handling PTL responsibilities in this release cycle so far,
after Ruslan Kamaldinov (who was handling them in Juno cycle) hand
over them to me on OpenStack Summit in Paris. I am working on Murano
since it's kick-off two years ago [2][3].

As a PTL of Murano I'll continue my work on making Murano better with
each day and become project of choice for building own Application
Catalogs & Marketplaces for private & public clouds on OpenStack. I
will focus on building great environment for contributors and work on
relationships built around the project itself not only around the
features needed by contributors.

[1] http://wiki.openstack.org/wiki/Murano
[2] http://stackalytics.com/report/contribution/murano/90
[3] http://stackalytics.com/?
release=kilo&metric=commits&project_type=stackforge&module=murano-group

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] how can deploy environment with useEnvironmentNerwork=false

2015-03-10 Thread Serg Melikyan

Hi Cheng-Dae,

We are working on improving supported networking schemes, please take
a look on following commits:
* https://review.openstack.org/152643 - Adds ability to join instances
to existing Neutron networks
* https://review.openstack.org/152747 - Configurable environment's
default network config

You also may be found details about current networking in the
following e-mail:
http://lists.openstack.org/pipermail/openstack-dev/2014-September/047111.html

On Mon, Mar 9, 2015 at 4:26 PM, Choe, Cheng-Dae  wrote:
> hi there
>
> In murano when deploy environment useEnvironmentNerwork=true is default.
>
> How can I deploy with useEnvironmentNerwork=true?
>
> I'm currently using sample Apache web server package
>
>
> --
> Choe, Cheng-Dae
> Blog: http://blog.woosum.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [murano] Application Usage Information Tracking

2015-03-10 Thread Serg Melikyan

Hi Darshan,

Unfortunately application usage is not tracked in Murano in any way.
We only have special logging message [1] that can help to organize
tracking of usage using some sort tools for log analysis (e.g.
Logstash).

[1] 
https://github.com/stackforge/murano/blob/73f8368024acc2f79ef4494b1fbfcc3d2452e494/murano/common/server.py#L113

On Tue, Mar 10, 2015 at 2:00 PM, Darshan Mn  wrote:
> Hi everyone,
>
> I would like to know if the application usage information is tracked by the
> murano-agent? If not, how is it done? Is ceilometer used at all, anywhere?
>
> Regards
> Darshan
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Should we run tests on all supported database engines?

2015-03-02 Thread Serg Melikyan

Hi Andrew,

I think we should isolate DB access layer and test this layer extensively
on MySQL & PostgreSQL.

On Mon, Mar 2, 2015 at 6:57 PM, Andrew Pashkin 
wrote:

> There is a bug:
> https://bugs.launchpad.net/murano/+bug/1419743
>
> It's about that search on packages is failing if use Postgres as DB
> backend. The fix is pretty easy there, but how this bug should be
> tested?
>
> I see such options:
> 1) Run all tests for all DBs that we support.
> 2) Run some tests for some DBs.
> 3) Do not test such issues at all.
>
> Do anyone has some thoughts on this?
>
> --
> With kind regards, Andrew Pashkin.
> cell phone - +7 (985) 898 57 59
> Skype - waves_in_fluids
> e-mail - apash...@mirantis.com
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Translation usage suggestion

2015-02-09 Thread Serg Melikyan

I think all proposed actions make sense, and I strongly agree that we need
to start working on them and finish them in Kilo cycle scope.

On Thu, Feb 5, 2015 at 3:49 PM, Ekaterina Chernova 
wrote:

> Hi all!
>
> Recently we have discussed the log and exception translations and have not
> come to a decision.
>
> I've made some research and found a useful documents:
>
>
>- https://wiki.openstack.org/wiki/LoggingStandards#Log_Translation
>- https://wiki.openstack.org/wiki/Translations
>
>
> Here two main points, that I can highlight
>
> * "*Exception text should **not** be marked for translation,*
> because if an exception occurs there is no guarantee that the
> translation machinery will be functional."
>
> ** "Debug level log messages are not translated"*
>
> Some projects do not follow these rules, but I suggest to take them into
> consideration and perform the following actions:
>
>- First of all, we should remove gettext utils usage and replace it
>with oslo.i18n;
>- Remove exception messages translation;
>- Add log translation to info, warn and error log level (and
>log.exception which creates log.error message).
>
> Note, that different log levels can be separated to different files. It's
> also supported to have different log files for different languages.
>
> What do you think?
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] exception in deployment

2015-02-04 Thread Serg Melikyan

 [-]
> cad324b38b064c6a92f8bdf55b01ce37: End execution:
> io.murano.system.Agent.prepare (-5222445134521330586) with exception
> [exceptions.IOError]: Socket closed _invoke_method_implementation
> /opt/stack/murano/murano/dsl/executor.py:156
>
> 2015-02-04 17:37:54.044 28689 DEBUG murano.dsl.executor [-]
> cad324b38b064c6a92f8bdf55b01ce37: End execution:
> io.murano.resources.Instance.deploy (-6771477997220427611) with exception
> [exceptions.IOError]: Socket closed _invoke_method_implementation
> /opt/stack/murano/murano/dsl/executor.py:156
>
> 2015-02-04 17:37:54.044 28689 DEBUG murano.dsl.executor [-]
> cad324b38b064c6a92f8bdf55b01ce37: End execution:
> io.murano.apps.linux.Telnet.deploy (-3331993352887903899) with exception
> [exceptions.IOError]: Socket closed _invoke_method_implementation
> /opt/stack/murano/murano/dsl/executor.py:156
>
> 2015-02-04 17:37:54.045 28689 DEBUG murano.dsl.executor [-]
> 2d99ec6cb8744a418321010e0155d1be: Begin execution:
> io.murano.system.AgentListener.stop (8219708049029306173) called from File
>  in method None
>
> None _invoke_method_implementation
> /opt/stack/murano/murano/dsl/executor.py:142
>
> 2015-02-04 17:37:54.045 28689 DEBUG murano.dsl.executor [-]
> 2d99ec6cb8744a418321010e0155d1be: End execution:
> io.murano.system.AgentListener.stop (8219708049029306173)
> _invoke_method_implementation /opt/stack/murano/murano/dsl/executor.py:160
>
> 2015-02-04 17:37:54.046 28689 DEBUG murano.dsl.executor [-]
> 2d99ec6cb8744a418321010e0155d1be: End execution:
> io.murano.Environment.deploy (2363767013075233465) with exception
> [exceptions.IOError]: Socket closed _invoke_method_implementation
> /opt/stack/murano/murano/dsl/executor.py:156
>
> 2015-02-04 17:37:54.046 28689 ERROR murano.common.engine [-]
>
>   exceptions.IOError: Socket closed
>
>   Traceback (most recent call last):
>
> File
> "/tmp/murano-packages-cache/1aaac863-f712-4ec6-b7c3-683d3498b951/io.murano/Classes/Environment.yaml",
> line 68:13 in method deploy of class io.murano.Environment
>
> $.applications.pselect($.deploy())
>
> File
> "/tmp/murano-packages-cache/1aaac863-f712-4ec6-b7c3-683d3498b951/io.murano.apps.linux.Telnet/Classes/telnet.yaml",
> line 32:9 in method deploy of class io.murano.apps.linux.Telnet
>
> $.instance.deploy()
>
> File
> "/tmp/murano-packages-cache/1aaac863-f712-4ec6-b7c3-683d3498b951/io.murano/Classes/resources/Instance.yaml",
> line 102:9 in method deploy of class io.murano.resources.Instance
>
> $.agent.prepare()
>
> File "/opt/stack/murano/murano/engine/system/agent.py", line 68 in
> method prepare
>
> with common.create_rmq_client() as client:
>
> File "/opt/stack/murano/murano/common/messaging/mqclient.py", line 52 in
> method __enter__
>
> self.connect()
>
> File "/opt/stack/murano/murano/common/messaging/mqclient.py", line 60 in
> method connect
>
> self._connection.connect()
>
> File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line
> 237 in method connect
>
> return self.connection
>
> File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line
> 741 in method connection
>
> self._connection = self._establish_connection()
>
> File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line
> 696 in method _establish_connection
>
> conn = self.transport.establish_connection()
>
> File "/usr/local/lib/python2.7/dist-packages/kombu/transport/pyamqp.py",
> line 112 in method establish_connection
>
> conn = self.Connection(**opts)
>
> File "/usr/local/lib/python2.7/dist-packages/amqp/connection.py", line
> 180 in method __init__
>
> (10, 30),  # tune
>
> File "/usr/local/lib/python2.7/dist-packages/amqp/abstract_channel.py",
> line 67 in method wait
>
> self.channel_id, allowed_methods)
>
> File "/usr/local/lib/python2.7/dist-packages/amqp/connection.py", line
> 240 in method _wait_method
>
> self.method_reader.read_method()
>
> File "/usr/local/lib/python2.7/dist-packages/amqp/method_framing.py",
> line 189 in method read_method
>
> raise m
>
> 2015-02-04 17:37:54.047 28689 DEBUG oslo_messaging._drivers.amqp [-]
> UNIQUE_ID is 7e43279a013a441eb58a9df6580988ab. _add_unique_id
> /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqp.py:224
>
> 2015-02-04 17:37:54.059 28689 DEBUG oslo_messaging._drivers.amqpdriver [-]
> MSG_ID is a6138cbd1245497eaf768f9ba2eb6bf1 _send
>

[openstack-dev] [Murano] Review Day on Monday

2015-01-16 Thread Serg Melikyan

Hi Team,

I would like to announce another Review Day schedule on Monday (Jan 19).
During New Year & Christmas holidays our CI was broken, and queue with
change-requests is now quote long. And what is more important, many patches
and specs related to Policy Guided Fulfillment are need to be reviewed, we
had not so much time to review them, and I propose to do it on Monday.

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc][python-clients] More freedom for all python clients

2015-01-13 Thread Serg Melikyan

I support this, it will help to not break compatibility with
global-requirements for sole purpose to include python client for other
stackforge project.

On Tue, Jan 13, 2015 at 12:14 AM, Boris Pavlovic  wrote:

> Hello TC,
>
> I would like to propose to allow adding all python-clients from stackforge
> (that are regarding global-requirements) to global requirements.
>
> It doesn't cost anything and simplifies life for everybody on stackforge.
>
> P.S. We already have billions libs in global requirements that aren't even
> on stackforge.
> Having few more or less doesn't make any sense...
>
>
> Best regards,
> Boris Pavlovic
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Meeting on 01/06 is canceled

2014-12-31 Thread Serg Melikyan

Hi folks,

We agreed to cancel next meeting scheduled on 01/06 due to extended
holidays in Russia. Next meeting is scheduled on 01/13.

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Nominating Kate Chernova for murano-core

2014-12-25 Thread Serg Melikyan

Kate, welcome to murano-core!

Congratulations!

On Thu, Dec 25, 2014 at 3:52 PM, Dmitry Teselkin 
wrote:

> +2 :)
>
> On Thu, Dec 25, 2014 at 1:25 PM, Alexander Tivelkov <
> ativel...@mirantis.com> wrote:
>
>> +2!
>> Need moar good cores!
>> --
>> Regards,
>> Alexander Tivelkov
>>
>>
>> On Thu, Dec 25, 2014 at 12:50 PM, Stan Lagun  wrote:
>> > +2
>> >
>> > Sincerely yours,
>> > Stan Lagun
>> > Principal Software Engineer @ Mirantis
>> >
>> >
>> > On Thu, Dec 25, 2014 at 12:42 PM, Ruslan Kamaldinov
>> >  wrote:
>> >>
>> >> Great addition to core team!
>> >>
>> >> +2
>> >>
>> >>
>> >>
>> >> On Thu, Dec 25, 2014 at 11:02 AM, Timur Sufiev 
>> >> wrote:
>> >> > +1 from me.
>> >> >
>> >> > On Thu, Dec 25, 2014 at 10:28 AM, Serg Melikyan <
>> smelik...@mirantis.com>
>> >> > wrote:
>> >> >>
>> >> >> I'd like to propose that we add Kate Chernova to the murano-core.
>> >> >>
>> >> >> Kate is active member of our community for more than a year, she is
>> >> >> regular participant in our IRC meeting and maintains a good score as
>> >> >> contributor:
>> >> >>
>> >> >> http://stackalytics.com/report/users/efedorova
>> >> >>
>> >> >> Please vote by replying to this thread. As a reminder of your
>> options,
>> >> >> +1
>> >> >> votes from 5 cores is sufficient; a -1 is a veto.
>> >> >> --
>> >> >> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>> >> >> http://mirantis.com | smelik...@mirantis.com
>> >> >>
>> >> >> ___
>> >> >> OpenStack-dev mailing list
>> >> >> OpenStack-dev@lists.openstack.org
>> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Timur Sufiev
>> >> >
>> >> > ___
>> >> > OpenStack-dev mailing list
>> >> > OpenStack-dev@lists.openstack.org
>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >> >
>> >>
>> >> ___
>> >> OpenStack-dev mailing list
>> >> OpenStack-dev@lists.openstack.org
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> >
>> > ___
>> > OpenStack-dev mailing list
>> > OpenStack-dev@lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Thanks,
> Dmitry Teselkin
> Deployment Engineer
> Mirantis
> http://www.mirantis.com
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Nominating Kate Chernova for murano-core

2014-12-24 Thread Serg Melikyan

I'd like to propose that we add Kate Chernova to the murano-core.

Kate is active member of our community for more than a year, she is regular
participant in our IRC meeting and maintains a good score as contributor:

http://stackalytics.com/report/users/efedorova

Please vote by replying to this thread. As a reminder of your options, +1
votes from 5 cores is sufficient; a -1 is a veto.
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Kilo-1 Dev Milestone Released!

2014-12-18 Thread Serg Melikyan

I forgot to mention that we also released handful of well-tested Murano
application, that can be used both as example and as ready applications for
your cloud. Application are available in our new repository:
https://github.com/stackforge/murano-apps

We released following applications in this milestone:

   - WordPress
   - Zabbix Monitoring
   - Apache HttpServer
   - Apache Tomcat
   - MySql
   - PostgreSql


On Thu, Dec 18, 2014 at 12:56 PM, Serg Melikyan 
wrote:
>
> Hi folks,
>
> I am happy to announce that first Kilo milestone is now available. You can
> download the kilo-1 release and review the changes here:
> https://launchpad.net/murano/kilo/kilo-1
>
> With this milestone we release several new and important features, that I
> would like to kindly ask to try and play with:
>
>- Handle auth expiration for long-running deployments
>- Per-class configuration files
>
> We added support for long-running deployments in Murano. Previously
> deployment time was restricted by token expiration time, in case when user
> started deployment close to token expiration time, deployment was failing
> on Heat stack creation.
>
> We've also implemented support for per-class configuration files during
> this milestone. Murano may be easily extended, for example with support for
> different third-party services, like monitoring or firewall. You can find
> demo-example of such extension here:
> https://github.com/sergmelikyan/murano/tree/third-party
>
> In this example we add ZabbixApi class that handles interaction with
> Zabbix monitoring system installed outside of the cloud and exposes API to
> all the applications in the catalog, giving ability to configure monitoring
> for themselves:
> https://github.com/sergmelikyan/murano/blob/third-party/murano/engine/contrib/zabbix.py
>
> Obviously we need to store credentials for Zabbix somewhere, and
> previously it was done in main Murano configuration file. Now each class
> may have own configuration file, with nice ability to automatically fill
> class properties by configuration values.
>
> Unfortunately these features are not yet documented, please refer to
> commit messages and implementation for details. We would be happy for any
> contribution to Murano and especially contribution to our documentation.
>
>   * https://review.openstack.org/134183
>   * https://review.openstack.org/119042
>
> Thank you!
>
> --
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
> http://mirantis.com | smelik...@mirantis.com
>
> +7 (495) 640-4904, 0261
> +7 (903) 156-0836
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Kilo-1 Dev Milestone Released!

2014-12-18 Thread Serg Melikyan

Hi folks,

I am happy to announce that first Kilo milestone is now available. You can
download the kilo-1 release and review the changes here:
https://launchpad.net/murano/kilo/kilo-1

With this milestone we release several new and important features, that I
would like to kindly ask to try and play with:

   - Handle auth expiration for long-running deployments
   - Per-class configuration files

We added support for long-running deployments in Murano. Previously
deployment time was restricted by token expiration time, in case when user
started deployment close to token expiration time, deployment was failing
on Heat stack creation.

We've also implemented support for per-class configuration files during
this milestone. Murano may be easily extended, for example with support for
different third-party services, like monitoring or firewall. You can find
demo-example of such extension here:
https://github.com/sergmelikyan/murano/tree/third-party

In this example we add ZabbixApi class that handles interaction with Zabbix
monitoring system installed outside of the cloud and exposes API to all the
applications in the catalog, giving ability to configure monitoring for
themselves:
https://github.com/sergmelikyan/murano/blob/third-party/murano/engine/contrib/zabbix.py

Obviously we need to store credentials for Zabbix somewhere, and previously
it was done in main Murano configuration file. Now each class may have own
configuration file, with nice ability to automatically fill class
properties by configuration values.

Unfortunately these features are not yet documented, please refer to commit
messages and implementation for details. We would be happy for any
contribution to Murano and especially contribution to our documentation.

  * https://review.openstack.org/134183
  * https://review.openstack.org/119042

Thank you!

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Question about Murano installation

2014-12-17 Thread Serg Melikyan

Hi, Raghavendra

Given screenshots that you have send, you are using extremely outdated
version of murano-dashboard (and probably outdated version of all other
components). That is why you may experience issues with manual
<http://murano.readthedocs.org/> written for Juno version of Murano.

I encourage you to use Juno version of Murano, you can obtain it by
checking out sources, e.g. for murano-dashboard:

git clone https://github.com/stackforge/murano-dashboard
git checkout 2014.2

You also can download tarballs from http://tarballs.openstack.org/:

   - murano-2014.2.tar.gz
   <http://tarballs.openstack.org/murano/murano-2014.2.tar.gz> (wheel
   <http://tarballs.openstack.org/murano/murano-2014.2-py2-none-any.whl>)
   - murano-dashboard-2014.2.tar.gz

<http://tarballs.openstack.org/murano-dashboard/murano-dashboard-2014.2.tar.gz>
(wheel

<http://tarballs.openstack.org/murano-dashboard/murano_dashboard-2014.2-py2-none-any.whl>
   )

Please, find answers to your questions bellow:

>should I use for mysql and the [murano] the localhost:8082, please clarify.

Option url in murano section should point to address where murano-api is
running. Option connection in database section, should point to address
where MySQL is runnings. Unfortunately I don't know your OpenStack
deployment scheme, so I can't answer more accurate.

>How can I install Murano Agent please provide details?

murano-agent is agent which runs on guest VMs and responsible for
provisioning application on VM. It is not required, but many existing
applications use murano-agent to do application provisioning/configuration.

We use Disk Image Builder
<https://github.com/openstack/diskimage-builder> project
to build images with murano-agent installed, please refer to murano-agent
ReadMe <https://github.com/stackforge/murano-agent#image-building-using-dib>
for
details about how to build image with murano-agent.

We also have pre-built images with murano-agent for Fedora 17 & Ubuntu
14.04:

   - http://murano-files.mirantis.com/F17-x86_64-cfntools.qcow2
   -
   http://murano-files.mirantis.com/ubuntu_14_04-murano-agent_stable_juno.qcow2

>How to install dashboard can I follow doc and install using tox?
>Where to update the murano_metadata url details?

To install murano-dashboard correctly you need just to follow manual and
use Murano 2014.2 version. There is no option MURANO_METADATA_URL anymore
in murano-dashboard.

On Tue, Dec 16, 2014 at 9:13 PM,  wrote:
>
>  Hi Serg,
>
>
>
> Thank you for your response.
>
>
>
> I have the Openstack Ubuntu Juno version on 14.04 LTS.
>
>
>
> I am following the below link
>
>
>
> https://murano.readthedocs.org/en/latest/install/manual.html
>
>
>
> I have attached the error messages with this email.
>
>
>
> I am unable to see the Application menu on the Murano dashboard.
>
> I am unable to install Applications for the Murano. (Please let me know
> how we can install the Application packages)
>
>
>
> I would like to know about Murano Agent.
>
>
>
> Can we spin up a  VM from Openstack and install the Murano Agent
> components for creating image ?
>
> If not please provide details.
>
>
>
>
>
> Incase of any doubts please let me know.
>
>
>
> Regards,
>
> Raghavendra Lad
>
> Mobile: +9198800 40919
>
>
>
> *From:* Serg Melikyan [mailto:smelik...@mirantis.com]
> *Sent:* Wednesday, December 17, 2014 12:58 AM
> *To:* Lad, Raghavendra
> *Subject:* Murano Mailing-List
>
>
>
> Hi, Raghavendra
>
>
>
> I would like to mention that we don't use mailing-list on launchpad
> anymore, there is no reason to duplicate messages sent to openstack-dev@
> to the murano-...@lists.launchpad.net.
>
>
>
> You can also reach team working on Murano using IRC on #murano at FreeNode
>
>
>
> --
>
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>
> http://mirantis.com | smelik...@mirantis.com
>
>
> +7 (495) 640-4904, 0261
>
> +7 (903) 156-0836
>
> --
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> __
>
> www.accenture.com
>

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] Review Day Announcement

2014-12-09 Thread Serg Melikyan

I would like to announce Review Day for Murano, that is scheduled to this
Friday, Dec 12. We will start at 10:00 UTC and will continue until 10:00 of
the next day to span across the globe.

We encourage to join our review day anyone who is interested in Murano, not
only core-reviewers.

Rules:
* review as much as possible
* stay in channel and respond to questions and comments promptly

-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Juno RC1 is Available

2014-10-01 Thread Serg Melikyan

We successfully released RC1 release of Murano!

The RC1 tarballs are available for download at:
https://launchpad.net/murano/juno/juno-rc1

Unless critical issues are found, this RC1 will be formally released
as the 2014.2 final version of Murano. Please, try to do extensive
testing of this version as possible, and do file all found bugs.
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Changes in networking part of Murano

2014-09-25 Thread Serg Melikyan

We are thinking about providing extended networking configuration to
the user during environment creation through the UI, and it is
mentioned in the Networking Manager specification [1]. But we decided
to focus on improvement of use-ability and stability in Juno cycle and
many really cool features was moved to the next cycle, like manual
networking configuration of networking in the environment. We are
currently working on the roadmap for the Kilo cycle, and maybe this
feature will be available in Kilo, though no guarantee.

[1] https://wiki.openstack.org/wiki/Murano/Specifications/Network_Management

On Thu, Sep 25, 2014 at 1:05 PM, Timur Nurlygayanov
 wrote:
> Hi,
>
> what if we will add drop down list with the list of all routers which are
> available in the specific tenant and user will have the ability to select
> the router during the application configuration? (like now user can select,
> for example, availability zone or keypair).
>
> Regards,
> Timur
>
> On Thu, Sep 25, 2014 at 12:15 PM, Serg Melikyan 
> wrote:
>>
>> Murano have advanced networking features that give you ability to not care
>> about configuring networks for your application. By default it will create
>> an isolated network for each environment and join all VMs needed by your
>> application to that network.
>>
>> Previously, created network was joined to the first found router in the
>> tenant and this behaviour is wrong in many ways. At least some tenants may
>> have more than one router, and this may cause issues when Murano attaching
>> network to the wrong router.
>>
>> We reworked this feature a little bit
>> (https://review.openstack.org/119800). Now you can choose which router
>> should be used by Murano to attach created networks. By default router
>> should be named as "murano-default-router". You can change name of the
>> router that will be used in configuration file, in the [networking]
>> section:
>> [networking]
>> ...
>>
>> # Name of the router that going to be used in order to join
>> # all networks created by Murano (string value)
>> router_name=router04
>>
>> Warning! This means, that if you will upgrade Murano to the juno-rc1
>> without additional configuration your deployment will stop working failing
>> with following error message: KeyError: Router murano-default-router was not
>> found
>>
>> Requiring cloud providers to have configured router for each tenant is a
>> burden on DevOps teams, therefore we improved
>> (https://review.openstack.org/121679) this feature a little bit more and
>> added ability to create router with specified name if it is not present in
>> the tenant. This behaviour may be switched on/off via configuration file,
>> and you can also specify which external network should be used to attach
>> router to:
>> [networking]
>> ...
>> # ID or name of the external network for routers to connect to
>> # (string value)
>> #external_network=ext-net
>> ...
>> # This option will create a router when one with "router_name"
>> # does not exist (boolean value)
>> #create_router=true
>>
>> --
>> Serg Melikyan
>> http://mirantis.com | smelik...@mirantis.com
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
>
> Timur,
> QA Engineer
> OpenStack Projects
> Mirantis Inc
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

-- 
Serg Melikyan
http://mirantis.com | smelik...@mirantis.com

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Murano] Changes in networking part of Murano

2014-09-25 Thread Serg Melikyan

Murano have advanced networking features that give you ability to not care
about configuring networks for your application. By default it will create
an isolated network for each environment and join all VMs needed by your
application to that network.

Previously, created network was joined to the first found router in the
tenant and this behaviour is wrong in many ways. At least some tenants may
have more than one router, and this may cause issues when Murano attaching
network to the wrong router.

We reworked this feature a little bit
(https://review.openstack.org/119800). Now
you can choose which router should be used by Murano to attach created
networks. By default router should be named as "*murano-default-router*".
You can change name of the router that will be used in configuration file,
in the [*networking]  *section:
[networking]
...

# Name of the router that going to be used in order to join
# all networks created by Murano (string value)
router_name=router04

Warning! This means, that if you will upgrade Murano to the *juno-rc1* without
additional configuration your deployment will stop working failing with
following error message: *KeyError: Router murano-default-router was not
found*

Requiring cloud providers to have configured router for each tenant is a
burden on DevOps teams, therefore we improved (
https://review.openstack.org/121679) this feature a little bit more and
added ability to create router with specified name if it is not present in
the tenant. This behaviour may be switched on/off via configuration file,
and you can also specify which external network should be used to attach
router to:
[networking]
...
# ID or name of the external network for routers to connect to
# (string value)
#external_network=ext-net
...
# This option will create a router when one with "router_name"
# does not exist (boolean value)
#create_router=true

-- 
Serg Melikyan
http://mirantis.com | smelik...@mirantis.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Attach an USB disk to VM [nova]

2014-09-15 Thread Serg Melikyan

Sure, take a look at Software Configuration feature of Heat
https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config-spec

Examples of SoftwareConfiguration usage may be found here:
https://git.openstack.org/cgit/openstack/heat-templates/tree/hot/software-config

On Mon, Sep 15, 2014 at 1:54 PM, pratik maru  wrote:

> Hi All,
>
> Is there any way to do the same using Heat ?
>
> Thanks
> fipuzzles
>
> On Mon, Sep 15, 2014 at 12:09 PM, Serg Melikyan 
> wrote:
>
>> Other approach to the way I have described in the mail above is to use
>> openstack/os-collect-config
>> <https://github.com/openstack/os-collect-config> project to handle
>> downloading and running shell script.
>>
>> On Mon, Sep 15, 2014 at 10:35 AM, Serg Melikyan 
>> wrote:
>>
>>> If data that are you planning to pass to the VM is considerably large
>>> Metadata mechanism may be used for passing at least a link to the source of
>>> data and simple shell script that will executed on VM with CloudInit right
>>> after the boot to obtain data via simple cURL.
>>>
>>> On Mon, Sep 15, 2014 at 10:20 AM, Denis Makogon 
>>> wrote:
>>>
>>>> Agreed with Max.
>>>> With nova you can use file injection mechanism. You just need to build
>>>> a dictionary of file paths and file content. But I do agree that it's not
>>>> the same as you want. But it's more than
>>>> valid way to inject files.
>>>>
>>>> Best regards,
>>>> Denis Makogon
>>>>
>>>> понедельник, 15 сентября 2014 г. пользователь Maksym Lobur написал:
>>>>
>>>> Try to use Nova Metadata Serivce [1] or Nova Config Drive [2]. There
>>>>> are options to pass Key-Value data as well as whole files during VM boot.
>>>>>
>>>>> [1]
>>>>> http://docs.openstack.org/grizzly/openstack-compute/admin/content/metadata-service.html
>>>>> [2]
>>>>> http://docs.openstack.org/grizzly/openstack-compute/admin/content/config-drive.html
>>>>>
>>>>> Best regards,
>>>>> Max Lobur,
>>>>> OpenStack Developer, Mirantis, Inc.
>>>>>
>>>>> Mobile: +38 (093) 665 14 28
>>>>> Skype: max_lobur
>>>>>
>>>>> 38, Lenina ave. Kharkov, Ukraine
>>>>> www.mirantis.com
>>>>> www.mirantis.ru
>>>>>
>>>>> On Sun, Sep 14, 2014 at 10:21 PM, pratik maru 
>>>>> wrote:
>>>>>
>>>>>> Hi Xian,
>>>>>>
>>>>>> Thanks for replying.
>>>>>>
>>>>>> I have some data which i wants to be passed to VM. To pass this data,
>>>>>>  I have planned this to attach as an usb disk and this disk will be used
>>>>>> inside the vm to read the data.
>>>>>>
>>>>>> What I am looking is for the functionality similar to "-usb" option
>>>>>> with qemu.kvm command.
>>>>>>
>>>>>> Please let me know, how it can be achieved in openstack environment.
>>>>>>
>>>>>> Thanks
>>>>>> fipuzzles
>>>>>>
>>>>>> On Mon, Sep 15, 2014 at 8:14 AM, Xiandong Meng <
>>>>>> mengxiand...@gmail.com> wrote:
>>>>>>
>>>>>>> What is your concrete user scenario for this request?
>>>>>>> Where do you expect to plugin the USB disk? On the compute node that
>>>>>>> hosts the VM or from somewhere else?
>>>>>>>
>>>>>>> On Mon, Sep 15, 2014 at 3:01 AM, pratik maru 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Is there any way to attach an USB disk as an external disk to VM
>>>>>>>> while booting up the VM ?
>>>>>>>>
>>>>>>>> Any help in this respect will be really helpful.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> fipuzzles
>>>>>>>>
>>>>>>>> ___
>>>>>>>> OpenStack-dev mailing list
>>>>>>>> OpenStack-dev@lists.openstack.org
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/

Re: [openstack-dev] Attach an USB disk to VM [nova]

2014-09-14 Thread Serg Melikyan

Other approach to the way I have described in the mail above is to use
openstack/os-collect-config
<https://github.com/openstack/os-collect-config> project
to handle downloading and running shell script.

On Mon, Sep 15, 2014 at 10:35 AM, Serg Melikyan 
wrote:

> If data that are you planning to pass to the VM is considerably large
> Metadata mechanism may be used for passing at least a link to the source of
> data and simple shell script that will executed on VM with CloudInit right
> after the boot to obtain data via simple cURL.
>
> On Mon, Sep 15, 2014 at 10:20 AM, Denis Makogon 
> wrote:
>
>> Agreed with Max.
>> With nova you can use file injection mechanism. You just need to build a
>> dictionary of file paths and file content. But I do agree that it's not the
>> same as you want. But it's more than
>> valid way to inject files.
>>
>> Best regards,
>> Denis Makogon
>>
>> понедельник, 15 сентября 2014 г. пользователь Maksym Lobur написал:
>>
>> Try to use Nova Metadata Serivce [1] or Nova Config Drive [2]. There are
>>> options to pass Key-Value data as well as whole files during VM boot.
>>>
>>> [1]
>>> http://docs.openstack.org/grizzly/openstack-compute/admin/content/metadata-service.html
>>> [2]
>>> http://docs.openstack.org/grizzly/openstack-compute/admin/content/config-drive.html
>>>
>>> Best regards,
>>> Max Lobur,
>>> OpenStack Developer, Mirantis, Inc.
>>>
>>> Mobile: +38 (093) 665 14 28
>>> Skype: max_lobur
>>>
>>> 38, Lenina ave. Kharkov, Ukraine
>>> www.mirantis.com
>>> www.mirantis.ru
>>>
>>> On Sun, Sep 14, 2014 at 10:21 PM, pratik maru 
>>> wrote:
>>>
>>>> Hi Xian,
>>>>
>>>> Thanks for replying.
>>>>
>>>> I have some data which i wants to be passed to VM. To pass this data,
>>>>  I have planned this to attach as an usb disk and this disk will be used
>>>> inside the vm to read the data.
>>>>
>>>> What I am looking is for the functionality similar to "-usb" option
>>>> with qemu.kvm command.
>>>>
>>>> Please let me know, how it can be achieved in openstack environment.
>>>>
>>>> Thanks
>>>> fipuzzles
>>>>
>>>> On Mon, Sep 15, 2014 at 8:14 AM, Xiandong Meng 
>>>> wrote:
>>>>
>>>>> What is your concrete user scenario for this request?
>>>>> Where do you expect to plugin the USB disk? On the compute node that
>>>>> hosts the VM or from somewhere else?
>>>>>
>>>>> On Mon, Sep 15, 2014 at 3:01 AM, pratik maru 
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Is there any way to attach an USB disk as an external disk to VM
>>>>>> while booting up the VM ?
>>>>>>
>>>>>> Any help in this respect will be really helpful.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> fipuzzles
>>>>>>
>>>>>> ___
>>>>>> OpenStack-dev mailing list
>>>>>> OpenStack-dev@lists.openstack.org
>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>>
>>>>> Xiandong Meng
>>>>> mengxiand...@gmail.com
>>>>>
>>>>> ___
>>>>> OpenStack-dev mailing list
>>>>> OpenStack-dev@lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>
>>>>>
>>>>
>>>> ___
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
> http://mirantis.com | smelik...@mirantis.com
>
> +7 (495) 640-4904, 0261
> +7 (903) 156-0836
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Attach an USB disk to VM [nova]

2014-09-14 Thread Serg Melikyan

If data that are you planning to pass to the VM is considerably large
Metadata mechanism may be used for passing at least a link to the source of
data and simple shell script that will executed on VM with CloudInit right
after the boot to obtain data via simple cURL.

On Mon, Sep 15, 2014 at 10:20 AM, Denis Makogon 
wrote:

> Agreed with Max.
> With nova you can use file injection mechanism. You just need to build a
> dictionary of file paths and file content. But I do agree that it's not the
> same as you want. But it's more than
> valid way to inject files.
>
> Best regards,
> Denis Makogon
>
> понедельник, 15 сентября 2014 г. пользователь Maksym Lobur написал:
>
> Try to use Nova Metadata Serivce [1] or Nova Config Drive [2]. There are
>> options to pass Key-Value data as well as whole files during VM boot.
>>
>> [1]
>> http://docs.openstack.org/grizzly/openstack-compute/admin/content/metadata-service.html
>> [2]
>> http://docs.openstack.org/grizzly/openstack-compute/admin/content/config-drive.html
>>
>> Best regards,
>> Max Lobur,
>> OpenStack Developer, Mirantis, Inc.
>>
>> Mobile: +38 (093) 665 14 28
>> Skype: max_lobur
>>
>> 38, Lenina ave. Kharkov, Ukraine
>> www.mirantis.com
>> www.mirantis.ru
>>
>> On Sun, Sep 14, 2014 at 10:21 PM, pratik maru 
>> wrote:
>>
>>> Hi Xian,
>>>
>>> Thanks for replying.
>>>
>>> I have some data which i wants to be passed to VM. To pass this data,  I
>>> have planned this to attach as an usb disk and this disk will be used
>>> inside the vm to read the data.
>>>
>>> What I am looking is for the functionality similar to "-usb" option with
>>> qemu.kvm command.
>>>
>>> Please let me know, how it can be achieved in openstack environment.
>>>
>>> Thanks
>>> fipuzzles
>>>
>>> On Mon, Sep 15, 2014 at 8:14 AM, Xiandong Meng 
>>> wrote:
>>>
>>>> What is your concrete user scenario for this request?
>>>> Where do you expect to plugin the USB disk? On the compute node that
>>>> hosts the VM or from somewhere else?
>>>>
>>>> On Mon, Sep 15, 2014 at 3:01 AM, pratik maru 
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Is there any way to attach an USB disk as an external disk to VM while
>>>>> booting up the VM ?
>>>>>
>>>>> Any help in this respect will be really helpful.
>>>>>
>>>>>
>>>>> Thanks
>>>>> fipuzzles
>>>>>
>>>>> ___
>>>>> OpenStack-dev mailing list
>>>>> OpenStack-dev@lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Xiandong Meng
>>>> mengxiand...@gmail.com
>>>>
>>>> ___
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] Introducing reference Murano packages repository

2014-07-31 Thread Serg Melikyan

Few month ago we have created repository on github to where we moved
several applications that were bundled with Murano previously. That
repository was created as a place where we could gather all
applications and packages that we had created for Murano, update them
at the same time and as place where we could point when answer for
some question about packages required example.

After successfully playing with that repository, we decided that there
is a need in dedicated repository on stackforge and now we are
introducing murano-apps repository:
https://git.openstack.org/cgit/stackforge/murano-apps

murano-apps will serve as a place where packages will be published that:

  * are proven to work on generic deployment of OpenStack
  * can serve as reference implementation
  * are simple as possible, but complex enough to show the idea

All changes with packages submitted to this repository will go through
rigorous review and helpful gate jobs that will check that package. We
haven't thought yet about what gate jobs we will have, but I think we
need to check that particular package may be deployed, check that all
specific files comply with specification (e.g. manifest is correct).

We need to start filling murano-apps repository with examples
targeting usage of Heat SoftwareConfiguration feature as it is a hot
topic, packages that consists from single heat template as
deployment/configuration scenario, and more generic simpler packages.

P.S. Our old repository with packages can be found on github:
https://github.com/murano-project/murano-app-incubator

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Image tagging

2014-07-23 Thread Serg Melikyan

,
>> "name": "Ubuntu", "version": "12.04", "arch": "x86_x64" } (this also may be
>> encoded as a single string)
>>
>> Workflows (MuranoPL contracts) need to be able to express
>> requirements based on those attributes. For example
>>
>>
>>
>> image:
>>
>>   Contract($.class(Image).check($.family = Linux and $.arch = x86)
>>
>>
>>
>>In UI only those images that matches such contract should be displayed.
>>
>>
>>
>> 2. Human readable image title "Ubuntu Linux 12.04 x86"
>>
>>
>>
>> 3. Information about built-in software for image-based deployment. Not
>> sure exactly what information is needed. Meybe even portion of Object Model
>> so that if such image is used Murano environment will automatically
>> recocnize and incorporate that application like it was added by user to be
>> installed on clean instance. This will allow using of pre-build images with
>> preinstalled software (e.g. speed up deployment) but will make it
>> transparent for the user so that this software could be managed as well as
>> applications that user choses to install
>>
>>
>>
>> 4. Minimal hardware requirement for the image. Murano could use that
>> information to guarantee that user will not select flavor that is too small
>> for that operating system.
>>
>>
>>
>> 5. General-purposed tags
>>
>>
>>
>> We need to think how this concept fits into our roadmap and new Glance
>> design (probably there are other projects that can benefit from extended
>> image metadata) before chosing one of your approaches
>>
>>
>>
>>
>>
>>
>>   Sincerely yours,
>> Stan Lagun
>> Principal Software Engineer @ Mirantis
>>
>>
>>
>> On Fri, Jul 18, 2014 at 6:46 PM, McLellan, Steven 
>> wrote:
>>
>>  Hi,
>>
>>
>>
>> Images that can be used for package deployment have to be tagged in
>> glance in order to enable the UI to filter the list of images to present to
>> a user (and potentially preselect). Currently the tags are defined in the
>> dashboard code (images/forms.py) which makes things very inflexible; if I
>> can upload an image and a package that consumes that image, I don’t want to
>> have to make a code change to use it.
>>
>>
>>
>> Anyone who can upload images should also be able to specify tags for
>> them. There is also the question of whether a user should be allowed to tag
>> images that don’t belong to them (e.g. a shared image used by a private
>> package), but I think that can be punted down the road somewhat.
>>
>>
>>
>> I think this needs to be more dynamic, and if that’s agreed upon, there
>> are a couple of approaches:
>>
>> 1)  Store allowed tags in the database, and allow administrators to
>> add to that list. Ordinary users would likely not be able to create tags,
>> though they could use pre-defined ones for images they owned.
>>
>> 2)  Have some public tags, but also allow user-specified tags for
>> private packages. I think this leads to all sorts of tricky edge cases
>>
>> 3)  Allow freeform tags (i.e. don’t provide any hints). Since
>> there’s no formal link between the tag that a package looks for and the
>> tags currently defined in code, this wouldn’t make anything more
>> susceptible to inaccuracies
>>
>>
>>
>> It would also be worth considering if there’s value allowing multiple
>> tags per image (I’m on the fence).
>>
>>
>>
>> Personally, I think that 1) would be an improvement over the current
>> situation that’s reasonably easy to implement; that would allow the bare
>> minimum of flexibility without requiring much extra design. The other
>> options would perhaps be a longer term goal.
>>
>>
>>
>> Thoughts? If there’s general agreement I will turn this into a blueprint.
>>
>>
>>
>> Steve
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel-dev] Upgrades for Murano in MOS

2014-07-23 Thread Serg Melikyan

Hi, Mike,

I can't be specific about implementation details due to lack of expertise
in Fuel, but to properly handle update of Murano from previous version to
MOS 5.1 we need to:

   1. show warning to the user about deleting all resources managed by
   Murano (all VMs, networks, etc.. created as part of applications
   deployment);
   2. remove them;
   3. delete database;
   4. install Murano as usual.

 I worry that first step may be quite hard to implement, here we need
expertise from Fuel team.



On Wed, Jul 23, 2014 at 5:53 PM, Mike Scherbakov 
wrote:

> Hi Serg,
> what needs to be done in order to include Alembic-related stuff into 5.1?
> The thing is that we are just a day before Soft Code Freeze.
>
> If this is trivial operation, such as adding a new package and updating
> configuration file, then we could consider it to be included.
>
> Thanks,
>
>
> On Wed, Jul 23, 2014 at 5:36 PM, Serg Melikyan 
> wrote:
>
>> During this cycle we introduced migrations based on Alembic
>> <https://bitbucket.org/zzzeek/alembic> framework that are incompatible
>> with previous set of migrations based on sqlalchemy-migrate
>> <https://github.com/stackforge/sqlalchemy-migrate>. This changes are
>> going to be included to MOS with release targeting Juno release of
>> Openstack.
>>
>> New migration framework makes imposible to seamlessly migrate from
>> previous version of Murano to the next one - all data stored in the
>> database is going to be lost. Murano (as part of MOS) can't be upgraded
>> from any previous version of MOS to MOS 6.0.
>>
>> I suggest to include this feature (migrations based on Alembic) to MOS as
>> soon as possible, to be precise to MOS 5.1. This will allow to have
>> upgrades for Murano from MOS 5.1 to all the next versions of MOS, including
>> 6.0. Upgrade from 5.0.1 to 5.1 for Murano without loosing all data will be
>> impossible.
>> --
>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>> http://mirantis.com | smelik...@mirantis.com
>>
>> +7 (495) 640-4904, 0261
>> +7 (903) 156-0836
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Mike Scherbakov
> #mihgen
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel-dev] Upgrades for Murano in MOS

2014-07-23 Thread Serg Melikyan

During this cycle we introduced migrations based on Alembic
<https://bitbucket.org/zzzeek/alembic> framework that are incompatible with
previous set of migrations based on sqlalchemy-migrate
<https://github.com/stackforge/sqlalchemy-migrate>. This changes are going
to be included to MOS with release targeting Juno release of Openstack.

New migration framework makes imposible to seamlessly migrate from previous
version of Murano to the next one - all data stored in the database is
going to be lost. Murano (as part of MOS) can't be upgraded from any
previous version of MOS to MOS 6.0.

I suggest to include this feature (migrations based on Alembic) to MOS as
soon as possible, to be precise to MOS 5.1. This will allow to have
upgrades for Murano from MOS 5.1 to all the next versions of MOS, including
6.0. Upgrade from 5.0.1 to 5.1 for Murano without loosing all data will be
impossible.
-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 2 >

1 - 100 of 126 matches

Mail list logo