<div dir="ltr">Ah-HA! OK, those are the dashboards I'm talking about. I will do that, thank you so much!<div><br></div><div>And then yes, I will back things down and see what's really required. :)<br><div><br></div><div>---- Nick</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 6, 2019 at 2:51 PM Roman Gorshunov <<a href="mailto:paye600@gmail.com">paye600@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Nick,<br>
Airship doesn't really have any dashboards at all. It is only planned<br>
that Airship 2.0 could have a GUI.<br>
What you might want to look at are MaaS dashboard and Airflow GUI.<br>
Since those dashboards changed their names, I didn't yet released a<br>
patch to get them published at the end of AIAB script run. There is an<br>
incomplete patch set from me available here:<br>
<a href="https://review.opendev.org/#/c/632457" rel="noreferrer" target="_blank">https://review.opendev.org/#/c/632457</a>.<br>
Check the commands in scrips which expose services as NodePort like<br>
`kubectl -n xxxx expose service/xxxx --type=NodePort --name=xxxxx`,<br>
modify them to your needs, and try to get to the dashboards.<br>
I hope it helps.<br>
<br>
Best regards,<br>
--<br>
Roman Gorshunov<br>
<br>
On Fri, Sep 6, 2019 at 8:41 PM Nick Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>> wrote:<br>
><br>
> Actually I'm not sure which messages have gotten through, but even with the larger machine, there are still issues. Horizon works, and the sample VM is deployed, but the Airship dashboards are not working.<br>
><br>
> ---- Nick<br>
><br>
> On Fri, Sep 6, 2019 at 1:03 PM அருண் குமார் (Arun Kumar) <<a href="mailto:thangam.arunx@gmail.com" target="_blank">thangam.arunx@gmail.com</a>> wrote:<br>
>><br>
>> Hi Nick,<br>
>><br>
>> Are you able to downgrade the VM spec and retest?<br>
>><br>
>> I was trying AIAB multiple times with same minimal VM requirements but it was failing and crashlooping for postgresql and Mariadb.<br>
>><br>
>> After seeing your update was surprised and see if you can bring down system requirements for Testing purpose.<br>
>><br>
>> Thanks<br>
>> Arun<br>
>><br>
>><br>
>><br>
>> வியா., 29 ஆக., 2019, AM 1:26க்கு, Nick Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>> எழுதியது:<br>
>>><br>
>>> Will do. I'm seeing how low I can go and have it still work. Thanks!<br>
>>><br>
>>> ---- Nick<br>
>>><br>
>>> On Wed, Aug 28, 2019 at 11:43 AM SKELS, KASPARS <<a href="mailto:ks3019@att.com" target="_blank">ks3019@att.com</a>> wrote:<br>
>>>><br>
>>>> Hi Nick, this is great to hear!<br>
>>>><br>
>>>><br>
>>>><br>
>>>> I would suggest to add documentation patchset to the AIAB readme to state minimal requirements for GCU in the AIAB!<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Kindly, Kaspars<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> From: Nick Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>><br>
>>>> Sent: Wednesday, August 28, 2019 7:34 AM<br>
>>>> To: Roman Gorshunov <<a href="mailto:paye600@gmail.com" target="_blank">paye600@gmail.com</a>><br>
>>>> Cc: <a href="mailto:airship-discuss@lists.airshipit.org" target="_blank">airship-discuss@lists.airshipit.org</a><br>
>>>> Subject: Re: [Airship-discuss] AIAB and default backend - 404<br>
>>>><br>
>>>><br>
>>>><br>
>>>> I found the problem. First off, I was citing the wrong repo. I actually was coming from <a href="https://opendev.org/airship/treasuremap/" rel="noreferrer" target="_blank">https://opendev.org/airship/treasuremap/</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> Second, apparently the requirements cited for the machine are too small. The README says 4vCPU/20GB RAM/32GB but with that I was in a periodic crashloop for Postgres. GCE was suggesting I increase the machine to 8vCPU/48GB RAM. Ultimately I'm at 16vCPU/60GB RAM and about 32GB of drive space is used.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> With the bigger machine, everything deployed properly and seems to be running smoothly.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> ---- Nick<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Tue, Aug 27, 2019 at 9:56 AM Nick Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>> wrote:<br>
>>>><br>
>>>> OK, I feel ridiculous saying this, but I can't find the Ingress. I get plenty of output from<br>
>>>><br>
>>>><br>
>>>><br>
>>>> kubectl get --all-namespaces ing<br>
>>>><br>
>>>><br>
>>>><br>
>>>> but "no resources" from<br>
>>>><br>
>>>><br>
>>>><br>
>>>> kubectl get ing<br>
>>>><br>
>>>><br>
>>>><br>
>>>> ---- Nick<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Tue, Aug 27, 2019 at 9:51 AM Nick Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>> wrote:<br>
>>>><br>
>>>> I ran the airship-in-a-bottle.sh script from <a href="https://opendev.org/airship/airship-in-a-bottle" rel="noreferrer" target="_blank">https://opendev.org/airship/airship-in-a-bottle</a>. Is there another preferred way? I can try the Vagrantfile.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> I'll check out the logs.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> ---- Nick<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov <<a href="mailto:paye600@gmail.com" target="_blank">paye600@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Hi Nick,<br>
>>>><br>
>>>> Which script did you run and from which repo?<br>
>>>> I would start with checking logs and config of running ingress.<br>
>>>><br>
>>>> Best regards,<br>
>>>> —<br>
>>>> Roman Gorshunov<br>
>>>><br>
>>>><br>
>>>> > On 26 Aug 2019, at 22:40, Nick Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>> wrote:<br>
>>>> ><br>
>>>> > I'm pleased to say that I've successfully run the script to install Airship in a Bottle -- or at least I think I did. When I try to access most of the endpoints, I get<br>
>>>> ><br>
>>>> > default backend - 404<br>
>>>> ><br>
>>>> > Except for the Horizon endpoint, where I get nothing at all.<br>
>>>> ><br>
>>>> > I'm assuming this is a K8s issue, but I'm not sure where to look further.<br>
>>>> ><br>
>>>> > Any ideas?<br>
>>>> ><br>
>>>> > ---- Nick<br>
>>>> > _______________________________________________<br>
>>>> > Airship-discuss mailing list<br>
>>>> > <a href="mailto:Airship-discuss@lists.airshipit.org" target="_blank">Airship-discuss@lists.airshipit.org</a><br>
>>>> > <a href="http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss" rel="noreferrer" target="_blank">http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Airship-discuss mailing list<br>
>>>> <a href="mailto:Airship-discuss@lists.airshipit.org" target="_blank">Airship-discuss@lists.airshipit.org</a><br>
>>>> <a href="http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss" rel="noreferrer" target="_blank">http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Airship-discuss mailing list<br>
>>> <a href="mailto:Airship-discuss@lists.airshipit.org" target="_blank">Airship-discuss@lists.airshipit.org</a><br>
>>> <a href="http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss" rel="noreferrer" target="_blank">http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss</a><br>
</blockquote></div>