The rubicon-issues from cci-moc

No Connection to the nodes

Schedule session about Assisted Installer and Power9 with Nir

Session about the Power9 installation.

Create a Slack channel for our collaboration with IBM on the 'Operate First' workspace

And invite the members of the group to channel.

Provision the first Node 10.0.21.7 with RHCOS/RHEL OS

investigate how the DHCP works on the Foremen

while we were trying to install RHCOS on the node using the Foreman server we saw that the node is reaching out to the Foreman on port 67 making a DHCP request but not receiving an answer.

Get the ISO file for RHEL/RHCOS that suits the ppc architecture

Hey @idanlv we don't have subscription to download the ISO file for RHEL/RHCOS for the IBM power servers architecture.
As a red hatter can you help me the right subscription ? Because my only option right now is to purchase this subscription.

Download the openshift-installer

Downloaded the openshift-installer for the ppc64le architecture.

Get updated firmware images for the BMC + the server itself

Configure the DNS entries

add entries for opeshift installation and general work:

worker, master, *.apps, *.api etc. by the documentation
configure all under the domain moc-ocp.com

Create RHCOS machines

Working on creating the RHCOS machines with the ignition files. encountered some issues with the installation, working on it.

Create an automation for the DNS

Assisted installer attempt

Trying to deploy openshift cluster using the assisted installer. Working with Nir on this.

Configure DNS entries for opeshift installation

Check why Foreman DHCP isn't working as should.

Foreman server is not providing DHCP for the clients machines, therefore no provision is possible until issue addressed.

create a DNS on the "Foreman" server

DOD:

DNS runs on a container
All nodes can access and get service from the sever
Create a documentation and automation for it

Create a direct connection to the bootstrap and masters

Create a DNS

Create a private registry on the foreman server

Managed to create and configure a private registry on the foreman server
https://github.com/CCI-MOC/rubicon-issues/wiki/Full-procedure-for-creating-a-registry

AIO OCP4 Deployment

This issue shows the progress of our main objective - Deploying OpenShift 4

Recover from Hardware failure

As part of power9 project,
original issue:
#33

Recovering from a power outage

Nics , IPs,...

Deploy an application to "Alex Cluster"

As part of the HTB program

Reference:
open-infrastructure-labs/ops-issues#41

Foreman Server is down.

@naved001 , please power on the machine.
Regards.

BMC servers are unreachable

Hey @naved001,
Trying to ssh to the 10.0.21.5 and 10.0.21.6 servers but can't reach them. cant open the BMC web interface of these servers as well.
Haven't done anything unusual on those servers.
10.0.21.7 is working fine.
Can you take a look, please?

Questions about the architecture of the OCP installation

hey @naved001, As we discussed in the meeting here are the questions we have:

Where does all of the network configuration taking place ? We need access to the DHCP/DNS server or we need someone whos got access, who will set up the ip addresses to the nodes ?
CPU architecture - is it x86_64 ? If not what is the architecture?
Network interface must be at least 1-GB for the routable baremetal network do we have it ?
UEFI - We need it to be boot on, how and who will configure it ?
According to the installation process we are using link here we need 2 networks, one baremetal network that is connected to the internet, and provisioning network. How can we reach this configuration from our current status.

Update the article about Rubicon/Redhat partnership

Noy and Idan did the first inspection of Yonatan's article, we are planning to have a second option on it by Katka.
Will need to add/change the article according to Katka's feedback.

Password request for root user on both BMC & foreman servers.

Also for hil user on BMC server.

HDD issues on node 7

Hi @naved001,
we are encountering some HDD issues on node7, seems something we messed up during our previous provisions.
The error we get is

As shown here all the devices have the same UUID but there is nothing about /dev/sda1 or /dev/sdb1:

Is there any option from your side to format the node and get the disk back to its original state or maybe we miss an easy solution without formatting the whole node storage?

Install & Configure a foreman server on the foreman

No route to host when trying to access bu-21-6 BMC web interface

Network & Forman information

Manage Security Policy via ACM on Alex cluster

As part of the HTB for ACM, task number 10.

Create a security policy that checks for a specific resource and inform on its presence. Create a remediation policy to take action when a violation is detected and correct/mitigate it.