Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of work last year, we got a RHOSP13 cloud up and mostly working, but it was a ton of work. After hearing from the Fedora Council and our various management chains we determined that it wouldn't really be a good use of our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we had allocated to this, but are weighing our options. We may want to setup OpenShift bare nodes so we can do kubevirt, we may want to just setup a normal virthost setup managed by ansible.
For the items currently in our cloud, we will be looking at options for them, we are definitely not shutting things off until we have plans in place.
Happy to answer any questions and will make sure everything is properly migrated.
kevin
This solution may not have a problem to solve ( a use case ) - a space for prototyping apps/solutions using buildah/podman/crio would be good, especially if there is a rule that everything done there is wiped out on a periodic basis. If it is on an isolated network, it might be a good space for an apprentice sandbox as well.
There may be other, more pressing needs, but if high value/low maintenance is the goal, this is a step in that direction possibly.
Happy Friday!
On Thu, Jan 31, 2019, at 5:05 PM, Kevin Fenzi wrote:
Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of work last year, we got a RHOSP13 cloud up and mostly working, but it was a ton of work. After hearing from the Fedora Council and our various management chains we determined that it wouldn't really be a good use of our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we had allocated to this, but are weighing our options. We may want to setup OpenShift bare nodes so we can do kubevirt, we may want to just
If the goal is OpenShift w/ KubeVirt, I'd love to help set it up. Been hoping to play around with that configuration.
V/r, James Cassell
Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of work last year, we got a RHOSP13 cloud up and mostly working, but it was a ton of work. After hearing from the Fedora Council and our various management chains we determined that it wouldn't really be a good use of our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we had allocated to this, but are weighing our options. We may want to setup OpenShift bare nodes so we can do kubevirt, we may want to just setup a normal virthost setup managed by ansible.
For the items currently in our cloud, we will be looking at options for them, we are definitely not shutting things off until we have plans in place.
Happy to answer any questions and will make sure everything is properly migrated.
Do we have a documented list of services running on that cloud instance?
Do we have a timeline?
Dne 27. 02. 19 v 23:00 Peter Robinson napsal(a):
Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of work last year, we got a RHOSP13 cloud up and mostly working, but it was a ton of work. After hearing from the Fedora Council and our various management chains we determined that it wouldn't really be a good use of our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we had allocated to this, but are weighing our options. We may want to setup OpenShift bare nodes so we can do kubevirt, we may want to just setup a normal virthost setup managed by ansible.
For the items currently in our cloud, we will be looking at options for them, we are definitely not shutting things off until we have plans in place.
Happy to answer any questions and will make sure everything is properly migrated.
Do we have a documented list of services running on that cloud instance?
From inventory/inventory:
[persistent-cloud] # artboard instance artboard.fedorainfracloud.org # copr production instances copr-be.cloud.fedoraproject.org copr-fe.cloud.fedoraproject.org copr-keygen.cloud.fedoraproject.org # copr dev instances copr-be-dev.cloud.fedoraproject.org copr-fe-dev.cloud.fedoraproject.org # taiga for kanban-style project planning taiga.fedorainfracloud.org taigastg.fedorainfracloud.org # glittergallery GSoC dev work glittergallery-dev.fedorainfracloud.org # fas2-dev fas2-dev.fedorainfracloud.org # fas3-dev fas3-dev.fedorainfracloud.org # Community Blog communityblog.fedorainfracloud.org # Fedora Magazine #magazine.fedorainfracloud.org magazine2.fedorainfracloud.org # Ansible Magazine ansiblemagazine.fedorainfracloud.org # Flock RegCfp instance regcfp2.fedorainfracloud.org # Fedora Bootstrap VM fedora-bootstrap.fedorainfracloud.org # lists development instance lists-dev.fedorainfracloud.org # java-deptools ticket 4846 java-deptools.fedorainfracloud.org # developer ticket 4876 developer.fedorainfracloud.org # fedimg-dev development instance fedimg-dev.fedorainfracloud.org # iddev iddev.fedorainfracloud.org # commops - ticket 5380 commops.fedorainfracloud.org # respins respins.fedorainfracloud.org # upstreamfirst - ticket 6066 upstreamfirst.fedorainfracloud.org # elastic devel instance - ticket 6479 elastic-dev.fedorainfracloud.org # koji simple ci development - ticket 6419 simple-koji-ci-dev.fedorainfracloud.org simple-koji-ci-prod.fedorainfracloud.org # telegram-irc bridge machine - ticket 6781 telegram-irc.fedorainfracloud.org # Happiness packets happinesspackets.fedorainfracloud.org happinesspackets-stg.fedorainfracloud.org libravatar.fedorainfracloud.org libravatar-stg.fedorainfracloud.org
# # These are in the new cloud # testdays.fedorainfracloud.org
Miroslav
On 3/1/19 4:36 AM, Miroslav Suchý wrote:
Dne 27. 02. 19 v 23:00 Peter Robinson napsal(a):
Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of work last year, we got a RHOSP13 cloud up and mostly working, but it was a ton of work. After hearing from the Fedora Council and our various management chains we determined that it wouldn't really be a good use of our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we had allocated to this, but are weighing our options. We may want to setup OpenShift bare nodes so we can do kubevirt, we may want to just setup a normal virthost setup managed by ansible.
For the items currently in our cloud, we will be looking at options for them, we are definitely not shutting things off until we have plans in place.
Happy to answer any questions and will make sure everything is properly migrated.
Do we have a documented list of services running on that cloud instance?
From inventory/inventory:
...snip...
Thats just what is in ansible, there are other hosts also (although those should all be tranistory (copr builders or scratch hosts or test hosts, etc).
As for timeline, I was moving last week, so I should be able to get back to it this coming week, especially since we should be in freeze soon. Since my current plan is to make the aarch64 and ppc64le hosts virthosts, I am going to try and get that done first so they can be used before anything else needs to be done. There's some networking changes needed, but hopefully in the next few weeks those will be online and copr can look at just using them from it's existing old cloud nodes. Then we can move on to the rest of the setup.
kevin
On Sat, Mar 2, 2019 at 4:17 PM Kevin Fenzi kevin@scrye.com wrote:
On 3/1/19 4:36 AM, Miroslav Suchý wrote:
Dne 27. 02. 19 v 23:00 Peter Robinson napsal(a):
Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of work last year, we got a RHOSP13 cloud up and mostly working, but it was a ton of work. After hearing from the Fedora Council and our various management chains we determined that it wouldn't really be a good use of our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we had allocated to this, but are weighing our options. We may want to setup OpenShift bare nodes so we can do kubevirt, we may want to just setup a normal virthost setup managed by ansible.
For the items currently in our cloud, we will be looking at options for them, we are definitely not shutting things off until we have plans in place.
Happy to answer any questions and will make sure everything is properly migrated.
Do we have a documented list of services running on that cloud instance?
From inventory/inventory:
...snip...
Thats just what is in ansible, there are other hosts also (although those should all be tranistory (copr builders or scratch hosts or test hosts, etc).
As for timeline, I was moving last week, so I should be able to get back to it this coming week, especially since we should be in freeze soon. Since my current plan is to make the aarch64 and ppc64le hosts virthosts, I am going to try and get that done first so they can be used before anything else needs to be done. There's some networking changes needed, but hopefully in the next few weeks those will be online and copr can look at just using them from it's existing old cloud nodes. Then we can move on to the rest of the setup.
Could we consider using RHEV here? That would give us some way of doing API-based provisioning without requiring anywhere close to the complexity of RHOSP and still let us have some niceties like live migration across nodes as needed.
On 3/2/19 1:29 PM, Neal Gompa wrote:
On Sat, Mar 2, 2019 at 4:17 PM Kevin Fenzi kevin@scrye.com wrote:
On 3/1/19 4:36 AM, Miroslav Suchý wrote:
Dne 27. 02. 19 v 23:00 Peter Robinson napsal(a):
Hey everyone.
As you know, we currently have a RHOSP5 ancient cloud. After a bunch of work last year, we got a RHOSP13 cloud up and mostly working, but it was a ton of work. After hearing from the Fedora Council and our various management chains we determined that it wouldn't really be a good use of our time moving forward to keep maintaining a OpenStack cloud.
We have not yet determined what we want to do with the hardware that we had allocated to this, but are weighing our options. We may want to setup OpenShift bare nodes so we can do kubevirt, we may want to just setup a normal virthost setup managed by ansible.
For the items currently in our cloud, we will be looking at options for them, we are definitely not shutting things off until we have plans in place.
Happy to answer any questions and will make sure everything is properly migrated.
Do we have a documented list of services running on that cloud instance?
From inventory/inventory:
...snip...
Thats just what is in ansible, there are other hosts also (although those should all be tranistory (copr builders or scratch hosts or test hosts, etc).
As for timeline, I was moving last week, so I should be able to get back to it this coming week, especially since we should be in freeze soon. Since my current plan is to make the aarch64 and ppc64le hosts virthosts, I am going to try and get that done first so they can be used before anything else needs to be done. There's some networking changes needed, but hopefully in the next few weeks those will be online and copr can look at just using them from it's existing old cloud nodes. Then we can move on to the rest of the setup.
Could we consider using RHEV here? That would give us some way of doing API-based provisioning without requiring anywhere close to the complexity of RHOSP and still let us have some niceties like live migration across nodes as needed.
We looked at RHEV, but it only provided network isolation if you use openstack-neutron with it. There were some other things we couldn't get it to do easily also (but I can't recall the details, relrod evaluated it).
kevin
infrastructure@lists.fedoraproject.org
-
James Cassell -
Kevin Fenzi -
Miroslav Suchý -
Neal Gompa -
Peter Robinson -
Zach Villers