brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From drigodwin <>
Subject [GitHub] brooklyn-docs pull request #93: Add to blueprinting-tips
Date Tue, 19 Jul 2016 11:18:06 GMT
Github user drigodwin commented on a diff in the pull request:
    --- Diff: guide/yaml/ ---
    @@ -98,8 +151,32 @@ If writing a custom integration, the following recommendations may
be useful:
       For example, if deploying a MongoDB cluster then first focus on single-node MongoDB,
and then make that
       configurable and composable for a cluster.
    -* Use the test framework to write test cases, so that others can run these to confirm
that the 
    -  entity works in their environment.
     * Where appropriate, share the new entity with the Brooklyn community so that it can
be reviewed, 
       tested and improved by others in the community!
    +## Cloud Portability
    +You get a lot of support out-of-the-box for deploying blueprints to different clouds.
The points 
    +below may also be of help:
    +* Test (and regression test) on each target cloud.
    +* Be aware that images on different clouds can be very different. For example, two CentOS
6.6 VMs 
    +  might have different pre-installed libraries, different default iptables or SE Linux
    +  different repos, different sudo configuration, etc.
    +* Different clouds handle private and public IPs differently. One must be careful about
    +  address to advertise to for use by other entities.
    +* VMs on some clouds will not have a well-configured hostname (e.g. `ping $(hostname)`
can fail).
    --- End diff --
    VMs on some clouds will not -> VMs on some clouds may not

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message