How to move existing VR to new Public IP Range

2018-10-02 Thread Netlynker
Hi,

Here is the scenarios -

- 1 vNet with Source NAT enabled
- Public IP (x.x.x.x | vlan 777)
- Private Subnet (y.y.y.y/24)
- User’s VM instances running inside the private subnet.

New public IP range has been added into CloudStack physical network -
z.z.z.z/28
How can I move VR to newly created public IP range with least impact to
user’s VM instances?

Thanks in advance,
Netlynker


RE: ***UNCHECKED*** Re: Network "restart required - yes"

2018-10-02 Thread Paul Angus
I'm fairly sure restart with clean up should destroy and recreate both simple 
VRs and VPCs
From watching the cloud.log when using restart (without cleanup) against a VPC 
- it didn't seem to do anything.

paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Andrija Panic  
Sent: 20 September 2018 11:11
To: users 
Subject: Re: ***UNCHECKED*** Re: Network "restart required - yes"

ok, thx once more :)

On Wed, 19 Sep 2018 at 18:06, Rafael Weingärtner < rafaelweingart...@gmail.com> 
wrote:

> >
> > Btw, do you know what actually REALLY happens when you restart 
> > Network (part of VPC), not the whole VPC - since I was not clear if 
> > this does anything (and it takes 1-3 seconds only...)
> >
> I have checked this before, but I do not know it by heart now.
> If I had to guess, I would that say restart network will reboot the VR.
> Restart network with cleanup (not the VPC) will remove and add 
> configurations applied in the VR after the reboot.
> Restart network with cleanup (in the VPC) will destroy and recreate the VR.
>
> On Wed, Sep 19, 2018 at 12:35 PM, Andrija Panic 
> 
> wrote:
>
> > Hi Rafael,
> >
> > thanks a lot for digging into code - I undestand possible situations 
> > now
> -
> > thx.
> >
> > Btw, do you know what actually REALLY happens when you restart 
> > Network (part of VPC), not the whole VPC - since I was not clear if 
> > this does anything (and it takes 1-3 seconds only...)
> >
> > thx again
> >
> > On Wed, 19 Sep 2018 at 15:52, Rafael Weingärtner < 
> > rafaelweingart...@gmail.com> wrote:
> >
> > > According to the code:
> > >
> > > >  a lot more code here
> > > >
> > >  if (forceCleanup) {
> > > >
> > >if (!rollingRestartVpc(vpc, context)) {
> > > >s_logger.warn("Failed to execute a rolling restart as a 
> > > > part
> of
> > > VPC
> > > > " + vpc + " restart process");
> > > >restartRequired = true;
> > > >return false;
> > > >}
> > > >return true;
> > > >
> > > }
> > > >
> > > s_logger.debug("Starting VPC " + vpc + " as a part of VPC restart
> process
> > > > without cleanup");
> > > > if (!startVpc(vpcId, false)) {
> > > > s_logger.warn("Failed to start vpc as a part of VPC " + 
> > > > vpc
> + "
> > > > restart process");
> > > > restartRequired = true;
> > > > return false;
> > > >  }
> > > >
> > >  a lot more code here
> > > >
> > > final VpcVO vo = _vpcDao.findById(vpcId);
> > > > vo.setRestartRequired(restartRequired);
> > > > _vpcDao.update(vpc.getId(), vo);
> > > >
> > >  a lot more code here
> > >
> > >
> > > That means,  something wrong happened either in 
> > > "rollingRestartVpc" or "startVpc" methods. Therefore, all of the 
> > > affected networks should
> > present
> > > log entries such as " Failed to start vpc as a part of VPC " or "
> > > Failed to execute a rolling restart as a part of VPC "
> > >
> > > On Wed, Sep 19, 2018 at 10:42 AM, Simon Weller 
> > >  >
> > > wrote:
> > >
> > > > Without digging into the code, I believe that the VR reports the
> > version
> > > > and it's matched against the min version. i'm not sure what 
> > > > happens
> if
> > > the
> > > > version is not reported at all.
> > > >
> > > > Is this recent and have you updated the system QCOW2 or 
> > > > systemvm.iso recently? And if so, did you rebuild the rpms, or 
> > > > manually place the
> > > image
> > > > or iso?
> > > >
> > > >
> > > > - Si
> > > >
> > > > 
> > > > From: Andrija Panic 
> > > > Sent: Wednesday, September 19, 2018 8:35 AM
> > > > To: users
> > > > Subject: Re: Network "restart required - yes"
> > > >
> > > > Just did some SQL - only 19 networks in this state (requires
> > restart...),
> > > > so a few of VPCs
> > > >
> > > > Minimum template version ss 4.6.0 (we run acs 4.8.x)
> > > >
> > > > and just checked all VRs from DB, did SQL, all existing routers 
> > > > are
> on
> > > this
> > > > version (4.6.0)
> > > >
> > > > Hm...
> > > >
> > > >
> > > > On Wed, 19 Sep 2018 at 15:02, Simon Weller 
> > > > 
> > > > wrote:
> > > >
> > > > > Andrija,
> > > > >
> > > > >
> > > > > Is this isolated to that particular VPC, or is this across the
> entire
> > > > > zone? What's the minreq.sysvmtemplate.version global set to?
> > > > >
> > > > >
> > > > > - Si
> > > > >
> > > > > 
> > > > > From: Andrija Panic 
> > > > > Sent: Wednesday, September 19, 2018 7:55 AM
> > > > > To: users
> > > > > Subject: Re: Network "restart required - yes"
> > > > >
> > > > > Actually, its the filed called "Restart required" - check here:
> > > > > https://pasteboard.co/HEBUmB0.png
> > > > >
> > > > > you go to inside VPC, click on network, and there it is...
> > > > >
> > > > >
> > > > > Thanks !
> > > > >
> > > > > On Wed, 19 Sep 2018 at 14:42, Rafael Weingärtner < 
> > > > > rafaelweingart...@gmail.com> wrote:
> > > > >
> > > > > >