Giter VIP home page Giter VIP logo

cf-docs's Introduction

cf-docs

NOTICE:

This repository is now deprecated. Please do not submit any new pull requests against it.

We announced a change to how the documentation is published on the vcap-dev mailing list on February 3, 2014.

The new website for Cloud Foundry open source documentation is docs.cloudfoundry.org.

There are new documentation repositories.

For details on how documentation is now published, see the readme on the docs-book-cloudfoundry repo.

The open source documentation is now split across multiple repos:

  • Cloud Foundry Concepts: a guide to the underlying concepts and architecture.
  • Developer Guide: step-by-step instructions and reference material for developers pushing applications to Cloud Foundry.
  • Services: information about extending Cloud Foundry with custom services, and the service broker API.
  • Buildpacks: a guide to developing your own buildpacks.
  • Deploying Cloud Foundry: instructions for operators deploying Cloud Foundry on various IaaS (AWS, OpenStack, etc.) using BOSH
  • Running Cloud Foundry: information for operators running Cloud Foundry.
  • BOSH: in-depth documentation on BOSH.

For documentation relating to the Pivotal Web Services Marketplace, please see PWS Services

cf-docs's People

Contributors

andreasmaier avatar andypiper avatar animatedmax avatar benjsmi avatar brunssen avatar byllc avatar cf-frameworks avatar d avatar danhigham avatar drnic avatar dsboulder avatar frodenas avatar gberche-orange avatar goonzoid avatar hochm avatar jasonlanderson avatar kehati avatar laur-craciun avatar marlboromoo avatar mmb avatar motdotla avatar mpmcgarry avatar mrdavidlaing avatar mreider avatar programsam avatar rajdeepd avatar scottfrederick avatar stephenitis avatar tpradeep avatar ytolsk avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

cf-docs's Issues

Update location of stemcell

The location of stemcell is no longed as documented.
To get latest stemcell for bosh/openstack, :

$ wget http://bosh-jenkins-artifacts.s3.amazonaws.com/bosh-stemcell/openstack/bosh-stemcell-latest-openstack-kvm-ubuntu.tgz

node-service-bindings missing critical information

The note at the top of the node-service-binding doc states:

Note: The auto-configuration functionality described on this page is not yet supported in Cloud Foundry v2.

but there is no information on how to manually configure services while we wait for auto-configuration to catch up.

How are node developers supposed to use services in V2?

cf-docs building does not detect broken local markdown hrefs

It would be great if cf-docs would build (e.g. on travis-ci) and would detect broken markdown hrefs, at least local references, and possibly reject PRs/commits with broken links.

I inadvertandly introduced a broken link in c33c282 sorry.

Other refactorings such as renaming a page will likely introduce other similar regressions.

BOSH job monit file can be empty

From: cloudfoundry/bosh#293 and @msackman

Bosh currently doesn't allow you to have a jobless release. This is very annoying as you're initially developing a release where all you care about is getting things compiled, and forces you to invent phantom jobs which wastes time.

That said, it's also very useful to have a job onto which your packages are deployed so that you can inspect your progress. In the end I created a phantom job which bosh/monit was happy with, however, I've just discovered by trial and error that having an empty monit file works and does not upset bosh or monit (which perhaps makes a mockery of the error you get if you have no monit file at all). This should mentioned in the documentation(!) and in the inevitable (and much needed) tutorials on how to develop a bosh release.

There should perhaps also be a built-in "deploy-all" job that simply finds every package in the release and depends on them all.

Take down any mention of micro cloud foundry

Micro cloud foundry is no longer available, yet the existence of pages such as this lead users to take steps to get one. If there is valuable content on these pages it needs to be harvested and put someplace else and we need to remove all mentions of micro cloud foundry (except maybe to say that it is no longer and maybe point people to bosh lite).

bosh aws create gives error Access Denied (AWS::S3::Errors::AccessDenied)

After "bosh aws create " command I get the following error:-

