On Fri, 31 Jan 2020 at 06:06, Tony Pearce <tony.pearce@cinglevue.com> wrote:
Thanks again Mark for your support and patience yesterday. I dont think I would have been able to go beyond that hurdle alone.
I have gone back to the universe from nothing this morning. The issue I had there was actually the same issue that you had helped me with; so I have now moved past that point. I am running this in a VM and I did not have nested virtualisation enabled on the hosts so I've had to side step to get that implemented. I am sticking with the stable/train. I was not sure about this, but I had figured that as I want to deploy Openstack Train, I'd need the Kayobe stable/train.
That's correct - use stable/train for kayobe, kayobe-config and a-universe-from-nothing to deploy Train.
In terms of the docs - I may be in a good position to help here. I'm not a coder by any means, so I may be in a position to contribute back in this doc sense.
That would be a great help. These first experiences with a project's documentation are always valuable when determining where the gaps are. Get in touch if you need help with the tooling.
Teething issues aside, I really like what I am seeing from Kayobe etc. compared to my previous experience with different deployment tool this seems much more user-friendly.
Glad to hear it :)
Thanks again
Regards
Tony
On Thu, 30 Jan 2020 at 21:40, Mark Goddard <mark@stackhpc.com> wrote:
On Thu, 30 Jan 2020 at 08:22, Tony Pearce <tony.pearce@cinglevue.com> wrote:
Hi all - I wanted to ask if there was such a reference architecture / step-by-step deployment guide for Openstack / Kayobe that I could follow to get a better understanding of the components and how to go about deploying it?
Hi Tony, we spoke in the #openstack-kolla IRC channel [1], but I thought I'd reply here for the benefit of anyone reading this.
The documentation is not that great so I'm hitting various issues when trying to follow what is there on the Openstack site. There's a lot of technical things like information on variables - which is fantastic, but there's no context about them. For example, the architecture page is pretty small, when you get further on in the guide it's difficult to contextually link detail back to the architecture.
As discussed in IRC, we are missing some architecture and from scratch walkthrough documentation in Kayobe. I've been focusing on the configuration reference mostly, but I think it is time to move onto these other areas to help new starters.
I tried to do the all-in-one deployment as well as the "universe from nothing approach" but hit some issues there as well. Plus it's kind of like trying to learn how to drive a bus by riding a micro-scooter :)
I would definitely recommend persevering with the universe from nothing demo [2], as it offers the quickest way to get a system up and running that you can poke at. It's also a fairly good example of a 'bare minimum' configuration. Could you share the issues you had with it? For an even simpler setup, you could try [3], which gets you an all-in-one control plane/compute host quite quickly. I'd suggest using the stable/train branch for a more stable environment.
Also, the "report bug" bug link on the top of all the pages is going to an error "page does not exist" - not sure that had been realised yet.
Andreas Jaeger kindly proposed a fix for this. Here's the storyboard link: https://storyboard.openstack.org/#!/project/openstack/kayobe.
[1] http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla... [2] https://github.com/stackhpc/a-universe-from-nothing [3] https://docs.openstack.org/kayobe/latest/development/automated.html#overclou...
Regards,
Tony Pearce | Senior Network Engineer / Infrastructure Lead Cinglevue International
Email: tony.pearce@cinglevue.com Web: http://www.cinglevue.com
Australia 1 Walsh Loop, Joondalup, WA 6027 Australia.
Direct: +61 8 6202 0036 | Main: +61 8 6202 0024
Note: This email and all attachments are the sole property of Cinglevue International Pty Ltd. (or any of its subsidiary entities), and the information contained herein must be considered confidential, unless specified otherwise. If you are not the intended recipient, you must not use or forward the information contained in these documents. If you have received this message in error, please delete the email and notify the sender.