Re: [openstack-dev] [Murano] How to debug a failed deployment?

[Ekaterina Chernova]

Hi Vahid,

looks like trace in bug should not block engine run, we are currently
investigating it.

If you are seeing that trace, then you are able to get engine logs :)
Can you start your deployment and attach all engine logs even with the
trace?


Regards,
Kate.


On Tue, Dec 8, 2015 at 4:12 AM, Vahid S Hashemian  wrote:

> Hi Stan,
>
> Not sure how I can enable murano engine log.
>
> Anyway, you were right that murano engine was not running.
> I started it and am now hitting this bug:
> https://bugs.launchpad.net/murano/+bug/1521087
>
> I guess I'll have to wait until the fix is released.
>
> Thanks.
>
> 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

Re: [openstack-dev] [Murano] How to debug a failed deployment?

[Ekaterina Chernova]

Hi!

Murano agent doesn't involved in the deployment of hot packages, that's why
this setting doesn't help.

Please attach agent logs and heat logs also (check if heat stack is created
or not).

Regards, Kate.


Regards,
Kate.


On Thu, Dec 3, 2015 at 11:44 AM, Dmytro Dovbii  wrote:

> Hi Vahid,
>
> Could you provide your logs anyway? Please publish them to
> http://paste.openstack.org/ for example
>
> 2015-12-02 23:08 GMT+02:00 Vahid S Hashemian :
>
>> Hello,
>>
>> I am trying to deploy a hello world HOT package in murano but the
>> deployment runs forever and does not stop (does not succeed or fail).
>> Stan advised me to modify the config setting below to set a timeout:
>>
>> # Time for waiting for a response from murano agent during the
>> # deployment (integer value)
>> agent_timeout = 300
>>
>> As you see I set the timeout to 300 seconds and restarted murano API, but
>> even after 15 minutes my deployment is still going.
>> I think my environment is not configured correctly for this to happen.
>>
>> I have devstack running on a VM, and my murano development is done on a
>> separate VM.
>> I bring up murano API and UI on my dev VM that successfully connect to my
>> devstack VM.
>>
>> I am able to deploy the HOT yaml using heat without an issue.
>> From what I can see it seems that murano is not able to talk to heat,
>> because I don't see any stack being created as a result of my deployment.
>>
>> I have also enabled murano logging in the config file as below:
>>
>> # (Optional) Name of log file to output to. If no default is set,
>> # logging will go to stdout. (string value)
>> # Deprecated group/name - [DEFAULT]/logfile
>> log_file = /opt/stack/logs/murano.log
>>
>> But no error  is reported while the deployment is in progress.
>>
>> Any tips on how to force the timeout, and also on how to resolve the
>> deployment problem is 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
>
>
__
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

[Ekaterina Chernova]

Hi Vahid,

Forms are rended after app is added to the environment in accordance with
the UI definition.
UI definition contains yaql expressions and one of your expression is
incorrect.
Please, share UI yaml so we can find out what's the problem.
You can also create a bug that it's not obvious which expression is failed.


Also, make sure that you have valid YAQL version installed (should
correspond to the version in requirements.txt)
And you can ask for help in #murano channel.

Regards,
Kate.


On Wed, Nov 25, 2015 at 4:39 AM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:

