Legality of Cannabis by U.S. Jurisdiction

Content deleted Content added
Johnuniq (talk | contribs)
Undid revision 377123518 by Lgharda (talk) please see WP:WTAF
Ceo2000 (talk | contribs)
No edit summary
(3 intermediate revisions by the same user not shown)
Line 17: Line 17:
Server provisioning is a set of actions to prepare a server with appropriate systems, data and software, and make it ready for network operation. Typical tasks when provisioning a server are: select a [[server (computing)|server]] from a pool of available servers, load the appropriate [[software]] ([[operating system]], [[device driver]]s, [[middleware]], and [[application software|application]]s), appropriately customize and configure the system and the software to create or change a [[boot image]] for this server, and then change its parameters, such as [[IP address]], [[Gateway (telecommunications)|IP Gateway]] to find associated network and storage resources (sometimes separated as ''resource provisioning'') to audit the system. By auditing the system, you ensure [[Open Vulnerability and Assessment Language|OVAL]] compliance with limit vulnerability, ensure compliance, or install patches. After these actions, you restart the system and load the new software. This makes the system ready for operation. Typically an [[internet service provider]] (ISP) or [[Network Operations Center]] will perform these tasks to a well-defined set of parameters, for example, a boot image that the organization has approved and which uses software it has license to. Many instances of such a boot image create a [[virtual host|virtual]] [[Dedicated hosting service|dedicated host]].
Server provisioning is a set of actions to prepare a server with appropriate systems, data and software, and make it ready for network operation. Typical tasks when provisioning a server are: select a [[server (computing)|server]] from a pool of available servers, load the appropriate [[software]] ([[operating system]], [[device driver]]s, [[middleware]], and [[application software|application]]s), appropriately customize and configure the system and the software to create or change a [[boot image]] for this server, and then change its parameters, such as [[IP address]], [[Gateway (telecommunications)|IP Gateway]] to find associated network and storage resources (sometimes separated as ''resource provisioning'') to audit the system. By auditing the system, you ensure [[Open Vulnerability and Assessment Language|OVAL]] compliance with limit vulnerability, ensure compliance, or install patches. After these actions, you restart the system and load the new software. This makes the system ready for operation. Typically an [[internet service provider]] (ISP) or [[Network Operations Center]] will perform these tasks to a well-defined set of parameters, for example, a boot image that the organization has approved and which uses software it has license to. Many instances of such a boot image create a [[virtual host|virtual]] [[Dedicated hosting service|dedicated host]].


