Hi,
I am stuck at a point.
I ran the cd.sh script and it created all the pods accordingly and all are
running fine (10 of them are stuck at pending state till the end).
All the Portal related pods are running well, there are no errors in that.
But according to the link:
*https://wiki.onap.org/display/DW/Tutorial%3A+Accessing+the+ONAP+Portal
<https://wiki.onap.org/display/DW/Tutorial%3A+Accessing+the+ONAP+Portal>*,
I need to have 4 different nodes (for sdc, policy, portal and vid) and the
IPs of these nodes are to be included in /etc/hosts file, so that I can
access the ONAP Portal.
Since, cd.sh did not create any node (it created just pods), what do I have
to do next to access portal?
Please help. I have no clue what to do now.
Thanks and Regards
Ankit
On Fri, Mar 2, 2018 at 1:59 AM, Michael O'Brien <frank.obr...@amdocs.com>
wrote:
> Ankit,
>
>The WIP entrypoint script is attached to the jira – I just tested it on
> the latest master on a clean VM – it will automatically install Rancher 1.6
> and OOM.
>
>A single namespace patch just went in 2 hours ago – so pods are coming
> up slower than normal (51 failures@20m (clean) and 21 failures@20 min
> (upgrade) on 2 separate VMs) – we should know the state of master shortly –
> may be a slower nexus3 issue (the wiki was down for a bit yesterday).
>
>
>
>The cd.sh script has a removal/deletion section for all pods and the
> config container – before it reclones OOM and creates all the pods – you
> will see errors deleting pods – if you run cd.sh on a clean system (not
> doing an upgrade) – you can ignore these.
>
>
>
>Troubleshooting:
>
>If you are stuck waiting for the config pod over 11 min (usually 3) –
> then your onap-parameters.yaml file is not correct – check the logs on the
> config container to see what variables are missing – remember
> onap-parameters.yaml is different for master and amsterdam – the line in
> the script is waiting for a “0/1 completed”
>
> https://git.onap.org/oom/tree/kubernetes/config/onap-
> parameters.yaml?h=amsterdam
>
>
>
> https://jira.onap.org/browse/OOM-710
>
> If you run the following example entrypoint.sh – it will wget everything
> required including a fake master version of onap-parameters.yaml (VNF
> creation or keystone login will not work unless you swap out your own for
> example)
>
> https://jira.onap.org/secure/attachment/11206/oom_entrypoint.sh
>
>
>
> Also make sure you are getting all the scripts either from the attached
> versions or the gerrit reviews themselves – as they are still under review
> and not committed to master yet.
>
> https://jira.onap.org/browse/OOM-716
>
>
>
>
>
> /michael
>
>
>
> *From:* ANKIT ROHILLA [mailto:ankit.rohill...@gmail.com]
> *Sent:* Thursday, March 1, 2018 02:57
> *To:* Michael O'Brien <frank.obr...@amdocs.com>
>
> *Subject:* Re: [onap-discuss] Regarding Full ONAP installation
>
>
>
> Hi,
>
> I followed the above steps but when I run "./cd.sh -b master" it gives
> multiple errors similar to the following error:
>
> Error: configmaps is forbidden: User
> "system:serviceaccount:kube-system:default"
> cannot list configmaps in the namespace "kube-system"
> Error from server (NotFound): namespaces "onap-mso" not found
> Error from server (NotFound): clusterrolebindings.rbac.
> authorization.k8s.io "onap-mso-admin-binding" not found
> Service account onap-mso-admin-binding deleted.
>
> I checked and found that all the folders like mso, aaf etc. are present in
> /oom/kubernetes/.
>
> After many errors similar to the above one, it loops on "waiting for
> config pod to complete. No resources found."
>
>
> Please help. What am I missing?
>
> Thank you
>
>
>
> On Tue, Feb 27, 2018 at 10:19 PM, ANKIT ROHILLA <ankit.rohill...@gmail.com>
> wrote:
>
> Thank you so much for the above procedure. I'll try it and let you know if
> any problem is encountered.
>
>
>
> Regards
>
> Ankit Rohilla
>
>
>
> On Feb 27, 2018 10:15 PM, "Michael O'Brien" <frank.obr...@amdocs.com>
> wrote:
>
> Ankit,
>
>Hi, the help page has been adjusted so that the automated scripts can
> be run while they are being reviewed (not in the OOM repo yet). The goal
> of OOM-710 is a one-click HEAT/ARM/CloudFormation template that runs
> oom_rancher_install.sh and cd.sh in sequence – this is being worked on –
> avoiding any manual DevOps
>
>
>
> https://jira.onap.org/browse/OOM-710
>
>
>
>As of today the rancher RI installation for Kubernetes, Helm, Docker is
> fully automated to run on Ubuntu 16.04 VM on any cloud provider belo