> Hi,
>
> I am working on the TOSCA CSAR plugin for murano and so far am able to
> successfully import an application definition archive of my CSAR example to
> murano.
> However, when I try to add the imported application to an environment I
> get this error from Murano Dashboard:
>
> DEBUG:muranodashboard.common.cache:Using cached value from
> /tmp/muranodashboard-cache/apps/91/4c2bfd5d504419a94a9affb7af809a/package_fqn.
> DEBUG:muranodashboard.catalog.views:Clearing forms data for application
> io.murano.apps.generated.CsarHelloWorld.
> DEBUG:muranodashboard.catalog.views:Clearing any leftover wizard step data.
> DEBUG:muranodashboard.common.cache:Using cached value from
> /tmp/muranodashboard-cache/apps/91/4c2bfd5d504419a94a9affb7af809a/ui/ui.yaml.
> DEBUG:muranodashboard.common.cache:Using cached value from
> /tmp/muranodashboard-cache/apps/91/4c2bfd5d504419a94a9affb7af809a/package_fqn.
> DEBUG:muranodashboard.dynamic_ui.services:Using data {} for app
> io.murano.apps.generated.CsarHelloWorld
> DEBUG:muranodashboard.dynamic_ui.services:Using in-memory forms for app
> io.murano.apps.generated.CsarHelloWorld
> DEBUG:muranodashboard.common.cache:Using cached value from
> /tmp/muranodashboard-cache/apps/91/4c2bfd5d504419a94a9affb7af809a/ui/ui.yaml.
> DEBUG:muranodashboard.common.cache:Using cached value from
> /tmp/muranodashboard-cache/apps/91/4c2bfd5d504419a94a9affb7af809a/package_fqn.
> DEBUG:muranodashboard.dynamic_ui.services:Using data {} for app
> io.murano.apps.generated.CsarHelloWorld
> DEBUG:muranodashboard.dynamic_ui.services:Using in-memory forms for app
> io.murano.apps.generated.CsarHelloWorld
> INFO:muranodashboard.dynamic_ui.forms:Creating form workflowManagement
> INFO:muranodashboard.dynamic_ui.forms:Creating form group0
> DEBUG:muranodashboard.api:Murano::Client http://localhost:8082/>
> DEBUG:muranoclient.common.http:curl -i -X GET -H 'X-Auth-Token:
> 324759651d234c4eaf08f6093dfd7000' -H 'Content-Type: application/json' -H
> 'User-Agent: python-muranoclient'
> http://localhost:8082//v1/catalog/packages/914c2bfd5d504419a94a9affb7af809a
> DEBUG:muranoclient.common.http:
> HTTP/1.1 200 OK
> Date: Wed, 25 Nov 2015 01:31:12 GMT
> Connection: keep-alive
> Content-Type: application/json
> Content-Length: 560
> X-Openstack-Request-Id: req-b6759ab2-04b4-4882-ac95-3ac06f970cb5
>
> {"updated": "2015-11-24T23:28:52", "description": "Template for deploying
> a single server with predefined properties.", "tags":
> ["TOSCA-CSAR-generated"], "class_definitions":
> ["io.murano.apps.generated.CsarHelloWorld"], "is_public": false, "id":
> "914c2bfd5d504419a94a9affb7af809a", "categories": [], "name":
> "csar_hello_world", "created": "2015-11-24T23:28:52", "author": "OASIS
> TOSCA TC", "enabled": true, "supplier": {}, "fully_qualified_name":
> "io.murano.apps.generated.CsarHelloWorld", "type": "Application",
> "owner_id": "1fee909728c54a698c96f0f7853412ae"}
>
> DEBUG:muranoclient.common.http:curl -i -X GET -H 'X-Auth-Token:
> 324759651d234c4eaf08f6093dfd7000' -H 'Content-Type: application/json' -H
> 'User-Agent: python-muranoclient'
> http://localhost:8082//v1/environments/b8d83a0b6fde465ab9de013f084518d4
> DEBUG:muranoclient.common.http:
> HTTP/1.1 200 OK
> Date: Wed, 25 Nov 2015 01:31:12 GMT
> Connection: keep-alive
> Content-Type: application/json
> Content-Length: 245
> X-Openstack-Request-Id: req-0ccb2b46-8a58-418f-b063-63067042e3f6
>
> {"status": "ready", "updated": "2015-11-24T23:29:11", "created":
> "2015-11-24T23:29:11", "tenant_id": "1fee909728c54a698c96f0f7853412ae",
> "acquired_by": null, "version": 0, "services": [], "id":
> "b8d83a0b6fde465ab9de013f084518d4", "name": "env1"}
>
> DEBUG:muranodashboard.common.cache:Using cached value from
> /tmp/muranodashboard-cache/apps/91/4c2bfd5d504419a94a9affb7af809a/ui/ui.yaml.
> DEBUG:muranodashboard.common.cache:Using cached value from
> /tmp/muranodashboard-cache/apps/91/4c2bfd5d504419a94a9affb7af809a/package_fqn.
> DEBUG:muranodashboard.dynamic_ui.services:Using data {} for app
> io.murano.apps.generated.CsarHelloWorld
> DEBUG:muranodashboard.dynamic_ui.services:Using in-memory forms for app
> io.murano.apps.generated.CsarHelloWorld
> DEBUG:muranoclient.common.http:curl -i -X GET -H 'X-Auth-Token:
> 324759651d234c4eaf08f6093dfd7000' -H 'Content-Type: application/json' -H
> 'User-Agent: python-muranoclient'
> http://localhost:8082//v1/catalog/packages/914c2bfd5d504419a94a9af

[openstack-dev] [puppet][murano] Launchpad project created

[Ekaterina Chernova]

Hi all,

as you know murano started creating puppet manifests.
They are located at the corresponding repository
[1]

And this is just a notification, that the separate project
 [2]to track puppet-related activities
is created and
puppet-openstack  [2] group is
selected as a maintainer.

Currently, there is just one bug there, but please, don't forget to triage
new bugs in this repository.

[1] - https://github.com/openstack/puppet-murano
[2] - https://launchpad.net/puppet-murano
[3] - https://launchpad.net/~puppet-openstack

Regards,
Kate.
__
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] Outreachy: Interest in contributing to open-source

[Ekaterina Chernova]

Hi Yolande,

welcome to OpenStack and open source!

We gladly introduce you with Murano project!

Topic 'Implementation of tagging heat stacks, created by murano' is already
taken,
but we can offer you another one after talking to you about what you are
interesting in.

You can go to #murano channel on IRC node and reach me (katyafervent) or
someone else.
Also, you can contact me directly by mail.


Regards,
Kate.


On Sat, Sep 26, 2015 at 11:20 PM, Amate Yolande 
wrote:

> Hello
>
> My name is Amate Yolande from Buea Cameroon. I am new to open source
> and I am interested in participating in the Outreachy. I would like to
> work on the "Murano - Implementation of tagging heat stacks, created
> by murano" project and would like to get some directives on how to
> familiarize myself with the project. So far I have been able to
> install and test OpenStack from dev-stack on a spare computer using a
> local network at home.
>
> Thanks
> Yolande
>
> __
> 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] [murano] Fix order of arguments in assertEqual

[Ekaterina Chernova]

Hi!

Good catch. Have no objections for fixing it right now.

Regards,
Kate.


On Thu, Sep 24, 2015 at 10:58 AM, Bulat Gaifullin 
wrote:

> +1
>
> > On 24 Sep 2015, at 10:45, Tetiana Lashchova 
> wrote:
> >
> > Hi folks!
> >
> > Some tests in murano code use incorrect order of arguments in
> assertEqual.
> > The correct order expected by the testtools is
> >
> > def assertEqual(self, expected, observed, message=''):
> > """Assert that 'expected' is equal to 'observed'.
> >
> > :param expected: The expected value.
> > :param observed: The observed value.
> > :param message: An optional message to include in the error.
> > """
> >
> > Error message has the following format:
> >
> > raise mismatch_error
> > testtools.matchers._impl.MismatchError: !=:
> > reference = 
> > actual= 
> >
> > Use of arguments in incorrect order could make debug output very
> confusing.
> > Let's fix it to make debugging easier.
> >
> > Best regards,
> > Tetiana Lashchova
> >
> __
> > 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] [murano][merlin] murano APIv2 and murano future ui

[Ekaterina Chernova]

Hi Nikolay!

Thanks for starting this activity! This is a really hot topic.
We also used to have plan to migrate our API to pecan. [1]
This also can be discussed.

Do we have a blueprint for that? Could you please file it and attach
etherpad to a new blueprint.

[1] -
https://blueprints.launchpad.net/murano/+spec/murano-api-server-pecan-wsme

Thanks,
Kate.

On Wed, Sep 9, 2015 at 2:07 PM, Nikolay Starodubtsev <
nstarodubt...@mirantis.com> wrote:

