In oneM2M, can an announced resource have a non announced resource as it's child? I went through the documentations for oneM2M but can't find anywhere that clearly mentions this.
For example, on my IN-CSE, I have created an announced AE (AE_ANNC), then I create an announced Container (CNT_ANNC), now can I have a normal Content Instance (non announced resource) inside this new announced container ie, inside CNT_ANNC.
Thanks in advance.
In oneM2M you can put a regular resource as a child of an announced resource. Specifically, the example that you provide is allowed.
There is not a lot of detail on this, but for each resource the table of child resources has a column to the right that indicates valid child resources of the announced variant of the resource. For your example,TS-0001 table 9.6.6-1 shows that a <containerAnnc> can have both <contentInstance> and <contentInstanceAnnc> child resources.
Related
Recently I was provisioning a new Azure Synapse resource, which ended up creating 2 different resource groups.
I understand a resource group is basically a container for related items, fair enough but thinking about it more I am actually confused why would Azure decide to create two separate resource groups instead of just putting it all into one?
The bigger burning question I have is after creating a number of resources - Lets say each one spawns multiple resource groups.
How can I tell which resource group is a "child" or a "parent" of another?
#rodneyc8063 Thanks for updating the concern of your question. Posting your discussion in the comments as an Answer to help other community members.
As said by Daniel Mann you are getting the additional resource group because your synapse workspace is creating the managed resource group.
A managed resource group is like a container which can hold the resources required by your resource. It is created by default when your workspace is created.
You can name it if you want, else its name will be created automatically.
When you delete the Main Resource Group of your resource, then the resources inside it also will be deleted.
The managed resource group also deleted when you delete the resource(managed application).
That’s why the second resource group is deleted when you delete the first one.
As far as I know apart from this there is no relationship between them.
References:
Overview of managed applications - Azure Managed Applications | Microsoft Docs
Blog from DataSimAntics about managed resource group.
Given that managed resource groups are mandatory for creating an Azure Databricks cluster, is there any way that I can tag the resource group in order to comply with the tagging policy on my subscription?
I am using the template here to deploy my resources.
Based on the post I found:,
Since Feb 10 2020, the Databricks resource will propagate any tags applied to the Databricks resource to the managed resources it created.
I think the solution is more simpler now by tagging Databricks resource directly.
Hope this answer (by others) works for everyone seeing this post.
Any tags that you use when creating the Databricks workspace will be used for the managed resource group as well so just make sure you add the needed tags to the workspace when creating it. I know this works when creating the workspace from the Azure Portal but I can't see any reason this wouldn't work when using ARM templates (or Terraform for that matter).
Also, I'm also pretty sure that future changes will be propagated to said resource group.
What actually happens within Azure when I create a resource with Azure Management Libraries, and then recreate the same exact resource? Does it "see" that the same exact resource is there and doesn't do anything? Or does it wipe out the existing resource and create a new, exact same one?
If there is a resource within azure, then you try to use Management Libraries to create the same exact resource. The library will first check it's name availability, if the name is in used(which means it's not available), then it will return false(an error will throw in your code) to indicate you cannot create this resource.
Hope it helps.
Is there any way to disable or stop a particular resource group temporarily? I know we can delete the resource group or we can stop certain services under the resource group but I am unable to find a way where I can just shut down the resource group or all of it's resources at once, temporarily.
Please let me know if I can provide few more details about this.
Thanks.
This does not seem to be possible at the moment but a request has been made here, however, no response from Microsoft on what it's status.
In general, if there are features that are not available in e.g. Azure, use the feedback site to suggest and vote on new features.
However, if you only got some specific type of resources in your resource group, like e.g. virtual machines, then you can stop them all in one PowerShell command like this:
Get-AzureRmResourceGroup <group name> | Stop-AzureRmVM -Force
Note: this approach is highly dependent on the type of resource and not a generic solutions like requested
A resource group is just a bounding-box, serving as a grouping mechanism and a security boundary. You cannot "stop" a resource group, as a resource group is never running. Yes, you can delete a resource group (along with everything in it), but that's a one-shot operation. It's not a fine-grained resource-management operation.
As for the services inside a resource group: some can be stopped, some cannot. For instance, you cannot stop a storage account. Others have very different behaviors when stopped: A VM simply sleeps/hibernates until restarted with everything preserved, while an HDInsight cluster, when stopped, deletes everything.
TL;DR there is currently no way to point to a resource group and have it stop all of its services, given the variability of behavior (and the fact there's no such supported API). You'll need to manage your resource starts/stops.
I just had a new "MSDN account" hit its budget limit and that made me realize this SHOULD be achievable!
When this happened Microsoft "disabled" my subscription.
In my case, I'm actually fine with having to "fence the resources" within a subscription if I had to. But at the moment, I haven't found a way to easily stop/start it in this manor. Anyone a guru with the Azure budgets? It looks like they can be applied at a Resource Group level as well.
Can you "enable/disable" resource groups or subscriptions this way?
Simply want to create something. Pay for it, of course. Pay for storage, sure. But 'disable' it, until I need to run it. Then, Enable it. Simple. :)
I've been upvoting and watching this "Feature Request" thread for some time:
https://feedback.azure.com/forums/217313-networking/suggestions/17670613-hibernate-pause-a-resource-group-or-subscription
I am trying to move all my current Azure services to my new Azure BizSpark Plus account. Following this article, there is this little note that needs to be checked before the move (see image below):
I understand that tools and scripts associated with moved resources will not work until I update them to use new resource IDs
What does this mean? Will I have to update my Azure API keys or Azure script URL in my client apps? Should I expect a downtime? How can I update the 'tools and scripts' to use the 'new resource ID'?
Note: the little exclamation mark lead back to the same article mentioned above.
Your IDs for your resources are in the format:
resource/subscriptions/[subscription id]/resourceGroups/[resource group name]/providers/Microsoft.Web/sites/[app name]/appServices
As you can see, the resource group name is part of that unique Id, so moving it to a new resource group changes that Id.
The warning is simply stating that if you currently have any tools or scripts that reference the resource using the old resource group name, they will need to be updated to the use the new Id.