40a9ce5629
Each TOSCA abstract type is handled by a separate generator. These contain the necessary logic to implement the abstract type as concrete Heat resource type. In this set, only the server type requires custom handling. All the other types are software config and are handled by the super class. The WordPress type is a custom type and will be moved to a separate place Partially implements blueprint heat-translator-tosca Change-Id: Ida687e6eed53e1edfdc611bc3d27704d9d9f3d67 O
28 lines
897 B
Python
Executable File
28 lines
897 B
Python
Executable File
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
from translator.hot.syntax.hot_resource import HotResource
|
|
|
|
|
|
class ToscaWebserver(HotResource):
|
|
'''Translate TOSCA node type tosca.nodes.WebServer.'''
|
|
|
|
toscatype = 'tosca.nodes.WebServer'
|
|
|
|
def __init__(self, nodetemplate):
|
|
super(ToscaWebserver, self).__init__(nodetemplate)
|
|
pass
|
|
|
|
def handle_properties(self):
|
|
pass
|