> Hi all,
> Yesterday on IRC weekly meeting murano team decided to start collecting
> ideas about murano APIv2 and murano future ui. We have to etherpads for
> this purpose:
> 1) https://etherpad.openstack.org/p/murano-APIv2 - for murano API v2 ideas
> 2) https://etherpad.openstack.org/p/murano-future-ui-(Merlin) - for
> future ui ideas
>
> Feel free to write your ideas. If you have any questions you can reach me
> in IRC.
>
>
>
> Nikolay Starodubtsev
>
> Software Engineer
>
> Mirantis Inc.
>
>
> Skype: dark_harlequine1
>
> __
> 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] [murano] [dashboard] Remove the owner filter from "Package Definitions" page

[Ekaterina Chernova]

Agreed.

Currently, pagination is broken on "Package definitions" page now, so
removing that filter
will fix it back. Also, 'Other' tab looks unhelpful, admin should indicate
to witch tenant this package belongs to.
This improvement will be added later.

Regards,
Kate.

On Fri, Sep 4, 2015 at 1:06 PM, Alexander Tivelkov 
wrote:

> ​+1 on this.
>
> Filtering by ownership makes sense only on Catalog view (i.e. on the page
> of usable apps) ​but not on the admin-like console like the list of package
> definitions.
>
> --
> Regards,
> Alexander Tivelkov
>
> On Fri, Sep 4, 2015 at 12:36 PM, Dmitro Dovbii 
> wrote:
>
>> Hi folks!
>>
>> I want suggest you to delete owner filter (3 tabs) from Package
>> Definition page. Previously this filter was available for all users and we
>> agreed that it is useless. Now it is available only for admin but I think
>> this fact still doesn't improve the UX. Moreover, this filter prevents the
>> implementation of the search by name, because the work of the two filters
>> can be inconsistent.
>> So, please express your opinion on this issue. If you agree, I will
>> remove this filter ASAP.
>>
>> Best regards,
>> Dmytro Dovbii
>>
>> __
>> 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] [murano] Proposing Nikolai Starodubtsev for core

[Ekaterina Chernova]

+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-dev] [Murano] Should we move to #openstack-murano ?

[Ekaterina Chernova]

Hi guys!

Currently Murano holds the *#murano* IRC channel.

But all openstack projects have the openstack- prefix in their channel’s
name.

So I have a question: should we move to *#openstack-murano*?

I think it’s a good idea, since it’s more obvious to go to*
#openstack-murano* if one needs help with murano.

Do you know if anybody tried to get help at *#openstack-murano* and
discovered that this is not the official Murano channel ?

Would it be hard to migrate from one channel to another?

Regards,
Kate.
__
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] Discuss simulated-execution-mode-murano-engine blueprint

[Ekaterina Chernova]

Folks,

I have specific topic to discuss: how murano test-fixture will look like
and how it can be run.

The idea is to implement a unit-testing framework, similar to regular
frameworks for python or other languages,
which will allow to define test fixtures in MuranoPL.
A Test fixture is a regular muranoPL class definition, which methods are
the test cases.
When such fixture is included into Murano application package the
deployment of application may be tested  without running actual VM's.

Here is how the test fixture may look like:

Namespaces:
=: io.murano.apps.foo.tests
sys: io.murano.system
pckg: io.murano.apps.foo

Extends: io.murano.tests.TestFixture

Name: FooTest

Methods:
initialize:
Body:
*# Object model can be loaded from json file, or provided
directly in murano-pl code as a yaml insertion.*
*# - $.appJson:
new(sys:Resources).json('foo-test-object-model.json')*
- $.appJson:
- ?:
type: io.murano.apps.foo.FooApp
  name: my-foo-obj
  instance:
  ?:
  type: io.murano.resources.Instance
  ...

setUp:
Body:
- $.env: $.createEnvironment($.appJson)   # creates an instance
of std:Environment
- $.myApp: $.env.applications.where($.name='my-foo-obj').first()
*# mock instance spawning*
- mock($.myApp.instance, "deploy", "mockInstanceDeploy", $this)
- mock(res:Instance, deploy, "mockInstanceDeploy", $this)


