Cloud Foundry yaml 解析错误答案

【问题标题】：Cloud Foundry yaml parse errorCloud Foundry yaml 解析错误
【发布时间】：2015-06-17 21:54:49
【问题描述】：

当我尝试为 memcached 服务代理推送 yaml 文件时，我在 cf push 上遇到错误：

#cf push
FAILED
Error reading manifest file:
yaml: [] mapping values are not allowed in this context at line 2, column 7
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:95 (0x2c0d87)
/usr/local/go/src/pkg/runtime/panic.c:248 (0x16276)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:144 (0x2c1609)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:161 (0x2c17e5)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:471 (0x2c3cd4)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:196 (0x2c1c6e)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:394 (0x2c336d)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:193 (0x2c1d38)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:171 (0x2c199e)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/cloudfoundry-incubator/candiedyaml/decode.go:137 (0x2c146d)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/manifest/manifest_disk_repository.go:82 (0xb13ef)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/manifest/manifest_disk_repository.go:50 (0xb0f72)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/manifest/manifest_disk_repository.go:33 (0xb0e13)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/manifest/manifest.go:1 (0xb300e)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/commands/application/push.go:377 (0x23e2c3)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/commands/application/push.go:356 (0x23e062)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/commands/application/push.go:120 (0x23ada2)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/command_runner/runner.go:50 (0xa70a9)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/command_runner/runner.go:1 (0xa73d4)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/tmp/cli_gopath/src/github.com/cloudfoundry/cli/cf/app/app.go:76 (0x8ecce)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/codegangsta/cli/command.go:101 (0xcb140)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/Godeps/_workspace/src/github.com/codegangsta/cli/app.go:125 (0xc9654)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/main/main.go:154 (0x3729)
/Users/pivotal/go-agent/pipelines/Mac-OSX-Testing/src/github.com/cloudfoundry/cli/main/main.go:91 (0x2eb9)
/usr/local/go/src/pkg/runtime/proc.c:220 (0x1804f)
/usr/local/go/src/pkg/runtime/proc.c:1394 (0x1a580)

很明显，我的 yaml 文件有些问题。但我不知道是什么。这是我所拥有的：

domain: cloudeast.mycompany.com
  nats:  secret
    machines:
      - 10.10.100.10
    password: secret
    port: 4222
    user: nats

  networks:
    apps: default
    management: default

  memcache_broker:
    broker_password: secret
    memcache:
      vip: 10.100.100.100:11211
      servers:
      - 10.100.100.101:11211
      - 10.100.100.102:11211
    plans:
      small:
        name: small
        description: A small cache with no redundency
        free: true

  memcache_hazelcast:
    heap_size: 512M
    host:
      src_api: https://memcache-hazelcast.cf-deployment.com
      password: secret
    memcache:
      secret_key: secret
    hazelcast:
      max_cache_size: 268435456
      machines:
        zone1:
        - 10.100.100.101
        zone2:
        - 10.100.100.102
    plans:
      small:
        backup: 0
        async_backup: 1
        eviction_policy: LRU
        max_idle_seconds: 86400
        max_size_used_heap: 100
      medium:
        backup: 0
        async_backup: 1
        eviction_policy: LRU
        max_idle_seconds: 86400
        max_size_used_heap: 200

我能否就为什么这个 yaml 文件无法正确解析获得一些帮助？

【问题讨论】：

@Anthon 解释了为什么您的 YAML 无效。但是在更正之后，这将不是一个有效的 cf 清单。您是打算将代理作为在 CF 本身上运行的应用程序运行，还是以某种方式独立运行（例如 BOSH-deployed），因为您文件中的某些数据看起来像是用于部署 CF 的 BOSH 清单本身，而不是在 CF 上运行的应用程序。
@AmitKumarGupta 感谢您对此进行了扩展。我对cloudfoundry不熟悉，我查看了他们的文档页面，可以找到任何与配置文件格式相关的内容，并在搜索了10分钟后放弃了。
在 CF 上运行的应用程序可以使用命令行标志或通过称为“清单”文件的配置文件进行配置。看起来您是故意制作该文件的，以下是有关清单文件的更多详细信息：docs.cloudfoundry.org/devguide/deploy-apps/manifest.html。目前尚不清楚您要解决什么更大的问题。由于您对 Cloud Foundry 不太熟悉，您确定需要从 memcached 部署服务代理吗？

标签： yaml cloud-foundry

【解决方案1】：

在第一行，您有一个标量 (domain)，后跟一个冒号 (:)，后跟一个标量 (cloudeast.mycompany.com)，这意味着在顶部，非缩进级别，您开始映射和domain 是键标量，cloudeast.mycompany.com 是值标量。

在下一行中，您应该再次拥有一个键标量，并且它必须缩进与上一行相同的级别（或者您以流结尾完成顶级映射 (...)或开始一个新文档 (---)。你开始一个缩进值，它是一个映射，解析器不知道你想用它做什么。

人们只能尝试并猜测您尝试做什么。如果cloudeast.mycompany.com 是域的名称，则应将其设为新的缩进标量值（使用键name），然后键machines 会出现相同的缩进错误。和以下3个键，之后文件就OK了：

domain: 
  name: cloudeast.mycompany.com   # scalar key "name" added
  nats:  secret
  machines:                       # this scalar key and next 3  dedented
  - 10.10.100.10
  password: secret
  port: 4222
  user: nats

  # from here everything as it was
  networks:
    apps: default
    management: default

  memcache_broker:
    broker_password: secret
    memcache:
      vip: 10.100.100.100:11211
      servers:
      - 10.100.100.101:11211
      - 10.100.100.102:11211
    plans:
      small:
        name: small
        description: A small cache with no redundency
        free: true

  memcache_hazelcast:
    heap_size: 512M
    host:
      src_api: https://memcache-hazelcast.cf-deployment.com
      password: secret
    memcache:
      secret_key: secret
    hazelcast:
      max_cache_size: 268435456
      machines:
        zone1:
        - 10.100.100.101
        zone2:
        - 10.100.100.102
    plans:
      small:
        backup: 0
        async_backup: 1
        eviction_policy: LRU
        max_idle_seconds: 86400
        max_size_used_heap: 100
      medium:
        backup: 0
        async_backup: 1
        eviction_policy: LRU
        max_idle_seconds: 86400
        max_size_used_heap: 200

当然，您也忽略了 cloudeaset.mycompany.com 的值。在这两种情况下，YAML 文件的顶层都是具有单个键标量的映射：domain。该键的值再次是与 nats、networks、memcache_broker 等键的映射

【讨论】：