# Restrict topology attributes by deault

**URL:** <https://forum.opennebula.io/t/restrict-topology-attributes-by-deault/8149>\
**Category:** Integration Support\
**Created:** [March 6, 2020, 2:16pm UTC](https://forum.opennebula.io/t/restrict-topology-attributes-by-deault/8149 "2020-03-06T14:16:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kvaps](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/kvaps/32/4496_2.png) [@kvaps](https://forum.opennebula.io/u/kvaps)\
**Post date:** [March 6, 2020, 2:16pm UTC](https://forum.opennebula.io/t/restrict-topology-attributes-by-deault/8149/1 "2020-03-06T14:16:29Z")

</div>

Hey, shouldn’t we restrict setting NUMA topology for the users by default?

```auto
VM_RESTRICTED_ATTR = "TOPOLOGY/CORES"
VM_RESTRICTED_ATTR = "TOPOLOGY/HUGEPAGE_SIZE"
VM_RESTRICTED_ATTR = "TOPOLOGY/MEMORY_ACCESS"
VM_RESTRICTED_ATTR = "TOPOLOGY/PIN_POLICY"
VM_RESTRICTED_ATTR = "TOPOLOGY/SOCKETS"
VM_RESTRICTED_ATTR = "TOPOLOGY/THREADS"

```

Eg user can allocate too many resources by this:

```auto
TOPOLOGY = [
  CORES = "9999",
  PIN_POLICY = "THREAD",
  SOCKETS = "9999" ]

```

---

<div class="post-metadata">

**Author:** ![cgonzalez](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/cgonzalez/32/7096_2.png) [@cgonzalez](https://forum.opennebula.io/u/cgonzalez)\
**Post date:** [March 9, 2020, 8:38am UTC](https://forum.opennebula.io/t/restrict-topology-attributes-by-deault/8149/2 "2020-03-09T08:38:43Z")

</div>

Hello @kvaps,

That’s make total sense, can you open a GitHub issue for that?