testFooApp:
Body:
- $.env.deploy()
- $.assertEqual(true, $.myApp.getAttr('deployed'))

mockInstanceDeploy:
Arguments:
- mockContext
Body:
- Return:
   * # heat template*


io.murano.tests.TestFixture - is a base class, that contains set of
methods, needed in all the test-cases which inherit it, such as assertEqual
and other similar assertions.
All it contains a $.createEnvironment method which may be called at the
setUp phase (a method being run before each test case) to construct the
object model to run the test against.

Test developer will be able to mock some of the functions or method which
are out of the scope of the current test
(for example, interaction with other applications or classes from the
standard murano library, such as instance.deploy etc).
The mock will allow to override the actual method execution and provide the
expected output of the method.
The actual implementation of  mocking requires more thoughtful design,  so
I'll create a separate spec for it.

What do you think about the overall idea and the test syntax proposed above?


On Wed, Jun 3, 2015 at 5:15 PM, Ekaterina Chernova 
wrote:

> Hi all!
>
> I'd like to discuss first implementation thoughts about this [1]
> blueprint, that we want to implement in Liberty.
> This feature is supposed to increase the speed of application development.
>
> Now engine interacts with API to get input task and packages.
>
> Items, planned to implement first would enable loading local task and new
> package, without API and Rabbit involved.
>
> After that simple testing machinery will be added to MuranoPL: mock
> support and simple test-runner.
>
> So user can test application methods as he wants by creating simple tests.
> Deployment parameters, such as heat stack and murano execution
> plan outputs
> may be set as returned value in tests.
>
> Finally, tests may be placed into a murano package for easier package
> verification and later modification.
>
> I'm going to write specification soon. But before, we need to prepare list
> of functions, that are needed to
> implement simple mocking machinery in MuranoPL.
>
> Please, leave your thoughts here or directly in the blueprint.
>
> Regards, Kate.
>
>
> [1] -
> https://blueprints.launchpad.net/murano/+spec/simulated-execution-mode-murano-engine
>
__
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] Watch new murano demos

[Ekaterina Chernova]

Hi all!

Recently murano team has recorded some demos describing features,
introduced in Kilo.
They can be found at murano wiki page [1].

Demo - is the easiest way to stay in touch with project news!

The list of updated demos:


   - Importing Murano Packages from Murano Repository
   
   - Plugins Opportunity 
   - New UI changes in Kilo 
   - Chef and Puppet executors in murano-agent
   
   - Steps of creation K8S applications with murano.
   


Follow murano channel on youtube [2] to stay tuned.

[1] - https://wiki.openstack.org/wiki/Murano/Screencasts
[2] -
https://www.youtube.com/playlist?list=PLdgU5edjetW_xCiO184uBsKkz6qmiIjZx
__
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

[Ekaterina Chernova]

Folks,

nice idea.

Who is wishing to look through all bugs in murano and move to murano-apps
project appropriate ones?

Regards,
Kate.



On Tue, Jun 9, 2015 at 2:49 PM, Kirill Zaitsev 
wrote:

> +1
>
> Can’t find any objectsions to separating murano-apps from murano.
>
> --
> Kirill Zaitsev
> Murano team
> Software Engineer
> Mirantis, Inc
>
> On 8 Jun 2015 at 17:13:22, Dmitro Dovbii (ddov...@mirantis.com) wrote:
>
>  Hi, Serg!
> Nice!
> Why only bug tracking?
> I'm looking forward to the first blueprint submitting :)
>
> Regards,
> Dmytro Dovbii
>
> 2015-06-08 16:34 GMT+03:00 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 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] [Murano] python-openstackclient support

[Ekaterina Chernova]

Hi all!

I support the idea!

Kirill, how much time do you think blueprint implementation will take?

On Tue, Jun 9, 2015 at 2:46 PM, Kirill Zaitsev 
wrote:

