I dug down quite a bit, and see that in openstack_plugin_common.__init__ in
the cosmo_list method of the NovaClientWithSugar class, I wrapped a call to
getattr with a try:except and see.
02:22:47 | I | nova_plugin.server.create | {u'args': OrderedDict(),
u'openstack_config': {'username': 'dewayne'
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 20 September 2017, 10:30 am PDT.
The report for your podling will fo
Regarding #1, I agree with Avia here. Substitution mapping is intended as
an extension of requirements-matching-capabilities. As you know, a
requirement can be as minimal as just specifying a capability type, but
could optionally additionally specify a node and even include a node filter
with more
1) Substitutable nodes (abstract nodes) are defined by their type. And a
node type should represent specific node/subsystem characteristics. Having
two node types ( with the same name) that represent different logical
entities seems odd, and indicates a possible bug in the design. That is
another r
Hi,
With respect to substituting stored service templates, I have few things to be
clarified
1) Handling substitution when multiple service templates matches for the
abstract node type .
Would the 1st match would be used for substitution or Are we looking
at policy to enable user to s
Is this everything?
It seems like this never reached the actual API call telling Nova to create
a server, but rather failed in the section where image/flavor, keypair,
security groups and nics are configured for the server
( see
https://github.com/cloudify-cosmo/cloudify-openstack-plugin/blob/maste
