Skip to main content

Definition of Private Cloud


In the last month a lot of people started to talk about private cloud. When people refer to private cloud, they already have an image in their mind with machines that are hosted by them.
The “private cloud” term in general don’t refer to a cloud (like Windows Azure) that is hosted by the client.
The term “private cloud”, that now is used more and more refers to a computing power and storage that is accessible by only a limited numbers of devices (machines). This private network that is created can be behind a firewall or in a private network that is not connected to the internet.
 The key term of this definition is “private”. Only a limited number of users can access these resources. Using virtualization and distributed computing can allow administrators to create very complicated networks and datacenters that provide access to different services and resources for all the consumers from that network. All the information that flow on a private cloud is controlled by the administrators of that private cloud.
Physically, the private cloud doesn’t need to be on machines that are owned by the company. A private cloud can have 3 types of configuration:
  • All the physical machines are own and hosted by the client.
  • All the physical machines are in a public cloud (for example in Windows Azure). In this case the machines are in a private network that can be accessed only from that network.
  • A part of physical machine is from a private network of the client but also from a public cloud like Windows Azure. In this case a private network exists between all this machines. All the data that exist in this private network can be accessed only from the network.  
The properties of a private cloud should be the following:
  • Scalable
  • Shared
  • Elastic implementation
  • Automated
From what we saw, a private network can have different configuration. The networks that form the private cloud (computing resources, data and so on) have limited access. Only from that private network this resources can be accessed and consume. The customer has the control and ownership of all the content regardless of location. The provider of this services offer limited access to this resources – only for the client that need the private cloud.

Comments

  1. Another "definition" of private cloud would be: "I am a very, very large enterprise, I want to use Azure, but I don't want to host my app on Microsoft datacenters" - now I can go to Fujitsu or HP with my Azure apps.. ;)
    (desi unii zis ca "private cloud" ar fi o contradictie in termeni: http://news.cnet.com/8301-13556_3-10150841-61.html)

    ReplyDelete
    Replies
    1. sorry for my romenglish :)
      (although some said that "private cloud" is a contradiction in terms: http://news.cnet.com/8301-13556_3-10150841-61.html)

      Delete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...