The target domain already exists with VMs running in it On Fri, Apr 26, 2024 at 1:46 PM Daan Hoogland <daan.hoogl...@gmail.com> wrote:
> so probably a stupoid suggestion, but why ot rename the domain then? > > On Fri, Apr 26, 2024 at 1:04 PM Ruben Bosch <ruben.bo...@cldin.eu> wrote: > > > > Hi Daan, cases may vary. For our first migration in the end all VMs will > > move to the other domain. > > > > On Fri, Apr 26, 2024 at 12:32 PM Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > > > > > Ruben, do you need to move domainA completely to domainB or do you > > > need to move *some* VMs from it? > > > > > > On Fri, Apr 26, 2024 at 11:00 AM Ruben Bosch <ruben.bo...@cldin.eu> > wrote: > > > > > > > > Hi all, > > > > > > > > We're looking into the following. We are using advanced networking > on ACS > > > > 4.16.1 (upgrading soon to 4.18.1). We have a guest network that is > > > assigned > > > > to a specific domain A (ROOT/foo/domainA). Now we will need to move > VMs > > > > from domain A to domain B (ROOT/bar/domainB) while preserving IP > > > addresses. > > > > We are exploring our options on how to make this a seamless > transition. > > > We > > > > have found that: > > > > > > > > - we cannot add the network with the same parameters again, as it > fails > > > on > > > > IP address start/end overlap check > > > > - we cannot add the extra domain in the "domain_network_ref" table > as it > > > > yields no result > > > > - we can assign the domain to ROOT and ensure no other users can > claim > > > IPs > > > > by updating "state" in "user_ip_address" > > > > > > > > Are there any other options available that we can think of? I'm > looking > > > > forward to your input. > > > > > > > > Kind regards, > > > > > > > > Ruben Bosch > > > > > > > > > > > > -- > > > Daan > > > > > > > -- > Daan >
