Thursday, September 30, 2010

облако

В ходе дискуссии нарылось достаточно, на мой взгляд, интересное определение что есть "Облако" в разных его ипостасях.
Может быть полезным в общении с руководством и продавцами.


The NIST Definition of Cloud Computing

Authors: Peter Mell and Tim Grance
Version 15, 10-7-09

National Institute of Standards and Technology, Information Technology Laboratory

Note 1: Cloud computing is still an evolving paradigm. Its definitions, use cases, underlying technologies, issues, risks, and benefits will be refined in a spirited debate by the public and private sectors. These definitions, attributes, and characteristics will evolve and change over time.

Note 2: The cloud computing industry represents a large ecosystem of many models, vendors, and market niches. This definition attempts to encompass all of the various cloud approaches.

Definition of Cloud Computing:


Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five essential characteristics, three service models, and four deployment models.

Essential Characteristics:
On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service’s provider.
Broad network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.
Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured Service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models:
Cloud Software as a Service (SaaS). The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Cloud Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models:
Private cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.
Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.
Public cloud. The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

Note: Cloud software takes full advantage of the cloud paradigm by being service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability.

Wednesday, September 29, 2010

пишем оперу

Сложные но необходимые в деловой переписке правила.



Imagine your document on the front page of The Financial Times, Wall Street Journal, Business Day, or another reputable publication, or being read out on CNN.  This may be the single best way to stay focussed as you write.

Imagine yourself in a witness box in Court or before a Tribunal, being cross-examined about the e-mail or document that you are writing.  This should also focus the mind!

Pick up the phone. Before sending an e-mail or creating another form of document or permanent record, consider whether it would facilitate communication and resolution of issues, particularly on sensitive matters, to have a face-to-face or telephone conversation.  Written communications are frequently necessary, but in many cases, face-to-face or telephone conversations are not only more effective and efficient, but can also reduce the risk of written records being misconstrued and save the company the considerable expense of document creation and retention.

Stick to your expertise.  The risk of a problematic document increases, for example, when an accountant comments on a marketing campaign, a marketing manager discusses accounting issues, or anyone offers an unsolicited opinion that something is “criminal” or “illegal.”

Prefer facts over opinions.  Opinions are much easier to argue about or misconstrue than facts.  For example, if someone says, "it's cold outside," a listener may find many reasons to disagree.  But if the statement is, "it's below zero today," the only area of disagreement is a thermometer reading.

Think how a competition authority might view your words.  Avoid language that could be misinterpreted, for example, by suggesting that you are co-coordinating any aspect of the company's commercial strategy with a competitor or that you are controlling your customer's resale prices.  Claims that we "dominate" or are "dominant" in markets or can "control" our customers or "punish" or “eliminate” our competitors, or that the competition has “significant barriers to entry” are also unhelpful.

Use some forms of humour judiciously.  Humour that prompts exaggeration can often be misinterpreted. Consider the comment, "the only thing that report is good for is my fireplace."  Now consider the impact of that comment (which inevitably will be found and produced in discovery) if the report in question cannot later be found in the company's records.

Count to 10 as needed.  Anger and frustration consistently yield poor word choices. For example: "I don't care how you do it. Just get it done"; "she is lying"; "this company will do anything for money."  Simply put, correspondence and reports are never good places to vent.
  
Double-check the distribution list.  Is everyone on the “to” line of your e-mail or memo critical to the communication?  What about the “cc” and “bcc” lines?  Omit recipients who aren’t necessary.

Avoid the use of company email for personal communication wherever possible.  Company e-mail is intended for the conduct of company business.  E-mails that are nothing more than personal communications with other employees or with persons outside the company will, however, have to be retained in the company’s electronic records for some period and may be subject to review and production in legal proceedings, particularly if the communication is in some way relevant to the company or its business.

Don't assume a message to a lawyer (in-house or external) is privileged.  A document that is protected by the attorney-client privilege need not be disclosed in litigation.  But keep in mind that a note to a lawyer is not automatically privileged.  If the discussion concerns only business issues and no legal issues, there may be no privilege.  Similarly, simply stamping the word "Privileged" on a document does not necessarily make it so.  If you intend a message to be privileged, be sure that you address it to a lawyer and, in so many words, either ask for legal advice and/or state that the message is in connection with pending or anticipated litigation.

Tuesday, September 28, 2010

турникеты и билеты

Транспорт в Англии стоит дорого. Адски дорого!
Особо это будет заметно, если ты турист и нет у тебя купленных заранее скидочных карт или возможности приобрести билет за пару недель до поездки. А бывает и потому, что не знает человек о некторых опциях, типа PlusBus, делающих поездку дешевле.
Перевозки выполняются очень качественно. Поезда в основном забиты несильно, ехать комфортно. Ну и организация на вокзалах отличная. За исключением турникетов.
На моей памяти не было такого случая, чтоб все установленные турникеты работали. И даже те, кто выглядят рабочими зачастую не работают. И даже если он работает, то не факт, что он тебя пропустит. Поэтому у турникетов стоят контролеры и пропускают тех, у кого не срослось с проходом. То же самое на выходе.
Именно поэтому у терникетов постоянное буление и неразбериха. И непонятно, что за препятствие стоит на пути починки так, чтоб все работало.

Friday, September 24, 2010

разминка

в очередной раз попробую начать отражать разные события в пиьменном виде.
для разминки. ну и для того, чтоб поржать, когда прочту. я, собственно, уже ржу, потому как знаю, что толково писать пока не обучен.
чего тут ждать:
- разных веселых и неочень деталей, связанных с жизнью в великобритании
- разных штук, которых я понахватаюсь в рамках новой моей работы
- разное