Re: Deployment manifest not recognized by BOSH


Dmitriy Kalinin
 

With YAML it's very much different to have

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*

vs

*---*
*networks: *
*- **type: dynamic*

First represents real classes being serialized, but the second shows
regular hashes (maps). There is no way bosh can deserialize the first
example since it does not have these objects.

On Tue, Jun 9, 2015 at 11:26 AM, John Wong <gokoproject(a)gmail.com> wrote:

I am not sure why it fails now, but my two cents are why not just
serialized the object?

In the case of python, i would see that if I try to save an object like in
your case: http://pyyaml.org/wiki/PyYAMLDocumentation#Objects
But I would write a method to convert my object to basic dictionary (in
Python), which I can easily convert into YAML using pyyaml library.

John

On Tue, Jun 9, 2015 at 11:47 AM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I am aware that this does not have anything to do with BOSH but when a
ruby object is converted to yaml, this format is appended automatically.

Couple of months ago, I was able to deploy with a manifest of this format
but now on a new BOSH deployment, I am not able to.

I am using the default yaml gem in ruby to transform from object to yaml
which appends this type of info for each objects that it transforms.

Any ideas would be great on this, or are you saying that the manifest is
invalid with this '!' info?

Thanks,
Kinjal


On Tue, Jun 9, 2015 at 7:10 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Your manifest is wrong "*- !ruby/object:AWSDynamicNetworkBean *" are
not a yaml field.
You script using to_yaml is just wrong, nothing related to bosh.


On Tue, Jun 9, 2015 at 7:08 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

would be great if someone could please help me with this matter.

Regards,
Kinjal

On Mon, Jun 8, 2015 at 6:25 PM, Kinjal Doshi <kindoshi(a)gmail.com>
wrote:

Hi,

I am trying to use manifest that is generated using the to_yaml
transformation technique in Ruby.

However, this deployment manifest is not recognized by bosh because it
has comments that detail the class names like:

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*
* cloud_properties: !ruby/object:AWSNetworkCPBean *
* security_groups: *
* - docker*
* - bosh*
* subnet: *
* name: default*
*- !ruby/object:AWSDynamicNetworkBean *
* type: vip*
* cloud_properties: {}*

As can be seen in above snippet, to_yaml adds object description using
'!' sign.

On using the command:

bosh deployment <manifest_file_path>

The following error is observed:

Usage: deployment [<filename>]

Removing the object details starting at '!' seems to resolve this
error.

However, this was not happening with previous version of bosh_cli. I
don't remember the previous version that I was using. Current version being
used by me is: bosh cli-1.2978.0

Would be great if some one can please help me with this matter.


Regards,
Kinjal



_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.