Hello Michael, The external network of 10.12.25.0/24 was in place before Oct 1st 2017. Using this network we quickly ran out of IP addresses.
To address this the lab was moved to an external network 10.12.0.0/16. But we left 10.12.25.0/24 in place as network-obsolete until Amsterdam was released (well really until just before Dec 31). Post Jan 1st ’18 we only have the 10.12.0.0/16 network: Range in 10.12.0.0/16 network Usage 10.12.0.0 – 10.12.4.255 Reserved for future use 10.12.5.0 – 10.12.8.255 ONAP Developers range - reserved for the external network 10.12.9.0 – 10.12.9.255 Reserved for ONAP demo usage (i.e. MWC and other marketing events) 10.12.10.0 – 10.12.24.255 Reserved for future use 10.12.25.1 Lab Gateway 10.12.25.2 – 10.12.25.255 VPN accounts 10.12.26.0- 10.12.255.254 Reserved for future use. Since the external gateway remained 10.12.25.1. If a VM uses 10.12.5.0/24 or 10.12.6.0/24, the gateway would not be reachable. I think this is what you are seeing. The correct range for VMs, directly connected to the external network, to use is 10.12.5.0/16 – 10.12.8.255/16 Br, - Stephen From: Michael O'Brien [mailto:frank.obr...@amdocs.com] Sent: Wednesday, January 17, 2018 18:16 To: Gooch, Stephen; Yunxia Chen Cc: onap-discuss Subject: RE: [integration]Please help us on Integration Lab Stephen Very nice appreciated - actually I was just trying the new appc network as a bridge – that network was not mine. The actual network I used in the past – should have looked it up – was “external-obsolete” on 10.12.25.0/24 which worked very well as a direct network not requiring an EIP. https://wiki.onap.org/display/DW/Vetted+vFirewall+Demo+-+Full+draft+how-to+for+F2F+and+ReadTheDocs#VettedvFirewallDemo-Fulldrafthow-toforF2FandReadTheDocs-OpenlabVNCandCLI The 10.12.6.0/24 EIP works well – thanks But I am unable to get any more 10.12.6.0/24 IPs allocated. I can allocate 10.12.5.0/24 and 10.12.9.0/24 EIP – but they will not attach to VMs in the same network. I tried another vm on 10.12.6.0/24 – the appc network (not mine) and I cannot get into this box either via my Jenkins with the EIP or directly Usually I am ok with public/vpc tunneling but having a hard time for some reason I don’t need anything special – just the ability to ssh directly or ssh tunnel via the jump box into additional VM’s I’ll try to write up the ssh tunneling procedure later – I think it is the way I am associating my vms with the 3 networks – will look into this and get back to you. Thank you Stephen /michael From: Gooch, Stephen [mailto:stephen.go...@windriver.com] Sent: Wednesday, January 17, 2018 04:18 To: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; Yunxia Chen <helen.c...@huawei.com<mailto:helen.c...@huawei.com>> Cc: onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: RE: [integration]Please help us on Integration Lab HI Michael, I am not positive how VMs connected to appc-multicloud-integration were directly accessed from the public network (the network the VPN accounts and jumpstation are on) without a floating IP. However, I assigned the oom-jenkins VM a floating IP on the public network (external), and now you can reach it: wrs_sgooch@pod-onap-01-vjhost:~$ nova list --all | grep oom-jenkins | awk {'print $4,$14,$15'} oom-jenkins appc-multicloud-integration=10.10.5.14, 10.12.6.49 wrs_sgooch@pod-onap-01-vjhost:~$ ssh -i openlab_oom_key.pem ubuntu@`nova list --all | grep oom-jenkins | awk {'print $15'}` Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-64-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage Get cloud support with Ubuntu Advantage Cloud Guest: http://www.ubuntu.com/business/services/cloud 0 packages can be updated. 0 updates are security updates. Last login: Wed Jan 17 08:51:07 2018 from 10.12.5.140 To run a command as administrator (user "root"), use "sudo <command>". See "man sudo_root" for details. ubuntu@oom-jenkins:~$ Br, -Stephen From: Michael O'Brien [mailto:frank.obr...@amdocs.com] Sent: Tuesday, January 16, 2018 19:16 To: Gooch, Stephen; Yunxia Chen Cc: onap-discuss Subject: RE: [integration]Please help us on Integration Lab Stephen, Hi, thank you – saw the return to service this morning – very nice!. I am still having SSH issues due to the network refactor over the holidays – we used to be able to get to 10.12.5.0/24 nodes directly – but some of those externally facing networks are gone. Currently using the jump box/bastion box instead – I still have ssh issues to vms I will test password-only access instead of ssh – is there a new procedure on which network to attach to our vm so we can get into it Thank you From the jira still having an issue with ssh between nodes – either directly or fron the jump box michael_o_brien@pod-onap-01-vjhost:~$ ssh -i openlab_oom_key.pem ubuntu@10.12.5.14<mailto:ubuntu@10.12.5.14> ssh: connect to host 10.12.5.14 port 22: Protocol not available oom-jenkins<http://10.12.25.2/project/instances/a44cd6d0-f5e7-493e-8a61-48df317e557d/> (not found) appc-multicloud-integration * 10.10.5.14 m1.xlarge<http://10.12.25.2/project/instances/> openlab_oom_key Active nova None Running 6 days, 13 hours Create Snapshot<http://10.12.25.2/project/images/a44cd6d0-f5e7-493e-8a61-48df317e557d/create/> oom-obrien-64<http://10.12.25.2/project/instances/dc78c7c8-1e99-40f1-89e7-e58c5b255868/> (not found) external * 10.12.5.10 m1.xxlarge<http://10.12.25.2/project/instances/> openlab_oom_key Active nova None Running 1 week, 4 days Create Snapshot<http://10.12.25.2/project/images/dc78c7c8-1e99-40f1-89e7-e58c5b255868/create/> oom-obrien-64-1<http://10.12.25.2/project/instances/a3e6b9e6-289a-4150-a610-a05ebec963a7/> (not found) oam_onap_6Gve * 10.0.0.29 m1.xxlarge<http://10.12.25.2/project/instances/> openlab_oom_key Active nova None Running 1 week, 4 days Create Snapshot<http://10.12.25.2/project/images/a3e6b9e6-289a-4150-a610-a05ebec963a7/create/> • Comment<https://jira.onap.org/secure/AddComment!default.jspa?id=17870> From: Gooch, Stephen [mailto:stephen.go...@windriver.com] Sent: Tuesday, January 16, 2018 04:05 To: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; Yunxia Chen <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>; Raineri, Eddy <eddy.rain...@windriver.com<mailto:eddy.rain...@windriver.com>>; Yang, Bin <bin.y...@windriver.com<mailto:bin.y...@windriver.com>> Cc: onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: RE: [integration]Please help us on Integration Lab Hello All, Lab access has been restored. Br, -Stephen From: Michael O'Brien [mailto:frank.obr...@amdocs.com] Sent: Monday, January 15, 2018 20:56 To: Yunxia Chen; Gooch, Stephen; Raineri, Eddy; Yang, Bin Cc: onap-discuss Subject: RE: [integration]Please help us on Integration Lab Fyi, I raised the issue on the VPN 36 hours ago after the Thu retrofit – service has been excellent and prompt – I would expect tomorrow we should be good. https://jira.onap.org/browse/OPENLABS-153 https://lists.onap.org/pipermail/onap-discuss/2018-January/007390.html For now you can consult the CD poc on AWS that is pending migration to the LF under (OOM-500<https://jira.onap.org/browse/OOM-500>) to at least get healthcheck hourly for master http://jenkins.onap.info/job/oom-cd/ http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(description:'',filters:!(),options:(darkTheme:!f),panels:!((col:1,id:AWAts77k3NTXK5mX2kuM,panelIndex:1,row:1,size_x:8,size_y:3,type:visualization),(col:9,id:AWAtuTVI3NTXK5mX2kuP,panelIndex:2,row:1,size_x:4,size_y:3,type:visualization),(col:1,id:AWAtuBTY3NTXK5mX2kuO,panelIndex:3,row:7,size_x:6,size_y:3,type:visualization),(col:1,id:AWAttmqB3NTXK5mX2kuN,panelIndex:4,row:4,size_x:6,size_y:3,type:visualization),(col:7,id:AWAtvHtY3NTXK5mX2kuR,panelIndex:6,row:4,size_x:6,size_y:6,type:visualization)),query:(match_all:()),timeRestore:!f,title:'CD%20Health%20Check',uiState:(),viewMode:view) Notice that the MSB fix has fixed the 8 failing heathcheck from the 13th – 3 hours ago https://gerrit.onap.org/r/#/c/27943/ thanks Stephen, /michael From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yunxia Chen Sent: Monday, January 15, 2018 10:15 To: Gooch, Stephen <stephen.go...@windriver.com<mailto:stephen.go...@windriver.com>>; Raineri, Eddy <eddy.rain...@windriver.com<mailto:eddy.rain...@windriver.com>>; Yang, Bin <bin.y...@windriver.com<mailto:bin.y...@windriver.com>> Cc: onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: Re: [onap-discuss] [integration]Please help us on Integration Lab Thank you Stephen. Since the team is doing MR testing, if possible, please help to get it up asap. Regards, Helen Chen From: "Gooch, Stephen" <stephen.go...@windriver.com<mailto:stephen.go...@windriver.com>> Date: Monday, January 15, 2018 at 7:10 AM To: Helen Chen 00725961 <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>, "Raineri, Eddy" <eddy.rain...@windriver.com<mailto:eddy.rain...@windriver.com>>, "Yang, Bin" <bin.y...@windriver.com<mailto:bin.y...@windriver.com>> Cc: onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: RE: [integration]Please help us on Integration Lab Hi Helen, The issue is in the building, external to the ONAP lab. See attached. Br, - Stephen From: Yunxia Chen [mailto:helen.c...@huawei.com] Sent: Monday, January 15, 2018 16:08 To: Gooch, Stephen; Raineri, Eddy; Yang, Bin Cc: onap-discuss Subject: [integration]Please help us on Integration Lab Hi, Stephen, Eddy & Bin, We cannot access Integration lab this morning, could you please help take a look? Regards, Helen Chen This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