There are many [[software]] products available to automate the provisioning of servers, services and end-user devices from vendors such as [[Stratavia]], [[BladeLogic]], [[IBM]],<ref>[http://www-306.ibm.com/software/tivoli/products/prov-mgrproductline/ IBM Tivoli]</ref> or [[Hewlett-Packard|HP]]. Middleware and applications can be installed either when the operating system is installed or afterwards by using an [[Application Service Automation]] tool. Further questions are addressed in academia such as when provisioning should be issued and how many servers are needed in multi-tier,<ref>Bhuvan Urgaonkar, Prashant Shenoy, Abhishek Chandra, Pawan Goyal and Timothy Wood. [http://doi.acm.org/10.1145/1342171.1342172 Agile dynamic provisioning of multi-tier Internet applications]. ACM Transactions on Autonomous and Adaptive Systems 3(1), March 2008.</ref> or multi-service applications.<ref>Jiang Dejun, Guillaume Pierre and Chi-Hung Chi. [http://www.globule.org/publi/ARPMSWA_www2010.html Autonomous Resource Provisioning for Multi-Service Web Applications]. In Proceedings of the 19th International World-Wide Web conference, April 2010.</ref>
There are many [[software]] products available to automate the provisioning of servers, services and end-user devices from vendors such as [[Stratavia]], [[Sigma Systems]], <ref> [http://www.sigma-systems.com/Home.aspx?PageID=334 Sigma Systems Device Provisioning]</ref> [[BladeLogic]], [[IBM]],<ref>[http://www-306.ibm.com/software/tivoli/products/prov-mgrproductline/ IBM Tivoli]</ref> or [[Hewlett-Packard|HP]]. Middleware and applications can be installed either when the operating system is installed or afterwards by using an [[Application Service Automation]] tool. Further questions are addressed in academia such as when provisioning should be issued and how many servers are needed in multi-tier,<ref>Bhuvan Urgaonkar, Prashant Shenoy, Abhishek Chandra, Pawan Goyal and Timothy Wood. [http://doi.acm.org/10.1145/1342171.1342172 Agile dynamic provisioning of multi-tier Internet applications]. ACM Transactions on Autonomous and Adaptive Systems 3(1), March 2008.</ref> or multi-service applications.<ref>Jiang Dejun, Guillaume Pierre and Chi-Hung Chi. [http://www.globule.org/publi/ARPMSWA_www2010.html Autonomous Resource Provisioning for Multi-Service Web Applications]. In Proceedings of the 19th International World-Wide Web conference, April 2010.</ref>


In short, server provisioning configures servers based on resource requirements. The use of a hardware or software component (e.g. single/dual processor, RAM, HDD, RAID controller, a number of LAN cards, applications, OS, etc.) depends on the functionality of the server, such as ISP, virtualization, NOS, or voice processing. Server redundancy depends on the availability of servers in the organization. Critical applications have less downtime when using cluster servers, RAID, or a mirroring system.
In short, server provisioning configures servers based on resource requirements. The use of a hardware or software component (e.g. single/dual processor, RAM, HDD, RAID controller, a number of LAN cards, applications, OS, etc.) depends on the functionality of the server, such as ISP, virtualization, NOS, or voice processing. Server redundancy depends on the availability of servers in the organization. Critical applications have less downtime when using cluster servers, RAID, or a mirroring system.

Revision as of 16:15, 11 August 2010

In telecommunication, provisioning is the process of preparing and equipping a network to allow it to provide (new) services to its users. In NS/EP telecommunications services, "provisioning" equates to "initiation" and includes altering the state of an existing priority service or capability.[1]

In a modern signal infrastructure employing information technology at all levels, there is no distinction possible between telecommunications services and "higher level" infrastructure. Accordingly provisioning configures any required systems, provides users with access to data and technology resources, and refers to all enterprise-level information resource management involved.

From a management perspective, it is typically managed by a CIO, and necessarily involves human resources and IT departments cooperating to:

  • give users access to data repositories or grant authorization to systems, networks applications and databases based on a unique user identity, and
  • appropriate for their use hardware resources, such as computers, mobile phones and pagers.

As its most central responsibility, the provisioning process monitors access rights and privileges to ensure the security of an enterprise's resources and user privacy. As a secondary responsibility, it ensures compliance and minimizes the vulnerability of systems to penetration and abuse. As a tertiary responsibility, it tries to reduce the amount of custom configuration using boot image control and other methods that radically reduce the number of different configurations involved.

"Provisioning" often appears in the context of virtualization, orchestration, utility computing, cloud computing, and open configuration concepts and projects. For instance, the OASIS Provisioning Services Technical Committee (PSTC) defines an XML-based framework for exchanging user, resource, and service provisioning information, e.g. SPML (Service Provisioning Markup Language) for "managing the provisioning and allocation of identity information and system resources within and between organizations".

Once provisioned, the process of SysOpping ensures that services are maintained to the expected standards. Provisioning thus refers only to the setup or startup part of the service operation, and SysOpping to the ongoing responsibility.

Server provisioning

Server provisioning is a set of actions to prepare a server with appropriate systems, data and software, and make it ready for network operation. Typical tasks when provisioning a server are: select a server from a pool of available servers, load the appropriate software (operating system, device drivers, middleware, and applications), appropriately customize and configure the system and the software to create or change a boot image for this server, and then change its parameters, such as IP address, IP Gateway to find associated network and storage resources (sometimes separated as resource provisioning) to audit the system. By auditing the system, you ensure OVAL compliance with limit vulnerability, ensure compliance, or install patches. After these actions, you restart the system and load the new software. This makes the system ready for operation. Typically an internet service provider (ISP) or Network Operations Center will perform these tasks to a well-defined set of parameters, for example, a boot image that the organization has approved and which uses software it has license to. Many instances of such a boot image create a virtual dedicated host.

There are many software products available to automate the provisioning of servers, services and end-user devices from vendors such as Stratavia, Sigma Systems, [2] BladeLogic, IBM,[3] or HP. Middleware and applications can be installed either when the operating system is installed or afterwards by using an Application Service Automation tool. Further questions are addressed in academia such as when provisioning should be issued and how many servers are needed in multi-tier,[4] or multi-service applications.[5]

In short, server provisioning configures servers based on resource requirements. The use of a hardware or software component (e.g. single/dual processor, RAM, HDD, RAID controller, a number of LAN cards, applications, OS, etc.) depends on the functionality of the server, such as ISP, virtualization, NOS, or voice processing. Server redundancy depends on the availability of servers in the organization. Critical applications have less downtime when using cluster servers, RAID, or a mirroring system.

Service used by most larger scale centers in part to avoid this. Additional resource provisioning may be done per service.

User provisioning

User provisioning refers to the creation, maintenance and deactivation of user objects and user attributes, as they exist in one or more systems, directories or applications, in response to automated or interactive business processes. User provisioning software may include one or more of the following processes: change propagation, self service workflow, consolidated user administration, delegated user administration, and federated change control. User objects may represent employees, contractors, vendors, partners, customers or other recipients of a service. Services may include electronic mail, inclusion in a published user directory, access to a database, access to a network or mainframe, etc. User provisioning is a type of identity management software, particularly useful within organizations, where users may be represented by multiple objects on multiple systems.

See User provisioning software.

Mobile subscriber provisioning

This refers to the setting up of new services, such as GPRS, MMS and Instant Messaging for an existing subscriber of a mobile phone network, and any gateways to standard Internet chat or mail services. The network operator typically sends these settings to the subscriber's handset using SMS or WAP as mobile operating systems accept.

Mobile content provisioning

This refers to delivering mobile content, such as mobile internet to a mobile phone, agnostic of the features of said device. These may include operating system type and versions, Java version, browser version, screen form factors, audio capabilities, language settings and a plethora of other characteristics. As of April 2006, an estimated 5000 permutations are relevant. Mobile content provisioning facilitates a common user experience, though delivered on widely different handsets.

Internet access provisioning

The process of getting a user / customer online. Beyond user provisioning and network provisioning the client system must be configured. This process possibly includes many steps, depending on the connection technology in question (DSL, Cable, Fibre, etc.). The possible steps are:

  • modem configuration
  • authentication with network
  • install drivers
  • setup Wireless LAN
  • secure operating system (primarily for Windows only)
  • configure browser provider-specifics
  • e-mail provisioning (create mailboxes and aliases)
  • e-mail configuration in client systems
  • install additional support software
  • install add-on packages purchased by the customer
  • etc.
  • There are three approaches to provisioning an internet access.

  • hand out manuals
  • on-site setup by a technician
  • server-side remote setup
  • client-side self-service applications (installation CD)
  • Manuals are a great help for experienced users, but inexperienced users will need to call the support hotline several times until all internet services are accessible. Every unintended change in the configuration, by user mistake or due to a software error, results in additional calls. Sending a technician on-site is the most reliable approach from the provider’s point of view, as the person ensures that the internet access is working, before leaving the customer’s premises. This advantage comes at high costs – either for the provider or the customer, depending on the business model. Furthermore it is inconvenient for customers, as they have to wait until they get an installation appointment and because they need to take a day off from work. For repairing an internet connection on-site or phone support will be needed again. Server-side modem configuration uses a protocol called TR-069. It is widely established and reliable. At the current stage it can only be used for modem configuration. Protocol extensions are discussed, but not yet practically implemented, particularly because most client devices and applications do not support them yet. All other steps of the provisioning process are left to the user, typically causing lots of rather long calls to the support hotline. Vendors of such solutions include companies like Friendly Tech, [6] DS2, and Axiros.[7] A client-side self-service installation CD can cover the entire process from modem configuration to setting up client applications, including home networking devices. The software typically acts autonomously, i.e. it doesn’t need an online connection and an expensive backend infrastructure. During such an installation process the software usually also install diagnosis and self-repair applications that support customers in case of problems, avoiding costly hotline calls. Such client-side applications also open completely new possibilities for marketing, cross- and up-selling. Such solutions come from highly specialised companies such as mquadr.at[8] or directly from the provider’s development department.

    References

    1. ^ Public Domain This article incorporates public domain material from Federal Standard 1037C. General Services Administration. Archived from the original on 2022-01-22.
    2. ^ Sigma Systems Device Provisioning
    3. ^ IBM Tivoli
    4. ^ Bhuvan Urgaonkar, Prashant Shenoy, Abhishek Chandra, Pawan Goyal and Timothy Wood. Agile dynamic provisioning of multi-tier Internet applications. ACM Transactions on Autonomous and Adaptive Systems 3(1), March 2008.
    5. ^ Jiang Dejun, Guillaume Pierre and Chi-Hung Chi. Autonomous Resource Provisioning for Multi-Service Web Applications. In Proceedings of the 19th International World-Wide Web conference, April 2010.
    6. ^ Friendly-tech.com
    7. ^ Axiros.com
    8. ^ Mquadr.at

    External links