Conversation

Notices

1. musicman (musicman@nu.federati.net)'s status on Thursday, 05-Nov-2020 17:50:09 EST musicman
   creating manifests erases the install-config.yaml. Is it supposed to? Idk. #openshift is a clusterfuck
   1. musicman (musicman@nu.federati.net)'s status on Thursday, 05-Nov-2020 17:58:25 EST musicman

      in reply to
      most (all) of that stiff is in cluster-config.yaml, which is in the manifests directory.
      
      I think https://nu.federati.net/url/277544
      
      but, tomorrow, mostly...
   2. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Thursday, 05-Nov-2020 19:34:36 EST lnxw48a1

      in reply to
      I've head that #OpenShift is the bee's knees, but they do not seem to be the same thing and the same software stack as they were when OS was first announced. I used to get the monthly newsletter, but after they changed, the newsletter is sort of ho hum to me.
      1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Thursday, 05-Nov-2020 19:57:02 EST lnxw48a1

         in reply to
         *heard*
      2. musicman (musicman@nu.federati.net)'s status on Friday, 06-Nov-2020 08:55:41 EST musicman

         in reply to
         I think it may well be amazing if you can actually get it installed. The (major?) problem is I don't have appropriate network access for our AWS or our ovirt. You would think since ovirt is a Red Hat project they could get it to work, and again, maybe it does, but I don't have any visibility into the network right now to see where things are actually failing.
         
         If I can get the ovirt agent to install via the yaml, then perhaps I will have some insight into what is going on.