zilongwang/ReadingBank huggingface dataset:
This document does not constitute an offer to provide goods/services to the British Council and the British Council is not obliged to award a contract for these goods/services. The British Council reserves the right to request reference information. NOTE: All costs related to travel; accommodation and meals will be agreed in advance with the British Council manager. Payment and Invoicing The British Council will pay correctly addressed and undisputed invoices within 30 days. The British Council has a requirement for invoices to be produced in an electronic format. Essential information to be included on any invoice for the British Council is: A description of the services supplied. The British Council reference number/Purchase Order number. Addressed to Accounts Payable. The costs including VAT (if applicable) and any other charges Contracting Any submissions must expressly accept the British Council’s Contract (Terms and Conditions). If you have any objections these must be stated in writing on a separate appendix. Instructions for applicants To be considered, one page proposal that would contain relevant experience and suggested points for discussion must be sent in electronic form to not later than 30 September 2017. For all options the following requirements are mandatory: Expert resume Proposal for the symposium
1 2 3 4 5 6 7 8 Line of enquiry LE (or Evaluation questions- EQ) Objectives of the evaluation Criteria Observations Triangulation Findings Conclusion Recommendation i.e. To what extend is the program relevant to users/beneficiary? i.e. To determine whether or not the program meet the needs of the beneficiary To determine whether or not the program is aligned with priorities i.e. Relevance i.e. What you observed against that line of enquiry only i.e. Type of triangulation if any i.e. What you against the relevance criteria i.e. Summary of a line or a related group of a lines of enquiry: conclude against the evaluation objectives i.e. Effective recommendations encourage improvements in the conduct of management and operations. Recommendations are not always required nor are mandatory. Recommendations are effective: 1- when they are addressed to parties that have the authority to act and 2- when the recommended actions are specific, practical, cost effective, and measurable. Etc.
Review/approve draft proposed agenda Review/approve minutes * May 25: ** Thanks to Artac for scribing Welcome to recently joined TC Members and Observers (those first announced in today's TC meeting listed in italics): Jim Fowler from US Department of Defense (Observer), Mr. Xu Yang from Huawei Technologies Co., Ltd. (Member), Mr. Weitao Gao from Huawei Technologies Co., Ltd. (Member), Mr. Daigang Xu from ZTE (Member), Mr. Joe Zhang from ZTE (Member), Mr. Srinivasa Addepalli from Intel Corporation (Observer), Ms. Priya TG from NetCracker (Observer), Mr. Takayuki Kuroda from NEC Corporation has been added as Observer, Mr. Shin Kondo from NEC Corporation (Observer), Mr. Feng Yuanxing from ZTE (Member), and Dr. Hui Deng from Huawei Technologies Co., Ltd. (Member) Co-chair remarks, notables, possible motions, etc. * Also, other News from TC members (outside of Ad Hoc group reports)? NOTE: Exact Order of Reports to be Determined During Meeting by Co-Chairs See explanation of OASIS document types and typical cadence Interoperability Subcommittee Report (Co-Chairs: Luc Boutier and Jacques Durand) * JOIN HERE (remember to remind your OASIS Primary Representative to approve afterwards) * Find the latest recognized work in progress, OASIS TOSCA Test Assertions v1.0 Committee Note Draft 01 (2016 Dec) here * Find the OASIS TOSCA Test Assertion Repo here * * You can send contributions for review to the Co-Chairs or post to the JIRA but to to contribute directly to the Repo, you will need to sign an individual CLA (see FAQ for more on individual (and optional entity) CLAs here) * 2017-05-17 meeting notes: pending Instance Model Ad Hoc Group (co-leaders: Frank Chauvel and Derek Palma) * TOSCA-275 (general group activity, and suggestions/questions/contributions from TC members)
attributes InstanceAttribute 0..N Corresponds to the attributes defined in the group type and holds the actual attribute values. Each attribute value indicates the value at the time the attribute was accessed. Attributes reflect the state of the underlying group and may change at any time. capabilities InstanceCapability 0..N Corresponds to the capabilities defined in the group type and desired values specified in the group template. Each capability property value indicates the final value used by the orchestrator for that property requirements InstanceRequirement 0..N Maps the source instance in a requirement relationship to the target instances. The mapping is 1 to N and does not have to be 1-1 or onto with respect to all source and target instances. Figure 6 Structure of InstanceGroups, shown as a UML class diagram InstanceMetadata Definition InstanceMetadata consists of named objects (a map: name → InstanceObject). Because InstanceObjects can encoded arbitrary information, virtually any information can be added to the instance model as InstanceMetadata. The instance model version is required (e.g., tosca_instance_version: tosca_simple_yaml_1_0) Orchestrators may add any additional metadata they like, such as their name and version, licensing, location, signatures, etc. InstanceMetdata should really be part of InstanceObject so any entity in the instance model can encode any information (like annotations) as InstanceObjects. InstanceInput Definition For each input in the service template, and InstanceInput instance is created containing the value used by the orchestrator for the input. Each InstanceInput is a <name, value> pair consisting of the name of the input in the respective TOSCA input definition and the value of the input encoded for the respective type of the input in the TOSCA input definition. InstancePolicy Definition For each policy applied in the service template, an InstancePolicy instance is created and, if applicable, references from the InstancePolicy to the instance model entities the policy is matched are created. Note that not all policies may be used by the orchestrator if they don’t match with entities in the final service topology created by the orchestrator.
Use of the TOSCA Service Template inputs section to declare a configurable value the template user may supply at runtime. In this case, the property named “cpus” (of type integer) is declared. Use of a property constraint to the allowed integer values for the “cpus” property to a specific list supplied in the property declaration. Use of the TOSCA Service Template outputs section to declare a value the template user may request at runtime. In this case, the property named “instance_ip” is declared The “instance_ip” output property is programmatically retrieved from the Compute node’s “ip_address” property using the TOSCA Service Template-level get_property function. Logical Diagram TBD Sample YAML tosca_definitions_version: tosca_simple_ description: > TOSCA simple profile that just defines a single compute instance. Note, this example does not include default values on inputs properties. inputs: cpus: type: integer description: Number of CPUs for the server. constraints: - valid_values: [ 1, 2, 4, 8 ] node_templates: my_server: type: tosca.nodes.Compute properties: # compute properties disk_size: 10 # in GB num_cpus: { get_input: cpus } mem_size: 4 # in MB # host image properties os_arch: x86_64 os_type: linux os_distribution: ubuntu os_version: 12.04 outputs: instance_ip:
properties: context_root: { get_input: context_root } admin_user: { get_input: wp_admin_username } admin_password: { get_input: wp_admin_password } db_host: { get_attribute: [ db_server, private_address ] } requirements: - host: apache - database_endpoint: wordpress_db interfaces: Standard: inputs: db_host: { get_attribute: [ db_server, private_address ] } db_port: { get_property: [ wordpress_db, port ] } db_name: { get_property: [ wordpress_db, name ] } db_user: { get_property: [ wordpress_db, user ] } db_password: { get_property: [ wordpress_db, password ] } apache: type: tosca.nodes.WebServer.Apache properties: # omitted here for brevity requirements: - host: web_server web_server: type: tosca.nodes.Compute capabilities: # omitted here for brevity wordpress_db: type: properties: name: { get_input: wp_db_name } user: { get_input: wp_db_user } password: { get_input: wp_db_password } port: { get_input: wp_db_port } requirements: - host: mysql type: tosca.nodes.DBMS.MySQL
Examples mycompanytypes.myrelationships.AppDependency: derived_from: valid_target_types: [ mycompanytypes.mycapabilities.SomeAppCapability ] Type A Group Type defines logical grouping types for nodes, typically for different management purposes. Groups can effectively be viewed as logical nodes that are not part of the physical deployment topology of an application, yet can have capabilities and the ability to attach policies and interfaces that can be applied (depending on the group type) to its member nodes. Conceptually, group definitions allow the creation of logical “membership” relationships to nodes in a service template that are not a part of the application’s explicit requirement dependencies in the topology template (i.e. those required to actually get the application deployed and running). Instead, such logical membership allows for the introduction of things such as group management and uniform application of policies (i.e., requirements that are also not bound to the application itself) to the group’s members. Keynames The following is the list of recognized keynames for a Group Type definition: Keyname Required Type Description derived_from no An optional parent Group Type name the Group Type derives from. version no An optional version for the Group Type definition. description no The optional description for the Group Type. properties no list of An optional list of property definitions for the Group Type. no [] An optional list of one or more of Node Types that are valid (allowed) as members of the Group Type. Note: This can be viewed by TOSCA Orchestrators as an implied relationship nodes, but one that does not have operational lifecycle considerations. For example, if we were to name this as an explicit Relationship Type we might call this “” (group). interfaces no list of An optional list of interface definitions supported by the Group Type. Grammar Types have one the following grammars: <>: derived_from: <> version: <> description: <>
Example 12 - An abstract Compute node template with a node filter tosca_definitions_version: tosca_simple_yaml_1_0 description: Template with requirements against hosting infrastructure. topology_template: inputs: # omitted here for brevity node_templates: mysql: type: properties: # omitted here for brevity requirements: - host: mysql_compute # Abstract node template (placeholder) to be selected by provider mysql_compute: type: Compute node_filter: capabilities: - host: properties: num_cpus: { equal: 2 } mem_size: { greater_or_equal: 2 GB } - os: properties: architecture: { equal: x86_64 } type: linux distribution: ubuntu As you can see the resulting mysql_compute node template looks very much like the “hello world” template as shown in (where the Compute node template was abstract), but this one also allows the TOSCA orchestrator more flexibility when “selecting” a host Compute node by providing flexible constraints for properties like mem_size. As we proceed, you will see that TOSCA provides many normative node types like Compute for commonly found services (e.g., BlockStorage, WebServer, Network, etc.). When these TOSCA normative node types are used in your application’s topology they are always assumed to be “selectable” by TOSCA Orchestrators which work with target infrastructure providers to find or allocate the best match for them based upon your application’s requirements and constraints.
Acknowledgments The following individuals have participated in the creation of this specification and are gratefully acknowledged: Contributors: Avi Vachnis (), Alcatel-Lucent Chris Lauwers () Derek Palma (), Vnomic Leymann (), Univ. of Stuttgart Gerd Breiter (), IBM Surti (), Cisco Ifat Afek (), Alcatel-Lucent Idan Moyal, (), Gigaspaces Jacques Durand (), Fujitsu Jin Qin, (), Huawei Juergen Meynert (), Fujitsu Kapil Thangavelu (), Canonical Karsten Beins (), Fujitsu Kevin Wilson (), HP Krishna Raman (), Red Hat Luc Boutier (), FastConnect Matt Rutkowski (), IBM Moshe Elisha (), Alcatel-Lucent Nate Finch (), Canonical Nikunj Nemani (), WMware Richard Probst (), SAP AG Sahdev Zala (), IBM Shitao li (), Huawei Simeon Monov (), IBM Stephane Maes (), HP Thomas Spatzier (), IBM Ton Ngo (), IBM Travis Tripp (), HP Hashemian (), IBM Wayne Witzel (), Canonical Yaron Parasol (), Gigaspaces
Stapleton, J. (2013). The ‘Welfareization’ of Disability Incomes in Ontario. : Metcalf Foundation, December. Statistics Canada. (2012). A profile of persons with disabilities among Canadians aged 15 years or older, 2012. Canadian Survey on Disability 2012. Ottawa. Till, M., T. Leonard, S. and G. Nicholls. (2015). A Profile of the Labour Market Experiences of Adults with Disabilities among Canadians Aged 15 Years and Older, 2012. Ottawa: Statistics Canada, catalogue no. 89-654-X2015005. Torjman, S. (2017). Poverty Reduction and Disability Income. Ottawa: Caledon Institute of Social Policy, February. Torjman, S. (2015). Delivery of Social Benefits through the Personal Income Tax. Ottawa: Caledon Institute of Social Policy, September. Torjman, S. (2009). The Three Ghosts of Poverty. Ottawa: Caledon Institute of Social Policy, October. Torjman, S. (2007). Five-Point Plan for Reforming Disability Supports. Ottawa: Caledon Institute of Social Policy, October. Torjman, S. (2000). Proposal for a National Personal Supports Fund. Ottawa: Caledon Institute of Social Policy, October. Torjman, S. and K. Battle. (1993). Breaking Down the Welfare Wall. Ottawa: Caledon Institute of Social Policy, July. Torjman, S. and A. Makhoul. (2016). Disability Supports and Employment Policy. Ottawa: Caledon Institute of Social Policy and Centre for Research on Work Disability Policy, October. Torjman, S., M. Mendelson and K. Battle. (2017). The 2017 Farewell Budget. Ottawa: Caledon Institute of Social Policy, March. Tweddle, A., K. Battle and S. Torjman. (2016). Welfare in Canada 2015. Ottawa: Caledon Institute of Social Policy, November.
5.8.2 TODO: Parser should parse shorthand Names and Type URL names. Parser 5.8.3 5.8.4 tosca.nodes.WebServer 5.8.5 tosca.nodes.WebApplication 5.8.6 tosca.nodes.DBMS 5.8.7 tosca.nodes.Database 5.8.8 tosca.nodes.ObjectStorage 5.8.9 tosca.nodes.BlockStorage 5.8.10 tosca.nodes.Container.Runtime 5.8.11 tosca.nodes.Container.Application 5.8.12 tosca.nodes.LoadBalancer 5.9 Group Types 5.9.1 tosca.groups.Root
Requirement Type Node Type Relationship Type Group Type Policy Type Template-specific definitions Capability assignment Requirement assignment Node Template Relationship Template Group definition Policy definition Topology Template definition Keynames Grammar Service Template definition Keynames Id: 3.9.1.1-metadata-01-valid Prerequisite: Description: Parsing a valid metadata section MUST succeed. Target: The 'metadata' out of the parsing Predicate: When parsing the template assert 'template_name' value is equal to 'tosca_meta_data_test' Prescription level: mandatory Conformance target: Parser-Validator