ariatosca-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ran-z <>
Subject [GitHub] incubator-ariatosca pull request #191: ARIA-321 Provide Clearwater IMS examp...
Date Sun, 03 Sep 2017 13:00:12 GMT
Github user ran-z commented on a diff in the pull request:
    --- Diff: examples/clearwater/clearwater-live-test-existing.yaml ---
    @@ -0,0 +1,54 @@
    +# Licensed to the Apache Software Foundation (ASF) under one or more
    +# contributor license agreements.  See the NOTICE file distributed with
    +# this work for additional information regarding copyright ownership.
    +# The ASF licenses this file to You 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
    +# 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.
    +tosca_definitions_version: tosca_simple_yaml_1_0
    +description: >-
    +  Project Clearwater is an open-source IMS core, developed by Metaswitch Networks and
released under
    +  the GNU GPLv3.
    +  template_name: clearwater-live-test-existing
    +  template_author: ARIA
    +  template_version: '1.0'
    +  aria_version: '0.1.2'
    +  - types/clearwater.yaml
    +  - aria-1.0
    +  inputs:
    +    hosts.ssh.user:
    +      type: string
    +    hosts.ssh.password:
    --- End diff --
    why is one "hosts.X.Y" and the other "existing_host.Z.W"? It makes it seem like the user/password
and the public-address are for two different hosts, doesn't it?

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