All,
I wanted to make everyone aware that its been announced that Openshift V2
will be closing down on September 30th. We currently run our Redmine and
Prprocessor on this infrastructure. This means that we will either need to
find new homes for these or migrate them to Openshift V3. More details will
follow as we work toward a solution. If anyone has concerns, or different
suggestions feel free to share them here.
To add to that, Evgeni, Michael & I were discussing this on IRC earlier
today. Evgeni and I will trial a migration to Openshift V3 next week
and report back.
Greg
–
IRC / Twitter: @gwmngilfen
Diaspora: gwmngilfen@joindiaspora.com
> All,
>
> I wanted to make everyone aware that its been announced that Openshift V2
> will be closing down on September 30th. We currently run our Redmine and
> Prprocessor on this infrastructure. This means that we will either need to
> find new homes for these or migrate them to Openshift V3. More details will
> follow as we work toward a solution. If anyone has concerns, or different
> suggestions feel free to share them here.
Isn't theforeman.org also running on OpenShift v2?
–
Eric D. Helms
Red Hat Engineering–
You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Daniel Lobato Garcia
@dLobatog
blog.daniellobato.me
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato
Thanks folks for doing this!
– Ivan
On Fri, 2017-08-25 at 09:39 -0400, Eric D Helms wrote:
All,
I wanted to make everyone aware that its been announced that
Openshift V2 will be closing down on September 30th. We currently run
our Redmine and Prprocessor on this infrastructure. This means that
we will either need to find new homes for these or migrate them to
Openshift V3. More details will follow as we work toward a solution.
If anyone has concerns, or different suggestions feel free to share
them here.To add to that, Evgeni, Michael & I were discussing this on IRC earlier
today. Evgeni and I will trial a migration to Openshift V3 next week
and report back.Greg
IRC / Twitter: @gwmngilfen
Diaspora: gwmngilfen@joindiaspora.com–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,
Nope, this is running on web02.rackspace.theforeman.org.
Michael Moll
Update from today's testing… many thanks to Evgeni for his help!
There are 3 apps listed on the v2 platform:
http://pluginmatrix-theforeman.rhcloud.com/
I don't think this is in active use, but if it's still needed, we can
add it to the migration list. No action taken so far.
We got this running on v3 without too much effort. I updated the
webhook in foreman_templates to test against the new URL and saw a post
from GitHub in the logs, things seemed to happen.
We think this is ready for larger testing - ideally we'd like to use
Foreman core as lots happens there. Process would be to alter the url
of the webhook to the new processor and let it run for a day or two to
check all is fine. We can then look at updating the webhooks on all the
configured repos (there is a script to do this in the codebase).
There are some small niggle to figure out as part of that, such as
getting a sensible custom url, and making cron work. we're confident we
can get that running.
Does anyone have concerns over enabling this in a few days time on
foreman/foreman for testing? I'll notify again before I do so, just in
case.
Obviously more complex, but initial tests have gone well. We got Psql
and Redmine (from our fork, with a few extra patches) running, db
migrated (clean, not a copy of ours), and could see the web interface.
Cron will also need enabling here (as above) and outgoing email needs
testing too, but so far it's promising.
We're requesting more resources to our account so that we can try a
larger test, and I'll update again once that's done. I *think we may be
able to run them side-by-side for a bit, which will allow some user
load testing - this is important as we have to move up to Ruby 2.2 or
2.3 as part of this (v2 is on 1.9.3), so making sure nothing subtle is
broken will help.
So far so good. Thanks again to Evgeni for the help!
Greg
In addition, we realized today that there is another project we should
migrate (and migrate to Foreman proper) the etherpad that is under the
Katello namespace:
http://pad-katello.rhcloud.com
Update from today’s testing… many thanks to Evgeni for his help!
There are 3 apps listed on the v2 platform:Pluginmatrix
http://pluginmatrix-theforeman.rhcloud.com/
I don’t think this is in active use, but if it’s still needed, we can
add it to the migration list. No action taken so far.PrProcessor
We got this running on v3 without too much effort. I updated the
webhook in foreman_templates to test against the new URL and saw a post
from GitHub in the logs, things seemed to happen.We think this is ready for larger testing - ideally we’d like to use
Foreman core as lots happens there. Process would be to alter the url
of the webhook to the new processor and let it run for a day or two to
check all is fine. We can then look at updating the webhooks on all the
configured repos (there is a script to do this in the codebase).There are some small niggle to figure out as part of that, such as
getting a sensible custom url, and making cron work. we’re confident we
can get that running.Does anyone have concerns over enabling this in a few days time on
foreman/foreman for testing? I’ll notify again before I do so, just in
case.Redmine
Obviously more complex, but initial tests have gone well. We got Psql
and Redmine (from our fork, with a few extra patches) running, db
migrated (clean, not a copy of ours), and could see the web interface.
Cron will also need enabling here (as above) and outgoing email needs
testing too, but so far it’s promising.We’re requesting more resources to our account so that we can try a
larger test, and I’ll update again once that’s done. I *think we may be
able to run them side-by-side for a bit, which will allow some user
load testing - this is important as we have to move up to Ruby 2.2 or
2.3 as part of this (v2 is on 1.9.3), so making sure nothing subtle is
broken will help.So far so good. Thanks again to Evgeni for the help!
Greg–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
I would expect that to be easy enough, but I have no access to the
katello openshift namespace. Once we've moved the rest we can sync on
getting that migrated.
No word yet on the requested extra resources.
Greg
Yea - I honestly don't think we even need to migrate the etherpad per say.
But rather, just spin up a new etherpad that we can make use of and note to
users to port any existing "long lived" pads over themselves.
Eric
On Wed, 2017-08-30 at 11:22 -0400, Eric D Helms wrote:
In addition, we realized today that there is another project we
should migrate (and migrate to Foreman proper) the etherpad that is
under the Katello namespace:I would expect that to be easy enough, but I have no access to the
katello openshift namespace. Once we’ve moved the rest we can sync on
getting that migrated.No word yet on the requested extra resources.
Greg
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
You all waiting on me?
– bk
No, I've filled out the internal form requesting additional Openshift
resources, and I'm waiting to hear back, so I assume we need to wait for
the process to complete. However, if there is any way for you to find
out how that's progressing, please do - time is of the essence for the
end-of-Sept deadline.
Thanks
Greg