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! 

-- 
  Zach Villers
  zach@mailup.net



On Thu, Jan 31, 2019, at 5:47 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
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


_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Attachments: