OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

 View Only
  • 1.  RE: [tosca] tosca.nodes.Database (and Webserver)

    Posted 06-09-2015 21:01




    Hi Luca,
     
    Yes, the Webserver and Database normative node types (as well as many of the other ones) are “lowest common denominator” types that can serve as a starting point
    for more sophisticated types:
     

    1.       
    You could create subclasses of these types that add properties etc. to support your more advanced use cases.

    2.       
    If there are sufficient commonalities between the various subclasses (of Webserver or of Database) then we should consider moving these into the base
    class.
     
    Do you have any recommendations for what types of attributes/properties/capabilities/requirements etc. you would like to see added into the base classes?
     
    thanks,
     
    Chris
     
     


    From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
    On Behalf Of Luca Gioppo
    Sent: Monday, June 08, 2015 1:56 AM
    To: TOSCA
    Subject: [tosca] tosca.nodes.Database


     

    The mapping of database containing the user is again a semplification that collapse the standard to a very simple and many times far from the enterprise approach that is perhaps needed.



    It would be better to define accounts in the engine and rights on the DB as in all DBMS systems.



    This way we can have the capability to install an engine, a database and one user for read and one user for read/write.



     


    Thanks


    Luca







  • 2.  RE: [tosca] tosca.nodes.Database (and Webserver)

    Posted 06-10-2015 07:04
    Which is the best way to proceed? Shall I open an issue or continue the discussion here in list?   Luca   >   _________________________________________________________________________   >      >    Il 9 giugno 2015 alle 23.01 Chris Lauwers <lauwers@ubicity.com> ha scritto:   >      >    Hi Luca,   Yes, the Webserver and Database normative node types (as well as many of the other ones) are “lowest common denominator” types that can serve as a starting point for more sophisticated types:   1.        You could create subclasses of these types that add properties etc. to support your more advanced use cases. 2.        If there are sufficient commonalities between the various subclasses (of Webserver or of Database) then we should consider moving these into the base class.   Do you have any recommendations for what types of attributes/properties/capabilities/requirements etc. you would like to see added into the base classes?   thanks,   Chris     From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of Luca Gioppo   >    Sent: Monday, June 08, 2015 1:56 AM   >    To: TOSCA   >    Subject: [tosca] tosca.nodes.Database   The mapping of database containing the user is again a semplification that collapse the standard to a very simple and many times far from the enterprise approach that is perhaps needed. It would be better to define accounts in the engine and rights on the DB as in all DBMS systems. This way we can have the capability to install an engine, a database and one user for read and one user for read/write.   Thanks Luca   >    


  • 3.  RE: [tosca] tosca.nodes.Database (and Webserver)

    Posted 06-10-2015 14:44




    Hi Luca,
     
    Rather than continuing email discussions, I recommend that you:
     
    1.       
    Open up a Jira issue
    2.       
    Participate in the “Simple Profile” meetings on Tuesdays. Here is the URL for the next meeting:
     
    https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=39583
     
    Thanks for all your excellent comments,
     
    Chris
     


    From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
    On Behalf Of Luca Gioppo
    Sent: Wednesday, June 10, 2015 12:04 AM
    To: TOSCA
    Subject: RE: [tosca] tosca.nodes.Database (and Webserver)


     
    Which is the best way to proceed?
    Shall I open an issue or continue the discussion here in list?
     
    Luca
     >  _________________________________________________________________________
     >  
     >  

    Il 9 giugno 2015 alle 23.01 Chris Lauwers < lauwers@ubicity.com > ha scritto:

     >  
     >  

    Hi Luca,
     
    Yes, the Webserver and Database normative node types (as well as many of the other ones) are “lowest common denominator” types that can serve as a starting point
    for more sophisticated types:
     
    1.       
    You could create subclasses of these types that add properties etc. to support your more advanced use cases.
    2.       
    If there are sufficient commonalities between the various subclasses (of Webserver or of Database) then we should consider moving these into the base class.
     
    Do you have any recommendations for what types of attributes/properties/capabilities/requirements etc. you would like to see added into the base classes?
     
    thanks,
     
    Chris
     
     


    From:
    tosca@lists.oasis-open.org [ mailto:tosca@lists.oasis-open.org ]
    On Behalf Of Luca Gioppo
     >   Sent: Monday, June 08, 2015 1:56 AM
     >   To: TOSCA
     >   Subject: [tosca] tosca.nodes.Database


     

    The mapping of database containing the user is again a semplification that collapse the standard to a very simple and many times far from the enterprise approach that is perhaps needed.


    It would be better to define accounts in the engine and rights on the DB as in all DBMS systems.


    This way we can have the capability to install an engine, a database and one user for read and one user for read/write.


     


    Thanks


    Luca



     >   






  • 4.  RE: [tosca] tosca.nodes.Database (and Webserver)

    Posted 06-10-2015 17:53
    Hi Luca,

    Returning from vacation... I fully agree
    with Chris' responses and recommendations.  What we need are concrete
    use cases / examples showing what you want to do cannot be done or could
    be done better.  In terms of WAS and DB, please pay attention to the
    Credential datatype and the Endpoint.Admin capability if you are looking
    at aligning how userid/passwords would be done consistently across any
    SoftwareComponent, but something the Simple Profile working group has not
    had a chance to fully discuss.

    Kind regards,
    Matt




    From:      
      Chris Lauwers <lauwers@ubicity.com>
    To:      
      Luca Gioppo <luca.gioppo@csi.it>,
    TOSCA <tosca@lists.oasis-open.org>
    Date:      
      06/10/2015 09:44 AM
    Subject:    
        RE: [tosca]
    tosca.nodes.Database (and Webserver)
    Sent by:    
        <tosca@lists.oasis-open.org>




    Hi Luca,
     
    Rather than continuing email
    discussions, I recommend that you:
     
    1.       Open
    up a Jira issue
    2.       Participate
    in the “Simple Profile” meetings on Tuesdays. Here is the URL for the
    next meeting:
     
    https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=39583
     
    Thanks for all your excellent
    comments,
     
    Chris
     
    From: tosca@lists.oasis-open.org
    [ mailto:tosca@lists.oasis-open.org ]
    On Behalf Of Luca Gioppo
    Sent: Wednesday, June 10, 2015 12:04 AM
    To: TOSCA
    Subject: RE: [tosca] tosca.nodes.Database (and Webserver)
     
    Which is the best way to proceed?
    Shall I open an issue or continue
    the discussion here in list?
     
    Luca
     >  _________________________________________________________________________
     >  
     >  
    Il 9 giugno 2015 alle 23.01 Chris
    Lauwers < lauwers@ubicity.com >
    ha scritto:
     >  
     >  
    Hi Luca,
     
    Yes, the Webserver and Database
    normative node types (as well as many of the other ones) are “lowest common
    denominator” types that can serve as a starting point for more sophisticated
    types:
     
    1.
          You
    could create subclasses of these types that add properties etc. to support
    your more advanced use cases.
    2.
          If
    there are sufficient commonalities between the various subclasses (of Webserver
    or of Database) then we should consider moving these into the base class.
     
    Do you have any recommendations
    for what types of attributes/properties/capabilities/requirements etc.
    you would like to see added into the base classes?
     
    thanks,
     
    Chris
     
     
    From: tosca@lists.oasis-open.org
    [ mailto:tosca@lists.oasis-open.org ]
    On Behalf Of Luca Gioppo
     >   Sent:
    Monday, June 08, 2015 1:56 AM
     >   To: TOSCA
     >   Subject:
    [tosca] tosca.nodes.Database
     
    The mapping of database containing
    the user is again a semplification that collapse the standard to a very
    simple and many times far from the enterprise approach that is perhaps
    needed.
    It would be better to define accounts
    in the engine and rights on the DB as in all DBMS systems.
    This way we can have the capability
    to install an engine, a database and one user for read and one user for
    read/write.
     
    Thanks
    Luca
     >