slagun's profile - activity

2016-03-04 08:44:09 -0600 answered a question Requesting Urgent Help Regarding Murano Openstack

TimeoutException indicates that Murano deployment engine didn't received in time a response from its guest agent on VM. Engine and agent talk to each other via RabbitMQ server that must be accessible to both parties. Usually the error happens because one of the following:

  1. Incorrect RabbitMQ parameters in [rabbitmq] section of murano.conf. For example host = 127.0.0.1

  2. There is no guest agent on VM (wrong image)

  3. Network connectivity issues between VM and RabbitMQ

  4. Some issue with cloud-init that caused agent config not to be updated with correct parameters on first boot

  5. Used flavor is too small or/and VM is running extremely slow and it takes ages to run script

2015-08-06 12:44:34 -0600 answered a question [Murano] How to use Murano DynamicUI forms to generate Heat templates?

There is no problem to create application that asks something from user and then generate Heat template with those values. Murano aplications are written using MuranoPL programming language which is completely object-oriented. There is a HeatStack class that represents one Heat stack. You can use environment's default stack or create your own. And it has update() method that can be used to merge a snippet into it and push() method to submit your changes to the Heat. And of cause MuranoPL is powerful enough to generate template of any complexity. That's how classes from MuranoPL core library work https://github.com/openstack/murano/tree/master/meta/io.murano/Classes/resources (https://github.com/openstack/murano/t...)

However there might be certain problems with making user chose from a list of options rather than have a plain-text field. The problem is that currently applications cannot hook into UI form life-cycle. For example you can define drop-down in our form and provide a list of available options. But you cannot hook it to MuranoPL function that will ask OpenStack and then populate returned values to that drop down. In other words you app begins to work after user has submitted his input.To certain degree this is solved by the fact that dUI forms have built-in support for image, flavor and recently network selection. This issue most likely will be addressed in OpenStack M release