slntopp / nocloud Goto Github PK

Describe the bug

Deleting dns zone from Admin UI leaves an empty key. So i case there are two records

A *       10.0.0.0
A test  172.0.0.0

And we delete the test record from FE, it actually stays in the backend as test: {}.
In such situation, attempts on resolving test. subdomain, will end up failed with no such host error

Front-end Used

• Admin UI
• CLI
• Cloud App
• Other

• Registry
• Services Registry
• Services Providers Registry
• ArangoDB
• Driver(s)

• Accounts Model
• Namespaces Model
• Permissions Graph
• Credentials Model
• Credentials Graph
• Accounts Proto
• Accounts API
  • Authorize
  • Create Account
  • #15
  • Get Account
  • #14
  • Delete Account
  • #16
  • Update Credentials
• Namespaces API
  • Create Namespace
  • Add Account to Namespace
  • List Namespaces
  • Get Namespace
  • Update Account -> Namespace access
  • Remove Account -> Namespace access
  • Delete Namespace
  • Give Namespace to Account
  • Update Namespace -> Account access
  • Delete Namespace -> Account access
• Authorization mechanism
• #13

Methods:

• Create/Update => Upsert permission between any Nodes
• Delete => Delete permission
• Transfer Ownership
• Check Access (to use in other controllers instead of direct HasAccess and AccessLevel functions calls)

Instance:

{
 "uuid": "UUID | string",
 "title": "Instance title | string",
 "state": { init, create, deploy, boot, runn, shut, off, deleted },
 "deploy_id": "Instance ID at back-end(KVM/Docker/etc)",
 "permissions": [ // One to Many
    Permission
 ],
 "host": Host, // One to One
 "resources": { // Instance Resources description per each type
    "type": Object<any>{} // like "aws": { "tier": "tierType" } or/and "kvm": { "cpu": "2", "ram": "4", ... }
 },
 "attributes": { // Other attributes description per each type
    "type": Object<any>{} // like "docker": { "container_name": "not_default_name" }
 }
}

This is not final Instance schema, and can be extended further

• Create Cursor/Connector
• Models packages
  • VMs(Deployable)
  • Accounts
  • Groups
• DB & DB Connection Health Probe
• Indexes
  • Standard Credentials by Username

• Basic Driver Package
• Basic Driver Listen Deploy Action Example
• Service to User IONe Driver

Host:

{
 "uuid": "UUID | string",
 "title": "Instance title | string",
 "permissions": [ // One to Many
    Permission
 ],
 "type": "End Host service type(example/KVM/Docker)"
}

Resource Permission:

{
    "account": "UUID of User account or Group | string",
    "resource": "UUID of Resource(Instance, Network, Datastore, etc)",
    "access": { none, read, write, admin }
}

• Test
• Create
• Manage Access
• Up
• Down
• Delete

• Generate bills (accounting data) per instance, pre group and per Service
• Store bills in TS
• Create User role - Wallet(user which has balance, which can be used for debiting bills)
• Make transactions to Wallet Users and store them

Service connected to DB, with few methods(create/delete/edit) and most importantly verify method, like Verify(account{id, group_id}, resource_id)

Proxy and Validate requests to IONe
Map Zones to NoCloud Hosts

• Gather Resources state info (cpu-ram time, drives, etc)
• Store Resources state info into TimeSeries DB

• Monitor instances states every N seconds
• Monitor ServicesProviders state every N seconds
• Configure N in settings

• #18
• #19
• Service Model
  • Title
  • Config
  • Config Hash
  • Balance
• Service API
  • Validate Instances
  • Create Service and Instances
  • Update Service and Instances
  • Delete Service and Instances
  • Perform Service Action
  • Perform Instance Action
• Instance Model
  • Title
  • State
  • Config
  • Config Hash
  • Logs

Tracking issue for:

• https://github.com/slntopp/nocloud/security/code-scanning/4

• Add new instances
• Delete removed instances
• Update existing instances