[Airship-discuss] AIAB and default backend - 404

Nick Chase nchase at mirantis.com
Fri Sep 6 18:41:52 UTC 2019


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.

----  Nick

On Fri, Sep 6, 2019 at 1:03 PM அருண் குமார் (Arun Kumar) <
thangam.arunx at gmail.com> wrote:

> Hi Nick,
>
> Are you able to downgrade the VM spec and retest?
>
> I was trying AIAB multiple times with same minimal VM requirements but it
> was failing and crashlooping for postgresql and Mariadb.
>
> After seeing your update was surprised and see if you can bring down
> system requirements for Testing purpose.
>
> Thanks
> Arun
>
>
>
> வியா., 29 ஆக., 2019, AM 1:26க்கு, Nick Chase <nchase at mirantis.com>
> எழுதியது:
>
>> Will do.  I'm seeing how low I can go and have it still work.  Thanks!
>>
>> ----  Nick
>>
>> On Wed, Aug 28, 2019 at 11:43 AM SKELS, KASPARS <ks3019 at att.com> wrote:
>>
>>> Hi Nick, this is great to hear!
>>>
>>>
>>>
>>> I would suggest to add documentation patchset to the AIAB readme to
>>> state minimal requirements for GCU in the AIAB!
>>>
>>>
>>>
>>> Kindly, Kaspars
>>>
>>>
>>>
>>>
>>>
>>> *From:* Nick Chase <nchase at mirantis.com>
>>> *Sent:* Wednesday, August 28, 2019 7:34 AM
>>> *To:* Roman Gorshunov <paye600 at gmail.com>
>>> *Cc:* airship-discuss at lists.airshipit.org
>>> *Subject:* Re: [Airship-discuss] AIAB and default backend - 404
>>>
>>>
>>>
>>> I found the problem.  First off, I was citing the wrong repo.  I
>>> actually was coming from https:*//opendev.org/airship/treasuremap/*
>>> <https://opendev.org/airship/treasuremap/>
>>>
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>> With the bigger machine, everything deployed properly and seems to be
>>> running smoothly.
>>>
>>>
>>>
>>> ----  Nick
>>>
>>>
>>>
>>> On Tue, Aug 27, 2019 at 9:56 AM Nick Chase <nchase at mirantis.com> wrote:
>>>
>>> OK, I feel ridiculous saying this, but I can't find the Ingress.  I get
>>> plenty of output from
>>>
>>>
>>>
>>> kubectl get --all-namespaces ing
>>>
>>>
>>>
>>> but "no resources" from
>>>
>>>
>>>
>>> kubectl get ing
>>>
>>>
>>>
>>> ----  Nick
>>>
>>>
>>>
>>> On Tue, Aug 27, 2019 at 9:51 AM Nick Chase <nchase at mirantis.com> wrote:
>>>
>>> I ran the airship-in-a-bottle.sh script from
>>> https://opendev.org/airship/airship-in-a-bottle
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__opendev.org_airship_airship-2Din-2Da-2Dbottle&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=L2WcX1Ge33cpIHXX6krAgw&m=3iLHLL1xBKOa3p0WqZPxJtQzj_sXlniVDTkYF2WYyyw&s=B9IEUmHn0lOPWsuzlYf_C8icUyPCG_6ka0WhZ8Xtgv8&e=>.
>>> Is there another preferred way?  I can try the Vagrantfile.
>>>
>>>
>>>
>>> I'll check out the logs.
>>>
>>>
>>>
>>> ----  Nick
>>>
>>>
>>>
>>> On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov <paye600 at gmail.com>
>>> wrote:
>>>
>>> Hi Nick,
>>>
>>> Which script did you run and from which repo?
>>> I would start with checking logs and config of running ingress.
>>>
>>> Best regards,
>>>>>> Roman Gorshunov
>>>
>>>
>>> > On 26 Aug 2019, at 22:40, Nick Chase <nchase at mirantis.com> wrote:
>>> >
>>> > 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
>>> >
>>> > default backend - 404
>>> >
>>> > Except for the Horizon endpoint, where I get nothing at all.
>>> >
>>> > I'm assuming this is a K8s issue, but I'm not sure where to look
>>> further.
>>> >
>>> > Any ideas?
>>> >
>>> > ----  Nick
>>> > _______________________________________________
>>> > Airship-discuss mailing list
>>> > Airship-discuss at lists.airshipit.org
>>> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=L2WcX1Ge33cpIHXX6krAgw&m=3iLHLL1xBKOa3p0WqZPxJtQzj_sXlniVDTkYF2WYyyw&s=aon5Br-LF49E22qMJbgQZPPz1oLX_rjE0o5BvSYVMkM&e=>
>>>
>>>
>>> _______________________________________________
>>> Airship-discuss mailing list
>>> Airship-discuss at lists.airshipit.org
>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=L2WcX1Ge33cpIHXX6krAgw&m=3iLHLL1xBKOa3p0WqZPxJtQzj_sXlniVDTkYF2WYyyw&s=aon5Br-LF49E22qMJbgQZPPz1oLX_rjE0o5BvSYVMkM&e=>
>>>
>>> _______________________________________________
>> Airship-discuss mailing list
>> Airship-discuss at lists.airshipit.org
>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20190906/bd578802/attachment.html>


More information about the Airship-discuss mailing list