Monday, 2021-07-19

TreerSam, you're going to have to tell me about this new gf00:08
Treergregarka, this channel is closed. You are going to have to leave.00:08
TreerSam, have you met her in person yet00:09
TreerPlease tell me about it00:09
TreerThis channel closed at 5pm CST weekends.00:09
TreerThis channel is closed. You are going to have to leave.02:15
-opendevstatus- NOTICE: The maintenance of the Gerrit service is now complete and service has been restored. Please alert us in #opendev if you have any issues. Thank you03:25
*** rpittau|afk is now known as rpittau09:31
*** marlinc is now known as Guest138110:40
*** sshnaidm|afk is now known as sshnaidm13:10
*** Dalton is now known as Guest139514:34
Guest1395Hello, I dont know if this chat is the right place to ask questions regarding installation problems... But I am trying to install Keystone on Ubuntu 20.04, without success... I had a problem and decided to start the installation again. So, I unninstalled the Keystone (apt remove keystone) and removed the /etc/keystone folder... Now, when I install the keystone again (apt install keystone), there is no /etc/keystone folder... 14:38
Guest1395I think the folder should be created during the installation. Am I wrong?14:38
Guest1395If this is not the right place to ask, please indicate me some appropriate communication channel (forum, email, etc.)14:39
jrosserGuest1395: a lot of deployments will use some automation tool to install everything, so there might not be specific answers for that15:12
Guest1395@jrosser, I am using this installation guide, without automation tool:
Guest1395Some minutes ago I made the same test in another machine with Ubuntu 18.04. The /etc/keystone folder existed and had just one file "fernet-keys". I installed Keystone and the folder now had more files. Then, I removed the folder, removed and reinstalled keystone. In the end, the folder /etc/keystone was created, but is empty. I think there is some problem regarding the installation process of keystone in Ubuntu.15:17
jrosserok well like i say most people are probably not following that guide and all these complexities are handled by installers of various kinds15:17
jrosseryou could take a look at how openstack-ansible, kolla, tripleo, canonical charmed openstack, microstack, debian osbpo..... these things all exist becasue installing by hand is really really hard15:22
Guest1395I already played with Microstack, very limited and unstable... I would like to install the components with two machines: one for controller and another for compute (like the tutorial suggests)15:26
Guest1395I was taking a look at some of these automation tools, but it seemed to me that all of them requires more machines and hardware resources...15:27
jrosserwell it depends, for full H/A certainly15:27
jrosserbut for smaller deployments one or two nodes is possible with several of those tools15:28
jrosserjust as an example here is a one node deployment of openstack-ansible
jrosserthe others may have similar15:29
Guest1395I will try the AIO and sees if I succeed installing it in two machines (because I want to separate the compute and later make some tests with VMs sharing GPU). Thanks, @jrosser15:34
jrosserwell, just read carefully becasue the AIO is a special setup where everything is NAT behind one interface, so may not be what you want15:34
jrosserbut it is pretty much guaranteed to work and be a reference for the thing you really want15:35
*** rlandy is now known as rlandy|rover15:52
*** rpittau is now known as rpittau|afk17:38
*** rlandy|rover is now known as rlandy|rvr|biab18:03
*** rlandy|rvr|biab is now known as rlandy|rover19:39
*** gilou_ is now known as Gilou19:42
*** marlinc is now known as Guest143423:06

Generated by 2.17.2 by Marius Gedminas - find it at!