>
> https://blueprints.launchpad.net/python-muranoclient/+spec/openstack-client-plugin-support
>
> I’ve done that a while ago, already =).
>
> Could you please approve it?
>
> --
> Kirill Zaitsev
> Murano team
> Software Engineer
> Mirantis, Inc
>
> On 9 Jun 2015 at 11:45:56, Serg Melikyan (smelik...@mirantis.com) wrote:
>
> 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
>
>
> __
> 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-dev] [Murano] Discuss simulated-execution-mode-murano-engine blueprint

[Ekaterina Chernova]

Hi all!

I'd like to discuss first implementation thoughts about this [1] blueprint,
that we want to implement in Liberty.
This feature is supposed to increase the speed of application development.

Now engine interacts with API to get input task and packages.

Items, planned to implement first would enable loading local task and new
package, without API and Rabbit involved.

After that simple testing machinery will be added to MuranoPL: mock support
and simple test-runner.

So user can test application methods as he wants by creating simple tests.
Deployment parameters, such as heat stack and murano execution
plan outputs
may be set as returned value in tests.

Finally, tests may be placed into a murano package for easier package
verification and later modification.

I'm going to write specification soon. But before, we need to prepare list
of functions, that are needed to
implement simple mocking machinery in MuranoPL.

Please, leave your thoughts here or directly in the blueprint.

Regards, Kate.


[1] -
https://blueprints.launchpad.net/murano/+spec/simulated-execution-mode-murano-engine
__
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

[Ekaterina Chernova]

+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
>  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

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

[Ekaterina Chernova]

+1

Welcome!

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

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

[Ekaterina Chernova]

Hi Filip and Serg!

I support the idea!

Let's discuss more details in IRC and summarize everything on the next
community meeting on Tuesday.

Regards,
Kate.

On Thu, Apr 2, 2015 at 11:31 AM, Filip Blaha  wrote:

>  Hi Serg
>
> we can inspire in other projects like sahara. Important is that pylint job
> should produce reasonable size meaningful output. Pylint without any
> configuration produces huge output. So we should point out which code
> checks are interesting for us and configure pylint accordingly. I will do
> some research on that.
>
> Regards
> Filip
>
>
> On 04/01/2015 05:57 PM, Serg Melikyan wrote:
>
> 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:unsubscribehttp://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] [murano] how can deploy environment with useEnvironmentNerwork=false

[Ekaterina Chernova]

Hi Choe!

Why do you want to set this option to false?
In that way new instance will not be connected to the environment network.

Do you have any issues with the deployment?

If you still want to try the deployment without handling networks by
default,
you need to set default value of specified  parameter to 'false' here

[1] and re-import murano core library.

You can contact us at #murano channel.

[1] -
https://github.com/stackforge/murano/blob/master/meta/io.murano/Classes/resources/Instance.yaml

Regards,
Kate.

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
>
>
__
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] Translation usage suggestion

[Ekaterina Chernova]

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

Re: [openstack-dev] [Murano] Oslo.messaging error

[Ekaterina Chernova]

Hi!

I recommend you to create separate user and password in Rabbit MQ and do
not use 'quest' user.
Don't forget to edit config file.

I recommend you to go to our IRC channel #murano Freenode. We will help you
to set up your environment step by step!

Regards,
Kate.

On Thu, Dec 11, 2014 at 10:12 AM,  wrote:

