My work place has a software integration with an Australian government agency, that has a specific requirement that our software and any version of it, must reside wholly geographically within Australia.
We currently use Azure DevOps previously known as TFS (Team Foundation Services) and I'm fairly certain it's hosted in the States which violates their terms. And I'd assume so too is GitHub. We only a 4 man team and we're not doing pipelines or anything else, just version control and so far it's been free. I'd prefer to stick with DevOps so I don't have to re-train the old dudes, who happen to be the business owners.
Is it possible to use DevOps Services or Server but specifically hosted in and perhaps also geo-locked for Australia only?
Based on the information provided here, you can choose to have your Azure DevOps instance and data located in Australia (Australia is one of the supported geographies). You can specify the region while creating your organization or by raising a support ticket later on.
If this does not work for you, you can always opt to host Azure DevOps on-premise using Azure DevOps Server. You can learn more about it here: https://azure.microsoft.com/en-us/services/devops/server/.
Related
How to migrate Boards, Pipeline, Test Plan, Artifacts and Repo from on-prem azdevops server to Existing organization in azdevops service? Is it any different tool available?
The different migration options are explained in the official documentation. There are some existing tool (see this High fidelity database migration option) but do not expect a 1:1 migration, you might loose some stuff in between. Depending on the criticality of your data, it might not be an issue though and could be enough.
The best probably remains to do it manually/using the APIs.
There is no officially supported way to merge 2 Azure DevOps Organisations or an Azure DevOps Server with an Azure DevOps organization.
With the official import tooling each Project Collection on your Azure DevOps Server will be mapped to a new Azure DevOps Organization.
There are all kinds of tools that can replay the history of work items and test plans. You can git mirror repositories from one place to another. You can use git-tfs or 3rd party tools to migrate TFVC history from one organization to another. Azure Pipelines can be exported/imported and Azure Artefacts can be downloaded/uploaded with the native tools for each kind of supported artifact feed.
This process is complicated, cannot be 100% and will cause certain data to be altered or lost. Since work item IDs and changesets and test case/plan IDs are unique per Organization it's impossible to migrate with these ids in tact. Hence all kinds of mapping and remapping is required. Certain dates (like Created Date, Changed Date) can't be overridden and will be reset to the time of migration
I'm a member of one of my colleague's personal Azure DevOps Services organization (I hope I'm using that term correctly). And there's another Azure DevOps organization that we're both a part of. In my colleague's personal organization there's a project I've been working on for a while. My colleague and I both agree that it would be best, at this time, to move that project from his personal organization to our company's organization in Azure DevOps Services. Only, we don't know how to do that.
So, is it possible to move a project (code, wiki, board, etc.) from one Azure DevOps organization to another? If so, how do I go about doing that?
Daniel Mann's answered my question in his comment in reply to my question:
No, it's not possible to move a project between organizations. The
best you can do is employ various migration tools to recreate the work
item data in the new organization, and accept that there is going to
be some degree of loss of fidelity. For example, you can easily move
your repos, but pull requests are simply not transferrable.
I am provisioning a new VM for Windows to run some samples using Python notebooks and sql server. The existing samples are using the classic portal. In the new portal, I have the options to add or provision one of two VMs:
Data Science Virtual Machine runs on Windows
Data Science Virtual Machine runs on Windows (CSP)
I want to know the difference; I might be misreading it, it seems one has license (CSP's description says "Bring Your Own License enabled.")? Also, When should one pick one over the other?
Thanks.
The CSP editions of the Data Science Virtual Machine (#DSVM) are only deployable in CSP (Cloud Solution Provider) based subscriptions. CSPs are Microsoft Partner companies that are certified to re-sell Microsoft cloud services and provide value added services on top.
Here's a comparison of the different licensing modes that are available:
Licensing Modes for Cloud Services
If you are not using a CSP subscription you deploy the non CSP offers. As the CSP offers require the licenses to be provided by a CSP and on a CSP Licensing Agreement.
We are a small company and are still unsure how to start all this azure stuff.
Ok, we are clear on the technicalities like table storage and queues and all the that stuff, what we don't know about at all is how to set up the organization around developing for our developers. Which/how many azure accounts, shared or individual ones.
So far we've done classic windows development, so everyone has his environment, unit tests run either locally or on the build server (after pushing to mercurial or git), deployment from the build server.
The thing is that we want to use Azure not just as a hoster, but the full set, like blob/document/table storage, event hubs, storage queues, ReliableActors and everything. Things we can't do locally.
What's the appropriate way for azure then? There are about 20 to 30 developers and most have the enterprise msdn subscription.
What is a "company or organisation" account for? Should developers have their own accounts? Does DevOps need their passwords for all the bamboo or jenkins build stuff?
I went through this recently and I can share a few tips here since I'm also not aware of a DevOps specific platform to share this on StackExhange.
As far as organizing your subscriptions go look at Azure Pay-As-You-Go Dev/Test Subscriptions link
or Enterprise Dev/Test link if you are an Enterprise Agreement customer. These are aimed at development teams, you get discounted rates since you don't pay for software licenses that are already included in your MSDN subscription.
It is best to use individual developer subscriptions for exploration, POC etc while running your main dev workload in the Dev-Test subscription. It looks tempting to try and save a buck by spreading the work across multiple MSDN subscriptions to use the credits but I wouldn't recommend it. It becomes a pain to manage 20~30 subscriptions and they can run out of credits and things stop working. If you remove the spending limit on all the subscriptions you run the risk of racking up a huge bill accidently if multiple devs leave VMs on or add premium storage to VMs etc.
As far as DevOps go, use RBAC and Azure Active Directory to manage access and certificates for your DevOps tooling, build servers, release management etc don't use individual developer credentials for this.
And I agree with the other comments, get in touch with MS as well, this is just the tip of the iceberg but it will get you started.
I'm an MSDN subscriber beginning a personal project that will involve WPF, Web Services, and SQL Server. I'm planning on using my MSDN benefits to host the Web Services on Azure and the database on SQL Azure.
I was going to run TFS on my own dev machine, but then heard about Microsoft's Team Foundation Service cloud offering. Also, it appears that I could run my own instance of TFS on Azure. At this point I'm thinking that Team Foundation Service is the best option because:
I'd prefer to have TFS in the cloud over my main dev machine so that I can access it anywhere and not have to worry about having to back it up.
I'd rather not have to worry about setting up and administrating TFS on Azure if I'm not getting anything extra out of it.
I'm not exactly sure if setting up and using TFS on Azure will be free (or continue to be free) with my MSDN Subscription.
Has anyone experienced any major drawbacks to using Team Foundation Service, like a major loss of flexibility or functionality?
I've been using TFS Services since it has been in preview for my personal work - and I haven't had any limitations in terms of source control/build services. The service is fairly comparable to the full TFS server; but doesn't include the more advanced features such as test automation.
The pricing page also states that service will continue to remain free for MSDN subscribers: https://tfs.visualstudio.com/en-us/pricing/information/
Before TFSPreview existed, I asked some people in the know at MS about running TFS in Azure and I was told that there are some non-trivial problems with running TFS on a virtual machine on Azure. I believe this is why MS are offering TFS as a service rather than as a template for a virtual machine. As such, if you want to use TFS and you want it to be in the cloud, I'd definitely use the TFS Preview.