[TripleO][Rdo][Train] Deploy OpenStack using only provisioning network
Ruslanas Gžibovskis
ruslanas at lpic.lt
Tue May 12 10:42:38 UTC 2020
Thank you Luke and Harald.
I was following your recommendations and links, and I have managed to do
these modifications to the setup shared by Harald, to adjust to my needs.
https://github.com/qw3r3wq/homelab Have done clone, and have updated my
changes.
I have 2 main issues now:
1) when deploying overcloud, it do not add ssh key to authorized host, and
gets timeout, but I can work with that.
1.solution) while running installation I ssh into it, before ansible
tries... shitty workaround, but should be ok for POC, need to fix it also.
*2) As you see from config files, I use local undercloud as repo for
container images, but it is not able to fetch data from there, as it is
marked as secure, but undercloud configures it as unsecure. Can I somehow
specify to installed, so it would modify
/etc/container(s)/repositories.conf to add undercloud IP and url to
insecure repo list. cause it helps tp fix my issues. but then cannot
proceed as it has part of things up, so I need to do fresh setup, which is
without insecure repos.*
*2.solution) no ideas.*
3) Problem: when setting up undercloud with proxy variables exported, it
adds them into containers, but even I have no_prpoxy which has idrac IP
specified, or range, ironic-conductor sends request to redfish using
proxy...
3.solution) I think solution would be to use undercloud repo
(predownload images) and make undercloud install from it, but when I even
add 'insecure' repos value to $local_ip it drops error [1] trying to
connect to repo....docker.io
Any thoughts?
[1]
Retrying (Retry(total=7, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at
0x7fed502f9e10>: Failed to establish a new connection: [Errno 111]
Connection refused',)': /v2
...
raise ConnectionError(e, request=request)
ConnectionError: HTTPSConnectionPool(host='registries-1.docker.io',
port=443): Max retries exceeded with url: /v2/ (Caused by
NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at
0x7fed50253bd0>: Failed to establish a new connection: [Errno 111]
Connection refused',))
On Tue, 5 May 2020 at 20:17, Harald Jensås <hjensas at redhat.com> wrote:
> On Mon, 2020-05-04 at 00:20 +0200, Ruslanas Gžibovskis wrote:
> > Hi all,
> >
> > I am doing some testing and will do some deployment on some remote
> > hosts.
> >
> > Remote hosts will use provider network only specific for each
> > compute.
> >
> > I was thinking, do I really need all the External, InternalAPI,
> > Storage, StorageManagemnt, Tenant networks provided to all of the
> > nodes? Maybe I could use a Provision network for all of that, and
> > make swift/glance copy on all computes to provide local images.
> >
> > I understand, if I do not have tenant network, all VM's in same
> > project but in different sites, will not see each other, but it is ok
> > at the moment.
> >
> > Thank you for your help
> >
>
> I use tripleo to deploy a single node aio with only 1 network interface
> as a lab at home. You can see the configuration here:
>
> https://github.com/hjensas/homelab/tree/master/overcloud
>
> Basically I use a an empty network data file, and removed
> the 'networks' section in my custom role data file.
>
> With no networks defined everything is placed on the 'ctlplane' (i.e
> provisioning network). Same thing you are asking for?
>
>
> I think you can do the same thing. For the provider networks I believe
> you will need per-role NeutronBridgeMappings i.e something like:
>
> ControllerParameters:
> NeutronBridgeMappings: br-ex:provider0
> ComputeSite1:
> NeutronBridgeMappings: br-foo:provider1
> ComputeSite2:
> NeutronBridgeMappings: br-bar:provider2
>
>
> --
> Harald
>
>
>
--
Ruslanas Gžibovskis
+370 6030 7030
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200512/366c7dfa/attachment-0001.html>
More information about the openstack-discuss
mailing list