diff --git a/aws/proposals/os-packages/README.md b/aws/proposals/os-packages/README.md new file mode 100644 index 00000000..9c17683e --- /dev/null +++ b/aws/proposals/os-packages/README.md @@ -0,0 +1,38 @@ +1. create a new satellite channel for rhel8 and rhel9 for aws +1. census-aws-... or similar +1. establish a couple of build machines, one for rhel8, one for 9 +1. establish a process to grab the source (github) and build +1. document the general process in a csvd repo (a new one, census-aws-packages or somethign like that) + * how to do for + * rpm build from spec + * pre-packaged rpm (add to repo) + * single binary or small set of binaries (rpm, ansible)? +1. more complicated setup (aws cli, for example)? +1. directions on how to do it for each package, minimally + * amazon-efs-utils + * amazon-ssm-agent +1. we may want to also do such a thing for utlities which need to be deployed, like + * session-manager-plugin + * aws_signing_helper (Release Release: v1.7.0 ยท aws/rolesanywhere-credential-helper) + * aws-cli +1. have either ansible or rpm ways to install all these things +1. perhaps use some sort of in-aws cicd for all of them? some are packages to build from spec, some are existing rpms to download and re-distribute (say, pop into our yum repo in satellite and on nexus) + +we have a lot of things we put in place for cloud stuff +many don't have rpms +but we need to install them on rhel boxes, sometimes on al2023 boxes (so on yum repo if rpm in nexus), and sometimes containers (apt-based) +this is a larger enterprise problem to solve +the signing helper, for example, newer versions use a newer glibc and fail, so they need to be re-built +prob need to spin up a group to chat about this + + +* pre-built rpm (easy, drop in self-hosted repo) + * session-manager plugin + * amazon-ssm-agent +* github, with spec file, needs build + * amazon-efs-utils +* github, non-spec file + * aws_signing_helper +* other install + * awscli +* and all the various other tools which shoudl have some packaging around them too