>
>
>
>
>
>
> HI Team,
>
>
>
> I am installing Murano on the Ubuntu 14.04 Juno setup and when I try the
> below install murano-api I encounter the below error. Please assist.
>
>
>
> When I install
>
>
>
> I am using the Murano guide link provided below:
>
> https://murano.readthedocs.org/en/latest/install/manual.html
>
>
>
>
>
> I am trying to execute the section 7
>
>
>
> 1.Open a new console and launch Murano API. A separate terminal is
> required because the console will be locked by a running process.
>
> 2. $ cd ~/murano/murano
>
> 3. $ tox -e venv -- murano-api \
>
> 4. > --config-file ./etc/murano/murano.conf
>
>
>
>
>
> I am getting the below error : I have a Juno Openstack ready and trying to
> integrate Murano
>
>
>
>
>
> 2014-12-11 12:28:03.676 9524 INFO eventlet.wsgi [-] (9524) wsgi starting
> up on http://0.0.0.0:8082/
>
> 2014-12-11 12:28:03.677 9524 DEBUG murano.common.statservice [-] Updating
> statistic information. update_stats
> /root/murano/murano/murano/common/statservice.py:57
>
> 2014-12-11 12:28:03.677 9524 DEBUG murano.common.statservice [-] Stats
> object:  object at 0x7ff72837d410> update_stats
> /root/murano/murano/murano/common/statservice.py:58
>
> 2014-12-11 12:28:03.677 9524 DEBUG murano.common.statservice [-] Stats:
> Requests:0  Errors: 0 Ave.Res.Time 0.
>
> Per tenant: {} update_stats
> /root/murano/murano/murano/common/statservice.py:64
>
> 2014-12-11 12:28:03.692 9524 DEBUG oslo.db.sqlalchemy.session [-] MySQL
> server mode set to
> STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
> _check_effective_sql_mode
> /root/murano/murano/.tox/venv/local/lib/python2.7/site-packages/oslo/db/sqlalchemy/session.py:509
>
> 2014-12-11 12:28:06.721 9524 ERROR oslo.messaging._drivers.impl_rabbit [-]
> AMQP server 192.168.x.x:5672 closed the connection. Check login
> credentials: Socket closed
>
>
>
> Warm Regards,
>
> *Raghavendra Lad*
>
>
>
> --
>
> 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
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [murano] Murano documentation needs improvement

[Ekaterina Chernova]

Hi, All!

I'd like to keep an attention to Murano documentation.
Documentation is really important and leaves the impression of the whole
project since it's a first thing with what user or developer faced.

So we need to concentrate on it's improvement.

I prepared an etherpad [1]
with the list of possible changes.
Anyone is welcome to add items and to take on their implementation since
it's a good way to get involved into the project.

Please, contact us at #murano channel if you have any questions.

Good luck everyone!
Kate.

[1] - https://etherpad.openstack.org/p/murano-docs
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Field 'name' is removed from Apps dynamic UI markup, should 'Version' be changed?

[Ekaterina Chernova]

Hi guys!

I agreed with Stan suggestion. We also need to track somewhere in the
documentation for mapping between the Murano version and Dynamic UI version.

BTW, what about to keep version values in integer, so the next one would be
3?

Regards, Kate.


On Sun, Jul 6, 2014 at 4:21 PM, Stan Lagun  wrote:

> I we increment version to say 2.1 we could add code to dashboard to check
> for markup version and if it encounters version 2.0 to print verbose error
> telling how to migrate markup to 2.1.
> I don't see how both version can be supported simulteniously but at lease
> Version attribute must be checked and forms older version must fail with
> descriptive message rather than causing unpredictable behavior.
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>  
>
>
> On Fri, Jul 4, 2014 at 8:24 PM, Timur Sufiev  wrote:
>
>> Hi, folks!
>>
>> Recently we had decided to change a bit how Murano's dynamic UI works,
>> namely do not explicitly specify 'name' field in first 'Add
>> Application' form, but add it here automatically, since every
>> component in Murano has a name. To avoid confusion with the 'name'
>> field added by hand to the first form's markup, 'name' field on the
>> first step will be forbidden and processing of an old UI markup which
>> has such field will cause an exception. All these changes are
>> described in the blueprint [1] in a greater detail.
>>
>> What is not entirely clear to me is whether should we increase
>> 'Version' attribute of UI markup or not? On one hand, the format of UI
>> markup is definitely changing - and old UI definitions won't work with
>> the UI processor after [1] is implemented. It is quite reasonable to
>> bump a format's version to reflect that fact. On the other hand, we
>> will hardly support both format versions, instead we'll rewrite UI
>> markup in all existing Murano Apps (there are not so many of them yet)
>> and eventually forget that once upon a time the user needed to specify
>> 'name' field explicitly.
>>
>> What do you think?
>>
>> [1]
>> https://blueprints.launchpad.net/murano/+spec/dynamic-ui-specify-no-explicit-name-field
>>
>> --
>> 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