Migrate Open-E FC Targets
Closed this issue · 3 comments
briansumma commented
Is it possible to Migrate Open-E Fibre Channel BLOCKIO Targets (also based on SCST and LVM) to ESOS?
msmith626 commented
I don't see why not. It would of course be a disruptive
migration/transition, but you should be able to boot ESOS on the same
hardware and produce a similar configuration. Especially if you have the
scst.conf file from the Open-E machine. Do you know which version of SCST
Open-E uses in the release you're running?
…--Marc
On Tue, Oct 9, 2018 at 11:40 AM Brian Summa ***@***.***> wrote:
Is it possible to Migrate Open-E Fibre Channel BLOCKIO Targets (also based
on SCST and LVM) to ESOS?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#222>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFkL3q_R3XHWKXELMNb0p8sseV8FcrMnks5ujMNZgaJpZM4XTkrO>
.
briansumma commented
I believe it [Open-E] still uses SCST 2.2.0 and is Debian based.
Other than being disruptive do you suspect it would be destructive? Obviously I would back up first but a “nuke and pave” is not my first choice.
—Brian
… On Oct 9, 2018, at 8:04 PM, Marc A. Smith ***@***.***> wrote:
I don't see why not. It would of course be a disruptive
migration/transition, but you should be able to boot ESOS on the same
hardware and produce a similar configuration. Especially if you have the
scst.conf file from the Open-E machine. Do you know which version of SCST
Open-E uses in the release you're running?
--Marc
On Tue, Oct 9, 2018 at 11:40 AM Brian Summa ***@***.***>
wrote:
> Is it possible to Migrate Open-E Fibre Channel BLOCKIO Targets (also based
> on SCST and LVM) to ESOS?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#222>, or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFkL3q_R3XHWKXELMNb0p8sseV8FcrMnks5ujMNZgaJpZM4XTkrO>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
msmith626 commented
No, I wouldn't expect it to be destructive as long as the SCST
configuration is the same (eg, keep exact same device name so EUI stays the
same, and especially make sure the logical block size... blocksize
attribute... is the same).
But yes, I'd have a good solid backup just in case. I have upgraded ESOS
machines from a long time ago that used SCST 2.x to newer versions of ESOS
which use SCST 3.x without issue.
…--Marc
On Tue, Oct 9, 2018 at 8:27 PM Brian Summa ***@***.***> wrote:
I believe it [Open-E] still uses SCST 2.2.0 and is Debian based.
Other than being disruptive do you suspect it would be destructive?
Obviously I would back up first but a “nuke and pave” is not my first
choice.
—Brian
> On Oct 9, 2018, at 8:04 PM, Marc A. Smith ***@***.***>
wrote:
>
> I don't see why not. It would of course be a disruptive
> migration/transition, but you should be able to boot ESOS on the same
> hardware and produce a similar configuration. Especially if you have the
> scst.conf file from the Open-E machine. Do you know which version of SCST
> Open-E uses in the release you're running?
>
> --Marc
>
>
> On Tue, Oct 9, 2018 at 11:40 AM Brian Summa ***@***.***>
> wrote:
>
> > Is it possible to Migrate Open-E Fibre Channel BLOCKIO Targets (also
based
> > on SCST and LVM) to ESOS?
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#222>, or mute the thread
> > <
https://github.com/notifications/unsubscribe-auth/AFkL3q_R3XHWKXELMNb0p8sseV8FcrMnks5ujMNZgaJpZM4XTkrO
>
> > .
> >
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#222 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFkL3jZbyVk3wcBvmLyfXQYZbCsA41Ijks5ujT7mgaJpZM4XTkrO>
.