Skip to main content

Cum sa configuram Azure development storage pentru a putea fi accesat de catre toata echipa de dezvoltare

By
In mod default, cand pornim storage-ul local, acesta accesează 127.0.0.1. Dar ce ne facem daca avem o echipa de dezvoltare care doreste sa lucreze pe un storage comun. Prima posibilitatea este sa ne configuram un storage sus pe cloud, dar asta înseamna bani in plus si un lag, in cazul in care nu avem o conexiune foarte rapida.
O alta varianta este s schimbam configurarea pe mașinile de development, astfel incat acestea sa bata spre aceiasi adresa. Pentru a putea face acest lucru trebuie sa deschidem fisierul DSService.exe.config din directorul ~Program Files\Windows Azure SDK\v1.4\bin\devstore\DSService.exe.config. Sub nodul services o sa gasim lista de adrese pentru blobs, queue si tables.
Fiecare adresa a serviciului poate sa fie modificata, ca in exemplul de mai jos:
<services>
  <service name="Blob" url="http://10.123.1.9:10000/"/>
  <service name="Queue" url="http://10.123.1.9:10001/"/>
  <service name="Table" url="http://10.123.1.9:10002/"/>
</services>
Dupa ce am facut aceste modificări este nevoie sa dam repornim storage-ul pentru development.
Labels:

Comments

  1. TudorApril 17, 2011 at 12:10 PM

    Prespun ca si in ServiceConfiguration.cscfg va trebui specificat explict IP-ul, in genul:
    < Setting name="BlobStorageEndpoint" value="http://10.123.1.9:1000" />
    <Setting name="QueueStorageEndpoint" value="http://10.123.1.9:1001" />
    <Setting name="TableStorageEndpoint" value="http://10.123.1.9:1002"/>
    si deschise respectivele porturi in firewall, daca e cazul..

    ReplyDelete
  2. Radu VunvuleaApril 20, 2011 at 12:32 PM

    Da, configuratia la aplicatie trebuie schimbata si ea. Configurarea retelei si a FF se face de la caz la caz daca este nevoie.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...
Post a Comment
Read more

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

By
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...
8 comments
Read more