Common use of Constraints on the Experimenters Use Clause in Contracts

Constraints on the Experimenters Use. The SoftFIRE infrastructure is composed by loosely integrated platform under different administrative domains. In addition, the different platforms are ran for experimental purposes and they are not yet considered a mass production tool. This means that bugs and issues in the platform behaviour can occur and will occur. Actually, the scope of the experiments is also to support the tune up and the assessment of the platform as a whole. The Platform is still under development and it has a basic set of functionalities that have to be tuned up and it is missing a number of features that will be progressively added in the future. SoftFIRE is by no means to be considered a product and so the usual support for software development cannot be granted. Even if SoftFIRE aims at programmers, not all the features to allow for a fast programming approach are provided. This is due to differences in the component testbeds and to security controls imposed by different administrative domains. The programming phases could result cumbersome and not particularly attractive; however they may improve along the lifetime of the project. Service level agreements (SLA) do not apply during the experimentation phases. Because this is a period to test and explore SoftFIRE, the experimenters should not run production applications on the infrastructure Platform during the trial. The SoftFIRE project reserves the right to discontinue at any time the service if the use is not consistent with the purpose of SDN/NFV and/or violate any aspects of infrastructure security or shall conflicts any ongoing experimentation. During the running period of the experiments, the SoftFIRE project will put in place a team that will support the experiments in their work on the platform. As said this is not offered as a professional service and its working will be on the base of best effort. The entire infrastructure should be considered more a sort of α-test platform. Possible downs could occur without notice or due to overload caused by parallel experiments. SoftFIRE will offer expertise available by email (with possible follow-up by phone) and two hours per day during the experimentation phase in order to collect issues and provide responses. We’ll try to provide most of the answers by 24 hours (typically next morning or afternoon). Some issues could be not solvable due to the short time of the experiment period or due to the need to intervene on the platform. The supporting time will work with experimenters for circumvent any problem. The project will also issue limits and constraints on the allocation of available resources. This is due to the need to support and allow parallel experimentations. This limitation depends on the total capabilities of the federated platform as well as the number of experimenters and their requests in terms of resources. Typical limitation could be related to the max number of VMs to be instanced, the number of physical resources usable or the max memory usable per experimenters. Other limitations could apply, or be notified during the course of the experimentations. Paid support: If you have extensive support needs during the experimentation, you may purchase paid support for the SoftFIRE Platform. The paid support package offers increasing levels of hands-on support and response time. A few aids for the experimenters could be added in due time in the SoftFIRE portal at xxxx://xxx.xxxxxxxx.xx • An “on line” tutorial on how to access and use the platform will be prepared before the experimentation phase • A presentation with a use case • Other educational material

Constraints on the Experimenters Use. The SoftFIRE infrastructure is composed by loosely integrated platform under different administrative domains. In addition, the different platforms are ran for experimental purposes and they are not yet considered a mass production tool. This means that bugs and issues in the platform behaviour can occur and will occur. Actually, the scope of the experiments is also to support the tune up and the assessment of the platform as a whole. The Platform is still under development and it has a basic set of functionalities that have to be tuned up and it is missing a number of features that will be progressively added in the future. SoftFIRE is by no means to be considered a product and so the usual support for software development cannot be granted. Even if SoftFIRE aims at programmers, not all the features to allow for a fast programming approach are provided. This is due to differences in the component testbeds and to security controls imposed by different administrative domains. The programming phases could result cumbersome and not particularly attractive; , however they may improve along the lifetime of the project. Service level agreements (SLA) do not apply during the experimentation phases. Because this is a period to test and explore SoftFIRE, the experimenters should not run production applications on the infrastructure Platform during the trial. The SoftFIRE project reserves the right to discontinue at any time the service if the use is not consistent with the purpose of SDN/NFV and/or violate any aspects of infrastructure security or shall conflicts any ongoing experimentation. During the running period of the experiments, the SoftFIRE project will put in place a team that will support the experiments in their work on the platform. As said this is not offered as a professional service and its working will be on the base of best effort. The entire infrastructure should be considered more a sort of α-test -test platform. Possible downs could occur without notice or due to overload caused by parallel experiments. SoftFIRE will offer expertise available by email (with possible follow-up by phone) and two hours per day during the experimentation phase in order to collect issues and provide responses. We’ll try to provide most of the answers by 24 hours (typically next morning or afternoon). Some issues could be not solvable due to the short time of the experiment period or due to the need to intervene on the platform. The supporting time will work with experimenters for circumvent any problemthe problems. The project will also issue limits and constraints on the allocation of available resources. This is due to the need to support and allow parallel experimentations. This limitation depends on the total capabilities of the federated platform as well as the number of experimenters and their requests in terms of resources. Typical limitation could be related to the max number of VMs to be instanced, the number of physical resources usable or the max memory usable per experimenters. Other limitations could apply, or be notified during the course of the experimentations. Paid support: If you have extensive support needs during the experimentation, you may purchase paid support for the SoftFIRE Platform. The paid support package offers increasing levels of hands-on support and response time. A few aids for the experimenters could be added in due time in the SoftFIRE portal at xxxx://xxx.xxxxxxxx.xx • h ttp://xxx.xxxxxxxx.xx  An “on line” tutorial on how to access and use the platform will be prepared before the experimentation phase •  A presentation with a use case •  Other educational material

Constraints on the Experimenters Use. The SoftFIRE infrastructure is composed by loosely integrated platform under different administrative domains. In addition, addition the different platforms platform are ran for experimental purposes and they are not yet considered a mass production tool. This means that bugs and issues in the platform behaviour behavior can occur and will occur. Actually, Actually the scope of the experiments is also to support the tune up and the assessment of the platform as a whole. The Platform is still under development and it has a basic set of functionalities that have to be tuned up and it is missing a number of features that will be progressively added in the future. SoftFIRE is by no means to be considered a product and so the usual support for software development cannot be granted. Even if SoftFIRE aims at programmers, not all the features to allow for a fast programming approach are provided. This is due to differences in the component testbeds and to security controls imposed by different administrative domains. The programming phases could result results cumbersome and not particularly attractive; , however they may improve along the lifetime of the project. Service level agreements (SLA) do not apply during the experimentation phases. Because this is a period to test and explore SoftFIRE, the experimenters should not run production applications on the infrastructure Platform during the trial. The SoftFIRE project reserves the right to discontinue at any time the service if the use is not consistent with the purpose of SDN/NFV and/or violate any aspects of infrastructure security or shall conflicts any ongoing experimentation. During the running period of the experiments, the SoftFIRE project will put in place a team that will support the experiments in their work on the platform. As said this is not offered as a professional service and its working will be on the base of best effort. The entire infrastructure should be considered more a sort of α-test -test platform. Possible downs could occur without notice or due to overload caused by parallel experiments. SoftFIRE will offer expertise available by email (with possible follow-up by phone) and two hours per day during the experimentation phase in order to collect issues and provide responses. We’ll try to provide most of the answers by 24 hours (typically next morning or afternoon). Some issues could be not solvable due to the short time of the experiment period or due to the need to intervene on the platform. The supporting time will work with experimenters for circumvent any problemthe problems. The project will also issue limits and constraints on the allocation of available resources. This is due to the need to support and allow parallel experimentations. This limitation depends on the total capabilities of the federated platform as well as the number of experimenters and their requests in terms of resources. Typical limitation could be related to the max number of VMs to be instanced, the number of physical resources usable or the max memory usable per experimenters. Other limitations could apply, or be notified during the course of the experimentations. Paid support: If you have extensive support needs during the experimentation, you may purchase paid support for the SoftFIRE Platform. The paid support package offers offer increasing levels of hands-on support and response time. A few aids for the experimenters could be added in due time in the SoftFIRE portal at xxxx://xxx.xxxxxxxx.xx •  An “on line” tutorial on how to access and use the platform will be prepared before the experimentation phase •  A presentation with a use case •  Other educational material

Constraints on the Experimenters Use. The SoftFIRE infrastructure is composed by loosely integrated platform under different administrative domains. In addition, addition the different platforms platform are ran for experimental purposes and they are not yet considered a mass production tool. This means that bugs and issues in the platform behaviour can occur and will occur. Actually, Actually the scope of the experiments is also to support the tune up and the assessment of the platform as a whole. The Platform is still under development and it has a basic set of functionalities that have to be tuned up and it is missing a number of features that will be progressively added in the future. SoftFIRE is by no means to be considered a product and so the usual support for software development cannot be granted. Even if SoftFIRE aims at programmers, not all the features to allow for a fast programming approach are provided. This is due to differences in the component testbeds and to security controls imposed by different administrative domains. The programming phases could result results cumbersome and not particularly attractive; , however they may improve along the lifetime of the project. Service level agreements (SLA) do not apply during the experimentation phases. Because this is a period to test and explore SoftFIRE, the experimenters should not run production applications on the infrastructure Platform during the trial. The SoftFIRE project reserves the right to discontinue at any time the service if the use is not consistent with the purpose of SDN/NFV and/or violate any aspects of infrastructure security or shall conflicts any ongoing experimentation. During the running period of the experiments, the SoftFIRE project will put in place a team that will support the experiments in their work on the platform. As said this is not offered as a professional service and its working will be on the base of best effort. The entire infrastructure should be considered more a sort of α-test platform. Possible downs could occur without notice or due to overload caused by parallel experiments. SoftFIRE will offer expertise available by email (with possible follow-up by phone) and two hours per day during the experimentation phase in order to collect issues and provide responses. We’ll try to provide most of the answers by 24 hours (typically next morning or afternoon). Some issues could be not solvable due to the short time of the experiment period or due to the need to intervene on the platform. The supporting time will work with experimenters for circumvent any problemthe problems. The project will also issue limits and constraints on the allocation of available resources. This is due to the need to support and allow parallel experimentations. This limitation depends on the total capabilities of the federated platform as well as the number of experimenters and their requests in terms of resources. Typical limitation could be related to the max number of VMs to be instanced, the number of physical resources usable or the max memory usable per experimenters. Other limitations could apply, or be notified during the course of the experimentations. Paid support: If you have extensive support needs during the experimentation, you may purchase paid support for the SoftFIRE Platform. The paid support package offers increasing levels of hands-on support and response time. A few aids for the experimenters could be added in due time in the SoftFIRE portal at xxxx://xxx.xxxxxxxx.xx • An “on line” tutorial on how to access and use the platform will be prepared before the experimentation phase • A presentation with a use case • Other educational material