Uploaded image for project: 'OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC'
  1. OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
  2. TOSCA-164

CLOSE - WD02 - Do we need a restart lifecycle operation for nodes?

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: CSD2
    • Fix Version/s: CSD2
    • Component/s: Profile-YAML
    • Labels:
      None
    • Resolution:
      Hide

      The TC agreed that a "restart" operation was not needed as using existing operations can accomplish / result in the same state for a node. In addition, having a granular restart has potential implications on the state model which the TC acknowledged would complicate a deterministic state model.

      Show
      The TC agreed that a "restart" operation was not needed as using existing operations can accomplish / result in the same state for a node. In addition, having a granular restart has potential implications on the state model which the TC acknowledged would complicate a deterministic state model.

      Description

      In coding an equivalent to Heat's Wordpres + MySQL app on same instance we found that after the scripts configured the wordpress app it restarted the web server (apache) that was hosting it to pick up the new settings. This basically voided TOSCA's approach to nodes and allowing the orchestrator to do these things.

      Here is the WordPress config scripts

      sed -i "/Deny from All/d" /etc/httpd/conf.d/wordpress.conf
      sed -i "s/Require local/Require all granted/" /etc/httpd/conf.d/wordpress.conf
      sed -i s/database_name_here/db_name/ /etc/wordpress/wp-config.php
      sed -i s/username_here/db_user/ /etc/wordpress/wp-config.php
      sed -i s/password_here/db_password/ /etc/wordpress/wp-config.php
      systemctl restart httpd.service

      Ideally, there should be a TOSCA way to do this.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mrutkows Matthew Rutkowski (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Due:
                Created:
                Updated: