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, Aug 30, 2017 at 12:25 PM, Greg Sutcliffe <[email protected]> wrote: > 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: > > > > http://pad-katello.rhcloud.com > > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
