greetings everyone.
I thought I would send out an email about where we are with staging and get more input on some things related to that. :)
Account system / noggin:
I will let the noggin team report here. I know they have been working on deployment and fixing issues they hit. I don't think other things a blocking them. Please do chime in here noggin team!
Buildsystem side:
* koji hub is up * koji db is up, but the prod->stg sync script failed with a db error. Still need to debug what is wrong there. Likely the koji db schema changed and we need to adjust the sync script. * The x86_64 and s390x buildvm's are up. * The aarch64/armv7 and ppc64le builders are not yet up. I need to talk with smooge next week when he is back and we need to adjust vlans and such to get them online. * I haven't deployed the aarch64 osbs yet, but it should be doable.
* I am currently doing a load of the db01 prod server db into db01.stg. This will then need adjustment for staging users/passwords on a app by app basis. This is a good time/place to change staging applications db passwords.
Things I have not deployed and why:
* basset - unclear if we are wanting this again to interface with noggin or not.
* datagrepper/datanommer - We did not save any of the staging databases sadly, so we would need to start with a copy of prod, but since we plan to redo this application soon, I thought why not just wait until then and we can deploy the replacement in stg.
* notifs - This is also going to get replaced, but also it would be difficult to deploy in stg since it's on a EOL fedora.
* badges - do we want to deploy this in stg? Or was it going to move to openshift?
* fedimg - we don't compose images in stg yet and we were going to replace this anyhow.
* mailman - Also wanting to be redeployed, so figured there wasn't much point in deploying the old thing again now.
So, basically everything is installed, we need to go and fix applications now that aren't working. Perhaps this could be a good use of a monitoring solution test. :)
One thing that needs doing soon is getting sssd working correctly in staging, which will allow non root logins and sudo and hopefully groups (some of which are used in playbooks). I hope to look more into that next week.
Thoughts? questions?
kevin
On Fri, Sep 18, 2020 at 3:32 PM Kevin Fenzi kevin@scrye.com wrote:
greetings everyone.
I thought I would send out an email about where we are with staging and get more input on some things related to that. :)
Account system / noggin:
I will let the noggin team report here. I know they have been working on deployment and fixing issues they hit. I don't think other things a blocking them. Please do chime in here noggin team!
Buildsystem side:
- koji hub is up
- koji db is up, but the prod->stg sync script failed with a db error.
Still need to debug what is wrong there. Likely the koji db schema changed and we need to adjust the sync script.
- The x86_64 and s390x buildvm's are up.
- The aarch64/armv7 and ppc64le builders are not yet up. I need to talk
with smooge next week when he is back and we need to adjust vlans and such to get them online.
I haven't deployed the aarch64 osbs yet, but it should be doable.
I am currently doing a load of the db01 prod server db into db01.stg.
This will then need adjustment for staging users/passwords on a app by app basis. This is a good time/place to change staging applications db passwords.
Things I have not deployed and why:
- basset - unclear if we are wanting this again to interface with noggin
or not.
- datagrepper/datanommer - We did not save any of the staging databases
sadly, so we would need to start with a copy of prod, but since we plan to redo this application soon, I thought why not just wait until then and we can deploy the replacement in stg.
- notifs - This is also going to get replaced, but also it would be
difficult to deploy in stg since it's on a EOL fedora.
- badges - do we want to deploy this in stg? Or was it going to move to
openshift?
- fedimg - we don't compose images in stg yet and we were going to
replace this anyhow.
- mailman - Also wanting to be redeployed, so figured there wasn't much
point in deploying the old thing again now.
So, basically everything is installed, we need to go and fix applications now that aren't working. Perhaps this could be a good use of a monitoring solution test. :)
One thing that needs doing soon is getting sssd working correctly in staging, which will allow non root logins and sudo and hopefully groups (some of which are used in playbooks). I hope to look more into that next week.
Thoughts? questions?
Thanks for getting this far along, Kevin! It's still on my plate to fix the mailman3 stack and get everything into Fedora...
Thanks for the update!
Account system / noggin:
IPA is deployed, Noggin is deployed, FASJSON (the REST API) is deployed, Ipsilon is deployed. Yesterday we manage to have the elections app authenticate a random user (that would be me) through Ipsilon (OIDC) as before, except Ipsilon is now authenticating against IPA's LDAP server and getting user data from FASJSON. We're unsure of OpenID (not-connect) support and we're investigating that right now with one of the apps that still do not talk OIDC. We're also working on the import script (FAS2IPA) but we haven't run it yet, so your accounts aren't there yet.
- basset - unclear if we are wanting this again to interface with noggin
or not.
Yes please! I have a plugin to add to Basset for Noggin support but the plan is to reuse it. It's not highest priority for us right now though, so please do it when you have nothing more urgent.
Cheers! Aurélien
On Fri, Sep 18, 2020 at 10:04:32PM +0200, Aurelien Bompard wrote:
Thanks for the update!
Account system / noggin:
IPA is deployed, Noggin is deployed, FASJSON (the REST API) is deployed, Ipsilon is deployed. Yesterday we manage to have the elections app authenticate a random user (that would be me) through Ipsilon (OIDC) as before, except Ipsilon is now authenticating against IPA's LDAP server and getting user data from FASJSON.
Excellent!
We're unsure of OpenID (not-connect) support and we're investigating that right now with one of the apps that still do not talk OIDC.
Yeah... if we switch to keycloak at some point we loose that too. But I guess it's worth trying to make work now.
We're also working on the import script (FAS2IPA) but we haven't run it yet, so your accounts aren't there yet.
ok.
- basset - unclear if we are wanting this again to interface with noggin
or not.
Yes please! I have a plugin to add to Basset for Noggin support but the plan is to reuse it. It's not highest priority for us right now though, so please do it when you have nothing more urgent.
ok. I will put this (low) on the list for next week...
kevin
Dear all, are there any plans to revamp and re-deploy the packages app that was hosted on https://apps.fedoraproject.org/packages previously? Thanks.
On 9/22/20 4:21 AM, Flo H wrote:
are there any plans to revamp and re-deploy the packages app that was hosted on https://apps.fedoraproject.org/packages previously?
There are two different replacements; no decision on which one will be used has been made yet. It also seems that communishift won't be coming back for a while, so it probably will take some time before anything happens.
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
On Tue, Sep 22, 2020 at 02:13:23PM -0500, Brendan Early wrote:
On 9/22/20 4:21 AM, Flo H wrote:
are there any plans to revamp and re-deploy the packages app that was hosted on https://apps.fedoraproject.org/packages previously?
There are two different replacements; no decision on which one will be used has been made yet. It also seems that communishift won't be coming back for a while, so it probably will take some time before anything happens.
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
Well, we do have staging available and we can also perhaps spin up some instances in ec2 to test with.
Can you share with us the state of fedora-packages-static? If we wanted to spin up a test / deploy in stg is it ready for that? Or needs more work?
Msuchy: can you share the same info on fedora-packages-ng?
I'd kind of be leaning toward fedora-packages-static myself because it makes sense to me that the data is pretty static and also Msuchy has a bunch of other things on his plate. :)
kevin
On 9/23/20 11:29 AM, Kevin Fenzi wrote:
Well, we do have staging available and we can also perhaps spin up some instances in ec2 to test with.
Can you share with us the state of fedora-packages-static? If we wanted to spin up a test / deploy in stg is it ready for that? Or needs more work?
I have a Dockerfile sitting in a PR pending review from Timothée. As soon as that's merged it should be ready to go for testing.
On Sat, Sep 26, 2020 at 07:34:16PM -0500, Brendan Early wrote:
On 9/23/20 11:29 AM, Kevin Fenzi wrote:
Well, we do have staging available and we can also perhaps spin up some instances in ec2 to test with.
Can you share with us the state of fedora-packages-static? If we wanted to spin up a test / deploy in stg is it ready for that? Or needs more work?
I have a Dockerfile sitting in a PR pending review from Timothée. As soon as that's merged it should be ready to go for testing.
Awesome. Thanks.
kevin
infrastructure@lists.fedoraproject.org