/home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/gems/aws-sdk-1.8.5/lib/aws/core/client.rb:339:in return_or_raise': Access Denied (AWS::S3::Errors::AccessDenied) from /home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/gems/aws-sdk-1.8.5/lib/aws/core/client.rb:440:inclient_request'
from (eval):3:in get_object' from /home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/gems/aws-sdk-1.8.5/lib/aws/s3/s3_object.rb:1272:inget_object'
from /home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/gems/aws-sdk-1.8.5/lib/aws/s3/s3_object.rb:1058:in read' from /home/ubuntu/workspace/bosh/bosh_cli_plugin_aws/lib/bosh_cli_plugin_aws/s3.rb:51:inblock in fetch_object_contents'
from /home/ubuntu/workspace/bosh/bosh_common/lib/common/common.rb:65:in block in retryable' from /home/ubuntu/workspace/bosh/bosh_common/lib/common/common.rb:64:inloop'
from /home/ubuntu/workspace/bosh/bosh_common/lib/common/common.rb:64:in retryable' from /home/ubuntu/workspace/bosh/bosh_cli_plugin_aws/lib/bosh_cli_plugin_aws/s3.rb:50:infetch_object_contents'
from /home/ubuntu/workspace/bosh/bosh_cli_plugin_aws/lib/bosh_cli_plugin_aws/migrator.rb:81:in load_migrations_for_env' from /home/ubuntu/workspace/bosh/bosh_cli_plugin_aws/lib/bosh_cli_plugin_aws/migrator.rb:35:inenvironment_migrations'
from /home/ubuntu/workspace/bosh/bosh_cli_plugin_aws/lib/bosh_cli_plugin_aws/migrator.rb:40:in needs_migration?' from /home/ubuntu/workspace/bosh/bosh_cli_plugin_aws/lib/bosh_cli_plugin_aws/migrator.rb:11:inmigrate'
from /home/ubuntu/workspace/bosh/bosh_cli_plugin_aws/lib/bosh/cli/commands/aws.rb:145:in create' from /home/ubuntu/workspace/bosh/bosh_cli/lib/cli/command_handler.rb:57:inrun'
from /home/ubuntu/workspace/bosh/bosh_cli/lib/cli/runner.rb:59:in run' from /home/ubuntu/workspace/bosh/bosh_cli/lib/cli/runner.rb:18:inrun'
from /home/ubuntu/workspace/bosh/bosh_cli/bin/bosh:7:in <top (required)>' from /home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/bin/bosh:19:inload'
from /home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/bin/bosh:19:in <main>' from /home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/bin/ruby_noexec_wrapper:14:ineval'
from /home/ubuntu/.rvm/gems/ruby-1.9.3-p327@bosh/bin/ruby_noexec_wrapper:14:in `

'

Interest in Loggregator?

Is there any interest in having the example bosh deployment manifest include loggregator and loggregator/trafficcontroller?

deploying cf on vcloud documentation is outdated

When trying to follow documentation at [1], it fails during bosh_deployer install:

$ >    gem install bosh_deployer
    ERROR:  While executing gem ... (Gem::DependencyResolutionError)
        conflicting dependencies aws-sdk (= 1.8.5) and aws-sdk (~> 1.3.6)
      Activated aws-sdk-1.3.6 via:
        aws-sdk-1.3.6 (~> 1.3.6), bosh_aws_registry-0.2.2 (~> 0.2.2), bosh_deployer-1.4.1 (= 1.4.1)
      instead of (= 1.8.5) via:
        blobstore_client-1.1761.0 (~> 1.1761.0), bosh_cli-1.1761.0 (>= 1.0.2), bosh_deployer-1.4.1 (= 1.4.1)

[1] http://docs.cloudfoundry.com/docs/running/deploying-cf/vcloud/deploying_to_vcloud_director.html

Applying the vsphere documentation worked fine on vCD 5.1 to perform bosh_micro installation.

Build Tools doc is missing `org` and `space` settings for Maven

When we tried to use the Maven plugin as documented we got the following error message:

[ERROR] Failed to execute goal org.cloudfoundry:cf-maven-plugin:1.0.0:push (default-cli) on project REDACTED: An exception was caught while executing Mojo. The org is not set. -> [Help 1]

Once we provide org we get the same message for space. So it seems these two parameters are required.

More succinct Director documentation?

https://github.com/cloudfoundry/cf-docs/blob/master/source/docs/running/bosh/components/director.html.md

The page above goes into excruciating detail about the implementation details of a Director. Who is the intended audience for this page?

In my opinion some of the implementation details on this page (e.g. Reference to *Manager classes and specific Model objects) are likely to change frequently (even if they haven't in the past).

I'd suggest rewriting this page with a BOSH Release Deployer in mind.

cf target failed: 401 Unauthorized; CC: Authorization is required' (NATS::ServerError)

Hi.
I followed the steps in http://docs.cloudfoundry.com/docs/running/deploying-cf/openstack/install_cf_openstack.html.
I have OpenStack Folsom with Nova networking. Deployment with micro-bosh works, but when I try to target CF, I get:

    $ cf target http://api.192.168.200.2.xip.io:8080 
    Setting target to http://api.192.168.200.2.xip.io:8080... FAILED
    CFoundry::Unauthorized: 401: 401 Unauthorized

Checking vms, the cloud_controller job is showing failing, but intermittently.

$ bosh vms
Deployment `cf-demo'

Director task 191

Task 191 done

+---------------------+---------+---------------+-------------------------------+
| Job/index           | State   | Resource Pool | IPs                           |
+---------------------+---------+---------------+-------------------------------+
| cloud_controller/0  | failing | common        | 192.168.100.8                 |
| dea/0               | running | large         | 192.168.100.11                |
| health_manager/0    | running | common        | 192.168.100.9                 |
| nats/0              | running | common        | 192.168.100.4                 |
| nfs_server/0        | running | common        | 192.168.100.6                 |
| postgres/0          | running | common        | 192.168.100.2                 |
| router/0            | running | common        | 192.168.100.10, 192.168.200.2 |
| syslog_aggregator/0 | running | common        | 192.168.100.5                 |
| uaa/0               | running | common        | 192.168.100.7                 |
+---------------------+---------+---------------+-------------------------------+

VMs total: 9

At other times I run bosh vms and all jobs show as running.
I downloaded the logs for cloud_controller and in cloud_controller_ng/cloud_controller_ng.stderr.log I see a lot of entries of:

/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/1.9.1/gems/nats-0.4.26/lib/nats/client.rb:567:in `block in connection_completed': 'Authorization is required' (NATS::ServerError)
        from /var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/1.9.1/gems/nats-0.4.26/lib/nats/client.rb:506:in `call'
        from /var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/1.9.1/gems/nats-0.4.26/lib/nats/client.rb:506:in `receive_data'
        from /var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'
        from /var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'
        from /var/vcap/packages/cloud_controller_ng/cloud_controller_ng/lib/cloud_controller/runner.rb:92:in `run!'
        from /var/vcap/packages/cloud_controller_ng/cloud_controller_ng/bin/cloud_controller:12:in `<main>'

I saw an entry from Dr Nic with the same log output (https://groups.google.com/a/cloudfoundry.org/forum/#!topicsearch/Authorization$20is$20required/vcap-dev/sjPlwv1km-U). The suggested fix was to remove dns from the network in the deployment yml. Dr. Nic's post didn't specify which job, so I tried for just cloud_controller as well as all jobs. Neither changes made any difference.

cloud_controller_ng/cloud_controller_ng.log showing NATS registration log:

{"timestamp":1379299306.676946,"message":"reusing default serving domain: 192.168.200.2.xip.io","log_level":"info","source":"cc.db.domain","data":{},"thread_id":14223020,"fiber_id":37402740,"process_id":26794,"file":"/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/app/models/core/domain.rb","lineno":149,"method":"block in find_or_create_shared_domain"}
{"timestamp":1379299306.9081013,"message":"Connected to NATS - router registration","log_level":"info","source":"cf.registrar","data":{},"thread_id":14223020,"fiber_id":37402740,"process_id":26794,"file":"/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/1.9.1/gems/vcap_common-2.2.1/lib/cf/registrar.rb","lineno":62,"method":"register_with_router"}
{"timestamp":1379299306.9115846,"message":"Sending registration: {:host=>\"192.168.100.8\", :port=>9022, :uris=>[\"ccng.192.168.200.2.xip.io\", \"api.192.168.200.2.xip.io\"], :tags=>{:component=>\"CloudController\"}, :index=>0, :private_instance_id=>nil}","log_level":"debug","source":"cf.registrar","data":{},"thread_id":14223020,"fiber_id":37402740,"process_id":26794,"file":"/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/1.9.1/gems/vcap_common-2.2.1/lib/cf/registrar.rb","lineno":96,"method":"send_registration_message"}

Stemcells I've used:

$ bosh stemcells

+---------------+---------+--------------------------------------+
| Name          | Version | CID                                  |
+---------------+---------+--------------------------------------+
| bosh-stemcell | 877     | 2302e4fc-38ae-4d69-9319-ea9afde70770 |
| bosh-stemcell | 939     | 3ca5db47-6ac0-4dc5-9f0b-0127b08cfcb5 |
| bosh-stemcell | 962     | f717056b-ba51-4cf4-aea0-910157e63f4a |
| bosh-stemcell | 991     | 9581def9-66e7-47c2-950b-a586dded7898 |
+---------------+---------+--------------------------------------+

CF release:

$ bosh releases

+------+----------+-------------+
| Name | Versions | Commit Hash |
+------+----------+-------------+
| cf   | 138*     | adca9c45+   |
+------+----------+-------------+
(*) Currently deployed
(+) Uncommitted changes

Releases total: 1

Deployment yaml (as per instructions from 13/09/13), except persistent disks are 15GB):

$ cat ../../deployments/cf/demo.yml
<%
director_uuid = "c75204b0-0315-4a2c-95ce-ac7ef2ecc39c"
protocol = "http"
ip_address = "192.168.200.2"
common_password = "passw0rd"
root_domain = "#{ip_address}.xip.io"
deployment_name = "cf-demo"
%>
name: <%= deployment_name %>
director_uuid: <%= director_uuid %>

releases:
 - name: cf
   version: 138

compilation:
  workers: 3
  network: default
  reuse_compilation_vms: true
  cloud_properties:
    instance_type: m1.small

update:
  canaries: 1
  canary_watch_time: 30000-300000
  update_watch_time: 30000-300000
  max_in_flight: 4

networks:
  - name: floating
    type: vip
    cloud_properties: {}
  - name: default
    type: dynamic
    cloud_properties:
      security_groups:
      - cf-public
      - cf-private

resource_pools:
  - name: common
    network: default
    size: 8
    stemcell:
      name: bosh-stemcell
      version: latest
    cloud_properties:
      instance_type: m1.small

  - name: large
    network: default
    size: 1
    stemcell:
      name: bosh-stemcell
      version: latest
    cloud_properties:
      instance_type: m1.large

jobs:
  - name: nats
    template:
      - nats
    instances: 1
    resource_pool: common
    networks:
      - name: default
        default: [dns, gateway]

  - name: syslog_aggregator
    template:
      - syslog_aggregator
    instances: 1
    resource_pool: common
    persistent_disk: 15360
    networks:
      - name: default
        default: [dns, gateway]

  - name: postgres
    template:
      - postgres
    instances: 1
    resource_pool: common
    persistent_disk: 15360
    networks:
      - name: default
        default: [dns, gateway]
    properties:
      db: databases

  - name: nfs_server
    template:
      - debian_nfs_server
    instances: 1
    resource_pool: common
    persistent_disk: 15360
    networks:
      - name: default
        default: [dns, gateway]

  - name: uaa
    template:
      - uaa
    instances: 1
    resource_pool: common
    networks:
      - name: default
        default: [dns, gateway]

  - name: cloud_controller
    template:
      - cloud_controller_ng
    instances: 1
    resource_pool: common
    networks:
      - name: default
        default: [dns, gateway]
    properties:
      ccdb: ccdb

  - name: router
    template:
      - gorouter
    instances: 1
    resource_pool: common
    networks:
      - name: default
        default: [dns, gateway]
      - name: floating
        static_ips:
          - <%= ip_address %>

  - name: health_manager
    template:
      - health_manager_next
    instances: 1
    resource_pool: common
    networks:
      - name: default
        default: [dns, gateway]

  - name: dea
    template: dea_next
    instances: 1
    resource_pool: large
    networks:
      - name: default
        default: [dns, gateway]

properties:
  domain: <%= root_domain %>
  system_domain: <%= root_domain %>
  system_domain_organization: "demo"
  app_domains:
    - <%= root_domain %>
  support_address: http://support.<%= root_domain %>
  description: "Cloud Foundry v2 sponsored by Pivotal"

  networks:
    apps: default
    management: default

  nats:
    address: 0.nats.default.<%= deployment_name %>.microbosh
    port: 4222
    user: nats
    password: <%= common_password %>
    authorization_timeout: 10

  router:
    status:
      port: 8080
      user: gorouter
      password: <%= common_password %>

  dea: &dea
    memory_mb: 4096
    disk_mb: 16384
    directory_server_protocol: <%= protocol %>

  dea_next: *dea

  syslog_aggregator:
    address: 0.syslog-aggregator.default.<%= deployment_name %>.microbosh
    port: 54321

  nfs_server:
    address: 0.nfs-server.default.<%= deployment_name %>.microbosh
    network: "*.<%= deployment_name %>.microbosh"
    idmapd_domain: dfw2

  debian_nfs_server:
    no_root_squash: true

  databases: &databases
    db_scheme: postgres
    address: 0.postgres.default.<%= deployment_name %>.microbosh
    port: 5524
    roles:
      - tag: admin
        name: ccadmin
        password: <%= common_password %>
      - tag: admin
        name: uaaadmin
        password: <%= common_password %>
    databases:
      - tag: cc
        name: ccdb
        citext: true
      - tag: uaa
        name: uaadb
        citext: true

  ccdb: &ccdb
    db_scheme: postgres
    address: 0.postgres.default.<%= deployment_name %>.microbosh
    port: 5524
    roles:
      - tag: admin
        name: ccadmin
        password: <%= common_password %>
    databases:
      - tag: cc
        name: ccdb
        citext: true

  ccdb_ng: *ccdb

  uaadb:
    db_scheme: postgresql
    address: 0.postgres.default.<%= deployment_name %>.microbosh
    port: 5524
    roles:
      - tag: admin
        name: uaaadmin
        password: <%= common_password %>
    databases:
      - tag: uaa
        name: uaadb
        citext: true

  cc_api_version: v2

  cc: &cc
    logging_level: debug
    external_host: ccng
    srv_api_uri: <%= protocol %>://api.<%= root_domain %>
    cc_partition: default
    db_encryption_key: <%= common_password %>
    bootstrap_admin_email: "[email protected]"
    bulk_api_password: <%= common_password %>
    uaa_resource_id: cloud_controller
    staging_upload_user: upload
    staging_upload_password: <%= common_password %>
    resource_pool:
      resource_directory_key: cf-att-io-cc-resources
    packages:
      app_package_directory_key: cf-att-io-cc-packages
    droplets:
      droplet_directory_key: cf-att-io-cc-droplets
    default_quota_definition: runaway

  ccng: *cc

  login:
    enabled: false

  uaa:
    url: <%= protocol %>://uaa.<%= root_domain %>
    no_ssl: <%= protocol == "http" %>
    catalina_opts: -Xmx768m -XX:MaxPermSize=256m
    resource_id: account_manager
    jwt:
      signing_key: |
        -----BEGIN RSA PRIVATE KEY-----
        MIICXAIBAAKBgQDHFr+KICms+tuT1OXJwhCUmR2dKVy7psa8xzElSyzqx7oJyfJ1
        JZyOzToj9T5SfTIq396agbHJWVfYphNahvZ/7uMXqHxf+ZH9BL1gk9Y6kCnbM5R6
        0gfwjyW1/dQPjOzn9N394zd2FJoFHwdq9Qs0wBugspULZVNRxq7veq/fzwIDAQAB
        AoGBAJ8dRTQFhIllbHx4GLbpTQsWXJ6w4hZvskJKCLM/o8R4n+0W45pQ1xEiYKdA
        Z/DRcnjltylRImBD8XuLL8iYOQSZXNMb1h3g5/UGbUXLmCgQLOUUlnYt34QOQm+0
        KvUqfMSFBbKMsYBAoQmNdTHBaz3dZa8ON9hh/f5TT8u0OWNRAkEA5opzsIXv+52J
        duc1VGyX3SwlxiE2dStW8wZqGiuLH142n6MKnkLU4ctNLiclw6BZePXFZYIK+AkE
        xQ+k16je5QJBAN0TIKMPWIbbHVr5rkdUqOyezlFFWYOwnMmw/BKa1d3zp54VP/P8
        +5aQ2d4sMoKEOfdWH7UqMe3FszfYFvSu5KMCQFMYeFaaEEP7Jn8rGzfQ5HQd44ek
        lQJqmq6CE2BXbY/i34FuvPcKU70HEEygY6Y9d8J3o6zQ0K9SYNu+pcXt4lkCQA3h
        jJQQe5uEGJTExqed7jllQ0khFJzLMx0K6tj0NeeIzAaGCQz13oo2sCdeGRHO4aDh
        HH6Qlq/6UOV5wP8+GAcCQFgRCcB+hrje8hfEEefHcFpyKH+5g1Eu1k0mLrxK2zd+
        4SlotYRHgPCEubokb2S1zfZDWIXW3HmggnGgM949TlY=
        -----END RSA PRIVATE KEY-----
      verification_key: |
        -----BEGIN PUBLIC KEY-----
        MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDHFr+KICms+tuT1OXJwhCUmR2d
        KVy7psa8xzElSyzqx7oJyfJ1JZyOzToj9T5SfTIq396agbHJWVfYphNahvZ/7uMX
        qHxf+ZH9BL1gk9Y6kCnbM5R60gfwjyW1/dQPjOzn9N394zd2FJoFHwdq9Qs0wBug
        spULZVNRxq7veq/fzwIDAQAB
        -----END PUBLIC KEY-----
    cc:
      client_secret: <%= common_password %>
    admin:
      client_secret: <%= common_password %>
    batch:
      username: batch
      password: <%= common_password %>
    client:
      autoapprove:
        - cf
    clients:
      cf:
        override: true
        authorized-grant-types: password,implicit,refresh_token
        authorities: uaa.none
        scope: cloud_controller.read,cloud_controller.write,openid,password.write,cloud_controller.admin,scim.read,scim.write
        access-token-validity: 7200
        refresh-token-validity: 1209600
      admin:
        secret: <%= common_password %>
        authorized-grant-types: client_credentials
        authorities: clients.read,clients.write,clients.secret,password.write,scim.read,uaa.admin
    scim:
      userids_enabled: true
      users:
      - admin|<%= common_password %>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write
      - services|<%= common_password %>|scim.write,scim.read,openid,cloud_controller.admin

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.