Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OneGate is not getting NIC_ALIAS information #4361

Closed
7 tasks
rdiaz-on opened this issue Mar 16, 2020 · 0 comments
Closed
7 tasks

OneGate is not getting NIC_ALIAS information #4361

rdiaz-on opened this issue Mar 16, 2020 · 0 comments

Comments

@rdiaz-on
Copy link
Contributor

Description
The NIC_ALIAS information of virtual machines is not available on OneGate command calls.

To Reproduce
Having a flow similar to this:

$ oneflow show 19
SERVICE 19 INFORMATION                                                          
ID                  : 19                  
NAME                : myflow               
USER                : oneadmin            
GROUP               : oneadmin            
STRATEGY            : straight            
SERVICE STATE       : RUNNING             

PERMISSIONS                                                                     
OWNER               : um-                 
GROUP               : ---                 
OTHER               : ---                 

ROLE router
ROLE STATE          : RUNNING             
VM TEMPLATE         : 1                   
CARDINALITY         : 1                   
NODES INFORMATION
 VM_ID NAME                    STAT UCPU    UMEM HOST                       TIME
    44 router_0_(service_19)   runn           0K localhost              0d 22h15

ROLE worker
ROLE STATE          : RUNNING             
PARENTS             : router              
VM TEMPLATE         : 1                   
CARDINALITY         : 2                   
NODES INFORMATION
 VM_ID NAME                    STAT UCPU    UMEM HOST                       TIME
    45 worker_0_(service_19)   runn           0K localhost              0d 22h15
    46 worker_1_(service_19)   runn           0K localhost              0d 22h15


LOG MESSAGES                                                                    
03/15/20 10:38 [I] New state: DEPLOYING
03/15/20 10:39 [I] New state: RUNNING

A virtual machine has attached a NIC ALIAS:

$ onevm show 45

...

VIRTUAL MACHINE TEMPLATE                                                        
AUTOMATIC_DS_REQUIREMENTS="(\"CLUSTERS/ID\" @> 0)"
AUTOMATIC_NIC_REQUIREMENTS="(\"CLUSTERS/ID\" @> 0)"
AUTOMATIC_REQUIREMENTS="(CLUSTER_ID = 0) & !(PUBLIC_CLOUD = YES) & !(PIN_POLICY = PINNED)"
CONTEXT=[
  DISK_ID="1",
  ETH0_ALIAS0_CONTEXT_FORCE_IPV4="",
  ETH0_ALIAS0_DNS="",
  ETH0_ALIAS0_EXTERNAL="",
  ETH0_ALIAS0_GATEWAY="192.168.100.1",
  ETH0_ALIAS0_GATEWAY6="",
  ETH0_ALIAS0_IP="192.168.100.50",

...

The NIC_ALIAS information is not shown when running onegate service show -j or onegate vm show -j:

localhost:~# onegate vm show -j
{
  "VM": {
    "NAME": "worker_0_(service_19)",
    "ID": "45",
    "STATE": "3",
    "LCM_STATE": "3",
    "USER_TEMPLATE": {
      "INFO": "Please do not use this VM Template for vCenter VMs. Refer to the documentation https://bit.ly/37NcJ0Y",
      "INPUTS_ORDER": "",
      "KEY": "VALUE",
      "LOGO": "images/logos/linux.png",
      "LXD_SECURITY_PRIVILEGED": "true",
      "MEMORY_UNIT_COST": "MB",
      "READY": "YES",
      "ROLE_NAME": "worker",
      "SCHED_REQUIREMENTS": "HYPERVISOR!=\"vcenter\"",
      "SERVICE_ID": "19"
    },
    "TEMPLATE": {
      "NIC": [
        {
          "IP": "172.16.100.3",
          "MAC": "02:00:ac:10:64:03",
          "NETWORK": "vnet"
        }
      ]
    }
  }
}

Expected behavior
When running onegate service show -j or onegate vm show -j you should get an output similar to this:

# onegate vm show -j
{
  "VM": {
    "NAME": "worker_0_(service_19)",
    "ID": "45",
    "STATE": "3",
    "LCM_STATE": "3",
    "USER_TEMPLATE": {
      "INFO": "Please do not use this VM Template for vCenter VMs. Refer to the documentation https://bit.ly/37NcJ0Y",
      "INPUTS_ORDER": "",
      "KEY": "VALUE",
      "LOGO": "images/logos/linux.png",
      "LXD_SECURITY_PRIVILEGED": "true",
      "MEMORY_UNIT_COST": "MB",
      "READY": "YES",
      "ROLE_NAME": "worker",
      "SCHED_REQUIREMENTS": "HYPERVISOR!=\"vcenter\"",
      "SERVICE_ID": "19"
    },
    "TEMPLATE": {
      "NIC": [
        {
          "IP": "172.16.100.3",
          "MAC": "02:00:ac:10:64:03",
          "NETWORK": "vnet"
        },
      "NIC_ALIAS": [
        {
          "IP": "192.168.100.50",
          "NETWORK": "othervnet"
        }
      ]
    }
  }
}

Details

  • Affected Component: OneGate
  • Version: from 5.10

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
atodorov-storpool added a commit to atodorov-storpool/one that referenced this issue Mar 16, 2020
Added the NAME attribute to have info for the NIC_ALIAS to NIC relation

Signed-off-by: Anton Todorov <a.todorov@storpool.com>
rdiaz-on pushed a commit to rdiaz-on/one that referenced this issue Mar 16, 2020
The NIC_ALIAS information of virtual machines is not available on
OneGate command calls

Signed-off-by: Ricardo Diaz <rdiaz@opennebula.systems>
rsmontero pushed a commit that referenced this issue Mar 16, 2020
Signed-off-by: Anton Todorov <a.todorov@storpool.com>
@rsmontero rsmontero added this to the Release 5.10.4 milestone Mar 16, 2020
rsmontero pushed a commit to OpenNebula/docs that referenced this issue Mar 16, 2020
Signed-off-by: Ricardo Diaz <rdiaz@opennebula.systems>
christian7007 pushed a commit that referenced this issue Mar 17, 2020
Signed-off-by: Anton Todorov <a.todorov@storpool.com>
rsmontero pushed a commit that referenced this issue Apr 7, 2020
Signed-off-by: Anton Todorov <a.todorov@storpool.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants