blog: deploying OpenShift Origin Stand-alone Registry #432
Conversation
This blog post details how to use the OpenShift Origin installer to deploy a stand-alone registry on Fedora 25 Atomic Host. This can be used as a fallback source of documentation in case the Atomic Registry installer does not work successfully.
|
cc: @aweiteka @dustymabe |
|
so this is an alternative to the docs that already exist for the atomic registry? almost seems like we should fix those docs instead? |
|
The atomic registry is broken, and when people ask in #atomic -- basically every single day -- they're told to use the standalone registry instead. I think it's atomic registry that needs fixing or straight up retirement. |
i agree with that |
|
@aweiteka, wanna weigh in on this? |
I briefly discussed this in person with @aweiteka and my impression was that he didn't have the bandwidth necessary to maintain the current Atomic Registry installer and/or always be available for the questions that come up on #atomic. After spending the day getting familiar with the stand-alone registry installation process via OpenShift Origin, I think moving to the OO Registry instead of the Atomic Registry wouldn't be a difficult change. |
|
can we please schedule some time to chat about this? with all the people on this ticket? we also probably need to start a weekly projectatomic meeting where the projects can sync. |
Can we add it to the atomic-wg meeting agenda? I know that it is mostly Fedora specific there, but a majority of the involved folks have shown up to that meeting before. |
| $ git checkout openshift-ansible-3.4.24-1 | ||
| HEAD is now at 90f6a70... Automatic commit of package [openshift-ansible] release [3.6.24-1]. | ||
|
|
||
| The next step is to prepare the inventory file for the installer. My dedicated system for the registry has a 'public' IP address of `10.8.172.199`, so we use that value throughout. (I'm using a VM in a private OpenStack instance, so the 'public' IP address is only visible on our corporate network and is not reachable from the Internet.) |
|
From a meeting between @jberkus, @dustymabe, @aweiteka and myself, it was decided we would gather feedback about sunsetting the Atomic Registry and moving towards suggesting the use OpenShift Origin stand-alone registry. Until the feedback has been gathered, this post is on hold. |
|
|
||
| Running the installer will take a few minutes, but once it finished, we can get right to the registry console. | ||
|
|
||
| Assuming you have used a similar value for `openshift_master_default_subdomain`, you'll be able to access your registry console at a URL similar to `https://registry-console-default.10.8.172.199.xip.io/`. Just append `registry-console-default.` to your `openshift_master_default_subdomain`. |
There was a problem hiding this comment.
Note: the registry console host will be made configurable once I clean up and land openshift/openshift-ansible#4181
|
So it looks like it'll take a while to resolve the Atomic Registry question. Given that, I'd like to publish the blog post but wait on replacing the Atomic Registry docs. |
Sounds like a good approach. |
I'd rather not drag our feet on that considering it is broken and we're just going to get more people that waste their time. Not a good first user experience. |
|
Feel free to go ahead with this format, I'll work on a more "production ready"-type post later this week, taking into account the experience we've had standing up the registry for RDO. I'll link to this post so people have an easy "proof of concept" route to take. |
|
I've got a few edits to make before publishing this, but I'm a bit swamped in RHEL testing at the moment. I still think I can get them done in the next day or two. |
|
Pushed some changes to address feedback from @aweiteka and opened the door for another blog post about running the registry in production. |
|
We probably want another date than May 12? |
|
I fix the date when I publish. This will go out today. |
This blog post details how to use the OpenShift Origin installer to
deploy a stand-alone registry on Fedora 25 Atomic Host. This can be
used as a fallback source of documentation in case the Atomic Registry
installer does not work successfully.