Let me set the stage here. I have deployed a 16GB Ubuntu 16.04 machine in openstack and logged into to it. Then I installed Rancher in Ubuntu. After that, I added Kubernetes stack in Rancher. As you can see, both Rancher & kubern8 cluster will be realized as docker containers.
After this basic installation, I then powered onap-oom by (via kubctl) ./createAll.bash -n onap , which then creates onap pods and services, that are grouped under different namespaces. However, under the hood, even onap pods are further realized as docker containers. With above premise, Are you suggesting that, I will have to find out respective docker container for the component of my interest ( say portal ) and then login via docker exec ?? BR, Viswa On Tue, Jul 4, 2017 at 2:43 PM, Elhay Efrat <[email protected]> wrote: > It’s not VMs it’s continer u need to access it via docker –it exec > continer /bin/bash > > > > *From:* [email protected] [mailto:onap-discuss-bounces@ > lists.onap.org] *On Behalf Of *Viswa KSP > *Sent:* Tuesday, July 4, 2017 11:55 AM > *To:* Roger Maitland <[email protected]> > > *Cc:* [email protected] > *Subject:* Re: [onap-discuss] [OOM] Contributing to OOM project > > > > Hi Roger, > > > > I tried exploring the seed code as per the guidelines given here : > https://wiki.onap.org/display/DW/ONAP+on+Kubernetes . I took RANCHER > approach. > > I installed Rancher + Docker + Kubectl and then powered ONAP PODs as per > the wiki. > > > > As expected, I hit permission issue while downloading images and then > resolved that with patched version of createAll.bash as per > https://jira.onap.org/browse/OOM-3 . > > > > Now most PODs stood up, but still I'm unable to get into any node or use > portal service. Judging by events logs, there is nothing alarming, but I > see now way to either get into individual components by SSH or through > portal application. > > > > Please let me know how to get inside kuben8 nodes via SSH or how to see > the status of ONAP nodes. The wiki explains the installation of rancher and > bringing up of onap-oom, but then it doesn't proceed further with opening > the portal etc. > > > > I'm a newbie here and any help is highly appreciated. > > > > Here is the get all output from my environment. > > > > *ubuntu@oom-onap*:*~*$ kubectl get service --all-namespaces=true | grep > onap > > *onap*-aai aai-service 10.43.29.56 <nodes> > 8443:30233/TCP,8080:30232/TCP > 21h > > *onap*-aai hbase None <none> > 8020/TCP > 21h > > *onap*-aai model-loader-service 10.43.104.161 <nodes> > 8443:30229/TCP,8080:30210/TCP > 21h > > *onap*-appc dbhost None <none> > 3306/TCP > 21h > > *onap*-appc dgbuilder 10.43.160.205 <nodes> > 3000:30228/TCP > 21h > > *onap*-appc sdnctldb01 None <none> > 3306/TCP > 21h > > *onap*-appc sdnctldb02 None <none> > 3306/TCP > 21h > > *onap*-appc sdnhost 10.43.0.177 <nodes> > 8282:30230/TCP,1830:30231/TCP > 21h > > *onap*-message-router dmaap 10.43.201.42 <nodes> > 3904:30227/TCP,3905:30226/TCP > 21h > > *onap*-message-router global-kafka None <none> > 9092/TCP > 21h > > *onap*-message-router zookeeper None <none> > 2181/TCP > 21h > > *onap*-mso mariadb 10.43.9.161 <nodes> > 3306:30252/TCP > 21h > > *onap*-mso mso 10.43.34.51 <nodes> > 8080:30223/TCP,3904:30225/TCP,3905:30224/TCP,9990:30222/TCP,8787:30250/TCP > 21h > > *onap*-policy brmsgw 10.43.121.44 <nodes> > 9989:30216/TCP > 21h > > *onap*-policy drools 10.43.236.89 <nodes> > 6969:30217/TCP > 21h > > *onap*-policy mariadb None <none> > 3306/TCP > 21h > > *onap*-policy nexus None <none> > 8081/TCP > 21h > > *onap*-policy pap 10.43.149.127 <nodes> > 8443:30219/TCP,9091:30218/TCP > 21h > > *onap*-policy pdp 10.43.63.44 <nodes> > 8081:30220/TCP > 21h > > *onap*-policy pypdp 10.43.204.137 <nodes> > 8480:30221/TCP > 21h > > *onap*-portal portalapps 10.43.48.144 <nodes> > 8006:30213/TCP,8010:30214/TCP,8989:30215/TCP > 21h > > *onap*-portal portaldb None <none> > 3306/TCP > 21h > > *onap*-portal vnc-portal 10.43.216.156 <nodes> > 6080:30211/TCP,5900:30212/TCP > 21h > > *onap*-robot robot 10.43.129.56 <nodes> > 88:30209/TCP > 21h > > *onap*-sdc sdc-be 10.43.5.116 <nodes> > 8443:30204/TCP,8080:30205/TCP > 21h > > *onap*-sdc sdc-cs None <none> > 9042/TCP,9160/TCP > 21h > > *onap*-sdc sdc-es None <none> > 9200/TCP,9300/TCP > 21h > > *onap*-sdc sdc-fe 10.43.41.248 <nodes> > 9443:30207/TCP,8181:30206/TCP > 21h > > *onap*-sdc sdc-kb None <none> > 5601/TCP > 21h > > *onap*-sdnc dbhost None <none> > 3306/TCP > 21h > > *onap*-sdnc sdnc-dgbuilder 10.43.240.69 <nodes> > 3000:30203/TCP > 21h > > *onap*-sdnc sdnc-portal 10.43.101.4 <nodes> > 8843:30201/TCP > 21h > > *onap*-sdnc sdnctldb01 None <none> > 3306/TCP > 21h > > *onap*-sdnc sdnctldb02 None <none> > 3306/TCP > 21h > > *onap*-sdnc sdnhost 10.43.168.248 <nodes> > 8282:30202/TCP > 21h > > *onap*-vid vid-mariadb None <none> > 3306/TCP > 21h > > *onap*-vid vid-server 10.43.198.231 <nodes> > 8080:30200/TCP > 21h > > *ubuntu@oom-onap*:*~*$ > > > > BR, > > Viswa > > > > On Tue, Jun 27, 2017 at 7:06 PM, Roger Maitland <[email protected]> > wrote: > > Hi Viswa, > > > > A preliminary version of the OOM ‘oneClick’ deployment of ONAP on > kubernetes/containers has been released in gerrit here: > https://gerrit.onap.org/r/#/admin/projects/oom > > > > This is still a work in progress as we don’t have a detailed wiki yet (but > we’re working on it) and DCAE isn’t fully supported but you’re welcome to > give it a try. > > > > Cheers, > > Roger Maitland > > [image: amdocs-a] > > *Amdocs a **Platinum member of ONAP* > <https://www.amdocs.com/open-network/nfv-powered-by-onap> > > > > *From:* [email protected] [mailto:onap-discuss-bounces@ > lists.onap.org] *On Behalf Of *Viswa KSP > *Sent:* Monday, June 26, 2017 10:36 AM > *To:* HU, JUN NICOLAS > *Cc:* [email protected] > *Subject:* Re: [onap-discuss] [OOM] Contributing to OOM project > > > > Thanks Nicolas. I'll look forward to the invite. > > BTW I'm Viswa. > > > > BR, > > Viswa > > > > On Mon, Jun 26, 2017 at 8:03 PM, HU, JUN NICOLAS <[email protected]> wrote: > > Hi BR, > > > > There is no separate mailing list in ONAP. We will set a weekly meeting > for the OOM project soon. Once the meeting is set, we will publish it on > mailing list. > > > > Thanks, > > > > Nicolas > > > > *From:* Viswa KSP [mailto:[email protected]] > *Sent:* Saturday, June 24, 2017 9:39 AM > *To:* HU, JUN NICOLAS <[email protected]> > *Cc:* [email protected] > *Subject:* [OOM] Contributing to OOM project > > > > Hi Jun Nicolas Hu, > > > > We would like to join the efforts of ONAP on Containers initiative. Could > you let me know what's the procedure to contribute OOM project. Is there a > separate mailing list for OOM project? > > > > Pls advise! > > > > BR, > > Viswa > > > > 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 [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
