This page is out of date. Will update the documents in Read the Docs.





  • No labels

7 Comments

  1. Borislav Glozman

    On the cloudify download page it says "Cloudify is available for a 60-day evaluation period."

    What happens after 60 days?

    How does this work with ONAP (Open Source, non-commercial etc.)?

    Do I need to buy a license in order to deploy OOM with Tosca?

    1. Michael O'Brien

      Looking forward to checking out any open source project that provides for alternative deployments - as part of a rich ecosystem

      /michael

  2. shay naeh

    "Cloudify is Open Source under the Apache 2 License. The code is hosted on Github under the code name Cosmo (we just love Kramer, what can you do). You’re most welcome to clone the code, fork it and submit pull requests."

     http://cloudify.co/community/

    I'm not sure why your talking the liberty on making such false assumptions without verifying it first.

    Also i'm not sure who has given you the authority to speak on behalf of ONAP and say what is or not recommended by ONAP!

    We remove your comment and if you would like to do so let's go though a formal process.

    Let me remind you that ONAP has dependency on other third party tools like MariaDB, Comundo and even Docker that has similar licensing model to that of Cloudify so i'd appreciate if you could verify your assessment before making such a public claims!

    Having said that we will make sure that the community edition license is clearer on the download page.

    1. Michael O'Brien

      Shay,

         Sounds good, I checked out the community link and I am going through the code https://github.com/cloudify-cosmo 

         Appreciate the links into the open source version of cloudify and clearing up any confusion on my part about the public/private model.  I am going through the deployment model now - I am particularly interested in the 4.3 AWS EC2 model example https://github.com/cloudify-cosmo/cloudify-hello-world-example/blob/master/ec2-blueprint.yaml

      thank you

      /michael

  3. Michael O'Brien

    Good review of the blueprint and some of the helm code in review in the last OOM meeting - thanks to shay naeh and Nicolas and Jun Hu and krzysztof.bijakowski@cloudify.co

    Reviewing now as I bring up the system - I think a live demo bringing up OOM would be a good topic for the next OOM meet.

    OOM Meeting Notes - 2018-01-10

    OOM-46 - Getting issue details... STATUS

    https://gerrit.onap.org/r/#/c/27751/1

  4. Michael O'Brien

    Starting AWS version of the bootstrap install (no baked AMI) on Ubuntu 16.04 for cloudify community - and documenting here under  OOM-579 - Getting issue details... STATUS  so I can get a feel for the deployment as it compares to using Rancher on top of Kubernetes/helm


  5. Michael O'Brien

    Having a lot of issues getting past template variable substitution in the blueprint on the dcae controller 

    The cloudify tasks are created, sent but fail with 2-4 authentication failures (tried all combinations of v2, v3.0)

    this is on openlab after I rebooted the aai_vm1 

    This is also specific to the HEAT part of the hybrid HEAT-Kubernetes install until the cloudify VM is containerized

    verified both /opt/config and /opt/app/inputs/templates

    root@onap-dcae-bootstrap:/opt# ./dcae2_vm_init.sh

    DCAEGEN2-300 - Getting issue details... STATUS

    LOG-167 - Getting issue details... STATUS 

    If you make changes to the blueprint, run `cfy local init -p ./blueprints/centos_vm.yaml` again to apply them

+ cfy local execute -w install --task-retries=10

2018-02-04 03:41:28 CFY <local> Starting 'install' workflow execution

2018-02-04 03:41:29 CFY <local> [security_group_bf1da] Creating node

2018-02-04 03:41:29 CFY <local> [floatingip_vm00_c5c0d] Creating node

2018-02-04 03:41:29 CFY <local> [private_net_f1ffd] Creating node

2018-02-04 03:41:29 CFY <local> [key_pair_6f85e] Creating node

2018-02-04 03:41:29 CFY <local> [key_pair_6f85e.create] Sending task 'nova_plugin.keypair.create'

2018-02-04 03:41:29 CFY <local> [floatingip_vm00_c5c0d.create] Sending task 'neutron_plugin.floatingip.create'

2018-02-04 03:41:29 CFY <local> [private_net_f1ffd.create] Sending task 'neutron_plugin.network.create'

2018-02-04 03:41:29 CFY <local> [security_group_bf1da.create] Sending task 'neutron_plugin.security_group.create'

2018-02-04 03:41:29 CFY <local> [key_pair_6f85e.create] Task started 'nova_plugin.keypair.create'

2018-02-04 03:41:29 CFY <local> [floatingip_vm00_c5c0d.create] Task started 'neutron_plugin.floatingip.create'

2018-02-04 03:41:29 CFY <local> [private_net_f1ffd.create] Task started 'neutron_plugin.network.create'

2018-02-04 03:41:29 CFY <local> [security_group_bf1da.create] Task started 'neutron_plugin.security_group.create'

2018-02-04 03:41:29 CFY <local> [key_pair_6f85e.create] Task failed 'nova_plugin.keypair.create' -> The request you have made requires authentication. [status_code=401]

2018-02-04 03:41:29 CFY <local> [floatingip_vm00_c5c0d.create] Task failed 'neutron_plugin.floatingip.create' -> {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}} [status_code=401]

2018-02-04 03:41:29 CFY <local> 'install' workflow execution failed: Workflow failed: Task failed 'nova_plugin.keypair.create' -> The request you have made requires authentication. [status_code=401]

Workflow failed: Task failed 'nova_plugin.keypair.create' -> The request you have made requires authentication. [status_code=401]