TritonDataCenter / TritonDataCenter/sdc-cloudapi
Owned NonFabric Networks don't show network information
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 22
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Networks that are owned by a tenant, but aren't fabrics don't display Subnet / Gateway information during triton networks.
/g/i/consul ❯❯❯ tt networks
SHORTID NAME SUBNET GATEWAY FABRIC VLAN PUBLIC
4b609af0 My-Fabric-Network 192.168.128.0/22 192.168.128.1 true 2 false
a0ae9499 consul_demo 192.168.10.0/24 192.168.10.1 true 2 false
b3c03534 home - - - - false
913849ab nexus 10.0.0.0/24 10.0.0.1 true 20 false
17d7aa50 sdc_nat - - - - true
owner:
[root@headnode (us-east-1) ~]# sdc-napi /networks/b3c03534-0380-43d2-83b6-45a112dcd057
HTTP/1.1 200 OK
Etag: 070215F5
Content-Type: application/json
Content-Length: 370
Date: Thu, 06 Dec 2018 01:42:15 GMT
Server: SmartDataCenter Networking API
x-request-id: 1d788afc-7f5f-4f45-ace1-4a9057027b9b
x-response-time: 65
x-server-name: b5c8e696-cce3-4eba-9163-984bb636c896
Connection: keep-alive
{
"family": "ipv4",
"mtu": 1500,
"nic_tag": "home",
"name": "home",
"provision_end_ip": "192.168.2.250",
"provision_start_ip": "192.168.2.100",
"subnet": "192.168.2.0/24",
"uuid": "b3c03534-0380-43d2-83b6-45a112dcd057",
"vlan_id": 0,
"resolvers": [
"192.168.1.1",
"8.8.8.8"
],
"gateway": "192.168.2.1",
"routes": {},
"owner_uuids": [
"4b60d82b-d858-4c5a-ea3e-a0b9b411d65d"
],
"netmask": "255.255.255.0"
}
account:
/g/i/consul ❯❯❯ tt account get ✘ 1
id: 4b60d82b-d858-4c5a-ea3e-a0b9b411d65d
login: smith
email: smith@smith.com
companyName: rawr
firstName: bruce
lastName: smith
triton_cns_enabled: true
phone: 510-123-3214
updated: 2018-11-30T18:38:14.208Z (5d)
created: 2018-11-07T04:33:26.359Z (4w)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the tt networks command and trace how it handles the sdc-napi /networks response for owned, non-fabric networks. Compare the displayed rows with the response fields, then verify that subnet and gateway information appears for networks like home.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100