Not certain what version you are running, but in my test 4.3 (advanced
shared zone), i have 1 VM that i call IP -tracker - its always offline
and has 1cpu x 64mb offering. I use that VM to reserve IPs i dont want
cloudstack to give away.
All I do is attach a network interface i need it to be on and then under
nics i can assign more IP address to it. That feature is available in
cloudstack.
Regards
ilya
On 5/8/15 3:35 AM, Franky Hall wrote:
Hi Vadim,
Now that answer is spot-on. This development environment grew into a larger
site than I expected. I can migrate the VMs; they do not require 100% uptime,
but the owners do like them up m-f 8-5 ya know? I plan to build out another
environment and move things into it, but that will take some time. This is the
first cloudstack installation I’ve done and so far things work pretty well.
I’ve had to iron out a few kinks here and there, but things have been fine so
far and I’m reasonably pleased with the product.
Thank you, again, for your feedback. I will look into cloud monkey, it sounds
like a tool I will find useful.
Warm regards,
Franky
On May 8, 2015, at 1:10 AM, Vadim Kimlaychuk <vadim.kimlayc...@elion.ee> wrote:
Franky,
If you have to move such number of hosts at production I would
recommend you to learn CloudMonkey and have to set-up development environment
first. There you can develop migration strategy and execute test-cases for
re-partitioning the network. We all learn from experience and there will
always be better solution in the future. As I understand the issue is not
critical - everything works as expected, but you have some unpleasant
side-effects. So, be prepared - develop new network layout, test it at
development and execute the same at production. I see no other choice. Doing
changes at database level manually is probably the worst thing you may do.
Vadim.
-----Original Message-----
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Friday, May 08, 2015 10:45 AM
To: users@cloudstack.apache.org
Subject: Re: How to reserve IPs
dirty trick: spin up vms, login, disable startup scripts/remove kernel, brang
them down and leave them there to rot. The ip will never be used in cs again.
If you like this trick: don't operate a cloud. (don't take this as
condescending, just as my view on the thing)
Op vr 8 mei 2015 om 09:21 schreef Franky Hall <fra...@cartcrafter.com>:
I wish that were so easy. :( I have 200 VMs running across 5 hosts,
and what you described is not a process I have time to learn right
now. I do appreciate your reply and advice. Thank you!
-Franky
On May 7, 2015, at 9:57 PM, Vadim Kimlaychuk
<vadim.kimlayc...@elion.ee>
wrote:
Hello Franky,
I would not reccomend you to change database tables directly
in
order to fix errors in configuration. It is better to set-up
cloudstack again with the proper configuration.
Vadim
________________________________________
From: Franky Hall <fra...@cartcrafter.com>
Sent: Friday, May 8, 2015 1:22
To: users@cloudstack.apache.org
Subject: How to reserve IPs
Hello,
I made the mistake of putting my entire /22 into cloudstack for
private
IPs. I need to put some other things into that network (like network
file storage), and I’m wondering how I can make sure CloudStack never
tries to assign one of the IPs I ‘steal’.
Is it as easy as updating the `state` column in the
`user_ip_address`
table to ‘Allocated’? I’d like to ‘allocate’ about 20 IPs for things
not created in CloudStack. Is that safe, or is there another way to do it?
Thanks,
Franky
