[Airship-discuss] Airship-In-A-Bottle_Dev-Single-Node_No-Proxy-Environment_Mass-Ingress_Error

[Roman Gorshunov]

Almost there.
The patch [0] works and really fixes maas ingress problem. Genesis
part gets finished, and everything fails on the actual site deploy
(error message is below [1]).
But later I've run commands [2] to deploy site manually, and
everything seems to be working fine.
You then should be able to see Airflow interface and running
`deploy_site` on the IP address of the VM on port 30004: http://<IP of
VM>:30004/. Port is taken from `kubectl get services -n ucp | grep
airflow-web-int` command output.

[0] https://review.openstack.org/#/c/629950/3

[1]:
> + sudo docker run -t --rm --net=host -e http_proxy= -e https_proxy= -e no_proxy= -e OS_AUTH_URL=http://keystone.ucp.svc.cluster.local:80/v3 -e OS_USERNAME=shipyard -e OS_USER_DOMAIN_NAME=default -e OS_PASSWORD=password18 -e OS_PROJECT_DOMAIN_NAME=default -e OS_PROJECT_NAME=service quay.io/airshipit/shipyard:master create action deploy_site
> Error: Unable to complete request to Airflow
> Reason: Airflow could not be contacted properly by Shipyard.
> - Error: <class 'requests.exceptions.ConnectTimeout'>

[2]:
cd /root/deploy/site
source creds.sh
# "create configdocs design", "create configdocs secrets", "commit
configdocs" have succeeded previously via "./airship-in-a-bottle.sh
-y" script; only deploy_site` dropped an error
./run_shipyard.sh create action deploy_site

-- Roman Gorshunov

On Fri, Mar 8, 2019 at 4:28 PM Roman Gorshunov <paye600 at gmail.com> wrote:
>
> Hello team,
> I'm working on getting maas-ingress working again. This patch set [0]
> I believe solves this specific problem when applied onto a current
> master [1]. Try to apply it from inside of cloned airship-in-a-bottle
> repository by running commands under Download -> Checkout menu in the
> right corner [2]. For me it passes trough maas initialization and helm
> tests.
>
> [0] https://review.openstack.org/#/c/629950/
> [1] 539f777c637ffd1927659469072ec6235188b247
> [2] git fetch https://git.openstack.org/openstack/airship-in-a-bottle
> refs/changes/50/629950/3 && git checkout FETCH_HEAD
>
> -- Roman Gorshunov
>
> On Thu, Mar 7, 2019 at 10:17 AM Loic Le Gal <l.legal.astellia at gmail.com> wrote:
> >
> > Thanks Matt for the feedback,
> >
> > I'd like to help as I can but as I'm noob to Airship it won't be easy at the beginning.
> > My aim (as many of firstcomers) is to try to get a functionning Airship demo with k8s & Openstack setup + a little VM on top (clearwater later :-)); all this installed on a big VM : That's AiaB!
> > Regarding Airskiff, I've already tryied it but as it is not AIO and require setting-up and plugging all layers together, it might not be the easiest staring point IMHO.
> > BTW, i'm close to have a Heat template to automate the building of such a AiaB VM (and with proxy management), this will ease future tests while waiting the Treasuremap's story you mentionned.
> >
> > Have you got a commit ID that is secured (like a stable one)? even if we don't have latest features/fixes.
> >
> > BR,
> >
> > Loïc
> >
> > Le mer. 6 mars 2019 à 22:16, MCEUEN, MATT <MM9745 at att.com> a écrit :
> >>
> >> Hi Loïc & Dimitrios,
> >>
> >>
> >>
> >> Shoot, sorry you guys hit this.  This looks like the Airship-in-a-Bottle single node dev site may have gotten stale.  We have a few different sets of YAMLs that should be aligned to one another to keep this from happening; I’ve captured the issue and proposed resolution in this story[1].  If you’d like to help with this it would be very much appreciated :-), and if anyone has some time to get the AiaB single-node dev site definition trued up in the meantime that would be valuable too.
> >>
> >>
> >>
> >> For a MaaS-free dev deployment, I suggest looking at the Airskiff [2] deployment scripts.  These deploy the software provisioning components (no MaaS, Drydock, Promenade) in a bring-your-own-k8s setup.  Dwalt has a patchset in progress to align these site manifests fully to the treasuremap reference globals, per the story.
> >>
> >>
> >>
> >> [1]: https://storyboard.openstack.org/#!/story/2005123
> >>
> >> [2]: https://airship-treasuremap.readthedocs.io/en/latest/airskiff.html
> >>
> >>
> >>
> >> Thanks,
> >>
> >> Matt
> >>
> >>
> >>
> >> From: Loic Le Gal <l.legal.astellia at gmail.com>
> >> Sent: Wednesday, March 6, 2019 9:49 AM
> >> To: airship-discuss at lists.airshipit.org
> >> Subject: Re: [Airship-discuss] Airship-In-A-Bottle_Dev-Single-Node_No-Proxy-Environment_Mass-Ingress_Error
> >>
> >>
> >>
> >> Hi Airshipers,
> >>
> >>
> >>
> >> Same issue for me, going back to previous commit (ad53fbf5c312929e8d0873e5095c5a0d1dcdd7f5), but another problem arise with maas-import-resources. I will open new thread if can't fix.
> >>
> >> Why is maas required even for AiaB as we don't have any baremetal involved ??
> >>
> >>
> >>
> >> BR,
> >>
> >>
> >>
> >> Loïc
> >
> > _______________________________________________
> > Airship-discuss mailing list
> > Airship-discuss at lists.airshipit.org
> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss