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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…