# FFU hackfest

> 22/June/2020 - Meeting:

~~~
Link to deck we're presenting: https://docs.google.com/presentation/d/1f2yzDVAhI6TJu3yq-XIbsohky3GLGdyhTEwyW3NRLWk/edit?usp=sharing

Trello board: https://trello.com/b/KLGRFQZZ/osp-161-upgrade-hackfest

OSP 16.1 Upgrade HF https://chat.google.com/u/1/room/AAAAey4OOaE

https://docs.google.com/presentation/d/1f2yzDVAhI6TJu3yq-XIbsohky3GLGdyhTEwyW3NRLWk/edit#slide=id.g87f0384620_0_132

https://bluejeans.com/playback/s/b8MzfAahfS2XHnwLQrerxTOoPrwXchy0rjjYR61a6DcBV9TcS61QfELkfKKAvgTn
~~~

offline mtg:

1) upgrade with vGPU -- pending
2) hci -- deploy in progress
3) ceph+nfs -- shatdru will integrate nfs
4) instance HA -- https://docs.google.com/document/d/18i8b234csojC78DTA7RNoJRQAD7437oNNCDSnhKHm34/edit

5) IR http://pastebin.test.redhat.com/879234

29-06-2020

1) 12:30 to 13:30 - Intro and scenario picking
2) [Leap introduction](https://docs.google.com/presentation/d/1Wqeo2harHgmIsjCOT4snJqQJI9BmSXCwJzhlLn39SO8/edit#slide=id.g8a4a478daf_0_175)

* LEAPP currently requires RHEL-ALT 7.6/RHEL 7.8 as a source version
* Although unsupported, it's possible to upgrade from other minor versions, for example RHEL 7.6 or 7.7
* [Supported in-place upgrade paths for Red Hat Enterprise Linux](https://access.redhat.com/articles/4263361)

*** Q and A for LEAP***

Q. how would you analyse the leapp preupgrade report ? what would you usually look for ?

Q. how would you analyse the leapp preupgrade report ? what would you usually look for ?

A. In the report, it's best to read all the messages there. The messages there are generated for that one system to be upgraded, so all of them are relevant. However, if you feel there's too many, you can read at least those with the high severity and those that have the inhibitor flag.

The pre-upgrade report is to be found here: /var/log/leapp/leapp-report.txt

**Parallel workload migration**

[Presentaion link](https://docs.google.com/presentation/d/1FvTTalPdgFdGw5PAQmcIf9zWNe_bQEptkCpOABojC8E/edit)

Note: all instances will be converted to boot from volume

**Framework for RHOSP13-16**

[Presentaion link](https://docs.google.com/presentation/d/155hbqQUpYIIYWSspBGxDoOyBSM0JUU7TmL4bX_N7oNU/edit#slide=id.g547716335e_0_260)

30-06-2020

Issue faced:

1) tag 16.1 was not available registry.redhat.io/rhosp-rhel8 and have to change the namespace to registry.redhat.io/rhosp-beta for pulling container images with tag 16.1

2) swift rsync and health check container failed to start, raised the BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1852360

3) If we using filestore and osd-scenario = collocated then we need to apply fix per BZ and re-run the UC upgrade again.
https://bugzilla.redhat.com/show_bug.cgi?id=1844591

~~~
ceph3_namespace: docker-registry.upshift.redhat.com/ceph
ceph3_tag: ceph-3.3-rhel-7-containers-candidate-76429-20200625173020
ceph3_image: ceph-3.3-rhel-7
~~~

02-July-2020

tripleO upgrade workflow

> https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/README.rst

step by step presentation from the OSP14 to 15 upgrade which would cover most of the workflow, except the OSP15 db migrations part and the computes hybrid part. But for the leapp upgrade, it gives a nice idea on how the procedure works

Presentations:-

> http://file.brq.redhat.com/~jstransk/talks/2019/sprint-info-upgrade-with-os/#/

> http://file.brq.redhat.com/~jstransk/talks/2019/november-ffu-13-16/#/

flow chart

> http://file.bne.redhat.com/~dmacpher/graphics/ffwd2.png

> fix for migration

https://review.opendev.org/#/c/736173/9

03-July-2020

filestore to bluestore

aplly patch https://review.opendev.org/#/c/733812